Prev | Table of Contents | Next

3. PJS Abend Codes

0102 Explanation: The ENQ for the PJS System Task resource failed. The PJS System Task was probably started when it was already running in another address space.

Action: If message PJS121 is issued, respond as specified for that message. If message PJS121 is not issued, this is probably an internal error. If the abend recurs, make sure another PJS System Task is not already running. Then obtain a dump of the address space before reporting the problem.

0104 Explanation: The PJS System Task operator communication subtask abended. This abend is issued by the main task.

Action: This abend is preceded by message PJS122. Check the subtask abend code and any other messages for the operator communications subtask, and respond as specified for those codes and messages.

0111 Explanation: PJSTASKB was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0112 Explanation: The PJS System Task Event Post/Reset table has overflowed.

Action: Increase the PTBLSZ parameter of the PJSOPT macro, reassemble the PJS Options Table, and restart the PJS System Task.

0113 Explanation: The PJS System Task Ready Request table has overflowed.

Action: Increase the RRTBLSZ parameter of the PJSOPT macro, reassemble the PJS Options Table, and restart the PJS System Task.

0114 Explanation: A PJS Request Queue I/O function by the PJS System Task failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0131 Explanation: PJSTASKJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0132 Explanation: A PJS Request Queue I/O function by the PJS System Task failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0133 Explanation: The PJS Job Submit Subtask (PJSSUB) abended, and optional APAR OPJ0033 has been applied.

Action: Determine the reason for the PJS Job Submit Subtask abend. Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0171 Explanation: PJSOPER was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0172 Explanation: A QEDIT function by the PJS System Task operator communication subtask failed.

Action: This abend is preceded by message PJS123. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0181 Explanation: PJSSUB was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0183 Explanation: An OPEN macro for the internal reader failed. This abend is issued by the PJS System Task job submit subtask. The PJS Main Task should continue.

Action: This abend is preceded by message PJS152. Respond as specified for that message.

0184 Explanation: A CLOSE macro for the internal reader failed. This abend is issued by the PJS System Task job submit subtask. The PJS Main Task should continue.

Action: This abend is preceded by message PJS153. Respond as specified for that message.

0185 Explanation: The PJS Installation Submit Exit set an invalid return code.

Action: Check the PJS Installation Submit Exit (PJSSUBX). Make sure that a valid return code is always set.

0201 Explanation: An OPEN macro for the PJS Request Queue failed. This abend is issued by the PJS Request Queue Initialization utility.

Action: This abend is preceded by message PJS711. Respond as specified for that message.

0202 Explanation: A PUT macro for the PJS Request Queue failed. This abend is issued by the PJS Request Queue Initialization utility.

Action: This abend is preceded by message PJS712. Respond as specified for that message.

0203 Explanation: A CLOSE macro for the PJS Request Queue failed. This abend is issued by the PJS Request Queue Initialization utility.

Action: This abend is preceded by message PJS713. Respond as specified for that message.

0241 Explanation: A PJS Request Queue I/O function by the PJS Request Queue Maintenance utility failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0242 Explanation: An OPEN macro for the PJS JCL Spool directory failed. This abend is issued by the PJS Request Queue Maintenance utility.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0243 Explanation: A STOW macro for the PJS JCL Spool directory failed. This abend is issued by the PJS Request Queue Maintenance utility.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0244 Explanation: The IEBCOPY utility was called to compress the PJS JCL Spool data set, and returned a non-zero return code. This abend is issued by the PJS Request Queue Maintenance utility.

Action: Check the IEBCOPY output for error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0245 Explanation: The PJS Request Queue Maintenance Utility Spool Directory table has overflowed.

Action: Increase the STBLSZ parameter of the PJSOPT macro, reassemble the PJS Options Table, and rerun the PJS Request Queue Maintenance utility.

0246 Explanation: The PJS Request Queue Maintenance Utility Owner table has overflowed.

Action: Increase the OTBLSZ parameter of the PJSOPT macro, reassemble the PJS Options Table, and rerun the PJS Request Queue Maintenance utility.

0247 Explanation: The PJS Request Queue Maintenance Utility Event table has overflowed.

Action: Increase the ETBLSZ parameter of the PJSOPT macro, reassemble the PJS Options Table, and rerun the PJS Request Queue Maintenance utility.

0261 Explanation: The PJS Event Post Utility was called with an invalid parameter list.

Action: Check that the PJSPOST program is invoked properly. Correct the problem, then rerun the utility.

