ECI Telematics ASYNC–XS Manual

ASYNCXS ManualPublication Number C320001300D0

February 1993

TELEMATICS INTERNATIONAL, INCORPORATEDWorldwide Headquarters

1201 Cypress Creek RoadFort Lauderdale, Florida 33309

UNITED STATES(305) 7723070

TELEMATICS INTERNATIONAL, LTD.

ISIS House, Reading RoadChineham, BasingstokeHampshire RG24 OTW

UNITED KINGDOM(0256) 467385

European Headquarters

ii ASYNCXSC320001300D0

Disclaimer

Telematics reserves the right to change this document, its contents, andany 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 mayoccur in this document. If you find any errors, please report them toTelematics:

TELEMATICS INTERNATIONAL, INCORPORATEDDocumentation DepartmentWorldwide Headquarters1201 Cypress Creek RoadFort Lauderdale, Florida 33309 U.S.A.

Telematics reserves the right to use or distribute freely any informationsupplied by readers without incurring obligations.

Any unauthorized use, duplication, or distribution of this document or anypart thereof without the prior written consent of Telematics is strictlyprohibited.

Copyright Telematics International, Inc., 1993. All rights reserved.

Revision History

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 iiiC320001300D0

Contents

1 IntroductionWhats In This Manual? 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product Description 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Relationships To Other Telematics Products 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Manuals 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standards Compliance 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Syntax Conventions 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 OperationsConnection 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iv ASYNCXSC320001300D0

3 X.3 Profiles and ParametersX.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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 ASYNCXS PMM CommandsBefore Creating Devices 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASYNCXS vC320001300D0

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 X.28 CommandsX.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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi ASYNCXSC320001300D0

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 PAD Service SignalsAccounting 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 AlarmsSeverity 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alarm Messages 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A ASCII Character Set

B IO InterfaceIntroduction B1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conventions B1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Include Files B2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modes B3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Event Notification B4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

IO Service Summary B6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO/CLOSE B8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO/CRDIR B9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASYNCXS viiC320001300D0

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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

viii ASYNCXSC320001300D0

pktrvalus B63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Errors B64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary

Index

Figures

Figure 11. Product Relationships 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 12. INF Relationships 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ASYNCXS 11C320001300D0

1 IntroductionThis manual describes the commands and parameters that configure andcontrol the Telematics ASYNCXS environment.

To use this manual effectively, you should be familiar with asynchronousdevice operation, X.25 packet switching procedures, and the CCITTstandards for PAD implementation in an X.25 network (X.3, X.28, andX.29). You should also be experienced with Telematics InteractiveNetwork Facilities (INF), NET25 software, and the NetworkConfiguration Model (NCM).To use the IO interface effectively, you should be familiar withprogramming in the Telematics TRAX operating system environment,including building and submitting IO subservice packets.

This is a reference manual. For information about how commands areused to configure and manage ASYNCXS, see the Release Notes, theConfiguration Model Manual, and the Configuration Model OperationsGuide.

Whats In This Manual?

The Introduction chapter, in addition to this section, describes theASYNCXS product. It also lists related manuals, standards compliance,and conventions used in this manual.

The Operations chapter describes features of the ASYNCXSenvironment and how to use them.

The X.3 Profiles and Parameters chapter describes the types of profilesASYNCXS uses and the effects of their parameter values.

The ASYNCXS PMM Commands and X.28 Commands chaptersdescribe their respective commands, and provide syntax and examples.

The PAD Service Signals chapter explains the events that can occur andthe type of information returned in the messages.

Other ASYNCXS events can generate different types of messages, whichare listed and described in the Alarms chapter.

The ASCII Character Set appendix lists the numeric equivalents fordefining special characters.

The IO Interface appendix describes the Assembly languageprogrammers interface to ASYNCXS, which includes IO subservices,return values, and include files.

INTRODUCTION

ASYNCXS12C320001300D0

Product Description

Telematics ASYNCXS is a Packet Assembler and Disassembler (PAD)that allows asynchronous devices to communicate with remote devicesand hosts through an X.25 packet switching network.ASYNCXS comprises two components: the ASYNCXS ProductManagement Module (PMM) and the ASYNCXS PAD. TheASYNCXS PMM provides a manmachine interface that allows networkoperations personnel to configure and monitor the ASYNCXS PADusing Telematics Interactive Network Facilities (INF). The ASYNCXSPAD provides X.3, X.28, and X.29 support.X.3 support includes a set of parameters that specify the operatingcharacteristics of each asynchronous port. ASYNCXS also offersextended Telematics parameters for added functionality. X.3 parameterscan be set dynamically on a percall basis. Reconfiguration can occurduring call acceptance.X.28 support defines the dialogue between the device and theASYNCXS PAD. X.28 commands set up and clear virtual calls to aremote computer through the packet switching network, and set/modifyX.3 parameters to accommodate the devices operating requirements.ASYNCXS implements the 1984 CCITT Recommendation X.28commands, plus Telematics extended commands. Optionally, a commandfile containing X.28 commands can be executed at call accept time at thelocal and/or remote ASYNCXS nodes.X.29 support handles the exchange of control information across anetwork 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 aremote device to read or alter PAD parameters. The X.29 moduleimplements this functionality using data packets with the qualifier bit set(i.e., Q=1).You can manage ASYNCXS locally or remotely to modify aconfiguration, monitor ASYNCXS activity, and display alarm/eventmessages for remote PADs. You can downline load ASYNCXS softwareto remote nodes from any NCC node and send configuration parameters toremote nodes from any point in the network. You can configure host orterminal devices manually or automatically using command files from thelocal or NCC node. See the Configuration Model Manual and theConfiguration Model Operations Guide for details.

