ERR 3270 Envoy Process Startup | Nortel Networks VT100 instruction

A COMI cell was missing in the application or the USER cell did not use function code 2 or 1 to initialize the request. Revise the application.

The flush command was sent before a transaction request was made.

Host error messages A-7

Action to take: None. Notification only.

ERR: 3270 Envoy Process Startup

Meaning: 3270 envoy has been started up.

Action to take: None. Notification only.

ERR: Process Startup

Meaning: The TRS process with no 3270 communication capability has been started up. This TRS process cannot run applications which access a remote host via COMI, COMO, COMA or USER cells.

Action to take: None. Notification only.

ERR: Received a service abort from the TRS Server

Meaning: TRS envoy process receives a message indicating that TRS server is exiting.

Action to take: If the TRS running in server mode was brought down, this is a normal message.

ERR: Received a Service Free Message

Meaning: IVR 2.0/I stopped.

Action to take: None. Normal shutdown notification.

ERR: Accept a connection to client

Meaning: TRS server was unable to accept the TRS envoy’s request for connection.

Action to take: Check the network integrity before consulting a Nortel service representative.

ERR: A flush command was sent prior to any request

Meaning:

Action to take:

Meridian IVR VT100 Gateway Development Guide Product release 2.0/I

Image 81

Nortel Networks VT100 manual ERR 3270 Envoy Process Startup, ERR Process Startup, ERR Received a Service Free Message

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 tables List of procedures How to use this guide About this guideWho should use this guide Additional Nortel manuals Appendix a Host error messagesConventions used in this guide IVR 2.0/I call flow interface 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 Reset-action Action-nameApp-name Reset-action template sequence sample Logout-action Reset-action template sample Logout action flow Manual mode optional field Screen-templateLogout-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 Valid ﬁeld I/O entries Entry Description $numText 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 Keyword Begin string optionalEnd string Screen.conf file Setting up the trs.conf file Session-number Board-number Initial-action template Initial-action Template Initial-template Heartbeat ProtocolExample 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 TRS default communication settings Setting up the com.conf fileDevice-name Terminal-type 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 cell name Call Audit EnabledCall Audit Information Comi action template Comi cell timeout Comi cell buffer countComi cell input buffers Setting the Como cell parameters Como cell parameter window Como cell name Como cell blocking? Como cell buffer countComo cell output buffers Como cell branches Como cellBranches 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 Createscreentemplates ERR LoadruntimeconfigERR Createactiontemplates ERR Ordertemplates ERR xx Sessions are Operational ERR All available sessions are non-operationalERR Unable to create Session Object Instance ERR Unable to create Process Object Instance ERR BD xx SS xxx ERR start host notify ERR xx is not a keywordERR CH=xx ERRRequest does not contain action name ERR CH= xx ERRInvalid action name ERR CH=xx ReadUpdateERR Createtimerinstance ERR CH=xx ReadinputERR CreatetimerinstanceERR CH=xx BD xxx SS xxx ReadinputERR copy PS ERR CH=xx BD xxx SS xxxx ReadinputERR Query cursor ERR Send Aid key failed ERR CH=xx ProcessERR Syntax error for variable operationERR CH=xx ProcessERR write to screen ERR msgwaitstart ERR Received a Service Free Message ERR Received a service abort from the TRS ServerERR 3270 Envoy Process Startup ERR Process Startup ERR CH=xx illegal Command ERR Server Node file trs.node does not existERR Invalid Aid key specified use the Enter Key ERR Sendwithaid failed with return code ERR Sendwithaid Connect to session xx failedERR Writetoscreen Connect request to session xx failed ERR Writetoscreen Writing of input xx failed 10Host error messages ERR Configuration file trs.conf not found ERR Createidletimer Idle timer memory allocation failedERR No Application field in trs.conf ERR An invalid entry in the trs.conf ERR Incorrect syntax for ping action ERR Protocol missing, specify 3270 or VT100ERR Invalid Protocol xxx, protocol ERR Invalid entry non-numeric ERR Last LU cannot be greater than ERR First LU cannot be less thanERR An Invalid Board# xx is specified ERR Couldn’t create appl object ERR In ../3270/buf.datpassword xx exceeds xxx characters ERR In ../3270/lubuf.datloginid xx exceeds xxx charactersERR in map.datSession xx not defined in trs.conf ERR read data from file ../3270/lubuf.dat ERR In ../3270/lubuf.datlubuf2 exceeds xx characters ERR In ../3270/lubuf.datlubuf1 exceeds xx charactersERR Unable to open screen file ERR Memory allocation failure for Screen entry ERR Field id xx exceeds xxx characters ERR Parse string xx of screen ERR Memory allocation failure for Action entry ERR Open action file xx failedERR Read head data from action file ERR Read screen name from action file ERR Unable to open Information Logger ERR Settimer Error setting interval timer structERR Buffer size is greater than ERR No row/column delimiter for screen template VT100 Gateway terms Glossary Channel System administratorComa Cell Comi Cell Transaction VT100 terminalGlossary-3 Page February