A fix is available
APAR status
Closed as new function.
Error description
A job build of a REORG with DISCARD on a TS *NOT* having NPSIs with the following options specified can result in separate REORG statements being generated for each partition: - Group Partitions by: None - Group Partitions with NPI: Yes The following new field is being added to the utility profile options panel: - Group PI partitions in step _ (Y - Yes, N - No) With the new option set to 'Y,' all PARTS of a partitioned object that do NOT have a defined non-partitioning index will be grouped together in the same step. This option differs from the 'Group Partitions with NPI' field in that it impacts those objects that have no NPIs. The syntax involved with the selected object partitions will be clustered instead of being individually specified in the same step. Example of the generated JCL prior to this PTF Step 1: ...PARTLEVEL(1) ...PARTLEVEL(8) Step 2: ...PARTLEVEL(3) Example of the generated JCL after APPLYing this PTF: Step 1: ...PARTLEVEL(1,8) Step 2: ...PARTLEVEL(3)
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All Users * **************************************************************** * PROBLEM DESCRIPTION: A job build of a REORG on a TS *NOT* * * having NPSIs with the following options * * specified can result in separate REORG * * statements being generated for each * * partition: * * * * - Group Partitions by: None * * - Group Partitions with NPI: Yes * * * * The following new field is being added * * to the utility profile options panel: * * * * - Group PI partitions in step _ * * (Y - Yes, N - No) * * * * With the new option set to 'Y,' all * * PARTS of a partitioned object that do * * NOT have a defined non-partitioning * * index will be grouped together in the * * same step. This option differs from * * the 'Group Partitions with NPI' field * * in that it impacts those objects that * * have no NPIs. The syntax involved with * * the selected object partitions will be * * clustered instead of being individually * * specified in the same step. * * * * Example of the generated JCL *prior* * * to this PTF: * * Step 1: * * ...PARTLEVEL(1) * * ...PARTLEVEL(8) * * * * Step 2: * * ...PARTLEVEL(3) * * * * Example of the generated JCL *after* * * APPLYing this PTF: * * Step 1: * * ...PARTLEVEL(1,8) * * Step 2: * * ...PARTLEVEL(3) * **************************************************************** * RECOMMENDATION: APPLY the PTF * **************************************************************** .
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
PH60347
Reported component name
AUTOMATION EXPE
Reported component ID
5698DAE00
Reported release
110
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-03-13
Closed date
2025-06-09
Last modified date
2025-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO03551
Modules/Macros
DAJ#AGEN DAJ#BCLR DAJ#BPRI DAJ#BUL2 DAJ#BULD DAJ#OBEX DAJ#UPRI DAJ#UTED DAJ$BMSG DAJ$BULD DAJ$BULJ DAJ$BUT2 DAJ$BUTB DAJ$BUTC DAJ$BUTI DAJ$BUTK DAJ$BUTM DAJ$BUTP DAJ$BUTQ DAJ$BUTR DAJ$BUTT DAJ$BUTW DAJ$BUTX DAJ$BUTY DAJ$BUTZ DAJ$DS DAJ$DSFT DAJ$DSN DAJ$RCFS DAJ$UDOP DAJ$URBD DAJ$URBO DAJ$URCB DAJ$URCC DAJ$URCE DAJ$URCF DAJ$URCL DAJ$URCV DAJ$UREO DAJ$URPR DAJ@CARD DAJHUREO DAJHVREO
Fix information
Fixed component name
AUTOMATION EXPE
Fixed component ID
5698DAE00
Applicable component levels
R110 PSY UO03551
UP25/06/11 P F506
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":"BU048","label":"IBM Software"},"Product":{"code":"SSSXEC9","label":"IBM Db2 Automation Expert for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110","Line of Business":{"code":"LOB76","label":"Data Platform"}}]
Document Information
Modified date:
02 July 2025