0262 Explanation: A PJS Request Queue I/O function by the PJS Event Post utility failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0281 Explanation: The PJS Event Reset Utility was called with an invalid parameter list.

Action: Check that the PJSRESET program is invoked properly. Correct the problem, then rerun the utility.

0282 Explanation: A PJS Request Queue I/O function by the PJS Event Reset utility failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0401 Explanation: PJSMAIN was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0402 Explanation: An ESTAE macro failed.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0405 Explanation: One or more options specified by the PJSOPT macro (or modified by the PJSOPTX Installation Options Exit) is invalid.

Action: This abend is preceded by message PJS013. Respond as specified for that message.

0501 Explanation: The PJS Job Request List TSO command processor (PJSTJL) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0502 Explanation: A PJS Request Queue I/O function by the PJS Job Request List TSO command processor (PJSTJL) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0511 Explanation: The PJS Job Request Add TSO command processor (PJSTJA) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0512 Explanation: A PJS Request Queue I/O function by the PJS Job Request Add TSO command processor (PJSTJA) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0513 Explanation: The maximum PJS JCL Spool member number has been exceeded. This abend is issued by the PJS Job Request Add TSO command processor (PJSTJA).

Action: Call PJS Technical Support for assistance. Since the maximum PJS JCL Spool member number is currently 9999999, this is not expected to occur soon.

0521 Explanation: The PJS Job Request Modify TSO command processor (PJSTJM) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0522 Explanation: A PJS Request Queue I/O function by the PJS Job Request Modify TSO command processor (PJSTJM) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0523 Explanation: The maximum PJS JCL Spool member number has been exceeded. This abend is issued by the PJS Job Request Modify TSO command processor (PJSTJM).

Action: Call PJS Technical Support for assistance. Since the maximum PJS JCL Spool member number is currently 9999999, this is not expected to occur soon.

0531 Explanation: The PJS Job Request Delete TSO command processor (PJSTJD) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0532 Explanation: A PJS Request Queue I/O function by the PJS Job Request Delete TSO command processor (PJSTJD) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0601 Explanation: The PJS Calendar List TSO command processor (PJSTCL) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0602 Explanation: A PJS Request Queue I/O function by the PJS Calendar List TSO command processor (PJSTCL) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0611 Explanation: The PJS Calendar Add TSO command processor (PJSTCA) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0612 Explanation: A PJS Request Queue I/O function by the PJS Calendar Add TSO command processor (PJSTCA) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0613 Explanation: The PJS Calendar Record service routine returned an invalid return code. This abend is issued by the PJS Calendar Add TSO command processor (PJSTCA).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0621 Explanation: The PJS Calendar Modify TSO command processor (PJSTCM) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0622 Explanation: A PJS Request Queue I/O function by the PJS Calendar Modify TSO command processor (PJSTCM) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0623 Explanation: The PJS Calendar Record service routine returned an invalid return code. This abend is issued by the PJS Calendar Modify TSO command processor (PJSTCM).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

0631 Explanation: The PJS Calendar Delete TSO command processor (PJSTCD) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0632 Explanation: A PJS Request Queue I/O function by the PJS Calendar Delete TSO command processor (PJSTCD) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0701 Explanation: The PJS Event List TSO command processor (PJSTEL) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0702 Explanation: A PJS Request Queue I/O function by the PJS Event List TSO command processor (PJSTEL) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0711 Explanation: The PJS Event Post TSO command processor (PJSTEP) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0712 Explanation: A PJS Request Queue I/O function by the PJS Event Post TSO command processor (PJSTEP) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

0721 Explanation: The PJS Event Reset TSO command processor (PJSTER) was called with an invalid parameter list. This program must be called as a TSO command processor.

Action: Make sure the PJS TSO command processors are being invoked properly.

0722 Explanation: A PJS Request Queue I/O function by the PJS Event Reset TSO command processor (PJSTER) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

1001 Explanation: The PJS ISPF Interface (PJSISPF) was called, but ISPF was not active.

Action: Make sure ISPF is active before you try to use the PJS ISPF Interface.

1011 Explanation: PJSIMJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1021 Explanation: PJSIMC was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1031 Explanation: PJSIME was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1051 Explanation: PJSISXIN was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1061 Explanation: PJSISXDS was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1071 Explanation: PJSISXNA was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1081 Explanation: PJSISXNO was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1101 Explanation: PJSIDJL was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1102 Explanation: A TSO service facility request failed. The issuing program is PJSIDJL.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1103 Explanation: The ISPF PQUERY service failed. The issuing program is PJSIDJL.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1104 Explanation: Insufficient storage is available to build the List Job Requests Table. The issuing program is PJSIDJL.

