PJS Messages and Codes

2. PJS Messages

PJS011I PJS OPTIONS IN EFFECT

Explanation: This message begins the PJS Options Table List in the SYSOUT data set from the PJS System Task. Message PJS012I will follow.

Action: Because this message does not signify an error condition, no action is required.

PJS012I option = value

Explanation: The PJS option indicated has been assigned the indicated value.

The following values are displayed:

option is the name of the option parameter on the PJSOPT macro.

value is the value assigned to the option parameter.

Action: Because this message does not signify an error condition, no action is required.

PJS013E PJS OPTION option IS INVALID

Explanation: The PJS option indicated has been assigned an invalid value. The value set is indicated by the preceding PJS012I message.

The following value is displayed:

option is the name of the option parameter on the PJSOPT macro.

Action: Contact the person who installed PJS to make sure the specifications in the PJSOPT module are correct. If you installed PJS, make sure the option is specified correctly. If the PJSOPTX Installation Options Exit is being used, make sure it is modifying the options correctly.

PJS101I jobname ‑ PJS release SYSTEM TASK STARTING

Explanation: The PJS System Task is beginning start-up processing.

The following values are displayed:

jobname is the jobname of the PJS Started Task.

release is the release and modification level of the PJS software.

Action: Because this message does not signify an error condition, no action is required.

PJS102I jobname ‑ PJS SYSTEM TASK ENDING

Explanation: The PJS System Task is ending execution.

The following value is displayed:

jobname is the jobname of the PJS Started Task.

Action: Because this message does not signify an error condition, no action is required.

PJS103W jobname ‑ PJS SYSTEM TASK NOT APF AUTHORIZED, TSO MESSAGES WILL NOT BE SENT

Explanation: The PJS System Task is not running with APF authorization. As a result, the TSO SEND command cannot be issued to send messages to the TSO user. PJS processing will continue, but PJS will not send messages.

The following value is displayed:

jobname is the jobname of the PJS Started Task.

Action: Contact the person who installed PJS. If you installed PJS, and if you want users to receive messages, please refer to the Personal Job Scheduler (PJS) Installation Guide for information on how to run PJS with APF authorization.

PJS111I jobname ‑ READY FOR COMMAND

Explanation: The PJS System Task is now accepting operator commands.

The following value is displayed:

jobname is the jobname of the task.

Action: Because this message does not signify an error condition, no action is required. For information on operator commands, refer to the Personal Job Scheduler (PJS) Installation Guide.

PJS112I jobname ‑ command

Explanation: The PJS System Task received the indicated command.

The following values are displayed:

jobname is the jobname of the task.

command is the command text PJS received.

Action: Because this message does not signify an error condition, no action is required.

PJS113E jobname ‑ INVALID COMMAND

Explanation: The last command received by the PJS System Task was not a valid command.

The following value is displayed:

jobname is the jobname of the task.

Action: If needed, review command syntax.

PJS121I jobname ‑ PJS SYSTEM TASK ALREADY STARTED

Explanation: The operator tried to start the PJS System Task when the PJS System Task was already started in another address space. The second copy of the PJS System Task will terminate.

The following value is displayed:

jobname is the jobname of the task.

Action: No action is required.

PJS122I OPERATOR COMMUNICATION SUBTASK ABENDED, CODE=abcode

Explanation: The operator communication subtask of the PJS System Task has abended. The PJS System Task is terminated. In most cases, a PJS internal error has generated this message.

The following value is displayed:

abcode is the abend code for the operator communication subtask.

Action: Restart the PJS System Task. Check the documentation on the abend, try to determine the cause of the error, and fix the problem. If the error recurs, report this problem.

PJS123I OPERATOR COMMUNICATION SUBTASK QEDIT ERROR, RC=rc, REF=ref‑ID

Explanation: A QEDIT macro issued by the operator communication subtask of the PJS System Task has failed. The PJS System Task is terminated. In most cases, a PJS internal error has generated this message.

The following values are displayed:

rc is the QEDIT macro return code.

ref‑ID is a PJS function reference-ID.

Action: Restart the PJS System Task. Try to determine the cause of the error and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS131I JOB SUBMISSION FOR REQUEST req‑ID SUCCESSFUL

Explanation: The job submission for the indicated Job Request was successful.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Because this message does not signify an error condition, no action is required.

PJS132E JOB SUBMISSION FOR REQUEST req-ID FAILED

Explanation: The job submission for the indicated Job Request failed. A previous message should indicate the reason for the failure. The Job Request is placed in ERROR status, and the following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Check any accompanying messages for more information, then delete or modify the job request. If necessary, resubmit the job.

PJS133E JOB SUBMIT SUBTASK ABENDED, CODE=abcode, REASON=reason

Explanation: The job submission subtask abended while attempting to submit a job. Message PJS132 will follow, indicating the Job Request being processed. It is possible that the job was actually submitted before the subtask abended in clean-up processing.

The following values are displayed:

abcode is the abend code for the job submission subtask.

