Nortel Networks VT100 manual Key-descriptor line syntax

Page 36

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

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 tablesHow 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 interfaceAbout the VT100 Gateway VT100 terminalTerminals connected to a host computer Vt100 VT100 application screen sampleMeridian IVR 2.0/I VT100 Gateway configuration VT100 Gateway softwareTRS communication process 6About the VT100 Gateway Template files Determining the required transactions2Template files Shows how screen templates relate to action templates Customer follows this sequence to retrieve dataAction and screen templates Procedure Accessing transaction information Action templatesAction template syntax Action template syntax#comment Action template for accounting applicationReset-action Action-nameApp-name Reset-action template sequence sample Reset-action template sample Logout-actionLogout 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 applicationScreen template syntax Screen template for accounting application Screen-name Validation-tag offsetValidation-tag Field-descriptorRow,column ﬁeld-name ﬁeld I/O Field-descriptor syntaxTemplate files Valid ﬁeld I/O entries Entry Description $numText Key-descriptor Key-descriptor line syntaxTAB Valid key namesSleep-descriptor optional Sleep-descriptor syntaxInitial-action templates Before using the VT100 Gateway Getting startedScreen.conf file Keyword Begin string optionalEnd string Setting up the trs.conf file Screen.conf fileBoard-number Session-numberInitial-template Initial-action template Initial-action TemplateHeartbeat ProtocolExample trs.conf File Setting up the vt100.ctl file Trs.conf file for accounting applicationVt100.ctl file syntax Vt100.ctl file for accounting applicationSetting up the com.conf file TRS default communication settingsDevice-name Terminal-typeIxon Baud Rate ParityComplete sample transaction Initial-action templateInitial-action template for accounting application TemplatesGetting started 16Getting started Action template performing a transaction 18Getting started Reset-action template for accounting application Action TemplateLogout-action template for accounting application Accessing the mainframe IVR 2.0/I call flow interfaceSetting the Comi cell parameters Activating the gateway from a Comi cellComi cell parameter window Call Audit Enabled Comi cell nameCall Audit Information Comi action templateComi cell timeout Comi cell buffer countComi cell input buffers Setting the Como cell parameters Como cell name Como cell parameter windowComo 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 cellAn 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 ScreensAppendix a Host error messages Terminal Resource Server TRS MessagesERR Loadruntimeconfig ERR CreatescreentemplatesERR Createactiontemplates ERR OrdertemplatesERR All available sessions are non-operational ERR xx Sessions are OperationalERR Unable to create Session Object Instance ERR Unable to create Process Object InstanceERR 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 nameERR 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 cursorERR CH=xx ProcessERR Syntax error for variable operation ERR Send Aid key failedERR CH=xx ProcessERR write to screen ERR msgwaitstartERR Received a service abort from the TRS Server ERR Received a Service Free MessageERR 3270 Envoy Process Startup ERR Process StartupERR 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 failed10Host 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.confERR Protocol missing, specify 3270 or VT100 ERR Incorrect syntax for ping actionERR Invalid Protocol xxx, protocol ERR Invalid entry non-numericERR First LU cannot be less than ERR Last LU cannot be greater thanERR An Invalid Board# xx is specified ERR Couldn’t create appl objectERR 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.datERR 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 entryERR Parse string xx of screen ERR Field id xx exceeds xxx charactersERR Open action file xx failed ERR Memory allocation failure for Action entryERR Read head data from action file ERR Read screen name from action fileERR Settimer Error setting interval timer struct ERR Unable to open Information LoggerERR Buffer size is greater than ERR No row/column delimiter for screen templateGlossary VT100 Gateway termsSystem administrator ChannelComa Cell Comi CellTransaction VT100 terminalGlossary-3 Page February