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

Error message within the printer file

I have iSeries V5R3, and I'm using BRMS. I have a CL in a control group that does all my printing. For some reason in my last three backups, with two different control groups I'm getting the message, "Reached Maximum number of spooled records for file QPDSPMSG in library QSYS" and it hangs the backup. I have called IBM support and they just tell me how to change the setting in my CL to answer the message with a "NOMAX" response or put a monitor in the CL for that message. They never tried to find what the cause was. Any advice would be appreciated.

The default values for printer file QSYS/QPDSPMSG is:

Spooling description

  Spooled output queue  . . . . . . . . . . . : OUTQ       *JOB      
  Max spooled output records  . . . . . . . . : MAXRCDS        100000
  Spooled output schedule . . . . . . . . . . : SCHEDULE   *FILEEND  
  Copies  . . . . . . . . . . . . . . . . . . : COPIES       1  
Apparently the number of records being processed by this printer file within your backup process is more that 100,000. This is why you have been getting the error. If you changed this printer file as follows, the error message you have been getting won't occur anymore:


The "danger" in doing this is that a job could theoretically encounter programming problems resulting in it getting into a "loop" while printing to QPDSPMSG. If this happens with the *NOMAX setting, it will continue to create output until system storage is completely used up. This is not good, because your system would shut down! If this is a concern, then you may want to just increase the size value for MAXRCDS to something like 1,000,000 instead of using *NOMAX.


Visit the ITKnowledge Exchange and get answers to your backup & recovery questions fast.

Search400.com's targeted search engine: Get relevant information on backup & recovery.

Check out this Search400.com Featured Topic on 30 backup/recovery tips in 30 minutes .

Dig Deeper on Past Releases

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.