The PSF Direct Printer Services Subsystem is active.

This message is only for information.

No response is necessary.

No response is necessary.

No response is necessary.

None.

The PSF Direct Printer Services Subsystem identified in this message failed to initialize. If you are using a 3800, until the problem is resolved, the 3800 can be directly allocated only if it is in compatibility mode.

The PSF Direct Printer Services Subsystem is not active.

No response is necessary.

The associated return code issued by the subsystem service routine is given in this message.

If the return code is 12, a GETMAIN failure has occurred. For more information, see PSF for z/OS: Diagnosis.

If the return code is 20, the module accessed is not in SYS1.LINKLIB or a library concatenated to a SYS1.LINKLIB (in LNKLSTxx PARMLIB member). Link-edit the module to SYS1.LINKLIB or to a concatenated library.

Inform your system programmer that this error occurred.

Items 1, 17.

An incorrect response was given to a previous load forms flash or to a thread-to-stacker message.

Processing stops until the operator responds to this message.

No response is necessary.

No response is necessary.

Enter the correct reply. See message APS003A for the correct reply.

None.

(nnnn) is the 3- or 4-digit device number of the printer. The forms flash frame, identified by O= in this message, is the frame specified by the FORMS FLASH keyword on the JCL. B= indicates whether the BURST keyword on the JCL specified yes or no for the burster-trimmer-stacker feature. F= specifies the form used with the job. The setup must be consistent with the JCL specified for this print request.

This message identifies one or more of these parameters. If one of these parameters is not specified here, it was not specified on the JCL.

Processing stops until the operator responds to this message.

No response is necessary.

No response is necessary.

Enter one of the following replies, where nn is the number the system specified when issuing this message:

• Rnn,U. This reply returns a hexadecimal code verifying either that the requested setup has been completed, or that the setup commands are to be ignored if the setup cannot be completed.
• Rnn,CANCEL. This reply causes a subsystem output block (SSOB) return code of X'04' to be passed back to the data management open routine. Return code X'04' indicates that the print request is canceled.

None.

The PSF Direct Printer Services Subsystem initialization parameter specified in the IEFSSNxx PARMLIB member is not valid. A parameter with more than 8 characters or non-numeric characters causes this message.

The PSF Direct Printer Services Subsystem continues to initialize.

No response is necessary.

Correct the initialization parameter specified in the IEFSSNxx PARMLIB member. For information about correcting the initialization parameter in the IEFSSNxx PARMLIB member, see PSF for z/OS: Diagnosis.

Inform your system programmer that this error occurred.

Item 1.

PSF initialization failed, for the reason given in one of the following reason codes:

04

GETMAIN for DPSS control block failed.

08

SJFREQ FINDSWB failed.

0C

SJFREQ retrieve failed.

10

GETMAIN for SSXB failed.

14

APSAFSA attach failed.

18

PSF abended.

1C

Operator specified cancel in response to message APS003A.

The print job is not started or is discontinued at its current location.

No response is necessary.

If the problem is a GETMAIN failure, increase the REGION size parameter. If the problem is a SJFREQ failure, follow the procedures described in PSF for z/OS: Diagnosis before contacting the IBM® Support Center. If the problem is an attach failure, check to see that PSF is accessible to DPSS. For an operator cancel, no response is necessary.

For an operator cancel, have the user resubmit the print request, and do not cancel it.

Items 1, 9, 17.

PSF initialization failed because a request was made to attach more FSAs than the maximum specified in SYS1.PARMLIB.

The print job is not started.

No response is necessary.

Either raise the maximum FSA number in SYS1.PARMLIB, or have the user resubmit the job when Direct Attach is not at capacity.

Inform your system programmer that this error occurred.

None.

The Message Exit requested ending the job.

The job stops processing.

Notify your system programmer of this error.

Evaluate why the Message Exit ended the job and take any appropriate action.

No response is necessary.

None.

An exception occurred for which the typical PSF recovery is to resend pages to the printer, which might have already printed. The Printer Inventory or Exit 7 specified that this recovery should not be performed.

PSF ends the current print job.

Resubmit the print job to reprint the incomplete portion of the print data, if needed.

No response is necessary.

No response is necessary.

Items 2, 3, 8.

An incorrect request was returned by the logical record processing exit 04 or 14.

The original record is processed.

Inform your system programmer that this error occurred.

Verify that recent changes have not caused an error in the logical record processing exit.

No response is necessary.

Items 1, 2, 3, 17, 19, 26.

PSF was incorrectly started with an MVS™ START command entered from a system console.

PSF ends without establishing communication with the Job Entry Subsystem (JES).

