ECI Telematics ASYNC-XS Manual

ASYNCXS Manual
Publication Number C320001300D0

February 1993
TELEMATICS INTERNATIONAL, INCORPORATED

Worldwide Headquarters
1201 Cypress Creek Road
Fort Lauderdale, Florida 33309
UNITED STATES
(305) 7723070
TELEMATICS INTERNATIONAL, LTD.
European Headquarters
ISIS House, Reading Road
Chineham, Basingstoke
Hampshire RG24 OTW
UNITED KINGDOM
(0256) 467385
Disclaimer
Telematics reserves the right to change this document, its contents, and
any products described herein at any time without prior notification.
The information in this document has been reviewed for accuracy, clarity,
and completeness. Telematics is not responsible for any errors that may
occur in this document. If you find any errors, please report them to
Telematics:
TELEMATICS INTERNATIONAL, INCORPORATED
Documentation Department
Worldwide Headquarters
1201 Cypress Creek Road
Fort Lauderdale, Florida 33309 U.S.A.
Telematics reserves the right to use or distribute freely any information
supplied by readers without incurring obligations.
Any unauthorized use, duplication, or distribution of this document or any
part thereof without the prior written consent of Telematics is strictly
prohibited.
Copyright Telematics International, Inc., 1993. All rights reserved.
Revision History
ii
A0
November 1987. Compatible with A.1 software
B0
February 1989. Compatible with E.0 software.
C0
August 1989. Compatible with G.0 software.
D0
February 1993. Compatible with H.0 software.
ASYNCXS
C320001300D0
Contents
Introduction
Whats In This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Relationships To Other Telematics Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Related Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Standards Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operations
Connection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Signon Include Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Printers and DisplayOnly Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
In Case of A Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Command Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Data Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
PAD Service Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Break Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Data Accumulation and Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Typeahead Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Data Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Editing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Editing Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Special Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Creating Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Symbol Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Symbolic Assignment Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Symbol Inquiry Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Symbol Replacement Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Device Operational States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Modem Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Modem Subparameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Subparameter Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Incoming Call Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Port Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
PADmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
PADmap Routing Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
ASYNCXS
C320001300D0
iii
X.3 Profiles and Parameters
X.3 Profiles Types and Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

X.3 Parameter Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Value Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
X.3 Parameter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
X.3 Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
P0 National Marker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
P1 PAD Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
P2 Terminal Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
P3 Data Forwarding Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
P4 Data Forwarding on Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
P5 Flow Control of the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
P6 PAD Service Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
P7 Action of PAD on Receipt of Break Signal . . . . . . . . . . . . . . . . . . . . . . . . 311
P8 Discard Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
P9 Padding after Carriage Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
P10 Line Folding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
P11 Speed of Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
P12 Flow Control of the PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
P13 Line Feed After Carriage Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
P14 Padding after Line Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
P15 Editing in Data Transfer Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
P16 Character Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
P17 Line Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
P18 Line Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
P19 Editing PAD Service Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
P20 Echo Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
P21 Parity Treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
P22 Page Wait (not currently implemented) . . . . . . . . . . . . . . . . . . . . . . . . . . 317
P23 Additional Data Forwarding Character . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
P24 Additional Data Forwarding Character . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
P25 Output Delay Due to Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
P26 Interval Timer for Transmitting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
P27 Padding after Horizontal Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
P28 XON Character from PAD to Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
P29 XOFF Character from PAD to Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
P30 XON Character from Device to PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
P31 XOFF Character from Device to PAD . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
P80 Signon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
P81 Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
P82 Alternate Break Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
P83 Forwarding on Character Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
P84 Extended Read Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
P85 Local Discard Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
P86 Diagnostic Echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
ASYNCXS PMM Commands
Before Creating Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
iv
ASYNCXS
C320001300D0
ASYNCXS Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Add Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Collect Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Create Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Create Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Create Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Define Initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Delete Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Destroy Device|Directory|Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Disable Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Enable Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Erase Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Modify Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Modify Initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
Modify Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Reset Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Set Defaults Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Set Defaults Initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Set Defaults Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Show Defaults Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Show Defaults Initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Show Defaults Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Show Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Show Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Show Initial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Show Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Show Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Show Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
X.28 Commands
X.28 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

