PM83858: THE STOP(QUIESCE) COMMAND RECEIVE INCONSISTENT COMPLETED CODE

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When issuing the UPD DB NAME(xxxx) STOP(QUIESCE) command on
    database in QUIESCED status, IMS will create a recovery
    point for the database. But for FP DB with multiple areas,
    it is possible to have different quiesce status on each areas.
    If there is no area in QUIESCE status, IMS return CC=C
    (COMMAND COMPLETE FOR NONE) because IMS does not create a
    recovery point.
    But if there are some areas in QUIESCE status, IMS should
    return a meaningful complete code because IMS created a
    recovery point. We need to take care two situations.
    1) IMS should return CC=0 if IMS created a recovery point
       for all the areas of the DB.
    2) or return CC=8 (COMMAND COMPLETE FOR SOME) if IMS created
       a recovery point for some areas (not all areas) of the DB.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IMS V11 users who issue the                  *
    *                 UPDATE DB|AREA|DATAGRP STOP(QUIESCE)         *
    *                 command.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: After the user issues an UPDATE AREA    *
    *                      START(QUIESCE) OPTION(HOLD) command     *
    *                      for each Area under a Fast Path DEDB,   *
    *                      the command returns a CC=C to the       *
    *                      TSOSPOC when the user subsequently      *
    *                      issues an UPDATE DB STOP(QUIESCE) for   *
    *                      the DEDB.                               *
    *                                                              *
    *                      If only several Areas of a Fast Path    *
    *                      DEDB are in a quiesced state and the    *
    *                      user issues UPDATE AREA STOP(QUIESCE)   *
    *                      for the DEDB, the command returns a     *
    *                      CC=C even though it successfully        *
    *                      released the Areas that were in a       *
    *                      quiesced state.                         *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    The user can issue an UPDATE AREA START(QUIESCE) OPTION(HOLD)
    command for each Area of a Fast Path DEDB to put them in a
    quiesced state.  To release them from the quiesced state, the
    user can then issue an UPDATE DB STOP(QUIESCE) command for the
    DEDB.  The command successfully releases each Area, however a
    completion code of 'C' (COMMAND COMPLETE FOR NONE) was returned
    on the TSOSPOC.  When performing the same scenario for HALDB
    partitions, the command correctly returns a completion code of
    '0' on the TSOSPOC.
    
    In a different scenario, it is possible to have only several
    Areas of a Fast Path DEDB or several partitions of a HALDB
    master in a quiesced state.  When the user issues the
    UPDATE DB STOP(QUIESCE) command it will successfully release
    the Areas or partitions that are in a quiesced state and
    return a completion code of 'C' (COMMAND COMPLETE FOR NONE).
    The completion code needs to be modified to indicate that
    some of the Areas or partitions were released successfully.
    

