VTAM Processing

Self-explanatory message.

VTAM INITIALIZATION STARTING

This message is associated with Com-plete VTAM support and is issued when Com-plete VTAM support is started, either via a VTAM START command or when VTAM=YES is specified in the Com-plete startup parameters.

Processing continues.

Informational message.

VTAM INITIALIZATION COMPLETE

This message is associated with Com-plete VTAM support and is issued when Com-plete VTAM initialisation has completed (see ZVT00001). Other messages may be issued that may indicate a non-successful completion.

Processing continues.

Informational message.

THIS TERMINAL IS CONNECTED TO Com-plete

This message is associated with Com-plete VTAM support. The message is written to a non-hardcopy terminal by Com-plete's VTAM interface. It indicates that the terminal (on which the message appears) has been successfully logged on to Com-plete from the network solicitor or VTAM.

None.

When this message appears, you may use the terminal to log on (i.e., '*ULOG utility') and proceed to use any Com-plete application program or utility for which you are authorised.

Self-explanatory message.

Self-explanatory message.

A call to function $1 subfunction $2 unexpectedly returned return code $3 and reason code $4.

Depends on the kind of function that failed and on the severity of the error.

Send the joblog to Software AG Support.

$ FAILED

This message is associated with Com-plete VTAM support and shows the name of the VTAM macro that failed (e.g., MODCB, SHOWCB, GENCB, or TESTCB). A logic error has occurred in Com-plete or VTAM. This message is printed whenever any of the above macros gets a non-zero return code.

Com-plete abends with a S0C6.

Contact your technical support representative.

Contact your system programmer.

This message is associated with Com-plete VTAM support. A VTAM macro (OPEN or CLOSE) has failed and this message shows the return code and ACB error (decimal). These values are documented by VTAM. This message is printed whenever a VTAM OPEN or CLOSE gets a non-zero return code. This message may be accompanied by message VTM1003.

Processing continues. Initialisation is terminated. CLOSE may not be finished, depending upon the error.

Correct the error or contact your technical representative.

Correct the error or contact your system programmer.

Self-explanatory message.

Self-explanatory message.

VTAM IS ALREADY STARTED

This message is associated with Com-plete VTAM support. Com-plete VTAM support is already started. This message can be the result of issuing VTAM START after it has already been done or after the VTAM=YES PARM has already been started.

Processing continues. VTAM support is not affected.

Code VTAM=NO if the operator is to start VTAM support.

Avoid issuing VTAM START when VTAM support is already active.

VTAM CLOSEDOWN COMPLETE

This message is associated with Com-plete VTAM support. The operator has requested that VTAM support be stopped via the VTAM STOP command. STOP processing has completed. ALL LUs have been released.

Processing continues. VTAM support is stopped.

Informational message.

A request was made to start the VTAM interface again under Com-plete . This is not possible because the interface is currently in a quiesced state as a result of the quiesce operator command. The VTAM interface may only be restarted once it has been fully stopped.

The request to start the VTAM interface is ignored and VTAM is left in the quiesced state.

To restart the VTAM interface, the intreface must be stopped via a VTAM STOP operator command. Once this has completed successfully, the START request will be accepted. Note however, that the VTAM STOP command will terminate all sessions currently outstanding with Com-plete .

Self-explanatory message.

See the Com-plete Computer Operator's Manual

VTAM session persistence has been turned on or off as per $1.

This message indicates that Com-plete has been configured to support persistent VTAM sessions, and the current number of persistent sessions as reported by VTAM. Following this message, Com-plete will attempt to recover these sessions (if any).

Processing continues.

In order to be able to support persistent VTAM sessions, Com-plete must be connected to a Coupling Facility structure, to be specified using sysparm XCF-STRUCTURE. Either this sysparm is not set, or the connection failed.

Startup continues. VTAM sessions will be non-persistent, consequently no session recovery will be possible after a Com-plete or system failure.

Make sure sysparm XCF-STRUCTURE= refers to a valid Coupling Facility list structure.

If sysparm XCF-STRUCTURE= is specified, check the console or joblog for messages indicating why Com-plete failed to connect to that Coupling Facility structure.

