Nortel Networks VT100 manual #comment, Action template for accounting application

Page 20

Template files 2-7

Figure 2-4

Action template for accounting application

#Example action template ﬁle: ﬁlename is getbalance.act getbalance accounting reset_cust logout_cust #acctrec chooses the balance option from the main menu acctrec

#acctno speciﬁes the account number for the customer acctno

#customer displays the customer’s account balance customer

In Figure 2-4, action-nameis getbalance, the name of the action template file without the .act extension. The app-nameis accounting. The reset-actionis reset_cust (file name reset_cust.act), and the logout-actionis logout_cust (file name logout_cust.act). Manual mode is omitted because manual mode is not required for this transaction (a description of manual mode follows).

The remaining lines identify the sequence of screens (accrec, acctno, and customer) the TRS must traverse to retrieve the customer billing information. These screens are listed in the order that they must be accessed.

An explanation of each entry in the action template syntax follows.

#comment

The first line of the template in Figure 2-3 is a comment. The comment line is not required but is recommended to describe the purpose of the action template.

Meridian IVR VT100 Gateway Development Guide Product release 2.0/I

Image 20

Contents Meridian IVR Iii Publication historyFebruary Contents Glossary Glossary-1 List of figures Appendix a Host error messagesIVR 2.0/I call flow interface List of procedures List of tablesWho should use this guide How to use this guideAbout 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 applicationApp-name Reset-actionAction-name Reset-action template sequence sample Reset-action template sample Logout-actionLogout action flow Logout-action template sample Manual mode optional fieldScreen-template 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 Text Valid ﬁeld I/O entries Entry Description$num 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 End string KeywordBegin string optional Setting up the trs.conf file Screen.conf fileBoard-number Session-numberInitial-template Initial-action template Initial-action TemplateExample trs.conf File HeartbeatProtocol 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 input buffers Comi cell timeoutComi cell buffer count Setting the Como cell parameters Como cell name Como cell parameter windowComo cell output buffers Como cell blocking?Como cell buffer count Branches of the Como cell Reason the branch would be taken Como cell branchesComo cell 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 Invalid Aid key specified use the Enter Key ERR CH=xx illegal CommandERR Server Node file trs.node does not exist 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 CellGlossary-3 TransactionVT100 terminal Page February