No response is necessary.

No response is necessary.

Use the appropriate JES command to start the device or writer. For the appropriate JES command, see the JES commands publication for the level of JES you are using.

Items 1, 26.

The PSF Functional Subsystem Application (FSA) initialization was stopped by the PSF subcomponent identified in this message.

The device does not start.

No response is necessary.

To determine an appropriate response, see the specific console message issued by the PSF subcomponent that failed to initialize.

To determine an appropriate response, see the specific console message issued by the PSF subcomponent that failed to initialize.

Items 1, 17, 19, 26.

PSF received the functional subsystem interface (FSI) abend request to stop the functional subsystem application (FSA).

PSF abends the FSA.

No response is necessary.

To determine an appropriate action, check the MVS console for any JES commands issued to the FSS that might have caused JES to request that the FSS be dumped. Save the memory dump for IBM Support Center use.

Inform your system programmer that this error occurred.

Items 1, 9, 17, 19, 26.

PSF received the functional subsystem interface (FSI) abend request to stop the functional subsystem (FSS).

PSF abends the PSF FSS address space.

No response is necessary.

To determine an appropriate action, check the MVS console for any JES commands issued to the FSS that might have caused JES to request that the FSS be dumped. Save the memory dump for IBM Support Center use.

Inform your system programmer that this error occurred.

Items 1, 9. 17, 19, 26.

This message is a null message. It contains no text generated by PSF; it is simply a carrier for a JES2 message or a JES3 message. If the operator entered a Forward Space command, processing of the data set might be stopped while forward spacing, in which case no end messages are printed.

This message is only for information.

The printed output might be acceptable. If any pages were duplicated or skipped, you might want to resubmit the print request. If the error persists, consult your system programmer.

For more information, see the JES messages publication for the level of JES you are using.

Inform your system programmer that this error occurred.

None.

Processing of the output data set was stopped because of an error, but the disposition of the data set was not changed for one of the following reasons:

• HONOR PRTERROR IS NOT INITIALIZED. The Error disposition supported option in the Printer Inventory does not specify Yes or the PRINTDEV initialization statement for this printer does not specify PRTERROR=HONOR.
• A PSF EXIT REQUESTED THE DATA SET BE HELD. PSF installation exit 6 or 7 specified that the data set should be held.
• MANDATORY PRINT LABELING IS IN EFFECT. The RACF® (Resource Access Control Facility) class PSFMPL is active on the system.

The default disposition for the error is taken, or, if an exit requested it, the data set is held.

If honor PRTERROR is not initialized, ask your system programmer to initialize it.

If users are to be allowed to set the error disposition, set Error disposition support to Yes in the Printer Inventory or add PRTERROR=HONOR on the PSF PRINTDEV statement for the printer.

No response is necessary.

Items 2, 3, 12, 13.

An I/O error was detected while the data set was being read from the Job Entry Subsystem (JES) spool.

Processing of the data set ends.

Resubmit the print request.

To determine an appropriate action, see the JES I/O error message.

Request that the user resubmit the job.

Items 1, 3, 17, 19, 26.

PSF detected a Job Entry Subsystem (JES) record too long to process. The maximum length for a PSF record is 32,768 bytes.

The partial record is processed, and processing for the current data set ends. The data set is requeued and held.

Inform your system programmer that this error occurred.

Ensure that the maximum record length for JES does not exceed the maximum record length for PSF.

After the error has been corrected, release the data set. For the appropriate command to release the data set, see the JES commands publication for the level of JES you are using.

Items 1, 3, 17, 19, 26.

While composing a spanned record, PSF detected the start of another spanned or nonspanned record. The error is caused by the Job Entry Subsystem (JES).

The partial record is processed, and processing for the current data set ends. The data set is requeued and held.

Inform your system programmer that this error occurred.

To determine an appropriate action, see the JES I/O error message.

After the error has been corrected, release the data set. For the appropriate command to release the data set, see the JES commands publication for the level of JES you are using.

Items 1, 3, 17, 19, 26.

PSF reached the end of the data set without finding the end of a spanned record. The error is caused by the Job Entry Subsystem (JES).

The partial record is processed. The data set is requeued and held.

Inform your system programmer that this error occurred.

To determine an appropriate action, see the JES I/O error message.

After the error has been corrected, release the data set. For the appropriate command to release the data set, see the JES commands publication for the level of JES you are using.

Items 1, 3, 17, 19, 26.

The first spanned record in the data set is not the beginning of a spanned record.

The partial spanned record is processed. Processing of the current data set ends. The data set is requeued and held.

Inform your system programmer that this error occurred.

