z/OS DFSMSdss Storage Administration
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Ignoring VSAM duplicate key errors (PN05529)

z/OS DFSMSdss Storage Administration
SC23-6868-01

If you set the flag at offset X'09' in ADRPATCH on (any value other than X'00'), DFSMSdss provides a serviceability aid that determines which records have duplicate keys. DFSMSdss restores all records of a keyed VSAM data set, ignoring any duplicate key error conditions that have occurred.

To set the flag to on dynamically, use the SET PATCH command. To set the flag to on (for example, X'FF') permanently, modify the sample JCL (see Sample JCL) as follows:
//SYSIN DD *
   NAME ADRDSSU ADRPATCH
   VER   09        00
   REP   09        FF

You can set a slip trap and use generalized trace facility (GTF) as follows:

  1. Use AMBLIST to locate the displacement (xxxx) of label ADRSLIP1 within ADRDSSU. The displacement of label ADRSLIP1 is used in setting the slip trap.
    //AMBLIST  JOB...
    //*
    //**************************************************************
    //*                                                            *
    //* SAMPLE JCL TO LOCATE THE DISPLACEMENT OF LABEL ADRSLIP1    *
    //* WITHIN ADRDSSU.  THE DISPLACEMENT OF ADRSLIP1 IS NEEDED    *
    //* TO SET THE SLIP TRAP.                                      *
    //*                                                            *
    //**************************************************************
    //LISTIT   EXEC PGM=AMBLIST
    //SYSPRINT DD   SYSOUT*
    //SYSLIB   DD   DISP=SHR,DSN=LIBNAME.LINKLIB
    //SYSIN DD *
    /*
  2. Set a slip trap from the system console. The displacement label of ADRSLIP1 obtained with AMBLIST is ’xxxx’. Registers 7 and 8 must be used as shown below:
    SLIP SET,IF,ACTION=TRACE,TRDATA=(STD,7R?,8R?),
    PVTMOD=(ADRDSSU,xxxx),JOBNAME=nnnnnnnn,END
  3. Start the GTF trace at the system console:
    1. Enter S GTF.
    2. Respond TRACE=SLIP,USR to message AHL125A ("SPECIFY TRACE OPTIONS").
    3. Respond U to message AHL125A ("RESPECIFY TRACE OPTIONS OR REPLY U").
    4. Run the DFSMSdss job.
    5. Use the Interactive Problem Control System (IPCS) to analyze the GTF trace output to determine which records are in error.
Note:
  1. The duplicate key error occurs only after the first record with a duplicate key gets written to the data set. Second and subsequent records with the same key are recognized as duplicates.
  2. Only the first 65 535 bytes of each duplicate record can be written to the trace data set.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014