NJE Interface Messages

Messages › NJE Interface Messages

NJE Interface Messages

ESF350

xxxxxxxx

Reason:

CA Spool has received a message xxxxxxxx from an NJE session. Processing continues.

Action:

None.

ESF351

xxxxxxxx IS NOW SIGNED-ON TO yyyyyyyy, BUFFER SIZE=ssss

Reason:

NJE node yyyyyyyy has received an NJE sign-on record from xxxxxxxx and accepted it. The ssss is the buffer size which will be used in this session. Processing continues.

Action:

None.

ESF352

xxxxxxxx IS NOW SIGNED-OFF FROM yyyyyyyy

Reason:

NJE node yyyyyyyy has received an NJE sign-off record from xxxxxxxx and accepted it. Processing continues.

Action:

None.

ESF353

SESSION IS NOW STARTED WITH yyyyyyyy

Reason:

CA Spool has accepted NJE session with yyyyyyyy. Processing continues.

Action:

None.

ESF354

SESSION IS NOW ENDED WITH yyyyyyyy

Reason:

CA Spool has completed NJE session with yyyyyyyy. Processing continues.

Action:

None.

ESF355

xxxxxxxx NJE SESSION HALTED

Reason:

CA Spool has halted all paths to xxxxxxxx after command Z,xxxxxxxx. Processing continues.

Action:

None.

ESF356

xxxxxxxx NJE SESSION DRAINED

Reason:

CA Spool has drained all paths to xxxxxxxx, after receiving unbind from VTAM, or command P,xxxxxxxx, PNET, TNET have been used. Processing continues.

Action:

None.

ESF357

MISSING RESPONSE FROM xxxxxxxx

Reason:

ESFNJE has sent an RPL to xxxxxxxx with definitive response, but next inbound RPL was not a response. Session will be drained.

Action:

Contact your systems programmer.

ESF358

ERROR IN RESPONSE FROM xxxxxxxx

Reason:

ESFNJE has received a response from xxxxxxxx which was not ok. Session will be drained.

Action:

Contact your systems programmer.

ESF359

INVALID FMH RECORD RECEIVED FROM xxxxxxxx

Reason:

ESFNJE has received an invalid function management header. Session will be drained.

Action:

Contact your systems programmer.

ESF360

ERROR DURING GETMAIN OF PCB TO xxxxxxxx

Reason:

Non-zero return code during GETMAIN of process control blocks for xxxxxxxx. Session will be drained.

Action:

Contact your systems programmer.

ESF361

ERROR DURING GETMAIN OF SNA BUFFER FOR xxxxxxxx

Reason:

Non-zero return code during GETMAIN of SNA buffer for xxxxxxxx. Session will be drained.

Action:

Contact your systems programmer.

ESF362

COMPACTION FOUND IN RECORD FROM xxxxxxxx, NOT SUPPORTED

Reason:

During decompressing, non-supported compaction character found. Session will be drained.

Action:

Contact your systems programmer.

ESF363

INVALID SYSOUT OR JOB CONTROL RECORD RECEIVED FROM xxxxxxxx

Reason:

ESFNJE has received a record from xxxxxxxx which contains an invalid RCB. Session will be drained.

Action:

Contact your systems programmer.

ESF364

aaaaaaaa (bbbbbb) FROM (cccccccc/dddddddd) 9.999.999 RECORDS ON eee

Reason:

ESFNJE has permitted file aaaaaaaa original job number bbbbbb from node cccccccc user ID dddddddd on SYSOUT/job receiver eee to allocate a spool file containing approximate 9.999.999 records. eee is logical receiver number which is used in this transmission. Processing continues.

Action:

None.

ESF365

ERROR DURING ESF aaaaaa RC bb ccc FOR NODE (dddddddd/eeeeeeee) CANCEL WILL BE SENT

Reason:

ESFNJE has received return code bb during aaaaa, where aaaaa is open, close, read, write and ccc is depending on aaaaa.

dddddddd is the node in which the file is currently received from or sent to.
eeeeeeee is the user ID attached to the file. Cancel command will be sent to dddddddd.

Action:

Review the error and take corrective action as required, depending upon aaaaa and RC bb ccc.

ESF365

ERROR DURING ESF OPEN, EMAIL ERROR FOR NODE (dddddddd/eeeeeee) CANCEL WILL BE SENT

Reason:

Files received with too many OUTPUT statement email parameters such as MAILTO, MAILCC, MAILBCC, MAILFROM, MAILFILE and REPLYTO; did not fit into the 16*60=960 characters USERDATA parameters.

dddddddd is the node which the file is currently being received from.
eeeeeeee is the user ID attached to the file. A cancel command will be sent to dddddddd.

Action:

None.

ESF366