To determine an appropriate action, see the Job Entry Subsystem (JES) I/O error message.

After the error has been corrected, release the data set. For the appropriate command to release the data set, see the JES commands publication for the level of JES you are using.

Items 1, 3, 17, 19, 26.

PSF reached the end of a data set before finding a nonresource record containing data rather than a resource. A nonresource record is a record from a line-data or Mixed Object Document Content Architecture (MO:DCA) data file.

Processing for the current data set is ended.

Ensure that the data set contains line-data records or MO:DCA data, and then resubmit the job.

No response is necessary.

No response is necessary.

Items 1, 3, 17, 19, 26.

PSF attempted to restart a data set from a Job Entry Subsystem (JES) checkpoint, but the data set was empty.

Processing for the data set is ended.

No response is necessary.

If you feel this message was issued in error, obtain a PSF memory dump on the message and see problem determination item 27.

Inform your system programmer that this error occurred.

Items 1, 3, 17, 19, 26, 27.

An abend has occurred that PSF considers a candidate for restart processing. The abend condition is described in the preceding APS050I message.

All active data sets are released, and PSF attempts to restart. PSF does not produce a memory dump unless the abend code was specified on the Dump: Message ID option in the Printer Inventory or the DUMP parameter of the PRINTDEV statement in the PSF startup procedure. If the restart is successful, message APS057I is issued, and PSF restarts by requesting a new data set from JES. If the restart is unsuccessful, PSF issues message APS053I and then ends.

No response is necessary.

If the restart is successful, but the abend condition is frequently producing a restart, you can specify the abend reason code on the DUMP parameter in the PSF startup procedure to generate a conditional dump. For more information about the DUMP parameter, see PSF for z/OS: Diagnosis.

Inform your system programmer that this error occurred.

Items 1, 26, 27.

An I/O error occurred previously on this data set, or an operator command was entered at a time when insufficient information was available to reposition accurately. Repositioning was done, and either it was successful, or a page was duplicated.

Page nnn is a relative page number from the beginning of your data set. The relative page number includes header pages, message pages, and multiple transmissions of the data set.

Processing of the data set continues. This message was issued to the JES operator console and was appended to the message data set.

Examine your output for duplicate pages.

No response is necessary.

No response is necessary.

None.

PSF attempted to restart the current data set while the printer was directly attached. Restart processing is not supported when a printer is being used in direct-printing mode.

Processing for the current data set ends.

No response is necessary.

Examine the accompanying PSF messages, if any, to determine why PSF attempted to restart the data set.

Examine the accompanying PSF messages, if any, to determine why PSF attempted to restart the data set.

Items 1, 2, 3, 4a, 8, 9, 12, 17.

PSF received the functional subsystem interface (FSI) abend request to stop the PSF Functional Subsystem Application (FSA).

PSF abends the FSA.

No response is necessary.

To determine an appropriate action, check the MVS console for any JES commands issued to the FSA that might have caused JES to request that the FSA be dumped. Save the memory dump for IBM Support Center use.

Inform your system programmer that this error occurred.

Items 1, 17, 19, 26.

The PSF ESTAE routine received a return code of X'04' after returning from the system's SVC dump routine. This indicates that a partial memory dump was created.

Abend processing continues.

No response is necessary.

Verify your SVC dump method, and then see z/OS MVS Diagnosis: Tools and Service Aids.

Inform your system programmer that this error occurred.

Items 1, 26.

A Stop Device functional subsystem interface (FSI) order with the dump option was received. PSF received a return code of X'08' from the system's SVC dump routine.

Device termination continues.

No response is necessary.

Verify your SVC dump method, and then see z/OS MVS Diagnosis: Tools and Service Aids.

Inform your system programmer that this error occurred.

Items 1, 19, 26.

The PSF ESTAE routine received a return code of X'08' from the system's SVC dump routine. This indicates that an SVC dump was unsuccessful.

Abend processing continues.

No response is necessary.

If you receive reason code '0B'X, Dump Analysis Elimination (DAE) has suppressed the memory dump because a dump of the same nature had occurred earlier. Check your organization’s DAE data set for a symptom string matching the dump that was just created.

If you receive reason code '05'X, verify your SVC dump method, and then see z/OS MVS Diagnosis: Tools and Service Aids.

Inform your system programmer that this error occurred.

Items 1, 26.

PSF attempted to dynamically allocate the device with the address identified in this message. PSF failed for one of the following reasons:

• The device was already allocated (DYNALLOC error code = X'0214').
• The operator denied the device allocation (DYNALLOC error code = X'0484').
• The specified ddname was already allocated (DYNALLOC error code = X'0410').

The printer does not start.

