Setting up the com.conf file, Device-name | Nortel Networks VT100

3-10Getting started

The follow sections describe each entry in the vt100.ctl file.

session-number

The session-numberentry specifies the session this line defines. For example, the first line in Figure 3-7 defines the terminal type to be used for session 2. The entry must be a single number, ranging from 2 to 16. You do not need to list the sessions in numerical order, and you can skip session numbers.

device-name

The device-nameentry is the exact name of the device file in the /dev directory to use for the VT100 Gateway for the specified sessions. Use the full directory path (as shown in Figure 3-7) when entering the device file name. You can set all necessary operating modes (e.g., baud rate, representation parameters, flow control, etc.) in the com.conf file discussed in the next section.

terminal-type

The terminal-typeentry defines the type of terminal to be emulated by the TRS process. For this release of the VT100 Gateway, this entry is always “vt100.” This field is included to support future releases that may allow additional terminal types.

Setting up the com.conf file

com.conf sets the communication attributes of the serial port. The com.conf file allows the adjustment of the terminal I/O options for the host’s input device, which in this case is the IVR 2.0/I TRS process. If the com.conf file does not exist, the TRS uses its hardcoded default values. Table 3-1 shows the TRS default communication settings.

Table 3-1

TRS default communication settings

Baud Rate:	9600

Parity:	None

Stop Bit:	1

555-9001-316 Standard 1.0 February 1996

Image 49

Nortel Networks VT100 manual Setting up the com.conf file, Device-name, Terminal-type, TRS default communication settings

Contents

Meridian IVR February Publication historyIii Contents IVR 2.0/I call flow interface Appendix a Host error messagesGlossary Glossary-1 List of figures List of tables List of procedures About this guide How to use this guideWho should use this guide Additional Nortel manuals Appendix a Host error messagesConventions used in this guide IVR 2.0/I call flow interface VT100 terminal About the VT100 Gateway Terminals connected to a host computer VT100 application screen sample Vt100 VT100 Gateway software Meridian IVR 2.0/I VT100 Gateway configuration TRS communication process 6About the VT100 Gateway Determining the required transactions Template files 2Template files Customer follows this sequence to retrieve data Shows how screen templates relate to action templates Action and screen templates Action templates Procedure Accessing transaction information Action template syntax Action template syntax Action template for accounting application #comment Action-name Reset-actionApp-name Reset-action template sequence sample Logout-action Reset-action template sample Logout action flow Screen-template Manual mode optional fieldLogout-action template sample Screen templates Screen showing fields and the system prompt Application screen for accounting application Screen template syntax Screen template syntax Screen template for accounting application Validation-tag offset Screen-name Field-descriptor Validation-tag Field-descriptor syntax Row,column ﬁeld-name ﬁeld I/O Template files $num Valid ﬁeld I/O entries Entry DescriptionText Key-descriptor line syntax Key-descriptor Valid key names TAB Sleep-descriptor syntax Sleep-descriptor optional Initial-action templates Getting started Before using the VT100 Gateway Screen.conf file Begin string optional KeywordEnd string Screen.conf file Setting up the trs.conf file Session-number Board-number Initial-action template Initial-action Template Initial-template Protocol HeartbeatExample trs.conf File Trs.conf file for accounting application Setting up the vt100.ctl file Vt100.ctl file for accounting application Vt100.ctl file syntax TRS default communication settings Setting up the com.conf fileDevice-name Terminal-type Ixon Parity Baud Rate Initial-action template Complete sample transaction Templates Initial-action template for accounting application Getting started 16Getting started Action template performing a transaction 18Getting started Action Template Reset-action template for accounting application Logout-action template for accounting application IVR 2.0/I call flow interface Accessing the mainframe Activating the gateway from a Comi cell Setting the Comi cell parameters Comi cell parameter window Comi cell name Call Audit EnabledCall Audit Information Comi action template Comi cell buffer count Comi cell timeoutComi cell input buffers Setting the Como cell parameters Como cell parameter window Como cell name Como cell buffer count Como cell blocking?Como cell output buffers Como cell Como cell branchesBranches of the Como cell Reason the branch would be taken Coma cell in the Cleanup branch of a Start cell Setting the Coma cell parameters An application using the COMI, COMO, and Coma cells 12IVR 2.0/I call flow interface Application cell functions Step Description 14IVR 2.0/I call flow interface Templates Corresponding Screens COMI/COMO cell parameters, TRS templates, and VT100 screens Terminal Resource Server TRS Messages Appendix a Host error messages ERR Createscreentemplates ERR LoadruntimeconfigERR Createactiontemplates ERR Ordertemplates ERR xx Sessions are Operational ERR All available sessions are non-operationalERR Unable to create Session Object Instance ERR Unable to create Process Object Instance ERR BD xx SS xxx ERR start host notify ERR xx is not a keywordERR CH=xx ERRRequest does not contain action name ERR CH= xx ERRInvalid action name ERR CH=xx ReadUpdateERR Createtimerinstance ERR CH=xx ReadinputERR CreatetimerinstanceERR CH=xx BD xxx SS xxx ReadinputERR copy PS ERR CH=xx BD xxx SS xxxx ReadinputERR Query cursor ERR Send Aid key failed ERR CH=xx ProcessERR Syntax error for variable operationERR CH=xx ProcessERR write to screen ERR msgwaitstart ERR Received a Service Free Message ERR Received a service abort from the TRS ServerERR 3270 Envoy Process Startup ERR Process Startup ERR Server Node file trs.node does not exist ERR CH=xx illegal CommandERR Invalid Aid key specified use the Enter Key ERR Sendwithaid failed with return code ERR Sendwithaid Connect to session xx failedERR Writetoscreen Connect request to session xx failed ERR Writetoscreen Writing of input xx failed 10Host error messages ERR Configuration file trs.conf not found ERR Createidletimer Idle timer memory allocation failedERR No Application field in trs.conf ERR An invalid entry in the trs.conf ERR Incorrect syntax for ping action ERR Protocol missing, specify 3270 or VT100ERR Invalid Protocol xxx, protocol ERR Invalid entry non-numeric ERR Last LU cannot be greater than ERR First LU cannot be less thanERR An Invalid Board# xx is specified ERR Couldn’t create appl object ERR In ../3270/buf.datpassword xx exceeds xxx characters ERR In ../3270/lubuf.datloginid xx exceeds xxx charactersERR in map.datSession xx not defined in trs.conf ERR read data from file ../3270/lubuf.dat ERR In ../3270/lubuf.datlubuf2 exceeds xx characters ERR In ../3270/lubuf.datlubuf1 exceeds xx charactersERR Unable to open screen file ERR Memory allocation failure for Screen entry ERR Field id xx exceeds xxx characters ERR Parse string xx of screen ERR Memory allocation failure for Action entry ERR Open action file xx failedERR Read head data from action file ERR Read screen name from action file ERR Unable to open Information Logger ERR Settimer Error setting interval timer structERR Buffer size is greater than ERR No row/column delimiter for screen template VT100 Gateway terms Glossary Channel System administratorComa Cell Comi Cell VT100 terminal TransactionGlossary-3 Page February