Action: Increase the region size for the TSO session, and try again.

1111 Explanation: PJSIDJS was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1112 Explanation: A TSO service facility request failed. The issuing program is PJSIDJS.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1121 Explanation: PJSIDJA was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1122 Explanation: A TSO service facility request failed. The issuing program is PJSIDJA.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1131 Explanation: PJSIDJM was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1132 Explanation: A TSO service facility request failed. The issuing program is PJSIDJM.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1141 Explanation: PJSIDJD was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1142 Explanation: A TSO service facility request failed. The issuing program is PJSIDJD.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1151 Explanation: PJSIDJE was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1152 Explanation: PJSIDJE was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1153 Explanation: The ISPF PQUERY service failed. The issuing program is PJSIDJE.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1154 Explanation: An invalid segment was found in the PJSQ Job Request Record. The issuing program is PJSIDJE.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1155 Explanation: The segments created could not fit in the PJSQ Job Request Record. The issuing program is PJSIDJE.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1161 Explanation: PJSIDJF was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1162 Explanation: An invalid segment was found in the PJSQ Job Request Record. The issuing program is PJSIDJF.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1163 Explanation: The segments created could not fit in the PJSQ Job Request Record. The issuing program is PJSIDJF.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1171 Explanation: PJSIDJB was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1172 Explanation: A TSO service facility request failed. The issuing program is PJSIDJB.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1173 Explanation: The ISPF Library Management service failed. The issuing program is PJSIDJB.

Action: An error message will be written to the ISPF Log data set. Respond as specified for that message. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

1191 Explanation: PJSISJDV was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1201 Explanation: PJSIDCL was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1202 Explanation: A TSO service facility request failed. The issuing program is PJSIDCL.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1203 Explanation: The ISPF PQUERY service failed. The issuing program is PJSIDCL.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1204 Explanation: Insufficient storage is available to build the List Calendars Table. The issuing program is PJSIDCL.

Action: Increase the region size for the TSO session, and try again.

1211 Explanation: PJSIDCS was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1212 Explanation: A TSO service facility request failed. The issuing program is PJSIDCS.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1221 Explanation: PJSIDCA was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1222 Explanation: A TSO service facility request failed. The issuing program is PJSIDCA.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1223 Explanation: The PJS Calendar Record service routine returned an invalid return code. The issuing program is PJSIDCA.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1231 Explanation: PJSIDCAI was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1232 Explanation: A TSO service facility request failed. The issuing program is PJSIDCAI.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1241 Explanation: PJSIDCM was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1242 Explanation: A TSO service facility request failed. The issuing program is PJSIDCM.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1243 Explanation: The PJS Calendar Record service routine returned an invalid return code. The issuing program is PJSIDCM.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1251 Explanation: PJSIDCD was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1252 Explanation: A TSO service facility request failed. The issuing program is PJSIDCD.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1261 Explanation: PJSIDCJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1262 Explanation: A TSO service facility request failed. The issuing program is PJSIDCJ.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1263 Explanation: The ISPF PQUERY service failed. The issuing program is PJSIDCJ.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1264 Explanation: Insufficient storage is available to build the List Job Requests Table. The issuing program is PJSIDCJ.

Action: Increase the region size for the TSO session, and try again.

1291 Explanation: PJSISCDV was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1301 Explanation: PJSIDEL was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1302 Explanation: A TSO service facility request failed. The issuing program is PJSIDEL.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1303 Explanation: The ISPF PQUERY service failed. The issuing program is PJSIDEL.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1304 Explanation: Insufficient storage is available to build the List Events Table. The issuing program is PJSIDEL.

Action: Increase the region size for the TSO session, and try again.

1311 Explanation: PJSIDES was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1312 Explanation: A TSO service facility request failed. The issuing program is PJSIDES.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1321 Explanation: PJSIDEP was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1322 Explanation: A TSO service facility request failed. The issuing program is PJSIDEP.

Action: This abend usually occurs when the PJS ISPF Interface TSO commands cannot be accessed by the PJS ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1331 Explanation: PJSIDER was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1332 Explanation: A TSO service facility request failed. The issuing program is PJSIDER.

Action: This abend usually occurs when the PJS/ISPF Interface TSO commands cannot be accessed by the PJS/ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1341 Explanation: PJSIDEJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1342 Explanation: A TSO service facility request failed. The issuing program is PJSIDEJ.