X.28 Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Aread . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
C (Call) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Call (Call Retry ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Clr (Clear) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Copyclr (Copy Clear) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Include . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
Intd (Interrupt and Discard) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Iclr (Invitation to Clear) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Npar (Network Parity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
ASYNCXS
C320001300D0
Parameter? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Prof (Profile Set) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Profile? (Profile Display) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Rpar? (Remote Parameter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Rprof (Remote Profile) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Rset (Remote Set) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Reset (Reset Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Stat (Status) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Tact (Port Test) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Tactt (Terminal Test) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Terminate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Wait . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
X28Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
X3Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
PAD Service Signals
Accounting Summary PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Acknowledge PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Clear PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Clear Cause Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
CCITT X.25 Clear Cause Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
CCITT X.25 Diagnostic Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Clear Service Signal Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Clear Confirmation PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Connected PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Invalid Command PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Reset PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Status PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Alarms
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
ASCII Character Set
IO Interface
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Include Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO Service Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO/CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO/CRDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
B1
B1
B2
B3
B4
B6
B8
B9
ASYNCXS
C320001300D0
IO/CRDIR Create Device Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B9

IO/CRDIR Create Profile Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B9
IO/CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B10
IO/CREATE Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B10
IO/CREATE Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B19
IO/DESTROY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B21
IO/DESTROY Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B21
IO/DESTROY Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B21
IO/DESTROY Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B21
IO/DISMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B22
IO/EXCHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B23
IO/EXCHANGE Define Initial Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . B24
IO/EXCHANGE Modify Initial Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . B25
IO/EXCHANGE Obtain Initial Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . B26
IO/EXCHANGE Deregister for Event Notification . . . . . . . . . . . . . . . . . . . . . B27
IO/EXCHANGE Pass Control to Handler Mode . . . . . . . . . . . . . . . . . . . . . . . B28
IO/EXCHANGE Pass Control to PAD Mode . . . . . . . . . . . . . . . . . . . . . . . . . . B29
IO/EXCHANGE Register for Event Notification . . . . . . . . . . . . . . . . . . . . . . . B30
IO/EXCHANGE Request X.25 Connection/Accept Incoming X.25 Call . . . . B32
IO/EXCHANGE Request X.25 Disconnection/Reject Incoming X.25 Call . . B36
IO/EXCHANGE Request Incoming Call Parameters . . . . . . . . . . . . . . . . . . . . B37
IO/EXCHANGE Modify Device Parameters While Online . . . . . . . . . . . . . . . B38
IO/INFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B39
IO/INFO Obtain Detailed Entity Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . B39
IO/INFO Obtain Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B40
IO/INFO Obtain Entity Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B40
IO/INFO Obtain Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B41
IO/INFO Obtain Profile Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B41
IO/INFO Obtain Device Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B42
IO/INFO Obtain PADmap Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B43
IO/INFO Obtain Async IO Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . B44
IO/MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B45
IO/MODE Enable Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B45
IO/MODE Disable Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B45
IO/MODE Modify Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B46
IO/MODE Modify Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B46
IO/MODE Reset Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B47
IO/MODE Add PADmap Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B48
IO/MODE Delete PADmap Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B49
IO/MODE Delete All PADmap Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B50
IO/MODE Enable/Disable Task Exception Processing . . . . . . . . . . . . . . . . . . B51
IO/MODE Modify Async IO Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . B52
IO/MOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B55
IO/OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B56
IO/READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B57
IO/RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B60
IO/WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B61
Return Values/Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B63
ASYNCXS
C320001300D0
vii
pktrvalus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B63
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B64
Glossary
Index
Figures
Figure 11. Product Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Figure 12. INF Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
viii
ASYNCXS
C320001300D0
1 Introduction
This manual describes the commands and parameters that configure and
control the Telematics ASYNCXS environment.
To use this manual effectively, you should be familiar with asynchronous
device operation, X.25 packet switching procedures, and the CCITT
standards for PAD implementation in an X.25 network (X.3, X.28, and
X.29). You should also be experienced with Telematics Interactive
Network Facilities (INF), NET25 software, and the Network
Configuration Model (NCM).
To use the IO interface effectively, you should be familiar with
programming in the Telematics TRAX operating system environment,
including building and submitting IO subservice packets.
This is a reference manual. For information about how commands are
used to configure and manage ASYNCXS, see the Release Notes, the
Configuration Model Manual, and the Configuration Model Operations
Guide.
Whats In This Manual?

The Introduction chapter, in addition to this section, describes the
ASYNCXS product. It also lists related manuals, standards compliance,
and conventions used in this manual.
The Operations chapter describes features of the ASYNCXS
environment and how to use them.
The X.3 Profiles and Parameters chapter describes the types of profiles
ASYNCXS uses and the effects of their parameter values.
The ASYNCXS PMM Commands and X.28 Commands chapters
describe their respective commands, and provide syntax and examples.
The PAD Service Signals chapter explains the events that can occur and
the type of information returned in the messages.
Other ASYNCXS events can generate different types of messages, which
are listed and described in the Alarms chapter.
The ASCII Character Set appendix lists the numeric equivalents for
defining special characters.
The IO Interface appendix describes the Assembly language
programmers interface to ASYNCXS, which includes IO subservices,
return values, and include files.
ASYNCXS
C320001300D0
11
INTRODUCTION
Product Description
Telematics ASYNCXS is a Packet Assembler and Disassembler (PAD)
that allows asynchronous devices to communicate with remote devices
and hosts through an X.25 packet switching network.
ASYNCXS comprises two components: the ASYNCXS Product
Management Module (PMM) and the ASYNCXS PAD. The
ASYNCXS PMM provides a manmachine interface that allows network
operations personnel to configure and monitor the ASYNCXS PAD
using Telematics Interactive Network Facilities (INF). The ASYNCXS
PAD provides X.3, X.28, and X.29 support.
X.3 support includes a set of parameters that specify the operating
characteristics of each asynchronous port. ASYNCXS also offers
extended Telematics parameters for added functionality. X.3 parameters
can be set dynamically on a percall basis. Reconfiguration can occur
during call acceptance.
X.28 support defines the dialogue between the device and the
ASYNCXS PAD. X.28 commands set up and clear virtual calls to a
remote computer through the packet switching network, and set/modify
X.3 parameters to accommodate the devices operating requirements.
ASYNCXS implements the 1984 CCITT Recommendation X.28
commands, plus Telematics extended commands. Optionally, a command
file containing X.28 commands can be executed at call accept time at the
local and/or remote ASYNCXS nodes.
X.29 support handles the exchange of control information across a
network between two PADs, or between a PAD and a packet mode DTE.
When a virtual circuit is established, it provides a way for a user at a
remote device to read or alter PAD parameters. The X.29 module
implements this functionality using data packets with the qualifier bit set
(i.e., Q=1).
You can manage ASYNCXS locally or remotely to modify a
configuration, monitor ASYNCXS activity, and display alarm/event
messages for remote PADs. You can downline load ASYNCXS software
to remote nodes from any NCC node and send configuration parameters to
remote nodes from any point in the network. You can configure host or
terminal devices manually or automatically using command files from the
local or NCC node. See the Configuration Model Manual and the
Configuration Model Operations Guide for details.
Relationships To Other Telematics Products
NET25 Like all Telematics access products, PAD support is
implemented jointly with the NET25 software, which processes call
packets, establishes virtual circuits, and manages data packet transfers. To
support the network connection, ASYNCXS:
Issues requests to NET25 to establish the virtual circuit or accept an

incoming call request
12
ASYNCXS
C320001300D0
INTRODUCTION
Collects characters from the device according to configuration

parameters and passes them to NET25 when a forwarding condition
occurs
Transmits characters received from NET25 to the device according to

configuration parameters
Processes X.29 commands from NET25 that the remote device has
sent, and responds accordingly
Issues requests to NET25 to clear the virtual circuit or respond to a

clear request from the remote device by clearing the virtual circuit
Information is exchanged between ASYNCXS and NET25 through the
Telematics Resident Applications Executive (TRAX) operating system.
System Libraries The Telematics asynchronous level 2 library provides
an interface between the level 1 asynchronous communications library and
the ASYNCXS PAD. The level 2 librarys routines help provide logical
read and write access to the asynchronous terminal devices, as well as
creating/managing communications channels and initiating data
transmissions. ASYNCXS also accesses the General Purpose Library
(GPLIB) for subroutine calls to TRAX.
Figure 11 shows the relationship between ASYNCXS, NET25, and the
system libraries.
NET25
GPLIB
C
TRAX IO
ASYNCXS PMM
TRAX IO
ASYNCXS
X.3
X.28
X.29
TRAX
IO
Application
Task
Subroutine Calls
Pascal
68000
Assembler
Async L2
Library
Async L1
Library
68000
Assembler
Asynchronous
Communications Lines
Figure 11. Product Relationships

INF INF is the network tool that manages the ASYNCXS environment
from a Telematics terminal. INF provides an interface between
ASYNCXS and NET25, and reports all ASYNCXS related status
messages and alarms. It also manages the interfaces to the various PMMs
(including the ASYNCXS PMM), which are product libraries loaded at
system startup. Figure 12 shows these software components.
ASYNCXS
C320001300D0
13
INTRODUCTION
ASYNCXS
PAD
HOST
ASYNCXS
PAD
Packet
Switching
Network
NET25
PMM
INF
Figure 12. INF Relationships
Related Manuals
The Configuration Model Manual (C320001700) and the Network
Configuration Model Operations Manual (C320003800)) explain how
to configure the ASYNCXS product on your Telematics system and
customize its operation to your networks needs.
The Release Notes that accompany the software indicate the required
library revisions.
The NET25 Manual (C320000800) and the Interactive Network
Facilities (INF) Manual (C320000900) describe the commands used to
configure and manage your Telematics network.
For users of the IO interface described in Appendix B, the Programmers
Guide (C310000100) and the TRAX Programmers Manual
(C315000100) describe how to build and submit TRAX operating
system IO service packets.
14
ASYNCXS
C320001300D0
INTRODUCTION
Standards Compliance
International Telecommunication Union. Recommendation V.24 List of
Definitions for Interchange Circuits Between Data Terminal Equipment
and Data CircuitTerminating Equipment. In Red Book Data
Communication Over the Telephone Network. vol. VIII fascicle VIII.1
Geneva: International Telecommunication Union, 1985.
______. AP IX48. Geneva: International Telecommunication Union,
1989.
______. AP IX49. Geneva: International Telecommunication Union,
1989.
______. Recommendation V.40 Error Indication with Electromechanical
Equipment. In Red Book Data Communication Over the Telephone
Network. vol. VIII fascicle VIII.1 Geneva: International
Telecommunication Union, 1985.
______. Recommendation V.54 Loop Test Devices for Modems. In Red
Book Data Communication Over the Telephone Network. vol. VIII
fascicle VIII.1 Geneva: International Telecommunication Union, 1985.
______. Recommendation X.3 Packet Assembly/Disassembly Facility
(PAD) in a Public Data Network. In Blue Book Data Communication
Networks Services and Facilities. vol VIII fascicle VIII.2. Melbourne:
International Telecommunication Union, 1988.
______. Recommendation X.15 Definition of Terms Concerning Public
Data Networks. In Red Book Data Communication Networks Services
and Facilities. vol. VIII fascicle VIII.2 Geneva: International
______. Recommendation X.20bis Use on Public Data Networks of Data
Terminal Equipment (DTE) which is Designed for Interfacing to
Asynchronous Duplex Vseries Modems. In Red Book Data
Communication Networks Interfaces. vol. VIII fascicle VIII.3 Geneva:
International Telecommunication Union, 1985.
_____. Recommendation X.25 Interface between Data Terminal
Equipment (DTE) and Data CircuitTerminating (DCE) for Terminals
Operating in the Packet Mode Connected to Public Data Networks by
Dedicated Circuit, In Blue Book Data Communication Networks
Interfaces. vol. VIII fascicle VIII.3 Melbourne: International
ASYNCXS
C320001300D0
15
INTRODUCTION
Syntax Conventions
Command syntax uses the following conventions:
<>
Angle brackets enclose values you must supply. Items within the
angle brackets are italicized.
[]
Square brackets enclose optional items.
...
An ellipsis indicates the preceding item can be repeated.
|
Vertical bars between items indicate you must select only one of
the items.
UPPERCASE
Uppercase indicates required characters; not the case (upper or

lower) in which they must be entered.
Null strings are noted by double quotes ().
Hexadecimal values are preceded with a dollar sign ($).
Pn refers to X.3 parameters, where P means parameter, and n is the
X.3 parameter number. For example, P13 indicates X.3 parameter
number 13.
Additional X.28 command conventions and syntax information is
provided on page 51.
The IO interface described in Appendix B uses the following conventions:
Field length specifications
B indicates a byte, W indicates a word, and L indicates a longword.
If no decimal precedes the letter, a single byte, word, or longword
is expected. A decimal preceding the letter indicates the number of
bytes, words, or longwords.
A hyphen () indicates the mnemonic in the Field column does not
represent a field offset. Such mnemonics represent the length of a
request packet or parameter buffer, and may be used when
reserving and initializing memory for them.
A V indicates the start of a variable length field. When a buffer has
a variable length field, the maximum buffer size includes the base,
plus the maximum variable length, plus 2.

The delta graphic indicates the device parameter can be modified
while the device is online.
16
ASYNCXS
C320001300D0
INTRODUCTION
*
A single asterisk indicates the preceding mnemonic is defined in
the asyxsuser.in include file (see next section, Include Files).
**
A double asterisk indicates the preceding mnemonic is defined in
the padiodefs.in include file (see next section, Include Files).
use and set
The word use preceding a mnemonic in the Contents column
indicates a MOVE instruction to copy a value into a field. The
word set indicates a BSET instruction to set the bit identified by
the mnemonic in that field.
ASYNCXS
C320001300D0
17
INTRODUCTION
18
ASYNCXS
C320001300D0
2 Operations
This chapter explains ASYNCXS PAD environment features, including:
Connection procedures
Signals
How data is accumulated and forwarded
Data editing
Special characters
Symbols
Device operational states
Modem processing
Incoming call routing
Connection Procedures
The first step in establishing a PAD connection is to physically and
logically connect the user terminal to the ASYNCXS PAD. The physical
connection is between the terminal and the Telematics system where
ASYNCXS resides. The logical connection, or signing on, ensures the
PAD is aware of the terminals characteristics and its readiness to begin.
Once the terminal is signed on, it is ready to make/receive calls from the
network and begin transferring data.
Terminals can be connected to the PAD in three ways: local connection,
leased line connection, and dialin line connection. The following
procedure is used for all types of terminal connections.
When modems are used, parameters configured for the terminal must be
compatible with those of the modems, and both the terminal and modem
parameters must be compatible with the PAD ports parameters. You
should check the compatibility of the terminal, modem, and operating
parameters for speed, parity, echo, bits per character, and flow control.
Also, check with your system administrator to determine whether the
autobaud option is enabled for your channel.
To establish a PAD connection:
For a local terminal or with a leased line and modem, connect the
terminal to a Telematics asynchronous channel that is configured for
ASYNCXS operation. Check with your system administrator for the
assigned channel.
ASYNCXS
C320001300D0
21
OPERATIONS
For a terminal connected via a dialin line and modem, make sure the
terminal is physically connected to the modem.
Turn the terminals power switch on.

For a dialin line, dial the number of the PAD. When the call is
accepted, switch the modem from voice to data mode.
If the autobaud option is enabled, enter several periods (.), at one to

two second intervals. When two periods echo on the screen, enter a
carriage return to automatically set the incoming baud rate and parity.
Signon Include Files
If the PAD already knows the terminals speed, and if the terminal is
configured so that no initial input is required before signing on, an
optional banner can be displayed from a local signon include file that
contains commands to set up the terminal for its session. For example, the
file can contain X.28 commands to display the current time, port
connection, or network availability information.
If both local signon and remote signon files are specified for a device, the
remote signon file functions as a nested include file to the local signon
file, i.e., the local signon files commands are executed, the remote signon
files commands are executed, then control returns to the local signon file
for completion.
After displaying the last output from the local signon include file, the PAD
service prompt (normally an asterisk) is displayed on a line by itself,
indicating that the terminal is in command mode and can accept
commands or incoming calls.
Printers and DisplayOnly Devices
If the terminal is a printer or other displayonly device, autobaud
detection cannot be used, and the device must be configured with the
exact transmission speed, and the banner (if configured) is displayed
immediately.
The devices configuration should not place it in a state where it must send
input. There are two ways to avoid this:
Include an X.28 command in the signon include file that automatically

makes a call at signon
Operate the device so that it receives an incoming call when it has

signed on, and is never required to make outgoing calls
In Case of A Problem
If you follow these procedures and nothing is displayed, turn the terminal
power switch off and on. If the problem persists, verify that ASYNCXS
is running on the Telematics system, and that the channel to which the
terminal is connected is enabled.
22
ASYNCXS
C320001300D0
OPERATIONS
Operation Modes
ASYNCXS devices have two operation modes: handler and PAD. The
handler mode uses TRAX IO services directly, and is described in
Appendix B. When a device is in PAD mode (the default), it can be in one
of two operational modes: command and data transfer.
Command Mode
After terminal setup and initialization procedures have completed
successfully, the terminal enters command mode. At this point, the
physical connection between the terminal and the PAD has been
established, and the user can enter X.28 commands. The terminal remains
in command mode until the PAD receives an X.28 command to make a
call to another device on the X.25 network, or until the PAD receives a
call from another device on the network.
If a nonzero command mode timeout value has been specified for the
terminal (CMDTImeout device parameter), the PAD waits for a specific
time interval for a command from the terminal after issuing the PAD
prompt signal (i.e., a command prompt) to the terminal. If the time
interval passes and no command is entered, the terminal is disconnected
from the PAD if there is no call active. If a call is active, the terminal
switches to data transfer mode. This timeout differs from the data transfer
mode timeout, which is described in the next section.
Data Transfer Mode
The terminal is placed in data transfer mode when an X.25 call is
successfully established. In data transfer mode, data can be transferred
between the terminal and the remote device. Depending on the X.3
parameters defined, the terminal remains in data transfer mode until one of
the following events occurs:
The terminal user enters the PAD recall character (depending on the
P1 value)
The terminal user enters a break signal with the break key or an
alternate break key (depending on the P7 value)
The PAD receives a call clear request from the network

While the terminal is in data transfer mode, the PAD does not try to
interpret user data. Most characters are transmitted to the remote device,
except:
Editing characters (depending on the P15, P16, P17, and P18 values)
PAD recall character (depending on the P1 value)
Flow control characters defined in P30 and P31 (depending on the
P12, P30, and P31 values)
Characters received with invalid parity (depending on the P21 value)

ASYNCXS
C320001300D0
23
OPERATIONS
When an X.25 call is active, the terminal user can temporarily leave data
transfer mode and return to command mode by entering the PAD recall
character (controlled by P1). The terminal remains in command mode, and
X.28 commands can be entered, until the terminal user enters the X.28
Continue command, a carriage return, or a plus sign (+), any of which
returns the terminal to data transfer mode. If P1=0, the user cannot leave
data transfer mode while a call is active unless a break or alternate break is
used, depending on the value of P7.
If a nonzero data transfer mode timeout value has been configured for the
terminal (X25IDLETimer device parameter), the PAD waits the specified
time interval for data to be entered from the terminal after forwarding the
previous data. If the time interval elapses and no data has been entered,
the active call is cleared and the terminal is disconnected from the PAD.
This timeout differs from the command mode timeout, which was
described in the previous section.
24
ASYNCXS
C320001300D0
OPERATIONS
Signals
This section covers two signal types: PAD service signals that are returned
from certain events, and the break signal used at the terminal.
PAD Service Signals
Data sent from the PAD to the device falls into two categories: data
received from the remote device, and PAD service signals. A PAD service
signal is either a response to an X.28 command or an indication of PAD or
network status. The value of X.3 P6 determines whether PAD service
signals are sent to the device; it also controls the format of those signals.
Several PAD service signals are described below. Chapter 6 lists the
defined PAD service signals and their meanings.
Prompt service signal This is the character or character string that
indicates the PAD is waiting for the terminal to send it an X.28 command.
The standard prompt service signal is an asterisk (*); the default extended
prompt service signal is Service:. The extended prompt service signal is
established when the device is configured.
Acknowledge service signal This is the indication from the PAD that it
has accepted an X.28 command. It consists of the <CR> and <LF>
characters.
Break service signal This is the notification from the PAD that an
indication of break has been received from the network.
Break Signal
The break feature allows the terminal to signal the PAD without loss of
character transparency, i.e., without reserving a special character that
cannot be sent as data. A break signal also acts as a command abort key
for X.28 Aread, Read, Tact, and Tactt commands. The break signal is
meaningful only when entered while a call is active; otherwise, it is
ignored.
If the terminal supports the break signal with the break key or another
defined break key, the PAD responds to the break signal according to the
setting of X.3 P7.
If the PAD receives an indication of break message from the network and
a call is active, the PAD sends a break service signal to the terminal. This
can take one of several forms, depending on the terminals configuration:
An actual break, generated by transmitting binary 0 for a specified

time interval (BREAKTime device parameter)
A string of characters (BREAKString device parameter)

No action; the indication of break message is ignored (NOBREAK
device parameter)
ASYNCXS
C320001300D0
25
OPERATIONS
Data Accumulation and Forwarding

This section explains how data entered at the terminal is accumulated and
eventually forwarded.
Typeahead Buffer
In data transfer or command mode, the PAD alternates between reading a
string of characters from the device and acting upon the characters read. A
string is terminated by a carriage return or a plus sign in command mode,
by a data forwarding character in data transfer mode, and in either mode
by exceeding the line folding margin (P10).
While an input string is being processed, the PAD is not actively reading
from the device; characters entered from the device during this time are
stored in a typeahead buffer. When the previous input has been processed
and the PAD is ready to begin reading data from the device again, it first
transfers all characters from the typeahead buffer into its internal read
buffer. This ensures that no data is lost during the processing of the
previous input.
If the PAD is not able to begin reading data quickly enough, input
characters fill the typeahead buffer, after which all subsequent input
characters are lost until the PAD begins reading again. There are two ways
to avoid this: configure a larger typeahead buffer (TYPeahead device
parameter) or enable input (terminal user) flow control with X.3 P5.
The following events cause the typeahead buffer to be purged, discarding
any characters that were typed:
Acceptance of an incoming call for the terminal

Expiration of the command mode timeout timer while a call is active,
switching the terminal into data transfer mode
Receipt of a break signal, if the value of P7 causes return to command

mode or data to be discarded when a break is entered
Receipt of an indication of reset message from the network

Clearing of an active call
Receipt of an X.28 Reset Circuit command from the terminal
Disabling the terminal
Data Forwarding
As characters are entered from the device in data transfer mode, they
accumulate in a PAD buffer until a data forwarding condition occurs. The
buffer size is determined by various factors in the network configuration,
e.g., maximum packet size. When a forwarding condition occurs, the
accumulated data is transmitted as a packet to the remote device, and the
buffer is cleared. The data forwarding conditions are:
26
ASYNCXS
C320001300D0
OPERATIONS
Buffer full If no other forwarding condition applies, data will be

forwarded upon reaching the larger of two values: the X25IOWrite device
parameter value or the X.25 links configured maximum packet size value.
For example, if the configured X25IOWrite value is 1000 bytes and the
links maximum packet size is 512 bytes, and if no other forwarding
condition occurs, the data will be forwarded when 1000 bytes accumulate
in the buffer. Similarly, if the X25IOWrite value is 256 bytes and the
links maximum packet size is 512, the data will be forwarded when 512
bytes accumulate (if no other forwarding condition occurs).
Idle timer X.3 P4 specifies an idle timer for data forwarding. The timer
is reset and started each time a character is entered from the device. If the
interval specified in P4 expires before the next character is entered, the
accumulated data is forwarded. Forwarding on the idle timer is disabled if
P15=1,which permits editing in data transfer mode.
Interval timer X.3 P26 specifies an interval timer for data forwarding.
When the time interval specified in P26 expires, the accumulated data is
forwarded and the timer is reinitialized. Forwarding on the interval timer
is disabled if the idle timer is enabled.
Data forwarding count X.3 P83 indicates that data will be forwarded
after the specified number of characters have been entered.
Break character When a break character (or an alternate break character
specified in X.3 P82) is entered from the terminal, and if P7 is nonzero,
any accumulated data is forwarded.
PAD recall When the PAD recall character specified in X.3 P1 is entered
from the terminal, any accumulated data is forwarded.
Data forwarding character When one of the characters specified in X.3
P3, P23, or P24 is entered, the accumulated data and the forwarding
character are sent to the remote device. Data forwarding can be suspended
by flow control, i.e., if the network cannot accept any more data from the
PAD. If a forwarding condition occurs and no data has accumulated from
the device, an empty packet is not forwarded.
ASYNCXS
C320001300D0
27
OPERATIONS
Editing Data
Before accumulated data is forwarded, it is held in a PAD buffer, and can
be edited. Editing can be done in both command and data transfer modes.
In command mode, editing is always enabled. In data transfer mode,
editing is enabled and disabled with X.3 parameter P15. When editing is
enabled in data transfer mode (i.e., P15=1), the idle timer controlled by P4
is ignored. You can only edit the current line.
Editing Characters
Editing uses three special characters: character delete, line delete, and line
display. These characters are not added to the buffer as data, but cause
specific actions to be performed to the accumulated data. X.3 P16, P17,
and P18 specify the three characters values. X.3 P19 controls the PADs
response when these characters are entered.
Character delete The default character delete character is <DEL>. X.3
P16 can be set to a nonzero value to designate an alternate character delete
character. When the PAD receives the character delete character from the
device, it deletes from its buffer the last character entered. If there are no
characters in the buffer, this editing function has no effect.
Line delete The default line delete character is <CAN>. X.3 P17 can be
set to a nonzero value to designate an alternate line delete character. When
the PAD receives this character from the device, it deletes all of the
characters in its buffer. The PAD responds to the device by sending an
editing service signal, which consists of the characters ^U followed by the
format effector (<CR><LF>). If there are no characters in the buffer, this
editing function has no effect.
Line display The default line display character is <DC2>. When the
PAD receives this character from the device, it sends a format effector
(<CR><LF>) to the device, followed by all the accumulated characters in
the buffer. X.3 P18 can be set to a nonzero value to designate an alternate
line display character.
28
ASYNCXS
C320001300D0
OPERATIONS
Special Characters
You can use X.3 parameters to identify certain control characters for
special action when they are entered from the terminal. These special
actions are:
Flow control
Display line
Line delete
Character delete
PAD recall (switch to command mode)

Packet forwarding
Break
Hot key string (if enabled; IO interface
users only; see Appendix B)
Control characters should be assigned unique values; do not define the

same character for more than one function. If a character is assigned two
or more functions, only one function will be performed, according to the
highest priority:
Hot key
Filter or terminate on escape (P84)
Local discard (P85)
Alternate break character (P82)
PAD recall (P1)
XOFF (P31, P12)
XON (P30, P12)
Character delete (P16, P15)
Line display (P18, P15)
Line delete (P17, P15)
PAD command signal delimiter (P81)
Additional data forwarding (P24)
Additional data forwarding (P23)
Data forwarding character (P3)
ASYNCXS
C320001300D0
highest
lowest
29
OPERATIONS
Symbols
This section explains how to create and display symbols.
Creating Symbols
Symbols are useful for creating commands with names that are familiar to
the terminal user. ASYNCXS predefines a number of symbols for
devices; some are defined when the device is enabled, and others are
defined/modified during the terminal session. The predefined symbols are:
PORT Devices port number.
PORTNUA Devices network address, e.g., 9999103105.
USERDATA Call user data from the most recent incoming call. Prior
to the first incoming call, the symbol is defined as empty, i.e., .
SYSDATE Current date, in the form ddmmmyy, e.g., 11FEB92.
SYSTIME Current time, in the form hh:mm:ss in 24 hour format,
e.g., 16:54:17.
SWREV Software revision identification.
Symbol Replacement
X.3 P81 controls symbolic replacement; replacement occurs only if P81
has the symbolic replacement option enabled. Symbolic replacement can
be temporarily disabled for part of a command line by using the toggle
function character, the backslash ( \ ).
Symbols are indicated by open apostrophes (). The symbol name can be
enclosed in a pair of open apostrophes, or preceded by a single open
apostrophe.
The first element in a command line is always replaced if it matches a
symbol name (it can be enclosed in a pair of open apostrophes, but this is
not required). All subsequent symbol names must be enclosed in a pair of
open apostrophes (or preceded by a single open apostrophe) in order to be
replaced in the command line.
Symbols can be defined with required and optional characters. When a
symbol is defined in both uppercase and lowercase, uppercase indicates
the required characters and lowercase indicates optional characters. A
symbol defined in all uppercase or lowercase must be typed completely.
Do not define a symbol with a character string that matches the case
significant characters of X.28 commands or parameter keywords. For
example, to define a symbol for remote profiles, do not use the string
RPROF or RPROFile in the definition. Examples of valid symbols are
RPRO1 and RPRtokyo.
Do not define a symbol beginning with the character C; this is the
significant character for the X.28 Call command.
210
ASYNCXS
C320001300D0
OPERATIONS
Do not define a symbol with the same format as a call facility parameter
value; symbol names that contain a single alphabetic character followed
by a number must not begin with the characters B, D, G, N, O, P, or W.
There are two symbol commands: symbolic assignment and symbolic
inquiry.
Symbolic Assignment Command
The Symbolic Assignment command defines a symbol name and assigns a
character string to it. The command line is limited to 128 characters; the
symbol assignment operator (:=) and quotation marks that enclose the
symbol value are included in the character count.
Syntax
<symbol>:=[<value>]
Parameters
<symbol>
Symbol name, containing up to 16 alphanumeric characters, the
first of which must be alphabetic. Uppercase indicates the
minimum number of significant characters.
[<value>]
Character string enclosed in quotation marks. The maximum
length is determined by the maximum line length (128 characters)
and the length of the symbol name. An empty string () deletes
the symbol definition.
Example
The following command assigns the string c 99990001234567 to the
symbol host. Once defined, the symbol (i.e., host) can be used in
response to a PAD service prompt to initiate an X.25 call request.
host:=c 99990001234567
A control character can be included in a string. The decimal value of

the control character must be enclosed in parentheses, i.e.,
<symbol>:=CHR(<value>). For example,
ABC:=Chr(7)
The following information can be returned in response to a Symbolic

Assignment command:
Acknowledge signal This is the normal command response. See Chapter
6 for the signal display format.
Symbol limit exceeded The symbol cannot be defined because the
number of symbols already defined for the device matches the
maximum symbol limit (MAxsymbol device parameter).
ASYNCXS
C320001300D0
211
OPERATIONS
Error, symbol not defined The symbol cannot be defined because the
memory space reserved for symbol definition at task startup is full.
Symbol Inquiry Command
The Symbol Inquiry command displays the value of an existing symbol.
To produce a display of all defined symbols and their values, use the X.28
Help Mnemonics command.
Syntax
<symbol>?
Parameters
<symbol>
Symbol name. Wildcard characters can be used, but not as the first
character.
?
Required command character.
The following information can be returned in response to a Symbol
Inquiry command:
<symbol value> This is the normal response to the command. The PAD
issues an Acknowledge PAD service signal (see Chapter 6 for format)
followed by the <symbol>=<symbol value>.
No match found The symbol has not been defined or the name has not
been specified correctly.
Symbol Replacement Example
The following symbols have been defined:
LOgon:=c 99990001234567
atlanta:=99990007654321
data:=this is a test
PRint:=type
hello:=type hi there (quotes enclose the command parameter)
212
command:
action:
LOGON
c 99990001234567
command:
action:
c atlanta
c 99990007654321
command:
action:
response:
print data (quotation marks enclose command parameter)

type data
data
command:
action:
response:
prin data
type this is a test
this is a test
ASYNCXS
C320001300D0
OPERATIONS
command:
action:
response:
pri status
type status (no symbol status defined)
status
command:
action:
response:
pr \data\
type data (temporarily disabled by backslash)
data
command:
action:
response:
pr PRint = <print>
type PRint = <type>
PRint = <type>
command:
action:
response:
hello
type hi there
hi there
command:
action:
response:
pr hello = <hello>
type hello = <type hi there>
hello = <type hi there>
Device Operational States

An ASYNCXS device can be in one of several operational states: offline,
enabled, signon, connect, disabled, or online. A devices initial state is
specified in its configuration (e.g., Create Device command) with the
INState parameter. During operations, the state can change; the Show
Device command (described in Chapter 4) can be used to display a
devices current state.
Offline The device is logically disconnected from the PAD.
Enabled A device is placed in this state when an Enable Device
command is entered or when the INState device parameter has a value
other than OFFline or DISabled. If the device uses a modem, the device
stays in this state until the modem connects. When the device enters the
enable state, ASYNCXS configures the asynchronous channel associated
with the device. If P81=8, the device automatically enters this state after
an internal disable occurs.
Signon When a device enters this state, the PAD initiates communication
with it and performs the defined signon procedures with the specified X.3
parameter values and device configuration options. The actions are
initiated in the following order:
Performs autobaud detection, if selected (P11)

Enables the asynchronous channel for read operations
Waits for <CR> input from the device (P80)
Processes the signon file, if enabled (P80). The signon file is identified
with the LSignon device parameter.
ASYNCXS
C320001300D0
213
OPERATIONS
Starts autocall procedures, if enabled (P81)

Connect When a device has signed on to the PAD and autocall is not
enabled for the device, the device enters the connect state. This is the
device state when it is in command mode. After a call is established, the
device is placed in the connect state when it changes from data transfer to
command mode.
Online When a call is established, the device is in the online state. At
this point, the device is in data transfer mode and can communicate with a
remote device across the network.
Modem Processing
The modem device parameter specifies whether the device is configured
for modem support. If modem support is configured, there are several
subparameters available; the combination that is specified can affect the
state of the signals and the port when other signals are asserted or
removed. This section first describes the subparameters in general, then
lists and describes the changes that can occur for each of the eight (8)
possible subparameter combinations.
Note that if the device is configured with the DTRCall parameter, it
overrides all the modem subparameters. Also, you should not modify
modem subparameters separately with a Modify Device command.
The modem device parameter has the following syntax:
MOdem=([NO]MODem,[NO]DTR,[NO]HANgup,[NO]AUToanswer)
Modem Subparameters
The [NO]DTR subparameters indicate the idle state of DTR. These
subparameters are valid regardless of whether MODem is enabled or not.
DTR indicates that DTR will be raised when the device is created;
NODTR indicates that DTR is low.
HANgup indicates the PAD should hang up the modem when the device is
disabled. NOHANgup indicates the PAD will not modify the state of the
modem signals when the device is disabled. The [NO]HANgup
subparameters are valid only if MODem is specified.
AUToanswer indicates the device is placed in the connect state when DSR
and DCD signals are both present. ASYNCXS follows the modem
control signals in autoanswer mode, based on the Industrial Electronics
Bulletin No. 9, Application Nodes for EIA Standard RS232C. When the
device is configured for NOAUToanswer, it remains in the enabled state.
A transition from this state requires that the modem report the RING
signal. When RING is detected, ASYNCXS forces DTR and RTS high
and starts a 30 second timer to wait for DSR and DCD to go high. If the
timer expires, the modem is disconnected and the device is disabled. If
DSR and DCD are present within 30 seconds, ASYNCXS places the
device in the signon state and cancels the timer. (Subsequent completion
of the signon include file, if configured, places the device in the connect
state.)
214
ASYNCXS
C320001300D0
OPERATIONS
When the device is in the connect state, loss of DCD for more than 2
seconds, or loss of DSR causes ASYNCXS to disable the device.
When the device is disabled, and if the modem option HANgup is
enabled, ASYNCXS lowers DTR and RTS for 2 seconds. After 2
seconds, modem control returns to the idle state.
Subparameter Combinations
When modem support is enabled, there are eight (8) possible
combinations of the [no]dtr, [no]hangup, and [no]autoanswer
subparameters. This section lists these combinations (with relevant X.3
parameter settings; see Chapter 3 for full X.3 parameter descriptions) and
describes the DTR and RTS signal and port state changes (if any) when
other signals are asserted or removed.
modem=(modem,nodtr,nohangup,noautoanswer) and par=(80:0 81:92)
When the port is first created, and DSR and CD are not applied: DTR
and RTS stay low; the state is enabled
When the port is first created, and DSR and CD are applied: DTR and
RTS stay low; the state is enabled
When DSR and CD are not applied and RI is applied: DTR and RTS
go high for 30 seconds; the state is enabled
When DSR and CD are individually applied and RI is then applied:

DTR and RTS go high for 30 seconds; the state is enabled
When DSR and CD are applied during the 30 seconds after RI is

applied: DTR and RTS stay high; the state changes to connect
When DSR and CD are applied and RI is applied: DTR and RTS go
high; the state changes to connect
When DSR and CD are applied, and CD is removed: DTR and RTS go
low after 2 seconds; the states changes from connect to enabled
When DSR and CD are applied, and CD is removed for less than 2
seconds: DTR and RTS stay high; the state remains connect; the port
will not accept or send data (if CD is restored during the initial 2
seconds, the port continues sending and receiving data)
When DSR and CD are applied, and DSR is removed: DTR and RTS
go low immediately; the state changes from connect to enabled
When DSR and CD are applied, and an X.28 call is placed, completed,
and cleared from both sides: DTR and RTS go low immediately; the
state changes from online to enabled (if par=(81:88), DTR and RTS
stay high, and the state stays in connect)
ASYNCXS
C320001300D0
215
OPERATIONS
modem=(modem,nodtr,nohangup,autoanswer) and par=(80:0 81:92)
RI has no effect with this configuration.

RTS stay high; the state is connect
seconds, the port continues sending and receiving data; if CD is not
restored, the state changes to enabled)
When DSR and CD are applied, and an X.28 call is placed, completed,
and cleared from both sides: DTR and RTS go low immediately, then
go high; the state changes from online to connect (if par=(81:88), DTR
and RTS stay high, and the state changes from online to connect)
modem=(modem,nodtr,hangup,noautoanswer) and par=(80:0 81:88)
RTS stay low; the state is enabled
go high for 30 seconds; the state is enabled
When DSR and CD are individually applied and RI is then applied:

DTR and RTS go high for 30 seconds; the state is enabled

applied: DTR and RTS stay high; the state is connect
When DSR and CD are applied and RI is applied: DTR and RTS go
216
ASYNCXS
C320001300D0
OPERATIONS
When DSR and CD are applied, par=(80:0 81:92), and an X.28 call is
placed, completed, and cleared from both sides: DTR and RTS go low
immediately; the state changes from online to enabled (if par=(81:88),
DTR and RTS stay high, and the state changes from online to connect)
modem=(modem,nodtr,hangup,autoanswer) and par=(80:0 81:88)

placed, completed, and cleared from both sides: DTR and RTS go low
immediately; the state changes from online to connect (if par=(81:88),
DTR and RTS stay high, and the state changes from online to connect)
modem=(modem,dtr,nohangup,noautoanswer) and par=(80:0 81:92)
and RTS stay high; the state is enabled
RTS stay high; the state is enabled
stay high; the state is enabled
When DSR and CD are individually applied: no effect

When DSR and CD are applied and RI is applied: DTR and RTS stay
When DSR and CD are applied, and CD is removed: DTR and RTS
stay high for 2 seconds, then go low for 2 seconds, then go high; the
state changes from connect to enabled
ASYNCXS
C320001300D0
217
OPERATIONS
go low immediately; after 2 seconds, DTR and RTS go high; the state
changes from connect to enabled immediately
When DSR and CD are applied,and an X.28 call is placed, completed,

and cleared from both sides: DTR and RTS stay high; after 2 seconds,
the state changes from online to enabled (if par=(81:88), DTR and
RTS remain high; after 2 seconds, the state changes from online to
connect)
modem=(modem,dtr,nohangup,autoanswer) and par=(80:0 81:92)

When DSR and CD are applied,and an X.28 call is placed, completed,

and cleared from both sides: DTR and RTS stay high; after 2 seconds,
the state changes from online to connect (if par=(81:88), DTR and
RTS remain high; after 2 seconds, the state changes from online to
connect)
modem=(modem,dtr,hangup,noautoanswer) and par=(80:0 81:88)
RTS stay high; the state is enabled
Disabling the device causes DTR and RTS to stay low.

218
ASYNCXS
C320001300D0
OPERATIONS
stay high; the state is enabled
When DSR and CD are individually applied: no effect

When DSR and CD are applied and RI is applied: the state changes to
connect
When DSR and CD are applied, and DSR is removed, or device is

disabled: DTR and RTS go low immediately; after 2 seconds, DTR
and RTS go high; the state changes from connect to enabled
immediately
placed, completed, and cleared from both sides: DTR and RTS go low;
the state changes immediately from online to enabled; after 2 seconds,
DTR goes high (RTS is irrelevant); (if par=(81:88), DTR and RTS
remain high; the state changes to connect)
modem=(modem,dtr,hangup,autoanswer) and par=(80:0 81:88)

ASYNCXS
C320001300D0
219
OPERATIONS
placed, completed, and cleared from both sides: DTR and RTS go low;
the state changes immediately from online to connect; after 2 seconds,
DTR and RTS go high; (if par=(81:88), DTR and RTS remain high;
the state changes to connect)
modem=(nomodem,dtr) and par=(80:0 81:92)
RTS is irrelevant; DTR stays high for all transitions of DSR, CD, and
RI; the state is always connect
modem=(nomodem,nodtr) and par=(80:0 81:92)
RTS is irrelevant; DTR stays low for all transitions of DSR, CD, and
RI; the state is always connect
220
ASYNCXS
C320001300D0
OPERATIONS
Incoming Call Routing

When creating an asynchronous device, you can assign a Network User
Address (NUA), which contains network access information and call
facilities that provide the device with network access.
When an asynchronous PAD device is created, ASYNCXS notifies
NET25s Call Processor Task (CPT) that the calling NUA associated with
the device is ready to accept incoming X.25 calls. This is known as
registering for incoming calls. Once a device is registered, ASYNCXS is
notified when an X.25 call request arrives that is destined for the NUA.
When an X.25 call request arrives, ASYNCXS determines which, if any,
of the available devices should accept the call. The selected device is not
necessarily the same as the device whose calling NUA was registered for
incoming calls. The assignment of incoming calls to available terminals is
accomplished using an internal ASYNCXS structure called the PADmap
table. Each PADmap entry has three fields: NUA, call user data, and port.
When an incoming call arrives, ASYNCXS examines the NUA and call
user data (CUD) fields of each PADmap entry against the corresponding
fields of the incoming call. If the PADmap NUA field matches the called
NUA field of the incoming call, and if the PADmap CUD field matches
the CUD field of the incoming call, the PADmap port field specifies which
device will be assigned to the call.
If either the NUA or CUD field does not match, or if no available device
can be assigned by a matching entry, ASYNCXS tries to find a match in
the next PADmap entry. The entire table is processed in sequence until
either a match results in the call being assigned, or the end of the PADmap
is reached and the call is rejected.
In summary, in order for PAD terminals to accept incoming calls, each
port must be configured with a calling NUA for which the ASYNCXS
task will register for incoming calls. In addition, a PADmap table must be
created to direct the routing of incoming calls to available devices. The
NUA specified for a PADmap table entry corresponds to a local (or
calling) network address; this value is compared to the called address field
of an incoming call request to determine which device is assigned the call.
Port Assignment
When an incoming call arrives at the PAD, ASYNCXS examines the
called address and CUD fields to see if they match the corresponding
fields of the PADmap entry. If they do, the value assigned to the port field
in a PADmap entry is used to locate the port for the incoming call. A
range of values as a port assignment creates a rotary; that is, an incoming
call for a specific NUA is routed to the first available port within the
range. This string can take one of the forms listed below; no enclosing
quotation marks are required when specifying these strings as input
values.
ASYNCXS
C320001300D0
221
OPERATIONS
Port String Definition

* . . . . . . . . . Directs the call to the first available device whose calling
NUA exactly matches the called NUA field of the
incoming call.
# . . . . . . . . . Directs the call to the device whose port number is
specified in the CUD field of the incoming call. The CUD
field of this PADmap entry must consist of the string P%,
P%%, P%%%, or P%%%% to indicate the number of
digits in the call user data to extract for the port number.
#n . . . . . . . . Directs the call to the device whose port number is given
by the low order n digits of the called NUA field of the
incoming call. Legal values for n are 13.
mmmnnn . . Directs the call to the first available device with a port
number in the range mmmnnn inclusive. Legal values are
0479.
PADmap
The PADmap table contains entries that define a routing scheme for
incoming calls. The ASYNCXS PMM has several commands that
manage the PADmap: the Add Map command adds an entry, the Delete
Map command removes an entry, the Erase Map command removes all
entries, and the Show Map command displays PADmap table entries.
PADmap Routing Examples
The following examples illustrate how a PADmap table is used to route
incoming calls.
PADmap Table
NUA
CUD
PORT
99991032000601
999910320006%%
9999103200*
*
P%%%
*
116
#
#2
Example 1
ASYNCXS routes a call with a called NUA of 99991032000622 and call
user data abc as follows:
The called address (99991032000622) is compared to the NUA field of
the first PADmap entry (99991032000601); the comparison fails, so
ASYNCXS moves on to the second entry.
the second PADmap entry (999910320006%%); the comparison results in
a match.
The call user data (abc) is compared to the CUD field of the second
PADmap entry (P%%%); the comparison fails, so ASYNCXS moves on
to the third PADmap entry.
222
ASYNCXS
C320001300D0
OPERATIONS

the third PADmap entry (9999103200*); the comparison results in a
match.
The call user data (abc) is compared to the CUD field of the third
PADmap entry (*); the comparison results in a match.
Both the called address and call user data of the third PADmap entry
match the corresponding fields of the incoming call, so the port field (#2)
is examined to determine which device should be assigned to the call. This
field instructs ASYNCXS to select the device whose port number is
given by the lower 2 digits of the incoming calls called address (22).
Thus, if the device whose port number is 22 is enabled and not busy on
another call, the call is routed to it. If the device is not enabled, the call is
rejected with a status code indicating that the destination is not obtainable,
since there are no more PADmap entries in the table to examine. If the
device is busy on another call, the call is rejected with a busy status code.
Example 2
Given the same PADmap table, ASYNCXS routes a call with a called
NUA of 99991032000600 and call user data P105 as follows:
the first PADmap entry (99991032000601); the comparison fails, so
ASYNCXS moves on to the second entry.
the second PADmap entry (999910320006%%); the comparison results in
a match.
The call user data (P105) is compared to the CUD field of the second
PADmap entry (P%%%); the comparison results in a match.
Both called address and call user data of the second PADmap entry match
the corresponding fields of the incoming call, so the port field (#) is
examined to determine which device should be assigned to the call. This
given by the lower 3 digits of the incoming calls call user data (P105).
another call, the call is routed to it. If the device is not enabled or is busy,
ASYNCXS proceeds to the next step.
the third PADmap entry (9999103200*); the comparison results in a
match.
The call user data (P105) is compared to the CUD field of the third
PADmap entry (*); the comparison results in a match.
ASYNCXS
C320001300D0
223
OPERATIONS
Both called address and call user data of the third PADmap entry match
the corresponding fields of the incoming call, so the port field (#2) is
examined to determine which device should be assigned to the call. This
given by the lower 2 digits of the incoming calls called address (00).
another call, the call is routed to it. If the device is not enabled, the call is
rejected with a status code indicating that the destination is not obtainable,
since there are no more PADmap entries in the table to examine. If the
device is busy on another call, or if the device selected by entry 2 is busy,
the call is rejected with a busy status code.
The order of entries in the PADmap table affects the manner in which call
assignments are made. In this example, the incoming call is eventually
assigned to a port number different from that originally specified in the
CUD field of the call request packet. If the second and third entries were
reversed in the PADmap table, the port number in the CUD field (new
entry 3) would only be used if the port identified by the loworder digits
of the NUA field (new entry 2) was unavailable.
224
ASYNCXS
C320001300D0
3 X.3 Profiles and Parameters

This chapter describes X.3 profiles and parameters, which control
terminals connected to ASYNCXS. The CCITT X.3 recommendation
defines 22 parameters; Telematics offers 16 extended parameters, as well
as extended values for several of the CCITTdefined parameters.
A profile is one complete set of X.3 parameters. Before creating an X.3
profile, you must first define a directory for it with the Create Directory
command.
X.3 Profiles Types and Uses

ASYNCXS has two types of profiles: initial and named.
Every device has an individual profile named initial. This profile contains
all the X.3 parameters to be used when the device is enabled. The initial
profile is created when the device is created (Create Device command).
The initial profile can be modified (Modify Device command). The initial
profile is destroyed when the device is destroyed (Destroy Device
command).
The system administrator can also create, modify, and destroy named
profiles with the Create Profile, Modify Profile, and Destroy Profile
commands.
There are two other sets of X.3 parameters that resemble profiles. They
are not profiles, but templates that are used to specify the initial profile
and a named profile. These X.3 parameters are changed with the Set
Defaults Profiles command.
Specifying the initial profile is straightforward but not obvious. When a
device is created without a default profile name (which is one of the
Create Device parameters), the initial profile uses the values specified on
the Create Device command line. Any parameters not specified on the
command line take default values.
When a device is created with a default profile name, the initial profile
uses the values specified in the Create Device command. Any parameters
not specified in the command use values from the named profile.
When the PMM creates a device or profile for ASYNCXS, the PMM
sends values for every parameter to ASYNCXS. The PMM makes
configuration easier by not requiring the network administrator to enter
values for every parameter; it keeps a template of parameters and refers to
them as defaults. Therefore, when the PMM processes a Create command,
any parameters not entered on the command line are taken from the
defaults. The PMM also allows a network administrator to change the
default values.
ASYNCXS
C320001300D0
31
X.3 PROFILES AND PARAMETERS
When the PMM modifies a device or profile, the PMM only sends the
values entered on the Modify command line. ASYNCXS then updates
only the values that were sent.
X.3 Parameter Conventions

Pn is a convention used throughout this manual to refer to X.3 parameters,
where P means parameter, and n is the X.3 parameter number. For
example, P13 indicates X.3 parameter number 13.
The format for specifying an X.3 parameter and its value is:
PARameter=(<number>:<value>,...). For example, PAR=(7:0,8:0).
Value Combinations
Some X.3 parameters support value combinations; that is, you can choose
more than one value and use their sum to indicate a combination of unique
actions. For example, parameter 13 can be given a value of 3 (1 + 2). This
represents a combination of the value 1 (insert a line feed character after
each carriage return sent to the device) and the value 2 (insert a line feed
character after each carriage return sent to the remote device). Legal value
combinations are not necessarily logical combinations for the environment
you are working in.
32
ASYNCXS
C320001300D0
X.3 Parameter Summary

This section lists the default X.3 parameter values assigned at task startup
and the optional values. Parameter numbers followed by an asterisk (*) are
Telematics extended parameters; individual parameter values followed by
an asterisk are Telematics extended values. Values noted with a plus sign
(+) are part of a value combination that matches the default value.
___________________________________________________________
Parameter:Default Name
Value(s) = Description(s)
___________________________________________________________
0:0 National Marker
0 = default value
___________________________________________________________
1:1 PAD Recall
0 = none
1 = CtrlP
2255 = ASCII character
___________________________________________________________
2:1 Echo
0 = disabled
1 = enabled
___________________________________________________________
3:2 Data Forwarding Character (value combinations allowed)
0 = none
1 = alpha/numeric
2 = <CR>
4 = <ESC>, <BEL>, <ENQ>, <ACK>
8 = <CAN>, <DEL>, <DC2>
16 = <EXT>, <EOT>
32 = <HT>, <LF>, <VT>, <FF>
64 = other ASCII control characters not listed above
___________________________________________________________
4:0 Idle Timer (Data Forwarding Timeout)
0 = none
1255 = time (1/20 seconds)
___________________________________________________________
5:0 Device Flow Control
0 = none
1 = data mode
2 = data/command mode
___________________________________________________________
6:5 PAD Service Signals
0 = none
1 = standard/no prompt
4 = standard/prompt only
5 = standard/all
8 = extended
9 = extended/no prompt
12 = extended/prompt only
13 = extended/all
16 = extended/English language signals
32 = extended/French language signals
48 = extended/Spanish language signals
___________________________________________________________
ASYNCXS
C320001300D0
33
___________________________________________________________
7:2 Break Action (Send Reset Message on Break)
0 = none
1 = interrupt
2 = reset
4 = break indication
5 = interrupt and break indication
8 = command mode escape
16 = discard data destined for device
21 = discard output, send interrupt and break indication
___________________________________________________________
8:0 Discard Output (Read Only)
0 = normal data delivery
1 = discard output
___________________________________________________________
9:0 Padding After Carriage Return
0 = none
1255 = number of characters
___________________________________________________________
10:0 Line Folding
0 = none
___________________________________________________________
11:22 Device Speed (Baud Rate)
0 = 110
1 = 134.5
2 = 300
3 = 1200
4 = 600
5 = 75
6 = 150
7 = 1800
10 = 50
11 = 75/1200
12 = 2400
13 = 4800
14 = 9600
15 = 19200
19* = 2000
20* = 3600
21* = 7200
22* = autobaud
___________________________________________________________
12:1 PAD Flow Control (Device Can Flow Control the PAD)
0 = disabled
1 = enabled
___________________________________________________________
13:1 Line Feed/Carriage Return Insertion (Data Mode) (value combinations allowed)
0 = none
1 = insert <LF> after <CR> to device
2 = insert <LF> after <CR> from device
4 = insert <LF> after echoed <CR>
8* = insert <CR> after <LF> to device
___________________________________________________________
14:0 Padding after Line Insertion (Data/Command Mode)
0 = none
1255 = number of character
___________________________________________________________
15:1 Editing in Data Transfer Mode
0 = disabled
1 = enabled
___________________________________________________________
16:127 Character Delete Character
___________________________________________________________
34
ASYNCXS
C320001300D0
___________________________________________________________
17:0 Line Delete Character
___________________________________________________________
18:0 Line Display Character
___________________________________________________________
19:2 Transmit Editing Service Signals
1 = for print devices
2 = for display terminals
___________________________________________________________
20:0 Echo Mask
0 = no mask
1 = no <CR> echo
2 = no <LF> echo
4 = no <VT>, <HT>, or <FF> echo
8 = no <BEL> or <BS> echo
16 = no <ESC> or <ENQ> echo
32 = no <ACK>, <NAK>, <STX>, <SOH>, <EOT>, <ETB>, or <ETX> echo
64 = no editing character echo
128 = no echo of <NUL>, <SO>, <SI>, <DLE>, <DC1>, <DC2>, <DC3>, <DC4>,
<SYN>, <CAN>, <EM>, <SUB>, <FS>, <GS>, <RS>, <US>, <DEL>
___________________________________________________________
21:0 Parity Treatment
0 = 8 bits no parity
2 = 8 bits, odd, no check
3 = 8 bits, odd
6* = 8 bits, even, no check
7* = 8 bits, even
16* = 7 bits, no parity

18* = 7 bits, odd, no check
19* = 7 bits, odd
22* = 7 bits, even, no check
23* = 7 bits, even
___________________________________________________________
22:0 Page Wait (not currently implemented)
0 = none
___________________________________________________________
23*:0 Additional Forwarding Character 1
0 = none
___________________________________________________________
24*:0 Additional Forwarding Character 2
0 = none
___________________________________________________________
25*:0 Output Pending (Due to Input)
0 = none
___________________________________________________________
26*:0 Interval Timer (For Transmitting Data)
0 = none
1255 = time (1/20 seconds)
___________________________________________________________
27*:0 Padding After Horizontal Tab <HT>
0 = none
___________________________________________________________
ASYNCXS
C320001300D0
35
___________________________________________________________
28*:0 XON Character from PAD to Device
0 = DC1
___________________________________________________________
29*:0 XOFF Character from PAD to Device (value combinations allowed)
0 = DC3
128 = send <BEL> only if typeahead buffer overflows
___________________________________________________________
30*:0 XON Character from Device to PAD
0 = DC1
___________________________________________________________
31*:0 XOFF Character from Device to PAD
0 = DC3
___________________________________________________________
80*:1 Signon Options (value combinations allowed)
0 = no wait for input
1 = wait for <CR>
4 = run signon file
8 = enable CTS output flow control
16 = enable DTR input flow control
32 = enable RTS input flow control
___________________________________________________________
81*:24 Session Control (value combinations allowed)
0 = none
1 = disable <CR> terminate
2 = autocall at enable
4 = disable at call clear
+8 = auto reenable
+16 = enable symbols
64 = restore precall profile at call clear
128 = disable + terminate
___________________________________________________________
82*:0 Alternate Break Character
0 = none
___________________________________________________________
83*:0 Forwarding on Character Count
0 = none
___________________________________________________________
84*:0 Read Options (value combinations allowed)
0 = none
8 = convert to uppercase
2 = enable X3.64
16 = passall
4 = filter X3.64
___________________________________________________________
85*:0 Discard Output
0 = none
___________________________________________________________
86*:0 Diagnostic Echo
0 = none
1 = echo
2 = echo size
3 = primary
4 = alternate
___________________________________________________________
36
ASYNCXS
C320001300D0
X.3 Parameter Descriptions

Parameter numbers followed by an asterisk (*) are Telematics extended
parameters; individual parameter values followed by an asterisk are
Telematics extended values. Values noted with a plus sign (+) are part of a
value combination required to match the default value. Values noted with
a double asterisk (**) are not supported.
P0 National Marker
P0 indicates to the PAD that any parameters following it are national
parameters.
Value
Function
0 . . . . . . . . . Default national marker value
P1 PAD Recall
P1 specifies how the terminal switches from data transfer mode to
command mode while a call is active. When a user enters the PAD recall
character, the terminal switches from data transfer mode to command
mode and then remains in command mode so that X.28 commands can be
entered. If the terminal is already in command mode, the PAD recall
character has no effect, i.e., the character is ignored. To return to data
transfer mode, enter the X.28 Continue command, <CR>, or +.
If any data characters were entered prior to the PAD recall character but
were not yet forwarded, they are forwarded when the PAD recall character
is entered.
If the network has data destined for the device when it enters command
mode, the PAD retains the data controlled at that point by X.25 protocol
subject to window size, flow control, and buffer size. Data is delivered to
the terminal when it returns to data transfer mode. When the PAD is flow
controlled, any X.29 command sent by a remote PAD is not processed
until flow is reenabled. This may cause an X.29 command timeout at the
remote PAD.
Value
Function
0 . . . . . . . . . PAD recall disabled
1 (Def) . . . . Recall with <DLE> character (CtrlP)
2255 . . . . . Value of recall character (CtrlB, ..., <DEL>)
When P1=0, the terminal cannot switch to command mode by entering a
single character.
When P1=1, entering the <DLE> character (or CtrlP) switches the
terminal to command mode.
When P1=2255, entering the character associated with the specified
value switches the terminal to command mode. CtrlA and Ctrl1 cannot
be used as PAD recall characters.
ASYNCXS
C320001300D0
37
You can also switch from data transfer mode to command mode by
transmitting a break if P7=8. To maintain character transparency and
permit any ASCII character to be sent as data, set P1=0 and use a break
(P7) to escape from data transfer mode.
P2 Terminal Echo
P2 tells the PAD whether input data from the device is to be transmitted
back to the device for visual display on the screen.
When local echo is enabled and block mode input is used, a delay can
occasionally occur between key depression and the character appearing on
the screen. This delay depends on the devices configured FBTimer value.
Value
Function
0 . . . . . . . . . Disable echo
1 (Def) . . . . Enable echo
P3 Data Forwarding Characters
P3 defines the characters that are used in data transfer mode to forward
accumulated data to the remote device. To select combinations of
forwarding characters, add the values and specify the sum. For example,
to select <CR>, <ETX>, and <EOT> as the data forwarding characters, set
P3=18 (the sum of 2 + 16).
Value
Function
0 . . . . . . . . . No data forwarding characters
1 . . . . . . . . . Forward on receipt of alphanumeric characters AZ,
az, and 09
2 (Def) . . . . Forward on receipt of <CR> character
4 . . . . . . . . . Forward on receipt of <ESC>, <BEL>, <ENQ>, and
<ACK> characters
8 . . . . . . . . . Forward on receipt of <CAN>, <DEL>, and <DC2>
characters
16 . . . . . . . . Forward on receipt of <ETX> and <EOT> characters
32 . . . . . . . . Forward on receipt of <HT>, <LF>, <VT>, and <FF>
characters
64 . . . . . . . . Forward on receipt of any other ASCII control
characters not included above
P4 Data Forwarding on Timeout
P4 controls the idle data forwarding timer. A nonzero value specifies the
interval of inactivity in data transfer mode after which the PAD forwards
any accumulated data to the remote device.
The timer is reset and started when a character is entered from the device.
If the P4 interval expires before another character is entered, the
characters in the packet are forwarded. Empty packets are not forwarded.
38
ASYNCXS
C320001300D0
Forwarding on expiration of the idle timer is disabled if editing is enabled

in data transfer mode (P15=1).
When the idle timer is enabled (P4 is nonzero), P26 (interval timer for
data forwarding) has no effect.
When block mode input is used, the FBTimer value may affect the idle
timers accuracy.
Value
Function
0 (Def) . . . . No data forwarding on timeout
1255 . . . . . Value of idle timer in twentieths of a second (50 ms)
P5 Flow Control of the Device
P5 specifies whether the PAD can send flow control characters to the
terminal in data transfer mode and command mode.
Value
0 (Def) . . . .
1 .........
2 .........
Function
No device flow control in data transfer mode
Device flow control in data transfer mode
Device flow control in command and data transfer
modes
When P5=1, flow control manages data entry into the typeahead buffer
while a call is active. The PAD flow controls the device whenever the
PAD is temporarily unable to receive more data because the flow control
level of the typeahead buffer is reached. When the PAD is later able to
accept data, it cancels flow control. In addition, the PAD sends a flow on
signal/character to the terminal when a call is established, and a flow off
signal/character to the terminal when a call is cleared.
When P5=2, flow control manages data entry into the typeahead buffer
even when a call is not active. The PAD flow controls the device when the
PAD is temporarily unable to receive more data because the flow control
level of the typeahead buffer is reached. When the PAD is later able to
accept data, it cancels flow control.
Flow control can be done with characters (XON and XOFF) or modem
signals. P28 and P29 specify the XON and XOFF character values. P80
specifies modem flow control by CTS, DTR, or RTS.
When P29 > 127, the PAD sends <BEL> characters to the terminal when
the typeahead buffer is full and P5 is nonzero.
If ASYNCXS is using a Line Processing Module (LPM) port that is
configured with XON/XOFF flow control, you cannot disable flow control
with P5.
Telematics strongly recommends that flow control be enabled (with P5)
and that the device respond accordingly when performing file transfers.
This is especially critical when echo is also enabled (with P2).
ASYNCXS
C320001300D0
39
P6 PAD Service Signals

P6 indicates whether PAD service signals are to be transmitted to the
device. A PAD service signal is either a response to an X.28 command or
a status indication for the PAD or the network.
Value
0 .........
1 .........
4 .........
Function
Signals are not transmitted
All signals except the prompt are transmitted
Standard prompt is transmitted; no service signals are
transmitted
5 (Def) . . . . Standard service signals and prompt are transmitted
8 . . . . . . . . . Service signals are transmitted in extended format
9 . . . . . . . . . Extended format service signals are transmitted; no
prompt is transmitted
12 . . . . . . . . Devicespecific prompt is transmitted; no service
signals are transmitted
13 . . . . . . . . Extended format service signals and devicespecific
prompt are transmitted
16 . . . . . . . . Extended format service signals are transmitted in
English
French
Spanish
When P6=0, 1, or 9, the PAD gives no indication to the device that it is
awaiting a command. This may be required if the device is a host
computer, but can be confusing if the device is a terminal.
Similarly, when P6=0, the PAD does not transmit messages informing the
device of certain events, e.g., invalid X.28 commands or network
connection commands that did not complete. This can be undesirable for a
terminal device; however, for a host computer device, this can eliminate
the need for the host software to parse PAD responses unnecessarily.
You can define an alternate prompt service signal for each terminal. If
P6=12 or 13, this prompt signal replaces the standard X.28 * prompt.
If the extended format plus French and/or Spanish values are set, multiple
service signals may be output.
The X.28 Language command (page 526) can be used to set certain P6
service signal format values (e.g., 5 (DEFAULT parameter) 21 (ENGLISH
parameter), 37 (FRENCH parameter), 53 (SPANISH parameter), 13
(DEPENDENT parameter)).
310
ASYNCXS
C320001300D0
P7 Action of PAD on Receipt of Break Signal

P7 defines the action the PAD takes when it receives a break signal from a
device in data transfer mode. A user sends a break signal by pressing the
break key (or an alternate character that represents the break signal when
P82 is nonzero). If a call is not active, the PAD ignores the break signal.
Value
0 .........
1 .........
2 (Def) . . . .
4 .........
5 .........
8 .........
16 . . . . . . . .
21 . . . . . . . .
Function
No action
Send interrupt packet to remote device
Issue a reset to remote device
Send indication of break message to remote device
Interrupt and indication of break
Escape from data transfer mode to command mode
Discard data destined for the device; sets P8=1
Discard data destined for the device, send interrupt and
break indication
Setting P7=21 can be used to terminate a large volume of output data from
a remote device. In this case, the local PAD transmits an interrupt packet
with all bits of the interrupt user data field set to 0, followed by an
indication of break message to the remote PAD. This message indicates in
its parameter field that P8 has been set to 1, and output is to be discarded.
The remote PAD, upon receiving the interrupt packet, returns a
confirmation packet to the local PAD. Upon receiving the indication of
break, the remote PAD discards any partially completed packets destined
for the local PAD. Before resuming data transmission to the local PAD,
the remote PAD must issue a response to the indication of break with a set
or set and read PAD message, indicating that P8 should be set back to zero
for normal data delivery.
The receipt of a break signal by the remote PAD is a packet forwarding
condition except when P7=0. Similarly, the remote PAD ignores a receipt
of break when no virtual call has been established.
P7=1 instructs the local PAD to transmit an interrupt packet with all bits of
the interrupt user data field set to 1.
P7=5 instructs the local PAD to transmit an interrupt packet with all bits of
ASYNCXS
C320001300D0
311
P8 Discard Output
P8 controls the delivery of data from the network to the device, allowing
normal delivery or instructing the PAD to discard any data received.
The value of P8 is always set initially to zero. For information about when
the PAD changes this value, see the X.29 Recommendation, sections 3.3.1,
3.3.2, and 3.3.3.
Value
Function
0 (Def) . . . . Normal data delivery
1 . . . . . . . . . Discard data
P9 Padding after Carriage Return
P9 controls the PADs automatic insertion of padding characters after each
<CR> character transmitted in the data stream to the device. Padding may
be required for terminals that try to display a character before the
preceding carriage return operation completes (because of a mechanical
printing assembly or other mechanism).
If the sequence <CR><LF> is sent to the device as a format effector for
line folding, or if a <LF> is inserted after the <CR> as specified by P13,
the padding is inserted after the <LF>.
The padding character is specified during device configuration (PADchar
parameter). Unless otherwise specified, the default padding character is
<NUL>. Padding characters are not inserted after a <CR> is echoed to the
terminal.
Value
Function
0 (Def) . . . . No padding after <CR>
1255 . . . . . Number of padding characters to be inserted after a
<CR> sent to the terminal
P10 Line Folding
P10 defines the devices line length. A <CR><LF> is automatically
transmitted to the terminal when data containing more graphic characters
than the defined line length is sent to the terminal. For example, if
P10=80, output lines are folded into 80 character segments when sent to
the terminal.
Only graphic characters count toward line length; nonprinting characters
are not counted.
Value
Function
0 (Def) . . . . No line folding
1255 . . . . . Number of graphic characters per line
312
ASYNCXS
C320001300D0
P11 Speed of Device

P11 indicates the devices line speed. If the initial configuration setting is
autobaud, the PAD sets P11 to reflect the actual device speed when the
device signs on to the PAD.
This parameter is read only; that is, its value can be displayed by the
terminal user, but not changed.
Value
Bit Rate
0 . . . . . . . . . 110
1 . . . . . . . . 134.5
2 . . . . . . . . . 300
3 . . . . . . . . 1200
4 . . . . . . . . . 600
5 . . . . . . . . . 75
6 . . . . . . . . . 150
7 . . . . . . . . 1800
8 . . . . . . . . 200**
9 . . . . . . . . 100**
10 . . . . . . . . 50
11 . . . . . . 75/1200
** Not supported
Value
Bit Rate
12 . . . . . . . 2400
13 . . . . . . . 4800
14 . . . . . . . 9600
15 . . . . . . . 19200
16** . . . . . . 48000
17 . . . . . . . 56000
18** . . . . . . 64000
19* . . . . . . . 2000
20* . . . . . . . 3600
21* . . . . . . . 7200
22* (Def) . . . Autobaud
When P11=11, the input and output line speeds are 75 and 1200 bits per
second, respectively.
To explicitly set the devices speed and parity, configure the speed with
P11, and the parity with P21.
You can configure a device so that the PAD automatically detects the
devices speed and parity when the device attempts to connect to the PAD.
During automatic detection, autoparity and autobaud are inseparable; if
speed is automatically detected, so is parity. In other words, you cannot
specify an explicit parity for the device and autobaud.
To select autobaud/autoparity detection, set P11=22; the P21 setting is
irrelevant. Enter several periods from the terminal at one to two
second intervals. When two periods echo, enter a carriage return to
automatically set the incoming baud rate and parity. At this point, the
PAD sets P11 and P22 to the detected speed and parity.
A one minute timer is set while the software is awaiting the input for
autobaud detection. If this timer expires with no input received from
the device, the device is disabled. You can use P81 to automatically
reenable the device for another minute.
ASYNCXS
C320001300D0
313
P12 Flow Control of the PAD

P12 controls the flow of data from the PAD to the device. If flow control
is enabled, the device notifies the PAD when it is ready to receive data and
when it is not ready to receive data.
Value
Function
0 . . . . . . . . . No flow control of PAD
1 (Def) . . . . Flow control of PAD
When P12=1, the device can flow control the PAD. P80 specifies whether
flow control is done with characters or the CTS control signal.
When flow control using characters is enabled, the XON and XOFF
characters cannot be transmitted as data. When flow control is disabled,
XON and XOFF can be transmitted as data, provided they have no other
special functions defined by other X.3 parameters. P30 and P31 specify
the XON and XOFF character values.
P13 Line Feed After Carriage Return
P13 controls the insertion of a <LF> character after a <CR>, or a <CR>
after a <LF> character, while the device is in data transfer mode. Certain
terminals may require this.
A combination of characteristics can be selected by setting P13 to the sum
of the values required. For example, P13=3 inserts a <LF> on both input
from and output to the device.
Value
Function
0 . . . . . . . . . No insertion of <LF> after <CR>
1 (Def) . . . . Insert a <LF> character after each <CR> sent to the
device (data transfer mode only)
2 . . . . . . . . . Insert a <LF> character after each <CR> sent to the
remote PAD (data transfer mode only)
4 . . . . . . . . . Insert a <LF> character after each <CR> echoed to the
device (data transfer mode only)
8* . . . . . . . . Insert a <CR> character after each <LF> sent to the
device (command and data transfer modes)
P14 Padding after Line Feed
P14 controls the PADs automatic insertion of padding characters after
each <LF> transmitted in the data stream to a device in data transfer
mode. Padding may be required for terminals that try to display a
character before the preceding line feed operation completes (because of a
mechanical printing assembly or other mechanism).
parameter). Unless otherwise specified, the default padding character is
<NUL>.
This parameters value does not add padding characters after the <LF> of
a format effector used for line folding; see P9.
314
ASYNCXS
C320001300D0
Value
Function
0 (Def) . . . . No padding after line feed
1255 . . . . . Number of padding characters to be inserted
P15 Editing in Data Transfer Mode
P15 controls the editing capabilities of the device while it is in data
transfer mode. Editing allows you to modify or display device input data
before it is forwarded.
You can only edit data on the current line. For example, if P10 sets a line
length of 20, and 25 characters have been entered, only characters 21
through 25 can be modified or displayed.
Setting P15=1 suspends the action of P4, i.e., data is not forwarded when
the idle timer expires.
Value
Function
0 . . . . . . . . . Disable editing in data transfer mode
1 (Def) . . . . Enable editing in data transfer mode
P16 Character Delete
P16 specifies the character delete character. Character delete can be used
in data transfer mode only if editing is enabled (P15=1). You can only edit
data on the current line.
Value
Function
0255 . . . . . Decimal value of the character delete character
(Def=127)
P17 Line Delete
P17 specifies the line delete character. Line delete can be used in data
transfer mode only if editing is enabled (P15=1). You can only edit data
on the current line.
Value
Function
0255 . . . . . Decimal value of line delete character (Def=0)
P18 Line Display
P18 specifies the line display character. Line display can be used in data
transfer mode only if editing is enabled (P15=1). You can only edit data
on the current line.
Value
Function
0255 . . . . . Decimal value of line display character (Def=0)
ASYNCXS
C320001300D0
315
P19 Editing PAD Service Signals

P19 controls whether editing PAD service signals are transmitted to a
terminal or to a print device. The PAD issues these signals after it receives
a character delete or line delete character from the terminal. This
parameter is effective only if P6 is not set to 0, which suppresses all
service signals.
Value
Function
1 . . . . . . . . . Transmit printer PAD service signals
2 (Def) . . . . Transmit editing PAD service signals
P20 Echo Mask
P20 instructs the PAD to disable echoing of selected groups of characters
as they are entered from the device. This occurs only in data transfer
mode. P20 is only effective when P2=1, which enables echo.
The PAD recall character specified in P1 is not echoed. If P12 (Flow
Control of PAD) is set to a nonzero value, the XON and XOFF characters
defined in P30 and P31 are not echoed.
Value
0 .........
1 .........
2 .........
4 .........
8 .........
16 . . . . . . . .
32 . . . . . . . .
Function
No echo mask (all characters echoed)
No echo of <CR>
No echo of <LF>
No echo of <VT>, <HT>, or <FF>
No echo of <BEL> or <BS>
No echo of <ESC> or <ENQ>
No echo of <ACK>, <NAK>, <STX>, <SOH>,
<EOT>, <ETB>, or <ETX>
64 . . . . . . . . No echo of editing characters specified in P16, P17,
and P18
128 . . . . . . . No echo of <NUL>, <SO>, <SI>, <DLE>, <DC1>,
<DC2>, <DC3>, <DC4>, <SYN>, <CAN>, <EM>,
<SUB>, <FS>, <GS>, <RS>, <US>, or <DEL>
P21 Parity Treatment
P21 instructs the PAD to check parity in the data stream from the device
and to generate parity in the data stream to the device.
Value
0 (Def) . . . .
2 .........
3 .........
6* . . . . . . . .
7* . . . . . . . .
316
Function
8 bits, no parity
8 bits, odd parity, no check
8 bits, odd parity
8 bits, even parity, no check
8 bits, even parity
ASYNCXS
C320001300D0
16*
18*
19*
22*
23*
.......
.......
.......
.......
.......
7 bits, no parity
7 bits, odd parity, no check
7 bits, odd parity
7 bits, even parity, no check
7 bits, even parity
P22 Page Wait (not currently implemented)

P22 allows the PAD to suspend transmission of characters to the device
after a specified number of lines have been output. This gives the user
time to read the data as it appears before the PAD resumes output.
Value
Function
0 . . . . . . . . . No page wait
P23* Additional Data Forwarding Character
Telematics P23, when nonzero, specifies a character that generates a data
forwarding condition when received from the device. This character is in
addition to those specified by P3 and P24.
Value
Function
0 (Def) . . . . No additional forwarding character
1255 . . . . . Decimal value of additional forwarding character
P24* Additional Data Forwarding Character
Telematics P24, when nonzero, specifies a character that generates a data
forwarding condition when received from the device. This character is in
addition to those specified by P3 and P23.
Value
Function
0 (Def) . . . . No additional forwarding character
1255 . . . . . Decimal value of additional forwarding character
P25* Output Delay Due to Input
Telematics P25 establishes a time delay for displaying output on a
terminal screen when information is being entered from the terminal at the
same time. This delay allows the terminal user to enter data while
information is being written to the screen without changing any of the
displayed data.
When block mode input is used, the FBTimer value may affect the output
delay timers accuracy.
Value
Function
0 . . . . . . . . . No output delay due to input
ASYNCXS
C320001300D0
317
P26* Interval Timer for Transmitting Data

Telematics P26, when nonzero, specifies a time interval for data
forwarding. The timer is started when the device enters data transfer
mode; when it expires, any accumulated data is forwarded. After the data
is forwarded to the remote device, the timer is reset.
Other data forwarding conditions can occur, but they do not reset the
interval timer. For example, if data forwarding characters are specified in
P3, they will still cause data forwarding to occur. In this case, the interval
timer is not reset.
Forwarding on the interval timer is disabled if the idle timer is enabled
(i.e., P4 is nonzero).
When block mode input is used, the FBTimer value may affect the interval
timers accuracy.
Value
Function
0 (Def) . . . . No forwarding on interval timer
1255 . . . . . Timer interval in 1/20 seconds
P27* Padding after Horizontal Tab
Telematics P27 controls the automatic insertion of padding characters
after each horizontal tab character transmitted in a data stream to the
device. Padding may be required for terminals that try to display a
character before the preceding horizontal tab operation completes
(because of a mechanical printing assembly or other mechanism).
parameter). The default padding character is <NUL>.
Value
Function
0 (Def) . . . . No padding after horizontal tab
1255 . . . . . Number of padding characters to be inserted
P28* XON Character from PAD to Device
Telematics P28 specifies the XON flow control character the PAD sends,
if flow control is enabled in P5.
Value
Function
0 (Def) . . . . XON character is <DC1>
1255 . . . . . Decimal value of the XON character
P29* XOFF Character from PAD to Device
Telematics P29 specifies the XOFF flow control character the PAD sends,
if flow control is enabled in P5.
When P29=128, the PAD sends a <BEL> character to the device each
time it receives an input character from the device after the typeahead
buffer is full. The <BEL> indicates that the character just entered was
discarded.
318
ASYNCXS
C320001300D0
You can specify an XOFF character and the use of the <BEL> by giving
P29 the value of 128 plus the decimal value of the XOFF character. For
example, if P29=150 (128+22), the XOFF character from the PAD to the
device is specified as <SYN>, and the PAD sends <BEL>s when the
typeahead buffer is full.
Value
0 (Def) . . . .
1127 . . . . .
128 . . . . . . .
Function
XOFF character is <DC3>
Decimal value of the XOFF character
Send <BEL> when typeahead full
P30* XON Character from Device to PAD

Telematics P30 specifies the XON flow control character the PAD accepts,
if flow control is enabled in P12. If the PAD has been flow controlled (i.e.,
received an XOFF character), it resumes transmitting data to the device
when it receives an XON character.
Value
Function
0 (Def) . . . . XON character is <DC1>
1255 . . . . . Decimal value of XON character
P31* XOFF Character from Device to PAD
Telematics P31 specifies the XOFF flow control character the PAD
accepts if flow control is enabled in P12. Upon receipt of the XOFF
character, the PAD stops transmitting data to the device until it receives an
XON character.
Value
Function
0 (Def) . . . . XOFF character is <DC3>
1255 . . . . . Decimal value of XOFF character
P80* Signon
Telematics P80 controls how devices sign on to the PAD. A device is
considered ready to sign on when it has been enabled (either when it is
configured or by an operator command at a later time).
Value
Function
0 . . . . . . . . . No input required from device before starting signon
procedures
1 (Def) . . . . Wait for device input of a <CR> before signing on the
device
4 . . . . . . . . . Run the local signon include file
8 . . . . . . . . . Enable CTS (clear to send) output flow control
16 . . . . . . . . Enable DTR input flow control
32 . . . . . . . . Enable RTS input flow control
When P80=0, the PAD signs on the device as soon as it is enabled, which
includes modem connection and autobaud procedures. When signon
procedures complete, the device is placed in the connect state. The PAD
does not wait for input from the device to initiate signon procedures.
ASYNCXS
C320001300D0
319
When P80=1, the PAD waits for input of a <CR> from the device before
initiating signon. Once the initial input has been used to sign on the
device, it is discarded and the device is placed in command mode.
When P80=4, the PAD executes the local signon include file for the
device. This file can contain X.28 commands to define symbols, establish
a call, or perform any other operations that can be initiated with
commands entered from the device itself. If P80=4, but no local signon
include file name is specified, the PAD takes no special action.
When P80=8, the PAD enables CTS flow control. In this case, the modem
stops sending data to the device when CTS drops, and resumes when CTS
is on. Setting P80=8 can only be done when the device is offline.
When P80=16, the PAD enables DTR flow control. In this case, the PAD
drops DTR instead of sending XOFF to the device, and raises DTR
instead of sending XON to the device. Setting P80=16 can only be done
when the device is offline.
When P80=32, the PAD enables RTS flow control. In this case, the PAD
drops RTS instead of sending XOFF to the device, and raises RTS instead
of sending XON to the device. Setting P80=32 can only be done when the
device is offline.
Both input flow control options (values 16 and 32) cannot be set at the
same time.
You can specify a combination of signon options. For example, if P80=5,
the PAD waits for input before signing on the device, and when input is
received, runs the signon include file, if present.
When P80s value is even (0, 4, 8, 16, or 32), the device is signed on as
soon as it is enabled, following modem connection and autobaud
procedures when required. When P80s value is odd (1 or 5), the device is
not recognized as being signed on to the PAD until the specified signon
actions complete.
P81* Session
Telematics P81 controls operational features of the session between the
device and the PAD.
Value
0 .........
1 .........
2 .........
4 .........
8 .........
Function
No session options
Disable <CR> command termination
Perform autocall at device enable
Disable device at call clear
Initiate reenable after disable, except INF operator
command (Default=24; 8+16)
16 . . . . . . . . Enable symbolic replacement (Default=24; 8+16)
64 . . . . . . . . Restore precall profile on call clear
320
ASYNCXS
C320001300D0
128 . . . . . . . Disable + command termination

When P81=0, <CR> or + act as terminators for X.28 commands.
When P81=1, <CR> is no longer used as a terminator for X.28 commands.
When P81=2, the autocall facility is enabled. The PAD automatically tries
to initiate a call to the devices default called NUA when the device is
enabled and signed on. A time delay can be specified for the autocall; in
this case, the PAD waits the specified number of seconds before initiating
the call. Autocall is not implemented for PVC connections.
The autocall facility is not used if a device that has been signed on
automatically has an X.28 Call command in its signon include file. P80
specifies whether a device is signed on when it is created and if a signon
include file is to be run.
When P81=4, the device is automatically disabled when the next call clear
occurs. This value is also set if a modem connection is lost (i.e., DSR goes
low or CD goes low for longer than 2 seconds).
When P81=8, the device is automatically reenabled if it becomes
disabled. The device can be disabled by an X.28 Terminate command, or
when the command or data transfer mode timeout expires (either by a
command from the terminal or by certain error conditions) or when the
next call clear occurs (P81=4). However, if the device is disabled by a
command from INF, it is not automatically reenabled.
When P81=16, the symbolic replacement facility is enabled, which
permits symbolic assignment from the terminal and the replacement of a
symbol with its value.
When P81=24, this corresponds to the default.
When P81=64, the devices X.3 parameter profile is reset when a call is
cleared to its value when the call was initiated.
When P81=128, the + character is no longer used as a terminator for X.28
commands.
You can specify a combination of facilities. For example, to enable
symbolic replacement and to cause the device to be disabled when a call is
cleared, set P81=20 (4+16).
P82* Alternate Break Signal
Telematics P82, when nonzero, specifies an ASCII character which the
PAD treats as a break signal.
Value
Function
0 (Def) . . . . No alternate break character

1255 . . . . . Decimal value of alternate break character
ASYNCXS
C320001300D0
321
P83* Forwarding on Character Count

Telematics P83, when nonzero, defines an additional data forwarding
condition. After a specified number of characters have been entered, the
data is forwarded if no other data forwarding condition has occurred.
When data accumulates in the typeahead buffer, the generated X.25 packet
size is not controlled by P83. This means that when the input rate is too
fast for the PAD or network to generate a packet for every forwarding
condition, the data is forwarded in larger packets. If a backlog develops
for a port, it is handled quickly, and a large queue does not develop in the
network.
When block mode input is used, data may occasionally not be forwarded
after the specified number of characters is entered; this depends on the
FBTimer value.
Value
Function
0 (Def) . . . . No forwarding on character count
1255 . . . . . Maximum character count for data forwarding
P84* Extended Read Options
Telematics P84 specifies additional options when the PAD reads data from
a device.
Value
Function
0 (Def) . . . . No extended read options
2 . . . . . . . . . Enable X3.64 escape sequence termination
4 . . . . . . . . . Filter out X3.64 escape sequences
8 . . . . . . . . . Convert lowercase input to uppercase
16 . . . . . . . . Read in passall mode
When P84=2, X3.64 escape sequence termination is enabled.
When P84 =4, X3.64 escape sequences are filtered from input from the
device.
When P84=8, lowercase input characters are converted to uppercase.
When P84=16, characters are read from the device in passall mode, i.e.,
all control characters are read as data without interpretation.
You can specify a combination of these facilities by setting P84 to the sum
of the values.
322
ASYNCXS
C320001300D0
P85* Local Discard Output

Telematics P85, when nonzero, specifies a character that causes the PAD
to discard any output data destined for the device. This is called local
discard, because the request to discard output is only honored by the local
PAD: it is never transmitted to the remote PAD.
The discarded output only applies for the duration of the current logical
message, i.e. the current output packet(s) with the M bit set. It does not
discard data for the remainder of the connection.
P85 does not affect the value of P8. See the descriptions for P7 and P8 to
optionally discard output data.
If output to the device is in progress and the character specified in P85 is
entered from the device, further output is discarded. Output can be
reenabled by entering the P85 character again.
Value
Function
0 (Def) . . . . No local discard
1255 . . . . . Decimal value of character to cause discard
P86* Diagnostic Echo
Telematics P86, when nonzero, enables one of several diagnostic echo
options. If the device is in data transfer mode and receives input from the
remote device, these options cause the PAD to immediately transmit
certain character strings to the remote device.
This option can be used to verify the integrity of the data path between the
remote device and the PAD, and to measure the time delay within the
network.
Value
0 (Def) . . . .
1 .........
2 .........
Function
No diagnostic echo
Echo received data characters
Echo primary test pattern with length equal to the
ASCII value of the received character
3 . . . . . . . . . Echo full primary test pattern
4 . . . . . . . . . Echo full alternate test pattern
The primary test pattern is shown below; P10s value specifies the actual
number of characters displayed on a line.
THE QUICK BROWN FOX JUMPED OVER THE LAZY DOGS BACK
~0123456789 The quick brown fox jumped over the lazy
dogs back
+!@#$%^&*()[]<>?/:;\|{}.,
The alternate test pattern is shown below; P10s value specifies the actual
number of characters displayed on a line.
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
0123456789
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
0123456789
ASYNCXS
C320001300D0
323
324
ASYNCXS
C320001300D0
4 ASYNCXS PMM Commands

This chapter describes the ASYNCXS PMM commands.
Before Creating Devices

Before creating devices, complete the following tasks:
Create X.3 directories and profiles You must create X.3 directories
before creating profiles. X.3 profiles can then be associated with a device
with the PROFILE=<name> parameter.
Customize NUAs NUA addresses are specified when creating devices
(CALLEd and CALLIng parameters).
Create device directories Every device you create must reside in a
directory; therefore, use the Create Directory command before the Create
Device command.
Once a device is created, you use its name in other commands such as
Modify Device, Destroy Device, and Show Statistics.
ASYNCXS
C320001300D0
41
ASYNCXS PMM COMMANDS
ASYNCXS Command Summary

All ASYNCXS commands have a user access privilege of 2. Access
privilege is a 32 category mask that defines the valid categories of access
for INF commands. For more information, see the INF Manual.
Add Map . . . . . . . . . . .
Collect Statistics . . . . . .
Create Device . . . . . . . .
Create Directory . . . . . .
Create Profile . . . . . . . .
Define Initial . . . . . . . .
Delete Map . . . . . . . . . .
Destroy Device . . . . . . .
Destroy Directory . . . . .
Destroy Profile . . . . . . .
Disable Device . . . . . . .
Enable Device . . . . . . .
Erase Map . . . . . . . . . .
Modify Device . . . . . . .
Modify Initial . . . . . . . .
Modify Profile . . . . . . .
Reset Statistics . . . . . . .
Set Defaults Devices . .
Set Defaults Initial . . . .
Set Defaults Profiles . .
Show Defaults Devices
Show Defaults Initial . .
Show Defaults Profiles
Show Device . . . . . . . .
Show Directory . . . . . .
Show Initial . . . . . . . . .
Show Map . . . . . . . . . .
Show Profile . . . . . . . .
Show Statistics . . . . . . .
42
Adds a PADmap table entry

Collects device statistics in a file
Creates a devices definition
Creates a device or profile directory
Creates an X.3 profile
Identifies logical volume options
Deletes a PADmap table entry
Deletes a devices definition
Deletes an empty profile directory or device
directory
Deletes an X.3 profile
Sets a device offline
Makes a device eligible to be signed on
Deletes all PADmap table entries
Changes a devices definition
Changes an alarm logical volume option
Changes an X.3 profiles characteristics
Resets a devices statistics to zero
Specifies default device parameter values
Specifies default logical volume options
Specifies default X.3 profile parameter values
Displays default device parameter values
Displays default volume options
Displays default X.3 profile parameter values
Displays device parameter values
Displays directory entry names
Displays logical volume options
Displays PADmap table entries
Displays an X.3 profiles parameter values
Displays device statistics
ASYNCXS
C320001300D0
Add Map
The Add Map command adds an entry to the PADmap table.
Syntax
ADD MAP NUA=<called_nua> [CUD=<call_user_data>] PORt=<port>
Parameters
NUA=<called_nua>
Called NUA address of an incoming call. The value assigned to the
NUA field in a PADmap entry is compared to the called address field
of the incoming call request.
Range:
115 digits; % and * wildcard characters are allowed

(surrounding quotes are optional for asterisk wildcard)
CUD=<call_user_data>
Call user data of an incoming call. The values P%, P%%, P%%%, or
P%%%% can be specified to indicate that the call user data field of the
incoming call request can contain up to four digits representing the
subaddress (port number). In this case, the port field must be #. If an
empty string () is specified, only incoming calls with no user data
will satisfy the match.
Range:
112 alphanumeric characters (09, az, AZ, and $); %

and * wildcard characters are allowed; leading spaces are
deleted; a string containing special characters must be
enclosed in quotes; must specify P%[%][%][%] if PORt=#
PORt=<port>
String identifying the devices port number where the incoming call is
to be routed.
Range:
*, #, #n, or mmmnnn, in the range 0479
Examples
The following command indicates that incoming calls with any called
NUA and with no call user data will be routed to the first available port of
12, 13, 14, 15, and 16.
add map nua=* port=1216
The following command indicates that incoming calls whose called NUA
has exactly 10 digits beginning with the digits 9999404, and whose call
user data consists of three characters beginning with P will be routed to
the port whose number is specified by the last two digits of the call user
data.
add map nua=9999404%%% cud=P%% port=#
ASYNCXS
C320001300D0
43
Collect Statistics
The Collect Statistics command collects (and optionally resets) device
statistics from one or more ASYNCXS devices.
Syntax
COLlect[,Verify][,RESet] STATISTICS [ON] <device> [USING]
<stat_file>
Modifiers and Parameters
Verify
When specified, displays a verification message when the command
completes.
Reset
When specified, zeroes statistics after theyre written to the file.
ON
Aids readability.
<device>
Device name.
Range: Defined device names; wildcard characters are allowed
Default: ??
USING
Aids readability.
<stat_file>
Statistics file name. This file must have been previously activated for
statistics collection with an INF Activate Statistics command.
Range:
Names of previously activated statistics files
Example
The following command collects device statistics from the device named
device/d10 and writes them to the previously activated statistics file
named statsd10.
col statistics on device/d10 using statsd10
44
ASYNCXS
C320001300D0
Create Device
The Create Device command identifies a port as an ASYNCXS device.
Before creating the device, you must create a device directory (Create
Directory command). You may also want to establish default parameter
values with a Set Defaults Devices command. If profiles are to be used,
you must create a profile directory (Create Profile command). You can
then define the profiles to be used in this directory. You may also want to
establish default parameter values with a Set Defaults Profile command.
After the appropriate directories are created, the device can be created. A
device name and port number (corresponding to the physical channel)
must be specified. The command then allocates a channel and its
associated resources.
If the device is created in PAD mode (the default), it is also registered to
receive incoming calls, which allows it access to the packet switching
network through ASYNCXS. If the device is created in handler mode, it
can be IO/OPENed and have IO/READs and IO/WRITEs issued to it.
Only one Create Device command can be issued for a physical channel. If
X.3 parameter values and/or a local signon file have previously been
specified in a Create Profile command, and different values are specified
in the Create Device command, the Create Device command values are
used.
Syntax
CReate DEvice <dev_dir>/<dev_name> [USING] <port>
[<optional_ parameters>]
Parameters
<dev_dir>/<dev_name>
Device directory name followed by a slash and the device name.
Range:
116 characters <dev_dir>; 116 characters <dev_name>
USING
Enhances readability.
<port>
Asynchronous port number to which device is attached. This must be a
scanned port.
Range:
0479
<optional_parameters>
Described below:
ACCNumber=<accnumber>
Account number to be used with Telematics accounting.
Range:
ASYNCXS
C320001300D0
or 120 characters
45
ACCType=<acctype>
Account type to be used with Telematics accounting.
Range:
0255
BILling=<billing>
Billing number to be used with Telematics accounting.
Range:
132 digits
BLOCK=(BUFsize=<bufsize>,ELEments=<elements>,
[NO]FBTimer[=<fbtimer>]) | NOBLOCK
Level 1 input method. NOBLOCK indicates single character input.
BLOCK indicates block mode input, with <bufsize> the number of
bytes each buffer can hold, <elements> the number of buffers, and
<fbtimer> the time between the receipt of the first byte in the
buffer and when the buffer is read if it is not full.
NOFBTimer indicates the buffer will be read immediately; an
FBTimer value indicates the time delay before reading the buffer.
Telematics recommends that you do not change the block mode
parameters from their default values; they represent optimization
for file transfers and interactive users.
Range:
NOBLOCK |
BLOCK=(BUFsize=<232000>,ELEments=<2250>,
[NO]FBTimer=<02000 milliseconds>)
BREAKTime=<breaktime> | BREAKString=<breakstring> |
NOBREAK
Format of the break signal sent from the PAD to the device when
an indication of break PAD message is received from the network.
NOBREAK indicates the PAD does not send anything to the
device. BREAKTime indicates the PAD sends a binary 1 for the
specified time. BREAKString indicates the PAD sends the
specified string.
Range:
BREAKTime=<010000 milliseconds> |
BREAKString=< or 190 characters> | NOBREAK
CALLDElay=<calldelay>
Delay after which the PAD automatically places an X.25 call (if
autocall is enabled) once the device is created. To enable autocall,
X.3 P81 must equal 2 or a sum including 2, and the device must
have a valid called address.
Range:
0500 seconds
CALLEd=<called_addr>
Called NUA (default destination address for an X.28 Call
command). This is used when the called address is omitted or
when autocall is enabled (P81=2 or a sum including 2). If this
parameter is omitted, each X.28 Call command must include a
called address.
46
ASYNCXS
C320001300D0
Range: or 115 digits

CALLIng=<calling_addr>
Calling NUA. Must be specified for a device to be notified by the
PAD of an incoming call.
Range: or 115 digits
CALLMethod=NORmal | DIRect | PVC | SVC
Type of remote connections that can be initiated from the device.
DIRect indicates the X.28 Call command initiates calls to a remote
device, but no called NUA can be provided with the command.
The device specification must have a value assigned to the called
NUA parameter, which is used as the destination address.
NORmal indicates remote connections can be supported by SVCs
or PVCs, and a called NUA can be provided in the X.28 Call
command.
PVC indicates the X.28 Call command cannot be used. Remote
connections use PVCs, and are initiated with the X.28 Connect
command.
SVC indicates the X.28 Connect command cannot be used.
Remote connections use SVCs, and are initiated with the X.28 Call
command.
CHArge=<charge>
Charge type to be used with Telematics accounting.
Range: 0255
CMDTImeout=<cmdtimeout>
Timeout value when the device enters X.28 command mode. When
this timer expires, ASYNCXS places the device in data transfer
mode if a call is active. If no call is active, the device is disabled.
A zero value indicates no timer (i.e., no timeout).
Range: 0500 seconds
Call user data to be sent with each call request, if the
corresponding field is omitted in the X.28 Call command. If this
information is omitted in the device specification and the X.28
Call command, no call user data is sent except the protocol
identifier.
Range: 1124 characters
DIRectory=<vol:dir/>
Volume and directory containing profiles the device can use.
[NO]DTRCall
DTRCall indicates the PAD raises DTR when an X.25 call is
established (prior to the X.28 incoming call PAD service signal),
and lowers DTR when an X.25 call is cleared (after the clear
confirmation PAD service signal).
ASYNCXS
C320001300D0
47
DTRCall cannot be specified when SPeed=AUTObaud. It is also

incompatible with modem (i.e., DTR and RTS) input flow control.
It overrides all the modem subparameters. Input modem signal
detection is disabled. If you specify DTR input flow control with
X.28 or X.29 commands, DTRCall overrides it. If DTRCall is
specified, DTR may temporarily go high when the device is
enabled.
FCLevel=<flow_control>
Number of character positions remaining in the typeahead buffer,
at which point the PAD outputs the flow control character (if P5=1
or 2, and output flow control is enabled). The flow control level
should be based on the device speed and the device response to a
flow control signal.
Range:
032767
INState=ONLine | ENAbled | OFFline | CONnected | DISabled

Initial device state. OFFline and DISabled create the device and
leave it in the disabled (offline) state; an Enable Device command
must be used to enable (online) the device. ONLine, ENAbled, and
CONnected create the device and enable it (no Enable Device
command). If OFFline is specified, no checking is done to see if
the port is scanned or if another task is using it.
INTdata=<intdata>
Single data byte to be sent with the X.29 Interrupt command if not
specified in the command.
Range:
0255 ($00$ff)
LSignon=<signon_file>
Name of file containing X.28 commands to be executed when the
device signs on to the PAD (if X.3 P80:4). Do not precede the file
name with the tm: identifier.
Range:
or 187 characters
MAxsymbols=<maxsymbols>
Maximum number of symbols that can be defined for a device
(Symbol Assignment command).
Range:
0256
Devices modem characteristics. Multiple values must be separated
by commas.
MODem indicates the device is configured for modem support.
ASYNCXS enables modem signal change notification (DSR,
DCD, and Ring Indication). See Chapter 2 for information about
subparameter effects. NOMODem indicates the device is not
configured for modem support.
48
ASYNCXS
C320001300D0
OPM=PAD | HANdler
Creates the device in either PAD or handler operating mode. The
handler operating mode allows a user task to issue TRAX IO
services to the PAD device.
PADchar=<padchar>
Padding data transmitted to the device. P9, P14, and P27 determine
padding.
Range:
0255 ($00$ff)
PARameters=(<n:v,...>)
X.3 parameter values.
Range:
See Chapter 3
PROFile=<profile>
Name of devices initial or default X.3 profile.
Range:
116 characters
PROMpt=<prompt>
Devices prompt string when it is in command mode. P6 controls
the prompt display.
Range:
or 116 characters; embedded spaces are not allowed
RETRYCount=<retrycount>
Number of times a call will be retried in case of failure. A zero
value indicates no retry limit. The RETRYTime parameter
specifies the interval between retries.
Range:
0127
RETRYTime=<retrytime>
Interval the PAD waits after a call has failed before trying again.
The RETRYCount parameter specifies the maximum number of
retries.
Range:
6600 seconds
REVerse=YES | NO | ALways
Reverse charging call facility. YES indicates the reverse charging
facility is specified in the X.28 Call command. NO indicates
reverse charging is not used, even if specified in the X.28 Call
command. ALways indicates reverse charging is used on every
call, even if it is not specified in the X.28 Call command.
RSIGNOFf=<remote_signoff_file>
Name of file containing X.28 commands to be executed when an
X.25 call to the device is cleared. Do not precede the file name
with the tm: identifier. If P81:4, the remote signoff file is not
executed at call clear time.
Range:
ASYNCXS
C320001300D0
or 187 characters
49
RSIGNON=<remote_signon_file>
PAD device issues a successful X.28 Call command or
successfully accepts a call. Do not precede the file name with the
tm: identifier.
Range:
or 187 characters
SERvice=NONE | DIAL | DIREct | 0255

Device connection (used with Telematics accounting): dial up
(DIAL or 1), leased line (DIREct or 2), neither dial up nor leased
line (NONE or 0), or other (0255).
SPeed=50 | 75 | 110 | 134 | 150 | 300 | 600 | 1200 | 1800 | 2000 | 2400 |
3600 | 4800 | 7200 | 9600 | 19200 | AUTObaud
Bit rate of device accessing the PAD. This parameter has the same
effect as X.3 P11, and setting P11 causes this parameter to be
assigned that value.
STOPbits=1 | 2
Number of stop bits.
TYPeahead=<buffersize>
Number of characters the typeahead buffer can hold.
Range:
12032767
X25IDLETimer=<timeout>
Data transfer mode timer value used to detect inactivity on an X.25
link. The timer starts when a device enters data transfer mode or
when ASYNCXS completes a write request to NET25. The timer
stops when a read from the device completes. When the timer
expires, the active call is cleared and the device is disabled. A zero
value indicates no timer (i.e., no timeout). (This parameters alias
is datatimeout, which was used in prior releases.)
Range:
0500 minutes
X25IORead=<x25ioread>
Size of read to be issued to X.25. A zero value indicates the links
maximum packet size will be used.
Range:
065535 bytes
X25IOWrite=<x25iowrite>
Size of write to be issued to X.25. A zero value indicates the links
Range:
065535 bytes
X25volume=<x25volume>
Name of X.25 volume to be associated with a device. This allows
association of different NET25 revisions with devices.
Range:
410
18 characters (if 9 characters are entered, the 9th must

be a colon)
ASYNCXS
C320001300D0
X28type=TELEmatics | C84
Type of X.28 commands available to the device. TELEmatics
indicates the device can issue any of the X.28 commands,
including Telematics extended commands. C84 indicates the
device is limited to CCITT 1984 X.28 standard commands, plus
only a few of the Telematics extended commands.
X3Type=TELEmatics | C84
Range of X.3 parameters available to the device. TELEmatics
indicates the device can use the full set of X.3 parameters,
including Telematics extended parameters. C84 indicates the
device is limited to CCITT 1984 X.3 standard parameters.
Examples
The following command creates a device (in the device directory named
device) with the IO entity name d23, connected to asynchronous port
number 23. The calling (local) NUA is 100010023432. The called
(remote) NUA is 1000221143054. All other parameters accept the defaults
in the most recent Set Defaults Device command, or the defaults from task
startup.
create device device/d23 using 23 called=1000221143054~
calling=100010023432
The following command creates a device (in the device directory named
devices) with the IO entity name d55, connected to asynchronous port
number 55. The calling (local) NUA is 311022510043. The default data
byte to be sent with an X.29 Interrupt command is $34. The device is
connected to a modem with the hangup option set, and the initial profile is
taken from a named profile that was previously created.
cr dev devices/d55 using 55 calling=311022510043~
intd=$34 modem=(modem,hangup) profile=terminal~
dir=asyncxs:profile/
The following command creates a device with the IO entity name 13 (in
the device directory named termdevs), connected to asynchronous port
number 13. The calling (local) network user address is 777720066754; the
called (remote) address is 777710023456. A maximum of 50 symbols can
be defined for this device. X.3 parameters are described after the example.
cr dev termdevs/13 13 calling=777720066754~
called=777710023456 maxs=50 par=(11:14,81:88)
P11s value of 14 specifies a bit rate of 9600.

P81s value of 88 specifies that the device is automatically reenabled
if it becomes disabled, that the symbolic replacement function is
enabled, and the devices X.3 parameter profile is reset when a call is
cleared to the values it had when the call was initiated.
ASYNCXS
C320001300D0
411
Create Directory
The Create Directory command creates a directory for devices and/or X.3
profiles. You must create a directory before creating the actual device and
X.3 profile.
Syntax
CReate DIrectory DEvice|PRofile <directory_name>/
Parameter
<directory_name>/
Directory name followed by a slash.
Range:
116 characters
Examples
The following command creates a device directory named device.
cr di device device/
The following command creates a profile directory named prof1.

create dir profile prof1/
412
ASYNCXS
C320001300D0
Create Profile
The Create Profile command defines a set of X.3 parameter values that
can be associated with a device.
Before creating a profile, you must create a profile directory (Create
Directory command). Also, before creating devices you may want to
establish default parameter values with the Set Defaults Profiles
command. Then, when you create a profile, you need only specify
parameters you want to change for the particular profile. If you have not
established defaults, the defaults assigned at task startup are used; X.3
parameter default values are listed in Chapter 3.
After an X.3 profile is defined, you can use the X.28 Profile command to
change the X.3 profile associated with a device.
Syntax
CReate PRofile <prof_dir>/<prof_name>
[PARameters=(<number>:<value>,...)]
Parameters
<prof_dir>/<prof_name>
Profile directory name followed by a slash and the profile name.
Range:
116 character <prof_dir>; 116 character <prof_name>
PARameters=(<number>:<value>,...)
Range:
See Chapter 3
Example
The following command defines a profile named R1 in the profile
directory named profile. The parameters not supplied (0, 19 through 31,
and 81 through 86) and the remote signon include file name, will be set
based on the corresponding values of the default profile. Table 31
contains parameter definitions and functions. This example assumes the
user is currently located at the appropriate profile directory.
create profile profile/R1 par=(1:1,2:1,3:2,4:0,5:0)~
par=(6:5,7:0,8:0,9:0,10:0,11:14,12:0,13:0,14:0)~
par=(15:1,16:127,17:24,18:18,80:1)
ASYNCXS
C320001300D0
413
Define Initial
The Define Initial command identifies the logical volume name to receive
handler alarms and/or the NET25 interface compatibility revision. This
should be the first command issued after the ASYNCXS task is mounted.
Syntax
DEFine INitial [ALarmvol=<alarm_vol>] [X25revision=F|G|H]
Parameters
ALarmvol=<alarm_vol>
Name of logical volume to receive handler alarms.
Default: none; no alarms handler
X25revision=F|G|H
NET25 revision.
Default: F
Example
The following command defines inf as the logical volume to receive
alarms, and ASYNCXS will be interfacing with NET25 revision H.
def in al=inf x25=h
414
ASYNCXS
C320001300D0
Delete Map
The Delete Map command removes an entry from the PADmap table. The
NUA, CUD, and Port parameters must match the corresponding
parameters of the Add Map command that created the entry. If there are
two or more identical PADmap entries, the Delete Map command deletes
the first one in the table.
To delete all entries in a PADmap table, use the Erase Map command.
Syntax
DELete MAP NUA=<called_nua> [CUD=<call_user_data>]
PORt=<port>
Parameters
NUA=<called_nua>
Called NUA; must match the called NUA field of the map entry.
Range:
115 digits
Call user data; must match the CUD field of the map entry.
Range:
112 characters
PORt=<port>
Port number; must match the port field of the map entry.
Range:
*, #, #n, or mmmnnn, in the range 0479
Example
The following command deletes the PADmap entry that specified NUA
9999404%%%, call user data P%%, and port #.
delete map nua=9999404%%% cud=P%% port=#
ASYNCXS
C320001300D0
415
Destroy Device|Directory|Profile
The Destroy command destroys a device, an empty directory, or a profile.
When a device is destroyed, the port is deallocated. Active devices must
be disabled (Disable Device command) before they can be destroyed.
Destroying a device also cancels the devices registration for incoming
calls. To ensure an orderly shutdown before ASYNCXS stops execution,
all devices enabled by ASYNCXS should be destroyed before destroying
the ASYNCXS task.
When a profile is destroyed, the named profile specification is destroyed.
Syntax
DEStroy PRofile|DEvice|DIrectory <prof_dev_dir/>
Parameter
<prof_dev_dir/>
Profile, device, or empty directory name.
Range:
Defined profile, device, and directory names.
Examples
The following command destroys the device named d14.
destroy device d14
The following command destroys the profile named host.

destroy profile host
The following command destroys the empty directory named device.

destroy dir device/
416
ASYNCXS
C320001300D0
Disable Device
The Disable Device command disables a device and signs it off from the
PAD. If a call is active to the device, it is cleared. The device can only be
reenabled by a subsequent Enable Device command, i.e., the device will
not automatically be reenabled if P81=8.
Syntax
DISable[,Verify] DEvice <device_name>
Modifier and Parameter
Verify
completes.
<device_name>
Device name.
Range:
Defined device names; wildcard characters are allowed
Examples
The following command disables the device term1 and sends a
verification message to the terminal.
disable,verify device term1
The following command disables all devices in the current directory.

dis de *
ASYNCXS
C320001300D0
417
Enable Device
The Enable Device command sets the status of a device so that it can be
signed on. When a device is enabled, ASYNCXS begins any signon
procedures defined for the device.
Several X.3 parameters, such as P80, determine which signon conditions
must be met before a device is ready to receive incoming calls. For
example, if P80 instructs the PAD to wait for input from the device, the
device cannot receive incoming calls until that input is supplied. In this
case, the device cannot accept incoming calls even though it is enabled.
Syntax
ENable[,Verify] DEvice <device_name>
Verify
completes.
<device_name>
Device name.
Range:
Examples
The following command enables the device named term1.
en dev term1
The following command enables all devices for signon in the current
directory, and sends verification messages to the terminal.
enable,verify de *
Erase Map
The Erase Map command deletes all entries from the PADmap table. To
delete an individual PADmap table entry, use the Delete Map command.
Syntax
ERase MAP
418
ASYNCXS
C320001300D0
Modify Device
The Modify Device command changes one or more parameters for an
asynchronous device connected to the PAD. The device must have been
created previously with a Create Device command. At least one parameter
must be specified on the Modify Device command line. The device must
be disabled (Disable Device command) before the Modify Device
command is allowed.
Note that changes to any X.3 parameters affect the initial X.3 profile, not
the current X.3 profile associated with the device.
The MAxsymbols parameter cannot be changed in a Modify Device
command. If it must be changed, destroy the device and create a new one.
Modem subparameters should not be modified separately.
Syntax
MODify DEvice <dev_dir>/<dev_name> [<opt_parameters>]
Parameters
<dev_dir>/<dev_name>
Device directory name followed by a slash and the device name.
Range:
116 characters <dev_dir>; 116 characters <dev_name>
<opt_parameters>
Described below:
Range:
or 120 characters
ACCType=<acctype>
Range:
0255
BILling=<billing>
Range:
132 digits
ASYNCXS
C320001300D0
419

Range:
NOBLOCK |
NOBREAK
specified string.
Range:
BREAKString=< or 190 characters> |
NOBREAK
X.3 P81 must equal 2 or a sum including 2, and the device must
have a valid called address.
Range:
0500 seconds
Called NUA (the default destination address for an X.28 Call
command). This value is used when the called address is omitted
or when autocall is enabled (P81=2 or a sum including 2). If this
called address.
Range:
or 115 digits
Calling NUA. This must be specified for a device to be notified by
the PAD of an incoming call. The previous calling address is
deregistered and the new address is registered when the device is
enabled.
Range:
or 115 digits

NUA parameter; this value is used as the destination address.
420
ASYNCXS
C320001300D0
command.
command.
command.
CHArge=<charge>
Range:
0255
Timeout value when the device enters X.28 command mode. When
the timer expires, ASYNCXS places the device in data transfer
Range:
0500 seconds
identifier.
Range:
1124 characters
Range:
126 characters
[NO]DTRCall
When DTRCall is specified, the PAD raises DTR when an X.25
call is established (that is, prior to the X.28 incoming call PAD
service signal), and lowers DTR when an X.25 call is cleared (that
is, after the clear confirmation PAD service signal).
X.28 or X.29 commands, DTRCall overrides it.
should be based on the speed of the device and the device response
to a flow control signal.
Range:
ASYNCXS
C320001300D0
032767
421

CONnected create the device and enable it (without an Enable
Device command). If OFFline is specified, no checking is done to
see if the port is scanned or if another task is using it.
INTdata=<intdata>
Single data byte to be sent with the X.29 Interrupt command if no
byte is specified in the command.
Range:
0255 ($00$ff)
device signs on to the PAD (if X.3 P80:4). Do not precede the file
name with the tm: identifier.
Range:
or 187 characters
by commas. Do not modify subparameters separately.
OPM=PAD | HANdler
Changes the device to either PAD or handler operating mode.
PADchar=<padchar>
Padding data transmitted to the device. The values of P9, P14, and
P27 determine padding.
Range:
0255 ($00$ff)
Range:
See Chapter 3
PROFile=<profile>
Range:
116 characters
PROMpt=<prompt>
the display of the prompt.
Range:
422
ASYNCXS
C320001300D0
value indicates no retry limit. The RETRYTime parameter
specifies the interval between retries.
Range:
0127
retries.
Range:
6600 seconds
Range:
or 187 characters
Name of file containing X.28 commands to be executed when a
tm: identifier.
Range:
or 187 characters

Used with Telematics accounting. The device connection: dial up
SPeed=50 | 75 | 110 | 134 | 150 | 300 | 600 | 1200 | 1800 | 2000 | 2400 |
3600 | 4800 | 7200 | 9600 | 19200 | AUTObaud
Bit rate of device accessing the PAD. This parameter has the same
effect as X.3 P11. Conversely, setting P11 causes this parameter to
be assigned that value.
STOPbits=1 | 2
Range:
ASYNCXS
C320001300D0
12032767
423
Range:
0500 minutes
Range:
065535 bytes
Range:
065535 bytes
Name of X.25 volume to be associated with the device. This
allows you to associate different revisions of NET25 with devices.
Range:

be a colon)
Example
The following command modifies the device named printer1, which is in
the device directory named printdevs. The interval for outgoing break
signals is changed to 200 milliseconds, and the data transfer mode idle
timer is changed to 180 seconds.
modify device printdevs/printer1 breakt=200 datat=180
424
ASYNCXS
C320001300D0
Modify Initial
The Modify Initial command changes the logical volume name to receive
handler alarms. Note that you can identify a NET25 revision interface
compatibility with the Define Initial command, but you cannot change it
with a Modify Initial command.
Syntax
MODify INitial [ALarmvol=<alarm_vol>]
Parameter
Default: none; no alarms handler
Example
The following command changes the alarm volume to inf1.
mod in al=inf1
ASYNCXS
C320001300D0
425
Modify Profile
The Modify Profile command changes one or more X.3 parameters in an
existing profile. Only the specified parameters are changed.
Syntax
MODify PRofile <prof_dir>/<prof_name>
[PARameters=(<number>:<value>,...)]
Parameters
<prof_dir>/<prof_name>
Profile directory name followed by a slash and a profile name.
Range:
Defined profile directory and profile names
PARameters=(<number>:<value>,...)
Range:
See Chapter 3
Example
The following command changes parameter 81 to a value of 88 for the
profile prof3, which is in the profile directory named profile. With
P81=88, all devices using this profile are automatically reenabled if they
become disabled. The symbolic replacement function is enabled and the
profile is reset when a call is cleared to the values it had when the call was
initiated.
modify profile profile/prof3 par=(81:88)
426
ASYNCXS
C320001300D0
Reset Statistics
The Reset Statistics command clears one or more devices statistics.
Syntax
RESet[,Verify] STAtistics <device_name>
Verify
completes.
<device_name>
Device name.
Range:
Example
The following command resets the statistics to zero for the device named
printer1.
reset statistics printer1
ASYNCXS
C320001300D0
427
Set Defaults Devices

The Set Defaults Devices command defines default device parameters.
Default parameter values are used in the Create Device command unless
they are specifically changed.
Syntax
SEt DEFaults DEvices [<optional_parameters>]
Parameters
<optional_parameters>
Described below:
Range:
or 120 characters
Default: Null
ACCType=<acctype>
Range:
0255
Default: 0
BILling=<billing>
Range:
132 digits
Default: 0
Range:
NOBLOCK |
Default: BLOCK=(BUFsize=80,ELEments=10,FBTimer=0)
428
ASYNCXS
C320001300D0
NOBREAK
specified string.
Range:
BREAKString=< or 190 characters> |
NOBREAK
Default: BREAKTime=500
P81 must equal 2 or a sum including 2, and the device must have a
valid called address.
Range:
0500 seconds
Default: 60 seconds
Called NUA (the default destination address for an X.28 Call
command). This value is used when the called address is omitted
or when autocall is enabled (P81=2 or a sum including 2). If this
called address.
Range:
or 115 digits
Default:
Calling NUA. Must be specified for a device to be notified by the
PAD of an incoming call.
Range:
or 115 digits
Default:
NUA parameter; this value is used as the destination address.
command.
ASYNCXS
C320001300D0
429
command.
command.
Default: NORmal
CHArge=<charge>
Range:
0255
Default: 1
Timeout value when a device enters X.28 command mode. When
the timer expires, ASYNCXS places the device in data transfer
Range:
0500 seconds
Default: 180 seconds

identifier.
Range:
1124 characters
Default:
Range:
126 characters
Default:
[NO]DTRCall
DTRCall indicates the PAD raises DTR when an X.25 call is
established (that is, prior to the X.28 incoming call PAD service
signal), and lowers DTR when an X.25 call is cleared (that is, after
the clear confirmation PAD service signal).
X.28 or X.29 commands, DTRCall overrides it.
Default: NODTRCall
430
ASYNCXS
C320001300D0
should be based on the speed of the device and the device response
to a flow control signal.
Range:
032767
Default: 10
CONnected create the device and enable it (without an Enable
Device command). If OFFline is specified, no checking is done to
see if the port is scanned or if another task is using it.
Default: CONnected
INTdata=<intdata>
Single data byte to be sent with the X.29 Interrupt command if no
byte is specified in the command.
Range:
0255 ($00$ff)
Default: 0
device signs on to the PAD. Do not precede the file name with the
tm: identifier.
Range:
or 187 characters
Default:
MAxsymbols=<maxsymbols>
Maximum number of symbols that can be defined for a device
with the Symbol Assignment command.
Range:
0256
Default: 10
by commas.
ASYNCXS
C320001300D0
431
If you specify only a single subparameter, the other subparameters

change to their hardcoded default values (shown below). Since
this may not be desirable, you should explicitly specify all
subparameter values.
Default: (NOMODem,DTR,NOHANgup,NOAUToanswer)
OPM=PAD | HANdler
Creates the device in either PAD or handler operating mode.
Default: PAD
PADchar=<padchar>
Padding data transmitted to the device. The values of P9, P14, and
P27 determine padding.
Range:
0255 ($00$ff)
Default: 0
X.3 parameter values. Note that values are not checked for validity
when specified in this command.
Range:
See Chapter 3
Default: See Chapter 3

PROFile=<profile>
Range:
116 characters
Default:
PROMpt=<prompt>
the display of the prompt.
Range:
Default: Service:
value indicates no retry limit. The RETRYTime specifies the
interval between retries.
Range:
0127
Default: 0
432
ASYNCXS
C320001300D0
retries.
Range:
6600 seconds
Default: 6 seconds
Default: YES
Range:
or 187 characters
Default:
Name of file containing X.28 commands to be executed when a
tm: identifier.
Range:
or 187 characters
Default:
Used with Telematics accounting. The device connection: dial up
Default: DIAL
SPeed=50 | 75 | 110 | 134 | 150 | 300 | 600 | 1200 | 1800 | 2000 | 2400 |
3600 | 4800 | 7200 | 9600 | 19200 | AUTObaud
Bit rate of the device accessing the PAD. This parameter has the
same effect as X.3 P11. Conversely, setting P11 causes this
parameter to be assigned the specified value.
Default: AUTObaud
ASYNCXS
C320001300D0
433
STOPbits=1 | 2
Default: 1
Range:
12032767
Default: 160
Range:
0500 minutes
Default: 20 minutes
Range:
065535 bytes
Default: 0
Range:
065535 bytes
Default: 0
Name of X.25 volume to be associated with a device. This allows
you to associate different revisions of NET25 with devices.
Range:

be a colon)
Default: X25:
434
ASYNCXS
C320001300D0
Default: TELEmatics
Default: TELEmatics
Example
The following command sets default values for subsequent Create Device
commands in which the corresponding parameters are omitted. The
remote signon message include file is named mh:apadsign. The initial
state of the device is disabled. When a device is in command mode and a
60 second timeout value is reached, the device is placed into data transfer
mode if a call is active, and disabled if no call is active. The values
assigned to the X.3 parameters are described following the example.
set def dev rsignon=mh:apadsign instate=disabled cmdti=60~
par=(1:0,5:0,15:1,16:8,17:24,18:18,11:14,21:0,80:5,82:0)
P1 disables switching from data transfer mode to command mode when a

call is active. P5 disables flow control of the device in data transfer mode.
P15 enables editing when in data transfer mode. P16 defines the
backspace (CtrlH) character as the character delete character. P17 defines
the CtrlX character as the line delete character. P18 defines the CtrlR
character as the line display character. P11 sets the baud rate to 9600. P21
sets 8 bits no parity. P80 ensures that the PAD will wait for device input
before signing on to the device and run the signon include file. P82
indicates there is no alternate break character.
ASYNCXS
C320001300D0
435
Set Defaults Initial

The Set Defaults Initial command identifies a new default logical volume
name to receive handler alarms and/or the NET25 interface compatibility
revision.
Syntax
SEt DEFaults INitial [ALarmvol=<alarm_vol>] [X25revision=F|G|H]
Parameters
Default: none, i.e., no alarms handler
X25revision=F|G|H
NET25 revision.
Default: F
Example
The following command sets the default NET25 interface compatibility
revision to H.
set def in x25=h
436
ASYNCXS
C320001300D0
Set Defaults Profiles

The Set Defaults Profiles command defines default X.3 parameters.
Default parameter values are used in the Create Profile command unless
they are specifically changed.
Syntax
SEt DEFaults PRofiles [PARameters=(<number>:<value>,...)]
Parameters
PARameters=(<number>:<value>)
X.3 parameter numbers and values.
Range: See Chapter 3
Default: See Chapter 3
Example
The following command sets default values for subsequent Create Profile
commands in which the corresponding parameters are omitted. The values
assigned to the X.3 parameters are described following the example.
set def profile ~
par=(1:0,5:0,15:1,16:8,17:24,18:18,11:14,21:0,80:5,82:0)
P1 disables switching from data transfer mode to command mode when a

call is active. P5 disables flow control of the device in data transfer mode.
P15 enables editing when in data transfer mode. P16 defines the
backspace (CtrlH) character as the character delete character. P17 defines
the CtrlX character as the line delete character. P18 defines the CtrlR
character as the line display character. P11 sets the baud rate to 9600. P21
sets 8 bits no parity. P80 ensures that the PAD will wait for device input
before signing onto the device and run the signon include file. P82
indicates there is no alternate break character.
ASYNCXS
C320001300D0
437
Show Defaults Devices

The Show Defaults Devices command displays the default device
parameter values.
Syntax
SHow DEFaults DEvices
Example
The following command displays the current device defaults. Note that
some values have been changed with a Set Defaults Devices command.
sh def de
ASYNCXS Device Defaults
Initial State[INState]
Auto call nua [CALLEd]
Local nua
[CALLIng]
Operating mode
[OPM]
= ONLine
=
= 666690010015
= PAD
Maximum Symbols
[MA]
PAD character
[PAD]
Interrupt Data
[INT]
Call retry cnt[RETRYC]
Call method
[CALLM]
Typeahead size
[TYP]
Stop bits
[STOP]
X.25 IO/WRITE [X25IOW]
Break time
[BREAKT]
=
=
=
=
=
=
=
=
=
20
00
?($00)
3
NORmal
512
1
0
250
Speed [SPeed] = 9600

X3Type
[X3T] = TELEmatics
X28Type [X28] = TELEmatics
Auto connect delay

CMD mode disconnect
X25 idle timer
Call retry time
X.25 volume name
Flow control level
Reverse charging
X.25 IO/READ
[CALLDE]
[CMDTI]
[X25IDLET]
[RETRYT]
[X25]
[FCL]
[REV]
[X25IOR]
=
=
=
=
=
=
=
=
10
0
20
6
x25:
10
yes
0
Block Input
[BLOCK] = NOBLOCK
Modem options [MOdem] = (NOMODem,DTR,NOHANgup,NOAUToanswer)
DTR control [DTRCall]
NODTRCall
Account Type
[ACCT]
Charge Indicator
[CHArge]
Configured Account Number [ACCN]
Configured Billing Number [BIL]
International X.3 Parameters
0:0
1:1
2:1
3:2
8:0
9:0
10:80 11:14
16:127
17:0
18:0
19:2
National X.3 Parameters
23:0 24:0 25:0 26:0
31:0
80:1 81:24 82:0 83:0
= 0
= 1
=
= 0
4:0
5:2
12:1 13:1
20:0 21:0
27:0
28:0
29:0
84:0
85:0
86:0
X.28 Command prompt

[PROMpt]
Profile Directory
[DIRectory]
Default Profile
[PROFile]
Local X.28 Signon File
[LSignon]
Remote X.28 Signon File
[RSIGNON]
Remote X.28 Signoff File [RSIGNOFf]
438
Service Type
6:5
14:0
22:0
[SERvice] = 2
7:2
15:1
30:0
= AsyncXS:
= asyncxs:profile/
=
=
=
=
ASYNCXS
C320001300D0
Show Defaults Initial

The Show Defaults Initial command displays the current default logical
volume related options.
Syntax
SHow DEFaults INitial
Example
sh def in
ASYNCXS Defaults Initial Options
ALarmvol = inf
X25revision = H
The default alarm volume is inf and the NET25 compatibility interface
revision H is specified.
Show Defaults Profiles

The Show Defaults Profiles command displays the default X.3 profile
parameter values.
Syntax
SHow DEFaults PRofiles
Example
sh def pr
ASYNCXS Profile Defaults
0:0
1:1
2:1
3:2
8:0
9:0
10:80
11:14
16:127 17:0
18:0
19:2
4:0
12:1
20:0
5:2
13:1
21:0
6:5
14:0
22:0
7:2
15:1

23:0
24:0
25:0
31:0
80:1
81:24
82:0
26:0
27:0
28:0
29:0
30:0
83:0
84:0
85:0
86:0
ASYNCXS
C320001300D0
439
Show Device
The Show Device command displays either summary or detailed
information about an asynchronous device. Device operational states are
initially configured; during operations, the current state is reported in this
command. See Chapter 2 for a description of each state.
Syntax
SHow DEVice[,Full] [<dev>]
Full
Requests a detailed display. If specified, the <dev> parameter must
specify a single device.
<dev>
Device name.
Range:
Defined device names; wildcard characters are allowed only

if the Full modifier is not specified
Default: * (when the Full modifier is not specified)
Examples
The following command displays summary information about all devices
whose names begin with the letter d.
sh dev d*
ASYNCXS Device Summary for d/* on <node_name>
Name
Type
State
d59
Device
Connect
Name
Type
State
The following command displays detailed information about the device

named d59.
sh,f dev device/d59
(see display on next page)
440
ASYNCXS
C320001300D0
ASYNCXS Device Configuration for device/d59 (59) on <node_name>

Initial State[INState]
Auto call nua [CALLEd]
Local nua
[CALLIng]
Operating mode
[OPM]
= ONLine
=
= 999910210059
= PAD
Maximum Symbols
[MA]
PAD character
[PAD]
Interrupt Data
[INT]
Call retry cnt[RETRYC]
Call method
[CALLM]
Typeahead size
[TYP]
Stop bits
[STOP]
X.25 IO/WRITE [X25IOW]
Break time
[BREAKT]
=
=
=
=
=
=
=
=
=
20
00
?($00)
0
NORmal
512
1
2500
200
Speed [SPeed] = 9600

X3Type
[X3T] = TELEmatics
X28Type [X28] = TELEmatics
Auto connect delay

CMD mode disconnect
X25 idle timer
Call retry time
X.25 volume name
Flow control level
Reverse charging
X.25 IO/READ
[CALLDE]
[CMDTI]
[X25IDLET]
[RETRYT]
[X25]
[FCL]
[REV]
[X25IOR]
=
=
=
=
=
=
=
=
10
0
0
10
x25:
488
yes
2500
Block Input
[BLOCK] = NOBLOCK
Modem options [MOdem] = (NOMODem,DTR,NOHANgup,NOAUToanswer)
DTR control [DTRCall] = NODTRCall
Account Type
[ACCT]
Charge Indicator
[CHArge]
Configured Account Number [ACCN]
Current Account Number
Configured Billing Number [BIL]
Current Billing Number
0:0
1:1
2:1
3:2
8:0
9:0
10:0
11:14
16:127
17:0
18:0
19:2
23:0 24:0 25:0 26:0
31:0
80:4 81:88 82:0 83:0
=
=
=
=
=
=
0 Service Type
0
axstest
axstest
999960010031
999960010031
4:1
5:2
12:1 13:0
20:0 21:0
27:0
28:0
29:0
84:0
85:0
86:0
X.28 Command prompt

[PROMpt]
Profile Directory
[DIRectory]
Default Profile
[PROFile]
Local X.28 Signon File
[LSignon]
Remote X.28 Signon File
[RSIGNON]
Remote X.28 Signoff File [RSIGNOFf]
ASYNCXS
C320001300D0
6:29
14:0
22:0
[SERvice] = 2
7:2
15:1
30:0
= AsyncXS:
= asyncxs:profile/
= terminal
=
=
=
441
Show Directory
The Show Directory command displays the names of all profile or device
entries in an ASYNCXS directory that match the name or wildcard
string.
Syntax
SHow DIrectory [<dir/name>]
Parameter
<dir/name>
Directory name followed by a slash and the device or profile name.
Range: Defined directory names
Default: * (all directories)
Examples
The following command displays the names of all entries in the directory
named device with device as part of the name.
show dir device/device*
The following command displays the names of all directories.

sh dir
ASYNCXS Directory Summary for * on <node_name>

Name
d
Type
State
Device
Name
p
Type
State
Profile
This display shows two directories: one device directory named d and one
profile directory named p (note that the State column is not used when the
command is issued without a parameter). The following commands
display the contents of each of these directories (only device directories
have State column entries; profile directories do not).
sh dir d/
ASYNCXS Directory Summary for d/* on <node_name>

Name
d30
442
Type
State
Device
Connect
Name
Type
State
ASYNCXS
C320001300D0
sh dir p/
ASYNCXS Directory Summary for p/* on <node_name>
Name
Type
State
Name
Type
State
90
ASYNCXS
C320001300D0
Profile
443
Show Initial
The Show Initial command displays the current logical volume options.
Syntax
SHow INitial
Example
sh in
ASYNCXS Initial Options
ALarmvol = inf
X25revision = H
The current alarm volume is inf and revision H is the NET25 interface
compatibility revision.
Show Map
The Show Map command displays all entries in the ASYNCXS PADmap
table.
Syntax
SHow MAP
Example
The following command displays the PADmap table entries.
sh map
ASYNCXS Map Table on <node_name>
NUA
666650010015
CUD
abc
Port
1 10
This PADmap table contains one entry for NUA 666650010015. The call
user data (CUD) of an incoming call is abc. Incoming calls are routed to
port numbers 110.
444
ASYNCXS
C320001300D0
Show Profile
The Show Profile command displays summary or detailed information
about X.3 profiles.
Syntax
SHow PRofile[,Full] [<prof>]
Full
Requests a detailed display. If specified, the <prof> parameter must
specify a single profile.
<prof>
Profile name.
Range:
Defined profile names; wildcard characters are allowed only

if the Full modifier is not specified
Default: * (when the Full modifier is not specified)
Examples
The following command displays detailed information about the profile
named p/90.
sh,f pro p/90
ASYNCXS Profile Configuration for p/90 on <node_name>

International X.3
0:0
1:1
8:0
9:0
16:127
17:0
Parameters
2:1
3:2
10:0
11:14
18:0
19:2

23:0 24:0 25:0 26:0
31:0
80:0 81:24 82:0 83:0
4:0
5:0
12:1 13:1
20:0 21:0
27:0
28:0
29:0
84:0
85:0
86:0
6:5
14:0
22:0
7:2
15:1
30:0
The following command displays summary information about the profile

named p/90.
sh pro p/90
ASYNCXS Profile Summary for p/90 on <node_name>

Name
Type
90
Profile
ASYNCXS
C320001300D0
State
Name
Type
State
445
Show Statistics
The Show Statistics command displays either summary or detailed device
statistics. Each counter shown in a detailed display rolls over to zero after
exceeding a value of 2321.
Syntax
SHow[,Full] STAtistics [<device_name>]
Full
Requests a detailed display. If specified, the <device_name> parameter
must specify a single device.
<device_name>
Device name.
Range:
Defined device names; wildcard characters are allowed if the

Full modifier is not specified
Default: * (if Full modifier is not specified)
Examples
The following command displays summary statistics for the device named
device/d59.
sh sta device/d59
ASYNCXS Device Statistics for device/d59 on <node_name>
Device
State
Local NUA
Remote NUA/PVCLCN
d59
Connect
999910210059
calling
999960010031
The following command displays detailed statistics for device device/d59.

sh,f sta device/d59
ASYNCXS Device Statistics for device/d59 on <node_name>

Device d59
Call active time:
Local NUA 999910210059
Calls issued:
Async characters written:
X.25 writes issued:
X.25 resets issued:
X.25 interrupts issued:
Async framing errors:
Async overflow errors:
446
00:10
calling
1
327
1
0
0
0
0
State: Online
Remote NUA/PVCLCN 999960010031
Calls received:
0
Async characters read:
62
X.25 reads issued:
1
X.25 resets received:
0
X.25 interrupts received: 0
Async parity errors:
0
Async breaks detected:
0
ASYNCXS
C320001300D0
5 X.28 Commands
This chapter describes the X.28 commands. The X.28 command language
implemented by Telematics conforms to standards in the CCITT 1984
Recommendation for communication between a terminal and a PAD.
Telematics also provides extended functionality for handling data transfers
in special ways.
X.28 Command Syntax

The syntax of X.28 commands is: <command>[?] [<parameter>,...]. The
<command> element identifies a command name and is required. Each
command name comprises a string of alphabetic characters; lowercase and
uppercase characters can be used interchangeably. The name cannot
contain embedded blanks, but can be preceded or followed by any number
of blanks.
The ? is an optional or mandatory element, depending on the command
name. The [<parameter>] element identifies a command parameter, such
as a value for an X.3 parameter setting. There must be at least one space
between the <command> (or ?, if present) and the first parameter, unless
the command is completely spelled out (not abbreviated).
Commands cannot exceed 128 characters.
Command terminator A command must end with a <CR> or a +
character, which causes the PAD to accept the preceding characters as a
single command. The <CR> and + are not considered part of the
command. (You can disable the + and/or <CR> as a command terminator
using X.3 P81 values; see Chapter 3.)
Comment character The exclamation point (!) can be used as a comment
character. When this character occurs on a line, any information following
it to the end of the input line is not evaluated.
Editing Editing characters can be entered at any time before the
command terminator to edit the command line. Any other control
characters are ignored, and do not count toward the 128 character
command length limit.
PAD service signals Each command description includes the responses
expected from the PAD. Responses that are specific to each command are
described under that commands section. Responses that can be returned
by several commands are given specific signal names, and are described in
Chapter 6.
ASYNCXS
C320001300D0
51
X.28 COMMANDS
Wildcard characters The Aread and Read commands establish pattern

strings that are compared with input strings from a device. Both
commands allow wildcard characters in the pattern strings. These
characters allow pattern strings to be defined that can match a number of
input strings, not just a specific input string. The wildcard characters are
% and *.
The percent sign (%) is the single character wildcard character; it
represents any single character. For example, the pattern string abc%%
will match the following input strings: abc01, abcde, abcxx, abcaa, but
not abcdef or abc.
The asterisk (*) is the multiple character wildcard character; it represents
any number of characters, including none. For example, the pattern string
abc* will match the following input strings: abc, abc01, abcd, abcxx,
abcoulomb, and any other string that begins with abc.
Pattern strings containing wildcard characters must be enclosed in
quotation marks () when specified on a command line. For example,
PATTERN=abc%
associates the string abc% with the PATTERN keyword; the string is
enclosed in quotation marks.
String format conventions Certain X.28 commands allow you to specify
a string of characters to be sent to a device. The Message and Type
commands send strings to a local device; the Send command sends a
string to a remote device.
A string is one or more ASCII characters (alphanumeric and
nonalphanumeric). Nonalphanumeric characters are any characters
other than AZ, az and 09.
Spaces are substring delimiters within a string. Spaces can be used within
a string to improve command line readability; however, the spaces are
removed from the final output unless the entire string is enclosed in
quotation marks.
A control character can be included in a string by using the expression:
CHR(<value>). The value must be enclosed in parenthesis and is the
decimal value of the control character. For example, the command
MES Here comes a line feed CHR(10). There it was.
produces the output

Herecomesalinefeed
.Thereitwas.
In this example, the words are considered substrings separated by spaces;

the spaces are removed when the substrings are concatenated. To preserve
interword spacing, the following command
MES Here comes a line feed CHR(10). There it was.
52
ASYNCXS
C320001300D0
X.28 COMMANDS
produces the output

Here comes a line feed
. There it was.
X.28 Command Summary

The following list briefly describes the X.28 commands. An asterisk
denotes a standard X.28 PAD command signal. In several cases,
Telematics also offers alternate syntax for the standard command signals;
this is shown with the individual commands syntax later in this chapter.
Telematics also offers additional nonstandard commands.
AREAD . . . . . . . . . . . . Reads a value from a device and optionally
assigns it to a symbol if it matches a pattern
string
C . . . . . . . . . . . . . . . . . . Establishes a virtual connection through the
PAD to another device on the X.25 network
CALL . . . . . . . . . . . . . . Retries the most recent outgoing call
CLR * . . . . . . . . . . . . . . Terminates an existing call
CONNect . . . . . . . . . . . Establishes a connection to a Permanent Virtual
Circuit (PVC)
COntinue . . . . . . . . . . . Switches a terminal from command mode to
data transfer mode
COPy . . . . . . . . . . . . . . Transmits data received from the network to
another network device
COPYClr . . . . . . . . . . . Stops the effect of a Copy command
Help . . . . . . . . . . . . . . . Displays information about PAD facilities
INClude . . . . . . . . . . . . Executes a file containing X.28 commands
INTerrupt * . . . . . . . . . . Sends an X.25 interrupt packet to a remote
device
INTD . . . . . . . . . . . . . . Sends an X.25 interrupt packet; sends an
indication of break to a remote device; discards
further data from the remote device until P8 is
reset to 0
ICLR * . . . . . . . . . . . . . Sends an invitation to clear request to a remote
device
LANGuage . . . . . . . . . . Sets X.3 parameter P6 service signal format or
language
MESsage . . . . . . . . . . . Sends a character string to a terminal as a PAD
service signal
NPar . . . . . . . . . . . . . . . Changes the parity of data transmitted through
the network
PAR? * . . . . . . . . . . . . . Displays the current profiles X.3 parameter
values
ASYNCXS
C320001300D0
53
X.28 COMMANDS
PROF * . . . . . . . . . . . . . Changes a terminals profile

PROFile? . . . . . . . . . . . Displays profile names or X.3 parameter values
for a specified profile
REAd . . . . . . . . . . . . . . Reads a value from a remote device into a
symbol
RPAr? * . . . . . . . . . . . . Displays a remote devices X.3 parameter
values
RPROf . . . . . . . . . . . . . Replaces a remote devices profile with a local
profile
RSEt . . . . . . . . . . . . . . . Changes a remote devices X.3 parameter values
RESet * . . . . . . . . . . . . Resets a virtual circuit to its initial state
SENd . . . . . . . . . . . . . . Sends data to a remote device in command
mode
SET * . . . . . . . . . . . . . . Specifies new X.3 parameter values
STAtus * . . . . . . . . . . . . Displays the current calls status
TACT . . . . . . . . . . . . . . Initiates a port test
TACTT . . . . . . . . . . . . . Initiates a terminal test
TERMinate . . . . . . . . . . Disconnects a terminal from the PAD
TYpe . . . . . . . . . . . . . . . Displays a character string
WAIT . . . . . . . . . . . . . . Instructs the PAD to pause before reading the
next command
X28Type . . . . . . . . . . . . Indicates if the device can use extended X.28
commands
X3Type . . . . . . . . . . . . . Indicates if the device can display/set extended
X.3 parameters
54
ASYNCXS
C320001300D0
X.28 COMMANDS
Aread
The Aread command reads a string of data from the device, compares it to
a pattern string, and optionally assigns the matched string to a symbol.
The input string from the device is compared to the specified pattern
string. If the input string does not match the pattern string, the PAD
discards the input string and reads another string from the device. If the
PAD does not receive a matching string within a specified time interval, or
if no input string is received from the device within the time interval, the
PAD disables the device. If no timer value is specified, the PAD continues
to read from the device until the pattern string is matched. Only when the
pattern is matched will another X.28 command be accepted.
This command is used primarily in the signon include file, requiring the
terminal user to enter a valid password before continuing the session. If
the user does not enter a valid password within the timeout period, the
terminal is disabled. Once a correct password has been entered, it can be
assigned to a symbol. Subsequent commands in the signon file can use the
symbol to invoke subsidiary include files whose names depend on the
password.
If a break is entered by the device that initiated the Aread command, the
command terminates.
Syntax
AREAD[,TIMer=<timeout>][,PATtern=<pattern_string>] [<symbol>]
Parameters
<timeout>
Interval the PAD waits for an input string to be read.
Range: 0255 seconds
Default: 0 (no timeout)
<pattern_string>
Pattern string to be compared to each input string. See page 52 for
information about using wildcard characters.
Range:
116 characters; must be enclosed in quotes if it contains

nonalphanumeric or wildcard characters
Default: Null string (matches/accepts any string)
<symbol>
Name of symbol to which the matched string is assigned.
Range:
ASYNCXS
C320001300D0
116 characters
55
X.28 COMMANDS
Response
Acknowledge PAD service signal This is the PADs normal response, and
indicates it is awaiting input. If the input string matches the pattern
string, the PAD displays the X.28 command prompt. Otherwise, the
PAD issues another Acknowledge signal and waits for another input
string to be supplied.
Read request timeout No data was received from the terminal during the
specified time limit; the terminal has been disabled.
56
ASYNCXS
C320001300D0
X.28 COMMANDS
C (Call)
The C (Call) command establishes a virtual connection (an X.25 call)
from the local device through the PAD and the packet switching network
to a remote device. The terminal user can specify a subset of NUA call
facilities on a percall basis. If NUA call facilities are specified, they must
be followed by a dash, as shown in the syntax below.
The remote device can be a terminal or a host computer, and may or may
not be connected to the network via a remote PAD. To successfully place a
call, neither the local nor the remote device can have an active call.
If the terminal has been configured with a default called NUA, the NUA
may be omitted. In this case, the PAD tries to call the default called NUA.
If the terminal has no default called NUA, the NUA field must be
supplied.
If the terminal has been configured with default call user data, the call user
data field may be omitted. In this case, the PAD sends the default call user
data with the call request. If the terminal has no default call user data, and
the call user data field is omitted from the Call command, no data is sent
with the call request.
The M. RPOA, S, T, and U facilities are not supported.
Syntax
[C] [<nua_call_facilities>,...] [<NUA>] [*<call_user_data>]
Parameters
C
Command keyword. This is the only X.28 command in which the
command keyword can be omitted.
<nua_call_facilities>
Includes the following:
A
Activates Telematics accounting, and accounting information is
displayed when the call clears.
B<CUG_number>
Activates the Bilateral Call User Group call facility, and provides
the CUG number for the call.
Range:
099
D[(<rcv_cls>,<tm_cls>)]
D[[(]<thru_class>[)]]
Activates the Throughput Class negotiation call facility, and
requests a receive and/or transmit throughput class. If both the
receive and transmit throughput classes (<rcv_cls> and <trn_cls>)
ASYNCXS
C320001300D0
57
X.28 COMMANDS
are supplied, they can have different values. If only one value
(<thru_cls>) is supplied, it applies to both receive and transmit
throughput classes, and the parentheses are optional. If no value is
supplied with the D key letter, the default is used. If this
negotiation call facility is specified in the links definition, it
overrides the specification in this command.
Range:
75 | 150 | 300 | 600 | 1200 | 2400 | 4800 | 9600 | 19200 |

40000
Default: 75
F
Activates the Fast Select call facility. The PAD prompts the device
for Fast Select data, and up to 124 characters can be supplied to
accompany the call request packet (control sequences are treated as
single characters; leading spaces are deleted). Data exceeding 124
characters is truncated. If an incoming Fast Select call request is
received, the device is prompted for call user data, and up to 124
characters can be entered to accompany the call accept packet.
FR
Activates the Fast Select Restricted call facility. If no call user data
is supplied with the Call command, the PAD prompts the device
for it, and the device can supply up to 124 characters to
accompany the call request. The remote device responds with a
clear request; any accompanying clear user data is written to the
device prior to the clear service signal. If an incoming Fast Select
Restricted call request is received, the PAD prompts the device for
clear user data, and the device can supply up to 124 characters to
accompany the clear packet. The call is then immediately cleared.
G[(]<CUG_number>[)]
Activates the Closed User Group call facility, and provides the
CUG number for the call. The calling NUA of the local device and
the called NUA of the remote destination must both belong to the
specified CUG.
Range:
099
N[<network_user_id>]
Activates the Network User ID (NUI) call facility, and optionally
provides the NUI string. The NUI can be used for call validation
by the PAD. For security, you may not want to include the NUI in
the Call command where it is visible. There are two ways to avoid
this: disable PAD echoing by setting P2=0, or omit the string from
the Call command. In the latter case (if the N facility code supplied
but the NUI is omitted), the PAD prompts for the NUI before
initiating the call, and reads the string without echoing the input. In
either case, the string is assigned to the symbol NUI, which can be
used in subsequent include files for validation.
Range:
58
0124 characters; must be enclosed in quotation marks
ASYNCXS
C320001300D0
X.28 COMMANDS
Default: If NUI not specified on command line, prompted

O[(]<CUG_number>[)]
Activates the Closed User Group with Outgoing Access call
facility, and provides the CUG number for the call. The calling
NUA of the local device and the called NUA of the remote
destination must both belong to the specified CUG.
Range:
099
P[[(]<pkt_size>[)]]
P[(<rcv_pkt>,<trn_pkt>)]
Activates the Packet Size Negotiation call facility, and requests a
receive and/or transmit packet size. If both receive and transmit
packet sizes (<rcv_pkt> and <trn_pkt>) are supplied, they can have
different values; if only one value (<pkt_size>) is supplied, it
applies to both receive and transmit packet sizes, and the
parentheses are optional. If no value is supplied with the P key
letter, the default is used. If this negotiation call facility is specified
in the links definition, it overrides the specification in this
command.
Range:
16 | 32 | 64 | 128 | 256 | 512 | 1024
Default: 16
R
Activates the Reverse Charging call facility. The Local Charge
Prevention call facility option must not be subscribed for the NUA
associated with the device accepting the charges.
W[(<rcv_wnd>,<trn_wnd>)]
W[[(]<wnd_size>[)]]
Activates the Window Size Negotiation call facility, and requests a
receive and/or transmit window size. If both the receive and
transmit window sizes (<rcv_wnd> and <trn_wnd>) are supplied,
they can have different values. If only one value (<wnd_size>) is
supplied, it applies to both receive and transmit window sizes, and
the parentheses are optional. If no value is supplied with the W key
command.
Range:
1127
Default: 1
<NUA>
Network User Address of the destination device. For international
calls, the Data Network Identification Code (DNIC) must be included
in the destination address.
Range: 115 digits
Default: Configured called NUA
ASYNCXS
C320001300D0
59
X.28 COMMANDS
*<call_user_data>
Information field, preceded by an asterisk. Call user data can include
any character except an X.28 command terminator (<CR> or +).
Control characters can be sent in the call user data field with the
following limitations:
Control characters must be encoded; they cannot be entered
directly (e.g., ABC<C is ABC controlC, XYZ<D<C is XYZ
controlD controlC, ABC<< is ABC<).
If a control character is assigned a function (e.g., editing), the
function is performed. Normal control characters are discarded.
Input is not terminated if the call user data exceeds the maximum
allowable length (12 for normal calls; 124 for fast select calls).
Call user data in excess of the maximum is discarded; only the
valid portion is used to make a call.
Range: 012 characters; leading spaces are deleted
Default: Null
Response
Connected PAD service signal The call was established successfully.
The terminal is placed in data transfer mode.
Clear PAD service signal The call was not established or the terminal is
not configured to permit outgoing calls. The Clear signal includes an
error code indicating the reason for the failure.
ENGAGED A call is already active on this terminal.
Invalid facility request One of the call facilities parameters is not a legal
value. Reenter the entire command with the correct parameter.
Invalid call user data The call user data field is larger than 12 characters
and neither the Fast Select (F) nor the Fast Select Restricted (FR) call
facility was specified.
Invalid parameter The command parameters are not specified in the
correct order or one of the parameters is not a legal value. Reenter the
entire command with correct parameters.
510
ASYNCXS
C320001300D0
X.28 COMMANDS
Examples
Under different conditions the command name, optional call facilities,
NUA, and call user data can be omitted from the Call command. However,
at least one of these fields must be supplied, as shown in the following
examples:
Command
Description
C . . . . . . . . . Issues a call request to the default called NUA.

777720044 . Omits the command name and call user data.
*12345 . . . . Uses the default called NUA but supplies the call user data
string 12345.
f*smithj . . Places a call to the default called NUA, requesting the Fast
Select call facility, and sending the call user data string
smithj.
ASYNCXS
C320001300D0
511
X.28 COMMANDS
Call (Call Retry )

The Call (Call Retry) command instructs the PAD to reissue the most
recent C (Call) or Connect command. The previous command may have
been successful and the call subsequently cleared, or it may have been
unsuccessful. A Call command cannot be retried if the device received an
incoming call since the Call command was issued.
A C (Call) or Connect command that was not successful because of syntax
errors will not be retried by this command. Instead, if the device
previously issued a syntactically correct C (Call) or Connect command,
that command will be retried.
Syntax
CALL
Response
Connected PAD service signal The call was established successfully, and
the terminal is placed in data transfer mode.
Clear PAD service signal The call was not established or the terminal is
not configured to permit outgoing calls. The signal includes an error
code that indicates the reason for the failure.
ENGAGED A call is already active on this terminal.
No call to retry No valid Call or Connect command was previously
issued from this terminal.
512
ASYNCXS
C320001300D0
X.28 COMMANDS
Clr (Clear)
The Clr (Clear) command terminates an active call. Data en route to the
PAD from the remote device can be lost when using this command. An
orderly disconnection from the remote device should be followed (e.g.,
logging off a remote host application before clearing the call).
If the PAD detects an error, it sends a Clear message with an appropriate
error code; it does not change the mode of the terminal.
Syntax
CLR
CLear
(if X28Type=C84 | TELEmatics)

(if X28Type=TELEmatics)
Response
Clear PAD service signal The call was cleared. If an error occurred
while the clear was in progress, the signal includes details of the error. The
terminal is returned to command mode.
No active call This command can be executed only when a call is active.
ASYNCXS
C320001300D0
513
X.28 COMMANDS
Connect
The Connect command establishes a virtual connection from the local
device through the PAD to the packet switching network with a permanent
virtual circuit (PVC). You must supply a link name and logical channel
number to uniquely identify the PVC.
This command is analogous to a Call command, in that it sets up remote
communication; however, the Call command specifies a destination device
address and allows the network to determine the physical path through
which the call is connected. The Connect command specifies the address
of a network link to which the device is to be connected, a link for which
the physical path (PVC) is predefined when the network is configured.
The Connect command completes execution when the local device is
linked to the PVC. However, there may or may not be a device connected
to the remote end of the link; data exchanges can only proceed when a
remote device connects. Until this occurs, the network buffers any data
entered by the local device, up to the transmit window capacity.
A previous Connect command can be retried using a Call Retry command.
The link can be broken with a Clear command.
Syntax
CONNect <link_name><channel_number>
Parameters
<link_name>
Name of physical X.25 link to which the connection is requested,
followed by a hyphen.
Range:
116 characters
<channel_number>
Logical channel number specifying the PVC on the link.
Range:
14096
Response
Connected PAD service signal The PVC connection was established
successfully, and the terminal is placed in data transfer mode.
Clear PAD service signal The PVC connection was not established. The
signal includes an error code indicating the reason for the failure.
ENGAGED The terminal has already established a PVC connection or a
call is already active for this terminal.
Invalid parameter The command parameters are not specified in the
correct order, or one of the parameters is not a legal value. Reenter
the entire command with correct parameters.
514
ASYNCXS
C320001300D0
X.28 COMMANDS
Continue
The Continue command switches the terminal from command mode to
data transfer mode. This command is only valid when a call is active, and
cannot be issued from an include file.
Syntax
COntinue
Response
Acknowledge PAD service signal The terminal has been switched to data
transfer mode and is ready to accept input data.
The terminal cannot be set to data transfer mode.
Continue not valid from signon include file The Continue command can
only be entered directly from the device, not from an include file.
ASYNCXS
C320001300D0
515
X.28 COMMANDS
Copy
The Copy command initiates a second call associated with a local device
to a copy device. When the command has been entered, data received
from the network and written to the local device is also written, through
the network, to the copy device. Data received from the copy device is
ignored. The copy and local devices must be associated with different
PADs. This command is valid only when a call is active. The M, RPOA,
S, T, and U facilities are not supported.
The copy operation continues until one of the following conditions occurs:
The local device enters a Copy Clear command

The call is cleared
The copy call is cleared
The copy device sends an invitation to clear
Syntax
COPy [<nua_call_facilities>,...] [<NUA>] [*<call_user_data>]
Parameters
<nua_call_facilities>
Includes the following:
A
Activates Telematics accounting, and accounting information is
displayed when the call clears.
B<CUG_number>
Activates the Bilateral Call User Group call facility, and provides
the CUG number for the call.
Range:
099
D[(<rcv_cls>,<tm_cls>)]
D[[(]<thru_class>[)]]
Activates the Throughput Class negotiation call facility, and
requests a specific receive and/or transmit throughput class. If both
the receive and transmit throughput classes (<rcv_cls> and
<trn_cls>) are supplied, they can have different values. If only one
value (<thru_cls>) is supplied, it applies to both receive and
transmit throughput classes, and the parentheses are optional. If no
value is supplied with the D key letter, the default is used. If this
Range:
75 | 150 | 300 | 600 | 1200 | 2400 | 4800 | 9600 | 19200 |

40000
Default: 75
516
ASYNCXS
C320001300D0
X.28 COMMANDS
F
Activates the Fast Select call facility. The PAD prompts the device
for Fast Select data, and up to 124 characters can be supplied to
accompany the call request packet (control sequences are treated as
single characters; leading spaces are deleted). Data exceeding the
124 character limit is truncated. If an incoming Fast Select call
request is received, the device is prompted for call user data, and
up to 124 characters can be entered to accompany the call accept
packet.
FR
Activates the Fast Select Restricted call facility. If no call user data
is supplied with the Call command, the PAD prompts the device
for call user data, and the device can supply up to 124 characters to
accompany the call request. The remote device responds with a
clear request; any accompanying clear user data is written to the
device prior to the clear service signal. If an incoming Fast Select
Restricted call request is received, the PAD prompts the device for
clear user data, and the device can supply up to 124 characters to
accompany the clear packet. The call is then immediately cleared.
G[([<CUG_number>])]
Activates the Closed User Group call facility, and provides the
CUG number for the call. The calling NUA of the local device and
the called NUA of the remote destination must both belong to the
specified CUG.
Range:
099
N[<network_user_id>]
Activates the Network User ID (NUI) call facility, and optionally
provides the NUI string. The NUI can be used for call validation
by the PAD. For security, you may not want to include the network
ID string in the Call command where it is visible. There are two
ways to avoid this: disable PAD echoing by setting P2=0, or omit
the string from the Call command. In the latter case (if the N
facility code supplied but the NUI is omitted), the PAD prompts
for the NUI before initiating the call, and reads the string without
echoing the input. In either case, the string is assigned to the
symbol NUI, which can be used in subsequent include files for
validation.
Range:
0124 characters; must be enclosed in quotation marks
Default: If NUI not specified on command line, prompted

O[(]<CUG_number>[)]
Activates the Closed User Group with Outgoing Access call
facility, and provides the CUG number for the call. The calling
NUA of the local device and the called NUA of the remote
destination must both belong to the specified CUG.
Range:
ASYNCXS
C320001300D0
099
517
X.28 COMMANDS
P[(<rcv_pkt>,<trn_pkt>)]
P[[(]<pkt_size>[)]]
Activates the Packet Size Negotiation call facility, and requests a
specific receive and/or transmit packet size. If both the receive and
transmit packet sizes (<rcv_pkt> and <trn_pkt>) are supplied, they
can have different values; if only one value (<pkt_size>) is
supplied, it applies to both receive and transmit packet sizes, and
the parentheses are optional. If no value is supplied with the P key
command.
Range:
16 | 32 | 64 | 128 | 256 | 512 | 1024
Default: 16
R
Activates the Reverse Charging call facility. The Local Charge
Prevention call facility option must not be subscribed for the NUA
associated with the device accepting the charges.
W[(<rcv_wnd>,<trn_wnd>)]
W[[(]<wnd_size>[)]]
Activates the Window Size Negotiation call facility, and requests a
specific receive and/or transmit window size. If both the receive
and transmit window sizes (<rcv_wnd> and <trn_wnd>) are
supplied, they can have different values. If only one value
(<wnd_size>) is supplied, it applies to both receive and transmit
window sizes, and the parentheses are optional. If no value is
supplied with the W key letter, the default is used. If this
Range:
1127
Default: 1
<NUA>
Network user address of the copy device. If a previous Copy command
was entered, this field can be omitted and the PAD assumes the
<NUA> of the previous Copy command.
Default: Previous Copy command or indeterminate
*<call_user_data>
Information field, preceded by an asterisk. Call user data can include
any character except an X.28 command terminator (<CR> or +).
Control characters can be sent in the call user data field with the
following limitations:
Control characters must be encoded; they cannot be entered
directly (e.g., ABC<C is ABC controlC, XYZ<D<C is XYZ
controlD controlC, ABC<< is ABC<).
518
ASYNCXS
C320001300D0
X.28 COMMANDS
If a control character is assigned a function (e.g., editing), the

function is performed. Normal control characters are discarded.
Input is not terminated if the call user data exceeds the maximum
allowable length (12 for normal calls; 124 for fast select calls).
Call user data in excess of the maximum is discarded; only the
valid portion is used to make a call.
Range: 012 characters; must be preceded by an asterisk (*)
Default: Null
Response
Copy already active A copy call has already been established for the
specified device.
Copy initiated The copy call to the specified device is established.
No active call This command can be executed only when a call is active
on the local device.
ASYNCXS
C320001300D0
519
X.28 COMMANDS
Copyclr (Copy Clear)

The Copyclr (Copy Clear) command clears a call to a copy device. The
primary call between the local and the remote devices is not affected. This
command is valid only when a call is active and a Copy command is in
effect.
Syntax
COPYClr
Response
Copy cleared The copy call associated with the local device has been
cleared.
No copy active There was no active copy call associated with the local
device.
520
ASYNCXS
C320001300D0
X.28 COMMANDS
Help
The Help command displays information about the PADs facilities: X.3
and X.28 types, X.28 commands, X.3 parameters, defined symbols, or
available profiles. If no keyword is specified, the command displays a list
of keyword choices.
Syntax
Help [XTypes | X28cmds | X3parms | Mnemonics | Profiles | Help]
Parameters
XTypes
Available X28types and X3Types.
X28cmds
Available X.28 commands. Different displays are written depending
upon the devices X28type.
X3parms
Available X.3 parameters and their meanings. Different displays are
written depending upon the devices X3Type.
Mnemonics
Symbols defined for this device. The predefined symbols SWREV and
NUI are not displayed.
Profiles
X.3 profiles available to this device. For information about a specific
profile, enter: h profile<profile_name>. This display is the same as the
Profile Display command.
Help
Explains how to use help information.
ASYNCXS
C320001300D0
521
X.28 COMMANDS
Include
The Include command instructs the PAD to begin accepting X.28
commands from a named file rather than directly from the device. The file
can contain any X.28 command except Continue.
Include files can be nested up to four levels. If an include file contains
nested Include commands, the PAD accepts X.28 commands from the new
file as indicated. When it reaches the end of an include file, it resumes
accepting commands from the file at the previous level, starting with the
command following the nested Include command. When the PAD reaches
the end of the include file at the top level, it resumes accepting commands
from the terminal.
If an Include command fails from within an autosignon include file, the
call is cleared. If an Include command fails from within a signon include
file, the terminal is disabled.
Syntax
INClude <file_name>
@<file_name>
(if X28Type=C84 | TELEmatics)
Parameter
<file_name>
Name of include file to be read. Must conform to Telematics file
specifier rules. Do not precede the file name with the tm: modifier; it
is automatically supplied.
Range:
187 characters
Response
The first X.28 command in the Include file determines the PADs normal
response. Possible error signals are:
Attempt to nest too many include files A maximum of four levels of
include files are permitted.
Error opening include file, may not exist: <status> The PAD
couldnt open the named file. Status is the numeric return value from
the Telematics system indicating the reason for the failure, and is
usually:
5
Invalid file name
Include file not found The PAD couldnt locate the named file. Ensure
that the file name is specified correctly.
Unexpected end of line There were additional characters on the
command line after the <file_name> parameter.
522
ASYNCXS
C320001300D0
X.28 COMMANDS
Interrupt
The Interrupt command sends an X.25 interrupt packet, optionally
including user data, to a remote device. This command is valid only when
a call is active.
Default interrupt data can be predefined with the INTdata device
parameter. If INTdata is defined, it is sent when the <data> parameter is
omitted from the Interrupt command. If the <data> parameter is included
in the Interrupt command, it supersedes any default data. If no default data
is defined and the <data> parameter is omitted in this command, a value
of zero is sent in the interrupt data field.
Syntax
INTerrupt [<data>]
Parameter
<data>
Number sent as part of the packet.
Range: 0255
Default: Configured interrupt data
Response
Acknowledge signal This is the PADs normal response when the
interrupt packet has been sent.
A number in the range 0 to 255 was expected The value specified as
interrupt data is not within the legal range. Reenter the command
with a correct value.
ASYNCXS
C320001300D0
523
X.28 COMMANDS
Intd (Interrupt and Discard)

The Intd (Interrupt and Discard) command allows a local device to
temporarily stop a remote device from sending any more data to it. The
local PADs actions in response to this command are the same as when it
receives a break signal from the device and P7=21. This command can be
used when you dont want to use the break key for this function.
This command causes the following actions:
An X.25 interrupt packet is sent to the remote device with all bits of
An indication of break PAD message is sent to the remote device. The

local PAD sets P8=1 for its associated device and notifies the remote
PAD that P8 has been changed. Any data received from the network
for the local device is discarded.
The remote PAD notifies its associated device that it has received an
indication of break PAD message, and responds with PAD a message
that resets P8 for the local device. When P8 is reset to zero, normal
data transmission resumes.
Syntax
INTD
Response
interrupt packet has been sent.
524
ASYNCXS
C320001300D0
X.28 COMMANDS
Iclr (Invitation to Clear)

The Iclr (Invitation to Clear) command sends an X.29 invitation to clear
PAD message to a remote device. A call must be active to this device. The
PAD receiving the message does not clear the X.25 call until it has
transmitted any data intended for its associated device to that device.
Syntax
ICLR
Response
invitation to clear PAD message has been sent.
ASYNCXS
C320001300D0
525
X.28 COMMANDS
Language
The Language command sets X.3 parameter P6s value to indicate the
PAD service signal format or language.
Syntax
LANGuage ENGLISH | SPANISH | FRENCH | DEPENDENT |
DEFAULT
Parameter
ENGLISH
Sets extended dialogue mode handling and English language PAD
service signals (P6:21).
SPANISH
Sets extended dialogue mode handling and Spanish language PAD
FRENCH
Sets extended dialogue mode handling and French language PAD
DEPENDENT
Sets the extended network dependent format for PAD service signals
(P6:13).
DEFAULT
Sets the standard format (nonextended) for PAD service signals (P6:5).
Example
The following command sets X.3 P6 to English extended mode (i.e.,
P6:29).
lang english
526
ASYNCXS
C320001300D0
X.28 COMMANDS
Message
The Message command creates a PAD service signal and sends the text
string to the device. This command is normally issued from an include file
to inform the user of the command processing state. The service signal
display from the Message command depends on the P6 setting.
Syntax
MESsage <message>
Parameter
<message>
Character string. See page 52 for string format conventions.
Range:
080 characters; can have embedded spaces to improve

readability, but to retain the spaces during the output display,
enclose the entire string in quotation marks
Default: Null (no message sent)
Response
<string> The normal response from the Message command is the
message string itself, followed by an Acknowledge PAD service signal.
Syntax error Either the <string> is incorrectly formed or there are
additional characters on the command line after the end of the <string>.
ASYNCXS
C320001300D0
527
X.28 COMMANDS
Npar (Network Parity)

The Npar (Network Parity) command permits a device to change the
parity of data transmitted across the network. This command is used to
generate the correct parity only when a remote PAD requires different
parity treatment.
If this command is used to set network parity to other than 8 bits no parity,
the remote PAD will never get a match when it issues a Read command.
Syntax
NPAr S | M | E | O | N
Parameters
S
Space parity.
M
Mark parity.
E
Even parity.
O
Odd parity.
N
No parity; this is the default value.
Response
Acknowledge signal This is the PADs normal response.
Invalid network parity value The parameter specified for network parity
is not a legal value. Reenter the command with a correct network
parity value.
528
ASYNCXS
C320001300D0
X.28 COMMANDS
Parameter?
The Parameter? command displays the values of some or all the X.3
parameters in the devices current profile. Parameter numbers can be
specified in any order and are displayed in the order specified. If no
parameter number is specified, the PAD displays all parameter values in
ascending order.
Syntax
PAR?
PARameter? [<number>,...]
(if X28Type=C84)
Parameters
?
Required character, even when the command is abbreviated.
<number>
X.3 parameter number. Multiple numbers must be separated by
commas or spaces.
Range:
031 and 8086 if devices X.3Type=TELEMATICS;

122 if devices X.3Type=C84
Default: Null (causes all parameters to be displayed)
Response
No service signals are returned in response to a Parameter command.
Instead, the PAD responds with the string PAR, followed by the
parameters and their values in the form: <number>:<value>,...
If a parameter number is not within the valid range of parameter numbers,
the parameter is displayed as: <number>:INV
Examples
The following command displays the values of all X.3 parameters, a result
of setting P10=44 (the line folding variable).
PAR?
Response:
PAR 1:1, 2:1, 3:2, 4:0, 5:0, 6:5, 7:0, 8:0,9:0, 10:44,
11:14, 12:0, 13:0, 14:0, 15:1, 16:127, 17:16, 18:23,
19:2, 20:2, 21:16, 22:0, 23:0, 24:0, 25:0, 26:0, 27:5,
28:0, 29:0, 30:0, 31:0, 80:4, 81:18, 82:0, 83:127;
84:0,85:0,86:1
The following command displays the value of X.3 parameter 2:

PAR? 2
Response:
ASYNCXS
C320001300D0
529
X.28 COMMANDS
PAR 2:1
The following command displays the values of X.3 parameters 13, 6, 18,
and 1.
PAR? 13,6,18,1
Response:
PAR 13:0, 6:5, 18:23, 1:1
530
ASYNCXS
C320001300D0
X.28 COMMANDS
Prof (Profile Set)

The Prof (Profile Set) command replaces the PADs current X.3 profile
with a predefined profile. Normally, when the PAD is configured, a
number of different profiles with associated names are created.
Profile names 90 through 99 are reserved for CCITT defined profiles.
Syntax
PROF <profile_name>
PROFile <profile_name>
(if X28Type=C84)
Parameter
<profile_name>
Name of existing profile. To invoke the profile associated with the
device when it was enabled, enter the word: initial.
Range:
116 characters
Response
Profile name invalid or not defined A nonexistent profile was specified.
ASYNCXS
C320001300D0
531
X.28 COMMANDS
Profile? (Profile Display)

The Profile? (Profile Display) command instructs the PAD to list either the
predefined profile names or the X.3 parameter values of a particular
profile. If the profile name is omitted from the command line, the PAD
lists the names of all available profiles.
The Parameter (PAR?) command can be used to display the parameter
values of the devices current profile.
Syntax
PROF?
PROFile? [<profile_name>]
(if X28Type=C84)
Parameters
?
Required character, even when the command is abbreviated.
<profile_name>
Name of existing X.3 profile. To display the profile assigned to the
device when it was enabled, enter the word initial.
Default: Null (all available profile names)
Response
Profile name invalid or not defined A nonexistent profile was specified.
532
ASYNCXS
C320001300D0
X.28 COMMANDS
Read
The Read command reads a data string from a remote device, compares it
to a pattern string, and optionally assigns the input string to a symbol. If
the remote device does not send a string that matches the pattern within a
specified time interval, the PAD clears the call. An input string
corresponds to the contents of a single data packet received from the
remote device; therefore, pattern matching operations are subject to the
remote devices forwarding conditions.
The input string from the remote device is compared to the pattern string
specified with the Read command. If the input string does not match the
pattern string, the PAD discards the input string and reads the contents of
another packet from the network. If no user data is received from the
network within the time interval, the PAD clears the call. If no timer value
is specified, the PAD continues to read from the network until the pattern
string is matched. Only when the pattern is matched will another X.28
command be accepted.
The Read command is used primarily in a remote signon include file,
requiring the remote device user to enter a valid password before allowing
the call to continue. If the remote device does not enter a valid password
within the timeout period, the call is cleared. Once a correct password is
entered, the password can be assigned to a symbol. Subsequent commands
in the file can use the symbol to invoke subsidiary include files whose
names depend on the password.
If a break is entered by the device that initiated the Read command, the
command terminates.
Syntax
REAd[,TIMer=<timeout>][,PATtern=<pattern_string>] [<symbol>]
Parameters
<timeout>
Interval the Read command waits to receive the pattern matching
string.
Range: 0255 seconds
Default: 0 (no timeout)
<pattern_string>
Pattern string to be compared to the contents of a received packet. See
page 52 for information about using wildcard characters.
Range:
116 characters; must been enclosed in quotes if it contains

nonalphanumeric or wildcard characters
Default: Null string (matches/accepts any string)
ASYNCXS
C320001300D0
533
X.28 COMMANDS
<symbol>
Name of symbol to which the matched string is assigned.
Range:
116 characters
Response
Read request timeout No data was received from the network during the
specified time limit; the call is cleared.
Read/Send command is invalid when no call is active This command
can be executed only when a call is active.
534
ASYNCXS
C320001300D0
X.28 COMMANDS
Rpar? (Remote Parameter)

The Rpar? (Remote Parameter) command displays some or all of a remote
PADs X.3 parameter values. If no parameter numbers are supplied, the
PAD displays all parameter values. Duplicate parameter numbers are
ignored. This command is valid only when a call is active.
The order of the parameter numbers is not significant, with two
exceptions: once a parameter number greater than 22 is entered (i.e., a
nonCCITT parameter), all parameters that follow must also be
nonCCITT parameters. If P0 is specified, it must occur after any
international parameter numbers (CCITT parameters) and before any
national parameter numbers (nonCCITT parameters).
Syntax
RPAr? [<number>,...]
Parameters
?
Required character.
<number>
X.3 parameter number. Multiple numbers must be separated by
commas or spaces.
Range:
031 and 8086 if devices X3Type=TELEmatics;

122 if devices X.3Type=C84
Default: Null (causes all parameters to be displayed)
Response
Remote X.29 request timeout The request was passed to the remote node
using an X.29 command, and no response was received. Possible
network problems exist.
If a parameter number is requested that has no meaning to the remote PAD
(for example, if P82 is requested and the remote node is not a Telematics
PAD and therefore doesnt support this parameter), the response is:
<number>:INV
ASYNCXS
C320001300D0
535
X.28 COMMANDS
Rprof (Remote Profile)

The Rprof (Remote Profile) Command replaces a remote devices X.3
parameter values with the corresponding values of a local profile. This
command is valid only when a call is active.
If the profile contains a parameter that has no meaning to the remote
device (for example, if P82 is requested and the remote node is not a
Telematics PAD and therefore doesnt support this parameter), the
parameter is not replaced.
Syntax
RPROf <profile_name>
Parameter
<profile_name>
Local profile name. To invoke the profile associated with the device
when it was enabled, enter the word: initial.
Range:
116 characters
Response
536
ASYNCXS
C320001300D0
X.28 COMMANDS
Rset (Remote Set)

The Rset (Remote Set) command changes a remote PADs X.3 parameter
values. If no parameters are specified, the remote PADs initial X.3 profile
parameter values are read in. Duplicate parameters are ignored. This
command is valid only when a call is active.
The order of parameter numbers are not significant, with two exceptions:
once a parameter number greater than 22 is entered (i.e., a nonCCITT
parameter), all parameters that follow must also be nonCCITT
parameters. P0s value may indicate a specific PAD implementation (e.g.,
Telematics, Telenet). Telematics implementation requires that P0=0 if
national parameters are to be altered. Other implementations may require
a different value. If P0 is specified, it must occur after any international
parameter numbers and before any national parameter numbers.
Syntax
RSEt[?] [<number>:<value>,...]
Parameters
?
Instructs the PAD to confirm the new setting of each specified
parameter.
Default: PAD responds with an acknowledge signal
<number>
X.3 parameter.
Range:

122 if devices X3Type=C84
Default: Null (causes remote PAD to set parameters to initial profile)
<value>
New value to be assigned to the corresponding parameter of the
remote device. See Chapter 3 for values. Multiple parameters must be
separated by commas or spaces.
Range: 0255
Default: Must be specified if number is specified
Response
ASYNCXS
C320001300D0
537
X.28 COMMANDS
Reset (Reset Circuit)

The Reset (Reset Circuit) command resets the current X.25 call. When the
PAD receives a Reset Circuit command, it sends the request to the
network and awaits confirmation. The reset operation discards any data
packets in transit between the local and remote devices, any packets
received by the PAD that are about to be written to the local device, and
any data from the local device being assembled into packets for
transmission. (The remote device performs similar actions.)
Syntax
RESet
RESET
(if X28Type=C84)
Response
Send
The Send command allows a device to send data to a remote device
without switching from command mode to data transfer mode. This
command can be used in an include file, where the Continue command is
prohibited.
Syntax
SENd <string>
Parameter
<string>
String. See page 52 for string format conventions.
Range:

enclose the entire string in quotes
Default: Null (no characters sent)
Response
Read/Send command is invalid when no call is active This command
can be executed only when a call is active.
Invalid parameter Either the <string> is incorrectly formed or there are
additional characters on the command line after the end of the
<string>.
538
ASYNCXS
C320001300D0
X.28 COMMANDS
Set
The Set command changes the devices X.3 parameter values. If
parameters are duplicated, the last one is used. Parameters 8, 11, and 21
are readonly and cannot be set with this command.
Syntax
SET[?] <number>:<value>,...
Parameters
?
Instructs the PAD to confirm the new setting of each specified
parameter.
Default: PAD responds with an acknowledge signal
<number>
X.3 parameter number.
Range:

122 if devices X3Type=C84
Default: Null (no parameters set)
<value>
New value to be assigned to the corresponding device parameter.
Multiple parameters must be separated by commas. See Chapter 3 for
values.
Response
If an invalid parameter number is requested, or if you try to set a
parameter to an invalid value, the parameter is displayed as:
<number>:INV
ASYNCXS
C320001300D0
539
X.28 COMMANDS
Stat (Status)
The Stat (Status) command instructs the PAD to display the current X.25
calls status.
If the Network User Address (NUA) was defined in X.25 with wildcard
characters, NUA information is not returned from the Status command.
Syntax
STAtus
STAT
(if X28Type=C84)
Response
Status signal This is the PADs normal response.
Tact (Port Test)

The Tact (Port Test) command instructs the PAD to read data from a
device and write each character back to the device. This test verifies data
transmission between the device and the PAD. The test continues until a
specified termination character is received from the device, until two
minutes expire, or a break key is entered.
This command cannot be used when a call is active; you must first clear
the call.
Syntax
TACT [<terminate_number>]
Parameter
<terminate_number>
Decimal value of the ASCII character that terminates the test.
Range:
0255
Response
No service signals are returned in response to a Port Test command.
Instead, the prompt Port Test: is displayed. The PAD echoes each
character entered from the terminal to the device.
540
ASYNCXS
C320001300D0
X.28 COMMANDS
Tactt (Terminal Test)

The Tactt (Terminal Test) command instructs the PAD to send a
predefined set of characters to the device. This test verifies the data path
between the PAD and the device. This command writes the string:
1234567890 The Quick Brown Fox Jumped Over The Lazy Dogs Back
repeatedly to the device until the PAD receives a specified termination
character from the device, until two minutes expire, or a break key is
entered.
This command cannot be used when a call is in progress; you must first
clear the call before invoking this command.
Syntax
TACTT [<number>]
Parameter
<number>
Decimal value of the ASCII character that terminates the test.
Range:
0255
Response
No service signals are returned in response to a Terminal Test command.
Instead, the string Terminal Test: is displayed on the screen. The test data
described above is then written to the screen until the test completes.
ASYNCXS
C320001300D0
541
X.28 COMMANDS
Terminate
The Terminate command signs the device off from the PAD and disables
the channel to which the device is connected. Any active call must be
cleared before you issue this command. If P81=8, or any combination of
values including 8, the channel is automatically reenabled after being
disabled.
Syntax
TERMinate
Response
ENGAGED A call is active. The call is retained and the Terminate
command has no effect. Clear the call (Clear command) and then
reissue the Terminate command.
Type
The Type command sends a text string to the local device. This command
is usually issued from an include file to inform the user of the command
processing state.
Syntax
TYpe <string>
Parameter
<string>
String. See page 52 for string format conventions.
Range:

enclose the entire string in quotation marks
Default: Null (no characters to type)
Response
<string> The normal response from the Type command is the string
itself, followed by an Acknowledge PAD service signal.
Invalid parameter Either the <string> is incorrectly formed or there are
additional characters on the command line after the end of the
<string>.
542
ASYNCXS
C320001300D0
X.28 COMMANDS
Wait
The Wait command instructs the PAD to wait a specified amount of time
before requesting the next command. This command is usually used in an
include file.
Syntax
WAIT [<seconds>]
Parameter
<seconds>
Interval for the PAD to wait.
Range: 190 seconds
Default: 1 second
Response
A number in the range 1 to 90 was expected The time interval value is
not within the legal range. Reenter the command with a correct value.
X28Type
The X28Type command changes a devices X28type. This determines if
the device can access the full range of ASYNCXS X.28 commands or if
it is limited to the CCITT 1984 X.28 Recommendation commands.
Syntax
X28Type TELEmatics | C84
Parameters
TELEmatics
Indicates terminal can use full range of X.28 commands.
C84
Indicates device is restricted to the X.28 commands in the CCITT
1984 X.28 Recommendation (i.e., those commands not marked with
an asterisk in the Command Summary) plus the Telematics commands
COntinue, Help, X3Type, X28Type, and @.
Response
Invalid X28 type The parameter specified as the X28 type is not a legal
value. Reenter the command with a correct value.
ASYNCXS
C320001300D0
543
X.28 COMMANDS
X3Type
The X3Type command changes the X3Type of a device. This determines
if the device can change or display the full set of ASYNCXS X.3
parameters or if it is limited to the CCITT 1984 X.3 Recommendation
parameters.
Syntax
X3Type TELEmatics | C84
Parameters
TELEmatics
Device can display and set all X.3 parameters.
C84
Device can display and set only X.3 parameters 122.
Response
Invalid X3 type The parameter specified as the X3type is not a legal
value. Reenter the command with a correct value.
544
ASYNCXS
C320001300D0
6 PAD Service Signals

This chapter describes the service signals that the PAD sends to the
device. Messages are sent in one of two formats, based on the value of P6.
If P6s value is 9 or 13, messages are sent in extended format, containing
as much information about the condition as possible.
Accounting Summary PAD Service Signal

When a call uses the accounting call facility, an accounting summary PAD
service signal is written to the device after the clear PAD service signal.
This provides information about the call.
Display Format
Call was <direction> remote NUA <nua>
Call start time <time>
Call duration <duration>
Resets transmitted/received:
Segments transmitted/received:
Interrupts transmitted/received:
X.25 packets transmitted/received:
Asynchronous characters written/received:
Asynchronous framing/parity errors received:
Asynchronous overflow errors/breaks received:
<in_out> call facilities <facilities>
<value>/<value>
<value>/<value>
<value>/<value>
<value>/<value>
<value>/<value>
<value>/<value>
<value>/<value>
<direction> . Either placed to or received from

<nua> . . . . . Network User Address of remote device
<time> . . . . Time of day call was established (24 hour format)
<duration> . Duration of call in hours and minutes
<in_out> . . . Either outgoing or incoming
<facilities> . Optional user facilities enabled for the call
Acknowledge PAD Service Signal

The acknowledge PAD service signal comprises the format effector
(<CR><LF>), conditionally followed by the PAD service prompt. The
acknowledge PAD service signal display and the PAD service prompt
depend on the value of P6.
ASYNCXS
C320001300D0
61
PAD SERVICE SIGNALS
Clear PAD Service Signal

When a call is cleared, or when an attempt to establish a call is
unsuccessful, the PAD writes a clear PAD service signal to the device.
Display Formats
Nonextended
CLR <cause>
Network Dependent
CLR <cause> C:<ccode> D:<diagnostic> <message>
<cause> . . . Keyword indicating the reason for clear; see list.

<ccode> . . . Numeric cause code value; see list.
<diagnostic> Numeric X.25 diagnostic code; see list.
<message> . Error message returned from NET25; see list.
Clear Cause Signals
Keyword
Meaning
CONF . . . . . Clear confirmation; the device successfully cleared the call.
DER . . . . . . The called number is out of order.
DTE . . . . . . DTE clearing; the remote device cleared the call.
ERR . . . . . . The PAD detected an error caused by the local device.
FNA . . . . . . The fast select option was refused.
ID . . . . . . . . The destination was incompatible.
INV . . . . . . An invalid call facility was requested.
NA . . . . . . . Access barred; the connection is not permitted.
NC . . . . . . . Network congestion or a fault in the network prevented call
acceptance.
NP . . . . . . . Not obtainable; the called address was not assigned to any
device.
OCC . . . . . . Number busy; the called device was engaged in other calls.
PAD . . . . . . The PAD has cleared the call in answer to an invitation to
clear from the remote device.
RNA . . . . . . The called DTE has not subscribed to reverse charging
acceptance.
ROO . . . . . . The call could not be routed as requested.
62
ASYNCXS
C320001300D0
PAD SERVICE SIGNALS
RPE . . . . . . The remote device detected an error caused by the local

device.
SA . . . . . . . The ship could not be contacted.
CCITT X.25 Clear Cause Codes
Decimal Hex
Hex
Decimal
Value
Value
Value
Value
DCE
DCE
DTE
DTE
0 . . . . . . $00 . . . . . . . . . . . . . . . . . . . . . .
1 . . . . . . $01 . . . . $81 . . . . 129 . . . .
3 . . . . . . $03 . . . . $83 . . . . 131 . . . .
5 . . . . . . $05 . . . . $85 . . . . 133 . . . .
9 . . . . . . $09 . . . . $89 . . . . 137 . . . .
11 . . . . . $0B . . . . $8B . . . . 139 . . . .
13 . . . . . $0D . . . . $8D . . . . 141 . . . .
17 . . . . . $11 . . . . $91 . . . . 145 . . . .
19 . . . . . $13 . . . . $93 . . . . 147 . . . .
21 * . . . . $15 . . . . $95 . . . . 149 . . . .
25 * . . . . $19 . . . . $99 . . . . 153 . . . .
Meaning
Originated from DTE
Number busy
Invalid facility request
Network congestion
Out of order
Access barred
Not obtainable
Remote procedure error
Local procedure error
RPOA out of order
Reverse charging acceptance
not subscribed
33 . . . . . $21 . . . . A1 . . . . . 161 . . . . Incompatible destination
41 * . . . . $29 . . . . A9 . . . . . 169 . . . . Fast select acceptance not
subscribed
49 . . . . . $39 . . . . B9 . . . . . 185 . . . . Ship absent
* Valid only if the corresponding call facilities are used
CCITT X.25 Diagnostic Codes

Dec.
Hex
0 . . . . . . . . . $00 . . . . . . .
1 . . . . . . . . . $01 . . . . . . .
2 . . . . . . . . . $02 . . . . . . .
16 . . . . . . . . $10 . . . . . . .
17 . . . . . . . . $11 . . . . . . .
18 . . . . . . . . $12 . . . . . . .
19 . . . . . . . . $13 . . . . . . .
20 . . . . . . . . $14 . . . . . . .
21 . . . . . . . . $15 . . . . . . .
22 . . . . . . . . $16 . . . . . . .
23 . . . . . . . . $17 . . . . . . .
24 . . . . . . . . $18 . . . . . . .
25 . . . . . . . . $19 . . . . . . .
26 . . . . . . . . $1A . . . . . . .
27 . . . . . . . . $1B . . . . . . .
ASYNCXS
C320001300D0
Meaning
No additional information
Invalid Ps
Invalid Pr
Invalid packet type
Invalid packet type in r1
Invalid packet type in p1
Invalid packet type in d1
63
PAD SERVICE SIGNALS
Dec.
28 . . . . . . . .
29 . . . . . . . .
32 . . . . . . . .
33 . . . . . . . .
34 . . . . . . . .
35 . . . . . . . .
36 . . . . . . . .
37 . . . . . . . .
38 . . . . . . . .
39 . . . . . . . .
40 . . . . . . . .
41 . . . . . . . .
42 . . . . . . . .
43 . . . . . . . .
44 . . . . . . . .
45 . . . . . . . .
48 . . . . . . . .
49 . . . . . . . .
50 . . . . . . . .
51 . . . . . . . .
52 . . . . . . . .
64 . . . . . . . .
65 . . . . . . . .
66 . . . . . . . .
67 . . . . . . . .
68 . . . . . . . .
69 . . . . . . . .
70 . . . . . . . .
71 . . . . . . . .
72 . . . . . . . .
73 . . . . . . . .
74 . . . . . . . .
75 . . . . . . . .
76 . . . . . . . .
77 . . . . . . . .
80 . . . . . . . .
81 . . . . . . . .
82 . . . . . . . .
83 . . . . . . . .
96 . . . . . . . .
97 . . . . . . . .
98 . . . . . . . .
64
Hex
$1C . . . . . . .
$1D . . . . . . .
$20 . . . . . . .
$21 . . . . . . .
$22 . . . . . . .
$23 . . . . . . .
$24 . . . . . . .
$25 . . . . . . .
$26 . . . . . . .
$27 . . . . . . .
$28 . . . . . . .
$29 . . . . . . .
$2A . . . . . . .
$2B . . . . . . .
$2C . . . . . . .
$2D . . . . . . .
$30 . . . . . . .
$31 . . . . . . .
$32 . . . . . . .
$33 . . . . . . .
$34 . . . . . . .
$40 . . . . . . .
$41 . . . . . . .
$42 . . . . . . .
$43 . . . . . . .
$44 . . . . . . .
$45 . . . . . . .
$46 . . . . . . .
$47 . . . . . . .
$48 . . . . . . .
$49 . . . . . . .
$4A . . . . . . .
$4B . . . . . . .
$4C . . . . . . .
$4D . . . . . . .
$50 . . . . . . .
$51 . . . . . . .
$52 . . . . . . .
$53 . . . . . . .
$60 . . . . . . .
$61 . . . . . . .
$62 . . . . . . .
Meaning
Packet not allowed
Unidentified packet
Call on one way LC
Invalid PVC packet
Reject on unassigned LC
Reject not subscribed to
Packet too short
Packet too long
Invalid GFI
Restart/registration packet has LC
Packet type not compatible with facility
Unauthorized interrupt confirmation
Unauthorized interrupt
Unauthorized reject
Timer expired
Incoming call timer expiration
Clear indication timer expiration
Reset indication timer expiration
Restart indication timer expiration
Call setup/clear/registration problem
Facility/registration not allowed
Expected facility not provided
Invalid called address
Invalid calling address
Invalid facility registration length
Incoming calls barred
No logical channels available
Call collision
Duplicate facility requested
Nonzero address length
Nonzero facility length
Expected facility not provided
Invalid CCITT specifies facility
Miscellaneous
Improper cause code from DTE
Nonaligned octet
Inconsistent Q bit setting
International setup/clearing problem
Unknown calling DNIC
TNIC mismatch
ASYNCXS
C320001300D0
PAD SERVICE SIGNALS
Dec.
99 . . . . . . . .
100 . . . . . . .
101 . . . . . . .
102 . . . . . . .
103 . . . . . . .
112 . . . . . . .
113 . . . . . . .
114 . . . . . . .
115 . . . . . . .
116 . . . . . . .
117 . . . . . . .
118 . . . . . . .
119 . . . . . . .
120 . . . . . . .
121 . . . . . . .
122 . . . . . . .
128 . . . . . . .
218 . . . . . . .
219 . . . . . . .
Hex
$63 . . . . . . .
$64 . . . . . . .
$65 . . . . . . .
$66 . . . . . . .
$67 . . . . . . .
$70 . . . . . . .
$71 . . . . . . .
$72 . . . . . . .
$73 . . . . . . .
$74 . . . . . . .
$75 . . . . . . .
$76 . . . . . . .
$77 . . . . . . .
$78 . . . . . . .
$79 . . . . . . .
$7A . . . . . . .
$80 . . . . . . .
$DA . . . . . .
$DB . . . . . .
Meaning
Call identifier mismatch
Negotiation error in utility parameter value
Invalid utility length
Nonzero utility length
M bit violation
International problem
Remote network problem
International network problem
International link out of order
International link busy
Transit network facility problem
Remote network facility problem
International routing problem
Temporary routing problem
Unknown called DNIC
Maintenance action
Network specific diagnostic
TRAX trap error for user call
User task error
Clear Service Signal Messages

Accept not valid on Fast Select Restricted Call
Buffer size invalid
Call collision
Called/calling address exceeds maximum length
Calling NUA not provided
Clear received
CUG outgoing access barred
CUG reference not found
Data handler indicated error
Destroy denied records still exists for entity
Error accessing data handler
Facility negotiation parameter unacceptable
Facility not subscribed to
Incoming calls barred on the node
Incoming calls barred to NUA
Incompatible facilities requested (e.g., FS + FS or CUG + CUGO)
Index number out of valid range
Invalid called address
Invalid calling address
Invalid logical channel specified for PVC
Invalid handler key specified
Invalid handler key specified
ASYNCXS
C320001300D0
65
PAD SERVICE SIGNALS
Invalid packet received

Link error
Maximum length of routing address exceeded
Missing call parameter block
No file or CPB specified
No more information available
NUA subaddress length invalid
Outgoing calls barred on the node
Outgoing calls barred to NUA
Packet negotiation unacceptable
Protocol error
PVC link not found
PVC already in use
PVC link is locked or outgoing access is barred
Reference not specified
Reference not found
Reference too long
Route not available all links are down or unavailable
Route not defined for specified called address
Specified link not found
Throughput class negotiation unacceptable
User requested clear
User data is invalid on Accept or Clear
User date length exceeds 16 characters
Userhook declined routing
Window size negotiation unacceptable
Clear Confirmation PAD Service Signal

The PAD issues a clear confirmation service PAD service signal when a
clear is received from the remote device or when the local device initiates
a call clear.
Display Formats
Nonextended
CLR CONF
Network Dependent
CLR CONF Call cleared, confirmed
66
ASYNCXS
C320001300D0
PAD SERVICE SIGNALS
Connected PAD Service Signal

The PAD writes a connected PAD service signal to the device when an
outgoing call is successfully established or when an incoming call is
accepted.
The display described below assumes call facilities and user data were
specified for the call. If facilities and/or data are not supplied, the display
is adjusted accordingly.
Display Format
<calling>/<called>
[FAC: <fac>] COM
[USERDATA: <cud>]
<calling> . . 115 digit Network User Address (NUA) of device that

initiated call.
<called> . . . Address of device to which call was destined. If the
connection was established with a Call command, this is
the 115 digit NUA of the caller. If the connection was
established to a PVC with a Connect command, this is
<link name><logical channel number>.
<facilities> . Optional call facilities, if used.
COM . . . . . Outgoing call is successfully established.
<cud> . . . . . Optional call user data accompanying call request, if any.
This is only included on Connected signals for incoming
calls.
ASYNCXS
C320001300D0
67
PAD SERVICE SIGNALS
Invalid Command PAD Service Signal

The PAD issues an invalid command PAD service signal when it receives
an invalid command from the terminal.
Display Formats
Nonextended
ERR
Network Dependent
ERR Invalid X.28 command entered
Reset PAD Service Signal

The PAD issues a reset PAD service signal when a local or remote X.28
Reset command is issued.
Display Formats
Nonextended
RESET
Network Dependent
RESET <cause>
The <cause> can be one of the following:

DTE . . . . . . Reset by remote device; data may be lost.
ERR . . . . . . Reset by network; local procedure error; data may be lost.
NC . . . . . . . Reset due to temporary network problem; data may be lost.
RPE . . . . . . Reset by network; remote procedure error; data may be
lost.
68
ASYNCXS
C320001300D0
PAD SERVICE SIGNALS
Status PAD Service Signal

The X.28 Show Status command returns a status PAD service signal.
Display Format
ENGAGED to <rem_nua>
Port: <port> NUA: <loc_nua> X3Type: <type> X28type: <type>
Outgoing calls are <per_pro>, incoming calls are <acc_nacc>
Outgoing calls must be charged to <charge> reverse charge call facility <use>
Incoming calls must be charged to the <charge>, <reverse>
X25 idle timer value:
Command mode timeout value:
Default packet size receive/transmit:
Maximum packet size receive/transmit:
Default window size receive/transmit:
Maximum window size receive/transmit:
Default throughput class receive/transmit:
Maximum throughput class receive/transmit:
<value>
<value>
(<value>/<value>)
(<value>/<value>)
(<value>/<value>)
(<value>/<value>)
(<value>/<value>)
(<value>/<value>)
<rem_nua> . Remote devices Network User Address

<port> . . . . Port number on local node
<loc_nua> . Local devices Network User Address
<type> . . . . Either Telematics or C84
<per_pro> . Either permitted or prohibited
<acc_nacc>
Either accepted or not accepted
<charge> . . One of: LOCAL DEVICE, REMOTE DEVICE, or LOCAL

or REMOTE DEVICE
<use> . . . . . One of: cannot be used, must be used, or use is optional
<reverse> . . One of: calls with reverse charge call facility set are not
accepted, only calls with the reverse charge call facility are
accepted, or reverse charge call facility use is optional
ASYNCXS
C320001300D0
69
PAD SERVICE SIGNALS
610
ASYNCXS
C320001300D0
7 Alarms
When INF receives notification of an event, a message is displayed on the
Telematics terminal. Telematics provides an include file containing the
default definitions of ASYNCXSspecific alarms. If you want to develop
your own alarm messages for ASYNCXS, see the INF Manual.
The format of an INF alarm is:
ALARM <number>:message
Severity
Informational Informational alarms require no action, and there should
be no adverse effect on ASYNCXS operation. Keep in mind that when
your resource is set to ASYNCXS, you can access all the INF
commands. If you create or type a symbol that matches the case
significance of an INF command, you will get an error message trying to
expand the symbol (which may not be the message you are expecting).
Check the syntax of the command.
Error Error alarms indicate soft or recoverable errors.
Warning Warning alarms indicate a temporary problem, and there should
be no adverse affect on ASYNCXS operation. No action is required;
however, repeated occurrences of these alarms may indicate a network or
configuration problem.
Fatal Fatal alarms rarely occur, but can affect system operation. Fatal
alarms indicate software, hardware, or configuration problems. Software
and configuration problems can occur in ASYNCXS, the network, or the
system.
ASYNCXS
C320001300D0
71
ALARMS
Alarm Messages
The following list describes alarms in ascending numerical order. All
alarms are category 18 (see the INF Manual for information about alarm
categories). In the alarm text (which is enclosed in quotation marks),
symbol S0 is the logical volume, symbol S1 is the device or profile name,
and error values indicated by N1 are defined in the level 2 include file
named l2asydef.in; see the logical read/write completion codes. The
alarms severity and explanation follow the text.
256 Device S0:S1 Async connected
Informational An asynchronous port has been logically connected to
ASYNCXS.
257 Device S0:S1 Async disconnected
Informational An asynchronous port has been logically disconnected
from ASYNCXS.
258 Device S0:S1 X.25 connected
Informational A call is complete and an X.25 logical channel has
been established.
259 Device S0:S1 X.25 disconnected
Informational An X.25 logical channel has been disconnected.
260 Reserved
261 Device S0:S1 X.29 command timer expired
Informational A timer starts when an X.29 command is issued that
requires a response. If the timer expires before a response is received,
the x29 timeout alarm is generated. Responses can be delayed for
several reasons: X.29 commands are queued in the network, one or
both PADs are in command mode, or there are normal data packets
ahead of the X.29 packets. In this case, nothing can happen until data
transfer mode is continued.
262 Device S0:S1 Command mode timer expired
Informational No activity has occurred in X.28 command mode, and
the timer has expired.
263 Device S0:S1 Data mode timer expired
Informational No activity has occurred in data transfer mode, and the
timer has expired.
264 Device S0:S1 Modem signal(s) lost
Error Modem signals were lost.
265 Device S0:S1 Memory (de)allocation error
Warning ASYNCXS requested memory from the operating system
and was denied. Memory use should be evaluated. Remedies include
increasing the amount of system memory, attaching fewer devices, or
allowing fewer concurrently executing tasks.
72
ASYNCXS
C320001300D0
ALARMS
266 Device S0:S1 X.25 open error, rvalu: N2

Warning An open request to X.25 has failed. Possible causes include
an invalid network address, a busy network, and network congestion.
The N2 error value may be a TRAX system completion code.
267 Device S0:S1 X.25 close error
Warning The X.25 software has returned an error to a close request,
which indicates a system failure or a problem in software, hardware,
or the network.
268 Device S0:S1 X.25 read error ($N2)
Warning The X.25 software has returned an error to a read request,
or the network. The N2 value represents a system completion code or
rvalu.
269 Device S0:S1 X.25 write error ($N2)
Warning The X.25 software has returned an error to a write request,
or the network. The N2 value represents a system completion code or
rvalu.
270 Reserved
271 Device S0:S1 Async close error
Warning An error on a close request occurred, which indicates a
system failure or a problem in software, hardware, or the network.
272 Device S0:S1 Async read error (N1)
Warning An abnormal read completion was received. The N1 error
value indicates the reason for the abnormal termination.
273 Device S0:S1 Async write error (N1)
Warning An abnormal write completion was received. The N1 error
value indicates the reason for the abnormal termination.
274 Reserved
275 Device S0:S1 File close error
Warning The file handler returned an error to the close request for a
previously opened file, which indicates a system failure or a problem
in software, hardware, or the network.
276 Device S0:S1 File read error
Warning A read error to an open file was received, which can
indicate a media or file format problem; otherwise, a software
problem, hardware problem, network problem, or system failure is
indicated.
277 Reserved
ASYNCXS
C320001300D0
73
ALARMS
278 Device S0:S1 Invalid X.29 message received

Warning The remote PAD violated X.29 protocol.
279 Reserved
280 Reserved
281 AsyncXS volume S0: compatible with X25 revision E
Informational Indicates compatibility with NET25 revision E.
282 AsyncXS volume S0: compatible with X25 revision F
Informational Indicates compatibility with NET25 revision F.
283 AsyncXS volume S0: NUI table is 90% full
Informational The NUI table is nearing its capacity.
284 AsyncXS volume S0: NUI table is full
Warning The NUI table has reached its capacity.
285 Device S0:S1 Invalid NUI entered
Informational An invalid NUI was entered.
286 AsyncXS volume S0: attempted to add duplicate NUI
Warning An attempt was made to add an NUI that duplicates an
existing one.
287 AsyncXS volume S0: compatible with X25 revision G
Informational Indicates compatibility with NET25 revision G.
288 Device S0:S1 encountered an internal error type N1
Warning An internal error occurred; errors are defined in the file
axsalarms.inf.
289 Device S0:S1 disabled, operator intervention required
Error Operator action is required to enable the device.
290 Device S0:S1 receiving bad characters, alarms stopped
Warning Bad data is being received; to avoid overloading the system
with alarms, they are no longer issued. Disable the device, then
reenable it.
291 Device S0:S1 received a parity error
Warning A bad character was received. This could indicate a line
problem.
292 Device S0:S1 received a framing error
problem.
74
ASYNCXS
C320001300D0
ALARMS
293 Device S0:S1 received a overflow error

problem.
294 Device S0:S1 received an unknown input error ($N2)
problem.
295 Device S0:S1 Configuration anomaly, value: N1
Informational An error (indicated by the N1 error value) was
detected while setting lower level parameters.
296 Device S0:S1 Unable to register for incoming calls: N2
Warning The N2 value contains the rvalu from X.25, indicating why
registration failed.
297 Device S0:S1 Error rejecting call, error N1
Warning The N1 value contains the rvalu from X.25, indicating why
the call was rejected.
298 Device S0:S1 Unable to deregister for incoming calls
Warning An error occurred during deregistration.
299 AsyncXS volume S0: compatible with X25 revision H
Informational Indicates compatibility with NET25 revision H.
300 Device S0:S1 X.25 Copy read error ($N2)
Warning The X.25 software has returned an error to a copy read
request, which indicates a system failure or a problem in software,
hardware, or the network.
301 Device S0:S1 X.25 Copy write error ($N2)
Warning The X.25 software has returned an error to a copy write
request, which indicates a system failure or a problem in software,
hardware, or the network.
302 Device S0:S1 Event notification error ($N2)
Warning An error was returned while attempting an event
notification. The system completion code in N2 indicates the error
returned.
303 Device S0:S1 Can not place call with call active
Warning A call cannot be placed because there is already an active
call.
304 Device S0:S1 Invalid state when X.25 close received
Warning An unexpected close was received.
ASYNCXS
C320001300D0
75
ALARMS
76
ASYNCXS
C320001300D0
ASCII Character Set

Dec.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
ASYNCXS
C320001300D0
Hex.
00
01
02
03
04
05
06
07
08
09
0A
0B
0C
0D
0E
0F
10
11
12
13
14
15
16
17
18
19
1A
1B
1C
1D
1E
1F
20
Oct.
00
01
02
03
04
05
06
07
10
11
12
13
14
15
16
17
20
21
22
23
24
25
26
27
30
31
32
33
34
35
36
37
40
Binary
0000 0000
0000 0001
0000 0010
0000 0011
0000 0100
0000 0101
0000 0110
0000 0111
0000 1000
0000 1001
0000 1010
0000 1011
0000 1100
0000 1101
0000 1110
0000 1111
0001 0000
0001 0001
0001 0010
0001 0011
0001 0100
0001 0101
0001 0110
0001 0111
0001 1000
0001 1001
0001 1010
0001 1011
0001 1100
0001 1101
0001 1110
0001 1111
0010 0000
ASCII
NUL
SOH
STX
ETX
EOT
ENQ
ACK
BEL
BS
HT
LF
VT
FF
CR
SO
SI
DLE
DC1
DC2
DC3
DC4
NAK
SYN
ETB
CAN
EM
SUB
ESC
FS
GS
RS
US
SP
Key
CTRL@
CTRL/A
CTRL/B
CTRL/C
CTRL/D
CTRL/E
CTRL/F
CTRL/G
CTRL/H, BACKSPACE
CTRL/I, TAB
CTRL/J, LINE FEED
CTRL/K
CTRL/L
CTRL/M, RETURN
CTRL/N
CTRL/O
CTRL/P
CTRL/Q
CTRL/R
CTRL/S
CTRL/T
CTRL/U
CTRL/V
CTRL/W
CTRL/X
CTRL/Y
CTRL/Z
ESC, ESCAPE
CTRL/\
CTRL/]
CTRL/^
CTRL//
SPACEBAR
A1
ASCII CHARACTER SET
Dec.
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
A2
Hex.
21
22
23
24
25
26
27
28
29
2A
2B
2C
2D
2E
2F
30
31
32
33
34
35
36
37
38
39
3A
3B
3C
3D
3E
3F
40
41
42
43
44
45
Oct.
41
42
43
44
45
46
47
50
51
52
53
54
55
56
57
60
61
62
63
64
65
66
67
70
71
72
73
74
75
76
77
100
101
102
103
104
105
Binary
0010 0001
0010 0010
0010 0011
0010 0100
0010 0101
0010 0110
0010 0111
0010 1000
0010 1001
0010 1010
0010 1011
0010 1100
0010 1101
0010 1110
0010 1111
0011 0000
0011 0001
0011 0010
0011 0011
0011 0100
0011 0101
0011 0110
0011 0111
0011 1000
0011 1001
0011 1010
0011 1011
0011 1100
0011 1101
0011 1110
0011 1111
0100 0000
0100 0001
0100 0010
0100 0011
0100 0100
0100 0101
ASCII
!
#
$
%
&
(
)
*
+
,
.
/
0
1
2
3
4
5
6
7
8
9
:
;
<
=
>
?
@
A
B
C
D
E
Key
!
#
$
%
&
(
)
*
+
,
.
/
0
1
2
3
4
5
6
7
8
9
:
;
<
=
>
?
@
A
B
C
D
E
ASYNCXS
C320001300D0
ASCII CHARACTER SET
Dec.
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
ASYNCXS
C320001300D0
Hex.
46
47
48
49
4A
4B
4C
4D
4E
4F
50
51
52
53
54
55
56
57
58
59
5A
5B
5C
5D
5E
5F
60
61
62
63
64
65
66
67
68
69
6A
Oct.
106
107
110
111
112
113
114
115
116
117
120
121
122
123
124
125
126
127
130
131
132
133
134
135
136
137
140
141
142
143
144
145
146
147
150
151
152
Binary
0100 0110
0100 0111
0100 1000
0100 1001
0100 1010
0100 1011
0100 1100
0100 1101
0100 1110
0100 1111
0101 0000
0101 0001
0101 0010
0101 0011
0101 0100
0101 0101
0101 0110
0101 0111
0101 1000
0101 1001
0101 1010
0101 1011
0101 1100
0101 1101
0101 1110
0101 1111
0101 0000
0110 0001
0110 0010
0110 0011
0110 0100
0110 0101
0110 0110
0110 0111
0110 1000
0110 1001
0110 1010
ASCII
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
[
\
]
^
a
b
c
d
e
f
g
h
i
j
Key
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
[
\
]
^
a
b
c
d
e
f
g
h
i
j
A3
ASCII CHARACTER SET
Dec.
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
A4
Hex.
6B
6C
6D
6E
6F
70
71
72
73
74
75
76
77
78
79
7A
7B
7C
7D
7E
7F
Oct.
153
154
155
156
157
160
161
162
163
164
165
166
167
170
171
172
173
174
175
176
177
Binary
0110 1011
0110 1100
0110 1101
0110 1110
0110 1111
0111 0000
0111 0001
0111 0010
0111 0011
0111 0100
0111 0101
0111 0110
0111 0111
0111 1000
0111 0101
0111 1010
0111 1011
0111 1100
0111 1101
0111 1110
0111 1111
ASCII
k
l
m
n
o
p
q
r
s
t
u
v
w
x
y
z
{
|
}
~
DEL
Key
k
l
m
n
o
p
q
r
s
t
u
v
w
x
y
z
{
|
}
~
DEL, RUBOUT
ASYNCXS
C320001300D0
IO Interface
This appendix describes the ASYNCXS PAD IO interface, which allows
a user application task to communicate directly with the PAD entity (e.g.,
transmit and receive data).
To use this appendix effectively, you must be familiar with programming
handlers and applications in the Telematics TRAX operating system
environment. This includes experience in building and submitting IO
subservice request packets, which is described in the Telematics
Programmers Guide (C310000100) and the TRAX Programmers
Manual (C315000100).
Introduction
This section lists documentation conventions and product features.
Conventions
Field length specifications
B indicates a byte, W indicates a word, and L indicates a longword. If
no decimal precedes the letter, a single byte, word, or longword is
expected. A decimal preceding the letter indicates the number of bytes,
words, or longwords.
A hyphen () indicates the mnemonic in the Field column does not
represent a field offset. Such mnemonics represent the length of a
request packet or parameter buffer, and may be used when reserving
and initializing memory for them.
A V indicates the start of a variable length field. When a buffer has a
variable length field, the maximum buffer size includes the base, plus
the maximum variable length, plus 2.

The delta graphic indicates the device parameter can be modified
while the device is online.
*
A single asterisk indicates the preceding mnemonic is defined in the
asyxsuser.in include file (see next section, Include Files).
**
A double asterisk indicates the preceding mnemonic is defined in the
padiodefs.in include file (see next section, Include Files).
use and set
The word use preceding a mnemonic in the Contents column indicates
a MOVE instruction to copy a value into a field. The word set
indicates a BSET instruction to set the bit identified by the mnemonic
in that field.
ASYNCXS
C320001300D0
B1
IO INTERFACE
Return values and error mnemonics are described at the end of the
appendix.
Include Files
The ASYNCXS PAD IO interface references three include files:
userdef.in, asyxsuser.in, and padiodefs.in.
The userdef.in include file defines the TRAX standard mnemonics and
macros.
The asyxsuser.in include file defines the ASYNCXS PAD standard

mnemonics and macros.
The padiodefs.in include file defines the mnemonics that are standard
to the Telematics IO interface for PADs.
By default, most mnemonics referenced in this appendix reside in the
userdef.in include file. Mnemonics from the asyxsuser.in include file are
noted with a single asterisk (*). Mnemonics from the padiodefs.in include
file are noted with a double asterisk (**).
For high level language compatibility, the following values can be used
for CTTYPE:
Assembler values:
typ$unkn_ or typ_unkn_ . . . . . . . . . . . . . .
typ$prof_ or typ_prof_ . . . . . . . . . . . . . . . .
typ$term_ or typ_term_ . . . . . . . . . . . . . . .
typ$dir_ or typ_dir_ . . . . . . . . . . . . . . . . . .
typ$vol_ or typ_vol_ . . . . . . . . . . . . . . . . .
typ$ddir_ or typ_ddir_ . . . . . . . . . . . . . . . .
Unknown
X.3 Profile
Terminal access
Directory
Volume
Device directory (return
info only)
typ$pdir_ or typ_pdir_ . . . . . . . . . . . . . . . . Profile directory (return
info only)
typ$portsw_ or typ_portsw_ . . . . . . . . . . . Port switch bit for
create/destroy
C values:
TYP$UNKN_ or TYP_UNKN_ . . . . . . . .
TYP$PROF_ or TYP_PROF_ . . . . . . . . . .
TYP$TERM_ or TYP_TERM_ . . . . . . . . .
TYP$DIR_ or TYP_DIR_ . . . . . . . . . . . . .
TYP$VOL_ or TYP_VOL_ . . . . . . . . . . . .
TYP$DDIR_ or TYP_DDIR_ . . . . . . . . . .
Unknown
X.3 Profile
Terminal access
Directory
Volume
info only)
TYP$PDIR_ or TYP_PDIR . . . . . . . . . . . . Profile directory (return
info only)
TYP$PORTSW_ or TYP_PORTSW_ . . . . Port switch bit for
create/destroy
B2
ASYNCXS
C320001300D0
IO INTERFACE
Pascal values:
typ$unkn_ or typ_unkn_ . . . . . . . . . . . . . .
typ$prof_ or typ_prof_ . . . . . . . . . . . . . . . .
typ$term_ or typ_term_ . . . . . . . . . . . . . . .
typ$dir_ or typ_dir_ . . . . . . . . . . . . . . . . . .
typ$vol_ or typ_vol_ . . . . . . . . . . . . . . . . .
typ$ddir_ or typ_ddir_ . . . . . . . . . . . . . . . .
Unknown
X.3 Profile
Terminal access
Directory
Volume
info only)
typ$pdir_ or typ_pdir_ . . . . . . . . . . . . . . . . Profile directory (return
info only)
typ$portsw_ or typ_portsw_ . . . . . . . . . . . Port switch bit for
create/destroy
Modes
Each created device can be placed in one of two operating modes: PAD or
handler.
When the device is in PAD mode (the default), the PADs functionality
remains the same; any IO/READs and IO/WRITEs issued to the device
will be returned in error. The device will be in either X.28 command
mode, or in data transfer mode (see Chapter 2).
When a device is placed in handler mode, any device write or read in
progress is terminated, and if a call is active, reads and writes to X.25 are
suspended. The only valid activity with the device is through the TRAX
IO services. IO/READs and IO/WRITEs are allowed.
To change from one mode to the other, issue the appropriate
IO/EXCHANGE subservice: Pass Control to PAD Mode or Pass Control
to Handler Mode. Note that the application task must have previously
completed an IO/OPEN to the device.
Additionally, when the device is in PAD mode, it is placed in handler
mode:
When it receives an X.25 Disconnect command (IO/EXCHANGE)

from the IO/OPENed application.
When it receives an X.25 Call Clear request.

When it receives notification of an entity disconnection (loss of
modem signals).
When the hot key is entered. The hot key is specified with the
IO/EXCHANGE Pass Control to PAD Mode subservice, and allows a
user to quickly access the application when the PAD is in PAD mode.
When the hot key is entered, the PAD is placed into handler mode and
the application receives an event notification (if it is registered for
event notification).
ASYNCXS
C320001300D0
B3
IO INTERFACE
Event Notification
An application task can register and deregister for event notification using
IO/EXCHANGE subservices. A task can also register for event
notification in the IO/OPEN service. Events comprise device related
occurrences that may require action. When a defined event happens, and
the application is registered for event notification, the task is notified with
an IO/MODE that an event occurred, in the format shown below. Note that
ASYNCXS events are distinct from alarms used by INF.
Returned Event Format
Length
Field
evntrev **
evntfunct **
evntprod **
evntnumber **
evntrvalu **
evntboottime **
evntyear **
evntmonth **
evntday **
evnthour **
evntminutes **
evntseconds **
evntmilisec **
evnthotkey **
evntport **
evntps1 **
evntps2 **
evntsize **
W
W
W
W
L
L
W
B
B
B
B
B
W
W
W
W
W
*
Contents
Event revision
Event function
Product number
Event number (see list below)
Return value
Milliseconds since boot
Year
Month
Day
Hour
Minutes
Seconds
Milliseconds
Index of hot key that caused exception
Port number
Product specific field
Product specific field
Size of buffer
** Defined in padiodefs.in
evntnumber Field Definitions

Mnemonic
evntx25c_
**
evntx25d_
**
evntx25i_ **
B4
No.
0
1
2
Text Description
X.25 connected The X.25 call is up and active,
and the device is in PAD mode
X.25 disconnected The call has been
disconnected, and the device is in handler mode
X.25 incoming call The user task can obtain a
copy of the call parameter block, and then must
either accept or reject the call
ASYNCXS
C320001300D0
IO INTERFACE
evntx25o_
**
evntentc_ **
evntentonl_
**
evntentd_
**
evntentoff_
**
evnthotkey_
**
evntx25t_ **
evntx28t_ **
10
evntctlc_ **
11
evntctly_ **
12
ASYNCXS
C320001300D0
X.25 outgoing call A device user is trying to

place a call from the X.28 command prompt; the
user task can obtain a copy of the call parameter
block, and then either connect or reject the call
Entity connected Modem signals (if required),
carrier detect, and data set ready are present; the
device is ready to receive and transmit data
Entity online Not supported by ASYNCXS
Entity disconnected Modem signals have been
placed in the idle state, and no data can be
transmitted or received
Entity offline Not supported by ASYNCXS
Hot key entered The device is placed into
handler mode; the user task decides the next
action (e.g., issue an IO/READ or IO/WRITE)
X.25 idle timer expired The call will be cleared
and the device will be placed into handler mode
X.28 command mode timer expired The device
will be placed into handler mode
ControlC character received A ControlC
character has been received during an IO/READ,
the device is in handler mode, and the user task
determines the actions required
ControlY character received A ControlY
character has been received during an IO/READ,
the device is in handler mode, and the user task
determines the actions required
B5
IO INTERFACE
IO Service Summary
This section provides a summary of the ASYNCXS IO service requests,
plus recommendations about the proper sequence in which services should
be requested.
The ASYNCXS IO interface supports the following IO services:
IO/CLOSE Closes access to an asynchronous channel

IO/CRDIR
Creates a directory for a device
Creates a directory for an X.3 profile
IO/CREATE
Creates a full duplex channel as an IO entity and assigns it to an IO
entity name.
Creates a set of X.3 parameters that can be associated with a
device
IO/DESTROY
Destroys the definition of a channel as an IO entity
Destroys a directory
Destroys a profile
IO/DISMOUNT Removes the definition of the PADs logical

volume
IO/EXCHANGE
Defines, modifies, or obtains initial parameters
Registers or deregisters for event notification
Passes control to PAD or handler mode
Requests an X.25 connection or accepts an incoming call
Requests an X.25 disconnection or rejects an incoming call
Requests incoming call parameters
Modifies a devices configuration parameters while the device is
online
B6
ASYNCXS
C320001300D0
IO INTERFACE
IO/INFO
Retrieves entity names or detailed properties
Retrieves a devices status
Retrieves a devices or profiles configuration information
Retrieves PADmap information
Retrieves async IO configuration information
IO/MODE
Enables, disables, or modifies a device
Resets a devices statistics
Adds or deletes a PADmap entry, or deletes the entire PADmap
table
Enables or disables task exception processing
Modifies async IO configuration information
IO/MOUNT Defines the PADs logical volume and claims a

Communications Processor activity queue
IO/OPEN Opens an asynchronous channel as an IO entity

IO/READ Transfers data from an IO entity to a buffer
IO/RESET Terminates certain types of IO operations or all IO
operations
IO/WRITE Transfers data from a buffer to an IO entity

The IO interface does not support the IO/CANCEL, IO/INTERRUPT, or
IO/RENAME services. If any of these services are requested, the system
completion code sccfnsp. (i.e., function not supported) is returned.
ASYNCXS
C320001300D0
B7
IO INTERFACE
IO/CLOSE
The IO/CLOSE service releases logical file access to an IO entity. When
this request completes, exception registrations, modem state change
notification registrations, and all queued and inprogress IO/READ and
IO/WRITE requests are terminated.
The PAD requires no handler specific options for this service.
Packet
Field
pktname
B8
Length
8B
Contents
Logical access name (left justified, space
filled)
ASYNCXS
C320001300D0
IO INTERFACE
IO/CRDIR
The IO/CRDIR service creates a directory for a device or an X.3 profile.
IO/CRDIR Create Device Directory
This subservice creates a directory for devices.
Packet
Field
pktimopt
pkthsopt
pktfname
pktfnsiz
Length
B
W
L
W
Contents
Class selection index; use ioicnam.
Handler specific option; use typ$term_ *
Address of entity name string
Length of entity name
* Defined in asyxsuser.in
IO/CRDIR Create Profile Directory

This subservice creates a directory for profiles.
Packet
Field
pktimopt
pkthsopt
pktfname
pktfnsiz
Length
B
W
L
W
Contents
Handler specific option; use typ$prof_ *
Address of profile directory name
Byte length of profile directory name
ASYNCXS
C320001300D0
B9
IO INTERFACE
IO/CREATE
The IO/CREATE service creates a device or X.3 profile definition.
IO/CREATE Device
This subservice identifies a channel as an IO entity and assigns it an IO
entity name. The calling task must provide a channel number
corresponding to a duplex channel in the range 0512, and an IO entity
name for the channel.
In response to this request, the PAD claims the specified full duplex
channel pair and defines the channels using the values specified in the
device configuration buffer. This is the same buffer that is used when
calling IO/MODE to set parameters.
Packet
Field
pkthsopt
pktfname
pktfnsiz
pktparam
pktpbsiz
Length
W
L
W
L
W
Contents
Address of entity name buffer
Address of device configuration buffer
Byte length of device configuration buffer; use
cmsize *
Device Configuration Buffer

This parameter buffer is used for creating a device, retrieving a devices
configuration information, and modifying a devices configuration while
the device is online or offline. However, not all the listed parameters are
used for each subservice; see notes preceding certain parameter groups
that apply only to certain services.
The graphic Y indicates the parameter is online modifiable, i.e., it can be
changed with an IO/EXCHANGE subservice request to Online Modify
Device Parameters.
Field
B10
Length
cmverlet *
cmvernum *
B
B
cmt1val *
Contents
Current product revision letter; use verlet *
Current product version number (e.g., for the
H.x release, the version number is 8); use
vernum *
Y Delay after which the PAD automatically
places an X.25 call (if autocall is enabled) once
the device is created. To enable autocall, P81
must equal 2 or a sum including 2, and the
device must have a valid called address.
Range: 0500 seconds
ASYNCXS
C320001300D0
IO INTERFACE
cmretim *
cmretmx *
cmcdsz *
cmcd *
B
16B
cmx25sz *
cmx25vo *
9B
cmcgsz *
cmcg *
B
16B
cmrevc *
cmcudsz *
cmcud *
W
128B
cmintd *
cmport *
cmpadc *
ASYNCXS
C320001300D0
Y Time interval the PAD waits after a call

has failed before trying again. Range: 6600
seconds
Y Number of times a call will be retried in
case of failure; a zero value indicates no retry
limit. Range: 0127
Length of remote called address Range: 015.
Called NUA (the default destination address
for an X.28 Call command). This value is used
when the called address is omitted or when
autocall is enabled (P81=2 or a sum including
2). If this parameter is omitted, each X.28 Call
command must include a called address.
Range: 015 digits
Length of X25 volume name. Range: 19
characters
Name of the X.25 volume to be associated with
a device. Range: 19 characters
Length of local calling address. Range: 015
Calling NUA; must be specified for the device
to be notified by the PAD of an incoming call.
Range: 015 digits
Reverse charge call facility: use revcyes_ * to
indicate the facility is specified in X.28 Call
command; use revcno_ * to indicate the facility
not used, even if specified in X.28 Call
command; use revcalways_ * to indicate the
facility is used on every call, even if omitted
from X.28 Call command.
Length of call user data. Range: 1124
Call user data (CUD) to be sent with each call
request, if the corresponding field is omitted in
the X.28 Call command. If CUD is omitted in
the device specification and the X.28 Call
command, no CUD is sent except the protocol
identifier. Range: 1124 characters
Single data byte to be sent with X.29 Interrupt
command if not specified in the command.
Range: 0255 ($00$ff)
Asynchronous port number to which the device
is to be connected. Range: 0479
Y Padding data transmitted to the device.
The P9, P14, and P27 values determine
padding. Range: 0255 ($00$ff)
B11
IO INTERFACE
B12
cmmodem *
cmbrkmk *
cmbrkln *
cmbrksr *
W
90B
cmbrkti *
cmstopbit *
cmdtrc *
cmbufsz *
cmelem *
cmblkfl *
cmfbtim *
B
B
L
Modem characteristics: set mdm_modem * to

indicate device is connected to a modem, clear
mdm_modem * to indicate no modem; set
mdm_dtr * to indicate DTR will be raised at
idle, clear mdm_dtr * to indicate DTR low; set
mdm_hang * to indicate modem hangup on
device disable, clear mdm_hang * to indicate
no hangup; set mdm_auto * to indicate ringin
detection is not required for a modem
connection, clear mdm_auto * to indicate wait
for ring.
Whether break is supported, length of time the
break is to be issued, or if a break string will be
used. Set brknone_ * for no break; brktime_ *
for timed break; brkstri_ * for break string to
be used.
Y Break string length.
Y Break string. Range: 190 characters
Y Number of milliseconds to send break.
Number of stop bits. Use onestopbit * or
twostopbit *.
DTRCall option; set dtr_call * to enable. When
enabled, the PAD raises DTR when an X.25
call is established (prior to the X.28 incoming
call PAD service signal), and lowers DTR
when an X.25 call is cleared (after the clear
confirmation PAD service signal). This option
cannot be specified when SPeed=AUTObaud;
it is also incompatible with DTR input flow
control (if you specify DTR input flow control
with X.28/X.29 commands, DTRCall overrides
it). It also overrides all modem subparameters.
Number of bytes each block mode buffer can
hold. (For full description of block mode
options, see Set Defaults Device command
description in Chapter 4.) Range: 232000
bytes
Number of block mode buffers. Range: 2250
Not currently used.
Y Time between the receipt of the first
character in the block mode buffer and when
the buffer is processed if it is not yet full.
Range: 02000 milliseconds
ASYNCXS
C320001300D0
IO INTERFACE
cmx3typ *
cmx28ty *
cmiact *
cmcallm *
cmsymax *
cmt2val *
ASYNCXS
C320001300D0
X3 type: use x3tele_ * to indicate the full X.3

parameter set and extended Telematics
parameters can be used; use x3c84_ * to
indicate device is limited to standard X.3
parameters.
X28 type: use x28tele_ * to indicate the full
X.28 command set and extended Telematics
commands can be used; use x28c84_ * to
indicate device is limited to standard X.28
commands.
Device initial state: use instoff_ * or instdisa *
to create the device and leave it disabled; use
inston_ *, instcon_ *, or instena * to create and
enable the device.
Type of remote connections that can be
initiated from the device: use calldir_ * to
indicate the X.28 Call command initiates calls
to a remote device, but no called NUA can be
provided with the command (the device
specification must have a called NUA
parameter value, which is used as the
destination address); use callnorm_ * to
indicate remote connections are supported by
SVCs or PVCs, and a called NUA can be used
in the X.28 Call command; use callpvc_ * to
indicate the X.28 Call command cannot be
used, and remote connections use PVCs and
are initiated with the X.28 Connect command;
use callsvc_ * to indicate the X.28 Connect
command cannot be used, and remote
connections use SVCs and are initiated with
the X.28 Call command.
Maximum number of symbols that can be
defined for a device with the Symbol
Assignment command. Range: 0256
Y Timeout value when a device enters X.28
command mode. When the timer expires,
ASYNCXS places the device in data transfer
mode if a call is active. If no call is active, the
device is disabled. A zero value indicates no
timer (i.e., no timeout). Range: 0500 seconds
B13
IO INTERFACE
B14
cmt3val *
cmpbsz *
cmprmpt *
W
16B
cmtypah *
cmfclev *
cmpnmsz *
cmpname *
16B
cmprosz *
cmpronm *
16B
cmsnmsz *
cmsname *
W
87B
cmabsz *
cmasign *
87B
cmoffcl *
cmoffcm *
87B
Y Data transfer mode timer value that starts

when a device enters data transfer mode or
when ASYNCXS completes a write request to
NET25. The timer stops when a read from the
device completes. When the timer expires, the
active call is cleared and the device is disabled.
A zero value indicates no timer (i.e., no
timeout). Range: 0500 minutes
Y Length of prompt message. Range: 016
Y Devices prompt string when it is in
command mode. P6 controls the display of the
prompt. Range: 016 characters (embedded
spaces not allowed)
Number of characters the typeahead buffer can
hold. Range: 12032767
Y Number of character positions remaining
in the typeahead buffer, at which point the PAD
outputs the flow control character (if P5=1 or
2, and output flow control is enabled). The
flow control level should be based on the
device speed and the devices response to a
flow control signal. Range: 032767
Y Length of profile directory name. Range:
116
Y Profile directory name. Range: 116
characters
Y Length of profile name. Range: 116
Y Devices initial or default X.3 profile
name. Range: 116 characters
Length of local signon file name. Range: 087
Name of file containing X.28 commands to be
executed when the device is enabled and signs
on to the PAD. Range: 087 characters
Length of remote signon file name. Range:
087
executed when a PAD device issues a
successful X.28 Call command or successfully
accepts a call. Range: 087 characters
Length of remote signoff file name. Range:
087
executed when an X.25 call to the device is
cleared. Range: 087 characters
ASYNCXS
C320001300D0
IO INTERFACE
For complete descriptions of the X.3 parameter values listed below,

see Chapter 3.
cmx3p00 *
cmx3p01 *
W
W
X.3 P0, not defined

X.3 P1, PAD escape
cmx3p02 *
X.3 P2, echo
cmx3p03 *
cmx3p04 *
W
W
X.3 P3, data forwarding

X.3 P4, idle timer
cmx3p05 *
X.3 P5, ancillary device control
cmx3p06 *
X.3 P6, PAD service signals
cmx3p07 *
cmx3p08 *
W
W
X.3 P7, break action

X.3 P8, discard output
cmx3p09 *
X.3 P9, padding after <CR>
cmx3p10 *
cmx3p11 *
cmx3p12 *
W
W
W
X.3 P10, line folding

X.3 P11, speed
X.3 P12, PAD flow control
cmx3p13 *
cmx3p14 *
W
W
X.3 P13, linefeed after <CR>

X.3 P14, linefeed padding
cmx3p15 *
X.3 P15, editing
cmx3p16 *
cmx3p17 *
W
W
X.3 P16, character delete

X.3 P17, line delete
cmx3p18 *
X.3 P18, line display
cmx3p19 *
cmx3p20 *
W
W
cmx3p21 *
cmx3p22 *
cmx3p23 #1
*
cmx3p24 #2
*
cmx3p25 *
cmx3p26 *
W
W
W
X.3 P19, editing service signals

X.3 P20, echo mask
X.3 P21, parity treatment
X.3 P22, page wait
X.3 P23, data forwarding character
X.3 P24, data forwarding character
W
W
X.3 P25, output delay due to input

X.3 P26, data forwarding interval timer
cmx3p27 *
X.3 P27, padding after tab
cmx3p28 *
cmx3p29 *
W
W
X.3 P28, XOFF character to device

X.3 P29, XON character to device
cmx3p30 *
X.3 P30, XOFF character to PAD
cmx3p31 *
cmx3p80 *
W
W
X.3 P31, XON character to PAD

X.3 P80, signon
ASYNCXS
C320001300D0
B15
IO INTERFACE
cmx3p81 *
X.3 P81, call definition
cmx3p82 *
X.3 P82, alternate break
cmx3p83 *
cmx3p84 *
W
W
X.3 P83, forward character count

X.3 P84, extended read option
cmx3p85 *
X.3 P85, local discard option
cmx3p86 *
cmbilling *
W
34B
cmcurbill *
cmaccnsz *
34B
W
cmaccn *
20B
cmcaccnsz *
cmcaccn *
cmacct *
W
20B
W
cmserv *
cmchg *
cmnui *
X.3 P86, diagnostic echo

Configured Telematics accounting billing
number. Range: 132 digits
Current billing number.
Configured account number size.
Configured Telematics accounting account
number. Range: 020 characters
Length of current account number.
Current account number.
Account type to be used with Telematics
accounting. Range: 0255
Device connection used with Telematics
accounting: use servdial_ * to indicate dial up, use
servdirect_ * to indicate leased line, use
servnone_ * to indicate neither dial up nor leased
line, or other as specified (0255).
Charge type to be used with Telematics
accounting. Range: 0255
NUI validation flag.
The following fields that begin with the characters cmx3c are returned
from an IO/INFO request to obtain device configuration information; they
are not valid for device configuration or modification. For complete
descriptions of X.3 parameter values, see Chapter 3.
B16
cmx3c00 *
cmx3c01 *
cmx3c02 *
cmx3c03 *
B
B
B
B
cmx3c04 *
cmx3c05 *
B
B
cmx3c06 *
cmx3c07 *
Current X.3 P0, not defined; returned in IO/INFO

Current X.3 P1, PAD escape; returned in IO/INFO
Current X.3 P2, echo; returned in IO/INFO
Current X.3 P3, data forwarding; returned in
IO/INFO
Current X.3 P4, idle timer; returned in IO/INFO
Current X.3 P5, ancillary device control; returned
in IO/INFO
Current X.3 P6, PAD service signals; returned in
IO/INFO
Current X.3 P7, break action; returned in
IO/INFO
ASYNCXS
C320001300D0
IO INTERFACE
cmx3c08 *
cmx3c09 *
cmx3c10 *
cmx3c11 *
cmx3c12 *
B
B
cmx3c13 *
cmx3c14 *
cmx3c15 *
cmx3c16 *
B
B
cmx3c17 *
cmx3c18 *
B
B
cmx3c19 *
cmx3c20 *
cmx3c21 *
B
B
cmx3c22 *
cmx3c23 *
B
B
cmx3c24 *
cmx3c25 *
cmx3c26 *
cmx3c27 *
cmx3c28 *
cmx3c29 *
cmx3c30 *
ASYNCXS
C320001300D0
Current X.3 P8, discard output; returned in

IO/INFO
Current X.3 P9, padding after <CR>; returned in
IO/INFO
Current X.3 P10, line folding; returned in
IO/INFO
Current X.3 P11, speed; returned in IO/INFO
Current X.3 P12, PAD flow control; returned in
IO/INFO
Current X.3 P13, linefeed after <CR>; returned in
IO/INFO
Current X.3 P14, linefeed padding; returned in
IO/INFO
Current X.3 P15, editing; returned in IO/INFO
Current X.3 P16, character delete; returned in
IO/INFO
Current X.3 P17, line delete; returned in IO/INFO
Current X.3 P18, line display; returned in
IO/INFO
Current X.3 P19, editing service signal; returned
in IO/INFO
Current X.3 P20, echo mask; returned in IO/INFO
Current X.3 P21, parity treatment; returned in
IO/INFO
Current X.3 P22, page wait; returned in IO/INFO
Current X.3 P23, data forwarding character #1;
returned in IO/INFO
Current X.3 P24, data forwarding character #2;
returned in IO/INFO
Current X.3 P25, output pending; returned in
IO/INFO
Current X.3 P26, data forwarding interval timer;
returned in IO/INFO
Current X.3 P27, padding after tab; returned in
IO/INFO
Current X.3 P28, XOFF character to device;
returned in IO/INFO
Current X.3 P29, XON character to device;
returned in IO/INFO
Current X.3 P30, XOFF character to PAD;
returned in IO/INFO
B17
IO INTERFACE
cmx3c31 *
cmx3c80 *
cmx3c81 *
B
B
cmx3c82 *
cmx3c83 *
cmx3c84 *
cmx3c85 *
cmx3c86 *
cmopm *
cmx25iow *
cmx25ior *
cmsize *
L
L
Current X.3 P31, XON character to PAD; returned

in IO/INFO
Current X.3 P80, signon; returned in IO/INFO
Current X.3 P81, call definition; returned in
IO/INFO
Current X.3 P82, alternate break; returned in
IO/INFO
Current X.3 P83, forward character count;
returned in IO/INFO
Current X.3 P84, extended read option; returned
in IO/INFO
Current X.3 P85, local discard option; returned in
IO/INFO
Current X.3 P86, diagnostic echo; returned in
IO/INFO
Operating mode: use opmpad_ * to indicate PAD
mode, use opmhand_ * to indicate handler mode.
Size of X.25 write. Range: 065535 bytes
Size of X.25 read. Range: 065535 bytes
Parameter buffer size.
B18
ASYNCXS
C320001300D0
IO INTERFACE
IO/CREATE Profile
This subservice defines a set of X.3 parameter values that can be
associated with a device.
Packet
Field
pkthsopt
pktfname
pktfnsiz
pktparam
pktpbsiz
Length
W
L
W
L
W
Contents
Address of profile name buffer
Length of profile name
Address of profile buffer
Byte length of profile buffer; use cpsize. *
Profile Buffer
See Chapter 3 for complete X.3 parameter descriptions and values.
Field
cpx3p00 *
cpx3p01 *
cpx3p02 *
cpx3p03 *
cpx3p04 *
cpx3p05 *
cpx3p06 *
cpx3p07 *
cpx3p08 *
cpx3p09 *
cpx3p10 *
cpx3p11 *
cpx3p12 *
cpx3p13 *
cpx3p14 *
cpx3p15 *
cpx3p16 *
cpx3p17 *
cpx3p18 *
cpx3p19 *
cpx3p20 *
cpx3p21 *
cpx3p22 *
ASYNCXS
C320001300D0
Length
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
Contents
X.3 P0, not defined
X.3 P1, PAD escape
X.3 P2, echo
X.3 P3, data forwarding
X.3 P4, idle timer
X.3 P5, ancillary device control
X.3 P6, PAD service signals
X.3 P7, break action
X.3 P8, discard output
X.3 P9, padding after <CR>
X.3 P10, line folding
X.3 P11, speed
X.3 P12, PAD flow control
X.3 P13, linefeed after <CR>
X.3 P14, linefeed padding
X.3 P15, editing
X.3 P16, character delete
X.3 P17, line delete
X.3 P18, line display
X.3 P19, editing service signals
X.3 P20, echo mask
X.3 P21, parity treatment
X.3 P22, page wait
B19
IO INTERFACE
cpx3p23 *
cpx3p24 *
cpx3p25 *
cpx3p26 *
cpx3p27 *
cpx3p28 *
cpx3p29 *
cpx3p30 *
cpx3p31 *
cpx3p80 *
cpx3p81 *
cpx3p82 *
cpx3p83 *
cpx3p84 *
cpx3p85 *
cpx3p86 *
cpsize *
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
W
X.3 P23, data forwarding character #1

X.3 P24, data forwarding character #2
X.3 P25, output delay due to input
X.3 P26, data forwarding interval timer
X.3 P27, padding after tab
X.3 P28, XOFF character to device
X.3 P29, XON character to device
X.3 P30, XOFF character to PAD
X.3 P31, XON character to PAD
X.3 P80, signon
X.3 P81, call definition
X.3 P82, alternate break
X.3 P83, forward character count
X.3 P84, extended read option
X.3 P85, local discard option
X.3 P86, diagnostic echo
Parameter buffer size
B20
ASYNCXS
C320001300D0
IO INTERFACE
IO/DESTROY
The IO/DESTROY service destroys a device, directory, or profile.
IO/DESTROY Device
This subservice destroys the definition of an IO entity. The PAD releases
all the IO entitys resources (including the channel) to the pool of
available system resources.
Packet
Field
pkthsopt
pktfname
pktfnsiz
Length
W
L
W
Contents
Address of entity name buffer
IO/DESTROY Directory
This subservice deletes a directory. All devices in the directory must be
destroyed before the directory can be destroyed.
Packet
Field
pkthsopt
pktfname
pktfnsiz
Length
W
L
W
Contents
Handler specific option; use typ$dir_ *
Address of directory name buffer
Length of directory name
IO/DESTROY Profile
This subservice deletes a profile specification.
Packet
Field
pkthsopt
pktfname
pktfnsiz
ASYNCXS
C320001300D0
Length
W
L
W
Contents
Address of profile name buffer
Length of profile name
B21
IO INTERFACE
IO/DISMOUNT
The IO/DISMOUNT service removes the definition of the PADs logical
volume. The PAD requires no handler specific fields for this service.
Packet
Field
pktname
B22
Length
8B
Contents
Logical volume name (left justified, space
filled)
ASYNCXS
C320001300D0
IO INTERFACE
IO/EXCHANGE
The IO/EXCHANGE service provides the following subservices:
Defining, modifying, and obtaining logical volume parameters

Modifying device parameters while the device is online
Registering and deregistering for event notification
Passing control between handler and PAD operating modes
Requesting an X.25 connection/disconnection or accepting/rejecting
an incoming X.25 call, as well as requesting incoming call parameters
These services are entity name class requests; unless otherwise noted. The
subservice packet may require a second parameter buffer pktparm2.
Required information is passed in the input pktparam, and information is
returned in the output pktparm2.
ASYNCXS
C320001300D0
B23
IO INTERFACE
IO/EXCHANGE Define Initial Parameters

This subservice defines logical volume parameters. This request should
immediately follow a successful IO/MOUNT request. The name of the
previously mounted logical volume is the entity name.
Packet
Field
pktextyp
pktexopt
pktfnsiz
pktfname
pktpbsiz
pktparam
pktpbsz2
pktparm2
Length
B
B
W
L
W
L
W
L
Contents
Request type number; use ioxvinit_ **
Request class number; use ioxcnam.
Length of parameter buffer; use initsize **
Address of parameter buffer
Length of return parameter buffer; use 0
Address of return parameter buffer; use 0
Input Parameter Buffer

Field
Length
inalrifrev **
inalrfunct **
inalrnmsiz**
inalrname **
W
W
W
V
inx25rev **
initsize **
Contents
Product interface revision; use axsrv1_ *
Function code; use 0
Length of alarm notification entity name
Alarm notification entity name (size specified
in inalrnmsiz **); 90 character maximum
Revision of X25; use f, g, or h
Size of input parameter buffer
* Defined in asyxsuser.in; ** Defined in padiodefs.in
B24
ASYNCXS
C320001300D0
IO INTERFACE
IO/EXCHANGE Modify Initial Parameters

This subservice modifies logical volume level parameters. The name of
the previously mounted logical volume is the entity name.
Packet
Field
pktextyp
pktexopt
pktfnsiz
pktfname
pktpbsiz
pktparam
pktpbsz2
pktparm2
Length
B
B
W
L
W
L
W
L
Contents
Request type number; use ioxrcnf_ **
Length of parameter buffer; use inalrmsize **

Field
Length
inalrifrev **
inalrfunct **
inalrnmsiz**
inalrname **
W
W
W
V
inalrmsize**
Contents
in inalrnmsiz); 90 byte maximum
Base size of input parameter buffer
ASYNCXS
C320001300D0
B25
IO INTERFACE
IO/EXCHANGE Obtain Initial Parameters

This subservice returns the current initial logical volume level parameters.
The name of the previously mounted logical volume is the entity name.
Packet
Field
Length
pktextyp
pktexmopt
pktfnsiz
pktfname
pktpbsiz
pktparam
pktpbsz2
B
B
W
L
W
L
W
pktparm2
Contents
Request type number; use ioxconf_ **
Length of input parameter buffer (exgsize **)
Address of input parameter buffer
Length of return parameter buffer; use
initsize **
Address of return parameter buffer

Field
exgifrev **
exgfunct **
exgsiz **
Length
W
W
Contents
Output Parameter Buffer

Field
Length
inalrifrev **
inalrfunct **
inalrnmsiz**
inalrname **
W
W
W
V
inx25rev **
initsize **
Contents
Product interface revision
Function code
in inalrnmsiz **); 90 byte maximum
Revision of X25
Size of parameter buffer
B26
ASYNCXS
C320001300D0
IO INTERFACE
IO/EXCHANGE Deregister for Event Notification

This subservice disables subsequent entity event reporting to the
notification entity for the file name pointed to by pktfname.
Packet
Field
Length
pktextyp
pktexopt
pktiaddr
B
B
L
pktname
8B
pktpbsiz
pktparam
pktpbsz2
pktparm2
W
L
W
L
Contents
Request type number; use ioxadreg_ **
Request class number; use ioxcfil.
System internal address returned from
IO/OPEN
Logical file name from IO/OPEN request (left
justified, space filled)
Length of parameter buffer (devntsize **)

Field
devntifrev**
devntfunct**
devntkey **
devntsize **
Length
W
W
L
Contents
User event notification key
ASYNCXS
C320001300D0
B27
IO INTERFACE
IO/EXCHANGE Pass Control to Handler Mode

This subservice passes the PADs control to handler mode for the file
pointed to by pktiaddr.
Packet
Field
Length
pktextyp
pktexopt
pktiaddr
B
B
L
pktname
8B
pktpbsiz
pktparam
pktpbsz2
pktparm2
W
L
W
L
Contents
Request type number; use ioxhan_ **
IO/OPEN
Length of parameter buffer (exgsize)
Length of second parameter buffer; use 0
Address of second parameter buffer; use 0

Field
exgifrev
exgfunct
exgsize
Length
W
W
Contents
B28
ASYNCXS
C320001300D0
IO INTERFACE
IO/EXCHANGE Pass Control to PAD Mode

This subservice passes the PADs control to PAD mode for the file pointed
to by pktiaddr. Note that hotksize does not include hotktable.
Packet
Field
Length
pktextyp
pktexopt
pktiaddr
B
B
L
pktname
8B
pktpbsiz
pktparam
pktpbsz2
pktparm2
W
L
W
L
Contents
Request type number; use ioxpad_ **
IO/OPEN
Length of base parameter buffer

Field
hothkifrev *
hothkfunct *
hothktasiz *
hotksize *
Length
W
W
B
V
Contents
Number of hot key entries; use 1
Base of hot key table
Hot Key Table Specification

Field
hotkeysiz *
hotkey *
Length
B
V
Contents
Length of hot key specification
Hot key specification
ASYNCXS
C320001300D0
B29
IO INTERFACE
IO/EXCHANGE Register for Event Notification

This subservice enables subsequent entity events to be reported to the
requesting application for the file name pointed to by pktname. For more
information (including returned event notification format), see the Event
Notification section beginning on page B4.
Packet
Field
Length
pktextyp
pktexopt
B
B
pktiaddr
pktname
8B
pktpbsiz
pktparam
pktpbsz2
pktparm2
L
W
L
Contents
Request type number; use ioxareg_ **
Request class number; use either ioxcnam. or
ioxcfil.
IO/OPEN
Maximum length of parameter buffer; use
revntsize ** plus length of notification entity
name plus 2

Field
Contents
revntifrev **
revntfunct
**
revntkey **
revnt1mask**
W
W

L
L
revnt2mask **
L
L
L
L
L
L
L
Event notification key

Events 310 relative mask (see bit mask list
below)
Events 6332 relative mask
Base size of buffer
revnt3mask **
revnt4mask **
revnt5mask **
revnt6mask **
revnt7mask **
revnt8mask **
revntsize
B30
Length
ASYNCXS
C320001300D0
IO INTERFACE
revntmnmsiz
**
revntmname
**
Length of notification entity name
Notification entity name (size specified in

revntmnmsiz)
revnt1mask Bit Mask

Mnemonic
Description
rev_x25c **
rev_x25d **
rev_x25i **
rev_x25o **
rev_entc **
rev_entonl **
rev_entd **
rev_entoff **
rev_hotkey **
rev_x25t **
rev_x28t **
Register for X.25 connected events

Register for X.25 disconnected events
Register for X.25 incoming call events
Register for X.25 outgoing call requested events
Register for entity connected events
Register for entity online events
Register for entity disconnected events
Register for entity offline events
Register for hot key detected events
Register for X.25 idle timer expired events
Register for X.28 command mode timer expired
events
Register for ControlC character received events
Register for ControlY character received events
rev_ctlc **
rev_ctly **
ASYNCXS
C320001300D0
B31
IO INTERFACE
IO/EXCHANGE Request X.25 Connection/Accept Incoming X.25 Call

This subservice requests either an X.25 call request to be issued, or
accepts an incoming X.25 call by the PAD for the file pointed to by
pktiaddr. The handler specific option indicates the request or acceptance;
pktparm contains the parameters needed to make the call; pktpbsiz
indicates the parameter buffer size. Upon successful completion, the PAD
updates the parameter buffer with the X.25 call accept parameters in
pktparm2. An unsuccessful completion indicates an X.25 reject of the call
or an inability to accept the incoming call.
If the hop_pad option is not used, the PAD remains in handler mode until
the application issues an IO/EXCHANGE Pass Control to PAD Mode
request.
The cparsize value does not include cparps1 or cparps2.
Packet
Field
Length
pkthsopt
pktextyp
pktexopt
pktiaddr
B
B
L
pktname
8B
pktpbsiz
pktparam
pktpbsz2
L
W
pktparm2
Contents
Handler specific options; set
hop_cal ** to request an X.25 connection,
hop_acc ** to accept an incoming X.25 call,
hop_pad ** to allow handler to go directly to
PAD mode once the call is accepted
Request type number; use ioxx25c_ **
IO/OPEN
Maximum length of base parameter buffer
(cparsize ** plus length of cparps2, plus 2)
Length of second base parameter buffer
(cparsize ** plus length of cparps2, plus 2)
Address of second parameter buffer
Call Parameter Buffer

Note that ASYNCXS does not use all the fields described below. See the
NET25 Manual for parameter and facility descriptions.
Field
cparifrev **
cparfunct **
cparopt **
B32
Length
W
W
W
Contents
Option field; use cpa_parm **
ASYNCXS
C320001300D0
IO INTERFACE
cpartype **
cparaserv **
cparachid **
cparacnsz **
cparacn **
cparbnsz **
cparbn **
cparprod **
cparport **
cparfpd1 **
cparfpd2 **
cparcdsz **
cparcd **
cparcgsz **
cparcg **
cparfopt **
cpartxpsz **
cparrxpsz **
cpartxwsz **
cparrxwsz**
cpartxtc **
cparrxtc **
cparrqtdy **
cpartxprio**
cparrxprio**
cparlcug **
cparicug **
cparlnksz **
cparlink **
cparlc **
cparctyp **
cparrful **
cpardopt **
cparcdesz **
cparcde **
cparcgesz **
cparcge **
cparmtxtc **
ASYNCXS
C320001300D0
B
B
B
B
20B
B
16B
W
W
W
W
B
16B
B
16B
L
W
W
W
W
W
W
W
B
B
4B
4B
W
16B
W
B
B
L
B
20B
B
20B
W
Account type
Account service type
Account charge indicator
Account number field length
Account number
Billing number field length
Billing number
Product type
Access port number
File product specific field 1
File product specific field 2
Called address length
Called address
Calling address length
Calling address
Facilities field (see list)
Transmit packet size
Receive packet size
Transmit window size
Receive window size
Transmit throughput class
Receive throughput class
Transit delay selected/indicated
Transmit priority
Receive priority
Closed User Group (CUG) selection
CUG interlock code
Link name length
Link name
PVC or SVC logical channel number
Connection type required
Word alignment
DTE facilities options field
Called address extension length
Called address extension
Calling address extension length
Calling address extension
Minimum acceptable transmit transfer count
B33
IO INTERFACE
cparmrxtc **
cparcmtdy**
cparretdy **
cparmxtdy**
cparexpdn**
cparcallid **
cparusrkey**
cparrssz **
cparrs **
cparrsn **
cparcause **
cpardiag **
cparncgsz **
cparncgid **
cparpwsz **
cparpw **
cparncdsz **
cparncdid **
cparnuisz **
cparnui **
cparsize **
cparps1 **
cparps2 **
W
W
W
W
B
L
L
B
16B
B
B
B
W
20B
W
10B
W
20B
W
16B
W
V
Minimum acceptable receive transfer count

Cumulative endtoend transit delay
Requested endtoend transit delay
Maximum acceptable endtoend transit delay
Expedited data negotiated
Network layer call ID
User supplied call key
Responding address size
Responding address
Reason for address difference
Cause code
Diagnostics code
Calling ID length
Calling NUI ID
Calling password length
Calling password
Called ID length
Called NUI ID
NUI length
NUI
Base size of structure
Length of call user data
Call user data (maximum 124 characters), size
specified in cparps1 **
Facilities
The following facility bits can be used in the cparfopt field.
B34
Mnemonic
Value
cfc_ffs **
cfc_ffsr **
cfc_fpsn **
cfc_fwsn**
cfc_ftcn **
cfc_fac **
cfc_frc **
cfc_fic **
cfc_fog **
cfc_crn **
0
1
2
3
4
5
6
7
8
9
Description
Fast select
Fast select restricted
Packet size negotiation
Window size negotiation
Throughput class negotiation
Accounting required
Reverse charge required
Incoming calls accepted
Outgoing calls accepted
Call redirection notification
ASYNCXS
C320001300D0
IO INTERFACE
cfc_cchi **
cfc_clamn **
cfc_nui **
10
11
12
cfc_lcp **
cfc_rpoa **
cfc_cug **
cfc_cugo**
cfc_bug **
13
14
15
16
17
cfc_rej **
cfc_fsa **
cfc_exn **
18
19
20
cfc_c84 **
cfc_tds **
cfc_cir **
cfc_dbn **
cfc_dbtxm **
cfc_dbrxm **
cfc_rca **
cfc_crna **
cfc_tdi **
21
22
23
24
25
26
27
28
29
Call charge indication (reserved for future)

Called address modification
NUI validation subscribed to (reserved for
future)
Local charge prevention
RPOA selection (reserved for future)
CUG selection
CUG with outgoing access
Bilateral CUG selection (reserved for
future)
Reject option subscribed
Fast select acceptance
Expedited data negotiation (reserved for
future)
CCITT 1984 interface supported
Transit delay selection
Call information request facility
D bit negotiation required (call related)
D bit modification (transmit link)
D bit modification (receive link)
Reverse charge acceptance
Call redirection notification acceptance
Transit delay selection
ASYNCXS
C320001300D0
B35
IO INTERFACE
IO/EXCHANGE Request X.25 Disconnection/Reject Incoming X.25 Call

This subservice requests either an X.25 call clear to be issued or rejects an
incoming X.25 call request by the PAD for the file pointed to by pktiaddr.
X.25 connections are cleared or reset according to protocol. The input
parameter buffer contains the X.25 call clear cause, X.25 diagnostic, and
clear user data. (Chapter 6 lists cause and diagnostic codes.)
When an X.25 disconnection completes, the PAD returns to handler mode,
and IO/READs and IO/WRITEs are permitted.
The ccrsize value does not include ccrudsiz or ccrudata.
Packet
Field
Length
pkthsopt
pktextyp
pktexopt
pktiaddr
B
B
L
pktname
8B
pktpbsiz
pktparam
pktpbsz2
pktparm2
L
W
L
Contents
Handler specific options; set either:
hop_dis ** to request an X.25 disconnection,
or hop_rej ** to reject an X.25 incoming call
Request type number; use ioxx25d_ **
IO/OPEN
Maximum length of parameter buffer
(ccrsize** plus length of clear user data plus 2)

Field
ccrifrev **
ccrfunct **
ccrcause **
ccrdiagn **
ccrsize **
ccrudsiz **
ccrudata **
Length
W
W
B
B
W
V
Contents
X.25 cause code
X.25 diagnostic code
Base size of structure
Size of clear user data
Clear user data
B36
ASYNCXS
C320001300D0
IO INTERFACE
IO/EXCHANGE Request Incoming Call Parameters

This subservice collects the X.25 call parameters received on an incoming
call request for the file pointed to by pktiaddr. On return, the PAD updates
the parameter buffer pktparm2 with the incoming X.25 call parameters.
The cparsize value does not include cparps1 or cparps2.
Packet
Field
Length
pktextyp
pktexopt
pktiaddr
B
B
L
pktname
8B
pktpbsiz
pktparam
pktpbsz2
W
L
W
pktparm2
Contents
Request type number; use ioxx25r_ **
IO/OPEN
Length of parameter buffer (exgsize **)
Length of second parameter buffer
(cparsize **)
Address of second base parameter buffer
Input Buffer
Field
exgifrev **
exgfunct **
exgsize **
Length
W
W
Contents
Output Buffer
The returned parameter buffer contains the information that is used for the
IO/EXCHANGE Request an X.25 Connection/Accept Incoming X.25 Call
subservice; see the list beginning on page B32.
ASYNCXS
C320001300D0
B37
IO INTERFACE
IO/EXCHANGE Modify Device Parameters While Online

This subservice modifies device parameters while the device is online.
You should issue an IO/INFO Obtain Device Statistics subservice request
to verify current values before changing them.
Packet
Field
Length
pktextyp
pktexopt
pktfname
pktfnsiz
pktname
B
B
L
W
8B
pktpbsiz
pktparam
pktpbsz2
pktparm2
W
L
W
L
Contents
Request type number; use ioxmdev_ **
Length of parameter buffer (cmsize *)

The parameter buffer contains information that is used for the
IO/CREATE Create Device subservice; see the list beginning on page
B10.
Note that only those parameters with the graphic can be modified while
the device is online. If nononlinemodifiable parameters are specified,
they are ignored.
B38
ASYNCXS
C320001300D0
IO INTERFACE
IO/INFO
The IO/INFO service provides the following information retrieval
subservices:
Detailed entity properties

Device status
Entity names
Device or profile configurations
Device statistics
PADmap table
Async IO configuration
TRAX does not use pktiaddr for name class IO. To avoid the chance of
error, Telematics recommends that that field not be provided.
IO/INFO Obtain Detailed Entity Properties
This subservice returns the properties of a volume, directory, device, or
profile.
Packet
Field
pktimopt
pktimtyp
pktfname
pktfnsiz
pktparam
pktpbsiz
Length
B
B
L
W
L
W
Contents
Type selection index; use ioidepr.
Address of return information buffer
Byte length of return information buffer; use
ioibsize
Return Information Buffer

Field
ioibflag
ioibdevt
ioibdtyp
ioibbsiz
ioibmblk
ioibmint
ioibmaxt
ioibhdef
ioibsize
ASYNCXS
C320001300D0
Length
W
B
B
L
L
L
L
2L
Contents
Definition flags
Device type; use typterm.
Data type
Block size (fixed block entities)
Max. number of blocks/transfer (fixed block)
Minimum read buffer size in bytes (variable)
Maximum transfer count in bytes
Hander defined information
Size of structure
B39
IO INTERFACE
IO/INFO Obtain Device Status

This subservice obtains the current status (online, offline, or in use) for a
volume, directory, device, or profile. In reality, this is only meaningful for
a device.
Packet
Length
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pktrvalu
B
L
W
B
L
Contents
Type selection index; use ioigdst.
Return status from TRAX
IO/INFO Obtain Entity Names

This subservice returns a list of device names in a directory.
Packet
Field
Length
pktimopt
pktfname
pktfnsiz
pktimtyp
pktparam
pktpbsiz
B
L
W
B
L
W
Contents
Type selection index; use ioinam_ *
Byte length of return information buffer; each
entry requires 20 bytes
Buffer Format for Each Entity Name Returned

Length
16B
W
W
B40
Contents
Entity name
Device type
Device state
ASYNCXS
C320001300D0
IO INTERFACE
IO/INFO Obtain Device Configuration

This subservice obtains the current device configuration information.
Packet
Field
pktimopt
pktimtyp
pktfname
pktfnsiz
pkthsopt
pktparam
pktpbsiz
Length
B
B
L
W
W
L
W
Contents
Type selection index; use ioicfg_ *
Byte length of return buffer; use cmsize *
Return Parameter Buffer

The returned parameter buffer contains the information that is used for the
IO/CREATE Create Device subservice, plus current X.3 parameter values;
see the list beginning on page B10.
IO/INFO Obtain Profile Configuration

This subservice obtains the current profile parameters.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pkthsopt
pktparam
pktpbsiz
Length
B
L
W
B
W
L
W
Contents
Byte length of return buffer; use cpsize *
Return Information Buffer

The return information buffer contains the information that is used for the
IO/CREATE Create Profile subservice; see the list beginning on page
B19. See Chapter 3 for complete X.3 parameter descriptions and values.
ASYNCXS
C320001300D0
B41
IO INTERFACE
IO/INFO Obtain Device Statistics

This subservice obtains a devices statistics.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pktparam
pktpbsiz
Length
B
L
W
B
L
W
Contents
Type selection index; use ioista_ *
ctsize *
Statistics Buffer
Field
ctname *
cttype *
ctstate *
ctcstat *
ctlsiz *
ctlnua *
ctrsiz *
ctrnua *
ctpsiz *
ctplnk *
ctplcn *
ctocnt *
cticnt *
ctctime *
cttcnt *
ctrcnt *
cttres *
ctrres *
cttint *
ctrint *
ctocall *
cticall *
ctframe *
B42
Length
4L
W
W
W
W
16B
W
16B
W
16B
W
L
L
L
L
L
L
L
L
L
L
L
L
Contents
Device name
Device type; use typ$term_ *
Device state
Call status/direction
Local NUA size
Local NUA
Remote NUA size
Remote NUA
PVC link name size
PVC link name
PVC logical channel number
Output byte count
Input byte count
Time connected (milliseconds) or 0
X.25 writes issued by PAD
X.25 reads issued by PAD
X.25 resets issued by PAD
X.25 resets received by PAD
X.25 interrupts issued by PAD
X.25 interrupts received by PAD
Calls issued
Calls received
Async framing errors
ASYNCXS
C320001300D0
IO INTERFACE
ctpari *
ctoverf *
ctbreak *
ctsize *
L
L
L
Async parity errors

Async overflow errors
Async breaks received
Statistics buffer size
IO/INFO Obtain PADmap Table

This subservice returns the current PADmap table. See page 221 for
information about how the PADmap is used for incoming call routing.
Packet
Field
pktimopt
pktimtyp
pktfname
pktfnsiz
pkthsopt
pktparam
pktpbsiz
Length
B
B
L
W
W
L
W
Contents
Type selection index; use ioismp_ *
Buffer number
mapssize *
Return Buffer
Field
maphfptr *
maphcnt *
Length
L
W
Contents
Address of next PADmap buffer
Number of entries in this buffer
Cell entries start here
PADmap Cell Structure

Field
Length
mapnual *
mapnua *
mapcudl *
mapcud *
maptype *
mapport1 *
B
16B
B
13B
B
W
mapport2 *
mapcsize *
mapssize *
ASYNCXS
C320001300D0
Contents
Called NUA length (without null)
Called NUA (null terminated)
Call user data length (without null)
Call user data (null terminated)
Type of port mapping (see list below)
First port (see maptype definitions list below
for meaning)
Second port
Size of map cell
Size of map structure
B43
IO INTERFACE
maptype Definitions
Mnemonic
maptinv_ *
maptstar_ *
maptrang_ *
maptcud_ *
maptnua_ *
Value Description
1
0
1
2
3
Entry has been deleted

Exact match calling NUA with PADmap NUA
Range of port numbers: port1port2
Port number is in CUD; use mapcud for wildcard
Low order digits of incoming call NUA contain
port number; mapport1 = number of digits
IO/INFO Obtain Async IO Configuration

This subservice returns the current async IO configuration information.
See the IO/MODE Modify Async IO Configuration (page B52) for
control character processing table information.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pktparam
pktpbsiz
Length
B
L
W
B
L
W
Contents
acnfsize *
Return Buffer
Field
acnfccprov *
acnfsize *
Length
32B
Contents
Control character processing table
Size of structure
B44
ASYNCXS
C320001300D0
IO INTERFACE
IO/MODE
The IO/MODE service provides the following subservices:
Enabling and disabling a device

Modifying a device or profile
Resetting a devices statistics
Adding and deleting PADmap entries
Enabling and disabling task exceptions
Modifying the asynchronous IO configuration
IO/MODE Enable Device
This subservice sets a devices status so that it can be signed on. When a
device is enabled, the PAD begins any defined signon procedures.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
Length
B
L
W
B
Contents
Class selection index; use iomcnam.
Type selection index; use iomenb_ *
IO/MODE Disable Device

This subservice disables a device and signs it off from the PAD. If a call is
active to the device, it is cleared.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
Length
B
L
W
B
Contents
Type selection index; use iomdisa_ *
ASYNCXS
C320001300D0
B45
IO INTERFACE
IO/MODE Modify Device

This subservice changes one or more parameters for an asynchronous
device connected to the PAD. The device must be disabled before changes
are allowed. You should issue an IO/INFO Obtain Device Statistics
subservice request to verify current values before changing them.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pkthsopt
pktparam
pktpbsiz
Length
B
L
W
B
W
L
W
Contents
Type selection index; use iommod_ *
Handler specific option; use type$term_ *
Byte length of parameter buffer; use cmsize *
Parameter Buffer
The parameter buffer can contain the information that is used for the
IO/CREATE Create Device subservice; see list beginning on page B10.
IO/MODE Modify Profile
This subservice changes one or more profile parameters for an
asynchronous device connected to the PAD.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pkthsopt
pktparam
pktpbsiz
Length
B
L
W
B
W
L
W
Contents
Type selection index; use iommod_ *
Handler specific option; use type$prof_ *
Byte length of parameter buffer; use cpsize *
Parameter Buffer
The parameter buffer can contain the information that is used for the
IO/CREATE Create Profile subservice; see the list beginning on page
B19. See Chapter 3 for complete X.3 parameter descriptions and values.
B46
ASYNCXS
C320001300D0
IO INTERFACE
IO/MODE Reset Statistics

This subservice clears a devices statistics.
Packet
Field
Length
pktname
8B
pktimtyp
pktiaddr
B
L
Contents
Type selection index; use iomres_ *
IO/OPEN
ASYNCXS
C320001300D0
B47
IO INTERFACE
IO/MODE Add PADmap Entry

This subservice adds an entry to the PADmap table. See page 221 for
information about how the PADmap is used for incoming call routing.
Packet
Field
Length
pktimopt
pktfname
pktfnsiz
pktimtyp
pktparam
pktpbsiz
B
L
W
B
L
W
Contents
Type selection index; use iomadm_ *
Byte length of parameter buffer; use mapcsize*
Map Cell Structure

Length
Field
mapnual *
mapnua *
mapcudl *
mapcud *
maptype *
mapport1 *
B
16B
B
13B
B
W
mapport2 *
mapcsize *
Contents
for meaning)
Second port
Size of map cell
maptype Definitions
Mnemonic
maptinv_ *
maptstar_ *
maptrang_ *
maptcud_ *
maptnua_ *
Value Description
1
0
1
2
3

B48
ASYNCXS
C320001300D0
IO INTERFACE
IO/MODE Delete PADmap Entry

This subservice removes an entry from the PADmap table. See page 221
for information about how the PADmap is used for incoming call routing.
Packet
Field
Length
pktimopt
pktfname
pktfnsiz
pktimtyp
pktiaddr
B
L
W
B
L
pktparam
pktpbsiz
L
W
Contents
Type selection index; use iomdem_ *
IO/OPEN
Byte length of parameter buffer; use mapcsize*
Map Cell Structure

Length
Field
mapnual *
mapnua *
mapcudl *
mapcud *
maptype *
mapport1 *
B
16B
B
13B
B
W
mapport2 *
mapcsize *
Contents
for meaning)
Second port
Size of map cell
maptype Definitions
Mnemonic
maptinv_ *
maptstar_ *
maptrang_ *
maptcud_ *
maptnua_ *
Value Description
1
0
1
2
3

ASYNCXS
C320001300D0
B49
IO INTERFACE
IO/MODE Delete All PADmap Entries

This subservice deletes all entries from the PADmap table. See page 221
for information about how the PADmap is used for incoming call routing.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
Length
B
L
W
B
Contents
Type selection index; use iomdea_ *
B50
ASYNCXS
C320001300D0
IO INTERFACE
IO/MODE Enable/Disable Task Exception Processing

This subservice enables or disables task exception processing. By default,
task exception processing is enabled.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pkthsopt
Length
B
L
W
B
W
Contents
Type selection index; use iomtskexc_ *
Handler specific option; set one of:
hop_dreg ** to disable task exception
processing
hop_reg ** to enable task exception processing
Sample Exception
When exception processing is enabled and an exception is detected, the
following information is displayed on the operator console:
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
<time>
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
asyncxs
ASYNCXS has received an exception

Registers at exception:
D0D3: <hex_value> <hex_value> <hex_value> <hex_value>
D4D7: <hex_value> <hex_value> <hex_value> <hex_value>
A0A3: <hex_value> <hex_value> <hex_value> <hex_value>
A4A7: <hex_value> <hex_value> <hex_value> <hex_value>
Exception information:
PC at exception: Instruct+<hex_value>
Exception type=<hex_value>,
CCR at exception: <hex_value>
Instruction Ranges:
Instruct Start:<hex_value>
l2asylib Start:<hex_value>
l1asylib Start:<hex_value>
l1suplib Start:<hex_value>
gplib
Start:<hex_value>
Size:
Size:
Size:
Size:
Size:
<hex_value>
<hex_value>
<hex_value>
<hex_value>
<hex_value>
Stack at exception:
<hex_value> <hex_value> <hex_value> <hex_value>
Service
Pkt
Pkt+$10
Pkt+$20
Pkt+$30
Queue Read Packet:

After the exception is reported, ASYNCXS cleans up the stack and reads
its service queue.
ASYNCXS
C320001300D0
B51
IO INTERFACE
IO/MODE Modify Async IO Configuration

This subservice modifies the current async IO configuration. The control
character processing table is a 32 byte field in which each byte
corresponds to a single ASCII control character in the range $00$1F. The
value of each byte, represented by a control character processing option
mnemonic, specifies the type of operation to be performed if the PAD
detects the corresponding control character in the input data stream while
in handler mode.
Packet
Field
pktimopt
pktfname
pktfnsiz
pktimtyp
pktparam
pktpbsiz
Length
B
L
W
B
L
W
Contents
Type selection index; use iomacnf_ *
Byte length of return buffer; use acnfsize *
Return Buffer
Field
acnfccproc *
acnfsize *
Length
32B
Contents
Control character processing table
Size of structure
Control Character Processing Options

Mnemonic
Description
ccctla_ *
ccctlb_ *
ccctlc_ *
Toggle terminal insert mode for command editing

Cursor to start of command line for command editing
ControlC processing. If specified, and that character
is detected in the input stream, the typeahead buffer is
purged, the ControlO state is reset, and any
IO/READ and IO/WRITE in progress are completed
(reads are completed with a transfer count of zero).
Cursor to end of command line for command editing
Delete character
Tab
Line feed
Vertical tab
Form feed
Record terminator
ccctle_ *
ccctlh_ *
ccctli_ *
ccctlj_ *
ccctlk_ *
ccctll_ *
ccctlm_ *
B52
ASYNCXS
C320001300D0
IO INTERFACE
ccctlo_ *
ccctlq_ *
ccctlr_ *
ccctls_ *
ccctlu_ *
ccctlx_ *
ccctly_ *
ccctlz_ *
ccigno_ *
ccnctl_ *
ccnuse_ *
cctext_ *
ControlO processing. If specified, and that character

is detected in the input stream, any output in progress
is terminated, and the string ^O is written to indicate a
premature termination. While in this state, all
IO/WRITE operations are terminated as if normally
written. The following conditions reset the ControlO
state:
An IO/READ is issued.
An IO/WRITE with hwop_cor * set in the pkthsopt
field.
A ControlC character detected in the input stream.
A ControlY character detected in the input stream.
XON release transmission
ControlR processing. If specified, and that character
is detected in the input stream, the PAD redisplays the
logical read prompt (if any) on the next line, along
with the data that has been previously received.
XOFF hold transmission
ControlU processing. If specified, and that character
is detected in the input stream, the PAD purges the
current input buffer, and the users prompt (if any) is
displayed on the next line.
ControlX processing. If specified, and that character
is detected in the input stream, the PAD purges the
typeahead and current input buffers, and the users
prompt (if any) is displayed on the next line.
ControlY processing. If specified, and that character
is detected in the input stream, the typeahead buffer is
purged, the ControlS state is reset, and any
IO/READ and IO/WRITE in progress are completed
(reads are completed with a transfer count of zero).
End of file. If specified, and that character is detected
in the input stream, the PAD treats it as a record
terminator, displays ^Z, and completes the IO/READ
in progress with an scceof. completion code.
Ignore, discard character
Printable character
No special operation; store character
Use Telematics standard text format on input
ASYNCXS
C320001300D0
B53
IO INTERFACE
Default Control Character Processing Table
B54
Index
Default
Index
Default
$00
$01
$02
$03
$04
$05
$06
$07
$08
$09
$0A
$0B
$0C
$0D
$0E
$0F
ccnuse_
ccctla_
ccctlb_
ccctlc_
ccnuse_
ccctle_
ccnuse_
ccnctl_
ccctlh_
ccctli_
ccctlj_
ccctlk_
ccctll_
cctext_
ccnuse_
ccctlo_
$10
$11
$12
$13
$14
$15
$16
$17
$18
$19
$1A
$1B
$1C
$1D
$1E
$1F
ccnuse_
ccctlq_
ccctlr_
ccctls_
ccnuse_
ccctlu_
ccnuse_
ccnuse_
ccctlx_
ccctly_
ccctlz_
ccnctl_
ccnuse_
ccnuse_
ccnuse_
ccnuse_
ASYNCXS
C320001300D0
IO INTERFACE
IO/MOUNT
The IO/MOUNT service mounts a logical volume and claims a
Communications Processor (CP) activity queue. The CP uses this activity
queue to notify the PAD of CPrelated event/exception conditions. A
successful IO/MOUNT request initializes the CP and handler offsets in the
activity queue, and enables interrupts. The calling task must have software
privilege to use this service.
Packet
Field
Length
pktdvtyp
pktname
W
8B
pktmtsqn
2L
ASYNCXS
C320001300D0
Contents
Entity type; use typinfbase.+1
Logical volume name (left justified, space
filled)
Name of PADs service queue
B55
IO INTERFACE
IO/OPEN
The IO/OPEN service opens a local IO entity, and optionally allows the
calling task to register for event notification. The IO entity name
represents a physical pair of input and output channels. Multiple tasks can
be open to an IO entity simultaneously. All logical files under the PAD are
created with read and write access.
Packet
Field
Length
pktssopt
pkthsopt
pktiaddr
pktname
8B
pktfnsiz
pktfname
pktpbsiz
W
L
W
pktparam
pktrvalu
L
L
Contents
Access options; to request exclusive access, set
sop.excl
Handler specific option; to register for events,
set hop_evnt **
On return, internal pointer for subsequent IO
requests
Logical access name (left justified, space
filled)
Size of optional event registration buffer
(revntsize **), or zero
Address of parameter buffer, or zero
On return from this service, the state of the
connection; see list below
Event Registration Parameter Buffer

The event registration parameter buffer contains the same information that
is used for the IO/EXCHANGE Register for Event Notification
subservice; see the list on page B30.
State Connection Return Values
Mnemonic
dstoffline_ *
dstenable_ *
dstsignon_ *
dstconnect_*
dstonline_ *
Value Description
0
1
2
3
4
Offline (disabled) state

Enabled, pending connection
Connected, pending signon
X.28 command mode
Data transfer state
B56
ASYNCXS
C320001300D0
IO INTERFACE
IO/READ
This service transfers data from an IO entity to a buffer. The calling task
may select any of the following options for each IO/READ request:
Lowercase to uppercase character conversion.

Echo disable.
Purge the typeahead buffer.
Timeout terminate the IO/READ operation. This is a percharacter
timer, rather than a timer set for the entire read operation. If the
timeout period expires, the PAD terminates the read with a sccait.
system completion code and a return value represented by artime_. To
select this option, the calling task must set the appropriate bit in the
pkthsopt field and specify the timer duration in the read parameter
buffer. A timer value of zero can be specified to obtain the current
contents of the typeahead buffer.
Read with prompt. This option writes the contents of the secondary
buffer to the IO entity before the read operation. To enable this option,
the calling task defines the secondary buffer by specifying an address
and byte length for it.
Passall mode. This option accepts all control characters without

interpretation, except for those control characters specified as logical
read terminators. In passall mode, the read terminates when the
primary buffer is full, or when a logical read terminator is detected.
Note that if the calling task does not specify a logical read terminator
mask, all control characters are treated as logical read terminators.
Logical read terminators. This option specifies control characters as

logical read terminators. The parameter buffer must contain the logical
read terminator mask and size. Each bit in this mask corresponds to an
ASCII character, beginning with $00 and ending with the last selected
character. To select a particular control character as a logical read
terminator, the calling task must set the corresponding bit in the mask.
The ControlZ character cannot be used as an endoffile character if
it is specified as a logical read terminator, so its use as such is not
recommended unless another character is defined as an endoffile
character.
If the calling task does not specify a logical read terminator mask, all
control characters are treated as logical read terminators. A mask size
of one (L) indicates that no control characters are interpreted as logical
read terminators.
Logical read terminator characters are echoed (if echo is enabled) as
they are received, with the exception of the ESC character, which is
echoed as a dollar sign ($). The calling task may select the option to
inhibit the echo of logical read terminators.
ASYNCXS
C320001300D0
B57
IO INTERFACE
The PADs logical volume may be opened and read.

A read request may terminate normally if the byte count reaches zero. In
this case, the system completion code field (pktccode) and return value
field (pktrvalu) are both set to zero.
Packet
Field
Length
pktfname
pktfnsiz
pkthsopt
L
W
W
pktiaddr
pktbf2ad
pktbf2ct
pktdpbad
pktdpbsz
Contents
Handler specific options; set any of the
following:
hrop_pur ** purge typeahead buffer before
the read
hrop_tim ** enable timeout feature using
value specified in parameter buffer
hrop_low * convert lowercase characters to
uppercase
hrop_nec * disable echo
hrop_pas * use passall mode
hrop_tne * inhibit echo of logical read
terminator characters
IO/OPEN
If using read with prompt option, address of
secondary buffer containing the prompt; else
zero
If using read with prompt option, byte length of
secondary buffer containing the prompt; else
zero
If using logical read terminators and/or timeout
options, address of parameter buffer; else zero
If using logical read terminators and/or timeout
options, byte length of parameter buffer; else
zero (use arpbsize * with logical read
terminators option)
B58
ASYNCXS
C320001300D0
IO INTERFACE
Parameter Buffer
This buffer is used to define a logical read terminator mask and/or a
timeout value.
Field
Length
arpbtime *
arpbtrsz *
arpbmask *
arpbsize *
32B
Contents
Read timeout value in milliseconds (0 to
2321); else zero; note that timer granularity is
configurable (default = 500 ms)
Byte length of logical read terminator mask;
else zero
Read terminator mask
Mnemonics for Info Returned on Abnormal IO Termination

If the read request returns with an sccait. system completion code, the
pktrvalu field indicates the cause of the abnormal termination:
Mnemonic
Description
axsrctlc_ *
Read ended with a control character for which

ControlC processing was selected
ControlO processing was selected
ControlY processing was selected
Operation was terminated due to a full buffer
Operation was terminated due to a timeout
Operation was terminated due to modem hangup
Operation was terminated due to the device being
disabled
axsrctlo_ *
axsrctly_ *
axsrbuff_ *
axsrtime_ *
axsrhang_ *
axsrserv_ *
ASYNCXS
C320001300D0
B59
IO INTERFACE
IO/RESET
The IO/RESET service cancels specific types or all of the outstanding data
server requests for a logical file.
Packet
Field
B60
Length
pktname
8B
pktssopt
pktiaddr
Contents
Subservice options; set any of the following:
sop.rii inhibit reset of reads in progress
sop.rio inhibit reset of writes in progress
sop.rqi inhibit reset of queued reads
sop.rqo inhibit reset of queued writes
A zero value resets all reads and writes
(queued and in progress)
IO/OPEN
ASYNCXS
C320001300D0
IO INTERFACE
IO/WRITE
The IO/WRITE service transfers data from a buffer to an IO entity. The
calling task can specify prefix and postfix values for the output data by
providing the address and length of a parameter buffer (which must be at
least four bytes long). The PAD does not support a secondary buffer for
IO/WRITE.
Packet
Field
Length
pktfname
pktfnsiz
pktssopt
L
W
W
pkthsopt
pktiaddr
pktdpbad
pktdpbsz
Contents
Subservice option; to indicate data chained
operation, set sop.dchn
Handler specific options; set any of the
following:
hwop_cor * reset ControlO state before
processing write request
hwop_txb * current request is not a write but
a break; the parameter buffer specifies the
duration
IO/OPEN
Address of parameter buffer (if using prefix
and postfix values, or if write is a break); else
zero
Byte length of parameter buffer (if using prefix
and postfix values, or if write is a break; use
awpbsize *); else zero
ASYNCXS
C320001300D0
B61
IO INTERFACE
Parameter Buffer
This parameter buffer is used to specify prefix and postfix values, or a
break duration if the IO/WRITE request is actually a break.
Field
Length
awpbprec *
awpbposc *
awpbpre *
awpbpos *
awpbtxb *
awpbsize *
Contents
Number of repetitions (0255) of prefix value;
else zero
Number of repetitions (0255) of postfix value;
else zero
Prefix; specify one of:
afixnil_ * null operation
afixcr_ * carriage return
afixlf_ * line feed
afixff_ * form feed
afixnl_ * newline
Else, zero
Postfix; use one of the mnemonics listed for
the awpbpre field; else zero
Duration of break in milliseconds; else zero
Mnemonics for Info Returned on Abnormal IO Termination

If the write request returns with an sccait. system completion code, the
pktrvalu field indicates the cause of the abnormal termination:
Mnemonic
Description
axsctlc_ *
Write ended with a control character for which

ControlC processing was selected
ControlO processing was selected
ControlY processing was selected
Operation was terminated because a task requested
the IO/RESET subservice for the logical access
Operation did not start because the device was out of
service
axsctlo_ *
axsctly_ *
axsrset_ *
axsserv_ *
B62
ASYNCXS
C320001300D0
IO INTERFACE
Return Values/Errors
pktrvalus
ASYNCXS can return the following pktrvalus:
Value
$10001
$10002
$10003
$10004
$10005
$10006
$10007
$10008
$10009
$1000A
$1000B
$1000C
$1000D
$1000E
$1000F
$10010
$10011
$10012
ASYNCXS
C320001300D0
Meaning
The PMM is incompatible with the PAD
Conflicting parameters: AUTOBAUD is invalid with
DTRCALL
Conflicting parameters: DTRCALL is invalid with
DTR flow control
An attempt was made to create or modify a device
with an invalid profile parameter
An error occurred on async online
An error occurred when allocating memory for
changing DI to block mode async input
The X25 revision was not specified in the command
or by a Define Initial command
The operating mode changed to PAD; an IO request
was terminated
The operating mode changed to HANDLER; an IO
request was terminated
No incoming call has been received
No call is active
Multiple Define Initial command calls are not valid
An attempt was made to create or modify a device
with an invalid X.3 parameter
Device cannot be enabled; a disable is in progress
A call was placed/accepted; the return buffer size is
invalid
The call user data length was greater than 16 on
nonFS/FSR call
Attempting to place a call; a call is already active
Attempting to place a call; a call is in progress
B63
IO INTERFACE
Errors
The following errors can be returned:
Mnemonic
Meaning
sccnxst.
sccexst.
sccuse.
scchie.
sccparm.
sccmem.
sccoptn.
The specified IO entity does not exist

The specified IO entity already exists
The specified IO entity is currently in use
A handler internal error occurred
A parameter buffer error occurred
A memory allocation error occurred
The channel number of IO entity named specified in
the IO/CREATE is invalid
The specified device type is not supported
The handler key is in error
An invalid name format was specified
An invalid return information buffer was provided
An invalid IO/INFO type was specified
The user buffer is too small
The specified communications processor activity
queue number is invalid
The resource is currently busy
The item is currently under exclusive use
The internal table is full
An abnormal IO termination occurred; check the
pktrvalu field for the cause of the termination
An abnormal IO termination occurred; check the
pktrvalu field for the cause of the termination
Success; endoffile
sccdtns.
scchke.
sccname.
sccbuf.
sccfnsp.
sccbhuf.
sccsop.
sccbusy.
sccexcl.
sccfull.
sccait.
sccait.
scceof.
B64
ASYNCXS
C320001300D0
Glossary
ASCII American Standard Code for Information Interchange
An eight bit alphanumeric code for data transfer adopted by the
American National Standards Institute (ANSI X3.4 1968). The eighth
bit in each character code provides parity.
asynchronous communications
Data transmission without regular time relationship. Transmission is
controlled by start/stop bits. The sending device inserts start/stop bits
at the beginning and end of each character. The receiving device
resynchronizes on the start bit of each character.
asynchronous terminal handler
A Telematics product that controls IO operations between user tasks
and asynchronous terminal devices. Terminal oriented facilities
include user defined communications characteristics and control
character processing.
bit rate
A unit of signaling speed that is equal to the number of discrete
conditions or signal events per second.
call facilities
Optional X.25 user services that can be independently configured for a
link, file, or network user address.
call registration
The process by which ASYNCXS notifies NET25 to accept
incoming calls at a particular network address. Registration is done
when a device is created.
call user data (CUD)
Data included in a call request packet.
CCITT Consultative Committee for International Telephone and
Telegraph
The international body that produces standards on behalf of national
telecommunications authorities.
channel
The part of a communication system that connects two points and
provides a path along which signals can be sent; referred to also as
port.
command mode
The state in which all characters from the terminal to the PAD are
interpreted by the PAD as commands.
ASYNCXS
C320001300D0
GL1
GLOSSARY
configuration
The process of identifying ASYNCXS devices and profiles to
ASYNCXS and placing them into operational states.
data forwarding character
Upon receipt of a data forwarding character, all characters in the input
buffer are assembled into a data packet that is sent to a remote DTE.
The data forwarding character is the last character in the data packet.
data forwarding timeout
Each time a character is received by a PAD, the timer is started. If the
timer expires, all characters in the input buffer are assembled into a
data packet and sent to a remote DTE.
data transfer mode
The state in which all characters received from the terminal by the
PAD are packaged into packets and sent to the host DTE.
device
The asynchronous hardware to which the PAD port connects, and the
data source and destination to/from the PAD (a keyboard/display
terminal, a printer, or an asynchronous channel on a host computer).
events
Device related occurrences that may require action. An application
task can register for event notification through the IO interface; when
a defined event happens for which the task is registered, the task is
advised with an IO/MODE event notification.
fast select
A facility provided by some packet switching networks that allows up
to 128 bytes of data to be passed across the network when a call is
initiated. This allows short exchanges of information without actually
establishing a call.
flow control
A mechanism by which a network limits the number of messages in
transit, in order to prevent overloading and poor performance.
Specifying window sizes is the typical flow control method.
handler mode
A state of an ASYNCXS device where the only valid activity is
through the TRAX IO services.
hot key
A designated character that when entered, places the PAD into handler
mode and generates an event notification.
INF Interactive Network Facilities
A Telematics network management tool providing network control,
report generation, and diagnostic capabilities.
GL2
ASYNCXS
C320001300D0
GLOSSARY
initial profile
An X.3 profile used as the default profile when a terminal or printer is
initially connected to the PAD.
IO entity
A Telematics term for anything with which a task can perform input
and output operations. This includes: a file stored on disk or in
memory; a device connected to the system through a channel card
(e.g., terminal, printer); a device connected via a CPU port (e.g., host
computer, operator terminal); another task running on the system (e.g.,
network gateway, protocol handler).
logical volume
A grouping of IO entities with common characteristics.
Network Configuration Model (NCM)
A set of files and procedures for configuring a Telematics network.
NET25
The Telematics product responsible for providing user connections to a
packet switching network and supporting the functions of a switching
node on the network.
network access point
The point at which a device accesses the packet switching network.
Each network access point has a network user address assigned to it
during network configuration.
NUA Network User Address
The identifier by which a DTE is known to the network. Comparable
to a subscribers telephone number.
packet switching network
A set of linked packet switched exchanges that can be used to pass
packets between two users connected to the network through their
respective X.25 links.
PAD Packet Assembler/Disassembler
A device that assembles packets from character streams and
disassembles packets into character streams. In the Telematics
environment, a PAD refers to a Telematics node providing PAD
support for devices. Access products such as ASYNCXS work jointly
with NET25 to provide PAD support for asynchronous devices that
communicate through a packet switching network.
PAD connection
Recommendations X.25, X.28, X.3, and X.29 constitute the PAD
connections on a packet switching network. PAD connections are used
with X.25. PAD connections allow nonpacketmode DTEs to
communicate with host DTEs across a packet switching network.
ASYNCXS
C320001300D0
GL3
GLOSSARY
padding
Padding assures that characters are not printed when the mechanical
device (carriage) is being returned to the left margin. Padding can be
nonprinting characters or time fill.
PADmap
An ASYNCXS structure containing NUA, call user data, and port
information that is used for assignment of incoming calls.
PAD messages
Messages sent between the host and the PAD. They are carried in data
packets with the Q bit set to 1.
PAD mode
The default device operating mode, which can be further classified as
command mode or data transfer mode.
PAD prompt
The messages sent back by the PAD to the terminal to indicate that the
physical connection is established and the link is active.
PAD service signals
Messages sent from the PAD to the terminal. Defined by
Recommendation X.28, these messages acknowledge PAD command
signals and return to the terminal the identity and internal state of the
PAD.
PMM Product Management Module
An INF command library for interfacing to a task, e.g., a PAD.
port
The physical channel from the Telematics system to the asynchronous
device. ASYNCXS communicates directly with the asynchronous
ports under its control, but makes no distinction between terminal and
host port connections.
profile
A set of X.3 parameters that control terminals connected to
ASYNCXS.
protocol
A procedure defining the interaction of two processes across an
interface.
PVC Permanent Virtual Circuit
A virtual circuit established during network configuration that
permanently connects two network users; equivalent to a leased line.
Recommendation X.3
The CCITT document defining the X.3 PAD parameters that establish
terminal specific characteristics or actions that the remote DTE wants
the PAD to take upon receipt of particular input from the terminal
(e.g., break).
GL4
ASYNCXS
C320001300D0
GLOSSARY
Recommendation X.25
The CCITT document defining the three levels of the X.25 protocol to
connect a customers DTE to a network node (DCE). The protocol
requires software in both the DTE and the network.
Recommendation X.28
The CCITT document defining terminal signaling, i.e., commands
typed by the terminal user that are understood by the PAD, and
messages that are returned by the PAD to the terminal user.
Recommendation X.29
The CCITT document defining control procedures between the X.25
DTE and the network PAD.
SVC Switched Virtual Circuit
A virtual circuit which connects two network users for the duration of
a call. It is set up when one party calls another and removed when
either party clears the call.
terminal user
The person at an asynchronous keyboard/display terminal who signs
the terminal onto the PAD, and either readies it to accept incoming
calls, or makes outgoing calls.
Telematics system
A generic name for all Telematics Programmable Communication
Processors.
throughput
The attainable line speed for a virtual circuit during normal and peak
usage.
transmission line
The physical means of connecting processors at different locations so
that information may be transferred between them. When direct wire
connection is impractical, processors generally communicate across
leased or switched lines.
TRAX
The Telematics operating system.
virtual circuit
A logical connection between two subscribers, as defined by X.25
level 3. Virtual circuits can be multiplexed along a single link.
X.25
The protocol defining the exchange of packets along a virtual circuit.
X.25 defines the physical transfer of data along a link (level 1), the
correct exchange of data between a users computer equipment and a
packet switched exchange (level 2), and the setup and clearing of
virtual circuits (level 3).
ASYNCXS
C320001300D0
GL5
GLOSSARY
X.28 PAD commands

PAD commands entered by the asynchronous terminal user to instruct
the PAD to perform actions.
X.3 (see profile)
GL6
ASYNCXS
C320001300D0
Index

!!,1+0'+% 1**.5 /#.2'!# /'%+)
!(+,3)#"%# /#.2'!# /'%+)
"" - !,**+"
).*/ 6
.#" !,**+"
!&.!0#. /#0
!,**+"/
"" -
,))#!0 00'/0'!/
.#0# #2'!#
.#0# '.#!0,.5
.#0# .,$')#
#$'+# +'0')
#)#0# -
#/0.,5
'/ )# #2'!#
+ )# #2'!#
./# -
,"'$5 #2'!#
,"'$5 +'0')
,"'$5 .,$')#
#/#0 00'/0'!/
#0 #$1)0/ #2'!#/
#0 #$1)0/ +'0')

