ERR Protocol missing, specify 3270 or VT100 | Nortel Networks

Check the syntax of the trs.conf file.

The board number was missing from the board field of the trs.conf file.

A-12Host error messages

ERR: Protocol missing, specify 3270 or VT100

Meaning: The protocol type was missing from the trs.conf protocol field.

Action to take: Make sure that ‘3270’ or ‘vt100’ is specified in the protocol field.

ERR: Incorrect syntax for ping action

Meaning: The heartbeat action template was specified incorrectly in the trs.conf file.

Action to take: Revise the trs.conf file so that the heartbeat field has the correct syntax.

ERR: Invalid Protocol xxx, protocol

Meaning: xxx is an invalid protocol.

Action to take: Revise the trs.conf file so that the protocol is either ‘3270’ or ‘vt100’.

ERR: Invalid entry non-numeric

Meaning: A non-numeric symbol occurred in the board number or session number field of the trs.conf file.

Action to take: Check the syntax of the trs.conf file.

ERR: A board # was not specified in the trs.conf

Meaning:

Action to take:

ERR: Possibly exceeded number of allowable boards

Meaning: The number of total boards defined in the trs.conf file exceeds the total number of boards the system allowed.

Action to take: Revise the trs.conf file and make sure the total board number does not exceed the maximum allowed which is 4.

555-9001-316 Standard 1.0 February 1996

Image 86

Nortel Networks manual ERR Protocol missing, specify 3270 or VT100, ERR Incorrect syntax for ping action

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