reason is the reason code associated with the abend code.

Action: Check any accompanying messages for more information, then delete or modify the Job Request. Resubmit the job; if another failure occurs, check for the existence of the data set, and make sure the data set contains JCL. Check the documentation on abend and reason codes, then try to determine the cause of the error and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS134E JOB SUBMIT WINDOW FOR REQUEST req-ID MISSED

Explanation: The job submit window for the indicated Job Request was exceeded. The action taken will be described by one of the following messages: PJS135, PJS136, or PJS137.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Check the following message for the disposition of the Job Request. If necessary, delete or modify the job request, or resubmit the job.

PJS135I JOB REQUEST req-ID HAS BEEN RESCHEDULED, NEXT RUN DATE/TIME = date time

Explanation: The displayed job request has been placed in WAIT status until the next scheduled run date and time.

The following values are displayed:

req‑ID is the request-ID for the processed job request.

date is the next scheduled run date.

time is the next scheduled run time.

Action: Because this message does not signify an error condition, no action is required.

PJS136I JOB REQUEST req-ID HAS BEEN COMPLETED

Explanation: The displayed job request has been placed in COMPLETE status.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Because this message does not signify an error condition, no action is required.

PJS137I JOB REQUEST req-ID HAS BEEN DISABLED

Explanation: The displayed job request has been placed in the DISABLED status.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Because this message does not signify an error condition, no action is required.

PJS138I JOB REQUEST req-ID HAS BEEN DELAYED

Explanation: The displayed job request has been delayed by a temporary submit error, and will be retried later. The job request is placed in the WAIT status.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: This message does not necessarily indicate an error. This is usually caused by another address space holding an exclusive enqueue on the JCL data set for the job request. If possible, find the cause of the enqueue and correct the situation.

PJS139I JOB REQUEST req-ID HAS BEEN DISABLED IN ERROR

Explanation: The displayed job request has been placed in the ERROR status. A previous message should indicate the reason for the failure.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Because this message does not signify an error condition, no action is required.

PJS141W SYSTEM FAILURE OCCURRED DURING SUBMIT FOR JOB REQUEST req-ID, SUBMIT STATUS CANNOT BE DETERMINED

Explanation: At system task start‑up time, a job request in SUBMIT status was found. This occurs when the PJS System Task fails while trying to submit a job. Because PJS doesn't know whether the job was submitted, it places the job request in ERROR status.

The following value is displayed:

req‑ID is the request-ID for the processed job request.

Action: Check the PJS Request Queue to see whether the job ran. Modify or delete the job request.

PJS152E OPEN ERROR FOR INTERNAL READER, RC=rc, REQID=req-ID

Explanation: The OPEN for the internal reader failed. The job request will be placed in ERROR status.

The following values are displayed:

rc is the OPEN macro return code.

req‑ID is the request-ID for the processed Job Request.

Action: Modify or delete the job request. Try to determine the cause of the error and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS153E CLOSE ERROR FOR INTERNAL READER, RC=rc, REQID=req-ID

Explanation: The CLOSE for the internal reader failed. The job request will be placed in ERROR status.

The following values are displayed:

rc is the CLOSE macro return code.

req‑ID is the request-ID for the processed job request.

PJS154E ACCESS TO SUBMIT FUNCTION DENIED, REQID=req-ID

Explanation: The PJS Installation Security Exit denied access to the PJS System Task Submit function. The job couldn't be submitted and was placed in ERROR status.

The following value is displayed:

req‑ID Request ID for the job request processed.

Action: Contact the site Security Administrator or the person who installed PJS.

PJS155E JOB SUBMISSION FOR REQUEST req-ID PURGED BY INSTALLATION

Explanation: The PJS Installation Submit Exit requested that the job for the displayed request-ID be purged before it could be executed. The job was not submitted and was placed in ERROR status.

The following value is displayed:

req‑ID is the request‑ID for the processed job request.

Action: Contact the site Security Administrator or the person who installed PJS.

PJS156E INSTALLATION SUBMIT EXIT ERROR, RC=rc, REQID=req-ID

Explanation: The PJS Installation Submit Exit generated an invalid return code. The job could not be submitted and was placed in ERROR status.

The following values are displayed:

rc is the invalid return code generated by the exit.

req‑ID is the request-ID for the processed job request.

Action: Contact the person who installed PJS.

PJS201I JOB REQUEST req-ID SUCCESSFULLY ADDED

Explanation: The displayed job request has been successfully added to the PJS Request Queue. This message will be followed by a listing of the added Job Request.

The following value is displayed:

req‑ID is the request-ID for the added job request.

Action: Because this message does not signify an error condition, no action is required.

PJS202I JOB REQUEST req-ID SUCCESSFULLY MODIFIED

Explanation: The displayed job request has been successfully modified on the PJS Request Queue. This message will be followed by a listing of the modified job request.

The following value is displayed:

req‑ID is the request-ID for the modified job request.

Action: Because this message does not signify an error condition, no action is required.