No response is necessary.

No response is necessary.

Before starting the device or writer, verify that the device is not allocated to another address space. If the allocation was denied by the operator, ensure that the device or writer that requires this device is not started. To interpret the DYNALLOC error code, see z/OS MVS Programming: Authorized Assembler Services Guide.

Items 1, 19, 26.

PSF attempted to write a Systems Management Facility (SMF) Type 6 record by use of the SMFWTM macro. The SMFWTM macro return code indicated that the SMF Type 6 record was not written.

If mandatory print labeling is active, PSF abends. Otherwise, processing continues.

No response is necessary.

To interpret the SMFWTM macro return codes, see the System Management Facility publication for your operating system.

Inform your system programmer that this error occurred.

Item 1.

During the processing of the SMF Type 6 record, a nonzero return code was received when the time of day and the date were being established (SVC 11).

If mandatory print labeling is active, PSF abends. Otherwise processing continues, and the record is written without these values.

No response is necessary.

Determine the cause of the SVC 11 failure.

Inform your system programmer that this error occurred.

Item 1.

The PSF ESTAE routine detected a PSF abend condition.

Depending on the error condition, PSF automatically restarts the printer, stops processing for the printer, or stops the PSF address space. A subsequent message from PSF tells the operator which action was taken.

An ESTAE routine creates an SVC dump, unless a dump was provided by an earlier routine or the functional subsystem interface (FSI) requested that no dump be created.

Inform your system programmer that this error occurred.

Examine the accompanying PSF message to determine the appropriate response.

To interpret system completion codes X'024', X'027', and X'0A6', see System completion codes and PSF abend reason codes.

Inform your system programmer that this error occurred.

Items 1, 3, 9, 17, 19, 26.

The PSF ESTAE issued this message as part of processing a PSF abend condition. Message APS050I or APS055I should have also been issued as part of the PSF abend processing. The ESTAE routine should have provided an SVC dump.

Abend processing continues.

Inform your system programmer that this error occurred.

Use the information provided in message APS050I or APS055I to determine an appropriate response. Save the memory dump for IBM Support Center use.

Inform your system programmer that this error occurred.

Items 1, 3, 9, 17, 19, 26.

The installed version of the Job Entry Subsystem (JES) does not support mandatory print labeling.

The data set being processed at the time of the error was returned to the Job Entry Subsystem (JES) to place on the HOLD queue.

No response is necessary.

Install the correct release of JES if mandatory print labeling is required.

Inform your system programmer that this error occurred.

Items 1, 3.

PSF was unable to restart following the abend reported in the previous APS050I message. The original abend is processed, and a memory dump is created.

Abend processing continues.

No response is necessary.

Use the information provided in the APS050I message that reported the original abend to diagnose the problem.

Inform your system programmer that this error occurred.

Items 1, 17, 26, 27.

PSF successfully completed an SVC dump to a SYS1.DUMPnn data set.

Abend processing continues.

No response is necessary.

Save the memory dump for IBM Support Center use.

Inform your system programmer that this error occurred.

1, 3, 9, 17, 19, 26.

The PSF ESTAE routine is unable to continue, for one of the following reasons:

• The abend reason code was not issued by PSF.
• The abend reason code was not stored in the function subsystem (FSB) control block.
• The FSB control-block address was incorrect.

Abend processing continues.

Inform your system programmer that this error occurred.

The contents of the registers at the time of the abend are provided in the SVC dump and register 15 might contain a PSF abend reason code. Save the dump for IBM Support Center use. To interpret the dump, see PSF for z/OS: Diagnosis. To interpret the system completion code, see the publication containing system messages for your operating system.

Inform your system programmer that this error occurred.

Items 1, 3, 9, 17, 19, 26.

SYSAREA = YES was specified for a printer that does not support security functions. This JCL parameter was on the OUTPUT statement for the job.

PSF releases the current data set back to JES and requests that it be held by the system.

If security page labeling is required, submit the print request to a printer that supports security functions. If security labeling is not required, change the OUTPUT JCL statement to remove the SYSAREA keyword.

No response is necessary.

No response is necessary.

Items 1, 3.

PSF has successfully completed abend restart processing and continues processing. A new job is requested from JES.

Processing continues.

No response is necessary.

No response is necessary.

The output from the data set that was printing when the abend occurred might need to be discarded, because the entire data set might be printed again after the restart. However, the data set that was printing when the abend occurred is not necessarily the next one to print after PSF restarts.

Items 1, 26, 27.

PSF received a "Not Ready" status from the printer as it was ending the IPDS session for one of these reasons:

• PSF received a STOP device order from JES.
• The disconnect interval (DISCINTV) expired.
• The release interval (RELINTV) expired.

Until the printer is made "Ready" and a new session is started with the printer, device status queries might not reflect the true status of the printer.

PSF does one of these:

• Ends the session with the printer if JES issues a STOP device order.
• Waits for more work if the disconnect interval expired.
• Waits for the acquire interval to expire.

None.

None.

The status of this printer might not be accurate until the device is made "Ready" and PSF starts a new session.

None.

Mandatory Print Labeling has been requested in direct-printing mode, but it is not allowed in that mode.

PSF issues message APS005I and then abends.

Inform your system programmer that this error occurred.

Deactivate class PSFMPL by using the Resource Access Control Facility (RACF). For information on how to do this, see the RACF publications.

Inform your system programmer that this error occurred.

Items 1, 3.

While processing the job, PSF detected an error that makes printing the job in a secure environment impossible.

PSF releases the current data set back to JES and requests that it be held by the system.

No response is necessary.

To determine an appropriate response, see the specific error conditions described in the accompanying messages.

Inform your system programmer that this error occurred.

1, 2, 3, 8, 17.

The print request identified in the message contained a node specified with the NOTIFY keyword that the system does not recognize as valid.

The print request was processed, but the node identified as not valid prevents the user from being notified that the processing of the print request has been completed.

Notify the individuals directly that processing of the print request has been completed. If the print request is to be resubmitted for printing, correct the incorrect node ID.

No response is necessary.

No response is necessary.

None.

Processing of the print request identified in the message has completed successfully. The print-job submitter specified that this message should be sent to the user IDs specified in the NOTIFY keyword in the JCL for the print request. When the printer is connected to PSF by use of the Distributed Print Function (DPF) of PSF, this message indicates only that PSF has completed its processing of the print request. The final disposition of the print request is controlled by DPF.

PSF continues processing.

The printed output is available at the printer, unless the printer is connected to PSF by use of DPF.

No response is necessary.

No response is necessary.

None.

Processing of the print request identified in the message has been canceled. The print-job submitter specified that this message should be sent to the user IDs specified in the NOTIFY keyword in the JCL for the print request.

PSF continues processing with the next print request.

Examine the PSF messages in the printed output to determine why the print request was canceled.

No response is necessary.

No response is necessary.

None.

Processing of the print request identified in the message has been interrupted by the operator. The print-job submitter specified that this message should be sent to the user IDs specified in the NOTIFY keyword in the JCL for the print request.

The print request was returned to the Job Entry Subsystem (JES) and can be restarted by the operator.

Examine the PSF messages in the printed output to determine why the print request was interrupted, or consult your system operator.

No response is necessary.

No response is necessary.

None.

Processing of the print request identified in the message has completed unsuccessfully. The print-job submitter specified that this message should be sent to the user IDs specified in the NOTIFY keyword in the JCL for the print request.

See the accompanying messages for the system action that was taken.

Examine the PSF messages in the printed output to determine the cause of the error.

No response is necessary.

No response is necessary.

None.

PSF processing of the print request identified in the message has determined that the data set is not printable. The print-job submitter specified that this message should be sent to the user IDs specified in the NOTIFY keyword in the JCL for the print request.

The print request was returned to the Job Entry Subsystem (JES) to be placed on the HOLD queue with a PSF message ID.

Examine the PSF messages in the printed output to determine why the print request was unprintable.

No response is necessary.

No response is necessary.

None.

The submitter of this print job has not been given authority to send the message to the user on the receiving system.

PSF continues processing the notify request.

Inform your system programmer that this error occurred.

Determine whether the user should be authorized to send the message (defined in the RACF SMESSAGE class). If the user should be authorized, use RACF to give the user the needed authorization. For information on how to do this, see z/OS Security Server RACF Security Administrator’s Guide for your operating system.

No response is necessary.

Items 1, 2, 29.

A notify request was unsuccessful; the decimal code indicates the cause of the failure.

Decimal
Code

Explanation

04

PSF logic error. Message truncated.

08

Exit canceled notify request. A system installation exit (not a PSF exit) has canceled the notify request. Inform your system programmer that this error occurred.

12

PSF logic error. No user ID specified.

20

PSF logic error. Notify extension ID is not valid.

24

PSF logic error. Notify version is not valid.

28

No storage for request. The Job Entry Subsystem (JES) cannot obtain enough storage in subpool 231 to satisfy the request. The system programmer must determine why insufficient storage is available.

36

PSF logic error. Error in message specification.

PSF continues processing the notify request.

Inform your system programmer that this error occurred.