Relationships To Other Telematics ProductsNET25 Like all Telematics access products, PAD support isimplemented jointly with the NET25 software, which processes callpackets, establishes virtual circuits, and manages data packet transfers. Tosupport the network connection, ASYNCXS: Issues requests to NET25 to establish the virtual circuit or accept an

incoming call request

INTRODUCTION


Collects characters from the device according to configurationparameters and passes them to NET25 when a forwarding conditionoccurs

Transmits characters received from NET25 to the device according toconfiguration parameters

Processes X.29 commands from NET25 that the remote device hassent, and responds accordingly

Issues requests to NET25 to clear the virtual circuit or respond to aclear request from the remote device by clearing the virtual circuit

Information is exchanged between ASYNCXS and NET25 through theTelematics Resident Applications Executive (TRAX) operating system.

System Libraries The Telematics asynchronous level 2 library providesan interface between the level 1 asynchronous communications library andthe ASYNCXS PAD. The level 2 librarys routines help provide logicalread and write access to the asynchronous terminal devices, as well ascreating/managing communications channels and initiating datatransmissions. ASYNCXS also accesses the General Purpose Library(GPLIB) for subroutine calls to TRAX.

Figure 11 shows the relationship between ASYNCXS, NET25, and thesystem libraries.

TRAX IO

68000

C

Pascal

ASYNCXS

NET25

X.3 X.28 X.29

GPLIB

Async L1

Subroutine Calls

AsynchronousCommunications Lines

Async L2Library

Assembler

68000Assembler

TRAX IO

ASYNCXS PMM

ApplicationTask

TRAXIO

Library

Figure 11. Product Relationships

INF INF is the network tool that manages the ASYNCXS environmentfrom a Telematics terminal. INF provides an interface betweenASYNCXS and NET25, and reports all ASYNCXS related statusmessages and alarms. It also manages the interfaces to the various PMMs(including the ASYNCXS PMM), which are product libraries loaded atsystem startup. Figure 12 shows these software components.

INTRODUCTION


NET25Packet

ASYNCXS PMMHOST INFSwitchingNetworkPAD

ASYNCXSPAD

Figure 12. INF Relationships

Related Manuals

The Configuration Model Manual (C320001700) and the NetworkConfiguration Model Operations Manual (C320003800)) explain howto configure the ASYNCXS product on your Telematics system andcustomize its operation to your networks needs.

The Release Notes that accompany the software indicate the requiredlibrary revisions.

The NET25 Manual (C320000800) and the Interactive NetworkFacilities (INF) Manual (C320000900) describe the commands used toconfigure and manage your Telematics network.

For users of the IO interface described in Appendix B, the ProgrammersGuide (C310000100) and the TRAX Programmers Manual(C315000100) describe how to build and submit TRAX operatingsystem IO service packets.

INTRODUCTION


Standards Compliance

International Telecommunication Union. Recommendation V.24 List ofDefinitions for Interchange Circuits Between Data Terminal Equipmentand Data CircuitTerminating Equipment. In Red Book DataCommunication Over the Telephone Network. vol. VIII fascicle VIII.1Geneva: International Telecommunication Union, 1985.

______. AP IX48. Geneva: International Telecommunication Union,1989.

______. AP IX49. Geneva: International Telecommunication Union,1989.

______. Recommendation V.40 Error Indication with ElectromechanicalEquipment. In Red Book Data Communication Over the TelephoneNetwork. vol. VIII fascicle VIII.1 Geneva: InternationalTelecommunication Union, 1985.

______. Recommendation V.54 Loop Test Devices for Modems. In RedBook Data Communication Over the Telephone Network. vol. VIIIfascicle VIII.1 Geneva: International Telecommunication Union, 1985.

______. Recommendation X.3 Packet Assembly/Disassembly Facility(PAD) in a Public Data Network. In Blue Book Data CommunicationNetworks Services and Facilities. vol VIII fascicle VIII.2. Melbourne:International Telecommunication Union, 1988.

______. Recommendation X.15 Definition of Terms Concerning PublicData Networks. In Red Book Data Communication Networks Servicesand Facilities. vol. VIII fascicle VIII.2 Geneva: InternationalTelecommunication Union, 1985.

______. Recommendation X.20bis Use on Public Data Networks of DataTerminal Equipment (DTE) which is Designed for Interfacing toAsynchronous Duplex Vseries Modems. In Red Book DataCommunication Networks Interfaces. vol. VIII fascicle VIII.3 Geneva:International Telecommunication Union, 1985.

_____. Recommendation X.25 Interface between Data TerminalEquipment (DTE) and Data CircuitTerminating (DCE) for TerminalsOperating in the Packet Mode Connected to Public Data Networks byDedicated Circuit, In Blue Book Data Communication Networks Interfaces. vol. VIII fascicle VIII.3 Melbourne: InternationalTelecommunication Union, 1988.

