PI92347: -STO DB(DBNAME) SP(*) COMMAND WITHOUT THE PART LEVEL KEYWORD RESULTS IN NO STATUS CHANGE FOR THE TABLE 18/03/23 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Create and -STOP a PBG object :
  
  L#@SSJW  TS    0001 STOP
  L#@SSJW  TS
  L#@ISJWB IX   L0001 STOP
  L#@ISJWB IX    L*
  
  Add a partition - ALTER TABLE PDUTL01.L#@TSJW ADD PARTITION;
                    COMMIT;
  so the object now looks like this :
  
  L#@SSJW  TS    0001 STOP
  L#@SSJW  TS    0002 RW
  L#@SSJW  TS
  L#@ISJWB IX   L0001 STOP
  L#@ISJWB IX   L0002 RW
  L#@ISJWB IX    L*
  
  Stop the object with -STO DB(L#@DSJW) SPACENAM(*) but the status
  of the object remains the same :
  
  L#@SSJW  TS    0001 STOP
  L#@SSJW  TS    0002 RW
  L#@SSJW  TS
  L#@ISJWB IX   L0001 STOP
  L#@ISJWB IX   L0002 RW
  L#@ISJWB IX    L*
  .
  Problem 2: Stop workfile hang after pi76466 / ui51665.
             Steps to illustrate:
             a) 'select * from sysibm.systables' using spufi with
                'autocommit no'.
             b) -stop db(..) space(dsn4k01)
                The stop command hangs as spufi thread holds
                s-dbd lock.
  Additional keywords: ZSA2
  

Local fix

• Issue a part-level stop cmd :
  
  -STO DB(L#@DSJW) SPACENAM(*) PART(2)
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of Db2 for z/OS who use the STOP                   *
  * DB and DISPLAY DB command are affected.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Code is updated to fix the two                               *
  * following problems:                                          *
  *                                                              *
  * STOP DB command without PART does not                        *
  * work correctly when object is a                              *
  * PBG tablespace and this has parts in                         *
  * STOP status and RW status.                                   *
  *                                                              *
  * STOP DB and DB DISPLAY command do                            *
  * not work correctly for the Work File                         *
  * database when a SFUFI thread runs a                          *
  * SELECT statement and holds a Share                           *
  * lock.                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * The customer needs to apply this PTF                         *
  * to fix the problem related to the STOP DB                    *
  * command. This PTF will fix PE APARs:                         *
  * V11 - PI75527/UI47964 and PI76466/UI51666                    *
  * V12 - PI78087/UI47516 and PI76466/UI51665.                   *
  ****************************************************************
  

Problem conclusion

• Two problems are resolved with this fix:
  
  --STOP DB command without PART does not stop the parts of a
  PBG tablespace when it has parts in stop status and parts in
  RW status. The reason this causes the problem is because objects
  were treated as a stopped object. To fix the problem all parts
  of the PBG tablespace are checked if they have the RW status.
  
  --The STOP DB command with spacename and DISPLAY DB command
  for the work file database are hung and waiting for the COMMIT
  of the SPUFI thread running of SELECT statement. For Work File
  case the STOP DB command without spacename still holds an
  exclusive lock but the STOP command with spacenane holds an
  UPDATE lock so it will not block the DISPLAY DB command.
  

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:

  UI54688 UI54731

Modules/Macros

• DSNFTDIR DSNILSTS DSNTDSTP DSNFCDIR DSNTDMSG DSNTDMST
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI54731

     UP18/03/29 P F803 {

• RB10 PSY UI54688

     UP18/03/29 P F803 {

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.