For codes “08” and “28”, see the explanation for the code. For all other codes, follow the procedures described in PSF for z/OS: Diagnosis before consulting the IBM Support Center.

No response is necessary.

Items 1, 29.

A notify request was unsuccessful; the decimal code indicates the cause of the failure.

Decimal
Code

Explanation

12

PSF logic error. No notify extension found.

PSF continues processing the notify request.

Inform your system programmer that this error occurred.

Follow the procedures described in PSF for z/OS: Diagnosis before consulting the IBM Support Center.

No response is necessary.

Item 29.

A notify request was unsuccessful; the decimal code indicates the cause of the failure.

Decimal
Code

Explanation

04

PSF logic error. Subsystem does not support this function.

08

Subsystem exists, but is not up. Restart the Job Entry Subsystem (JES).

12

PSF logic error. Subsystem does not exist.

16

Function not completed; disastrous error. Determine cause of error from dump.

20

PSF logic error. Logical error (incorrect subsystem option block [SSOB] format, incorrect length, or some other logical error).

PSF continues processing the notify request.

Inform your system programmer that this error occurred.

For codes “08” and “16”, see the explanation for the code. For all other codes, follow the procedures described in PSF for z/OS: Diagnosis before consulting the IBM Support Center.

No response is necessary.

Items 1, 29.

Resolving the error described by the preceding message requires the assistance of your system programmer.

PSF continues processing the notify request.

Consult your system programmer for assistance. Inform your system programmer that this error occurred.

See the error codes in the preceding message.

No response is necessary.

Items 1, 2, 3.

The conditional processing information that is used in printing this data set was too large to fit into the checkpoint record that PSF had previously written to JES. This can happen when the page definition specifies CONDITION commands by use of the WHEN CHANGE parameter, which causes large amounts of data to be tested. If too many of the WHEN CHANGE type of conditions are specified, the checkpoint record becomes too large to write to JES. PSF must then write the checkpoint record to JES without any of the conditional processing information.

Because this data set needs the conditional processing information in order to restart from a checkpoint, but the JES checkpoint record given back to PSF does not contain this information, PSF must restart this data set from the beginning. This allows the conditional processing information to be rebuilt, and the data set prints correctly.

PSF issues this message to the operator console and the message data set, and continues processing from the beginning of the data set.

Examine your output for duplicate pages.

No response is necessary.

If you know which page the printing should restart on, issue a forward space command.

None.

The interrupt message page that PSF inserts in your printed output was suppressed because the Printer Inventory or Exit 7 has requested that no interrupt message page be printed.

Processing continues without the interrupt message page being printed.

If you feel that this message has been issued incorrectly, ask your system programmer to check the target device, the Printer Inventory and Exit 7 for correctness.

Ensure that the target device is appropriate. For microfilm devices, interrupt message pages are suppressed regardless of what functions were requested in PSF Exit 7 or the Printer Inventory.

For non-microfilm devices, ensure that the Interrupt message page value is set correctly in the Printer Inventory or XTP7IPSU is set correctly by Exit 7.

No response is necessary.

Items 1, 3.

Virtual storage could not be acquired above the line for all required message data set redirection control blocks.

The user data set completed printing, but the associated message data set was lost. The data set was released as incomplete for future reprinting. The FSA printing the data set was stopped with abend reason code 0335.

Inform your system programmer that this error occurred.

Increase the REGION parameter on the procedure used to start PSF.

Inform your system programmer that this error occurred.

Items 1, 9, 17, 19.

An unsuccessful attempt was made to use an SVC 99 instruction to perform the dynamic allocation of the redirected message data set.

The user data set completed printing, but the associated message data set was lost. The data set was released as incomplete for future reprinting. The FSA printing the data set was stopped with abend reason code 0335.

Inform your system programmer that this error occurred.

Use the return code and reason code to determine the cause of the error and an appropriate response. For information about the SVC 99 return and reason codes, see z/OS MVS Diagnosis: Tools and Service Aids.

Inform your system programmer that this error occurred.

Items 1, 4, 9, 17, 19.

An OPEN macro, which results in an SVC 19, was issued to open the redirected message data set for output. After returning from the OPEN macro, PSF discovered that the data control block (DCB) had not been opened.

The user data set completed printing, but the associated message data set was lost. The data set was released as incomplete for future reprinting. The FSA printing the data set was stopped with abend reason code 0335.

Inform your system programmer that this error occurred.

See the additional console messages associated with this error.

Inform your system programmer that this error occurred.

Items 1, 4, 9, 17, 19.

A CLOSE macro, which results in an SVC 20, was issued to close the redirected message data set. After returning from the CLOSE macro, PSF discovered that the data control block (DCB) had not been closed.