INTRODUCTION


Syntax Conventions

Command syntax uses the following conventions:

< >Angle brackets enclose values you must supply. Items within theangle 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 ofthe items.

UPPERCASEUppercase indicates required characters; not the case (upper orlower) 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 theX.3 parameter number. For example, P13 indicates X.3 parameternumber 13.

Additional X.28 command conventions and syntax information isprovided on page 51.

The IO interface described in Appendix B uses the following conventions:

Field length specificationsB indicates a byte, W indicates a word, and L indicates a longword.If no decimal precedes the letter, a single byte, word, or longwordis expected. A decimal preceding the letter indicates the number ofbytes, words, or longwords.

A hyphen () indicates the mnemonic in the Field column does notrepresent a field offset. Such mnemonics represent the length of arequest packet or parameter buffer, and may be used whenreserving and initializing memory for them.

A V indicates the start of a variable length field. When a buffer hasa 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 modifiedwhile the device is online.

INTRODUCTION


*

A single asterisk indicates the preceding mnemonic is defined inthe asyxsuser.in include file (see next section, Include Files).

**

A double asterisk indicates the preceding mnemonic is defined inthe padiodefs.in include file (see next section, Include Files).

use and setThe word use preceding a mnemonic in the Contents columnindicates a MOVE instruction to copy a value into a field. Theword set indicates a BSET instruction to set the bit identified bythe mnemonic in that field.

INTRODUCTION


21ASYNCXSC320001300D0

2 OperationsThis 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 andlogically connect the user terminal to the ASYNCXS PAD. The physicalconnection is between the terminal and the Telematics system whereASYNCXS resides. The logical connection, or signing on, ensures thePAD 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 thenetwork and begin transferring data.

Terminals can be connected to the PAD in three ways: local connection,leased line connection, and dialin line connection. The followingprocedure is used for all types of terminal connections.

When modems are used, parameters configured for the terminal must becompatible with those of the modems, and both the terminal and modemparameters must be compatible with the PAD ports parameters. Youshould check the compatibility of the terminal, modem, and operatingparameters for speed, parity, echo, bits per character, and flow control.Also, check with your system administrator to determine whether theautobaud option is enabled for your channel.

To establish a PAD connection:

For a local terminal or with a leased line and modem, connect theterminal to a Telematics asynchronous channel that is configured forASYNCXS operation. Check with your system administrator for theassigned channel.

OPERATIONS


For a terminal connected via a dialin line and modem, make sure theterminal 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 isaccepted, switch the modem from voice to data mode.

If the autobaud option is enabled, enter several periods (.), at one totwo second intervals. When two periods echo on the screen, enter acarriage return to automatically set the incoming baud rate and parity.

Signon Include FilesIf the PAD already knows the terminals speed, and if the terminal isconfigured so that no initial input is required before signing on, anoptional banner can be displayed from a local signon include file thatcontains commands to set up the terminal for its session. For example, thefile can contain X.28 commands to display the current time, portconnection, or network availability information.

If both local signon and remote signon files are specified for a device, theremote signon file functions as a nested include file to the local signonfile, i.e., the local signon files commands are executed, the remote signonfiles commands are executed, then control returns to the local signon filefor completion.

After displaying the last output from the local signon include file, the PADservice prompt (normally an asterisk) is displayed on a line by itself,indicating that the terminal is in command mode and can acceptcommands or incoming calls.

Printers and DisplayOnly DevicesIf the terminal is a printer or other displayonly device, autobauddetection cannot be used, and the device must be configured with theexact transmission speed, and the banner (if configured) is displayedimmediately.

The devices configuration should not place it in a state where it must sendinput. There are two ways to avoid this:

Include an X.28 command in the signon include file that automaticallymakes a call at signon

Operate the device so that it receives an incoming call when it hassigned on, and is never required to make outgoing calls

In Case of A ProblemIf you follow these procedures and nothing is displayed, turn the terminalpower switch off and on. If the problem persists, verify that ASYNCXSis running on the Telematics system, and that the channel to which theterminal is connected is enabled.

OPERATIONS


Operation Modes

ASYNCXS devices have two operation modes: handler and PAD. Thehandler mode uses TRAX IO services directly, and is described inAppendix B. When a device is in PAD mode (the default), it can be in oneof two operational modes: command and data transfer.

Command ModeAfter terminal setup and initialization procedures have completedsuccessfully, the terminal enters command mode. At this point, thephysical connection between the terminal and the PAD has beenestablished, and the user can enter X.28 commands. The terminal remainsin command mode until the PAD receives an X.28 command to make acall to another device on the X.25 network, or until the PAD receives acall from another device on the network.

If a nonzero command mode timeout value has been specified for theterminal (CMDTImeout device parameter), the PAD waits for a specifictime interval for a command from the terminal after issuing the PADprompt signal (i.e., a command prompt) to the terminal. If the timeinterval passes and no command is entered, the terminal is disconnectedfrom the PAD if there is no call active. If a call is active, the terminalswitches to data transfer mode. This timeout differs from the data transfermode timeout, which is described in the next section.

Data Transfer ModeThe terminal is placed in data transfer mode when an X.25 call issuccessfully established. In data transfer mode, data can be transferredbetween the terminal and the remote device. Depending on the X.3parameters defined, the terminal remains in data transfer mode until one ofthe following events occurs:

