PH58761: SPT01 INLINE LENGTH INFORMATION NOT AVAILABLE REASON 1AF07A90 TYPE 7EB39000

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer migrated one member (HS1A) of a data sharing group
  from Db2 V12 FL510 to Db2 V13 FL M100.
  They left member HS2A running on Db2 V12 runtime code.
  Member HS1A we started up on V13 Runtime code and ran the
  CATMAINT to M100. (CATMAINT UPDATE LEVEL V13R1M100 ).
  .
  All went well, when doing a DISPLAY GROUP DETAIL we could see
  the new catalog level and the code level each member was running
  on as
  we expected. They also saw this message in the Db2 12 HS2A:
  SPT01 INLINE LENGTH INFORMATION NOT AVAILABLE
  REASON 1AF07A90
  TYPE 7EB39000
  NAME
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Db2 12 for z/OS and Db2 13 for z/OS                      *
  * users of the -DISPLAY GROUP command.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * This APAR addresses the following                            *
  * issues with DISPLAY GROUP command                            *
  * output.                                                      *
  * (1) DISPLAY GROUP command output                             *
  * indicates that the inline length of                          *
  * directory table space SPT01 is not                           *
  * available:                                                   *
  * SPT01 INLINE LENGTH INFORMATION NOT                          *
  * AVAILABLE.                                                   *
  * (2) If the DISPLAY GROUP DETAIL                              *
  * command option is specified then the                         *
  * SPT01 INLINE LENGTH INFORMATION NOT                          *
  * AVAILABLE information can appear twice                       *
  * in the command output.                                       *
  * (3) When the SPT01 INLINE LENGTH                             *
  * INFORMATION NOT AVAILABLE information                        *
  * is displayed, the accompanying REASON,                       *
  * TYPE, and NAME information can contain                       *
  * uninitialized storage data.                                  *
  * (4) The Migration Readiness Report                           *
  * that is shown with the DISPLAY GROUP                         *
  * DETAIL option is specified, the                              *
  * information shown for an already                             *
  * migrated member can be confusing.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply corrective PTF when available                          *
  ****************************************************************
  DISPLAY GROUP is not properly displaying the SPT01 inline
  length. This can happen in both data sharing and non-data
  sharing in the following scenarios:
  (1) Data sharing - in the lower release in release coexistence
  cases and also in fallback situations.
  (2) Non-data sharing - in release fallback situations.
  

Problem conclusion

• Db2 code has been changed to address each of the four items
  noted in the Problem Description as follows:
  (1) DISPLAY GROUP output now properly shows the SPT01 INLINE
  LENGTH information as expected.
  (2) The SPT01 information, successfully displayed or not,
  should now only appear in DISPLAY GROUP output once.
  (3) Uninitialized storage is no longer displayed if SPT01
  INLINE LENGTH information cannot be displayed for some reason.
  Instead, the information shown in the REASON, TYPE and NAME
  fields will now contain zeroes, blanks or diagnostic
  information that will help determine what the problem is. This
  should greatly help with the problem diagnosis process in the
  future.
  (4) The Migration Readiness Report output has been changed as
  follows:
  - In data sharing where release coexistence is active,
  members that have already migrated to the next release of Db2
  will now show 'N/A' in the Migration Eligible column. This
  indicates that these members have already migrated to the next
  release of Db2.
  - The MIGRATION READINESS STATUS: readiness-text will now
  display the following: "MIGRATION IN PROGRESS TO DB2 13".
  - The REASON: reason-text will now show the following:
  "ALL REMAINING MEMBERS ARE READY FOR DB2 13".
  The following example shows how the Migration Readiness report
  will look when DISPLAY GROUP with DETAIL is executed on a Db2
  12 member that is in a Db2 12/13 release coexistence data
  sharing group:
  ---------------------------------------------------------------
  MIGRATION READINESS REPORT
  --------------------------
  DB2       CODE       SPE      MIGRATION
  MEMBER    LEVEL      APAR     ELIGIBLE
  --------  ---------  -------  ---
  DB2A      V13R1M504  .......  N/A
  DB2B      V12R1M510  PH37108  YES
  MIGRATION READINESS STATUS: GROUP MIGRATION IN PROGRESS TO
  DB2 13
  REASON: ALL REMAINING MEMBERS ARE READY FOR DB2 13
  ---------------------------------------------------------------
  

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:

  UI95046 UI95047

Modules/Macros

• DSNUECM2 DSNRNTFY DSNUECMJ DSN7GCMD DSNUECMI
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RC10 PSY UI95046

     UP23/12/27 P F312

• RD10 PSY UI95047

     UP23/12/27 P F312

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.