The user data set completed printing, but the associated message data set was lost. The data set was released as incomplete for future reprinting. The FSA printing the data set was stopped with abend reason code 0335.

Inform your system programmer that this error occurred.

See the additional console messages associated with this error.

Inform your system programmer that this error occurred.

Items 1, 4, 9, 17, 19.

Message data set redirection was requested by specifying PIMSG=NO on the OUTPUT statement for the message data set in the startup procedure, but one of these occurred:

• The operating system does not support the functions required for message data set redirection.
• Message data set redirection was requested while using direct-printing mode.

The request for message data redirection was ignored. Any error messages were printed with the associated user data set.

No response is necessary.

Either correct the problem described by the Explanation section, or do not request message data set redirection (do not specify PIMSG on the message data set OUTPUT statement in the startup procedure or specify PIMSG=YES).

Inform your system programmer that this error occurred.

Items 1, 9, 17, 27.

XTP7IHIB was set to off for the first data set of the job, but PSF Exit 7 set it on for a subsequent step of the job. PSF must perform the same level of recovery for the entire job.

Recovery is allowed for the entire job.

Notify your system programmer.

Change PSF Exit 7 so that it sets XTP7IHIB the same way for each data set of a job.

No response is necessary.

Items 2, 3, 8.

PSF Exit 7 set XTP7IHIB to on for the first data set of the job but not for a subsequent step of the job. PSF must perform the same level of recovery for the entire job.

Recovery is inhibited for the entire job.

Notify your system programmer.

Change PSF Exit 7 so that it sets XTP7IHIB the same way for each data set of a job.

No response is necessary.

Items 2, 3, 8.

A get record request on the Functional Subsystem Interface (FSI) was rejected.

PSF ends with system completion code 024 and an abend reason code 0130.

Notify your system programmer.

Contact IBM service and supply the GLRFLGS1 indicated.

Notify your system programmer.

None.

The information for the sheet collection finishing at the copy group level, which is used in printing this data set, was too large to fit into the checkpoint record that PSF had previously written to JES. This can happen when too many finishing operations are nested inside a copy group and the checkpoint record becomes too large to write to JES. PSF must then write the checkpoint record to JES without any of this finishing information.

Because this data set needs the sheet collection finishing information at the copy group level in order to restart from a checkpoint, but the JES checkpoint record given back to PSF does not contain this information, PSF must restart this data set from the beginning. This lets the finishing information be rebuilt, and the data set prints correctly.

PSF issues this message to the operator console and the message data set, and continues processing from the beginning of the data set.

Examine your output for unfinished and duplicate pages.

No response is necessary.

If you know which page the printing should restart on, issue a forward space command.

None.

The UNICODE value in the PARM keyword of the EXEC JCL statement is no longer used; however, if it is specified, it must be UNICODE. If not specified, PSF or AFP Download Plus is always started with Unicode support.

PSF or AFP Download Plus continues processing with Unicode support.

No response is necessary.

Correct the PARM information in the JCL. For the correct format of the EXEC statement, see PSF for z/OS: Diagnosis or PSF for z/OS: AFP Download Plus.

Inform your system programmer that this error occurred.

Item 1.

A value in the PARM keyword of the EXEC JCL statement specifies the type of tracing to be performed. The value can be FULL, INTR, IPDS, LIMIT, or SYNC.

PSF or one of its features continues processing and uses the default value of INTR to produce an internal trace.

No response is necessary.

Correct the PARM information in the JCL. For the correct format of the EXEC statement, see &apsd000t;, &apsp000t;, or PSF for z/OS: Download for z/OS.

Inform your system programmer that this error occurred.

Item 1.

A value in the PARM keyword of the EXEC JCL statement indicates whether an operator response is required to initialize the operator interface for PSF or a PSF feature. The value can be PROMPT or NOPROMPT.

PSF or one of its features continues processing and uses the default value of NOPROMPT.

No response is necessary.

Correct the PARM information in the JCL. For the correct format of the EXEC statement, see &apsd000t;, &apsp000t;, or PSF for z/OS: Download for z/OS.

Inform your system programmer that this error occurred.

Item 1.

A value in the PARM keyword of the EXEC JCL statement indicates how much memory is allocated for an internal trace. Valid values are from 1 to 999.

PSF or one of its features continues processing and uses one of these values to determine how much memory is allocated:

• If the value is not an integer or is less than 1, the default value of 32 is used.
• If the value is an integer greater than 999, the value of 999 is used.

No response is necessary.

