Ansicht
Dokumentation

CPF2526 - Job message queue for &3/&2/&1 can not be extended. Job ended. ( OS/400 )

CPF2526 - Job message queue for &3/&2/&1 can not be extended. Job ended. ( OS/400 )

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF2526
Job message queue for &3/&2/&1 can not be extended. Job ended.

Message Long Text :

Cause . . . . . : The size of the job message queue for &3/&2/&1 reached the maximum size. The maximum size is defined in the JOBMSGQMX value of the job description used by the job. When the job message queue becomes full, the job attribute, JOBMSGQFL, identifies the action to take.
Recovery . . . : Do the following:
- Look at the messages in the job message queue to determine why the job message queue has become full. You can do this by using the Display Job Log (DSPJOBLOG) command and specifying &3/&2/&1 for the JOB parameter. If an IPL has been done after this problem occurred the job message queue may not be found. If the job log output parameter (LOGOUTPUT) for the job was set to *PND, then try using the Work with Job Log (WRKJOBLOG) CL command to view the job log.
- If JOBMSGQFL job attribute is *NOWRAP, increase the maximum size of a job message queue or allow a job message queue to wrap. This can be done by specifying the JOBMSGQMX or JOBMSGQFL parameters on the following commands: Create job description (CRTJOBD) command, change job description (CHGJOBD) command, submit job (SBMJOB) command, or batch job (//BCHJOB) command. If the JOBMSGQMX and JOBMSGQFL parameters are not specified on those commands, the value to use for the job is taken from the QJOBMSGQMX and QJOBMSGQFL system values.
- Start the job again to get a new job message queue.
Technical description . . . . . . . . : A job message queue could become full with messages that do not appear in the job log, such as type *STATUS messages. In this situation, the job is ended regardless of the value in the JOBMSGQFL parameter. If the job was suppose to wrap but could not remove enough messages to allow wrapping, before the job is ended a dump of the internal queue space object is generated to a spooled file. View the dump and if it does not indicate what filled the queue to prevent wrapping, send the dump to IBM. Another way to determine why the job ended, if the problem can be recreated, is to trace the job with the Start Trace (STRTRC) command. Examine the trace to find out what types of messages are being sent.

Message File : QCPFMSG
Library Message File : QSYS2924


TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by IBM.

Length: 3252 Date: 20240329 Time: 033816     sap01-206 ( 6 ms )