Key-descriptor line syntax | Nortel Networks VT100 instruction

Template files 2-23

When entering a field-descriptor, the entries on the line should be separated by white space or tab characters. If you are entering text for the field I/O, the TRS ignores any white space you include with the value until it encounters the new line character (e.g., the value includes several words).

Note: The order of the field-descriptorlines in your screen template file determines how data is entered and retrieved from the screens and written into the input and output buffers of a COMO cell. Chapter 4 describes how to use Meridian IVR 2.0/I cells to retrieve data from the host computer.

key-descriptor

Identifies a key to be used with the screen. To send information to the computer for processing or to execute a command, the terminal operator presses a key on the terminal keyboard. If you do not specify a key, nothing is sent to the host and the current screen does not change. The key could be the ENTER key or a function key. The format of this line is similar to the field-descriptor. Figure 2-14 contains the format of the key-descriptor.

Figure 2-14

Key-descriptor line syntax

position-indicator > keyname

position-indicatorThis entry should be set to 0,0.

>This character indicates that this line contains a key.

Meridian IVR VT100 Gateway Development Guide Product release 2.0/I

Image 36

Nortel Networks VT100 manual Key-descriptor line syntax

Contents

Meridian IVR Publication history FebruaryIii Contents Appendix a Host error messages IVR 2.0/I call flow interfaceGlossary Glossary-1 List of figures List of procedures List of tables How to use this guide About this guideWho should use this guide Appendix a Host error messages Additional Nortel manualsConventions used in this guide IVR 2.0/I call flow interface About the VT100 Gateway VT100 terminal Terminals connected to a host computer Vt100 VT100 application screen sample Meridian IVR 2.0/I VT100 Gateway configuration VT100 Gateway software TRS communication process 6About the VT100 Gateway Template files Determining the required transactions 2Template files Shows how screen templates relate to action templates Customer follows this sequence to retrieve data Action and screen templates Procedure Accessing transaction information Action templates Action template syntax Action template syntax #comment Action template for accounting application Reset-action Action-nameApp-name Reset-action template sequence sample Reset-action template sample Logout-action Logout action flow Manual mode optional field Screen-templateLogout-action template sample Screen templates Screen showing fields and the system prompt Screen template syntax Application screen for accounting application Screen template syntax Screen template for accounting application Screen-name Validation-tag offset Validation-tag Field-descriptor Row,column ﬁeld-name ﬁeld I/O Field-descriptor syntax Template files Valid ﬁeld I/O entries Entry Description $numText Key-descriptor Key-descriptor line syntax TAB Valid key names Sleep-descriptor optional Sleep-descriptor syntax Initial-action templates Before using the VT100 Gateway Getting started Screen.conf file Keyword Begin string optionalEnd string Setting up the trs.conf file Screen.conf file Board-number Session-number Initial-template Initial-action template Initial-action Template Heartbeat ProtocolExample trs.conf File Setting up the vt100.ctl file Trs.conf file for accounting application Vt100.ctl file syntax Vt100.ctl file for accounting application Setting up the com.conf file TRS default communication settingsDevice-name Terminal-type Ixon Baud Rate Parity Complete sample transaction Initial-action template Initial-action template for accounting application Templates Getting started 16Getting started Action template performing a transaction 18Getting started Reset-action template for accounting application Action Template Logout-action template for accounting application Accessing the mainframe IVR 2.0/I call flow interface Setting the Comi cell parameters Activating the gateway from a Comi cell Comi cell parameter window Call Audit Enabled Comi cell nameCall Audit Information Comi action template Comi cell timeout Comi cell buffer countComi cell input buffers Setting the Como cell parameters Como cell name Como cell parameter window Como cell blocking? Como cell buffer countComo cell output buffers Como cell branches Como cellBranches of the Como cell Reason the branch would be taken Setting the Coma cell parameters Coma cell in the Cleanup branch of a Start cell 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 COMI/COMO cell parameters, TRS templates, and VT100 screens Templates Corresponding Screens Appendix a Host error messages Terminal Resource Server TRS Messages ERR Loadruntimeconfig ERR CreatescreentemplatesERR Createactiontemplates ERR Ordertemplates ERR All available sessions are non-operational ERR xx Sessions are OperationalERR Unable to create Session Object Instance ERR Unable to create Process Object Instance ERR xx is not a keyword ERR BD xx SS xxx ERR start host notifyERR CH=xx ERRRequest does not contain action name ERR CH= xx ERRInvalid action name ERR CH=xx ReadinputERR Createtimerinstance ERR CH=xx ReadUpdateERR CreatetimerinstanceERR CH=xx BD xxx SS xxx ReadinputERR copy PS ERR CH=xx BD xxx SS xxxx ReadinputERR Query cursor ERR CH=xx ProcessERR Syntax error for variable operation ERR Send Aid key failedERR CH=xx ProcessERR write to screen ERR msgwaitstart ERR Received a service abort from the TRS Server ERR Received a Service Free MessageERR 3270 Envoy Process Startup ERR Process Startup ERR CH=xx illegal Command ERR Server Node file trs.node does not existERR Invalid Aid key specified use the Enter Key ERR Sendwithaid Connect to session xx failed ERR Sendwithaid failed with return codeERR Writetoscreen Connect request to session xx failed ERR Writetoscreen Writing of input xx failed 10Host error messages ERR Createidletimer Idle timer memory allocation failed ERR Configuration file trs.conf not foundERR No Application field in trs.conf ERR An invalid entry in the trs.conf ERR Protocol missing, specify 3270 or VT100 ERR Incorrect syntax for ping actionERR Invalid Protocol xxx, protocol ERR Invalid entry non-numeric ERR First LU cannot be less than ERR Last LU cannot be greater thanERR An Invalid Board# xx is specified ERR Couldn’t create appl object ERR In ../3270/lubuf.datloginid xx exceeds xxx characters ERR In ../3270/buf.datpassword 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.datlubuf1 exceeds xx characters ERR In ../3270/lubuf.datlubuf2 exceeds xx charactersERR Unable to open screen file ERR Memory allocation failure for Screen entry ERR Parse string xx of screen ERR Field id xx exceeds xxx characters ERR Open action file xx failed ERR Memory allocation failure for Action entryERR Read head data from action file ERR Read screen name from action file ERR Settimer Error setting interval timer struct ERR Unable to open Information LoggerERR Buffer size is greater than ERR No row/column delimiter for screen template Glossary VT100 Gateway terms System administrator ChannelComa Cell Comi Cell Transaction VT100 terminalGlossary-3 Page February