A fix is available
APAR status
Closed as program error.
Error description
LOAD of PBG setting COPY pending status of parts not updated. A job is doing a load resume on a table living in a 2 partition PBG UTS.The LOAD is indicating that only partition 2 got rows loaded. But both partitions 1 and 2 are showing up in COPY PENDING status.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 11 for z/OS and Db2 12 for z/OS * * users of LOAD RESUME YES LOG NO on a * * partition-by-growth ( PBG ) table space. * **************************************************************** * PROBLEM DESCRIPTION: * * LOAD RESUME YES LOG NO SHRLEVEL NONE * * sets all partitions of a PBG table * * space in COPY pending and inserts a * * SYSCOPY record for all partitions, * * even though not all partitions were * * loaded with any rows. * **************************************************************** * RECOMMENDATION: * * Apply corrective PTF when available * **************************************************************** User ran a LOAD RESUME YES LOG NO SHRLEVEL NONE utility on a PBG table space and did not specify COPYDDN or RECOVERYDDN and did not include a COPY template or data set. Although it was correct for LOAD to place the partitions that were loaded into a COPY pending status, the utility placed all partitions in a COPY pending state regardless of whether rows were loaded into that PBG partition. In addition, LOAD was inserting a SYSCOPY record for all PBG partitions, instead of only the PBG partitions which were loaded.
Problem conclusion
LOAD RESUME YES LOG NO SHRLEVEL NONE utility code has been modified to only place the PBG partitions into COPY pending status and only insert a SYSCOPY record for those partitions loaded.
Temporary fix
Comments
APAR Information
APAR number
PH16841
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-09-12
Closed date
2020-03-17
Last modified date
2020-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI68450 UI68451
Modules/Macros
DSNURSLD DSNURWBF
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
25 March 2020