IBM Support

Identifying possible corruption of IWS z/OS VSAM files

Troubleshooting


Problem

A VSAM file for example EQQCP1DS ( CP1 ) or EQQCP2DS ( CP2 ) may have become corrupted. Can this be verified or prevented?

Diagnosing The Problem

The following message in the EQQMLOG can indicate that a file ( EQQJS1DS in this example) has become corrupted:

EQQN043E UNSUCCESSFUL VSAM I/O REQUEST. DETAILED INFORMATION FOLLOWS:
EQQN043I ACTIVE TASK IS WS ANALYZER     . LOAD MODULE IS EQQJHJSX              
EQQN043I I/O REQUEST IS FROM EQQJHPUT 04/05/25 13.44.55 UQ88793  AT OFFSET +0E90
EQQN043I REQUESTED FUNCTION IS ISRT ON LOGICAL FILE JS  , DDNAME EQQJS1DS      
EQQN043I VSAM RETURN CODE IS 8, REASON CODE IS 0032, KEY IS
.                M0779C021104562$3212021105..
EQQN043I                               HEXADECIMAL ZONES
.                DFFFFCFFFFFFFFF5FFFFFFFFFF00
EQQN043I                               HEXADECIMAL DIGITS
.                407793021104562B321202110503

The VSAM return code 8, reason code 0032 is what indicates a possible corruption of the
file. This corruption can be confirmed by running an IDCAMS EXAMINE of the file.

Message IDC11705I INDEX RECORD CONTAINS DUPLICATE INDEX POINTERS
in the EXAMINE output is normally seen only for files with VSAM SHR(3), and indicates
a corruption problem for this file.

It is possible that VSAM corruption could occur without the EQQN043E message being seen- for
example a VSAM error could be seen when running a backup job like IDCAMS REPRO or
DFDSS utility.

Resolving The Problem

If a corruption of a VSAM file has already occurred then some recovery actions such as restoring the file from a backup will be needed. It is suggested to open a PMR to get assistance with this. Chapter
"Backup and recovery of data sets" in the Customization and Tuning Gude has a section "Restoring
a damaged IBM Workload Scheduler for z/OS file from backup" contains general instructions;

VSAM provides a method to prevent possible corruption of the VSAM files, by using VSAM shareoption(2) . For further information, limitations and usage effects in IWS for z/OS, see this technote:”

http://www-01.ibm.com/support/docview.wss?uid=swg21198958

This can be done without having to redefine the file- an IDCAMS ALTER command can be
used to modify the shareoptions, as shown in the following example:

//STEP1     EXEC PGM=IDCAMS,REGION=6M                              
//SYSPRINT  DD SYSOUT=*                                            
//SYSIN     DD *                                                    
    ALTER TWSZ.V9R3M0.JS1DATA SHR(2)                                
    ALTER TWSZ.V9R3M0.JS1INDEX SHR(2)
.
You can get the DATA and INDEX component names by running a LISTCAT
on the cluster.

[{"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
13 September 2019

UID

swg22009568