During Com-plete startup or processing of a VTAM START command, a persistent VTAM session has been successfully restored. $4 indicates the state of the session at session loss time: Whether or not a recoverable application program was in effect, and if it was, then whether the application or the terminal was designated to sending.

This message is logged in order to help diagnosing problems during recovery of persistent VTAM sessions.

During recovery of persistent VTAM sessions, VTAM requested that the session with LU $1 be restored. However, for one reason or another, the connection could not be reestablished.

When recovering persistent VTAM sessions, some sessions may have been terminated since the time of the shutdown or failure. After processing all recovery requests from VTAM, Com-plete deletes from the XCF structure the recovery data of those sessions for which recovery has not been requested.

This is just an informational message.

When the evacuation of VTAM sessions is initiated, for each session to be evacuated this message indicates terminal ID, user ID, current program, and action taken (started / flagged).

After evacuation of VTAM sessions has been initiated, this message summarizes how many sessions will be subject to evacuation.

Evacuation of VTAM sessions is only possible among Com-plete instances that are members of a common Generic Resource name.

LU=$ TID=$ $

Logon failed for reason indicated by text ($3).

Processing continues. The LU is not connected.

Make the LU available for release or code ACQ=NO on the TIB macro.

Make the LU available and attempt a restart or ignore the message.

LU=$ TID=$ TIB IS DELETED AND CANNOT BE LOGGED ON TO

A LU has attempted a logon to Com-plete . This message shows the TID of the TIB that this LU should be connected to (name= parameter of the TIB macro). The logon failed because the TIB specified to log on to is deleted. Connection can be established when the TIB is not deleted.

Processing continues. The LU is not connected.

Do not code DEL=YES on the TIB; coding DEL=YES will prevent logging on.

Make the TIB available by issuing RESTART TID to un-delete it.

LU=$ TID=$ OPNDST(ACCEPT) FAILED TO CONNECT (NIBFLG1 NIBCON OFF)

This message is associated with Com-plete VTAM support. Here, $1 is the LU that has attempted a logon to Com-plete . In this case, $2 is the TID that the LU is assigned to. Connection was not established by VTAM.

Processing continues. The LU is not connected.

Determine the error detected by VTAM.

Make the LU available and attempt a restart or ignore the message.

• $1 is the LU that attempted a logon to Com-plete ,

• $2 the TID assigned to the LU;

• $3 is either Com-plete or VTAM, indicating which support is unavailable;

• $4 is the Tib device type (TIBDTYPE) if $3 is Com-plete ,

• or

• $4 is the VTAM device type (DEVTCODE from ISTDVCHR) if $3 is VTAM.

The logon has failed because:

1. VTAM device type $4 is not supported by Com-plete .

2. Com-plete device type $4 support is not linked into Com-plete .

Processing continues. The LU is not connected.

Include the correct modules in the Com-plete link edit to correct item b. from above.

Contact your system programmer.

LU=$ LOSTERM CODE=$ This message is associated with Com-plete VTAM support. Here, $1 is the LU for which the LOSTERM exit was entered. $2 is the LOSTERM code documented by VTAM. CODE=036 usually indocates that more VTAM buffers need to be assigned either to Com-plete or to the LU.

Processing continues.

If CODE=036 entries are common, the VTAM buffers may need increasing.

Informational message. Contact your system programmer.

LOGON LU=$. NO TIB AVAILABLE

A LOGON request was received and there were no free TIBTAB entries.

The LOGON is rejected.

Increase the size of the TIBTAB.

Contact your system programmer.

LOSTERM LU=$ TID=$ CODE=$

This message is associated with Com-plete VTAM support. Here, $1 is the LU for which the LOSTERM exit was entered. $2 is the LOSTERM code documented by VTAM. CODE=036 usually indicates that more VTAM buffers need to be assigned either to Com-plete or to the LU.

Processing continues.

If CODE=036 entries are common, the VTAM buffers may need increasing.

Informational message. Contact your system programmer.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

Self-explanatory message.

This message is associated with Com-plete VTAM support. LU= is where the LU name may be unknown. TID= is where the TID may be unknown. $3 is the Com-plete to VTAM request. This message is printed with an additional explanation for codes VTM3011 through VTM3021, all of which concern VTAM. The VTAM codes are described in the appropriate VTAM reference manual. This message can be accompanied by VTM3002.

