OA62765: AFTER PTFS FOR APAR OA61055, LWORM VOLUMES IN SCRATCH POOL ARE FAILING WITH EDG4055I 22/01/31 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In OA61055, code was added that preserved the WORM, WWID, and
  WMC fields for LWORM volumes that are returned to scratch so
  they could be more easily recovered in a premature scratch
  situation. If this PTF is not applied on other LPARs running
  DFRMM however, they are rejected as scratch mounts with EDG4055I
  VOLUME xxxxxx REJECTED. WWID yyyyyyyyyy FOR VOLUME DOES NOT
  MATCH RECORDED VALUE. The volume then gets moved in the error
  category and has status REJ BY TAP MGT SYS.
  .
  The issue here is that the code in the PTF causes EXPROC to
  leave the WORM attributes intact in the RMM CDS entry for the
  former
  LWORM volumes but other systems without the same code level do
  not know this data should be ignored/reset on re-use as a
  scratch candidate.
  
  ADDITIONAL KEYWORDS:
  MSGEDG4055I EDG4005E MSGEDG4005E IEC518I MSGIEC518I SOFTWARE
  ERRSTAT REJTMS
  
  PE INFORMATION:
  USERS AFFECTED:
  ALL DFSMSrmm users who have applied APAR OA61055 to one system,
  but not all systems sharing the RMM CDS.
  
  
  USER IMPACT:
  APAR OA61055 fixed the problem it reported but introduced a new
  problem.
  

Local fix

• BYPASS/CIRCUMVENTION:
  1) Remove the PTF from the system that will run EDGHSKP EXPROC
  or run EDGHSKP EXPROC processing on an LPAR that does not have
  the PTF applied. (and then run once the job in option 3)
  .
  2) For those interested in using the new function apply the PTF
  to all the remaining RMM LPARs in the RMMPLEX
  .
  3) If the PTF is to be left applied to the LPAR running EXPROC,
  but not to the rest of the systems in the RMMPLEX, then run the
  following two steps to turn off the WORM flag on all volumes in
  the scratch pool daily after each EDGHSKP EXPROC run:
  .
  a) Use the RMM SV command, generate a list of RMM CV
  commands for affected volumes to disable the WORM flag
  .
  //STEPA EXEC PGM=IKJEFT01
  //SYSTSPRT DD DUMMY
  //RMMCLIST DD DSN=hlq.RMMDV,
  // DISP=(NEW,CATLG,DELETE),
  // SPACE=(CYL,(20,20),RLSE),
  // UNIT=SYSDA,LRECL=80,RECFM=FB
  //SYSTSIN DD *
   RMM SV VOLUME(*) OWNER(*) STATUS(SCRATCH) WORM(YES) LIM(*) -
      CLIST('RMM CV ',' NOWORM')
  .
  b) To execute the output file and turn off the WORM flag,
  once you have confirmed the contents of the hlq.RMMDV file is
  correct, you can execute those commands with the following JCL:
  .
  //STEPB    EXEC  PGM=IKJEFT01,DYNAMNBR=60
  //SYSTSPRT DD DSN=hlq.RMMDV.OUT,
  //         DISP=(NEW,CATLG,DELETE),
  //         SPACE=(CYL,(100,20),RLSE),
  //         UNIT=SYSDA,LRECL=80,RECFM=FB
  //SYSTSIN  DD   DISP=SHR,
  //          DSN=hlq.RMMDV
  
  
  
  
  
  RECOVERY ACTION:
  1) run the steps noted in item 3 under Local Circumvention to
  turn off the WORM flag in the scratch pool volumes
  .
  2) Any volumes that were moved to REJ BY TAP MGT SYS status can
  be taken out of this status by using ISMF ALTER of the USE
  ATTRIBUTE from S to S. Even though they are already scratch, it
  will take the volumes out of the error category
  or
  .
  3) Use the EDGSPLCS utility to issue a move to scratch command
  for those volumes in the error category (same effect as 2 above,
  but in bulk)
  .
  //EDGSPLCS EXEC PGM=EDGSPLCS
  //SYSPRINT DD   SYSOUT=*
  //INDD     DD   DSN=command.dataset,DISP=SHR
  //OUTDD    DD   SYSOUT=*
  .
  Where 'command.dataset' contains commands in the following
  format:
  .
  S  volser <<< col.1 command, S for scratch,col.4 volume serial
  number
  .
  For example, to issue the SCRATCH command for volumes T10001 to
  T10004. your 'command.dataset' will need to include:
  .
  ----+----1----+----2----+----3----+----4
  S  T10001
  S  T10002
  S  T10003
  S  T10004
  .
  To use EDGSPLCS to issue SCRATCH command to these volumes RMM
  must be active.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All DFSMSrmm users having all of the following conditions:   *
  * - using Logical WORM (LWORM) volumes;                        *
  * - using several systems (LPARs) sharing the same DFSMSrmm    *
  * control data set (CDS);                                      *
  * - having applied PTF(s) for APAR OA61055 on some but not all *
  * LPARs of the SYSPLEX.                                        *
  * Note: For z/OS V2R5 the OA61055 PTF has been integrated into *
  * the base code.                                               *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The OA61055 PTF code provides                                *
  * possiblity for easy recovery in a                            *
  * premature scratch situation for LWORM                        *
  * volumes by means of preserving the                           *
  * WORM fields for LWORM volumes when                           *
  * returning volumes to scratch during                          *
  * EXPROC run. Also, the PTF ensures                            *
  * that a LWORM scratch volume with the                         *
  * preserved WORM fields can be re-used                         *
  * as either a new WORM volume or as a                          *
  * normal R/W (non-WORM) volume.                                *
  *                                                              *
  * However, if the PTF has been applied                         *
  * on some, but not all systems of the                          *
  * RMMPLEX, then a LWORM scratch volume                         *
  * with the preserved WORM fields will be                       *
  * rejected with:                                               *
  *                                                              *
  * EDG4055I VOLUME vvvvvv REJECTED. WWID                        *
  * wwwwwwwwwww FOR VOLUME DOES NOT MATCH                        *
  * RECORDED VALUE uuuuuuuuuuu                                   *
  *                                                              *
  * when it gets mounted from scratch on                         *
  * the system where the PTF has not been                        *
  * applied. The volume then gets moved in                       *
  * the error category and receives status                       *
  * REJ BY TAP MGT SYS.                                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the applicable PTF(s) on all systems(LPARs) sharing    *
  * the same DFSMSrmm control data set.                          *
  ****************************************************************
  A preconditioning APAR should have preceded OA61055 that would
  prepare RMM to perform correct processing for LWORM volumes on
  their mount from scratch.
  

Problem conclusion

• The problem has been fixed by backing out the part of OA61055
  code that preserves the WORM fields on returning a LWORM volume
  to scratch during EXPROC run.
  Thus, the OA61055 enhancement gets disabled with this APAR.
  
  ZOS0203C/K
  ZOS0204C/K
  ZOS0205C/K
  ZOS0301C/K
  

Temporary fix

• *********
  * HIPER *
  *********
  
  *********
  The ++APAR is available upon request.
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  UJ07744 UJ07745 UJ07746 OA62888

Modules/Macros

• EDGMUPD  EDGSOCE  EDGMTSO
  

Fix information

• Fixed component name

  DFSMSRMM

• Fixed component ID

  5695DF186

Applicable component levels

• R250 PSY UJ07746

     UP22/02/18 P F202 ­

• R230 PSY UJ07744

     UP22/02/18 P F202 ­

• R240 PSY UJ07745

     UP22/02/18 P F202 ­

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.