Q
Problem solve Get help with specific problems with your technologies, process and projects.

Messages and spool hanging up SAVLIB jobs when OUTPUT(*PRINT) is specified

Override QPSAVOBJ to eliminate messages hanging up SAVLIB jobs when utilizing the OUTPUT(*PRINT) command.

Would I insert OVRPRFT before or after my save command example below?

OVRPRTF    FILE(QSYSPRT) MAXRCDS(*NOMAX)

LIBSAVE:    SAVLIB     LIB(*ALLUSR) DEV(TAP01) ENDOPT(*LEAVE) +

                     SAVACT(*SYNCLIB) SAVACTMSGQ(QSYS/QSYSOPR) +

                     ACCPTH(*YES) OUTPUT(*PRINT)
The save generates a huge number of spool and the job hangs until *NOMAX can be responded to in QSYSOPR.
When OUTPUT(*PRINT) is specified for a SAVLIB command on my V5R4 system, the print file used is QPSAVOBJ, not QSYSPRT. Overriding QPSAVOBJ should eliminate the message that has been hanging up your SAVLIB job.

As an alternative, you might want to try using the OUTPUT(*OUTFILE) value which will place all the SAVLIB information...

into a database file. It could make checking the SAVE information much easier.

This was last published in January 2009

Dig Deeper on Printing on iSeries

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchDataCenter

Close