APAR status
INTRAN
Error description
Last update: 01/05/2000 15:48 EDT --------------------------------- RMM APAR OW42560 Enhanced Diagnostic Tools for DFSORT Users *** The jobs described by the following procedure are *** contained in three INFO APARs -- II12197 (this one), *** II12198 and II12199. In order to prevent any loss of data please follow this procedure: 1. Apply either the ++APAR AW42560 from RETAIN/DLL or the ZAP listed in INFO APAR II12193. If the ZAP doesn't fit to your maintenance level get in contact with IBM system support and provide the PTF level for module EDGSOCE. ++APARs are AW42560, BW42560, CW42560 or DW42560 depending on the DFSMSrmm release. 2. To prevent volumes getting scratched in error do not run Inventory Management EXPROC function. Use the listed JOB1/2 below and the following procedures, to identify any potentially affected volumes. If you have not yet run JOB1 or JOB2, we recommend you start with step 3 procedures. Problem and Recovery Overview: RMM does not correctly record the volume expiration date as 99365 or 99366 when permanent retention dates are supported by the installation and multiple files are written to a tape using mixed retentions with at least one case of permenent retention requested and one expiration date of 2000/001 or higher. The information recorded by RMM depends on the sequence of the expiration dates used. When 99365/6 are used before a 21st century date, RMM records the correct date in the CDS and in SMFAUD and JOURNAL records. Later the date in the CDS is replaced with a 21st century date at OPEN time. If the sequence is reversed, RMM does not record the 99365/6 date. When JCL retention is specified(EXPDT or RETPD), RMM also records an 'original expiration date'. Any volume affected by this problem will have an original expiration date under normal circumstances. However, if RMM commands are used to alter the expiration date to 99365/6 the original expiration date is not updated so cannot be a guarantee that a volume may be affected. Potentially affected volumes have an expiration date higher than 1999366 and multiple files, and should not have expired until 1st January 2000 or later. Recovery of affected volumes depends on the above information but it can only accurately identify volumes when the SMFAUD or JOURNAL data includes 99365/6. In other cases, using current CDS information recovery can identify volumes which may have been lost or may have been subject to the problem but are still in the CDS. Recovery from history data allows existing volumes, still containing the same data, to be corrected back to 999365 expiration date. It also allows volumes that have been reused to be identified. Use IDENTVOL to build commands to correct identified volumes, and use the list of reused/LOST volumes and potentially affected volumes from IDENTVOL and either JOB1 or JOB2 as an aid to identifying further volumes based on local knowledge. Recovery: JOB1 identifies volumes: A) Still MASTER B) Still MASTER, but Pending release C) Already returned to scratch since 1999366 and still scratch. Use the list to decide if any should be reclaimed. JOB2, below, is also available. It produces a reduced list of affected volumes on the assumption that the original expiration date is set for any volumes that ever used EXPDT or RETPD JCL values. Use JOB2 only if you never used RMM commands to set EXPDT(99365) for volumes and later wrote files with 21st century dates to them. The jobs create three output files for the types listed above. They also create RMM command files with CHANGEVOLUME commands to reclaim volumes from scratch and pending release, and ADDVRS command files to prevent suspect volumes being released in error. Use these lists and run them as TSO command files. In order to reclaim the volumes from scratch a default owner of Y99365 will be used. This owner needs to be defined in RMM manually. Start with the xxxCV commands and continue with the xxxAS commands. They will reclaim volumes from scratch, change the EXPDT and assign volume VRSs. Then run EDGHSKP with PARM=VRSEL to assign these VRSes to the volumes. After the detailed verification of identified volumes these VRSs can easily be deleted and the volumes will either be correctly retained or go back to scratch after the next inventory management run. Note: If a large number of volumes are identified as potential candidates, some performance impact may be experienced due to the number of Volume VRSes defined to retain the volume candidates. Using JOB2 and also the following procedures allows the list to be reduced. After changes have been made to correct the expiration dates make sure that the volume VRS is deleted for each volume. . 3. Five ICETOOL jobs below -- SMFAUD, JOURNAL, OLDCDSB, CDSB and IDENTVOL -- are available to analyze the history data against the current CDS. SMFAUD: analyzes the history SMF data. You can go back in time as far as you would like. JOURNAL: Uses history data from the RMM journals OLDCDSB: Uses history data from before 31st December CDSB: Uses the current CDS backup to identify potentially affected volumes IDENTVOL: Uses output from history analysis and CDSB to identify volumes actually affected. You will need to provide the following input: SMFAUD: SMFDUMP(s) as much as you have available JOURNAL: RMM journal backups as much as you have available OLDCDSB: An RMM CDS backup from before 31st December. We believe a backup prior to the default retention period before 31st December is best. For example, RETPD(10) use backup from 20th December or earlier. CDSB: Current BACKUP copy of the RMM CDS If the backup was taken using the DSS option you must first restore the backup to a new VSAM KSDS and use IDCAMS REPRO to create a sequential input file required by the CDSB job. . Which ever option you use you will run CDSB and IDENTVOL at least once. We recommend you run OLDCDSB if possible and either SMFAUD or JOURNAL. When you run OLDCDSB you should process SMFAUD or JOURNAL using data at least from the data of the old CDS backup. 1 Customize SMFAUD and specify the SMFAUD number from the EDGRMMxx parmlib member in HEX format. 2 Run CDSB to create an extract of the CDS volume records 3 Run one of SMFAUD, OLDCDSB, or JOURNAL to create input for IDENTVOL. Each time you run one of these jobs, rerun IDENTVOL to process the data 4 Run IDENTVOL once for each history extract you create. It will create two output files with RMM commands to set the volume expiration date to 99365: CMDM - volumes still in MASTER status CMDS - volumes already in SCRATCH status and one file with volume records: LOST - already rewritten The SMFDUMP or JOURNAL data sets can either be concatenated or the SMFAUD/JOURNAL job followed by the IDENTVOL job can run against each JOURNAL and each SMFDUMP data set. The prefered way is to start with the newest data set. Use the CMDM and CMDS files to reclaim volumes and correct the expiration date. Now you can rerun JOB1 or JOB2 to produce an updated list of potentially affected volumes. The recovered volumes will no longer be listed. You can delete the old volume VRSs, and use the new commands from JOB1/2 to add the latest required set of VRSs. Any volume still covered by a volume VRS must be verified using local knowledge to decide if they may be affected. . (For searchability: RMMY2K Y2K YR2000 YEAR2000 SYNCTOOL ) *** The seven jobs below -- JOB1, JOB2, SMFAUD, OLDCDSB, JOURNAL *** CDSB and IDENTVOL -- are separated by a line of equal signs. ================================================================ //* THIS HAS BEEN TESTED ON Syncsort 3.6 //JOB1 JOB ('T,H,IOM,,',SYSPROG),'G.OW42560', // MSGLEVEL=(1,1),MSGCLASS=H,REGION=4096K //*------------------------------------------------------ //* RUN INVENTORY MANAGEMENT //*------------------------------------------------------ //EDGHSKP1 EXEC PGM=EDGHSKP,REGION=24M, // PARM='RPTEXT,DATEFORM(J)' //* 2 following files must be pre-allocated and cataloged //MESSAGE DD DISP=SHR,DSN=RMM.OW42560.MESSAGE //REPTEXT DD DISP=SHR,DSN=RMM.OW42560.REPTEXT //SYSPRINT DD SYSOUT=* //*------------------------------------------------------ //* SYNCSORT SORT STEP USING OUTFIL //*------------------------------------------------------ //OUTFIL EXEC PGM=SORT,REGION=24M //SYSOUT DD SYSOUT=* //SORTIN DD DSN=RMM.OW42560.REPTEXT,DISP=SHR //SORTOF1 DD DSN=RMM.OW42560.MASTER, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE) //SORTOF2 DD DSN=RMM.OW42560.SCRATCH, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE) //SORTOF3 DD DSN=RMM.OW42560.PENDING, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE) //SYSIN DD * OPTION VLSHRT SORT FIELDS=COPY *-------------------------------------------------------- * IF VOLUME RECORD AND * VOLUME IS NOT SCRATCH AND * VOLUME IS NOT PENDING RELEASE AND * EXPIRATION DATE IS Y2K OR HIGHER AND * MULTI FILE VOLUME THEN * INCLUDE RECORD *-------------------------------------------------------- OUTFIL FILES=1, INCLUDE=(5,1,CH,EQ,C'V',AND, 322,8,CH,NE,C'SCRATCH ',AND, 330,1,CH,EQ,C'N',AND, 119,10,CH,GT,C'1999/366 ',AND, 134,4,CH,GT,C' 1') *-------------------------------------------------------- * IF VOLUME RECORD AND * VOLUME IS SCRATCH AND * SCRATCH DATE IS Y2K OR HIGHER AND * MULTI FILE VOLUME THEN * INCLUDE RECORD *-------------------------------------------------------- OUTFIL FILES=2, INCLUDE=(5,1,CH,EQ,C'V',AND, 322,8,CH,EQ,C'SCRATCH ',AND, 240,10,CH,GT,C'1999/366 ',AND, 134,4,CH,GT,C' 1') *-------------------------------------------------------- * IF VOLUME RECORD AND * VOLUME IS NOT SCRATCH AND * VOLUME IS PENDING RELEASE AND * EXPIRATION DATE IS Y2K OR HIGHER AND * MULTI FILE VOLUME THEN * INCLUDE RECORD *-------------------------------------------------------- OUTFIL FILES=3, INCLUDE=(5,1,CH,EQ,C'V',AND, 322,8,CH,NE,C'SCRATCH ',AND, 330,1,CH,EQ,C'Y',AND, 119,10,CH,GT,C'1999/366 ',AND, 134,4,CH,GT,C' 1') //* //TOOL EXEC PGM=SYNCTOOL,REGION=24M //SYSOUT DD SYSOUT=* //TOOLMSG DD SYSOUT=* //DFSMSG DD SYSOUT=* //MASTER DD DSN=RMM.OW42560.MASTER, // DISP=SHR //SCRATCH DD DSN=RMM.OW42560.SCRATCH, // DISP=SHR //PENDING DD DSN=RMM.OW42560.PENDING, // DISP=SHR //MSTAS DD DSN=RMM.OW42560.MSTAS, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE),LRECL=255 //SCRAS DD DSN=RMM.OW42560.SCRAS, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE),LRECL=255 //PNDAS DD DSN=RMM.OW42560.PNDAS, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE),LRECL=255 //SCRCV DD DSN=RMM.OW42560.SCRCV, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE),LRECL=255 //PNDCV DD DSN=RMM.OW42560.PNDCV, // DISP=(,CATLG),UNIT=SYSALLDA, // SPACE=(CYL,(2,1),RLSE),LRECL=255 //TOOLIN DD * MODE CONTINUE COPY FROM(MASTER) TO(MSTAS) USING(AVRS) COPY FROM(SCRATCH) TO(SCRAS) USING(AVRS) COPY FROM(PENDING) TO(PNDAS) USING(AVRS) COPY FROM(SCRATCH) TO(SCRCV) USING(SCRC) COPY FROM(PENDING) TO(PNDCV) USING(PNDC) //* //AVRSCNTL DD * *-------------------------------------------------------- * CREATE TSO COMMANDS TO ADD VOLUME VRS'S: * RMM AS VOLUME(......) *-------------------------------------------------------- OUTREC FIELDS=(1,4,C'RMM AS VOLUME(',9,6,C')',255:X) //* //SCRCCNTL DD * *-------------------------------------------------------- * CREATE TSO COMMANDS TO RECLAIM SCRATCH VOLUME * RMM CV ...... RETPD(5) STATUS(MASTER) OWNER(Y99365) *-------------------------------------------------------- OUTREC FIELDS=(1,4,C'RMM CV ',9,6, C' RETPD(5) STATUS(MASTER) OWNER(Y99365)', 255:X) //* //PNDCCNTL DD * *-------------------------------------------------------- * CREATE TSO COMMANDS TO RECLAIM PENDING RELEASE VOLUMES * RMM CV ...... RETPD(5) *-------------------------------------------------------- OUTREC FIELDS=(1,4,C'RMM CV ',9,6,C' RETPD(5)',255:X) *** INFO APAR II12200 contains JOB2, SMFAUD and CDSB *** INFO APAR II12201 contains IDENTVOL, OLDCDSB, JOURNAL
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II12195
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
INTRAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2000-01-04
Closed date
Last modified date
2000-01-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
05 January 2000