Processing continues.

Correct the problem indicated by the message. (Note that some messages are merely informational.)

Perform the action specified by the accompanying message or notify the system programmer.

VTAM SENSE DATA - SSENSEI(1),SSENSMI(1),USENSEI(2)- $$$

This message is associated with Com-plete VTAM support.

Here, $1 is the input system sense (SSENSEI), $2 is the input system modifier (SSENSMI), and $3 is the user system sense (USENSEI) or the BTU response codes $1$2 for IBM 3270.

This is a sense and status message code.

This message is printed whenever VTM3001 is printed and the sense field of the RPL (RPLFDBK2 for 4 bytes) is not zero. This message contains additional RPL information that may be required for further debugging. The VTAM codes are described in the appropriate VTAM reference manual.

Processing continues.

Correct the problem indicated by the message. (Note that some messages are merely informational.)

Perform the action specified by the accompanying message or notify the system programmer.

VTAM SHOULD NOT OCCUR - ABEND S0C3 This message is associated with Com-plete VTAM support. This message is printed whenever a SHOULD NOT OCCUR condition occurs.

Processing ends. Com-plete abends with a S0C3; a dump should be taken.

Contact your technical representative.

Notify the system programmer.

ACTION CODE REQUESTS ABEND S0C6

This message is associated with Com-plete VTAM support and is printed whenever the SYNAD or LERAD routines are entered and the action code that Com-plete determines from the given RTNCD and FDBK2 indicates that the abend will occur. The table is in module TLAMVTER. VTM3001 and VTM3002 will have been printed if they apply. This message will occur only if special diagnostic zaps have been applied to Com-plete .

Processing ends. Com-plete abends with an S0C6.

Contact your technical representative.

Perform the action specified by the accompanying message or notify the system programmer.

SIMLOGON FAILED - DEVICE NOT AVAILABLE

This message is associated with Com-plete VTAM support.

The SIMLOGON macro that Com-plete issued at Com-plete /VTAM initialisation or at restart has failed because VTAM determined that the device is not available. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=16 and FDBK2=00. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not acquired or restarted.

Make the LU available for release or code ACQ=NO on the TIB macro.

Make the LU available and attempt a restart, or ignore the message.

OPNDST FAILED - PROBABLE BIND ERROR

This message is associated with Com-plete VTAM support.

The OPNDST macro, issued by Com-plete in the LOGON exit, failed.

This may indicate a bind error.

This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=16 and FDBK2=01. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not accepted.

Determine the error reported by VTAM.

Contact the system programmer.

VTAM/NCP INCOMPATIBILITY

This message is associated with Com-plete VTAM support.

A VTAM macro, issued by Com-plete , has indicated a VTAM/NCP incompatibility. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=16 and FDBK2=01. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. If an I/O was in progress, it is given an indication of a permanent I/O error.

Correct the VTAM/NCP compatibility error.

Contact the system programmer.

VTAM ERROR. LOGICAL UNIT LOST

VTAM has reported a VTAM error. The LU is lost. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=16 and FDBK2=10. This message is accompanied by ZVT03001 (showing the RTNCD and FDBK2 values) and ZVT03002, if required.

Processing continues. The LU is lost to Com-plete .

Determine the reason for the VTAM error.

An IGNORE LU and RESTART LU may reaquire the LU, depending on the error.

VTAM BUFFERS FULL. INCREASE BUFFACT.

VTAM has reported that its buffers are full. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=16 and FDBK2=15. This message is accompanied by ZVT03001 (showing the RTNCD and FDBK2 values) and by ZVT03002, if required.

Processing continues. A temporary I/O error is reported to the application program using this LU.

VTAM may need more buffers for this LU. Increase VTAM's BUFFACT.

Contact the system programmer.

NEGATIVE RESPONSE ON START DATA TRAFFIC

This message is associated with Com-plete VTAM support. The OPNDST macro that Com-plete issued in the LOGON exit failed because the LU returned a negative response to START DATA TRAFFIC (SDT). This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=16 and FDBK2=17. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not accepted.

Determine why the LU is not accepting SDT.

Make the LU available and attempt a restart or ignore the message.

INVALID LOGMODE NAME (VTAMLOGMODE PARM)

