Nortel Networks VT100 manual Heartbeat, Protocol, Example trs.conf File

Page 46

Getting started 3-7

heartbeat

You can specify an optional heartbeat action for the application specified by app-name. You can use this feature to send an indication to the host that a session is still active. Some hosts log out sessions that remain idle for a period of time. You can also use the heartbeat action to check connectivity, verifying that the session remains on the appropriate screen. Typically, the heartbeat action contains a logout-action template which brings the session back to the login screen if the connectivity with the mainframe fails. If you do not need a heartbeat action, enter a hyphen for this action.

You specify the heartbeat in this format: actiontemplate@n, where n is the number of seconds between each execution of the action template when the session is idle.

The heartbeat action template uses the same syntax as the action templates described earlier in this chapter, and usually only specifies a single screen template. That screen template is usually the last screen specified in the initial-action template. Typically, your screen template would only include a key-descriptorline, usually the ENTER key and validation-tag.

protocol

The protocol entry indicates the communications protocol being used by app-name. This field is required and should be set to vt100.

Example “trs.conf” File

Consider the following example. Initial-action template files login.act and signin.act have been defined and reside in the /u/ivr/3270 directory. There are four applications which you want to access on the host computer:

•accounting, accesses the accounting software

•market, tracks stock market activity

•banking, retrieves credit balances

•airline, for purchasing tickets on a local commuter carrier

The application names shown here are not necessarily the actual names assigned on the host computer, but they are the names assigned on the application processor for the trs.conf file and all action templates that use these applications.

Meridian IVR VT100 Gateway Development Guide Product release 2.0/I

Image 46

Contents Meridian IVR February Publication historyIii Contents IVR 2.0/I call flow interface Appendix a Host error messagesGlossary Glossary-1 List of figures List of procedures List of tablesAbout this guide How to use this guideWho should use this guide Conventions used in this guide Appendix a Host error messagesAdditional Nortel manuals 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 applicationAction-name Reset-actionApp-name Reset-action template sequence sample Reset-action template sample Logout-actionLogout action flow Screen-template Manual mode optional fieldLogout-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 $num Valid ﬁeld I/O entries Entry DescriptionText 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 Begin string optional KeywordEnd string Setting up the trs.conf file Screen.conf fileBoard-number Session-numberInitial-template Initial-action template Initial-action TemplateProtocol HeartbeatExample trs.conf File Setting up the vt100.ctl file Trs.conf file for accounting applicationVt100.ctl file syntax Vt100.ctl file for accounting applicationDevice-name Setting up the com.conf fileTRS default communication settings 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 Information Call Audit EnabledComi cell name Comi action templateComi cell buffer count Comi cell timeoutComi cell input buffers Setting the Como cell parameters Como cell name Como cell parameter windowComo cell buffer count Como cell blocking?Como cell output buffers Como cell Como cell branchesBranches 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 Createactiontemplates ERR LoadruntimeconfigERR Createscreentemplates ERR OrdertemplatesERR Unable to create Session Object Instance ERR All available sessions are non-operationalERR xx Sessions are Operational ERR Unable to create Process Object InstanceERR 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 nameERR 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 cursorERR CH=xx ProcessERR write to screen ERR CH=xx ProcessERR Syntax error for variable operationERR Send Aid key failed ERR msgwaitstartERR 3270 Envoy Process Startup ERR Received a service abort from the TRS ServerERR Received a Service Free Message ERR Process StartupERR Server Node file trs.node does not exist ERR CH=xx illegal CommandERR 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 failed10Host 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.confERR Invalid Protocol xxx, protocol ERR Protocol missing, specify 3270 or VT100ERR Incorrect syntax for ping action ERR Invalid entry non-numericERR An Invalid Board# xx is specified ERR First LU cannot be less thanERR Last LU cannot be greater than ERR Couldn’t create appl objectERR 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.datERR 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 entryERR Parse string xx of screen ERR Field id xx exceeds xxx charactersERR Read head data from action file ERR Open action file xx failedERR Memory allocation failure for Action entry ERR Read screen name from action fileERR Buffer size is greater than ERR Settimer Error setting interval timer structERR Unable to open Information Logger ERR No row/column delimiter for screen templateGlossary VT100 Gateway termsComa Cell System administratorChannel Comi CellVT100 terminal TransactionGlossary-3 Page February