PJS203I JOB REQUEST req-ID SUCCESSFULLY DELETED

Explanation: The displayed job request has been successfully deleted from the PJS Request Queue. This message will be followed by a listing of the deleted job request.

The following value is displayed:

req‑ID is the request-ID for the deleted job request.

Action: Because this message does not signify an error condition, no action is required.

PJS204W NO CHANGES MADE, JOB REQUEST NOT MODIFIED

Explanation: The modify command entered did not specify any changes. The job request record was not modified.

Action: If you want to modify a job request, review command syntax, and try again.

PJS211E JOB REQUEST req-ID NOT FOUND

Explanation: The displayed job request does not exist.

The following value is displayed:

req‑ID is the request-ID for the specified job request.

Action: Make sure you specify the correct request‑ID, and try again.

PJS212E NO JOB REQUESTS FOR SPECIFIED OWNER

Explanation: PJS tried to list job requests for an owner-ID that has no job requests on the PJS Request Queue.

Action: Because this message does not signify an error condition, no action is required.

PJS213E NO JOB REQUESTS IN REQUEST QUEUE

Explanation: PJS tried to list all the job requests in the PJS Request Queue, but there are no job requests on the PJS Request Queue.

Action: Because this message does not signify an error condition, no action is required.

PJS214E ACCESS TO JOB REQUEST req-ID DENIED BY INSTALLATION

Explanation: The PJS Installation Security Exit has denied access to the specified job request record.

The following value is displayed:

req‑ID is the request-ID for the job request.

Action: Contact your site Security Administrator or the person who installed PJS.

PJS215E JOB REQUEST req-ID EXCEEDS MAXIMUM SIZE

Explanation: PJS tried to add or modify a job request. Including the base segment, the calendar segment, the event segment, and the installation data area, the job request record exceeds the maximum PJS Request Queue record size of 4084 bytes.

The following value is displayed:

req‑ID is the request-ID for the job request you want to add or modify.

Action: Specify fewer calendars or events for the job request. If this is not possible, contact the person who installed PJS.

PJS216E JOB REQUEST req-ID IS IN SUBMIT STATUS

Explanation: PJS tried to delete or modify a job request in SUBMIT status. The request is either being submitted or the PJS System Task abnormally terminated during submit processing for the job request and has not been restarted.

The following value is displayed:

req‑ID is the request-ID for the specified job request.

Action: If the request is being submitted, wait until PJS finishes the submission, then try to delete or modify the job request. If the PJS System Task abnormally terminated, wait for the System Task to restart and for PJS to set the ERROR status, then try again.

PJS217E NO REQUEST‑ID'S FOR OWNER owner-ID

Explanation: An attempt was made to add a job request for an owner‑ID that has 999 queued job requests, which is the upper limit.

The following value is displayed:

owner-ID is the owner-ID for the job request to be added.

Action: If feasible, delete one queued job request for each new job request you plan to add to the PJS Request Queue.

PJS221I CALENDAR cal-ID SUCCESSFULLY ADDED

Explanation: The displayed calendar has been successfully added to the PJS Request Queue. This message will be followed by a listing of the added calendar.

The following value is displayed:

cal‑ID is the calendar-ID for the added calendar.

Action: Because this message does not signify an error condition, no action is required.

PJS222I CALENDAR cal-ID SUCCESSFULLY MODIFIED

Explanation: The displayed calendar has been successfully modified. This message will be followed by a listing of the modified calendar.

The following value is displayed:

cal‑ID is the calendar-ID for the modified calendar.

Action: Because this message does not signify an error condition, no action is required.

PJS223I CALENDAR cal-ID SUCCESSFULLY DELETED

Explanation: The displayed calendar has been successfully deleted from the PJS Request Queue. This message will be followed by a listing of the deleted calendar.

The following value is displayed:

cal‑ID is the calendar-ID for the deleted calendar.

Action: Because this message does not signify an error condition, no action is required.

PJS224W NO CHANGES MADE, CALENDAR NOT MODIFIED

Explanation: The modify command did not specify any changes. The calendar record was not modified.

Action: If you want to modify a calendar, review command syntax, and try again.

PJS231E CALENDAR cal-ID NOT FOUND

Explanation: The displayed calendar does not exist.

The following value is displayed:

cal‑ID is the calendar-ID for the specified calendar.

Action: Make sure you specify the correct calendar‑ID, and try again.

PJS232E NO CALENDARS FOR SPECIFIED OWNER

Explanation: PJS tried to list calendars for an owner-ID that has no calendars on the PJS Request Queue.

Action: Because this message does not signify an error condition, no action is required.

PJS233E NO CALENDARS IN REQUEST QUEUE

Explanation: PJS tried to list all the calendars in the PJS Request Queue, but there are no calendars on the PJS Request Queue.

Action: Because this message does not signify an error condition, no action is required.

PJS234E ACCESS TO CALENDAR cal-ID DENIED BY INSTALLATION

Explanation: The PJS Installation Security Exit has denied access to the specified calendar record.

