DFS4747E AUTOMATIC IMPORT FAILED FOR RESOURCE=resourcename AS AN LNB / RCNT / SMB BECAUSE IT ALREADY EXISTS AS AN LNB / RCNT / SMB
Explanation
Automatic import from the IMSRSC repository failed for the resource named resourcename as message destination resource type LNB / RCNT / SMB, because it already exists with the same name as a different message destination resource type of LNB / RCNT / SMB. Message destination types of resources include remote logical terminals (LTERMs), transactions, and MSC logical link paths (MSNAMEs).
In the message text:
- resourcename
- Indicates the name of the resource for which the error occurred.
The message destination type of resource can be one of the following:
- LNB
- MSC logical link path (MSNAME) control block
- RCNT
- MSC remote LTERM control block
- SMB
- Transaction control block
System action
IMS cold start continues with automatic import without creating the resource resourcename for the different message destination resource type of LNB / RCNT / SMB. Instead, the resource resourcename of the original message destination resource type of LNB / RCNT / SMB is automatically imported.
System programmer response
After automatic import and IMS cold start have completed, do all of the following tasks to prevent message DFS4747E from being issued at the next IMS cold start:- Determine which message destination resource type (LTERM, MSNAME, or transaction) you want to define for resource resourcename.
- For every message destination resource type that you do not want defined for resource
resourcename, issue the
DELETE DEFN TARGET(REPO) TYPE(LTERM | MSNAME | TRAN) NAME(resourcename)command. - If the message destination resource type you want to define for resource resourcename failed during automatic import, either cold start IMS again, or delete the resource locally and create it again locally with the correct message destination resource type.