aaaaaaaa FILE bbbbbb TO (cccccccc/dddddddd) 9.999.999 RECORDS ON eee

Reason:

ESFNJE has sent a request to destination cccccccc for permission to allocate spool file aaaaaaaa file number bbbbbb for node dddddddd with approximately 9.999.999 records on eee. eee is the logical transmission number which is used in this transmission. Processing continues.

Action:

None.

ESF367

ALLOCATE DENIED FOR FILE zzzzzz DESTINATION xxxxxxxx NODE yyyyyyyy

Reason:

ESFNJE has received allocation denied as an answer to the request for permission to allocate on destination xxxxxxxx node yyyyyyyy. Processing continues.

Action:

None.

ESF368

FILE aaaaaa HELD

Reason:

Action after message ESF367, file aaaaaaaa is closed and flagged as held. Processing continues.

Action:

None.

ESF369

PCB WILL BE DRAINED

Reason:

Action after message ESF368, PCB, receiver will be flagged as drained. Processing continues.

Action:

Contact your systems programmer.

ESF370

aaaaaaaa FILE bbbbbb (cccccccc/dddddddd) TO eeeeeeee TRANSFERRED

Reason:

ESFNJE has successfully completed transfer file aaaaaaaa file number bbbbbb to destination eeeeeeee on node cccccccc for user dddddddd. Processing continues.

Action:

None.

ESF371

aaaaaaaa FILE bbbbbb (cccccc) (dddddddd/eeeeeeee) TO ffffffff RECEIVED–ORIGINAL DEST gggggggg

Reason:

ESFNJE has successfully received file aaaaaaaa with file number bbbbbb, which has original file number cccccc from node dddddddd user ID eeeeeeee to destination ffffffff. If NJEOPT=2 and DESTVAL=YES have been specified and a file is received for an unknown destination, the file will be created for destination $$NODEST and the orginal destination will be given in gggggggg.

Action:

None.

ESF372

FILE zzzzzz REQUEUED TO DESTINATION xxxxxxxx NODE yyyyyyyy

Reason:

Action after TNET command or VTAM error for file zzzzzz, depending on who has responsibility for the file, message ESF373 can be issued. Processing continues.

Action:

None.

ESF373

FILE aaaaa TO DESTINATION bbbbbbbb CANCELLED BY NODE cccccccc

Reason:

ESFNJE has received a cancel command from node cccccccc, on file aaaaa to destination bbbbbbbb. The file aaaaa will be closed and scheduled for purge processing.

Action:

None.

ESF374

NJE xxxxxxxx - INVALID NJE FOUND

Reason:

When trying to dynamically add NJE xxxxxxxx, CA Spool found that the existing NJE node was not an NJE node. Processing continues.

Action:

Contact your systems programmer.

ESF375

NJE xxxxxxxx - ALREADY DEFINED

Reason:

The NJE xxxxxxxx could not be defined because the name already existed. Processing continues.

Action:

Use unique names when defining users and nodes.

ESF376

NJE xxxxxxxx - NO MORE NODES CAN BE DEFINED

Reason:

The NJE xxxxxxxx could not be defined because the total number of NJEs added to the parameter deck exceeded the DYNNJE parameters. Processing continues.

Action:

Decrease the number of NJEs in the parameter deck, then re-issue the REINIT command, or shutdown, then restart CA Spool.

ESF377

EMAIL ERROR - NOT ENOUGH USERDATA SPACE FOR ALL EMAIL PARMS

Reason:

Files received with too many OUTPUT statement email parameters such as MAILTO, MAILCC, MAILBCC, MAILFROM, MAILFILE and REPLYTO; does not fit into the 16*60=960 characters USERDATA parameters.

Action:

None.

ESF378

NJE xxxxxxxx - NOT REDEFINED, BECAUSE IT WAS ACTIVE

Reason:

The NJE xxxxxxxx could not be redefined because it was in session with CA Spool when the REINIT command was issued. Processing continues.

Action:

Re-issue the REINIT command when the node is drained if the node definition was changed.

ESF379

NJE xxxxxxxx - DUPLICATE APPLID NAME

Reason:

The specified VTAM application name for NJE xxxxxxxx was already assigned to another node. Processing continues.

Action:

If the VTAM application name was moved from one node to another node, re-issue the REINIT command.

ESF380

This message number represents one of the following messages:

NJE nnnnnnnn APPL aaaaaaaa BFSZ=ssss(qqqq),
STATUS=xxxxxxxxxx SYSTEM=vvvvvvvvvv
ttt yyyyyyyyy oooooooo (ffffff) dddddddd REC(rrrrrr,zzzzzz)
MSG yyyyyyyyy QCMD(qqqq) QRSP(pppp) MAX CMD(mm)
CUR CMD(cc)