The terminal user enters the PAD recall character (depending on theP1 value)

The terminal user enters a break signal with the break key or analternate 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 tointerpret 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)

OPERATIONS


When an X.25 call is active, the terminal user can temporarily leave datatransfer mode and return to command mode by entering the PAD recallcharacter (controlled by P1). The terminal remains in command mode, andX.28 commands can be entered, until the terminal user enters the X.28Continue command, a carriage return, or a plus sign (+), any of whichreturns the terminal to data transfer mode. If P1=0, the user cannot leavedata transfer mode while a call is active unless a break or alternate break isused, depending on the value of P7.

If a nonzero data transfer mode timeout value has been configured for theterminal (X25IDLETimer device parameter), the PAD waits the specifiedtime interval for data to be entered from the terminal after forwarding theprevious 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 wasdescribed in the previous section.

OPERATIONS


Signals

This section covers two signal types: PAD service signals that are returnedfrom certain events, and the break signal used at the terminal.

PAD Service SignalsData sent from the PAD to the device falls into two categories: datareceived from the remote device, and PAD service signals. A PAD servicesignal is either a response to an X.28 command or an indication of PAD ornetwork status. The value of X.3 P6 determines whether PAD servicesignals are sent to the device; it also controls the format of those signals.

Several PAD service signals are described below. Chapter 6 lists thedefined PAD service signals and their meanings.

Prompt service signal This is the character or character string thatindicates the PAD is waiting for the terminal to send it an X.28 command.The standard prompt service signal is an asterisk (*); the default extendedprompt service signal is Service:. The extended prompt service signal isestablished when the device is configured.

Acknowledge service signal This is the indication from the PAD that ithas accepted an X.28 command. It consists of the and characters.

Break service signal This is the notification from the PAD that anindication of break has been received from the network.

Break SignalThe break feature allows the terminal to signal the PAD without loss ofcharacter transparency, i.e., without reserving a special character thatcannot be sent as data. A break signal also acts as a command abort keyfor X.28 Aread, Read, Tact, and Tactt commands. The break signal ismeaningful only when entered while a call is active; otherwise, it isignored.

If the terminal supports the break signal with the break key or anotherdefined break key, the PAD responds to the break signal according to thesetting of X.3 P7.

If the PAD receives an indication of break message from the network anda call is active, the PAD sends a break service signal to the terminal. Thiscan take one of several forms, depending on the terminals configuration:

An actual break, generated by transmitting binary 0 for a specifiedtime interval (BREAKTime device parameter)

A string of characters (BREAKString device parameter) No action; the indication of break message is ignored (NOBREAK

device parameter)

OPERATIONS


Data Accumulation and Forwarding

This section explains how data entered at the terminal is accumulated andeventually forwarded.

Typeahead BufferIn data transfer or command mode, the PAD alternates between reading astring of characters from the device and acting upon the characters read. Astring 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 modeby exceeding the line folding margin (P10).While an input string is being processed, the PAD is not actively readingfrom the device; characters entered from the device during this time arestored in a typeahead buffer. When the previous input has been processedand the PAD is ready to begin reading data from the device again, it firsttransfers all characters from the typeahead buffer into its internal readbuffer. This ensures that no data is lost during the processing of theprevious input.

If the PAD is not able to begin reading data quickly enough, inputcharacters fill the typeahead buffer, after which all subsequent inputcharacters are lost until the PAD begins reading again. There are two waysto avoid this: configure a larger typeahead buffer (TYPeahead deviceparameter) or enable input (terminal user) flow control with X.3 P5.The following events cause the typeahead buffer to be purged, discardingany 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 commandmode 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 ForwardingAs characters are entered from the device in data transfer mode, theyaccumulate in a PAD buffer until a data forwarding condition occurs. Thebuffer size is determined by various factors in the network configuration,e.g., maximum packet size. When a forwarding condition occurs, theaccumulated data is transmitted as a packet to the remote device, and thebuffer is cleared. The data forwarding conditions are:

OPERATIONS


Buffer full If no other forwarding condition applies, data will beforwarded upon reaching the larger of two values: the X25IOWrite deviceparameter value or the X.25 links configured maximum packet size value.For example, if the configured X25IOWrite value is 1000 bytes and thelinks maximum packet size is 512 bytes, and if no other forwardingcondition occurs, the data will be forwarded when 1000 bytes accumulatein the buffer. Similarly, if the X25IOWrite value is 256 bytes and thelinks maximum packet size is 512, the data will be forwarded when 512bytes accumulate (if no other forwarding condition occurs).Idle timer X.3 P4 specifies an idle timer for data forwarding. The timeris reset and started each time a character is entered from the device. If theinterval specified in P4 expires before the next character is entered, theaccumulated data is forwarded. Forwarding on the idle timer is disabled ifP15=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 isforwarded and the timer is reinitialized. Forwarding on the interval timeris disabled if the idle timer is enabled.

Data forwarding count X.3 P83 indicates that data will be forwardedafter the specified number of characters have been entered.