The following value is displayed:

cal‑ID is the calendar-ID for the calendar.

Action: Contact your site Security Administrator or the person who installed PJS.

PJS235E CALENDAR cal-ID EXCEEDS MAXIMUM SIZE

Explanation: PJS tried to add or modify a calendar. The total size of the calendar, which is based on the difference between the first selected date and the last selected date, exceeds the maximum PJS Request Queue record size of 4084 bytes.

The following value is displayed:

cal‑ID is the calendar-ID for the calendar you want to add or modify.

Action: Eliminate the last dates selected on the calendar. If this is not possible, contact the person who installed PJS.

PJS237E CALENDAR cal-ID ALREADY EXISTS

Explanation: You tried to add a calendar-ID that already exists on the PJS Request Queue.

The following value is displayed:

cal-ID is the specified calendar-ID.

Action: Use a different calendar-ID for the calendar you want to add.

PJS241I EVENT event-ID SUCCESSFULLY POSTED

Explanation: The displayed event has been successfully posted on the PJS Request Queue. The individual job request events will be posted by the PJS System Task on its next PJS Request Queue Scan. Until then, the event record will be in POST PENDING status. This message will be followed by a listing of the posted event.

The following value is displayed:

event‑ID is the event-ID for the posted event.

Action: Because this message does not signify an error condition, no action is required.

PJS242I EVENT event-ID SUCCESSFULLY RESET

Explanation: The displayed event has been successfully reset on the PJS Request Queue. The individual job request events will be reset by the PJS System Task on its next PJS Request Queue Scan. Until then, the event record will be in RESET PENDING status. This message will be followed by a listing of the posted event.

The following value is displayed:

event‑ID is the event-ID for the reset event.

Action: Because this message does not signify an error condition, no action is required.

PJS251E EVENT event-ID NOT FOUND

Explanation: The displayed event does not exist.

The following value is displayed:

event‑ID is the event-ID for the specified event.

Action: Make sure you specify the correct event‑ID, and try again.

PJS252E NO EVENTS FOR SPECIFIED OWNER

Explanation: PJS tried to list events for an Owner-ID that has no events on the PJS Request Queue.

Action: Because this message does not signify an error condition, no action is required.

PJS253E NO EVENTS IN REQUEST QUEUE

Explanation: PJS tried to list all the events in the PJS Request Queue, but there are no events on the PJS Request Queue.

Action: Because this message does not signify an error condition, no action is required.

PJS254E ACCESS TO EVENT event-ID DENIED BY INSTALLATION

Explanation: The PJS Installation Security Exit has denied access to the specified event record.

The following value is displayed:

event‑ID is the event-ID for the event.

Action: Contact your site Security Administrator or the person who installed PJS.

PJS301E NOSAVE OPTION IS NOT ALLOWED BY INSTALLATION

Explanation: NOSAVE was specified on the job request add or modify command. When PJS was installed, the PJS Options Table was defined to allow only the SAVE option. The job request was not added or modified.

Action: Remove the NOSAVE option from the command before you resubmit the command.

PJS302E SAVE OPTION IS NOT ALLOWED BY INSTALLATION

Explanation: SAVE was specified on the job request add or modify command. When PJS was installed, the PJS Options Table was defined to allow only the NOSAVE option. The job request was not added or modified.

Action: Remove the SAVE option from the command before you resubmit the command.

PJS303E RESAVE SPECIFIED, JCL IS NOT CURRENTLY SAVED

Explanation: RESAVE was specified on the job request add or modify command. No previous SAVE parameter was specified for the job request or NOSAVE was specified or accepted. The job request was not added or modified.

Action: Specify the SAVE parameter in the add or modify command to save a copy of the job JCL on the PJS JCL Spool. Then resubmit the command.

PJS304E SAVED JCL LIMIT EXCEEDED FOR OWNER owner-ID

Explanation: The total number of records saved in the PJS JCL Spool for this owner exceeds the maximum allowed by the installation. The job request was not added or modified.

The following value is displayed:

owner-ID is the owner-ID for which the JCL Spool Limit is exceeded.

Action: Reduce the number of JCL records saved in the PJS JCL Spool. Then resubmit the command.

PJS311E END DATE/TIME IS LESS THAN START DATE/TIME

Explanation: The End Date and End Time specified for the Job Request being added or modified is less than the Start Date and Start Time. The job request was not added or modified.

Action: Make sure you specify a valid Start Date, Start Time, End Date, and End Time before you resubmit the command.

PJS312E NEXT RUN DATE/TIME EXCEEDS END DATE/TIME, OR IS ALREADY PAST

Explanation: The Next Run Date and Time specified for the job request you plan to add or modify exceeds the specified End Date and End Time, or, for a one‑time job request, is already past. The Next Run Date and Time is calculated from the Start Date and Start Time, the frequency selected for job submission, and the current system date and time. The job request was not added or modified.

Action: Make sure you specify a valid Start Date, Start Time, End Date, and End Time, and frequency option before you resubmit the command.

