Nortel Networks VT100 manual Screen.conf file

Page 41

3-2Getting started

screen.conf file

Since the VT100 protocol is character based, it has no built in mechanism for notifying the TRS that host output has ended and the application is ready for input. Creating the screen.conf file allows the TRS to quickly process host output by eliminating the time it spends waiting after host output ends.

The TRS uses the screen.conf file to determine the end of host transmission. The TRS checks every screen sent from the host against the screens you define in screen.conf. Each time the TRS recognizes a complete host screen, it allows the transaction to continue.

The TRS searches each host screen for one of the keywords in screen.conf. When it finds the keyword on the host screen, it then searches for the end of the screen. When it encounters the end of the screen, host output has ended so the TRS allows the transaction to continue. As an added checking mechanism, the TRS can also check for the beginning of the screen to ensure that it is passing along the correct screen.

Screen.conf must reside in the /u/ivr/3270 directory.

Screen.conf should contain the definitions of every screen the TRS will encounter - one definition per line. The order of the lines does not matter since the TRS checks every screen against all the definitions in screen.conf. Figure 3-1 shows the syntax of the screen.conf file.

555-9001-316 Standard 1.0 February 1996

Image 41

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 tables List of proceduresWho should use this guide How to use this guideAbout this guide Additional Nortel manuals Appendix a Host error messagesConventions used in this guide IVR 2.0/I call flow interfaceVT100 terminal About the VT100 GatewayTerminals connected to a host computer VT100 application screen sample Vt100VT100 Gateway software Meridian IVR 2.0/I VT100 Gateway configurationTRS communication process 6About the VT100 Gateway Determining the required transactions Template files2Template files Customer follows this sequence to retrieve data Shows how screen templates relate to action templatesAction and screen templates Action templates Procedure Accessing transaction informationAction template syntax Action template syntaxAction template for accounting application #commentApp-name Reset-actionAction-name Reset-action template sequence sample Logout-action Reset-action template sampleLogout action flow Logout-action template sample Manual mode optional fieldScreen-template Screen templates Screen showing fields and the system prompt Application screen for accounting application Screen template syntaxScreen template syntax Screen template for accounting application Validation-tag offset Screen-nameField-descriptor Validation-tagField-descriptor syntax Row,column ﬁeld-name ﬁeld I/OTemplate files Text Valid ﬁeld I/O entries Entry Description$num Key-descriptor line syntax Key-descriptorValid key names TABSleep-descriptor syntax Sleep-descriptor optionalInitial-action templates Getting started Before using the VT100 GatewayScreen.conf file End string KeywordBegin string optional Screen.conf file Setting up the trs.conf fileSession-number Board-numberInitial-action template Initial-action Template Initial-templateExample trs.conf File HeartbeatProtocol Trs.conf file for accounting application Setting up the vt100.ctl fileVt100.ctl file for accounting application Vt100.ctl file syntaxTRS default communication settings Setting up the com.conf fileDevice-name Terminal-typeIxon Parity Baud RateInitial-action template Complete sample transactionTemplates Initial-action template for accounting applicationGetting started 16Getting started Action template performing a transaction 18Getting started Action Template Reset-action template for accounting applicationLogout-action template for accounting application IVR 2.0/I call flow interface Accessing the mainframeActivating the gateway from a Comi cell Setting the Comi cell parametersComi cell parameter window Comi cell name Call Audit EnabledCall Audit Information Comi action templateComi cell input buffers Comi cell timeoutComi cell buffer count Setting the Como cell parameters Como cell parameter window Como cell nameComo 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 Coma cell in the Cleanup branch of a Start cell Setting the Coma cell parametersAn 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 screensTerminal Resource Server TRS Messages Appendix a Host error messagesERR Createscreentemplates ERR LoadruntimeconfigERR Createactiontemplates ERR OrdertemplatesERR xx Sessions are Operational ERR All available sessions are non-operationalERR Unable to create Session Object Instance ERR Unable to create Process Object InstanceERR 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 nameERR 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 cursorERR Send Aid key failed ERR CH=xx ProcessERR Syntax error for variable operationERR CH=xx ProcessERR write to screen ERR msgwaitstartERR Received a Service Free Message ERR Received a service abort from the TRS ServerERR 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 failed with return code ERR Sendwithaid Connect to session xx failedERR Writetoscreen Connect request to session xx failed ERR Writetoscreen Writing of input xx failed10Host 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.confERR Incorrect syntax for ping action ERR Protocol missing, specify 3270 or VT100ERR Invalid Protocol xxx, protocol ERR Invalid entry non-numericERR Last LU cannot be greater than ERR First LU cannot be less thanERR An Invalid Board# xx is specified ERR Couldn’t create appl objectERR 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.datERR 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 entryERR Field id xx exceeds xxx characters ERR Parse string xx of screenERR Memory allocation failure for Action entry ERR Open action file xx failedERR Read head data from action file ERR Read screen name from action fileERR Unable to open Information Logger ERR Settimer Error setting interval timer structERR Buffer size is greater than ERR No row/column delimiter for screen templateVT100 Gateway terms GlossaryChannel System administratorComa Cell Comi CellGlossary-3 TransactionVT100 terminal Page February