z/OS JES2 Messages
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


$HASP208

z/OS JES2 Messages
SA32-0989-01

$HASP208

Explanation

Read syntax diagramSkip visual syntax diagram
>>-event--SCHEDULED FOR--luname--RC=--xx------------------------>

>--NSEXIT SCHEDULED FOR--luname--CLEANUP,--xx------------------->

>--NSEXIT SCHEDULED FOR -luname--NOTIFY,--tt,--rr,--ssssssss---><

A system network architecture (SNA) event event occurred requiring that the specified session be ended. Not all SNA events have an associated reason code. Additional diagnostic information is provided for an NSEXIT. If the SNA event has a reason code, the reason code is defined by xx. See z/OS Communications Server: SNA Programming for an explanation of the hexadecimal reason codes. Possible values of the SNA event and the explanation of each are:
Event
Explanation
TPEND
VTAM® TPEND exit (terminal pending)

Reason code provided: Yes

LSTRM
VTAM LOSTERM exit (lost terminal services)

Reason code provided: Yes

UNBND
VTAM SCIP exit (unbind)

Reason code provided: No

RQRVY
VTAM SCIP exit (request recovery)

Reason code provided: No

NSXIT
VTAM NSXIT exit (network services)

Reason code provided: See below

There are 2 types of NSEXITs scheduled by VTAM: CLEANUP and NOTIFY.

For CLEANUP requests, in the message text:
xx
The reason code indicating how the session was taken down.
For NOTIFY requests, in the message text:
tt
The status byte.
rr
The associated reason code if the status byte is a procedure error (03).
ssssssss
The associated sense data if the status byte is a procedure error (03).

System action

JES2 ends the affected sessions. Message $HASP210 provides additional information.

Operator response

None.

System programmer response

If the termination is unexpected, examine any VTAM messages related to the session that terminated.

Module

HASPSNA

Routing Code: 8,10

Descriptor Code: 4

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014