Action: This abend usually occurs when the PJS/ISPF Interface TSO commands cannot be accessed by the PJS/ISPF Interface dialog. Check that PJS has been properly installed. Try to determine the cause of the abend and fix the problem. If the abend recurs, obtain a dump of the address space before reporting the problem.

1343 Explanation: The ISPF PQUERY service failed. The issuing program is PJSIDEJ.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1344 Explanation: Insufficient storage is available to build the List Job Requests Table. The issuing program is PJSIDEJ.

Action: Increase the region size for the TSO session, and try again.

1391 Explanation: PJSISEDV was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

1501 Explanation: PJSITJG was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1502 Explanation: PJSITJG was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1503 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Get Job Request TSO command processor (PJSITJG) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1504 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Get Job Request TSO command processor (PJSITJG).

Action: Check the PJS Installation Security Exit (PJSSECX).

1505 Explanation: The record area passed to the PJS/ISPF Get Job Request TSO command processor (PJSITJG) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1511 Explanation: PJSITJL was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1512 Explanation: PJSITJL was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1513 Explanation: A PJS Request Queue I/O function by the PJS/ISPF List Job Requests TSO command processor (PJSITJL) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1514 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF List Job Requests TSO command processor (PJSITJL).

Action: Check the PJS Installation Security Exit (PJSSECX).

1515 Explanation: The record table area passed to the PJS/ISPF List Job Requests TSO command processor (PJSITJL) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1521 Explanation: PJSITJA was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1522 Explanation: PJSITJA was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1523 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Add Job Request TSO command processor (PJSITJA) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1524 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Add Job Request TSO command processor (PJSITJA).

Action: Check the PJS Installation Security Exit (PJSSECX).

1525 Explanation: The record area passed to the PJS/ISPF Add Job Request TSO command processor (PJSITJA) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1526 Explanation: The maximum PJS JCL Spool member number has been exceeded. This abend is issued by the PJS/ISPF Add Job Request TSO command processor (PJSITJA).

Action: Call PJS Technical Support for assistance. Since the maximum PJS JCL Spool member number is currently 9999999, this is not expected to occur soon.

1531 Explanation: PJSITJM was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1532 Explanation: PJSITJM was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1533 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Modify Job Request TSO command processor (PJSITJM) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1534 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Modify Job Request TSO command processor (PJSITJM).

Action: Check the PJS Installation Security Exit (PJSSECX).

1535 Explanation: The record area passed to the PJS/ISPF Modify Job Request TSO command processor (PJSITJM) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1536 Explanation: The maximum PJS JCL Spool member number has been exceeded. This abend is issued by the PJS/ISPF Modify Job Request TSO command processor (PJSITJM).

Action: Call PJS Technical Support for assistance. Since the maximum PJS JCL Spool member number is currently 9999999, this is not expected to occur soon.

1541 Explanation: PJSITJD was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1542 Explanation: PJSITJD was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1543 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Delete Job Request TSO command processor (PJSITJD) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1544 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Delete Job Request TSO command processor (PJSITJD).

Action: Check the PJS Installation Security Exit (PJSSECX).

1551 Explanation: PJSITJJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1552 Explanation: PJSITJJ was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1553 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Get Saved JCL for Job Request TSO command processor (PJSITJJ) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1554 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Get Saved JCL for Job Request TSO command processor (PJSITJJ).

Action: Check the PJS Installation Security Exit (PJSSECX).

1555 Explanation: The DDNAME area passed to the PJS/ISPF Get Saved JCL for Job Request TSO command processor (PJSITJJ) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1601 Explanation: PJSITCG was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1602 Explanation: PJSITCG was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1603 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Get Calendar TSO command processor (PJSITCG) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1604 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Get Calendar TSO command processor (PJSITCG).

Action: Check the PJS Installation Security Exit (PJSSECX).

1605 Explanation: The record area passed to the PJS/ISPF Get Calendar TSO command processor (PJSITCG) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1611 Explanation: PJSITCL was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1612 Explanation: PJSITCL was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1613 Explanation: A PJS Request Queue I/O function by the PJS/ISPF List Calendars TSO command processor (PJSITCL) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1614 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF List Calendars TSO command processor (PJSITCL).

Action: Check the PJS Installation Security Exit (PJSSECX).

1615 Explanation: The record table area passed to the PJS/ISPF List Calendars TSO command processor (PJSITCL) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1621 Explanation: PJSITCA was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1622 Explanation: PJSITCA was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1623 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Add Calendar TSO command processor (PJSITCA) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1624 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Add Calendar TSO command processor (PJSITCA).