#0 #$1)0/ .,$')#/

&,3 #$1)0/ #2'!#/

&,3 #$1)0/ +'0')

&,3 #$1)0/ .,$')#/

&,3 #2'!#
&,3 '.#!0,.5
&,3 +'0')
&,3 -
&,3 .,$')#
&,3 00'/0'!/
/1**.5
10, 1"

10,!))

10,-.'05

ASYNCXS
C320001300D0

.#(
!0',+ ,+ .#!#'-0

)0#.+0# /'%+)

"0 $,.3."'+% ,+ .#!#'-0 ,$
/#.2'!# /'%+)
1$$#./

)) !,**+"
)) )) #0.5 !,**+"
)) .,10'+%
"#/!.'-0',+
#4*-)#/
&.!0#. "#)#0# !&.!0#.

&.!0#./
!,+0.,) '+0#.$!# 6
"0 $,.3."'+%

"#)#0'+% '+ #"'0'+%

#"'0'+%
/-#!')
)#.
!1/# /'%+)/
!,+$'.*0',+ /#.2'!# /'%+)
/#.2'!# /'%+)
). )#. !,**+"
,))#!0 00'/0'!/ !,**+"

,**+" *,"#
,++#!0 !,**+"
,++#!0#" /#.2'!# /'%+)
,++#!0',+ -.,!#"1.#/
,+0'+1# !,**+"
,+0.,) !&.!0#./ '+0#.$!#
6
,+2#+0',+/
,-5 !,**+"
,-5!). ,-5 )#. !,**+"
.#0# #2'!# !,**+"
IN1
INDEX
0%!2% )0%#2.07 #.,,!-$
0%!2% 0.&)+% #.,,!-$
D
!2! &.05!0$)-'
!$$)2).-!+ #(!0!#2%0