Break character When a break character (or an alternate break characterspecified 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 enteredfrom the terminal, any accumulated data is forwarded.

Data forwarding character When one of the characters specified in X.3P3, P23, or P24 is entered, the accumulated data and the forwardingcharacter are sent to the remote device. Data forwarding can be suspendedby flow control, i.e., if the network cannot accept any more data from thePAD. If a forwarding condition occurs and no data has accumulated fromthe device, an empty packet is not forwarded.

OPERATIONS


Editing Data

Before accumulated data is forwarded, it is held in a PAD buffer, and canbe 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 isenabled in data transfer mode (i.e., P15=1), the idle timer controlled by P4is ignored. You can only edit the current line.

Editing CharactersEditing uses three special characters: character delete, line delete, and linedisplay. These characters are not added to the buffer as data, but causespecific actions to be performed to the accumulated data. X.3 P16, P17,and P18 specify the three characters values. X.3 P19 controls the PADsresponse when these characters are entered.

Character delete The default character delete character is . X.3P16 can be set to a nonzero value to designate an alternate character deletecharacter. When the PAD receives the character delete character from thedevice, it deletes from its buffer the last character entered. If there are nocharacters in the buffer, this editing function has no effect.

Line delete The default line delete character is . X.3 P17 can beset to a nonzero value to designate an alternate line delete character. Whenthe PAD receives this character from the device, it deletes all of thecharacters in its buffer. The PAD responds to the device by sending anediting service signal, which consists of the characters ^U followed by theformat effector (). If there are no characters in the buffer, thisediting function has no effect.

Line display The default line display character is . When thePAD receives this character from the device, it sends a format effector() to the device, followed by all the accumulated characters inthe buffer. X.3 P18 can be set to a nonzero value to designate an alternateline display character.

OPERATIONS


Special Characters

You can use X.3 parameters to identify certain control characters forspecial action when they are entered from the terminal. These specialactions are:

Flow control PAD recall (switch to command mode)Display line Packet forwardingLine delete BreakCharacter delete Hot key string (if enabled; IO interface

users only; see Appendix B)Control characters should be assigned unique values; do not define thesame character for more than one function. If a character is assigned twoor more functions, only one function will be performed, according to thehighest priority:

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)

highest

lowest

Hot key

OPERATIONS


Symbols

This section explains how to create and display symbols.

Creating SymbolsSymbols are useful for creating commands with names that are familiar tothe terminal user. ASYNCXS predefines a number of symbols fordevices; some are defined when the device is enabled, and others aredefined/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. Priorto 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 ReplacementX.3 P81 controls symbolic replacement; replacement occurs only if P81has the symbolic replacement option enabled. Symbolic replacement canbe temporarily disabled for part of a command line by using the togglefunction character, the backslash ( \ ).Symbols are indicated by open apostrophes (). The symbol name can beenclosed in a pair of open apostrophes, or preceded by a single openapostrophe.

The first element in a command line is always replaced if it matches asymbol name (it can be enclosed in a pair of open apostrophes, but this isnot required). All subsequent symbol names must be enclosed in a pair ofopen apostrophes (or preceded by a single open apostrophe) in order to bereplaced in the command line.

Symbols can be defined with required and optional characters. When asymbol is defined in both uppercase and lowercase, uppercase indicatesthe required characters and lowercase indicates optional characters. Asymbol defined in all uppercase or lowercase must be typed completely.

Do not define a symbol with a character string that matches the casesignificant characters of X.28 commands or parameter keywords. Forexample, to define a symbol for remote profiles, do not use the stringRPROF or RPROFile in the definition. Examples of valid symbols areRPRO1 and RPRtokyo.

Do not define a symbol beginning with the character C; this is thesignificant character for the X.28 Call command.

OPERATIONS


Do not define a symbol with the same format as a call facility parametervalue; symbol names that contain a single alphabetic character followedby a number must not begin with the characters B, D, G, N, O, P, or W.

There are two symbol commands: symbolic assignment and symbolicinquiry.

Symbolic Assignment CommandThe Symbolic Assignment command defines a symbol name and assigns acharacter string to it. The command line is limited to 128 characters; thesymbol assignment operator (:=) and quotation marks that enclose thesymbol value are included in the character count.

Syntax

:=[]Parameters

Symbol name, containing up to 16 alphanumeric characters, thefirst of which must be alphabetic. Uppercase indicates theminimum number of significant characters.

[]Character string enclosed in quotation marks. The maximumlength is determined by the maximum line length (128 characters)and the length of the symbol name. An empty string () deletesthe symbol definition.

Example

The following command assigns the string c 99990001234567 to thesymbol host. Once defined, the symbol (i.e., host) can be used inresponse 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 ofthe control character must be enclosed in parentheses, i.e.,:=CHR(). For example,

ABC:=Chr(7)

The following information can be returned in response to a SymbolicAssignment command:

Acknowledge signal This is the normal command response. See Chapter6 for the signal display format.

Symbol limit exceeded The symbol cannot be defined because thenumber of symbols already defined for the device matches themaximum symbol limit (MAxsymbol device parameter).

OPERATIONS


Error, symbol not defined The symbol cannot be defined because thememory space reserved for symbol definition at task startup is full.

Symbol Inquiry CommandThe Symbol Inquiry command displays the value of an existing symbol.To produce a display of all defined symbols and their values, use the X.28Help Mnemonics command.

Syntax

?

Parameters

Symbol name. Wildcard characters can be used, but not as the firstcharacter.

?Required command character.

