335E

CA‑ACF2 CMS storage trap detected an error, code=<cd>, save=<addr>, len=<len>, addr=<addr2>, return=<addr3>

Reason

CA ACF2 for z/VM‑supplied CMS modules and programs have a storage trap built‑in that detects errors in CMS storage requests. This trap has detected an error. A CMS abend occurs after this message. If this abend occurs in the service machine, CA ACF2 for z/VM takes a VMDUMP and the service machine logs off and starts again. This message can be caused by an internal error, by a user exit, or by another program overlaying storage owned by the CA ACF2 for z/VM module that is executing.

The variable <cd> is a code that indicates the type of error detected. These are:

1: Free/fret header eyecatcher is invalid
3: Free/fret trailer storage address does not match the request
4: For a get save area, the header eyecatcher is invalid
5: For a get save area, the trailer eyecatcher is invalid
6: For a release save area, the trailer eyecatcher is invalid
<addr>: Address of the save area CA ACF2 for z/VM support uses to save the requester’s registers
<len>: Length of the processed storage block
<addr2>: Address of the processed storage block
<addr3>: Return address the requester specified.

Action

If the service machine issued this message, save the service machine dump and console log. Try to determine if a user program caused this error. Review any service machine user programs for possible incorrect base register use or displacement. If you can reproduce this problem, remove the user program and try to reproduce the problem. If the error does not reproduce, the problem is the user program. If the problem is still not resolved, contact CA Support.

If the service machine did not issue this message, use CMS DEBUG to display the PSW and register contents and record these values. Use the CP VMDUMP command to create a storage dump.

If a user‑written module that uses a CA ACF2 for z/VM‑supplied program issued this message, the probable cause is a storage overlay by the user module. Using the dump, try to identify the code causing the overlay. If you can reproduce the problem, use the STORE options of the CP TRACE command to trap the cause of the overlay. If you still cannot resolve the problem, contact CA Support.