Problem conclusion

  • GEN:
    KEYWORDS:
    
    *** END IMS KEYWORDS ***
    The following parts were modified to address these issues:
    
    ************
    * DFSDBQ00 *
    ************
    For the UPDATE STOP(QUIESCE) command flow, DFSDBQ00 was changed
    to return a response line for each Fast Path Area or HALDB
    partition that could not be released by the command.  If all
    Areas / partitions failed, the command will continue to return
    a completion code of 'C' for the DEDB / HALDB master response
    line.  If only some of the Areas / partitions failed, the
    command will return a completion code of '8' (COMMAND COMPLETE
    FOR SOME) for the DEDB / HALDB master response line.
    
    ************
    * DFSDBQ40 *
    ************
    Originally, DFSDBQ40 primed the HALDB master entry of the
    internal quiesce list built by UPDATE STOP(QUIESCE) with a
    completion code of 'C'.  This change removes the priming of the
    HALDB master entry.  DFSDBQ40 was also changed to set a
    completion code of 'E9' for any partitions that could not be
    released by the UPDATE STOP(QUIESCE) command.
    
    ************
    * DBFDBQ50 *
    ************
    Originally, DBFDBQ50 primed the Fast Path DEDB entry of the
    internal quiesce list built by UPDATE STOP(QUIESCE) with a
    completion code of 'C'.  This change removes the priming of the
    Fast Path DEDB entry.  DBFDBQ50 was also changed to set a
    completion code of 'E9' for any Areas that could not be
    released by the UPDATE STOP(QUIESCE) command.
    
    
    ----
    A document change is needed in the following publication:
    IMS Version 11 Commands, Volume 2:
    IMS Commands N - V (SC19243102)
    Chapter 29. UPDATE Commands
    ----
    UPDATE AREA command
    ...
    STOP()
      QUIESCE
        Specifies that the DEDB areas named on the command should
        be made available again by releasing the quiesce on the
        areas.
    
        Unlike START(QUIESCE) where each database resource listed
        must be quiesced in order for the command to complete
        successfully, STOP will continue to process each listed
        resource even if some are not in quiesced state or cannot
        be released from quiesced state.  For those resources that
        are not in a quiesced state or cannot be released from a
        quiesced state, the command will return a response line
        identifying those resources.
    
    ----
    UPDATE DATAGRP command
    ...
    STOP()
      QUIESCE
        Specifies that the database group named on the command
        should be made available again by releasing the quiesce on
        the database group members.
    
        Unlike START(QUIESCE) where each database resource listed
        must be quiesced in order for the command to complete
        successfully, STOP will continue to process each listed
        resource even if some are not in quiesced state or cannot
        be released from quiesced state.  For those resources that
        are not in a quiesced state or cannot be released from a
        quiesced state, the command will return a response line
        identifying those resources.
    
    ---
    UPDATE DB command
    ...
    STOP()
      QUIESCE
        Specifies that the database named on the command should be
        made available again by releasing the quiesce on the
        databases.
    
        Unlike START(QUIESCE) where each database resource listed
        must be quiesced in order for the command to complete
        successfully, STOP will continue to process each listed
        resource even if some are not in quiesced state or cannot
        be released from quiesced state.  For those resources that
        are not in a quiesced state or cannot be released from a
        quiesced state, the command will return a response line
        identifying those resources.
    ...
    In Examples, replace Example 3 and 4 with the Example 3 and 4
    listed below.  Also add the new Example 5 listed below.
    
    Example 3 for UPDATE DB command
    TSO SPOC input:
     UPD DB NAME(DEDBJN22) START(QUIESCE) OPTION(HOLD)
         SET(TIMEOUT(60))
    TSO SPOC output:
     DBName    MbrName  CC
     DEDBJN22  IMS1      0
     DEDBJN22  IMS2      0
     DEDBJN22  IMS3      0
    Explanation: This example is of a successful quiesce and hold
    for Fast Path DEDB DEDBJN22 coordinated across three IMS.
    
    
    Example 4 for UPDATE DB command
    TSO SPOC input:
     UPD DB NAME(DEDBJN22) STOP(QUIESCE)
    TSO SPOC output:
     DBName   AreaName MbrName  CC CCText
     DEDBJN22          IMS1      C COMMAND COMPLETE FOR NONE
     DEDBJN22 DB22AR0  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
     DEDBJN22 DB22AR1  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
     DEDBJN22 DB22AR2  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
     DEDBJN22 DB22AR3  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
     DEDBJN22 DB22AR4  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
    
    Explanation:  This example attempts to release a quiesce on a
    DEDB.  DEDB DEDBJN22 consists of five areas.  The command
    failed because none of the areas were held in a quiesced state.
    A response line is returned for the DEDB name with CC=C
    (COMMAND COMPLETE FOR NONE) since none of the areas under the
    DEDB were in a state to be released.  A response line is also
    returned for each area.
    
    
    Example 5 for UPDATE DB command
    TSO SPOC input:
     UPD DB NAME(DEDBJN22) STOP(QUIESCE)
    TSO SPOC output:
     DBName   AreaName MbrName  CC CCText
     DEDBJN22          IMS1      8 COMMAND COMPLETE FOR SOME
     DEDBJN22 DB22AR0  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
     DEDBJN22 DB22AR3  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
     DEDBJN22 DB22AR4  IMS1     E9 DB IN WRONG STATE TO BE QUIESCED
    
    Explanation:  This example attempts to release a quiesce on a
    DEDB.  DEDB DEDBJN22 consists of five areas.  The command was
    partially successful because it was only able to release the
    quiesce on DB22AR1 and DB22AR2.  In this example, DB22AR0,
    DB22AR3, and DB22AR4 were not in a quiesced state.  A response
    line is returned for the DEDB name with CC=8 (COMMAND COMPLETE
    FOR SOME) since only some of the areas under the DEDB were in a
    state to be released.  A response line is also returned for
    each area that could not be processed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83858

  • Reported component name

    IMS V11

  • Reported component ID

    5635A0200

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-28

  • Closed date

    2013-03-08

  • Last modified date

    2013-04-02

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

    PM76444

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

    UK92384

Modules/Macros

  •    DBFDBQ50 DFSDBQ00 DFSDBQ40
    

Publications Referenced
SC19243102        

Fix information

  • Fixed component name

    IMS V11

  • Fixed component ID

    5635A0200

Applicable component levels

  • R100 PSY UK92384

       UP13/03/12 P F303

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:

IMS

Software version:

100

Reference #:

PM83858

Modified date:

2013-04-02

Translate my page

Machine Translation

Content navigation