PJS313E CALENDAR HAS NO DATES

Explanation: The calendar you plan to add or modify has no selected, or all of the selected dates are past. The calendar was not added or modified.

Action: Make sure the calendar selects at least one date that is not past before you resubmit the command.

PJS321E WINDOW OPTION SPECIFIED FOR JOB REQUEST WITHOUT WINDOW TIME

Explanation: You specified the Window Option parameter for the job request, but not a Window Time. The job request was not added or modified.

Action: Specify a Window Time parameter, or remove the Window Option parameter before you reissue the command.

PJS331E ADDCALENDAR PARAMETER SPECIFIED FOR NON-CALENDAR FREQUENCY JOB REQUEST

Explanation: The ADDCALENDAR parameter was specified for the job request being added or modified, but the job request does not specify calendar scheduling. The job request was not added or modified.

Action: Use the CALENDARS parameter to specify calendar scheduling, or remove the ADDCALENDAR parameter before you resubmit the command.

PJS332E DELCALENDAR PARAMETER SPECIFIED FOR NON-CALENDAR FREQUENCY JOB REQUEST

Explanation: The DELCALENDAR parameter was specified for the job request being added or modified, but the job request does not specify calendar scheduling. The job request was not added or modified.

Action: Remove the DELCALENDAR parameter before you resubmit the command.

PJS333E MAXIMUM NUMBER OF CALENDARS FOR JOB REQUEST EXCEEDED

Explanation: The job request being added or modified specifies more calendars than can be stored in a job request record. The current maximum is 3 calendars. The job request was not added or modified.

Action: Delete at least one calendar using the DELCALENDAR parameter, or respecify all the calendars using the CALENDARS parameter before you resubmit the command.

PJS334E ALL CALENDARS DELETED FROM JOB REQUEST

Explanation: The DELCALENDARS parameter attempted to delete all calendars for the job request being added or modified. The job request was not added or modified.

Action: To delete all calendars from a job request, another frequency option must be specified. Specify a non-calendar frequency parameter before you resubmit the command.

PJS341E MAXIMUM NUMBER OF EVENTS FOR JOB REQUEST EXCEEDED

Explanation: The job request being added or modified specifies more events than can be stored in a job request record. The current maximum is 50 events. The job request was not added or modified.

Action: Delete one or more events using the DELEVENTS parameter, or respecify all the events using the EVENTS parameter before you resubmit the command.

PJS351E DAY-OF-WEEK SCHEDULING SPECIFIED, BUT NO DAYS SELECTED

Explanation: The job request being added or modified specifies the WEEKDAYS parameter, but does not include any days of the week. The job request was not added or modified.

Action: Include at least one day of the week parameter with the WEEKDAYS parameter before you resubmit the command.

PJS391E ACCESS TO FUNCTION DENIED

Explanation: The PJS Installation Security Exit (PJSSECX) has denied access to the requested function.

Action: Contact the Site Administrator or the person who installed PJS.

PJS401E DYNAMIC function FAILED FOR data-set, error-desc

Explanation: An SVC 99 (dynamic allocation) function failed.

The following values are displayed:

function is the SVC 99 function being performed:

ALLOCATION

DEALLOCATION

data-set indicates the data set for which the function is being performed:

REQUEST QUEUE

JCL SPOOL

INTERNAL READER

TEMPORARY DATA SET

dsname (User’s JCL data set)

error-desc describes the error encountered. The individual errors are described in the following paragraphs:

DATA SET NOT FOUND

Explanation: The data set could not be found. One of the following occurred:

· The data set was not cataloged.

· The data set could not be found on the volume indicated by the catalog.

· The name of the data set was misspelled.

Action: Correctly specify the name of the data set, and try again. If this error message is redisplayed, try to determine the cause of the error and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

DATA SET IN USE

Explanation: The data set could not be allocated, because another address space has allocated the data set with exclusive control.

Action: If this message is issued by the PJS System Task for the JCL data set, and the maximum retry limit has not been exceeded, the PJS system task will retry the submit later. If possible, try to resolve the conflict before the retry limit is exceeded. In all other cases, either wait until exclusive control is relinquished or contact the user who has allocated the data set.

UNIT NOT AVAILABLE

Explanation: All JES internal readers are currently allocated. The PJS System Task is unable to submit jobs. All job submits will be delayed until an internal reader is available. The job submit retry option limit does not apply to this situation.

Action: Increase the number of JES internal readers, or reduce the number of tasks using internal readers. PJS will resume job submission when an internal reader is available.

SVC 99 ERROR, RC=rc, ERROR=X'error', INFO=X'info'

Explanation: An unanticipated error occurred in SVC 99 processing.

The following values are displayed:

rc is the SVC 99 Return Code.

error is the SVC 99 Error Reason Code.

info is the SVC 99 Information Reason Code.

Action: Check the documentation on the displayed codes, then try to determine the cause of the error and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS431E VSAM ACB ERROR FOR REQUEST QUEUE, FUNC=func, RC=rc, REASON=reason, REF=ref-ID