Action: Check the PJS Installation Security Exit (PJSSECX).

1625 Explanation: The record area passed to the PJS/ISPF Add Calendar TSO command processor (PJSITCA) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1631 Explanation: PJSITCM was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1632 Explanation: PJSITCM was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1633 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Modify Calendar TSO command processor (PJSITCM) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1634 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Modify Calendar TSO command processor (PJSITCM).

Action: Check the PJS Installation Security Exit (PJSSECX).

1635 Explanation: The record area passed to the PJS/ISPF Modify Calendar TSO command processor (PJSITCM) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1641 Explanation: PJSITCD was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1642 Explanation: PJSITCD was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1643 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Delete Calendar TSO command processor (PJSITCD) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1644 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Delete Calendar TSO command processor (PJSITCD).

Action: Check the PJS Installation Security Exit (PJSSECX).

1651 Explanation: PJSITCJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1652 Explanation: PJSITCJ was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1653 Explanation: A PJS Request Queue I/O function by the PJS/ISPF List Job Requests for Calendar TSO command processor (PJSITCJ) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1654 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF List Job Requests for Calendar TSO command processor (PJSITCJ).

Action: Check the PJS Installation Security Exit (PJSSECX).

1655 Explanation: The record table area passed to the PJS/ISPF List Job Requests for Calendar TSO command processor (PJSITCJ) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1701 Explanation: PJSITEG was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1702 Explanation: PJSITEG was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1703 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Get Event TSO command processor (PJSITEG) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1704 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Get Event TSO command processor (PJSITEG).

Action: Check the PJS Installation Security Exit (PJSSECX).

1705 Explanation: The record area passed to the PJS/ISPF Get Event TSO command processor (PJSITEG) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1711 Explanation: PJSITEL was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1712 Explanation: PJSITEL was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1713 Explanation: A PJS Request Queue I/O function by the PJS/ISPF List Events TSO command processor (PJSITEL) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1714 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF List Events TSO command processor (PJSITEL).

Action: Check the PJS Installation Security Exit (PJSSECX).

1715 Explanation: The record table area passed to the PJS/ISPF List Events TSO command processor (PJSITEL) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1721 Explanation: PJSITEP was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1722 Explanation: PJSITEP was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1723 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Post Event TSO command processor (PJSITEP) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1724 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Post Event TSO command processor (PJSITEP).

Action: Check the PJS Installation Security Exit (PJSSECX).

1731 Explanation: PJSITER was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1732 Explanation: PJSITER was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1733 Explanation: A PJS Request Queue I/O function by the PJS/ISPF Reset Event TSO command processor (PJSITER) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1734 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF Reset Event TSO command processor (PJSITER).

Action: Check the PJS Installation Security Exit (PJSSECX).

1741 Explanation: PJSITEJ was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1742 Explanation: PJSITEJ was called with an invalid command.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1743 Explanation: A PJS Request Queue I/O function by the PJS/ISPF List Job Requests for Event TSO command processor (PJSITEJ) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

1744 Explanation: The PJS Installation Security Exit (PJSSECX) denied access to the PJS/ISPF List Job Requests for Event TSO command processor (PJSITEJ).

Action: Check the PJS Installation Security Exit (PJSSECX).

1745 Explanation: The record table area passed to the PJS/ISPF List Job Requests for Event TSO command processor (PJSITEJ) is invalid.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

2001 Explanation: The PJS Message Service Routine (PJSMSG) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2002 Explanation: The PJS Message Service Routine (PJSMSG) was called with an invalid message-ID.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2003 Explanation: The PJS Message Service Routine (PJSMSG) was called with an invalid message destination list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2004 Explanation: The Message Format Service Routine (PJSMSGF) returned with an unexpected return code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2005 Explanation: The message buffer passed to the PJS Message Service Routine (PJSMSG) was not large enough to contain the formatted message.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2011 Explanation: The PJS Display Message on System Console Service Routine (PJSMSGC) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2021 Explanation: The PJS Display ISPF Message Service Routine (PJSMSGI) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2022 Explanation: An ISPF variable service issued by the PJS Display ISPF Message Service Routine (PJSMSGI) failed.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2031 Explanation: The PJS Display Message on Printer Service Routine (PJSMSGP) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2032 Explanation: An OPEN macro for the printer data set failed. This abend is issued by the PJS Display Message on Printer Service Routine (PJSMSGP).

Action: Make sure the SYSOUT DD statement is specified correctly. Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

2033 Explanation: A CLOSE macro for the printer data set failed. This abend is issued by the PJS Display Message on Printer Service Routine (PJSMSGP).

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem.