!$$)2).-!+ #(!0!#2%0

#(!0!#2%01
#.-$)2).-1

.- #(!0!#2%0 #.3-2

.- )$+% 2),%0 %6/)0!2).-

.- )-2%04!+ 2),%0 %6/)0!2).-

.- 0%#%)/2 .& "0%!* #(!0!#2%0

.- 0%#%)/2 .& &.05!0$)-' #(!0!#2%0

.- 0%#%)/2 .& 0%#!++ #(!0!#2%0

5(%- "3&&%0 &3++

!2! 20!-1&%0 ,.$%

%&)-% -)2)!+ #.,,!-$
%+%2% !/ #.,,!-$
%120.7 #.,,!-$
%4)#% ./%0!2).-!+ 12!2%1

%4)#% 1/%%$
)!'-.12)# %#(.

)1!"+% %4)#% #.,,!-$
)1!"+% $%4)#% .- #!++ #+%!0

)1#!0$ .32/32

)1/+!7 .32/32 $%+!7

E
#(.
$)!'-.12)#

+.#!+ %-!"+%$)1!"+%

,!1*

$)2)-'
#(!0!#2%0 $%+%2% #(!0!#2%0

#(!0!#2%01

%-!"+%$)1!"+% )- $!2! 20!-1&%0 ,.$%