Explanation: A VSAM ACB based macro for the PJS Request Queue has failed.

The following values are displayed:

func is the VSAM ACB function being performed.

rc is an ACB Macro Return Code (from register 15).

reason is an ACB Error Reason Code (from ACB).

ref‑ID is a PJS function reference-ID.

Action: Check the documentation on the codes, then try to determine the cause of the error and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS432E VSAM RPL ERROR FOR REQUEST QUEUE, FUNC=func, RC=rc, REASON=reason, REF=ref-ID

Explanation: A VSAM RPL based macro for the PJS Request Queue has failed.

The following values are displayed:

func is the VSAM RPL function being performed.

rc is the RPL Macro Return Code (from register 15).

reason is the RPL Error Reason Code (from RPLERRCD).

ref‑ID is a PJS function reference-ID.

PJS433E VSAM CONTROL BLOCK ERROR FOR REQUEST QUEUE, FUNC=func, RC=rc, REASON=reason, REF=ref-ID

Explanation: A VSAM control block manipulation macro for the PJS Request Queue has failed. In most cases, this is a PJS internal error.

The following values are displayed:

func is the VSAM control block function being performed.

rc is the Control Block Macro Return Code (from register 15).

reason is the Control Block Macro Error Reason Code (from register 0).

ref‑ID is a PJS function reference-ID.

PJS441E JCL MEMBER NOT FOUND, DSN=dsname(member)

Explanation: The JCL member could not be found in the JCL data set specified.

The following values are displayed:

dsname is the name of the JCL data set.

member is the name of the JCL member.

Action: Correctly specify the name of the JCL member, and try again.

PJS442E JCL DATA SET ACCESS DENIED, DSN=dsname

Explanation: The PJS Installation Security Exit (PJSSECX) has denied access to the specified JCL data set.

The following value is displayed:

dsname is the name of the JCL data set.

Action: Contact the site Security Administrator or the person who installed PJS.

PJS443E JCL MEMBER SPECIFIED, DATA SET IS NOT PARTITIONED, DSN=dsname(member)

Explanation: A member name was specified for the JCL data set, but the JCL data set is not a partitioned data set.

The following values are displayed:

dsname is the name of the JCL data set.

member is the name of the JCL member.

Action: Correctly specify the name of the JCL data set, and try again.

PJS444E JCL MEMBER NOT SPECIFIED, DATA SET IS PARTITIONED, DSN=dsname

Explanation: No member name was specified for the JCL data set, but the JCL data set is a partitioned data set.

The following value is displayed:

dsname is the name of the JCL data set.

Action: Specify the name of a member from the JCL data set, and try again.

PJS445E JCL DATA SET HAS INVALID ORGANIZATION, DSN=dsname

Explanation: The JCL data set organization (DSORG) is not sequential (PS) or partitioned (PO).

The following value is displayed:

dsname is the name of the JCL data set.

Action: Make sure you correctly specified the name of the JCL data set. If needed, fix the problem and resubmit the job.

PJS446E JCL DATA SET HAS INVALID RECORD FORMAT, DSN=dsname

Explanation: The JCL data set record format (RECFM) is not fixed (F, FB, or FBS).

The following value is displayed:

dsname is the name of the JCL data set.

Action: Make sure you correctly specified the name of the JCL data set. If needed, fix the problem and resubmit the job.

PJS447E JCL DATA SET HAS INVALID RECORD LENGTH, DSN=dsname

Explanation: The JCL data set record length (LRECL) is not 80 bytes.

The following value is displayed:

dsname is the name of the JCL data set.

Action: Make sure you correctly specified the name of the JCL data set. If needed, fix the problem and resubmit the job.

PJS451E OPEN ERROR FOR JCL DATA SET, RC=rc, DSN=dsname

Explanation: An OPEN macro for the JCL data set failed.

The following values are displayed:

rc is an OPEN macro return code.

dsname is the name of the JCL data set.

Action: Check the documentation on the OPEN macro return code, try to determine the cause of the error, and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS452E CLOSE ERROR FOR JCL DATA SET, RC=rc, DSN=dsname

Explanation: A CLOSE macro for the JCL data set failed.

The following values are displayed:

rc is the CLOSE macro return code.

dsname is the name of the JCL data set.

Action: Check the documentation on the CLOSE macro return code, try to determine the cause of the error, and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS453E FIND ERROR FOR JCL DATA SET, RC=rc, REASON=reason, DSN=dsname

Explanation: A FIND macro for the JCL data set failed.

The following values are displayed:

rc is the FIND macro return code.

reason is the FIND macro reason code.

dsname is the name of the JCL data set.

Action: Check the documentation on the FIND macro return code and reason code, try to determine the cause of the error, and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS454E I/O ERROR FOR JCL DATA SET, DSN=dsname(member), SYNADAF MESSAGE=message

Explanation: A I/O error occurred for the JCL data set.

The following values are displayed:

dsname is the name of the JCL data set.