The following information can be returned in response to a SymbolInquiry command:

This is the normal response to the command. The PADissues an Acknowledge PAD service signal (see Chapter 6 for format)followed by the =.

No match found The symbol has not been defined or the name has notbeen specified correctly.

Symbol Replacement ExampleThe following symbols have been defined:

LOgon:=c 99990001234567atlanta:=99990007654321data:=this is a testPRint:=typehello:=type hi there (quotes enclose the command parameter)command: LOGONaction: c 99990001234567

command: c atlantaaction: c 99990007654321

command: print data (quotation marks enclose command parameter)action: type dataresponse: data

command: prin dataaction: type this is a testresponse: this is a test

OPERATIONS


command: pri statusaction: type status (no symbol status defined)response: status

command: pr \data\action: type data (temporarily disabled by backslash)response: data

command: pr PRint = action: type PRint = response: PRint =

command: helloaction: type hi thereresponse: hi there

command: pr hello = action: type hello = response: hello =

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 isspecified in its configuration (e.g., Create Device command) with theINState parameter. During operations, the state can change; the ShowDevice command (described in Chapter 4) can be used to display adevices current state.

Offline The device is logically disconnected from the PAD.

Enabled A device is placed in this state when an Enable Devicecommand is entered or when the INState device parameter has a valueother than OFFline or DISabled. If the device uses a modem, the devicestays in this state until the modem connects. When the device enters theenable state, ASYNCXS configures the asynchronous channel associatedwith the device. If P81=8, the device automatically enters this state afteran internal disable occurs.

Signon When a device enters this state, the PAD initiates communicationwith it and performs the defined signon procedures with the specified X.3parameter values and device configuration options. The actions areinitiated in the following order:

Performs autobaud detection, if selected (P11) Enables the asynchronous channel for read operations

Waits for input from the device (P80) Processes the signon file, if enabled (P80). The signon file is identified

with the LSignon device parameter.

OPERATIONS


Starts autocall procedures, if enabled (P81)Connect When a device has signed on to the PAD and autocall is notenabled for the device, the device enters the connect state. This is thedevice state when it is in command mode. After a call is established, thedevice is placed in the connect state when it changes from data transfer tocommand mode.Online When a call is established, the device is in the online state. Atthis point, the device is in data transfer mode and can communicate with aremote device across the network.

Modem Processing

The modem device parameter specifies whether the device is configuredfor modem support. If modem support is configured, there are severalsubparameters available; the combination that is specified can affect thestate of the signals and the port when other signals are asserted orremoved. This section first describes the subparameters in general, thenlists 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, itoverrides all the modem subparameters. Also, you should not modifymodem 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. Thesesubparameters 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 isdisabled. NOHANgup indicates the PAD will not modify the state of themodem signals when the device is disabled. The [NO]HANgupsubparameters are valid only if MODem is specified.AUToanswer indicates the device is placed in the connect state when DSRand DCD signals are both present. ASYNCXS follows the modemcontrol signals in autoanswer mode, based on the Industrial ElectronicsBulletin No. 9, Application Nodes for EIA Standard RS232C. When thedevice is configured for NOAUToanswer, it remains in the enabled state.A transition from this state requires that the modem report the RINGsignal. When RING is detected, ASYNCXS forces DTR and RTS highand starts a 30 second timer to wait for DSR and DCD to go high. If thetimer expires, the modem is disconnected and the device is disabled. IfDSR and DCD are present within 30 seconds, ASYNCXS places thedevice in the signon state and cancels the timer. (Subsequent completionof the signon include file, if configured, places the device in the connectstate.)

OPERATIONS


When the device is in the connect state, loss of DCD for more than 2seconds, or loss of DSR causes ASYNCXS to disable the device.

When the device is disabled, and if the modem option HANgup isenabled, ASYNCXS lowers DTR and RTS for 2 seconds. After 2seconds, modem control returns to the idle state.

Subparameter CombinationsWhen modem support is enabled, there are eight (8) possiblecombinations of the [no]dtr, [no]hangup, and [no]autoanswersubparameters. This section lists these combinations (with relevant X.3parameter settings; see Chapter 3 for full X.3 parameter descriptions) anddescribes the DTR and RTS signal and port state changes (if any) whenother 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 andRTS stay low; the state is enabled

When DSR and CD are not applied and RI is applied: DTR and RTSgo 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 isapplied: DTR and RTS stay high; the state changes to connect

When DSR and CD are applied and RI is applied: DTR and RTS gohigh; the state changes to connect

When DSR and CD are applied, and CD is removed: DTR and RTS golow after 2 seconds; the states changes from connect to enabled

When DSR and CD are applied, and CD is removed for less than 2seconds: DTR and RTS stay high; the state remains connect; the portwill not accept or send data (if CD is restored during the initial 2seconds, the port continues sending and receiving data)

When DSR and CD are applied, and DSR is removed: DTR and RTSgo 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; thestate changes from online to enabled (if par=(81:88), DTR and RTSstay high, and the state stays in connect)

OPERATIONS


modem=(modem,nodtr,nohangup,autoanswer) and par=(80:0 81:92) RI has no effect with this configuration.

When the port is first created, and DSR and CD are not applied: DTRand RTS stay low; the state is enabled

When the port is first created, and DSR and CD are applied: DTR andRTS stay high; the state is connect


