Considerations regarding the job log maximum size and the resulting job actions might help you solve the problem.
If you are having problems with storage consumption, you might need to change the job log maximum size on the server job. You should specify a relatively small size for the job log to avoid consuming excessive storage and, in some cases, excessive processing time. These types of resource consumption occur when the system produces job logs. For example, if a repetitive error occurs on a long running server job, your job log fills up with repetitive messages and increases your storage consumption level.
The value specified for the Job message queue maximum size (JOBMSGQMX) parameter for the job indicates the size of the job log. This value, along with the rest of the job's properties, is given to the job when the job is started. Some server jobs specify this value in the job description used by the job. Other server jobs specify this value by defaulting to the setting of the QJOBMSGQMX system value.
The recommended value for the JOBMSGQMX parameter is 8 MB. You cannot change the value for this parameter by using the Change Job (CHGJOB) command. However, you can change the value by accessing the parameter through the job description using the Change Job Description (CHGJOBD) command.
When the job log reaches its maximum capacity as determined by the JOBMSGQMX parameter, several different actions can occur depending on the value specified in the Job message queue full action (JOBMSGQFL) parameter for the job. In most cases, the job description indicates *WRAP as the default value. Many server jobs specify this value in the job description used by the jobs.
You should verify that *WRAP is specified for the JOBMSGQFL parameter by accessing the job description. This value ensures that the job log messages overlay one another when the job log reaches its maximum capacity. Be aware that other values, such as *NOWRAP, can cause the server job to end when the job log reaches its maximum capacity.