+)-% $%+%2% #(!0!#2%0

IN2
+)-% $)1/+!7 #(!0!#2%0

1/%#)!+ #(!0!#2%0 &3-#2).-1

20!-1,)2 %$)2)-' 1%04)#% 1)'-!+1

-!"+% %4)#% #.,,!-$
0!1% !/ #.,,!-$
4%-2 -.2)&)#!2).- )-2%0&!#%
$%0%')12%0

$%1#0)/2).-
0%')12%0 8
F
+.5 #.-20.+
$%4)#%

5)2( ,.$%, 1)'-!+1
#(!0!#2%0

#(!0!#2%0

G
+.11!07
H
!-$+%0 ,.$% )-2%0&!#%
%+/ #.,,!-$

.2 *%7 )-2%0&!#%
I
#+0 -4)2!2).- 2. +%!0 #.,,!-$

$+% 2),%0

-#+3$% #.,,!-$
-#.,)-' #!++ 0.32)-'

-2$ -2%003/2 !-$ )1#!0$ #.,,!-$

-2%0!#2)4% %25.0* !#)+)2)%1
-2%003/2 #.,,!-$

-2%04!+ 2),%0

-4!+)$ .,,!-$ 1%04)#% 1)'-!+
ASYNCXS
C320001300D0
INDEX
/4:+8,')+
!

