A fix is available
APAR status
Closed as program error.
Error description
When running a larger amount of DDL DROPs you may commit in between to not hold to many locks at one point in time. .. DROP PROGRAMVIEW xxxxx DROP PROGRAMVIEW yyyyy COMMIT DDL DROP PROGRAMVIEW aaaaa DROP PROGRAMVIEW bbbbb COMMIT DDL [...] . But committing in between DROPs leads into this: . INFO: IMS Universal Drivers build number: 14111 java.sql.SQLException: -8005: IMS returned the AIB return code 00000108 and the reason code 0000071C . DLISAS shows the reason: DFS4328E DDL CHANGES COULD NOT BE ACTIVATED. OTHER CHANGES IN PROGRESS. . From control region it appears as if a second DMU region has been started to process the second set of DROP PROGRAMVIEWs before the deletion for the first set was complete: . 20.16.28 STC16496 DFS551I DMU REGION DFSDM011 STARTED 20.16.29 STC16496 DFS551I DMU REGION DFSDM011 STARTED . Analysis: If import is driven by DDL DROP, then during COMMIT Phase 4 DFS3DL40 does not wait after sending AWE to DFS3DL50. This creates a window that a new DMU region can come-up and start processing DROP and start IMPORT?s prepare phase. . If customer enables AUTOIMPORT via DFSDF member then this whole issue does not happen. If auto-import is enabled, then we already have code to go into WAIT state and wait for commit phase 4 to finish.
Local fix
If one enables AUTOIMPORT via DFSDF member then this whole issue does not happen.
Problem summary
**************************************************************** * USERS AFFECTED: * * All IMS V15 users of DDL. * **************************************************************** * PROBLEM DESCRIPTION: * * A set of DDL DROP statements with multiple COMMIT DDLs * * failed with DFS4328E DDL CHANGES COULD NOT BE ACTIVATED. * * OTHER CHANGES IN PROGRESS message in shared IMS Catalog and * * Directory environment. * **************************************************************** * RECOMMENDATION: * * INSTALL CORRECTIVE SERVICE FOR APAR/PTF * **************************************************************** Problem 1: During the COMMIT DDL processing, IMS issues IMPORT's Commit Phase 4 and does not wait for CMT P4 to finish. IMS terminates the DMU region and reports CC=0 while CMT P4 may be still running. While CMT P4 is still in progress, another DMU region can start and issue Commit Prepare phase which will fail with "DFS4328E DDL CHANGES COULD NOT BE ACTIVATED. OTHER CHANGES IN PROGRESS" and the DDL batch utility reports java.sql.SQLException: -8005: IMS returned the AIB return code 00000108 and the reason code 0000071C. Problem 2: For non IMS searchable database changes, DDL does not create new instance but sets pending timestamp in the resource header of the IMS Catalog.
Problem conclusion
DFS3DL40 was changed to wait for Import's Commit Phase 4 to finish. DFS3DL50 was changed to post the autoimport caller after processing the Commit Phase 4 request. DFS3DL10 was changed to not set pending timestamp in the resource header in the case of non-IMS searchable DDL database change. DFS3RLM macro was changed to add DROP DDL driven Import flag. Additional Keywords: IMSDDL/K
Temporary fix
Comments
APAR Information
APAR number
PH32897
Reported component name
IMS V15
Reported component ID
5635A0600
Reported release
500
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-12-22
Closed date
2021-05-25
Last modified date
2021-07-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI75566
Modules/Macros
DFS3DL50 DFS3DL40 DFS3DL10
Fix information
Fixed component name
IMS V15
Fixed component ID
5635A0600
Applicable component levels
R500 PSY UI75566
UP21/06/03 P F106
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"15","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
22 December 2023