This message is associated with Com-plete VTAM support. The terminal operator or program that initiated the LOGON has passed Com-plete an invalid LOGON sequence, or the VTAMLOGMODE PARM contains a name that is not found in the LOGMODE table. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=20 and FDBK2=x'4B'. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Com-plete -VTAM initialisation continues. The LU is not accepted, acquired, or restarted.

Determine the reason for the VTAM return code. It is possible that the VTAM-Com-plete user exit placed an invalid LOGMODE name in the NIB or that the VTAMLOGMODE PARM is incorrect.

An IGNORE and RESTART may be attempted for the LU.

TIBNAME NOT FOUND OR NOT ACTIVE

This message is associated with Com-plete VTAM support. The SIMLOGON macro, issued by Com-plete at Com-plete /VTAM initialisation or restart has failed because VTAM cannot find an active LU with the given name. The TIB name Com-plete attempted to acquire is not active or defined. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=20 and FDBK2=x'53'. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not acquired or restarted.

Make the LU available or correct the TIB name or VTAM LU definition. The TIB name may also have been changed in the user exit.

Make the LU available and attempt a restart or ignore the message.

TIBNAME NOT VALID FOR CONNECTION

The SIMLOGON macro, issued by Com-plete at Com-plete /VTAM initialisation or restart has failed because VTAM has determined that the LU name is invalid for connection. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=20 and FDBK2=x'54'. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not acquired or restarted.

Correct the TIB name or VTAM LU definition. The TIB name may also have been changed in the user exit.

Contact your system programmer.

SIMLOGON/OPNDST NOT AUTHORIZED (APPL STMT)

This message is associated with Com-plete VTAM support. The SIMLOGON or OPNDST macro that Com-plete issued at Com-plete /VTAM initialisation or at restart has failed because the APPL statement does not allow SIMLOGON or OPNDST macros. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=20 and FDBK2=x'55'. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not acquired or restarted.

Code AUTH=ACQ on Com-plete's APPL statement.

Contact your system programmer.

DEVICE/LU OFFLINE. NOT ACQUIRED.

This message is associated with Com-plete VTAM support.

The SIMLOGON macro that Com-plete issued at Com-plete /VTAM initialisation or at restart has failed because VTAM has determined that the device is offline or is in the process of being varied offline. This message is printed whenever the SYNAD or LERAD routines are entered with RTNCD=12 and FDBK2=09. This message is accompanied by VTM3001 (showing the RTNCD and FDBK2 values) and VTM3002, if required.

Processing continues. The LU is not acquired or restarted.

Vary the LU online or code ACQ=NO on the TIB macro.

Vary the LU online and attempt a restart or ignore the message.

LUSTAT LU=$ TID=$ SENSE=$

A LUSTAT response has been received from the indicated logical unit.

Processing continues.

RPLEXIT LU=$ TID=$ REQ=$ RC=00 FDBK2=$

A non-fatal error occurred during processing in an RPL exit. REQ indicates either 'CLSDST' or 'SIMLOGON'.

Processing continues.

LU=$ TID=$ EXCESSIVE INPUT - INPUT DROPPED

This message is associated with Com-plete VTAM support.

$1 is the logical unit name, $2 is the terminal Id. Com-plete received record mode input longer than 4080 bytes from an LU.

Processing continues. The input from the LU is dropped.

Ensure that the LU sends less than 4080 bytes of input.

LU=$ TID=$ NOT ACQUIRED -- IN USE (SIMLOGON RTNCD=00 FDBK2=008)

The SIMLOGON issued by Com-plete at RESTART LU has failed because VTAM has determined that the LU is already in use by another application. This message is printed when the SIMLOGON macro completes with RTNCD=00 and FDBK2=08.

Processing continues. The LU is not restarted.

Make the LU available for release.

Make the LU available and attempt a restart or ignore the message.

LU=$ TID=$ NOT ACQUIRED -- IN USE (SIMLOGON RTNCD=00 FDBK2=008)

This message is associated with Com-plete VTAM support. An EOT was not received on the first input from a basic mode device. This means that the buffer used for basic mode READs is too small.

Processing continues. The input from the LU is dropped.

Increase the VTAMRBUFFER PARM (basic mode READ buffer size).