Ansicht
Dokumentation

CPI2411 - A cleanup program was run to clean up the job message queue for &3/&2/&1. ( OS/400 )

ROGBILLS - Synchronize billing plans   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by IBM.


Message : CPI2411
A cleanup program was run to clean up the job message queue for &3/&2/&1.

Message Long Text :

Cause . . . . . : The size of the job message queue for &3/&2/&1 had reached its maximum object size (16M).
Recovery . . . : After the cleanup program completed, the job was able to continue. You may look at the messages in the job message queue to determine why the job message queue has become full by using the Display Job Log (DSPJOBLOG) command specifying &3/&2/&1 for the JOB parameter. If the cleanup program starts to send this message out frequently for the same job, user action is recommended to obtain a fresh job message queue. For system jobs (QLUS, QSYSARB, or SCPF) an IPL is required. For subsystem jobs (QBATCH, QINTER, ...) you need to end the subsystem (ENDSBS) and then restart the subsystem (STRSBS). For user jobs either end the job (ENDJOB) and restart the job, or remove all the inactive messages in your job message queue by using the Remove Message (RMVMSG PGMQ(*ALLINACT) CLEAR(*ALL)) command to free up some space.
Technical description . . . . . . . . : &4 internally defined messages that were no longer needed were deleted from the job message queue so that additional program messages can be sent. Once a job message queue becomes full, it will still be using 16 megabytes of memory after the cleanup program is run. If this is a concern, consider the user actions described above.

Message File : QCPFMSG
Library Message File : QSYS2924


CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by IBM.

Length: 3257 Date: 20240426 Time: 130748     sap01-206 ( 4 ms )