KLVVT021 text: appl, <lu><dest>,<cid>,<logmode>, seqno,req, <mod>cntrl, fdbk<,fdbk2><,osens>

Edit online

Explanation

VTAM® and TMS:Engine information have been formatted because a VTAM error has occurred or because TMS:Engine has been directed to trace certain VTAM actions. The data that may be shown follows (RPL field names are in brackets):
  • text: Short description of the error.
    PI TRACE
    TMS:Engine has been directed to trace the flow of control for this ACB.
    EXIT TRACE
    TMS:Engine has been directed to trace the flow of control for this ACB.
    DFASY EXIT
    TMS:Engine has been directed to trace the flow of control for this ACB.
    REQUEST RETRY
    The request was rejected because of a storage shortage. TMS:Engine will wait one second and then retry the request.
    INBOUND -RSP-
    A negative response was received and DEBUG(Y) has been requested.
    INBOUND +RSP
    A positive response was received and TMS:Engine has been directed to trace the flow of control for this ACB.
    CHAIN RETRY
    An exceptional condition was detected for this request and is being retried.
    CHAIN RETRY FAILED
    An attempt to retry a request that failed for an exceptional reason was not successful. The session is terminated. Refer to the data fields in the message to determine the problem.
    OUTBOUND -RSP-
    A negative response is being reflected to the requester. Refer to the data fields in the message for more information.
    LOGICAL ERROR
    A VTAM logical error was detected. Refer to the data fields in the message for more information.
    VTAM NSXIT, UNKNOWN RU
    The TMS:Engine Network Services Exit was scheduled, but the request unit (RU) received was not a Cleanup, Notify, or Network Services RU. Contact your site z/OS® Communications Server systems programmer.
    INVALID CORRELATOR
    A solicited BIND has been received, but the user-provided correlator returned by VTAM is not valid. The BIND is rejected. Contact your z/OS Communications Server systems programmer.
    PHYSICAL ERROR
    A z/OS Communications Server physical error was detected. If the error was a z/OS Communications Server storage shortage the request is retried until it succeeds or fails for a different reason. Refer to the data fields in the message to determine the problem.
  • appl: Application ID.
  • lu: Logical unit name.
  • dest: Destination (for CLSDST PASS).
  • cid: Communication identifier.
  • logmode: Associated logmode.
  • seqno: RPL sequence number. [RPLSEQNO].
  • req: Request code. If it is one of a standard set, it is shown in English; otherwise it is formatted in hexadecimal. [RPLREQ].
  • nie: Control modifier: [RPLSRTYP] and [RPLRH3].
    • R Response
    • BB Begin bracket
    • EB End bracket
    • CEB Conditional end bracket
    • CD Change direction
  • cntrl Control information. If it is one of a standard set, it is shown in English; otherwise it is formatted in hex. [RPLCNTRL].
  • fdbk: Request feedback. If it is one of a standard set, it is shown in English; otherwise it is formatted in hex. [RPLFDBK].
  • fdbk2: More feedback information, displayed in hex. [PRLFDBK2].
  • osens: Sense code information, displayed in hex. [RPLOSENS].

If a data item cannot be located, it is omitted from the message. If DEBUG(Y) was specified in the TMS:Engine KLVSYSIN file, the contents of any request units, the RPL, and an TMS:Engine control block will be displayed, if they are relevant.

System action

The system action depends on the reason for the dump.

User response

Refer to IBM® z/OS Communications Server SNA Programming to obtain information about the FDBK, FDBK2, and OSENS fields. If the dump seems to be associated with a persistent problem, contact IBM Software Support.

Note: Many of these dumps are the result of normal conditions, such as powering a terminal off.

Message Type

LOG. If DEBUG(Y) is specified, LOG, VIEW.