II13326: COMMON PROBLEMS FROM SHCDS DEFINITION AND USAGE.

APAR status

• INTRAN

Error description

• Due to a number of problems we've been seeing in the field
  from new customers, we decide to put together this informational
  APAR to help guide you through the process of setting up and
  trouble-shooting problems with SMSVSAM/RLS shared control
  dataset (SHCDS).
  .
  PART 1: SHCDS DEFINITION
  .
  Here is a checklist that you need to run through to make sure
  you have defined your SHCDS properly:
  1- See 14.1.6  Defining Sharing Control Data Sets in DFSMSdfp
     Storage Admin. Reference for details. Also see section
     14.1.10  Establishing Authorization for VSAM RLS in DFSMSdfp
     Storage Administration Reference (including MASTER CATALOG )
  2- SHCDS must be a VSAM Linear data set.
     The SHCDS can be either SMS or non-SMS managed.
  3- CISIZE for SHCDS must be 4096.  Make sure that if you are
     using a Dataclass you are getting 4096.
  4- Shareoptions must be (3,3). GRS must be set up to enable
     VSAM sharing, i.e. SYSZIGW3 and SYSVSAM MUST NOT be in GRS
     Exclusion list. If GRS equivalent product, such as CA MIM,
     is used, please contact the vendor for guidance on how to set
     up RLS QNAMES correctly as global resources (II13751).
  5- Secondary extents are strongly recommended.
  6- Initial size of the SHCDS needs to be at least CYL(20,5).
     Larger if there are more than 6 systems in the plex.
  7- When defined, the SHCDS does not need to be catalogued on
     all systems in the sysplex. If it is cataloged, it must be in
     a catalog available when SMSVSAM initializes. The user
     may issue the command, Vary SMS,SHCDS(dsname),NEW
     and Vary SMS,SHCDS(dsname),NEWSPARE from any
     system in the sysplex, not just from the system where the
     SHCDS was defined and catalogued originally.  SMSVSAM
     will attempt to re-catalog the SHCDS if it cannot find the
     SHCDS in a catalog on that system.
  8- SMSVSAM must be authorized to update SYS1.DFPSHCDS.*
     data sets.
     If you protect SYS1.* data sets be sure SMSVSAM is
     able to access  SYS1.DFPSHCDS.* for update.
  9- Follow the SHCDS naming convention.  The SHCDS name must
     match the volume that it resides on.  That is,
     SYS1.DFPSHCDS.firstnam.Vvolser resides on volume volser
  Note:  APAR OW49746 prevents addition of a SHCDS if the SHCDS is
         not linear or if the CISIZE is not 4096.
  .
  The SHCDS may be defined using IDCAMS.  Here is an example:
  //*------------------------------------------------------
  //* ALLOCATE ON XP0301 - GUARANTEED SPACE IS SXPXXS04
  //*------------------------------------------------------
  //ALLOCLD1 EXEC PGM=IDCAMS
  //SYSPRINT DD SYSOUT=*
  //SYSIN DD *
    DEFINE CLUSTER (NAME(SYS1.DFPSHCDS.ACTIVE3.VXP0301) LINEAR -
          STORCLAS(SXPXXS04)                              -
          SHAREOPTIONS(3 3)   CYL(20 20) VOLUME(XP0301) )
  /*
  .
  PART 2: COMMON USAGE PROBLEMS
  .
  For suspected problems with the SHCDS, look for messages
  starting with IGW6, such as IGW615I.  Also look for messages
  that indicate a security problem with your SHCDS.
  .
  A- Problem:  Sharing Control Data Sets are added, but when
     when SMSVSAM is recycled or the system is IPLed, the SHCDS
     are deleted during initialization.
     Possible solutions:
     1- SHCDS is not correctly defined.  See "SHCDS Definition"
        above.  Redefine SHCDS.
     2- SMSVSAM does not have proper access to the SHCDS.
        Examine the Syslog for error messages indicating problems
        with the SYS1.DFP.  Set up access properly.
  B- Problem:  SMSVSAM initialization is not proceeding.
     Use the command, D SMS,SMSVSAM.  If the response indicates
     that SMSVSAM is in SHC_Ph2_Init:
  .
  IGW420I DISPLAY SMS,SMSVSAM
  DISPLAY SMS,SMSVSAM - SERVER STATUS
  SYSNAME:  SYSTEM2  UNAVAILABLE ASID: 00FC STEP: SHC_Ph2_Init
  .
  You should have received some IGW6* messages, such as
  IGW611A, IGW610A, or IGW609A, prior to this point.  Look for
  these messages in the Syslog. Issue the command, D SMS,SHCDS.
  Examine the "Status" column.  Make sure that you have at least
  2 active SHCDS and 1 Spare SHCDS.  A common error is to forget
  to add a Spare SHCDS or to add three actives instead of
  2 actives and a spare.
  .
  PART 3: COMMON TASKS
  .
  You may want to swap in a new set of SHCDS, because you want to
  increase the size of the SHCDS or you want to change the volume
  where the SHCDS resides.  You must use the VARY SMS,SHCDS
  command when making changes to the SHCDS in order for SMSVSAM
  to know about the SHCDS. Do not delete an active or spare SHCDS
  even if SMSVSAM is not active.  Do not move a SHCDS from one
  volume to another, because the SHCDS naming convention depends
  on the volume to match the SHCDS name.
  .
  NOTE: Do not delete and redefine an active or spare SHCDS
  without first deleting the SHCDS from SMSVSAM using the
  command - V SMS,SHCDS(shcdsname),DELETE.  SMSVSAM remembers
  the SHCDSs from one SMSVSAM recycle to the next. You must
  tell SMSVSAM that the SHCDS is no longer an active or
  spare SHCDS.
  .
  A common error is to delete and redefine the SHCDS without
  deleting the SHCDS from SMSVSAM  - for example,  when
  SMSVSAM is not active. The correct way to communicate
  changes for the SHCDS is through the command - V SMS,SHCDS.
  Once you have deleted a SHCDS using the command
  V SMS,SHCDS(shcdsname),DELETE, you can then safely use
  IDCAMS DELETE and DEFINE to modify your SHCDS.
  .
  NOTE:  Do not move a SHCDS from one  volume to another,
  because the SHCDS naming convention depends on the volume
  to match the SHCDS name.
  Remember that once you've added 2 Active SHCDS and 1 Spare SHCDS
  you will not be allowed delete them when using the command, Vary
  SMS,SHCDS(dsname),delete.  To make a swap, you must add the new
  SHCDS first and delete the old SHCDS to make sure you stay
  within criteria.  For example, if you have:
  .
  16.40.09 SYSTEM1           d sms,shcds
  IGW612I 16:40:10    DISPLAY SMS,SHCDS
  Name                      Size    %UTIL Status  Type
  TOOSMALL.VXP0301         7200Kb     5%  GOOD    ACTIVE
  TOOSMALL.VXP0302         7200Kb     5%  GOOD    ACTIVE
  WRONGVOL.VXP0201         7200Kb     5%  GOOD    SPARE
  .
  Issue these commands:
  V SMS,SHCDS(JUSTRITE.VXP0301),NEW
  V SMS,SHCDS(JUSTRITE.VXP0302),NEW
  V SMS,SHCDS(RIGHTVOL.VXP0202),NEWSPARE
  .
  Now you have:
  SYSTEM1           d sms,shcds
  IGW612I 16:45:49    DISPLAY SMS,SHCDS
  Name                      Size    %UTIL Status  Type
  TOOSMALL.VXP0301         7200Kb     5%  GOOD    ACTIVE
  TOOSMALL.VXP0302         7200Kb     5%  GOOD    ACTIVE
  JUSTRITE.VXP0301        14400Kb     2%  GOOD    ACTIVE
  JUSTRITE.VXP0302        14400Kb     2%  GOOD    ACTIVE
  WRONGVOL.VXP0201         7200Kb     5%  GOOD    SPARE
  RIGHTVOL.VXP0202         7200Kb     5%  GOOD    SPARE
  .
  Then you can issue:
  V SMS,SHCDS(TOOSMALL.VXP0301),DELETE
  V SMS,SHCDS(TOOSMALL.VXP0302),DELETE
  V SMS,SHCDS(WRONGVOL.VXP0201),DELETE
  .
  Which will leave you with:
  SYSTEM1           d sms,shcds
  IGW612I 16:47:07    DISPLAY SMS,SHCDS
  Name                      Size    %UTIL Status  Type
  JUSTRITE.VXP0301        14400Kb     2%  GOOD    ACTIVE
  JUSTRITE.VXP0302        14400Kb     2%  GOOD    ACTIVE
  RIGHTVOL.VXP0202         7200Kb     5%  GOOD    SPARE
  See 4.56.12  Changing the State of Coupling Facility Cache
  Structures and Volumes in MVS System Commands for information
  on the VARY command.
  .
  PART 4: SYMPTOMS OF HAVING PROBLEMS WITH SHCDS DEFINITION/USAGE
  .
  The following symptoms result from this set of steps.
  Please note that this is NOT a valid way to change the
  way the SHCDSs are defined.  See the section above for the
  recommended way of redefining your SHCDS.
  - Terminate SMSVSAM
  - Delete all SHCDSs (could also happen if delete some SHCDSs)
  - Redefine SHCDSs
  - Bring up SMSVSAM
  DUMP00 TITLE=COMPID=DF122,CSECT=IGWXSS90+0890,DATE=10/13/01,
           MAINTID= NONE   ,ABND=0F4,RC=00000024,RSN=67260989
  DUMP01 TITLE=COMPID=DF122,CSECT=IGWXSS91+0628,DATE=10/13/01,
          MAINTID= NONE   ,ABND=0F4,RC=00000024,RSN=67610382
  RSN67610382 67610382
  --------------------------------------------------------------
  SHCDS has CISIZE=6K and is added successfully.
  Things can go along fine for a while and then you get :
  DUMP00 TITLE=COMPON=MEDIA MANAGER, COMPID=DF106, ISSUER=ICYFRR
      DUMP TAKEN TIME=15.06.59 DATE=05/31/2002
      SYSTEM ABEND CODE=0C4  REASON CODE=00301314
      MODULE=IEANUC01 CSECT=ICYSTOR
  --------------------------------------------------------------
  Non-linear SHCDS - defined as a PS or whatever is default:
  On system2:
  15.46.35 SYSTEM2   IGW602E ADD SHARE CONTROL DATA SET FAILED,
  SYS1.DFPSHCDS.NONLINNC.VSPLXP2 IS NOT A VSAM LINEAR DATA SET
  On system1:
  15.46.35 SYSTEM2   IGW602E ADD SHARE CONTROL DATA SET FAILED,
  SYS1.DFPSHCDS.NONLINNC.VSPLXP2 IS NOT A VSAM LINEAR DATA SET
  .
  then later:
  DUMP00 TITLE=COMPON=MEDIA MANAGER, COMPID=DF106, ISSUER=ICYFRR
           SYSTEM ABEND CODE=0C4  REASON CODE=00301314
           MODULE=IEANUC01 CSECT=ICYSTOR
  --------------------------------------------------------------
  During Server initialization, insufficient access authority
  to SHCDS. Previously defined SHCDS are deleted.
  ICH408I JOB(SMSVSAM ) STEP(SMSVSAM ) 744
    SYS1.DFPSHCDS.ACTIVE2.VSPLXPK CL(DATASET ) VOL(USRPAK)
    INSUFFICIENT ACCESS AUTHORITY
    FROM SYS1.DFPSHCDS.* (G)
    ACCESS INTENT(UPDATE )  ACCESS ALLOWED(NONE   )
  IEF196I IEC161I 040(056,006,IGG0CLFT)-002,IEESYSAS,SMSVSAM,SYS00
  IEC161I 040(056,006,IGG0CLFT)-002,IEESYSAS,SMSVSAM,SYS00001,,,
  IEF196I IEC161I SYS1.DFPSHCDS.ACTIVE2.VSPLXPK
  IEC161I SYS1.DFPSHCDS.ACTIVE2.VSPLXPK
  .
  IEA794I SVC DUMP HAS CAPTURED: 760
  DUMPID=001 REQUESTED BY JOB (SMSVSAM )
  DUMP TITLE=COMPID=DF122,CSECT=IGWXSI20+0490,DATE=04/16/00,MAINT
           ID= NONE   ,ABND=0F4,RC=00000024,RSN=67510404
  RSN67510404 67510404
  .
  *IGW611A SHARE CONTROL DATA SET NEVER ASSIGNED
  *IGW609A NO SPARE SHARE CONTROL DATA SETS EXIST. IMMEDIATE ACTIO
   REQUIRED
  ----------------------------------------------------------------
  During Server initialization, insufficient access to SHCDS
  During initialization on a new system, a previously defined
  SHCDS might be deleted.
  With OW49746, we will fail the initialization process.
  IEF196I IEF237I 081F ALLOCATED TO SYS00002
  IEF196I ICH408I JOB(IEESYSAS) STEP(SMSVSAM )
  IEF196I   SYS1.MVSRES.MASTCAT CL(DATASET ) VOL(USRPAK)
  IEF196I   INSUFFICIENT ACCESS AUTHORITY
  IEF196I   ACCESS INTENT(UPDATE )  ACCESS ALLOWED(NONE   )
  ICH408I JOB(IEESYSAS) STEP(SMSVSAM ) 785
    SYS1.MVSRES.MASTCAT CL(DATASET ) VOL(USRPAK)
    INSUFFICIENT ACCESS AUTHORITY
    ACCESS INTENT(UPDATE )  ACCESS ALLOWED(NONE   )
  IGW601E ADD SHARE CONTROL DATA SET FAILED, 790
  UNABLE TO ALLOCATE SYS1.DFPSHCDS.ACTIVE.VSPLXPK
  ----------------------------------------------------------------
  During initialization on a new system, a previously defined
  SHCDS might be deleted.
  Instead, we will fail the initialization process.
  IGW619I ACTIVE SHARE CONTROL DATA SET 949
  SYS1.DFPSHCDS.ACTIVE2.VSPLXPK ADDED.
  IEF196I IEF237I 081F ALLOCATED TO SYS00002
  IGW619I ACTIVE SHARE CONTROL DATA SET 951
  SYS1.DFPSHCDS.ACTIVE.VSPLXPK ADDED.
  IGW601E ADD SHARE CONTROL DATA SET FAILED, 952
  UNABLE TO ALLOCATE SYS1.DFPSHCDS.SPARE.VXP0201
  IEF196I IEF237I 081F ALLOCATED TO SYS00003
  IGW619I SPARE SHARE CONTROL DATA SET 954
  SYS1.DFPSHCDS.SPARE.VSPLXPK ADDED.
  ----------------------------------------------------------------
  During initialization on a new system, a SHCDS that is on an
  offline volume, will be deleted.
  14.33.02 SYSTEM1          *IGW615W SHARE CONTROL DATA SET
   SYS1.DFPSHCDS.ACTIVE4.VXP0302 HAS FAILED
  .
  PART 5: FALLBACK PROCEDURE
  .
  **** IMPORTANT ********
  PRIOR TO PERFORM FALLBACK PROCEDURE, A DSS PRINT OF THE ACTIVE
  SHCDS SHOULD BE OBTAINED AND PROVIDED TO IBM WHEN REPORTING YOUR
  YOUR PROBLEM.
  **********************************************************
  For some SHCDS errors, FALLBACK is the only way to correct the
  problem and to get the SMSVSAM to intialize successfully again.
  If you get repeated abends with the prefix '67' in the RSN code,
  then you know it's time to do a FALLBACK.
  .
  NOTE: *** IPL would NOT help because SHCDS is remembered from
            one IPL to another ***
  .
  FALLBACK procedure is documented in z/OS V1R3.0 DFSMSdfp Storage
  Administration Reference.
  (The FALLBACK procedure described in the manual is more complete
  and should be used ONLY IF you are going to disable RLS for
  real. The FALLBACK procedure described below is intended for
  recovering corrupted SHCDS so that you can begin RLS processing
  again.)
  In a nutshell, FALLBACK will reformat the SHCDS and hence clear
  all the errors.
  FALLBACK involves:
    - Terminate all servers in the plex by using the command
      "VARY SMS,SMSVSAM,TERMINATESERVER" on each server.
    - Issue "VARY SMS,SMSVSAM,FALLBACK"
    - Reply to the WTOR that you are sure you want to do FALLBACK
    - Reactivate the server one at a time using -
      "VARY SMS,SMSVSAM,ACTIVE"
      One the first system, you will be asked to specify 2 ACTIVE
      and 1 SPARE SHCDS.
      To add an active SHCDS: "VARY SMS,SHCDS(SHCDS_name),NEW"
      To add a spare SHCDS: "VARY SMS,SHCDS(SHCDS_name),NEWSPARE"
  So far, we know the following errors would require FALLBACK:
    - Abend0F4 RC24 RSN675D0355 (check GRS / MIM set up!)
    - Abend0F4 RC24 RSN67260989
  Additional keywords:
  MSGIGW608A MSGIGW609A MSGIGW611A
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• 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