Using CA Compress and receiving a S50D abend in an application job. How is this resolved?
Using CA Compress and receiving a S50D abend in an application job. How is this resolved? This is a multi-step job but also happens with a single step.
In the CA Compress for Release 5.5 Reference Guide you can find this situation documented. This type of situation is to be excluded from CA Compress management.
See Section Special Considerations when using SUBSYS and the label is JCL Restrictions. (Page 122)
? SPACE=(...,...,RLSE)—When an application program closes multiple data sets in a single CLOSE macro call where one or more of the data sets is compressed by CA Compress RLSE can cause an S50D abend. CA Compress issues messages ZSUR007I and ZSUR050I.
CA Recommends you review the entire section of the manual.
Although, you may see this situation, if you believe this is not the situation then you should provide the documentation to CA and open a support issue for a review.
As a circumvention to your current situation you can add an exclusion DD statement to your job to keep CA Compress from managing the files.
//@ZSM@XFR DD DUMMY
Documentation required should you decide you want CA to review your documentation on the S50D abend.
set a SLIP.
Run the test again with a @PST@TRC DD in the steps so we can get a good Compress trace.