S0D3 abend in CAL7 address space on z/OS 3.2 compatibility - CA 11

Products

• Workload Automation Restart Option for z/OS Schedulers (CA 11)

Issue/Introduction

When upgrading to z/OS 3.2, the CA 11 CAL7 address space or the DBAS task may encounter an S0D3 abend. This occurs intermittently when calling address spaces are started with the REUSASID=YES parameter.  Is there a way to test/validate the product  the issue after PTF LU18910 has been applied? 

Environment

z/OS 3.2

CA 11 11.0

Cause

CA 11 does not support the ASID Reuse facility (REUSASID=YES) for its own address space. On z/OS 3.2, if a calling address space—such as the IBM Health Checker (HZSPROC)—is started with REUSASID=YES, it can trigger a cross-memory conflict leading to the S0D3 abend.

Resolution

  PTF  LU18910 addresses environmental compatibility and does not include a specific IVP test job.  

Follow these validation and configuration steps:

1. Ensure the CA 11 started task and Datacom MUF initialize without an S0D3 abend.
2. Verify that the CAL7 address space is not started with REUSASID=YES.
3. If the IBM Health Checker (HZSPROC) is started with REUSASID=YES in your environment, modify the CA 11 configuration file (typically in the CAL7OPTN library) to set HLTHCK=NO.
4. Confirm the product is accessible via ISPF panels.