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


$HASP679

z/OS JES2 Messages
SA32-0989-01

$HASP679

Explanation

Read syntax diagramSkip visual syntax diagram
>>-$SN,A=--applid--REJECTED – --reason-------------------------><

The operator attempted to initiate an SNA application-to-application session using the $SN command.

In the message text:
applid
The VTAM® application identifier.

reason is one of the following:

JES2/VTAM INTERFACE INACTIVE, RC=01
The JES2/VTAM interface has not been activated. The LOGON1 DCT has either not been defined or not been started using the $S LOGON1 command.
LINElna IS NOT A SNA/VTAM LINE, RC=02
The line specified on the $SN command is a BSC line, not an SNA line.
LINElna IS NOT ACTIVE, RC=03
The line specified on the $SN command has not been started. The line must be started before you reissue the $SN command.
LINElna IS BUSY, RC=04
The line specified on the $SN command is already busy for another SNA node or remote.
NO IDLE SNA LINE IS AVAILABLE, RC=05
No line was specified on the $SN command and JES2 could not find a started SNA line that was not currently busy for another SNA node or remote.
applid IS NOT A DEFINED APPL OR NODE, RC=06
The application name specified on the $SN command is neither a defined application (APPL) nor the name of an existing node. The name is incorrect, the application should be defined using the $T APPL(applname) command, or a node should be renamed to that application name.
NODEnnnn IS THE LOCAL NODE, RC=07
The application name specified on the $SN command either implied a local node or, if no such application exists, was the name of a local node. Networking cannot be initiated from the local node to itself.
ALREADY IN SESSION WITH applid, RC=08
The application name specified on the $SN command either implied, or was the name of, a node already in session with the local node for networking.
MAXIMUM SESSIONS ALREADY ACTIVE, RC=09
Because the maximum number of SNA applications are already active, no additional applications can be started at this time. Use the SESSION parameter on the TPDEF initialization statement to specify the maximum number of applications allowed.
NO STORAGE AVAILABLE FOR APPL, RC=10
An application (APPL) was to be dynamically defined but no storage was available for the necessary control blocks.
THE NODE FOR APPL applid IS INVALID, RC=11
An existing application (APPL) was found for the $SN command but it references an incorrect node number.
DEDICATED LINE LINEnnnn IS NOT AVAILABLE, RC=12
The line specified on the $SN command or defined in the NODE(nnnn) initialization statement is not usable. Possible reasons are:
  1. Dedicated line number lna is also dedicated to an RJE device (RMT5,LINE=5).
  2. Dedicated line number lna is in disconnect process (draining).
  3. Dedicated line number lna has a "password" set on it.
  4. User has multiple SNA paths to NODE5 and has set the node for the dedicated line instead of setting the associated APPL statement for a dedicated line.
NETWORK PATH MANAGER IS NOT AVAILABLE, RC=13
JES2 could not start the connection because the network path manager PCE failed. JES2 also issued message $HASP502 to indicate this condition.

System action

Processing continues.

Operator response

Take appropriate action to correct the condition and then repeat the $SN command.

System programmer response

For RC=02, reason 1 or 2, this line cannot be used for SNA/NJE line dedication. Another line must be used. For RC=02, reason 3, turn off the password to this line or use another line. For RC=02, reason 4, dedicate the line on the APPL definition instead of the NODE definition.

Module

HASPCOMM

Routing Code: #

Descriptor Code:

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014