Copy Detector datastore from a previous Release to a recently installed Release.

Document ID : KB000010293
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

A recent Detector Release has been installed and you define a new Detector datastore in the new Release, you would like to copy the previous Detector datastore to the new Detector datastore defined in the new Release with JCL in CDBASRC(PDTDSCPY) member but the PDT0316 message is displayed and Job finished with RC=08.
 
PDT0316 DATASTORE DSN IS UNAVAILABLE, DSN=DSNAME.DTR0002.SSID

Instructions:

Problem was the Detector datastore defined in the recently installed Release did not have same structure as the Detector datastore defined in previous Release, the DTR0002 data set for Exceptions was defined in the Detector datastore for the recently installed Release but it was not defined in the Detector datastore for previous Release .
 
This Copy process is not supported, you have to copy the Detector datastore from a previous Release to recently installed Release exactly with same structure. Internally the structure of the Detector datastore is stored in the Xmanager Control file, so although you manually deleted or define the DTR0002
data set for Exceptions, the data set name is still in the Xmanager Control file.
 
There is no way of modifying an existing Detector datastore. After the DTR0002 (Exception) and DTR0003 (SQL Error) data sets have been defined for a Detector datastore they cannot be dynamically removed, the opposite is the same, to add the Exception or SQL Error data sets to the Detector datastore, you have to create a new Detector datastore and add those additional data sets during the creation.