A fix is available
APAR status
Closed as new function.
Error description
Improvements to the LOAD utility taking image copies at the partition level.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All Db2 12 for z/OS users of LOAD COPYDDN * * or RECOVERYDDN * **************************************************************** * PROBLEM DESCRIPTION: * * Allow LOAD with COPYDDN at the * * statement level without requiring * * RESUME or REPLACE at the statement * * level. * **************************************************************** * RECOMMENDATION: * **************************************************************** Currently, users either have the option to specify a copy-spec along with RESUME or REPLACE keywords at the table space level, which serializes the entire table space and prohibits concurrent LOAD jobs from running against other partitions within the same table space, or users can optionally specify a copy-spec per INTO TABLE PART, which creates a separate image copy per partition. Moreover, the LOAD INTO TABLE specification's current behavior when used with a partitioned table space with many partitions may also cause undesirable scenarios necessitating multiple serialized LOAD instantiations. User wants to drive LOAD at the partition level while creating sequential inline image copy datasets to tape but is restricted by the number of tape drives in their environment, which limits the number of partitions they can LOAD at once. Due to this restriction, their alternative today is either to allocate the sequential inline image copies to DASD, or reduce the number of partitions being LOADed in each serial job.
Problem conclusion
Temporary fix
Comments
This enhancement provides new functionality to the LOAD utility enabling the user to specify a single inline image copy at the table space level, which can then be used for multiple INTO TABLE PARTs without the need to specify a copy-spec per table partition. Partition-level image copies will then be included in this image copy. This APAR will make the following external changes. LOAD syntax in existing jobs will still be accepted. LOAD utility syntax diagram change: >>-LOAD--| resume-spec |--+---------------+-> '-| copy-spec |-' Note: The copy-spec cannot be specified for RESUME YES SHRLEVEL CHANGE copy-spec will be removed from resume-spec but the user is required to specify REPLACE or RESUME YES at either the statement level or on the INTO TABLE PART clause. Certain scenarios that today fail with RC8 messages will be altered to facilitate a copy-spec at the statement level with INTO TABLE PART to yield a successful program execution. ×**** PE22/05/19 FIX IN ERROR. SEE APAR PH46058 FOR DESCRIPTION ×**** PE22/05/02 FIX IN ERROR. SEE APAR PH46058 FOR DESCRIPTION
APAR Information
APAR number
PH40709
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
C10
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-09-17
Closed date
2022-01-10
Last modified date
2022-09-08
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI78864
Modules/Macros
DSNURBID DSNURELD DSNUGUIP DSNURILD DSNULSWT DSNURECS DSNUGDDF DSNUGUCA
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RC10 PSY UI78864
UP22/01/19 P F201
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
08 September 2022