" @

!" &

!#"
%
@
@
@
#"

@
!"
$ " @
9;(9+8</)+ 9;33'8? @

!

)8+':+ *+</)+ */8+):58?
)8+':+ 685,/2+ */8+):58? @
"
)8+':+ *+</)+ @
)8+':+ 685,/2+ @

!" &
*+9:85? *+</)+

*+9:85? */8+):58?

*+9:85? 685,/2+

!#"
%
'))+6: /4)53/4- %
)'22
@
*+,/4+ /4/:/'2 6'8'3+:+89

*+8+-/9:+8 ,58 +<+4: 45:/,/)':/54

35*/,? *+</)+ =./2+ 542/4+ @
35*/,? /4/:/'2 6'8'3+:+89

5(:'/4 /4/:/'2 6'8'3+:+89

6'99 )54:852 :5 .'4*2+8 35*+

6'99 )54:852 :5 35*+

8+-/9:+8 ,58 +<+4: 45:/,/)':/54
@
8+0+): /4)53/4- %
)'22
8+7;+9: /4)53/4- )'22 6'8'3+:+89
@
8+7;+9: %
)544+):/54
@
8+7;+9: %
*/9)544+):/54

5(:'/4 '9?4) )54,/-;8':/54
5(:'/4 *+:'/2+* +4:/:? 6856+8:/+9
5(:'/4 *+</)+ )54,/-;8':/54
5(:'/4 *+</)+ 9:':/9:/)9
@
5(:'/4 *+</)+ 9:':;9
5(:'/4 +4:/:? 4'3+9
5(:'/4 3'6 :'(2+ @
5(:'/4 685,/2+ )54,/-;8':/54
ASYNCXS
C320001300D0

'** 3'6 +4:8?
*+2+:+ '22 3'6 +4:8/+9
*+2+:+ 3'6 +4:8?
*/9'(2+ *+</)+
*/9'(2+ :'91 +>)+6:/54 685)+99/4-
+4'(2+ *+</)+
+4'(2+ :'91 +>)+6:/54 685)+99/4-
35*/,? '9?4) )54,/-;8':/54

@
35*/,? *+</)+
35*/,? 685,/2+
8+9+: 9:':/9:/)9
#"

@
!"
$ " @
L
'4-;'-+ )533'4*

