WHY DO I GET AN S0C4 ABEND IN TSSKPORT + 13B2?

book

Article ID: 50059

calendar_today

Updated On:

Products

CA Cleanup CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Top Secret CA Top Secret - LDAP CA Top Secret - VSE

Issue/Introduction

Description:

You may see the following abend in CA Top Secret:

TSS9999E CA-TSS SECURITY SVC ABEND S0C4 IN TSSKPORT+13B2   
IEA995I SYMPTOM DUMP OUTPUT 976   
SYSTEM COMPLETION CODE=0C4 REASON CODE=00000011   
TIME=12.00.16 SEQ=30287 CPU=0000 ASID=010B   
PSW AT TIME OF ERROR 073C7400 9B9EB5BA ILC 6 INTC 11   
NO ACTIVE MODULE FOUND - PRIMARY NOT EQUAL TO HOME   
NAME=UNKNOWN

Solution:

The problem in this case is caused by switching from the old password format to the new password format without an IPL.

While we see it was stated that NEWPWBLOCK was never specified when running TSSXTEND, running TSSXTEND under 14.0 will always result in the
output file having the new password format.

Since there are existing control blocks using the old password format, and we make our decisions based on the password format currently in effect,
we are incorrectly calculating the length of the data we are trying to move. This results in the abend.

We haven't been able to come up with any way to detect this situation programmatically. While in theory it is a good idea to IPL when changing
security files, we can see that it is not always practical to do so. However, any problems caused by the discrepancy in password formats will be cleared
up by an IPL.

This abend is caused by changing password format without an IPL.

Environment

Release:
Component: AWAGNT