OA36158: ENABLE THE Z/OS 1.13 SPOOL MIGRATION FUNCTION.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • This APAR enables the SPOOL Migration function
    
    Verification Steps:
    1) If spool migration is attempted with this enablement APAR not
        applied, you will encounter:
    
     $HASP003 RC=(73),M SPL(SPOOL1)  - ALL MEMBERS ARE NOT AT THE
     $HASP003 REQUIRED PRODUCT/SERVICE LEVEL
    .
    Additional Keywords:
    ======================
    $MSPL $MSPOOL $M
    .
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of HJE7780.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Enablement of the SPOOL Migration       *
    *                      function.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SPOOL Migration function had been disabled.
    

Problem conclusion

Temporary fix

  • *** * TEMPORARY FIX MAY BE OBTAINED FROM DLL OR INFO/ACCESS ****
    ******************* OA36158  DECK AVAILABLE ********************
    

Comments

  • TYPE/RESTART(HOT) IPL/REQUIRED(NO) CLPA(NO)
    
    SPOOL Migration function has been enabled.
    Two new web pages have been updated with information about
    the SPOOL Migration function.
    
    URL for the new SPOOL Migration web page:
    http://www-03.ibm.com/systems/z/os/zos/
     jes2_spoolmigration.html
    
    URL for the new SPOOL Migration FAQ pdf file:
    http://publibz.boulder.ibm.com/zoslib/pdf/
     jes2_spoolmigrationFAQ.pdf
    
     *======================================================*
     * SPOOL migration may not function correctly until all *
     * members of the MAS have this APAR's PTF and all the  *
     * PREREQs of this APAR applied.                        *
     *======================================================*
    
    The information in the following JES2 manuals/publications
    is missing/incorrect:
    
    1.z/OS V1R13.0 JES2 Messages      SA22-7537-11
    
    Under Chapter 8.0 Four-hundreds, the following message is added:
    
    $HASP447
    
    Explanation:
    
    WARM start denied - Active SPOOL migration detected
    
    A member cannot be warm started while a SPOOL Migration is in
    progress.  Refer to JES2 Commands, Migrating SPOOL volume
    overview, MAS member restrictions, for more information on MAS
    member restrictions.
    
    System action: JES2 terminates.
    
    Operator response: Wait for SPOOL migration to complete before
                       retrying to warm start a JES2 member.
    
    System Programmer Response: None.
    
    Detecting Module: HASPIRMA
    
    Routing Code: 1,2,10
    
    Descriptor Code: 4
    
    Updates will only be made to the 'JES2 Messages' manual in
    future JES2 releases.
    
    ========================================================
    
     The information in the following JES2 manuals/publications
     is missing/incorrect:
    
     1.z/OS V1R13.0 JES2 Commands      SA22-7526-12
    
     The text for Chapter 1. Controlling JES2, Migrating
     SPOOL volumes, should have the following text and
     table added at the end of the Moving and merging
     SPOOL volumes section:
    
     The following table summarizes the limitations
     when using a MOVE or MERGE Migration, helping the
     user determine the type of migration that is best
     for their environment:
    
                                                    | M | M
                                                    | O | E
                                                    | V | R
                                                    | E | G
                                                    |   | E
    ------------------------------------------------+---+---
     Source SPOOL volume must be INACTIVE           | X |
    ------------------------------------------------+---+---
     Target SPOOL volume must be ACTIVE             |   | X
    ------------------------------------------------+---+---
     The Source SPOOL volume's number of records    |   |
       per track must be less than or equal to the  |   |
       Target SPOOL volume's records per track      | X | X
    ------------------------------------------------+---+---
     The Target SPOOL volume must support the       |   |
       Source SPOOL volume's LARGEDS settings       | X |
    ------------------------------------------------+---+---
     The number of tracks per track group is        |   |
       inherited from the Source SPOOL volume       | X |
    ------------------------------------------------+---+---
     The Source SPOOL volume cannot use absolute    |   |
       addressing                                   | X |
    ------------------------------------------------+---+---
     The Target SPOOL volume cannot use absolute    |   |
       addressing                                   | X | X
    ------------------------------------------------+---+---
    
    ===============================================
    
     The text for Chapter 1. Controlling JES2, Migrating
     SPOOL volumes, should have the following sentence
     added in the Moving and merging SPOOL volumes section
     after the sentence "However, the extent($DAS) for
     SPOOL1 still exists and can be displayed with a special
     MAPPED status by the command $DSPOOL(SPOOL1).":
    
     A SPOOL volume will stay in the MAPPED status until
     all jobs that were assigned space on the volume are
     purged from the system. JES2 is no longer using the
     data set on the MAPPED volume.
    
    ===============================================
    
     The text for Chapter 1. Controlling JES2, Migrating
     SPOOL volumes, should have the following section
     added at the end:
    
     Migrator and Assistants
       The "Migrator" is a subtask on a MAS member that
       coordinates a specific SPOOL migration. "Migrator"
       is also used to refer to the MAS member running
       the Migrator subtask.
    
       An "Assistant" or migration assistant is the subtask
       that runs on each MAS member to manage runtime duties
       on that MAS member for any active SPOOL migration.
       The Migrator and Assistants communicate with each other
       using messages sent to JESXCF mailboxes to coordinate
       activity for a specific SPOOL migration.
    
    ===================================================
    
     The "Migration Recovery Considerations" section to be added
     in Chapter 1. Controlling JES2, Migrating SPOOL volumes,
     as shown below:
    
     Migrating SPOOL volumes
         SPOOL migration terms
         SPOOL migration phases
         MAS migration restrictions
         Moving and merging SPOOL volumes
         Calculating tracks
         Allocating tracks
         Migration Recovery Considerations   <--To be added here
    
    ====================================================
    
     The following to be added in Chapter 1, under the
     "Migration Recovery Considerations" section :
    
     Migration Recovery Considerations:
    
      This section describes a rare circumstance where a Source
      and/or Target data set connectivity may be lost during a
      migration and  what options are available in such an event.
      Lost connectivity is discussed from both "JES2 active" and
      "JES2 warmstart" context.  Also covered are actions to take
      if migration appears hung or a MAS member acting as Migrator
      goes down.
    
     JES2 active -- Source and/or Target data set communication
      path is lost.
    
      What are the considerations if a communication path to Source
      and/or Target volume is lost? The migration is interrupted and
      the operator is presented with a $HASP807 message detailing
      which paths have been lost and corresponding options, followed
      by a $HASP814 requesting the operator response.   If the
      migration can be cancelled,  then options are RETRY (continue
      migration) or CANCEL.  If data set path(s) can be re-
      established then do so and respond RETRY and the migration
      will continue. If path communication cannot be reinstated,
      then respond CANCEL to end the migration.
    
      If the migration cannot be cancelled, then options are RETRY
      (continue migration) or QUIT (cancel migration and use Source
      volume data set) or FORCECOMPLETE  (complete migration and use
      Target volume data set).  If data set path(s) can be re-
      established then do so and respond RETRY and the migration
      will continue. If communication path(s) cannot be re-
      established, then one must decide whether to QUIT migration
      and just use Source data set as is, or FORCECOMPLETE thereby
      finishing the migration and using Target data set as is.
      Because of when the problem occurred, there are some data
      updates that only exist on the Source and others that only
      exist on the Target.  Deciding which option to use (QUIT or
      FORCECOMPLETE) will depend on which volume was lost and how
      far the CATCHUP phase progressed. There may be stale data or
      missing data if either QUIT or FORCECOMPLETE are selected.
    
     Warm start -- Source and/or Target data set cannot be allocated
    
      What are the warm start considerations if migration had been
      active and JES2 is unable to allocate Source and/or Target
      data sets on an all member warm start?  The operator will be
      presented with msgHASP867 and msgHASP853.  The $HASP867
      message will identify the data set(s) which cannot be
      allocated and the $HASP853 presents those responses listed
      below that are valid for this migration:
    
      QUIT replied
      Terminate JES2 warm start. Proceed to rectify the allocation
      problem and restart JES2.  This is the preferred action.
    
      GO replied
      Halt the missing volume. There are three situations handled:
        1.If volume is Target of a mapped volume, then both Target
          and all volumes mapped to the Target volume are halted.
        2.If an active migration is using the volume as Target, then
          cancel migration - unless it has reached the CLEANUP
          phase. This could result in stale or missing data if the
          migration is in the CATCHUP phase.  If the migration
          reached the CLEANUP phase, then the migration is
          completed and the Source volume halted.
        3.If volume is Source of an active migration, then
          cancel migration - unless it has reached the CLEANUP
          phase.  This could result in stale or missing data if
          the migration is in the CATCHUP phase.  If the
          migration reached the CLEANUP phase, then the
          migration is completed and the Source volume halted.
    
      PURGE replied
      Delete the missing volume. There are three situations handled:
        1.If volume is Target of a mapped volume, then the Target
          and all volumes mapped onto the Target are deleted.
        2.If an active migration is using the volume as Target, then
          cancel migration regardless of migration phase.
        3.If volume is Source of an active migration, then delete
          the volume and cancel the migration.
    
     SPOOL migration appears to be hung. How do I determine what
     it is waiting for?
      Issue the $D SPL command to determine which MAS member(s) the
      migration is waiting for. Then issue the $D MEMBER command to
      determine if the migration is waiting on the hot start of a
      failed member.  When a SPOOL migration is started, all active
      members of a MAS (JESplex) participate in the migration
      through their Assistant subtasks. If the JES2 address space
      has abended and is hot startable, the migration cannot
      complete until that JES2 address space hot starts and
      completes its portion of the migration, or the system is
      partitioned out of the Sysplex.
    
     The MAS member acting as the Migrator for my SPOOL Migration
     went down. What happened to my SPOOL Migration?
      If possible, another MAS member will automatically take over
      as the Migrator and either cancel or complete the Migration.
      This action is termed Migrator Takeover. The member taking
      over will issue a $HASP808 message denoting this action.  The
      migration will complete if it has reached CATCHUP migration
      phase, otherwise the migration will be cancelled.
    
     Updates will only be made to the 'JES2 Commands' manual in
     future JES2 releases.
    
    Searchable keywords:
    MSGHASP447 MSG$HASP447 MSGHASP807 MSG$HASP807 MSGHASP808
    MSG$HASP808 MSGHASP814 MSG$HASP814 MSG$HASP853 MSG$HASP867
    
    APAR OA36158 prereq's (and sup's) for FMID HJE7780:
    Pre's: GA38240 GA37847 GA37332 GA36844 GA36471 GA36180 GA36140
    

APAR Information

  • APAR number

    OA36158

  • Reported component name

    JES2

  • Reported component ID

    5752SC1BH

  • Reported release

    780

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Installability

  • Submitted date

    2011-04-11

  • Closed date

    2012-02-24

  • Last modified date

    2012-07-17

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

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

    UA64366

Modules/Macros

  •    HASPIRMA
    

Publications Referenced
SA22753711 SA22752612      

Fix information

  • Fixed component name

    JES2

  • Fixed component ID

    5752SC1BH

Applicable component levels

  • R780 PSY UA64366

       UP12/03/14 P F203

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

780

Operating system(s):

MVS, z/OS

Reference #:

OA36158

Modified date:

2012-07-17

Translate my page

Machine Translation

Content navigation