2034 Explanation: The PJS Display Message on Printer Service Routine (PJSMSGP) was called to print a message, or close the print data set, but the printer data set was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2035 Explanation: The PJS Display Message on Printer Service Routine (PJSMSGP) was called to open the printer data set, but it had previously been open and closed.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2036 Explanation: The printer data set has an invalid record format. This abend is issued by the PJS Display Message on Printer Service Routine (PJSMSGP).

Action: Make sure the SYSOUT DD statement is specified correctly. The record format must be F, FA, FM, FB, FBA, FBM, V, VA, VM, VB, VBA, or VBM.

2037 Explanation: The printer data set has an invalid record length.

Action: Make sure the SYSOUT DD statement is specified correctly. The data portion of the record, which does not include the RDW or carriage control character, must be at least 80 bytes long but no more than 255 bytes long.

2041 Explanation: The PJS Display Message on TSO Terminal Service Routine (PJSMSGT) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2042 Explanation: The PJS Display Message on TSO Terminal Service Routine (PJSMSGT) was called to send a message to the TSO terminal, but the CPPL address in the PJSVT was zero.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2043 Explanation: The TSO PUTLINE service routine failed. Register 15 contains the PUTLINE return code. This abend is issued by the PJS Display Message on TSO Terminal Service Routine (PJSMSGT).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2051 Explanation: The PJS Send Message on TSO User Service Routine (PJSMSGU) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2101 Explanation: The PJS Dynamic Allocation Service Routine (PJSALLOC) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2102 Explanation: The PJS Dynamic Allocation Service Routine (PJSALLOC) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2103 Explanation: SVC 99 (dynamic allocation) returned with an unexpected return code. This abend is issued by the PJS Dynamic Allocation Service Routine (PJSALLOC).

Action: This abend is preceded by message PJS401. Respond as specified for that message.

2201 Explanation: The PJS Request Queue I/O Service Routine (PJSQIO) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2202 Explanation: The PJS Request Queue I/O Service Routine (PJSQIO) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2203 Explanation: The PJS Request Queue I/O Service Routine (PJSQIO) was called with an invalid record type code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2204 Explanation: A PJS Request Queue record passed to the PJS Request Queue I/O Service Routine (PJSQIO) had an invalid record length.

Action: If your PJS Installation Security Exit (PJSSECX) updates the Installation Data Area, make sure this code is correct. An internal error can also cause this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2205 Explanation: A PJS Request Queue record passed to the PJS Request Queue I/O Service Routine (PJSQIO) had an invalid record key.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2211 Explanation: The PJS Request Queue I/O Service Routine Open Processor (PJSQIO1) was called to open the PJS Request Queue, but the PJS Request Queue was already open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2212 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) unexpectedly returned control to the PJS Request Queue I/O Service Routine Open Processor (PJSQIO1).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2221 Explanation: The PJS Request Queue I/O Service Routine Close Processor (PJSQIO2) was called to close the PJS Request Queue, but the PJS Request Queue was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2222 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) unexpectedly returned control to the PJS Request Queue I/O Service Routine Close Processor (PJSQIO2).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2231 Explanation: The PJS Request Queue I/O Service Routine Read Processor (PJSQIO3) was called to access the PJS Request Queue, but the PJS Request Queue was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2232 Explanation: The PJS Request Queue I/O Service Routine Read Processor (PJSQIO3) attempted to reestablish its position in the PJS Request Queue, but no current positioning has been established.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2234 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) unexpectedly returned control to the PJS Request Queue I/O Service Routine Read Processor (PJSQIO3).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2242 Explanation: The PJS Request Queue I/O Service Routine Add Processor (PJSQIO4) was called to update the PJS Request Queue, but the PJS Request Queue was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2244 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) unexpectedly returned control to the PJS Request Queue I/O Service Routine Add Processor (PJSQIO4).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2251 Explanation: The PJS Request Queue I/O Service Routine Update Processor (PJSQIO5) was called to update the PJS Request Queue, but the PJS Request Queue was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2252 Explanation: The PJS Request Queue I/O Service Routine Update Processor (PJSQIO5) attempted to reestablish its position in the PJS Request Queue, but no current positioning has been established.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2253 Explanation: The PJS Request Queue I/O Service Routine Update Processor (PJSQIO5) was called to update a PJS Request Queue record, but the record had not been previously read for update processing.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2254 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) unexpectedly returned control to the PJS Request Queue I/O Service Routine Update Processor (PJSQIO5).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2261 Explanation: The PJS Request Queue I/O Service Routine Delete Processor (PJSQIO6) was called to update the PJS Request Queue, but the PJS Request Queue was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2262 Explanation: The PJS Request Queue I/O Service Routine Delete Processor (PJSQIO6) attempted to reestablish its position in the PJS Request Queue, but no current positioning has been established.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2263 Explanation: The PJS Request Queue I/O Service Routine Delete Processor (PJSQIO6) was called to delete a PJS Request Queue record, but the record had not been previously read for update processing.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2264 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) unexpectedly returned control to the PJS Request Queue I/O Service Routine Delete Processor (PJSQIO6).

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2291 Explanation: The PJS Request Queue I/O Service Routine Error Handler (PJSQIO9) was called with an invalid error type code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2292 Explanation: A VSAM ACB based macro for the PJS Request Queue failed with an unexpected reason code. This abend is issued by the PJS Request Queue I/O Service Routine Error Handler (PJSQIO9).

