Reason:
The data set name for the DDNAME should contain the CXXNAME, that is, the DBSIDPR module in use should specify that the CXXNAME is within the data set name for every database index and data area. However, an edit-check discovered an error in which a data set name did not contain the correct name.
Note:This edit check ensures that the data set is being used by the correct CA Datacom instance as part of the protection preventing, for example, a test MUF accidentally pointing to a production data set that could occur if production data sets or different production MUFs were to use each other’s data sets.
In the message text:
Action:
Check to see if you are executing with the correct environment, that is, with the correct DBSIDPR module. If the DBSIDPR is correct, check the DDNAME data set and its data set name. It is likely that the DDNAME data set is not the correct one to use with this MUF, in which case the error is valid, and the correct data set needs to be found or created. If you find that the data set is the correct one for this MUF and that the error was caused by its name not including the CXXNAME as edited, because of the DBSIDPR, you can either rename the data set to include the correct CXXNAME value, or you can update the DBSIDPR module to remove the editing.
If this is a MUF and if the DBSIDPR is being changed, the MUF must be recycled.
|
Copyright © 2014 CA.
All rights reserved.
|
|