Reason:

This message is displayed in response to a display command for an NJE node.

nnnnnnnn is the NJE node name.
aaaaaaaa is the NJE node application name.
ssss is the maximum buffer size which the NJE connection will accept.
qqqq is the buffer size currently used, if any session is active.
xxxxxxxx is the status codes for this session if any session is active.
Valid status codes are:
ACTIVE—The session is established and active.
INACTIVE—No session is active.
STARTING—The operator has issued an S command but the session has not yet been established.
QUEUED—A session request has been received.
DRAINING—The operator has issued a P command and the session has not yet ended.
DRAINED—The drain command has completed.
HALTING—The operator has issued a Z command to prevent any more activities.
HALTED—The halt command has completed.
CANCEL—The operator has issued a C command to cancel all current activities. Transmissions are interrupted and the input file is put on hold. Receivals will complete, but the data received will not be stored in CA Spool.
FAST CLOSE—A session error has been detected and termination processing has been started as if a cancel command had been issued.
QUIESCING—The session has received a notify and has started termination processing.
vvvvvvvvvv is the name of the assumed session partner, based on the interpretation of received messages and control blocks. Valid names are:
CA SPOOL—CA Spool
ASP—ASP subsystem
HASP—HASP subsystem
JES/RES—JES/RES subsystem
JES2—JES2 subsystem
JES3—JES3 subsystem
VSE/POWER—VSE/POWER subsystem
VM/RSCS—VM/RSCS subsystem
HOME NODE—Desired home node
NA—Information not available
ttt is the logical device name. Valid names are:
ST?—ST means SYSOUT transmitter, ? is a number range from 1 to 7.
ST?—SR means SYSOUT receiver, ? is a number range from 1 to 7.
JT?—JT means job transmitter, ? is a number range from 1 to 7.
JT?—JR means job receiver, ? is a number range from 1 to 7.
MSG—MSG means message transmitter and receiver.
yyyyyyyyyy is the status code of the logical device. Valid status codes are:
ACTIVE—The logical device is active.
INACTIVE—No activity on this logical device.
STARTING—For a receiving device a session start request has been received. For a transmitting device a start request has been sent.
DRAINING—The operator has issued a P command against the logical device, but the command has not yet completed.
DRAINED—The drain command has completed on the logical device.
HALTING—The operator has issued a Z command against the logical device, but the command has not yet completed.
HALTED—The halt command has completed on the logical device.
CANCELING—The operator has issued a C command to cancel the current activities. Transmissions are interrupted and the input file is put in hold status. Data being received will complete, but the data received will not be stored in CA Spool. The command has not yet completed.
FAST CLOSE—A session error has been detected and termination processing has started as if a cancel command was issued.
oooooooo is the file name of the currently transmitting or receiving file.
ffffff is the file sequence number of the currently transmitting or receiving file.
dddddddd is the node name (writer name) of currently transmitting or receiving file.
rrrrrr is the number of records to be transmitted or received.
zzzzzz is the number of records currently transmitted or received.
qqqq is the number of queued commands not yet executed.
pppp is the number of queued responses not yet transmitted to the requestor.
mm is the maximum number of commands concurrently executed.
cc is the current number of commands executing.

ESF381

FILE zzzzzz TO DESTINATION xxxxxxxx NODE yyyyyyyy CANCELLED

Reason:

Operator has issued a cancel command against file zzzzzz to destination xxxxxxxx node yyyyyyyy. Cancel request will be sent to destination xxxxxxxx and file zzzzzz will be flagged as transmitted. Processing continues.

Action:

None.

ESF382

FILE zzzzzz FROM DESTINATION xxxxxxxx NODE yyyyyyyy SKIPPED TO EOJ

Reason:

Operator has issued a cancel command against file zzzzzz receiving from destination xxxxxxxx to node yyyyyyyy.

Cancel request will be sent to destination xxxxxxxx when file zzzzzz EOJ has been received, file zzzzzz will be purged. Processing continues.

Action:

None.

ESF383

INVALID PASSWORD RECEIVE FROM aaaaaaaa SESSION WILL BE TERMINATED

Reason:

ESFNJE has received a sign on record which contains a node password which does match the specified password from the parameter deck. The session will be drained.

Action:

Contact your systems programmer.

ESF384

INVALID NODE NAME RECEIVED FROM aaaaaaaa SESSION WILL BE TERMINATED

Reason:

ESFNJE has received a sign on record containing a node name which does not match the specified node name from the parameter deck. The session is drained.

Action:

Contact your systems programmer.

ESF385

SESSION IS NOW RESUMED WITH yyyyyyyy

Reason:

The halted session with NJE node yyyyyyyy has been resumed.

Action:

None.