Correct the PARM information in the JCL. For the correct format of the EXEC statement, see &apsd000t;, &apsp000t;, or PSF for z/OS: Download for z/OS.

Inform your system programmer that this error occurred.

Item 1.

A value in the PARM keyword of the EXEC JCL statement specifies the name of a TCP/IP address space; however, it was greater than eight characters in length.

PSF or AFP Download Plus continues processing and uses the default name of TCPIP.

No response is necessary.

Correct the PARM information in the JCL. For the correct format of the EXEC statement, see &apsd000t; or &apsp000t;.

Inform your system programmer that this error occurred.

Item 1.

A value in the PARM keyword of the EXEC JCL statement specifies the PSF Notify Subtask Trace (NST) data set name or Download for z/OS® FSS trace output data set name (FSSddname) that is defined in a DD statement. The value must be one to eight characters in length in order for PSF or AFP Download Plus to be started with NST tracing, or Download for z/OS to be started with FSS tracing.

PSF, AFP Download Plus, or Download for z/OS continues processing without activating tracing.

No response is necessary.

Correct the PARM information in the JCL. For the correct format of the EXEC statement, see &apsd000t;, &apsp000t;, or PSF for z/OS: Download for z/OS.

Inform your system programmer that this error occurred.

Item 1.

The initialization of the Download for z/OS exit routine failed because insufficient length was specified in the APSUCOM table, the APSUCOM module could not be located, or a BLDL macro failed. Download for z/OS detected this error. See PSF for z/OS: Download for z/OS for more information about this feature.

Processing continues without the installation exit.

No response is necessary.

Evaluate any changes made to the APSUCOM module (static table), to the exit routine, or to the methods used to establish the tables or routines in the system. Other messages might contain BLDL macro return and reason codes.

Inform your system programmer that this error occurred.

Items 1, 3.

A nonzero return code was received from the invocation of CEEPIPI to initialize for subroutines. Return codes associated with this message are:

Return
Code

Explanation

04

The function code is not valid.

08

Some of the addresses in the table were not resolved. This can occur if a LOAD failure was encountered, a routine within the table was not generated by a Language Environment-conforming HLL, or a C or PL/I routine within the table was not retrievable.

12

Storage for the preinitialization environment could not be obtained.

16

CEEPIPI was called from an active environment.

For more information on this invocation of CEEPIPI and its return codes, see z/OS Language Environment Programming Guide.

PSF processing ends abnormally with a system completion code 024 and abend reason code 0A57 or 0A5D.

No response is necessary.

If the problem cannot be diagnosed from the return code, contact the IBM Support Center.

Inform your system programmer that is error occurred.

Items 1, 17, 19, 27.

A nonzero return code was received from the invocation of CEEPIPI to add an entry. Return codes associated with this message are:

Return
Code

Explanation

04

The function code is not valid.

08

CEEPIPI was called from a Language Environment-conforming routine.

12

The routine did not contain a common runtime environment PPA style prologue. The PIPI table was not updated, and the routine_entry is set to the address of the loaded routine. This might have occurred for one of these reasons:

• An installation exit in assembler has been given a C exit name and link-edited like an installation exit in C.
• An installation exit in assembler has been named with a C exit name and has been link-edited like an installation exit in assembler.
• The main function name in the C exit is not the same as the load module name.

16

The token is not valid.

20

The routine_name contains only blanks and the routine_entry was zero. The PIPI table was not updated.

24

The routine_name was not found or there was a load failure. The PIPI table was not updated.

28

The PIPI table is full. No routine was added to the table, nor was any routine loaded by Language Environment®.

For more information on this invocation of CEEPIPI and its return codes, see z/OS Language Environment Programming Guide.

PSF processing stops abnormally with a system completion code 024 and abend reason code 0A58 or 0A5E.

No response is necessary.

Make sure that any assembler installation exits are named correctly and are link-edited as assembler exits. Make sure that the main function name of any C installation exit is the same as the load module name. If the exits are correct and the problem cannot be diagnosed from the return code, contact the IBM Support Center.

Inform your system programmer that this error occurred.

Items 1, 17, 19, 27.

PSF is trying to load an assembler installation exit but its C version has already been loaded.

Processing continues without the assembler version of the installation exit.

No response is necessary.

You have both a C version and an assembler version of the same exit. If you would like to use the assembler version, delete the C version of the exit.

Inform your system programmer that this error occurred.

Item 1.

An installation exit in C has been found, but the operating system version you are using does not support installation exits in C.

Processing continues without the installation exits that are written in C. All assembler exits are used.

No response is necessary.

If you wish to use installation exits written in C, install the current version of z/OS.

Inform your system programmer that this error occurred.

Item 1.