Dispatch - Dispatch task is failing with SEA1
search cancel

Dispatch - Dispatch task is failing with SEA1

book

Article ID: 244323

calendar_today

Updated On:

Products

Dispatch Output Mgmt

Issue/Introduction

Dispatch task that is failing with a SEA1 abend/error.

Environment

Dispatch, 11.7, SEA1, abend, reason, cause, z/OS

Cause

Possible causes for the SEA1 condition are:

 - APF authorization problem related the Dispatch load library or other Dispatch STC concatenated load library. 
 - Some type of CVKEY change related to upgrading to z/OS 2.4 or higher. Broadcom recommends that you use CVKEY=04.
 - Not having Dispatch PTF "LU14245 - DISPATCH MAIN TASK ABENDS WITH SEA1" applied.
 - Not having Dispatch PTF "RO40492 - CA DISPATCH SEA1 ABEND" applied. 
 - Upgrading the CPU and not having the required Dispatch compatibility maintenance applied. (APAR# SO00970 and SO00682).
 - High CPU using AFP resources in PDSE data sets. 
 - An Automation process or Operator had issued a PURGE and then a CANCEL of the active Dispatch task. 

Resolution

Suggested resolutions to SEA1 abends depending on your particular circumstances:

* Make sure you have all of the PTF's listed in the CAUSE section of this article applied and that the code from these PTF' shas been moved into the appropriate load library.
* Make sure your Disatch load library, as well as any other concatenated load libraries, are APF AUTHORIZED.
* If you suspect that your SEA1 is related to a CVKEY change, refer to Knowledge Article ID: 11361 and perform the following process:
 
1. Apply or RE-Apply DSINCVKEY usermod to set CVKEY=04. (Check output for RC=00).
2. Move updated CADSSVC module into appropriate loadlib - (For reload of SVC AND for "CAS9 at IPL" as well).
3. Perform LLA REFRESH if load libraries are LINKLISTED.
4. Implement the PPT entries to match CVKEY=04 as described in article 11361 mentioned above.
5. Run CAS9 to reload Dispatch SVC. (Check output for RC=00).
6. Restart Dispatch. 

Additional Information

Regarding the CVKEY point above, as of z/OS r2.4 and IBM's requirement that ALLOWUSERKEYCSA be set to NO, all Dispatch customers are required to change the default CVKEY from 8 to a value value between 0 and 7. We recommend using CVKEY=04.