What Causes S0F4 Abend in CA Disk and CA Vantage?
search cancel

What Causes S0F4 Abend in CA Disk and CA Vantage?

book

Article ID: 12290

calendar_today

Updated On:

Products

Disk Backup and Restore - MVS DISK BACKUP AND RESTORE- ADD-ON OPTIO DISK BACKUP AND RESTORE

Issue/Introduction



What Causes S0F4 Abend in CA Disk and CA Vantage?

Environment

Release: SMV3EN00200-12.6-Graphical Management Interface
Component:

Resolution

Here are resolutions to S0F4 reports in CA Disk and CA Vantage.
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1.  
The CA Disk team opened PMR to IBM lab.  After the LAB analysed the problem they
advised to team to apply a PTF.
    
What we can see is that the we get a message:
IDI0002I Module IGWDRAC0 offset X'1CA7C': Abend S0F4-X'20'
A system abend 0F4 RC x'20' occurred in module IGWDRAC0 at offset X'1CA7C'.
The abend was caused by machine instruction 0A0D (ABEND).
This is a IBM problem for which they provided a fix.
 
[The Apar or PTF number was not given to CA.] 
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2.  
CA Disk encountered a corrupted PDSE data set, printed appropriate error messages,
skipped the data set, and continued on to a successful completion.
The issue is that a dump was produced for a S0F4-20 ABEND. The S0F4 ABEND is
coming from the IBM PDSE support modules and is what that IBM code returns to
Disk when the corrupted PDSE data set is encountered. This is normal.
  
The only thing the customer can do is to fix the corrupted PDSE data sets.
To identify the data set that caused the dump, browse the dump data set for
'DMS DIAGNOSTIC AREA'. This is a work area in memory that documents the data set
Disk is currently processing. Once you have the data set name, browse the job
output for it to find the error messages documenting the problem Disk had with the data set.
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
3.
Corrupted PDSE files also cause S0F4 abends in CA Vantage and the bad PDSEs must be removed.
   
To find the corrupted PDSE data sets, do the following:
1) Check the JESMSGLG for the exact time when the abends happened.
2) Compare the time of the abends with the messages in MSGE0001.  The times should match.
3) Check the data sets and verify that they that are usable.
Based on the findings from IBM, the corrupted data sets appears to be PDSE
data set but is HFS data set in reality (it has FORMAT-1 DSCB set to indicate PDSE data set).
I think that by simply trying to browse the data set you should see some error for the corrupted data set.
 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Additional Information

Please contact CA Technical Support if any questions.