/(8'8/+9
/4+
*+2+:+ ).'8'):+8 %

*/962'? ).'8'):+8 %

,++* ',:+8 )'88/'-+ 8+:;84 %

,++* 6'**/4- ',:+8 %
,52*/4- %
M
+99'-+ )533'4*

5*+3
)54,/-;8/4- 9;(56:/549

9/-4'2 ,25= )54:852 %
5*+9 5, 56+8':/54

5*/,? +</)+ )533'4*
5*/,? 4/:/'2 )533'4*

5*/,? 85,/2+ )533'4*

N
':/54'2 3'81+8 %
"

6'8 +:=581 '8/:? )533'4*

IN3
INDEX
,- ")+/" -)"/"- +))*!

,"-/&+* )+!".

,-+# ")+/" -+#&(" +))*!
,"-/&+* )+!". &*/"-# "
."/ ")+/" "/ +))*!
0/,0/ !"(3 !0" /+ &*,0/

-1(0.
P

/&+* +* -" "&,/ +# -"' .&$*(

#(+2 +*/-+(

)+!" &*/"-# "
,-+),/
-" (( %- /"-
."-1& " .&$*(.
5
S
"*! +))*!
),

"-1& " .&$*(.

+0*/&*$ .0))-3
'*+2("!$"
-"'

