Additional Nortel manuals | Nortel Networks VT100 specification

xAbout this guide

Chapter 4: IVR 2.0/I call flow interface

This chapter explains how to integrate the templates you created in Chapter 3 with your Meridian IVR 2.0/I application call flow.

Appendix A: Host error messages

This appendix lists error messages and provides information on troubleshooting.

Additional Nortel manuals

You may find the following manuals useful while reading this manual.

Manual	NTP Number

Meridian IVR Application Development Guide	NTP 555-9001-310

Meridian IVR System Administration Guide	NTP 555-9001-300

Conventions used in this guide

Throughout this guide, several typographic conventions have been used to highlight certain types of information.

•Items that are part of the Meridian IVR 2.0/I screens appear in quotes (for example, “Function Code” in the parameters window).

•Meridian IVR 2.0/I buffer names are shown in all upper case characters (for example, the CURRENT MESSAGE buffer).

•Items that are file names or messages are shown in bold (for example, the /u/ivr/vt100/getbalance.act file).

For convenience, this guide uses the keyname <Enter> to represent both the Enter and Return keys.

555-9001-316 Standard 1.0 February 1996

Image 7

Nortel Networks VT100 Additional Nortel manuals, Conventions used in this guide, IVR 2.0/I call flow interface

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 tables List of procedures About this guide How to use this guideWho should use 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 Gateway Terminals connected to a host computer VT100 application screen sample Vt100 VT100 Gateway software Meridian IVR 2.0/I VT100 Gateway configuration TRS communication process 6About the VT100 Gateway Determining the required transactions Template files 2Template files Customer follows this sequence to retrieve data Shows how screen templates relate to action templates Action and screen templates Action templates Procedure Accessing transaction information Action template syntax Action template syntax Action template for accounting application #comment Action-name Reset-actionApp-name Reset-action template sequence sample Logout-action Reset-action template sample Logout action flow Screen-template Manual mode optional fieldLogout-action template sample Screen templates Screen showing fields and the system prompt Application screen for accounting application Screen template syntax Screen template syntax Screen template for accounting application Validation-tag offset Screen-name Field-descriptor Validation-tag Field-descriptor syntax Row,column ﬁeld-name ﬁeld I/O Template files $num Valid ﬁeld I/O entries Entry DescriptionText Key-descriptor line syntax Key-descriptor Valid key names TAB Sleep-descriptor syntax Sleep-descriptor optional Initial-action templates Getting started Before using the VT100 Gateway Screen.conf file Begin string optional KeywordEnd string Screen.conf file Setting up the trs.conf file Session-number Board-number Initial-action template Initial-action Template Initial-template Protocol HeartbeatExample trs.conf File Trs.conf file for accounting application Setting up the vt100.ctl file Vt100.ctl file for accounting application Vt100.ctl file syntax Terminal-type Setting up the com.conf fileTRS default communication settings Device-name Ixon Parity Baud Rate Initial-action template Complete sample transaction Templates Initial-action template for accounting application Getting started 16Getting started Action template performing a transaction 18Getting started Action Template Reset-action template for accounting application Logout-action template for accounting application IVR 2.0/I call flow interface Accessing the mainframe Activating the gateway from a Comi cell Setting the Comi cell parameters Comi cell parameter window Comi action template Call Audit EnabledComi cell name Call Audit Information Comi cell buffer count Comi cell timeoutComi cell input buffers Setting the Como cell parameters Como cell parameter window Como cell name Como 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 Coma cell in the Cleanup branch of a Start cell Setting the Coma cell parameters 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 Templates Corresponding Screens COMI/COMO cell parameters, TRS templates, and VT100 screens Terminal Resource Server TRS Messages Appendix a Host error messages ERR Ordertemplates ERR LoadruntimeconfigERR Createscreentemplates ERR Createactiontemplates ERR Unable to create Process Object Instance ERR All available sessions are non-operationalERR xx Sessions are Operational ERR Unable to create Session Object Instance ERR 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 name ERR 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 PS ERR msgwaitstart ERR CH=xx ProcessERR Syntax error for variable operationERR Send Aid key failed ERR CH=xx ProcessERR write to screen ERR Process Startup ERR Received a service abort from the TRS ServerERR Received a Service Free Message ERR 3270 Envoy Process Startup ERR Server Node file trs.node does not exist ERR CH=xx illegal CommandERR Invalid Aid key specified use the Enter Key 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 failed 10Host 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.conf ERR Invalid entry non-numeric ERR Protocol missing, specify 3270 or VT100ERR Incorrect syntax for ping action ERR Invalid Protocol xxx, protocol ERR Couldn’t create appl object ERR First LU cannot be less thanERR Last LU cannot be greater than ERR An Invalid Board# xx is specified ERR 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.conf ERR 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 file ERR Field id xx exceeds xxx characters ERR Parse string xx of screen ERR Read screen name from action file ERR Open action file xx failedERR Memory allocation failure for Action entry ERR Read head data from action file ERR No row/column delimiter for screen template ERR Settimer Error setting interval timer structERR Unable to open Information Logger ERR Buffer size is greater than VT100 Gateway terms Glossary Comi Cell System administratorChannel Coma Cell VT100 terminal TransactionGlossary-3 Page February