At Spool startup the following error message is issued when attempting to connect to a JES2 node:
ESF401 UNABLE TO ESTABLISH SESSION nnnnnnnn
The cause is a VTAM error
IST663I INIT OTHER REQUEST FAILED , SENSE=0805000B
IST664I REAL OLU=nnnnn.nnnnn REAL DLU=bbbbbb.bbbbbbb
IST889I SID = XXXXXXXXXXXX
IST314I END
The sense code 0805 means:
Session limit exceeded: The requested session cannot be activated, as one of the NAUs is at its session limit, for example, the LU-LU session limit or the (LU, mode) session limit. This sense code applies to ACTCDRM, INIT, BIND, and CINIT requests.
The sense code specific information '000B' means:
The request was rejected because a session already exists between the same LU pair, and at least one of the LUs does not support parallel sessions.
The cause was a timing problem caused by the sequence of commands issued by an automation tool. When Spoolis started, it automatically attempts to connect to the NJE nodes. At the same time the automation is issuing the commands below:
00:02:42.94 nnnnnnnn 00000280 $SN,A=nje1
00:02:43.07 bbbbbbbb 00000280 F ESF,P,nje2
See that a JES command (SN) is being issued to connect the nodes. Some seconds later a command is issued on the ESF side to stop the connection. This sequence causes, in some timely dependent circumstances, a partial connection with the JES2 LU and then the VTAM error.