ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SO07191 and SO05694 conflict over DDDEF SCSQLOAD

book

Article ID: 133519

calendar_today

Updated On:

Products

IDMS IDMS - Database IDMS - ADS

Issue/Introduction

The HOLDDATA in SO05694 has instructions to ADD DDDEF SCSQLOAD and point it to the IDMS CAGJLOAD.

SO07191, which has SO05694 as a pre-requisite, also has HOLDDATA instructions to ADD DDDEF SCSQLOAD, but to point it to "IBMHLQ.SCSQLOAD".

Attempting to run this SMP/E as described will fail with this error message:

GIM35601E ** DATASET SUBENTRY WAS NOT ADDED BECAUSE IT ALREADY EXISTS.


 

Cause

The two PTFs instruct the user to define the same DDDEF but to point it to different load libraries.

Environment

Release : r19.0
Component : CA IDMS/DB

Resolution

SO04635 does not actually need anything from SCSQLOAD, but a DDDEF of SCSQLOAD (pointing to anything) was necessary to allow the link-edit to complete successfully.

Therefore, instructions were provided in SO05694 to define SCSQLOAD and point it to CAGJLOAD.

SO07191 does actually require that SCSQLOAD point to "IBMHLQ.SCSQLOAD".

So the solution is to use the HOLDDATA from SO07191.

If SCSQLOAD has already been defined with the input from SO05694, use the input from SO07191 but change the ADD DDDEF statements to REP DDDEF.