member is the name of the JCL member.

message is the message returned by the SYNADAF function describing the error.

Action: Check the SYNADAF error message to try to determine the cause of the error, and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS461E JCL SPOOL MEMBER NOT FOUND, REQID=req-ID, MEMBER=member

Explanation: The JCL Spool Member could not be found in the JCL data set specified, or the request-ID in the directory entry user data did not match the job request record. This situation can occur if an abend or system crash occurs while PJS is updating the PJS JCL Spool, or if a utility other than PJS updates the PJS JCL Spool.

The following values are displayed:

req-ID is the request-ID of the job request associated with the PJS JCL Spool member.

member is the name of the PJS JCL Spool member.

Action: Delete the job request involved, then re-add it. Make sure non-PJS utilities do not update the user data field of the directory entries for the PJS JCL Spool data set.

PJS471E JCL SPOOL DATA SET IS INVALID

Explanation: The PJS JCL Spool data set is invalid. The PJS JCL Spool must be a partitioned data set with RECFM=FB, LRECL=80, and any appropriate blocksize.

Action: Report this error to the person who installed PJS.

PJS472E OPEN ERROR FOR JCL SPOOL DATA SET, RC=rc

Explanation: An OPEN macro for the PJS JCL Spool data set failed.

The following value is displayed:

rc is an OPEN macro return code.

PJS473E CLOSE ERROR FOR JCL SPOOL DATA SET, RC=rc

Explanation: A CLOSE macro for the PJS JCL Spool data set failed.

The following value is displayed:

rc is the CLOSE macro return code.

PJS474E BLDL ERROR FOR JCL SPOOL DATA SET, RC=rc, REASON=reason, MEMBER=member, REQID=req-ID

Explanation: A BLDL macro for the PJS JCL Spool data set failed.

The following values are displayed:

rc is the BLDL macro return code.

reason is the BLDL macro reason code.

member is the name of the PJS JCL Spool member.

req-ID is the request-ID of the job request associated with the PJS JCL Spool member.

Action: Check the documentation on the BLDL macro return code and reason code, try to determine the cause of the error, and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS475E FIND ERROR FOR JCL SPOOL DATA SET, RC=rc, REASON=reason, MEMBER=member, REQID=req-ID

Explanation: A FIND macro for the PJS JCL Spool data set failed.

The following values are displayed:

rc is the FIND macro return code.

reason is the FIND macro reason code.

member is the name of the PJS JCL Spool member.

req-ID is the request-ID of the job request associated with the PJS JCL Spool member.

PJS476E STOW ERROR FOR JCL SPOOL DATA SET, RC=rc, REASON=reason, MEMBER=member, REQID=req-ID

Explanation: A STOW macro for the PJS JCL Spool data set failed.

The following values are displayed:

rc is the STOW macro return code.

reason is the STOW macro reason code.

member is the name of the PJS JCL Spool member.

req-ID is the request-ID of the job request associated with the PJS JCL Spool member.

Action: Check the documentation on the STOW macro return code and reason code, try to determine the cause of the error, and fix the problem. If possible, repeat the actions that preceded the generation of this message. If the error recurs, report this problem.

PJS477E I/O ERROR FOR JCL SPOOL DATA SET, MEMBER=member, REQID=req-ID, SYNADAF MESSAGE=message

Explanation: A I/O error occurred for the PJS JCL Spool data set.

The following values are displayed:

member is the name of the PJS JCL Spool member.

req-ID is the request-ID of the job request associated with the PJS JCL Spool member.

message is the message returned by the SYNADAF function describing the error.

PJS501E MAXIMUM SPOOL RECORD COUNT EXCEEDED

Explanation: The total number of records saved in the PJS JCL Spool for the JCL Spool member exceeds the maximum allowed by the installation. The job request was not added or modified.

Action: Reduce the number of JCL records saved in the PJS JCL Spool. Then resubmit the command.

PJS531E OPEN ERROR FOR TEMPORARY DATA SET, RC=rc, DSN=dsname

Explanation: An OPEN macro for a temporary data set failed.

The following values are displayed:

rc is an OPEN macro return code.

dsname is the data set name of the temporary data set.

PJS532E CLOSE ERROR FOR TEMPORARY DATA SET, RC=rc, DSN=dsname

Explanation: A CLOSE macro for a temporary data set failed.

The following values are displayed:

rc is a CLOSE macro return code.

dsname is the data set name of the temporary data set.

PJS701I PJSQINIT ‑ QUEUE DATA SET INITIALIZATION

Explanation: The PJS Request Queue initialization utility is starting.

Action: Because this message does not signify an error condition, no action is required.

PJS702I PJSQINIT ‑ QUEUE DATA SET SUCCESSFULLY INITIALIZED

Explanation: The PJS Request Queue has been successfully initialized.

Action: Because this message does not signify an error condition, no action is required.

PJS711E PJSQINIT ‑ VSAM OPEN ERROR FOR QUEUE DATA SET, RC=rc, REASON=reason