Action: This abend is preceded by message PJS431. Respond as specified for that message.

2293 Explanation: A VSAM RPL based macro for the PJS Request Queue failed with an unexpected reason code. This abend is issued by the PJS Request Queue I/O Service Routine Error Handler (PJSQIO9).

Action: This abend is preceded by message PJS432. Respond as specified for that message.

2294 Explanation: A control block manipulation macro for the PJS Request Queue failed. This abend is issued by the PJS Request Queue I/O Service Routine Error Handler (PJSQIO9).

Action: This abend is preceded by message PJS433. Respond as specified for that message.

2301 Explanation: The PJS JCL Spool I/O Service Routine (PJSSIO) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2302 Explanation: The PJS JCL Spool I/O Service Routine (PJSSIO) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2303 Explanation: The PJS JCL Spool I/O Service Routine (PJSSIO) either found a PJSSIO Data Area already allocated before the open, or could not locate the PJSSIO Data Area after the open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2304 Explanation: The PJS JCL Spool I/O Service Routine (PJSSIO) was called to open the PJS JCL Spool, but the PJS JCL Spool was already open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2305 Explanation: The PJS JCL Spool I/O Service Routine (PJSSIO) was called to access or close the PJS JCL Spool, but the PJS JCL Spool was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2306 Explanation: The PJS JCL Spool Data Set specified by the PJS Installation Options Module (PJSOPT) is invalid. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS471. Respond as specified for that message.

2307 Explanation: An OPEN macro for the PJS JCL Spool failed. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS472. Respond as specified for that message.

2308 Explanation: A BLDL macro for the PJS JCL Spool failed. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS474. Respond as specified for that message.

2309 Explanation: A FIND macro for the PJS JCL Spool failed. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS475. Respond as specified for that message.

2310 Explanation: A STOW macro for the PJS JCL Spool failed. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS476. Respond as specified for that message.

2311 Explanation: A CLOSE macro for the PJS JCL Spool failed. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS473. Respond as specified for that message.

2312 Explanation: An I/O error was encountered while processing the PJS JCL Spool. This abend is issued by the PJS JCL Spool I/O Service Routine (PJSSIO).

Action: This abend is preceded by message PJS477. Respond as specified for that message.

2401 Explanation: The PJS JCL Data Set I/O Service Routine (PJSJIO) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2402 Explanation: The PJS JCL Data Set I/O Service Routine (PJSJIO) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2403 Explanation: The PJS JCL Data Set I/O Service Routine (PJSJIO) either found a PJSJIO Data Area already allocated before the open, or could not locate the PJSJIO Data Area after the open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2404 Explanation: The PJS JCL Data Set I/O Service Routine (PJSJIO) was called to open the JCL Data Set, but the JCL Data Set was already open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2405 Explanation: The PJS JCL Data Set I/O Service Routine (PJSJIO) was called to access or close the JCL Data Set, but the JCL Data Set was not open.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2406 Explanation: An OPEN macro for the JCL Data Set failed. This abend is issued by the PJS JCL Data Set I/O Service Routine (PJSJIO).

Action: This abend is preceded by message PJS451. Respond as specified for that message.

2407 Explanation: A FIND macro for the JCL Data Set failed. This abend is issued by the PJS JCL Data Set I/O Service Routine (PJSJIO).

Action: This abend is preceded by message PJS453. Respond as specified for that message.

2408 Explanation: A CLOSE macro for the JCL Data Set failed. This abend is issued by the PJS JCL Data Set I/O Service Routine (PJSJIO).

Action: This abend is preceded by message PJS452. Respond as specified for that message.

