Deliver - Report not delivered because they stay in BNDL WAIT
search cancel

Deliver - Report not delivered because they stay in BNDL WAIT


Article ID: 244535


Updated On:




To reduce the number of alerts generated by a fail check on "DLVR_PRFM_PQE@xxxxxxx", we raised the RMOPARM PRBTASK from 1 to 4 and then 4 to 8.

This helped to reduce the count of alerts being generated by health-check, but on the other hand, this revived an old problem where some reports will stay in "BNDL WAIT" on a daily basis.

I investigated the issue for the H-C in 2020, following this link:

Since we couldn't come to find a way to reduce the count, I applied one of the suggestions to raise PRBTASK. 

The issue with PRBTASK is not something new to us, as we got that problem in 2010-2011 and after investigating with CA, and since we couldn't find a way to avoid the issue, we decided to return PRBTASK to 1. Everything worked very fine that way.

We have 4 Deliver RMOSTC tasks active. 3 are set with PRBTASK=12 and never cause problems, but the most active task is the one giving us grief.

Can you identify anything that could address issues with reports in "BNDL WAIT" ? If not, I will return PRBTASK to 1 and disregard incidents for "DLVR_PRFM_PQE@xxxxxxx".

Also, I tried to INACTIVATE the H-C for "DLVR_PRFM_PQE", and tried to raise the WARN value but nothing seems to work.

Is there an easy way to disable a specific check  ?


Release : 14.0

Component :


Clients can control the activity of individual health checks, or groups of health checks through masking, using the native IBM z/OS Health Checker facilities. 

Health checks may be dynamically controlled using a product like SYSVIEW or SDSF. 

The z/OS Health Checker address space, HZSPROC, supports z/OS MODIFY commands to dynamically control health checks. 

To make permanent changes, the z/OS Health Checker control statements should be placed in the logical PARMLIB member, HZSPRMxx, which HZSPROC reads at start up.

See the Managing Checks chapter, in the IBM Health Checker for z/OS User's Guide, for detailed information regarding the control of health checks.

The statement needed to stop the message is:



Clients that have very heavy processing loads can use the utility program RMORAP to control the utilization of their checkpoint data set.  

Use of RMORAP can reduce what is in BNDL WAIT.  

If RMORAP is used this way, then the RMOPARM initialization parameter PRBTASK should be set to 1 (PRBTASK=1).