Getting started | Nortel Networks VT100 guide

Getting started 3-15

The screen template acctlog1.scn does the following:

•enters the login name

•enters the password

•waits three seconds for the host to process the login action

The screen template acctlog2.scn does the following:

•at the system prompt, enters the command to run the application

•types the ENTER key to start the application

•waits five seconds for the host to run the accounting application

The screen template atacctmenu.scn validates the accounting main menu screen, but performs no action.

The acctlog1 and acctlog2 screen templates use “0,0” as the row,column location and a hyphen for the field-tagto indicate that all text will be entered at the current cursor position. This method is used because the login prompt and the first prompt may not always appear in the same location on the screen. Prompts vary from system to system, and can include longer, customized names.

Note: No key-descriptoris specified for the “atacctmenu” screen template. This means once the screen is validated, this screen remains active until the next transaction is executed.

The initial-action template shown in Figure 3-10 specifies the clinit.act logout-action template, and does not specify a reset-action template.

Figure 3-10 shows the clinit logout-action template, its corresponding screen templates, and the associated application screens.

Meridian IVR VT100 Gateway Development Guide Product release 2.0/I

Image 54

Nortel Networks VT100 manual Getting started

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 Conventions used in this guide Appendix a Host error messagesAdditional Nortel manuals 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 Device-name Setting up the com.conf fileTRS default communication settings 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 Information Call Audit EnabledComi cell name 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 Createactiontemplates ERR LoadruntimeconfigERR Createscreentemplates ERR Ordertemplates ERR Unable to create Session Object Instance ERR All available sessions are non-operationalERR xx Sessions are Operational ERR Unable to create Process Object Instance ERR CH=xx ERRRequest does not contain action name ERR xx is not a keywordERR BD xx SS xxx ERR start host notify ERR CH= xx ERRInvalid action name ERR CH=xx BD xxx SS xxx ReadinputERR copy PS ERR CH=xx ReadinputERR CreatetimerinstanceERR CH=xx ReadUpdateERR Createtimerinstance ERR CH=xx BD xxx SS xxxx ReadinputERR Query cursor ERR CH=xx ProcessERR write to screen ERR CH=xx ProcessERR Syntax error for variable operationERR Send Aid key failed ERR msgwaitstart ERR 3270 Envoy Process Startup ERR Received a service abort from the TRS ServerERR Received a Service Free Message 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 Writetoscreen Connect request to session xx failed ERR Sendwithaid Connect to session xx failedERR Sendwithaid failed with return code ERR Writetoscreen Writing of input xx failed 10Host error messages ERR No Application field in trs.conf ERR Createidletimer Idle timer memory allocation failedERR Configuration file trs.conf not found ERR An invalid entry in the trs.conf ERR Invalid Protocol xxx, protocol ERR Protocol missing, specify 3270 or VT100ERR Incorrect syntax for ping action ERR Invalid entry non-numeric ERR An Invalid Board# xx is specified ERR First LU cannot be less thanERR Last LU cannot be greater than ERR Couldn’t create appl object ERR in map.datSession xx not defined in trs.conf ERR In ../3270/lubuf.datloginid xx exceeds xxx charactersERR In ../3270/buf.datpassword xx exceeds xxx characters ERR read data from file ../3270/lubuf.dat ERR Unable to open screen file ERR In ../3270/lubuf.datlubuf1 exceeds xx charactersERR In ../3270/lubuf.datlubuf2 exceeds xx characters ERR Memory allocation failure for Screen entry ERR Parse string xx of screen ERR Field id xx exceeds xxx characters ERR Read head data from action file ERR Open action file xx failedERR Memory allocation failure for Action entry ERR Read screen name from action file ERR Buffer size is greater than ERR Settimer Error setting interval timer structERR Unable to open Information Logger ERR No row/column delimiter for screen template Glossary VT100 Gateway terms Coma Cell System administratorChannel Comi Cell Transaction VT100 terminalGlossary-3 Page February