Nortel Networks manual VT100 Gateway software, Meridian IVR 2.0/I VT100 Gateway configuration

Page 11

1-4About the VT100 Gateway

The VT100 Gateway software

You can install the Meridian IVR 2.0/I VT100 Gateway on Intel’s new generation 64-bit PentiumTM microprocessor. To support the VT100 Gateway, the application processor must

•have an ACCESS link connected to Meridian Mail

•be connected to one or more host computers via an asynchronous connection

•have enough serial ports to provide enough terminal connections (one digiBoard with 8 ports per card)

Northern Telecom (Nortel) does not supply the VT100 communication hardware. Figure 1-3 shows the typical hardware configuration for processing VT100 terminal sessions.

Figure 1-3

Meridian IVR 2.0/I VT100 Gateway configuration

Async

ACCESS Link

HOST	MIVR	MERIDIAN MAIL
	(Application processor)

555-9001-316 Standard 1.0 February 1996

Image 11

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