II13024: INFO APAR TO DOCUMENT STEPS FOR PROCESSING IMS MAINTENANCE VIA ACCEPT BYPASS APPLYCHECK PROCESSING - UPGRADE

APAR status

• INTRAN

Error description

• The following are the steps required when:
  A. Processing IMS maintenance using ACCEPT BYPASS APPLYCHECK
     processing.
  B. Removing features from the Gen'd IMS system.
  C. Anything that requires the re-building of Target
     zones/datasets from the Distribution zones/datasets.
  
     ** NOTE see Informational APAR II08928 for steps necessary
        for IMS V7 and below.  **
  
   **NOTE**: This process only works if ACCJCLIN was
             specified in the distribution zone when
             IMS was initially installed and has
             remained.
  
  1) Backup the SMP/E datasets (Global, Target, Distribution
     zones, smpmts, etc.) as well as your Target and
     Distribution datasets (just in case fallback is
     necessary).
  
  2) Either ACCEPT or identify all outstanding service for all
     products present in the IMS Distribution and Target zones.
     The following are sample SMP/E control statements to identify
     service has been applied only:
        //SMPCNTL DD *
          SET BDY(targetzonename) .
           LIST NOACCEPT NOSUP.
  
  3) UNLOAD the Target zone DDDEFs using the SMP/E UNLOAD command.
     The following are sample SMP/E control statements and
     additional JCL to accomplish this:
        //SMPCNTL DD *
          SET BDY(targetzonename) .
          UNLOAD DDDEF .
        //SMPPUNCH DD DSN=IMS.SMPUNLD,DISP=(,CATLG),
        // UNIT=SYSDA,SPACE=(TRK,(5,1),RLSE),
        // DCB=(RECFM=FB,BLKSIZE=16000,LRECL=80)
  
  4) LIST the Target zone.
     a) This is done to determine the name of the SMP/E options
        entry being used.  This information will be used in a
        later step.
        The following are sample SMP/E control statements to
        accomplish this:
        //SMPCNTL DD *
          SET BDY(targetzonename) .
          LIST TARGETZONE .
  
  5) Scratch and re-allocate the following data sets:
  
     * SMPMTS
     * SMPSTS
     * SMPSCDS
     * SMPLTS
     Note:  The SMP/E cleanup command can be used instead of
            scratching and re-allocating SMPMTS, SMPSTS and
            SMPSCDS.  SMPLTS will need to be scratched and
            re-allocated.
  
  6) ZONEDELETE and Redefine the Target zone.
     a) Zonedelete the Target zone.
        The following are sample SMP/E ZONEDELETE control
        statements:
        //SMPCNTL DD *
          SET BDY(targetzonename) .
          ZDEL TZONE(targetzonename) .
     b) Delete and redefine Target CSI (the VSAM cluster).
        Note:  If multiple zones are contained in the same CSI
               as the target zone DO NOT delete and redefine the
               cluster as you will loose the information for those
               zones also - in this case skip this step (6b) as it
               is for performance.
  
  7) Re-Initialize the new Target zone.
     a) Repro GIMZPOOL to the new Target zone.
        (Initialization of the new Target zone requires
        SYS1.MACLIB(GIMZPOOL) be REPRO'd into the new
        Target zone cluster to seed/prime it).
        Note: If step 6b was skipped because the target zone is
              in the same VSAM cluster as other zones skip this
              step (7a) also.
   b) Rebuild the relationship between the old Distribution zone
      and the new Target zone.
      The following are sample SMP/E control statements to
      do this:
      //SMPCNTL DD *
        SET BDY(GLOBAL).
          UCLIN.
            ADD GZONE ZONEINDEX(
            (targetzonename,target.zone.cluster.name,TARGET)
                                ).
          ENDUCL.
  
         SET BDY(targetzonename).
           UCLIN.
             ADD TARGETZONE(targetzonename)
                 SREL(P115)
                 RELATED(dlibzonename)
                 OPTIONS(xxxxxx).
           ENDUCL.
           ** Note:  The name of the SMP/E Options entry can be
           determined from the output from step 4.
     c) Run UCLIN for the Target zone DDDEFs using the file
        created in step 3 above.
         The following are sample SMP/E control statements and
         additional JCL accomplish this:
              //SMPCNTL DD *
                SET BDY(targetzonename) .
              //        DD DSN=IMS.SMPUNLD,DISP=SHR
   ** NOTE return code 4 is expected from this step
      due to DDDEFs being added as opposed to replaced.
  
  8) Run SMP/E RECEIVE and ACCEPT GROUPEXTEND BYPASS(APPLYCHECK)
     commands for the PTFs to be processed.
     Be sure to RECEIVE current Enhanced Holddata
     (see http://service.boulder.ibm.com/390holddata.html
     for additonal information) before SMP/E processing and
     to resolve PE's during SMP/E processing.  Once SMP/E
     processing is complete, run SMP/E REPORT ERRSYSMODS to
     identify missing HIPERs and PE exposure.
     The following are sample SMP/E control statements for
     running the ACCEPT
      //SMPCNTL DD *
        SET BDY(GLOBAL) .
            RECEIVE LIST
                 SYSMODS
                 HOLDDATA .
       SET BDY(dlibzonename).
           ACCEPT GROUPEXTEND
               BYPASS(APPLYCHECK
                      HOLDCLASS(ERREL,UCLREL)
                      HOLDSYSTEM
                      )
                 SOURCEID(RSU09*,RSU10*,RSU11*,RSU120*,etc)
                 PTFS .
  
    The following are sample SMP/E control statements for
    running the REPORT ERRSYSMODS command:
      //SMPCNTL DD *
      SET    BOUNDARY (GLOBAL)   .
       REPORT ERRSYSMODS ZONES(targetzonename) .
  
   Note: This step is for maintenance processing only
  
  9) Run ZONEMERGE CONTENT to merge the Distribution zone into
     the new Target zone.
     The following are sample SMP/E control statements to
     do this:
     //SMPCNTL DD *
       SET BDY(targetzonename) .
           ZONEMERGE(dlibzonename)
               INTO(targetzonename)
               CONTENT
                 .
  
  10) Run the SMP/E GENERATE command to create the JCL to be used
      for building target libraries.  **NOTE This is
      dependent on ACCJCLIN being set in the Distribution zone
      before the IMS FMID's were ACCEPTed.  The following are
      sample SMP/E control statements and additional JCL
      accomplish this:
       //CNTL     DD  DSN=yourpds,DISP=SHR
       //SMPPUNCH DD  DSN=IMS.GENERATE,
       //             DISP=(,CATLG),UNIT=SYSDA,
       //             SPACE=(CYL,(25,5),RLSE),
       //             DCB=(RECFM=FB,LRECL=80,BLKSIZE=16000)
       //SMPCNTL DD *
        SET BDY(targetzonename) .
        GENERATE JOBCARD(CNTL,J) REPLACE.
  
       ** NOTE - In this example the dataset for DD 'CNTL'
                 needs to have a member named 'J' which contains a
                 sample JOB card.
  
  11) Run jobs created by SMP/E GENERATE which are in dataset
      IMS.GENERATE (from step 10) to synchronize the target
      libraries with their distribution libraries.
  
        * Job SMPLTS will encounter a return code of 4 due
          to unresolved external references (IEW2454W).
          All other jobs should end with a return code of 0.
  
  12) Run an 'ALL' IMS system definition Stage1 and Stage2.
      Notes: If Large GEN (LGEN) support is used you will need
            to allocate the IMS.LGENIN and IMS.LGENOUT datasets
            before running the IMS SYSDEF preprocessor (The
            preprocessor performs Stage1 for LGEN).
  
  13) Run JCLIN using the IMS Stage2 as input.
     Notes: If the large GEN (LGEN) support is used, the output
            from the DFSIVG10 program must be used as input to
            JCLIN.  (The Stage2 issued as the input to DFSIVG10)
            For assistance with DFSIVG10, refer to IVP job
            IV_C401J or skeleton DFSIXSC5 (in IMS.SDFSSLIB).
            See step 10 for sample JCLIN statements.
  
     WARNING: If the large GEN (LGEN) support is used, JCLIN
              processing must be performed after Stage2
              execution!
  
  14) Re-APPLY any IMS service that was not accepted.
      This service was identified in step # 2.
  
  15) Re-APPLY service for other products that was not accepted.
      This service was identified in step # 2.
  *************************** Butterweck 08/01/12 **********
  

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