When DSR and CD are applied, and CD is removed for less than 2seconds: DTR and RTS stay high; the state remains connect; the portwill not accept or send data (if CD is restored during the initial 2seconds, the port continues sending and receiving data; if CD is notrestored, 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, thengo high; the state changes from online to connect (if par=(81:88), DTRand RTS stay high, and the state changes from online to connect)

modem=(modem,nodtr,hangup,noautoanswer) and par=(80:0 81:88) 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 andRTS stay low; the state is enabled

When DSR and CD are not applied and RI is applied: DTR and RTSgo 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 isapplied: DTR and RTS stay high; the state is connect

When DSR and CD are applied and RI is applied: DTR and RTS gohigh; the state changes to connect



OPERATIONS



When DSR and CD are applied, par=(80:0 81:92), and an X.28 call isplaced, completed, and cleared from both sides: DTR and RTS go lowimmediately; 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) RI has no effect with this configuration.

When the port is first created, and DSR and CD are not applied: DTRand RTS stay low; the state is enabled





When DSR and CD are applied, par=(80:0 81:92), and an X.28 call isplaced, completed, and cleared from both sides: DTR and RTS go lowimmediately; 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) When the port is first created, and DSR and CD are not applied: DTR

and RTS stay high; the state is enabled When the port is first created, and DSR and CD are applied: DTR and

RTS stay high; the state is enabled When DSR and CD are not applied and RI is applied: DTR and RTS

stay high; the state is enabled When DSR and CD are individually applied: no effect 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 stay

high; the state changes to connect 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; thestate changes from connect to enabled

OPERATIONS



When DSR and CD are applied, and DSR is removed: DTR and RTSgo low immediately; after 2 seconds, DTR and RTS go high; the statechanges 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 andRTS remain high; after 2 seconds, the state changes from online toconnect)

modem=(modem,dtr,nohangup,autoanswer) and par=(80:0 81:92) RI has no effect with this configuration.

When the port is first created, and DSR and CD are not applied: DTRand RTS stay high; the state is enabled


When DSR and CD are applied, and CD is removed: DTR and RTSstay high for 2 seconds, then go low for 2 seconds, then go high; thestate 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 stay high; after 2 seconds,the state changes from online to connect (if par=(81:88), DTR andRTS remain high; after 2 seconds, the state changes from online toconnect)

modem=(modem,dtr,hangup,noautoanswer) and par=(80:0 81:88) When the port is first created, and DSR and CD are not applied: DTR

and RTS stay high; the state is enabled

When the port is first created, and DSR and CD are applied: DTR andRTS stay high; the state is enabled

Disabling the device causes DTR and RTS to stay low.

OPERATIONS


When DSR and CD are not applied and RI is applied: DTR and RTSstay high; the state is enabled

When DSR and CD are individually applied: no effect

When DSR and CD are applied during the 30 seconds after RI isapplied: DTR and RTS stay high; the state changes to connect

When DSR and CD are applied and RI is applied: the state changes toconnect



When DSR and CD are applied, and DSR is removed, or device isdisabled: DTR and RTS go low immediately; after 2 seconds, DTRand RTS go high; the state changes from connect to enabledimmediately

When DSR and CD are applied, par=(80:0 81:92), and an X.28 call isplaced, 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 RTSremain high; the state changes to connect)

modem=(modem,dtr,hangup,autoanswer) and par=(80:0 81:88) RI has no effect with this configuration.

When the port is first created, and DSR and CD are not applied: DTRand RTS stay high; the state is enabled





OPERATIONS


When DSR and CD are applied, par=(80:0 81:92), and an X.28 call isplaced, 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

OPERATIONS


Incoming Call Routing

When creating an asynchronous device, you can assign a Network UserAddress (NUA), which contains network access information and callfacilities that provide the device with network access.

When an asynchronous PAD device is created, ASYNCXS notifiesNET25s Call Processor Task (CPT) that the calling NUA associated withthe device is ready to accept incoming X.25 calls. This is known asregistering for incoming calls. Once a device is registered, ASYNCXS isnotified 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 notnecessarily the same as the device whose calling NUA was registered forincoming calls. The assignment of incoming calls to available terminals isaccomplished using an internal ASYNCXS structure called the PADmaptable. Each PADmap entry has three fields: NUA, call user data, and port.

When an incoming call arrives, ASYNCXS examines the NUA and calluser data (CUD) fields of each PADmap entry against the correspondingfields of the incoming call. If the PADmap NUA field matches the calledNUA field of the incoming call, and if the PADmap CUD field matchesthe CUD field of the incoming call, the PADmap port field specifies whichdevice will be assigned to the call.

If either the NUA or CUD field does not match, or if no available devicecan be assigned by a matching entry, ASYNCXS tries to find a match inthe next PADmap entry. The entire table is processed in sequence untileither a match results in the call being assigned, or the end of the PADmapis reached and the call is rejected.In summary, in order for PAD terminals to accept incoming calls, eachport must be configured with a calling NUA for which the ASYNCXStask will register for incoming calls. In addition, a PADmap table must becreated to direct the routing of incoming calls to available devices. TheNUA specified for a PADmap table entry corresponds to a local (orcalling) network address; this value is compared to the called address fieldof an incoming call request to determine which device is assigned the call.