2409 Explanation: An I/O error was encountered while processing the JCL Data Set. This abend is issued by the PJS JCL Data Set I/O Service Routine (PJSJIO).

Action: This abend is preceded by message PJS454. Respond as specified for that message.

2501 Explanation: The Copy JCL to Spool Service Routine (PJSSPOOL) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2521 Explanation: The Copy JCL Spool Member to Temporary Data Set Service Routine (PJSTEMP) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2522 Explanation: An OPEN macro for a Temporary Data Set failed. This abend is issued by the Copy JCL Spool Member to Temporary Data Set Service Routine (PJSTEMP).

Action: This abend is preceded by message PJS531. Respond as specified for that message.

2523 Explanation: A CLOSE macro for a Temporary Data Set failed. This abend is issued by the Copy JCL Spool Member to Temporary Data Set Service Routine (PJSTEMP).

Action: This abend is preceded by message PJS532. Respond as specified for that message.

2601 Explanation: The Format Job Request Record Service Routine (PJSJRQFM) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2602 Explanation: The output data area passed to the Format Job Request Record Service Routine (PJSJRQFM) is not large enough to contain the formatted Job Request.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2603 Explanation: A token formatted by the Format Job Request Record Service Routine (PJSJRQFM) is larger than the area allocated for it.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2604 Explanation: The Format Job Request Record Service Routine (PJSJRQFM) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2621 Explanation: The Format Calendar Record Service Routine (PJSCALFM) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2622 Explanation: The output data area passed to the Format Calendar Record Service Routine (PJSCALFM) is not large enough to contain the formatted Calendar.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2623 Explanation: A token formatted by the Format Calendar Record Service Routine (PJSCALFM) is larger than the area allocated for it.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2624 Explanation: The Format Calendar Record Service Routine (PJSCALFM) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2641 Explanation: The Format Event Record Service Routine (PJSEVNFM) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2642 Explanation: The output data area passed to the Format Event Record Service Routine (PJSEVNFM) is not large enough to contain the formatted Event.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2643 Explanation: A token formatted by the Format Event Record Service Routine (PJSEVNFM) is larger than the area allocated for it.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2644 Explanation: The Format Event Record Service Routine (PJSEVNFM) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2701 Explanation: The Calculate Next Run Date/Time Service Routine (PJSFREQ) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2702 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid date or time field.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2703 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid frequency type code.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2704 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid frequency period units code.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2705 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid frequency period quantity.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2706 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid days-of-week flag.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2707 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid number of days before end-of-month value.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2708 Explanation: The PJSQ Job Request record passed to the Calculate Next Run Date/Time Service Routine (PJSFREQ) contains an invalid or missing Calendar Table segment.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2709 Explanation: A PJS Request Queue I/O function by the Calculate Next Run Date/Time Service Routine (PJSFREQ) failed.

Action: Check for previous error messages and respond as specified for those messages. If the cause of the problem cannot be determined, obtain a dump of the address space before reporting the problem. This TSO command is intended for PJS internal use only.

2801 Explanation: The Calendar Data Utility Service Routine (PJSCALU) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2802 Explanation: The Calendar Data Utility Service Routine (PJSCALU) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

2803 Explanation: The PJSQ Calendar record passed to the Calendar Data Utility Service Routine (PJSCALU) contains an invalid selected dates string.

Action: Check the PJS Request Queue for corrupted records. In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

3001 Explanation: The Job Request-ID Input Service Routine (PJSJRQID) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

3101 Explanation: The Calendar-ID Input Service Routine (PJSCALID) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

3201 Explanation: The Event-ID Input Service Routine (PJSEVNID) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

3501 Explanation: The PJS Date/Time Service Routine (PJSDATIM) was called with an invalid parameter list.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

3502 Explanation: The PJS Date/Time Service Routine (PJSDATIM) was called with an invalid function code.

Action: In most cases, an internal error has caused this abend. Check that PJS has been properly installed. If the abend recurs, obtain a dump of the address space before reporting the problem.

40 nn Explanation: This abend code ranges from 4000 through 4095; this range of abend codes is reserved for use in installation exits. Their meaning depends on the type of exit installed at your site.

Action: Note the actions that preceded generation of the abend code, and contact the person who installed PJS. If you are the PJS installer, check the installation exits for the source of the abend, and fix the problem. For more information on the PJS Installation Exits, please refer to the Personal Job Scheduler (PJS) Installation Guide.

Prev | Table of Contents | Next

Copyright © Northrop Grumman, 1990, 2004. All rights reserved.