Explanation: The VSAM OPEN macro for the PJS Request Queue has failed.

The following values are displayed:

rc is the OPEN Macro Return Code (from register 15).

reason is the ACB Error Reason Code (from ACB).

PJS712E PJSQINIT ‑ VSAM I/O ERROR FOR QUEUE DATA SET, RC=rc, REASON=reason

Explanation: A VSAM PUT macro for the PJS Request Queue has failed.

The following values are displayed:

rc is the PUT Macro Return Code (from register 15).

reason is the RPL Error Reason Code (from RPLERRCD).

PJS713E PJSQINIT ‑ VSAM CLOSE ERROR FOR QUEUE DATA SET, RC=rc, REASON=reason

Explanation: The VSAM CLOSE macro for the PJS Request Queue has failed.

The following values are displayed:

rc is the CLOSE Macro Return Code (from register 15).

reason is the ACB Error Reason Code (from ACB).

PJS714E PJSQINIT ‑ VSAM CONTROL BLOCK ERROR FOR QUEUE DATA SET, RC=rc, REASON=reason

Explanation: A VSAM control block manipulation macro for the PJS Request Queue has failed. In most cases, this is a PJS internal error.

The following values are displayed:

rc is the Control Block Macro Return Code (from register 15).

reason is the Control Block Macro Error Reason Code (from register 0).

PJS741I PJSQMNT ‑ QUEUE DATA SET MAINTENANCE - START

Explanation: The PJS Request Queue Maintenance utility is starting.

Action: Because this message does not signify an error condition, no action is required.

PJS742I PJSQMNT ‑ QUEUE DATA SET MAINTENANCE - END

Explanation: The PJS Request Queue Maintenance utility completed successfully.

Action: Because this message does not signify an error condition, no action is required.

PJS743I PJSQMNT ‑ COMPLETED JOB REQUEST DELETED - REQID=req-ID

Explanation: The displayed PJS Request Queue job request record was in COMPLETE status for more than the time specified by the CMPTIME parameter of the PJSOPT macro.

The following value is displayed:

req-ID is the Request-ID of the deleted job request record.

Action: Because this message does not signify an error condition, no action is required.

PJS744I PJSQMNT ‑ DISABLED JOB REQUEST DELETED - REQID=req-ID

Explanation: The displayed PJS Request Queue job request record was in DISABLED status for more than the time specified by the DISTIME parameter of the PJSOPT macro.

The following value is displayed:

req-ID is the Request-ID of the deleted job request record.

Action: Because this message does not signify an error condition, no action is required.

PJS745I PJSQMNT ‑ ERROR JOB REQUEST DELETED - REQID=req-ID

Explanation: The displayed PJS Request Queue job request record was in ERROR status for more than the time specified by the ERRTIME parameter of the PJSOPT macro.

The following value is displayed:

req-ID is the request-ID of the deleted job request record.

Action: Because this message does not signify an error condition, no action is required.

PJS746I PJSQMNT ‑ UNREFERENCED EVENT DELETED - EVENTID=event-ID

Explanation: The displayed PJS Request Queue Event record was not referenced in any job request record, and was deleted.

The following value is displayed:

event-ID is the event-ID of the deleted Event record.

Action: Because this message does not signify an error condition, no action is required.

PJS747I PJSQMNT ‑ UNREFERENCED OWNER DELETED - OWNERID=owner-ID

Explanation: The displayed PJS Request Queue Owner record had no job request, calendar, or event records, and was deleted.

The following value is displayed:

owner-ID is the owner-ID of the deleted Owner record.

Action: Because this message does not signify an error condition, no action is required.

PJS748I PJSQMNT ‑ UNREFERENCED SPOOL MEMBER DELETED - MEMBER=member

Explanation: The displayed PJS JCL Spool member was not referenced in any job request record, and was deleted.

The following value is displayed:

member is the name of the deleted PJS JCL Spool member.

Action: Because this message does not signify an error condition, no action is required.

PJS749I PJSQMNT ‑ SAVED JCL RECORD COUNT UPDATED FOR JOB REQUEST - REQID=req-ID

Explanation: The PJS JCL Spool Record Count for the displayed PJS Request Queue job request record was updated to reflect the correct number of saved JCL records.

The following value is displayed:

req-ID is the request-ID of the updated job request record.

Action: Because this message does not signify an error condition, no action is required.

PJS750I PJSQMNT ‑ SAVED JCL RECORD COUNT UPDATED FOR OWNER - OWNERID=owner-ID

Explanation: The PJS JCL Spool Record Count for the displayed PJS Request Queue Owner record was updated to reflect the correct number of saved JCL records.

The following value is displayed:

owner-ID is the Owner-ID of the updated Owner record.

Action: Because this message does not signify an error condition, no action is required.

PJS751I PJSQMNT ‑ JCL SPOOL DATA SET COMPRESSED

Explanation: The PJS JCL Spool data set was successfully compressed.

Action: Because this message does not signify an error condition, no action is required.