Port AssignmentWhen an incoming call arrives at the PAD, ASYNCXS examines thecalled address and CUD fields to see if they match the correspondingfields of the PADmap entry. If they do, the value assigned to the port fieldin a PADmap entry is used to locate the port for the incoming call. Arange of values as a port assignment creates a rotary; that is, an incomingcall for a specific NUA is routed to the first available port within therange. This string can take one of the forms listed below; no enclosingquotation marks are required when specifying these strings as inputvalues.

OPERATIONS


Port String Definition* Directs the call to the first available device whose calling. . . . . . . . .

NUA exactly matches the called NUA field of theincoming call.

# Directs the call to the device whose port number is. . . . . . . . . specified in the CUD field of the incoming call. The CUDfield of this PADmap entry must consist of the string P%,P%%, P%%%, or P%%%% to indicate the number ofdigits 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 theincoming 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 are0479.

PADmapThe PADmap table contains entries that define a routing scheme forincoming calls. The ASYNCXS PMM has several commands thatmanage the PADmap: the Add Map command adds an entry, the DeleteMap command removes an entry, the Erase Map command removes allentries, and the Show Map command displays PADmap table entries.

PADmap Routing ExamplesThe following examples illustrate how a PADmap table is used to routeincoming calls.

PADmap Table

NUA CUD PORT

99991032000601 * 116999910320006%% P%%% #9999103200* * #2

Example 1

ASYNCXS routes a call with a called NUA of 99991032000622 and calluser data abc as follows:

The called address (99991032000622) is compared to the NUA field ofthe first PADmap entry (99991032000601); the comparison fails, soASYNCXS moves on to the second entry.

The called address (99991032000622) is compared to the NUA field ofthe second PADmap entry (999910320006%%); the comparison results ina match.

The call user data (abc) is compared to the CUD field of the secondPADmap entry (P%%%); the comparison fails, so ASYNCXS moves onto the third PADmap entry.

OPERATIONS


The called address (99991032000622) is compared to the NUA field ofthe third PADmap entry (9999103200*); the comparison results in amatch.

The call user data (abc) is compared to the CUD field of the thirdPADmap entry (*); the comparison results in a match.

Both the called address and call user data of the third PADmap entrymatch the corresponding fields of the incoming call, so the port field (#2)is examined to determine which device should be assigned to the call. Thisfield instructs ASYNCXS to select the device whose port number isgiven 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 onanother call, the call is routed to it. If the device is not enabled, the call isrejected with a status code indicating that the destination is not obtainable,since there are no more PADmap entries in the table to examine. If thedevice 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 calledNUA of 99991032000600 and call user data P105 as follows:

The called address (99991032000600) is compared to the NUA field ofthe first PADmap entry (99991032000601); the comparison fails, soASYNCXS moves on to the second entry.

The called address (99991032000600) is compared to the NUA field ofthe second PADmap entry (999910320006%%); the comparison results ina match.

The call user data (P105) is compared to the CUD field of the secondPADmap entry (P%%%); the comparison results in a match.

Both called address and call user data of the second PADmap entry matchthe corresponding fields of the incoming call, so the port field (#) isexamined to determine which device should be assigned to the call. Thisfield instructs ASYNCXS to select the device whose port number isgiven by the lower 3 digits of the incoming calls call user data (P105).Thus, if the device whose port number is 105 is enabled and not busy onanother call, the call is routed to it. If the device is not enabled or is busy,ASYNCXS proceeds to the next step.

The called address (99991032000600) is compared to the NUA field ofthe third PADmap entry (9999103200*); the comparison results in amatch.

The call user data (P105) is compared to the CUD field of the thirdPADmap entry (*); the comparison results in a match.

OPERATIONS


Both called address and call user data of the third PADmap entry matchthe corresponding fields of the incoming call, so the port field (#2) isexamined to determine which device should be assigned to the call. Thisfield instructs ASYNCXS to select the device whose port number isgiven by the lower 2 digits of the incoming calls called address (00).Thus, if the device whose port number is 0 is enabled and not busy onanother call, the call is routed to it. If the device is not enabled, the call isrejected with a status code indicating that the destination is not obtainable,since there are no more PADmap entries in the table to examine. If thedevice 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 callassignments are made. In this example, the incoming call is eventuallyassigned to a port number different from that originally specified in theCUD field of the call request packet. If the second and third entries werereversed in the PADmap table, the port number in the CUD field (newentry 3) would only be used if the port identified by the loworder digitsof the NUA field (new entry 2) was unavailable.


3 X.3 Profiles and ParametersThis chapter describes X.3 profiles and parameters, which controlterminals connected to ASYNCXS. The CCITT X.3 recommendationdefines 22 parameters; Telematics offers 16 extended parameters, as wellas extended values for several of the CCITTdefined parameters.

A profile is one complete set of X.3 parameters. Before creating an X.3profile, you must first define a directory for it with the Create Directorycommand.

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 containsall the X.3 parameters to be used when the device is enabled. The initialprofile is created when the device is created (Create Device command).The initial profile can be modified (Modify Device command). The initialprofile is destroyed when the device is destroyed (Destroy Devicecommand).The system administrator can also create, modify, and destroy namedprofiles with

Documents

ECI Telematics ASYNC–XS Manual