Nortel Networks VT100 manual ERR Open action file xx failed, ERR Read head data from action file

Page 91

Host error messages A-17

Action to take: Revise the application to keep the screen templates within the limit specified by xx.

ERR: Open action file xx failed

Meaning: TRS failed to open the action file xx.

Action to take: Create or change permissions of the action template file to readable.

ERR: Memory allocation failure for ACTION entry

Meaning: TRS was unable to allocate memory for the action structure.

Action to take: Contact your Nortel service representative.

ERR: Read head data from action file xx

Meaning: Syntax error in the header section of the action template file.

Action to take: Check the syntax of the header section of the action template file.

ERR: Read screen name from action file xx

Meaning: The screen name was missing from the action template file xx.

Action to take: Add appropriate screen names under the header section of the action template file.

ERR: Action xx exceeds max screen entries xxx

Meaning: There are too many screens defined in the action template file xx.

Action to take: Revise the action template file to keep the total number of

screens within the limit specified by xxx.

ERR: Screen xx of Action xxx not found

Meaning: Screen xx defined in the action template xxx was not found under the 3270 directory.

Action to take: Create the appropriate screen template file.

Meridian IVR VT100 Gateway Development Guide Product release 2.0/I

Image 91

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 proceduresAbout 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 guideVT100 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 #commentAction-name Reset-actionApp-name Reset-action template sequence sample Logout-action Reset-action template sampleLogout 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 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 $num Valid ﬁeld I/O entries Entry DescriptionText 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 Begin string optional KeywordEnd string Screen.conf file Setting up the trs.conf fileSession-number Board-numberInitial-action template Initial-action Template Initial-templateProtocol HeartbeatExample trs.conf File 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 buffer count Comi cell timeoutComi cell input buffers Setting the Como cell parameters Como cell parameter window Como cell nameComo 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 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 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 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 CellVT100 terminal TransactionGlossary-3 Page February