221W

ACF2VM IUCV MSGLIMIT has been reached

Reason

CA ACF2 for z/VM is not active or you have reached the IUCV message limit.

Action

CA ACF2 for z/VM automatically queues new messages in CP until it receives this condition. Some system slowdown can occur. Ensure that the CA ACF2 for z/VM service machine is still logged on and running. If not, determine the cause by reviewing console logs from the service machine and operator and take the action indicated.

If the service machine is processing normally and CA ACF2 for z/VM rarely issues this message, this message probably indicates an unusual demand for CA ACF2 for z/VM service machine services, indicating you must take evasive action.

If the service machine is processing normally and CA ACF2 for z/VM frequently issues this message, update the service machine VM directory entry. The MSGLIMIT on the IUCV control statement in a VM directory entry determines the IUCV MSGLIMIT. The default is 10. Change the current service machine IUCV control statement for *RPI services to establish a higher limit. However, the MSGLIMIT should normally NOT be increased to the maximum value of 255. Rather, it should be increased to a level where the message no longer is issued frequently. The reason 255 should not normally be used is that message 221W is sometimes the only message that will tell you that there is a problem with CA ACF2 for z/VM processing. By increasing MSGLIMIT to 255, you would not be warned that there is a problem until 255 users were waiting on CA ACF2 for z/VM services. A value of 25 or 50 for the IUCV MSGLIMIT should be more than enough for most systems. CA ACF2 for z/VM VM will queue up the additional requests itself beyond the MSGLIMIT, so the requests will not be lost. Ensure that the service machine is given a high priority and favored status. If the problem persists, contact CA Support.