ZDE2801E: TFILE01(L) DATA SET ALREADY CONTAINS MEMBER 'membername' ASSOCIATED WITH INVALID CC @cc-ref-no
search cancel

ZDE2801E: TFILE01(L) DATA SET ALREADY CONTAINS MEMBER 'membername' ASSOCIATED WITH INVALID CC @cc-ref-no

book

Article ID: 52365

calendar_today

Updated On:

Products

Alchemist TPX - Session Management Vman Session Management for z/OS

Issue/Introduction

Request fails.  Entity log for failed entity contains these messages:
ZDE2801E: TFILE01(L) DATA SET ALREADY CONTAINS  MEMBER 'member-name' ASSOCIATED
     WITH INVALID CC @cc-ref-no
ZDE2830I: FAILURE RC=12 REASON=00 DATA1= DATA2=@cc-ref-no
ZDE5801E: TFILE01(L) DATA SET ALREADY CONTAINS  MEMBER 'member-name' ASSOCIATED
    WITH INVALID CC @cc-ref-no
ZDE5830I: FAILURE RC=12 REASON=00 DATA1= DATA2=@cc-ref-no 
ZDE5811E: TFILE01(L) BACKOUT TERMINATED
ZDE5801E: TFILE02(C) DATA SET ALREADY CONTAINS  MEMBER 'member-name' ASSOCIATED
    WITH INVALID CC @cc-ref-no
ZDE5830I: FAILURE RC=12 REASON=00 DATA1= DATA2=@cc-ref-no
ZDE5811E: TFILE02(C) BACKOUT TERMINATED
ZDE5800I: IMPLEMENTATION BACKOUT INITIATED

 

Environment

Release:
Component: ALCMST

Resolution

A couple of things to check first to analyze this situation:

  • Check entity access for the target zone. Does the entity exist in the zone?

  • Check the target libraries. Does the entity exist in the target libraries? Does the @member exist for the current request version and/or the @member noted in the error messages?

Scenario 1: Entity does NOT exist in the zone, and does NOT exist in any of the target libraries

To resolve this situation:

  1. Allow request to go to FAIL status, if not already in FAIL.

  2. HOLD failed entity within request index (line command H).

  3. Release the request which should go to COMPLETE status and clean up the entity versions.

    • If this request fails again with the same errors, verify whether or not the entity now exists in entity access and or target files and refer to that scenario. Contact CA if the situation is the same as the original instance.

  4. If the original request is now COMPLETE, create a new request containing only an UPDATE for the HELD entity that previously failed.

    • release the request (line command E).

    • If this entity has similar error messages, reassess if this is still the same scenario. If it is the same scenario, open an issue with CA Support. Otherwise, follow the directions for the new scenario.

Scenario 2: Entity does NOT exist in the zone, but does exist in one or more zone target libraries

Since the entity does not exist in the ZCL (Zone Control Library), Alchemist expects that there would be no members for this entity in the target files and therefore fails the request.

To resolve this situation:

  1. Rename the entity in the datasets corresponding to the identified TFILES to a temporary name of your choosing.

  2. If the active CC Ref (Change Control Reference) @member exists in the target libraries, that may also need to be renamed.

  3. Then re-execute the package (change request) by releasing it (line command E). This should allow the request to complete successfully (status COMPLETE).

    • If the request fails again on the same entity, reevaluate the original questions to identify if this is a new situation. If it is the same scenario, open an issue with CA Support.

  4. After the request is complete, delete the target file members that were previously renamed.

Scenario 3: Entity exists in the zone but does NOT exist in any of the target libraries

Make note of whether the CC Ref (Change Control Reference) for the current version of the entity in the zone is the same as the CC Ref the active entity in this change request (package) or for a previous version. This will impact step 4a.

To resolve this situation:

  1. Allow request to go to FAIL status, if not already in FAIL.

  2. HOLD failed entity within request index (line command H).

  3. Release the request which should go to COMPLETE status and clean up the entity versions.

    1. If this request fails again with the same errors, verify whether or not the entity now exists in entity access and or target files and refer to that scenario. Contact CA if the situation is the same as the original instance.

  4. If the original request is now COMPLETE, create a new request

    1. Is the CC Ref (Change Control Reference) for the current version of the entity in the zone the same as the CC Ref for the active entity in the original change request (package) or for a previous version?

      • CC Ref is same as original request: add an UPGRADE for the HELD entity that previously failed. (NOTE: UPGRADE, not UPDATE. The UPGRADE will populate the target files with the entity already existing in the target zone.)

      • CC Ref is for a previous version: add an UPDATE for the HELD entity that previously failed

    2. release the request (line command E).

    3. If this entity has similar error messages, reassess if this is still the same scenario. If it is the same scenario, open an issue with CA Support. Otherwise, follow the directions for the new scenario.

Scenario 4: Entity exists in the zone as well as one or more zone target libraries

To resolve this situation:

  1. Rename the entity from the datasets corresponding to the identified TFILES to a temporary name of your choosing.

  2. If the active CC Ref (Change Control Reference) @member exists in the target libraries, that may also need to be renamed.

  3. Then re-execute the package (change request) by releasing it (line command E). This should allow the request to complete successfully (status COMPLETE).

    • If the request fails again on the same entity, reevaluate the original questions to identify if this is a new situation. If it is the same scenario, open an issue with CA Support.

  4. After the request is complete, delete the target file members that were previously renamed.

NOTE: This approach would apply to any entities, not only to ETDs.

Powered by Wolken Software