("-
("- +*#&-)/&+*

+**" /"!
!". -&,/&+*

&*1(&! +))*!
-"."/
.//0.
/-*.)&/ "!&/&*$
/-*.)&/.0,,-"..
$" 2&/

"..&+*

-)"/"- +))*!

"/ +))*!
-&/3
!"/" /&+*
/-"/)"*/

"/ "#0(/. "1& ". +))*!

+-/ ..&$*)"*/

%+2 "#0(/. "1& ". +))*!
!!&*$
#/"- --&$" -"/0-*
#/"- %+-&4+*/( /

#/"- (&*" #""!
-+!0 / !". -&,/&+*
"/ "#0(/. *&/&( +))*!

"/ "#0(/. -+#&(". +))*!
%+2 "#0(/. *&/&( +))*!
-+# -+#&(" "/ +))*!
%+2 "#0(/. -+#&(". +))*!
-+#&(" -+#&(" &.,(3 +))*!
%+2 "1& " +))*!
-+#&(".
%+2 &-" /+-3 +))*!
-+),/ ."-1& " .&$*(

%+2 *&/&( +))*!

%+2 , +))*!
R
"! +))*!
"! +,/&+*.
""*(" !"1& "

"(/"! )*0(.
"."/ "."/ &- 0&/ +))*!
"."/ ."-1& " .&$*(
"."/ //&./& . +))*!

"/0-* 1(0".
IN4
%+2 -+#&(" +))*!

%+2 //&./& . +))*!
&$*+*
&* (0!" #&(".

+,/&+*.

," &( %- /"- #0* /&+*.

,""! +# !"1& "
/*!-!. +),(&* "
//". !"1& " +,"-/&+*(

//0.
// +))*!
ASYNCXS
C320001300D0
INDEX
4'37+%' 4+)/#-

:.$0- /26+3: %0..#/&

:.$0-+% 44+)/.'/5 %0..#/&

:.$0-4
%0..#/&4
:.$0- /26+3:

:.$0-+% 44+)/.'/5

%3'#5+/)

&+41-#:+/) 7#-6'4

13'&'(+/'&

3'1-#%'.'/5
'/#$-+/) "

'9#.1-'4

36-'4

:/5#9 %0/7'/5+0/4
T
#%5 035 '45 %0..#/&
#%55 '3.+/#- '45 %0..#/&
'3.+/#%0//'%5+0/ 130%'&63'4

4+)/0/ +/%-6&' (+-'4

'3.+/#5' %0..#/&
:1' %0..#/&
:1'#*'#& $6(('3

W
!#+5 %0..#/&
X
"
%0..#/&4
3'#&
#--
#-- #-- '53:
-3 -'#3
0//'%5
0/5+/6'
01:
01:%-3 01: -'#3

'-1

ASYNCXS
C320001300D0
%-3 /7+5#5+0/ 50 -'#3

/%-6&'
/5& /5'33615 #/& +4%#3&

/5'33615

#/)6#)'

'44#)'

1#3 '5803, #3+5:

#3#.'5'3

30( 30(+-' '5
30(+-' 30(+-' +41-#:
'#&
'4'5 '4'5 +3%6+5
1#3 '.05' #3#.'5'3
130( '.05' 30(+-'
4'5 '.05' '5
'/&
'5
5#5 5#564
46..#3:
4:/5#9
#%5 035 '45
#%55 '3.+/#- '45
'3.+/#5'
:1'
!#+5
"
:1'
" :1'
" 1#3#.'5'34
%*#/)+/) -0%#- 7#-6'4
%*#/)+/) 3'.05' 7#-6'4
&'4%3+15+0/4 ;

&+41-#:+/) -0%#- 7#-6'4

&+41-#:+/) 130(+-' /#.'47#-6'4
&+41-#:+/) 3'.05' 7#-6'4

130(+-' 5:1'4
3'1-#%+/) -0%#- 130(+-'4
3'1-#%+/) 3'.05' 130(+-'4
46..#3: ;
7#-6' %0.$+/#5+0/4
" 130(+-'4

"
:1' %0..#/&
" :1' %0..#/&
" %*#3#%5'3
(30. &'7+%' 50 "
(30. 50 &'7+%' "

" %*#3#%5'3
(30. &'7+%' 50 "
(30. 50 &'7+%' "

IN5
INDEX
IN6
ASYNCXS
C320001300D0

ECI Telematics ASYNC-XS Manual

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

ECI Telematics ASYNC-XS Manual

Diunggah oleh

Hak Cipta:

Format Tersedia

ASYNCXS Manual

Publication Number C320001300D0

TELEMATICS INTERNATIONAL, INCORPORATED

November 1987. Compatible with A.1 software

February 1989. Compatible with E.0 software.

August 1989. Compatible with G.0 software.

February 1993. Compatible with H.0 software.

Whats In This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

X.3 Profiles and Parameters

X.3 Profiles Types and Uses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

ASYNCXS PMM Commands

Before Creating Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

ASYNCXS Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

X.28 Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

PAD Service Signals

Accounting Summary PAD Service Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

ASCII Character Set

IO/CRDIR Create Device Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B9

Whats In This Manual?

Issues requests to NET25 to establish the virtual circuit or accept an

Collects characters from the device according to configuration

Transmits characters received from NET25 to the device according to

Issues requests to NET25 to clear the virtual circuit or respond to a

Figure 11. Product Relationships

Figure 12. INF Relationships

Uppercase indicates required characters; not the case (upper or

Turn the terminals power switch on.

If the autobaud option is enabled, enter several periods (.), at one to

Include an X.28 command in the signon include file that automatically

Operate the device so that it receives an incoming call when it has

The PAD receives a call clear request from the network

Characters received with invalid parity (depending on the P21 value)

An actual break, generated by transmitting binary 0 for a specified

A string of characters (BREAKString device parameter)

Data Accumulation and Forwarding

Acceptance of an incoming call for the terminal

Receipt of a break signal, if the value of P7 causes return to command

Receipt of an indication of reset message from the network

Buffer full If no other forwarding condition applies, data will be

PAD recall (switch to command mode)

Control characters should be assigned unique values; do not define the

A control character can be included in a string. The decimal value of

The following information can be returned in response to a Symbolic

print data (quotation marks enclose command parameter)

Device Operational States

Performs autobaud detection, if selected (P11)

Starts autocall procedures, if enabled (P81)

When DSR and CD are individually applied and RI is then applied:

When DSR and CD are applied during the 30 seconds after RI is

modem=(modem,nodtr,nohangup,autoanswer) and par=(80:0 81:92)

RI has no effect with this configuration.

When DSR and CD are individually applied and RI is then applied:

When DSR and CD are applied during the 30 seconds after RI is

RI has no effect with this configuration.

When DSR and CD are individually applied: no effect

When DSR and CD are applied,and an X.28 call is placed, completed,

RI has no effect with this configuration.

When DSR and CD are applied,and an X.28 call is placed, completed,

Disabling the device causes DTR and RTS to stay low.

When DSR and CD are individually applied: no effect

When DSR and CD are applied, and DSR is removed, or device is

RI has no effect with this configuration.

Incoming Call Routing