Joined Object Was Not Created. Join Definition Already Exists.

Products

• Vantage Storage Resource Manager

Issue/Introduction

Attempting to create and new JOIN using CA 1 Files object as the Base Object and CA 1 Volumes object. Received the below error message, but there no JOIN Object with the same Join Name.  No way to tell what JOIN Object Name (PDS Member name) is that it’s saying is a duplicate. Following is the screenshot of the error message displayed on the web client.

 

We checked the main task for MVS errors but didn't see any.

Cause

Customer is using an 'old' V1 PDS file for these, but it's causing problems due to the MAXGENS parameter.

Resolution

Vantage Release 14.1 contains sample jobs that allocate V2 PDSE data sets. If your environment uses a MAXGENS value of 2 or higher, V2 PDSE enables you to take advantage of member versioning. This optional feature enables you to revert to an older version of a member if required.

If you do not wish to allocate these libraries as V2, you can allocate them as standard LIBRARY (PDSE) type, and you can modify the MAXGENS parameter value or remove the MAXGENS parameter without impacting Vantage functionality.

Or by copying the members from the old V1 PDS into the new V2 PDS without using REPLACE, so that if a same named member is in the V2 library it doesn't get overwritten with the older version from the old V1 library, Vantage won't have any problems finding/reading the PDS members.

For more information about V2 PDSE data sets, see the IBM documentation.

Additional Information

Refer to Note in the Overview section of the Vantage tech doc.