Nortel Networks VT100 manual ERR xx is not a keyword, ERR BD xx SS xxx ERR start host notify

Page 78

A-4Host error messages

Action to take: Contact your Nortel service representative.

ERR: xx is not a keyword

Meaning: The screen template contains an invalid keyword.

Action to take: Revise the screen template. Make sure the KEYWORD (&LOGIN_ID, &PASSWORD, &LU_BUF1 and &LU_BUF2) are spelled correctly.

ERR: BD xx SS xxx ERR: start host notify

Meaning: TRS was unable to communicate with host on Board xx session xxx.

Action to take: Contact your Nortel service representative.

ERR: CH=xx ERR::Request does not contain action name

Meaning: The action template name passed by IVR 2.0/I is a zero-length string.

Action to take: Check the COMI or USER cell used to start an transaction to make sure it contains an action template name.

ERR: CH= xx ERR::Invalid action name xxx

Meaning: The action template name xxx in the USER or COMI cell

was not found under the 3270 directory.

Action to take: Check or create action template file.

ERR: CH=xx ERR::Action xxx not defined in any appl

Meaning: The action template xxx did not define an application name.

Action to take: Revise the action template to add the application name in the appropriate field.

ERR: CH=xx ERR::Appl name xxx not defined in trs.conf

Meaning: The application name defined in the action template did not match any application name defined in the trs.conf file.

Action to take: Revise the trs.conf or the action template to make sure the application name matches.

555-9001-316 Standard 1.0 February 1996

Image 78

Contents Meridian IVR Publication history FebruaryIii Contents Appendix a Host error messages IVR 2.0/I call flow interfaceGlossary Glossary-1 List of figures List of procedures List of tablesHow to use this guide About 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 applicationReset-action Action-nameApp-name Reset-action template sequence sample Reset-action template sample Logout-actionLogout action flow Manual mode optional field Screen-templateLogout-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 Valid ﬁeld I/O entries Entry Description $numText 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 Keyword Begin string optionalEnd string Setting up the trs.conf file Screen.conf fileBoard-number Session-numberInitial-template Initial-action template Initial-action TemplateHeartbeat ProtocolExample 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 timeout Comi cell buffer countComi cell input buffers Setting the Como cell parameters Como cell name Como cell parameter windowComo cell blocking? Como cell buffer countComo cell output buffers Como cell branches Como cellBranches 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 Screens Appendix 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 CH=xx illegal Command ERR Server Node file trs.node does not existERR 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 CellTransaction VT100 terminalGlossary-3 Page February