EXPORT command
Use the EXPORT command to export runtime resource and descriptor definitions from the online IMS system to a resource definition data set (RDDS) or the IMSRSC repository as stored resource definitions.
- Added to IMS dynamically through the IMPORT command
- Imported from an RDDS during an IMS cold start
- Imported from the repository during an IMS cold start, or an IMS warm start or emergency restart for changed list processing
Subsections:
Environment
The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the command and keywords.
| Command / Keywords | DB/DC | DBCTL | DCCTL |
|---|---|---|---|
| EXPORT | X | X | X |
| DEFN | X | X | X |
| ENDTIME | X | X | X |
| NAME | X | X | X |
| OPTION | X | X | X |
| RDDSDSN | X | X | X |
| SET | X | X | X |
| STARTTIME | X | X | X |
| TARGET | X | X | X |
| TYPE | X | X | X |
Syntax
Keywords
The following keywords are valid for the EXPORT command:
- DEFN
- Specifies that resource and descriptor definitions are to be exported.
- ENDTIME
- Specifies the end time until which new and modified runtime resource
definitions are to be gathered to be exported to the repository. ENDTIME
is the local time and is specified in the following format:
where yyyy.ddd is required, and the rest of the parameters (hh, mm, ss, ms, and th) are optional and default to 0.yyyy.ddd hh:mm:ss.ms.thWhen the ENDTIME keyword is specified, all the resource definitions that have either a create time stamp or an update time stamp less than the ENDTIME value specified are exported to the repository. If the TYPE, NAME, or STARTTIME keyword is specified with ENDTIME, the resource definitions that match all the specified keywords are exported to the repository.
If ENDTIME is not specified, all the resources that are found that match the STARTTIME, NAME, and TYPE keywords are exported to the repository.
Note: Consideration must be taken in specifying the ENDTIME value when there is a change in time for the Daylight Saving Time. - NAME()
- Specifies the 1-8 character name of a resource or descriptor. Wildcards can be specified in the name. The name is a repeatable parameter. If the NAME parameter specified is a specific name or a wildcard, command responses are returned for all the resource names that are processed. NAME is an optional parameter, and if not specified, it defaults to NAME(*). For NAME(*), command responses are returned only for the resource and descriptor names that resulted in an error. OPTION(ALLRSP) can be specified with NAME(*) to obtain the command responses for all of the resource and descriptor names that are processed.
- OPTION()
- Specifies additional functions to be performed along with the
command.
- ALLRSP
- Indicates that response lines are to be returned for all resources
and descriptors that are processed by the command. If NAME(*) is specified,
the default action is to return response lines only for the resources
and descriptors that resulted in an error. OPTION(ALLRSP) can be
used with NAME(*) to request response lines for all resources and
descriptors processed by the command. If a name value other than
NAME(*) is specified, the default action is to return a response line
for all resources and descriptors processed by the command. If OPTION(ALLRSP)
is specified with a name value other than NAME(*), the ALLRSP parameter
is ignored.
For HALDB databases, only the definition of the HALDB master database is exported. HALDB partition definitions are not exported, because the partition definitions are maintained in the RECON data set. OPTION(ALLRSP) does not include the partitions definitions in the output and therefore does not flag them with a nonzero completion code.
When coding the Destination Creation exit routine (DFSINSX0), the user can indicate whether the definitions for transaction and program resources created by the exit should be exported. Transaction and program resource definitions that are not exported are not included in the OPTION(ALLRSP) output.
IMS resources such as the Fast Path utility (DBF#FPU0) and the IMS defined descriptors (DBFDSRT1, DFSDSDB1, DFSDSPG1, and DFSDSTR1) are not exported. OPTION(ALLRSP) does not include these resources and descriptors in the output and therefore does not flag them with a nonzero completion code.
- APPEND
- Indicates that the resource and descriptor definitions are to
be appended to the end of the specified RDDS data set. If OPTION(NOCHECK)
is not specified, validity checking is done to ensure that the IMS performing the export is the
same IMS that previously exported
definitions to the RDDS. The APPEND option is valid only when exporting
to a non-system RDDS.
APPEND is mutually exclusive with OVERWRITE. If APPEND results in multiple definitions for the same resource in the RDDS, IMS uses the definition that was exported most recently when the definitions are imported.
- CHANGESONLY
- Specifies that the runtime resource definitions with changes (resources
and descriptors that are created or updated) since the last successful
export are to be exported to be hardened in the repository. OPTION(CHANGESONLY)
is supported only for TARGET(REPO).
The list of the names of the resources that are to be exported to the repository can also be provided on the command input. If a list of resource names is specified, the resources that have changes (creates or updates) since the last successful export are exported to the repository. If the specified resource does not have any changes, a completion code is returned for that resource. The export is completed for all other resources that have changes.
A list of the names of the resources that are exported to the repository is returned on the command response.
When NAME(*) is specified with OPTION(CHANGESONLY), it is treated as if OPTION(ALLRSP) was specified; all resource names that are exported to the repository are returned on the command response. If no resource names have any changes when NAME(*) is specified, no resources are exported and the command results in an error reason code.
- NOCHECK
- Indicates that no ID checking is to be done when definitions are appended to an RDDS. If OPTION(NOCHECK) is specified, the IMS performing the export can be a different IMS than the one that performed the previous export. The NOCHECK option is valid only when exporting to a non-system RDDS. NOCHECK is mutually exclusive with OVERWRITE and can be specified only if APPEND is specified.
- OVERWRITE
- Indicates that the resource and descriptor definitions are to overwrite any existing definitions in the RDDS. APPEND is mutually exclusive with OVERWRITE. OVERWRITE is the default and the only valid option when exporting to a system RDDS.
- RDDSDSN(dsname)
- An optional keyword that is used to specify the name of a non-system
RDDS to which resource and descriptor definitions are to be exported.
When the RDDSDSN() keyword is omitted from the EXPORT command,
the definitions are written to the system RDDS that contains the oldest
data. The data set name specified in the RDDSDSN() keyword cannot
be the name of any of the system RDDSs defined in the DYNAMIC_RESOURCES
section of the DFSDFxxx PROCLIB member. If a set of system data sets
is not defined in the DYNAMIC_RESOURCES section of the DFSDFxxx PROCLIB
member, the RDDSDSN() keyword is required on the EXPORT command.
If using the RDDSDSN() keyword to specify a specific data set, care should be taken when routing the EXPORT command by using Operations Manager (OM) routing. If the command is routed to multiple IMS systems in the IMSplex, only the IMS selected as the command master will process the command.
The data set specified for the RDDSDSN() keyword must be a physical sequential (DSORG=PS) BSAM data set. The data set must exist and be cataloged. When creating and allocating the RDDS data set, ensure that an end-of-file (EOF) mark is placed at the beginning of the data set. Failure to do so can produce unpredictable results. To place an EOF mark at the beginning of the data set, use program IEBGENER. The sample job skeleton DFSRDDAL, which is in the IMS.SDFSSLIB data set, can be used for this step. An alternative method of allocating the RDDS data sets is to use the ALLOCATE function of ISPF utilities. The ALLOCATE function places an EOF mark correctly at the beginning of the data set. Do not use program IEFBR14 to allocate the RDDS data sets, because IEFBR14 does not place an EOF mark at the beginning of the data set.
IMS allocates the RDDS with DISP=OLD during the export process. If you attempt to allocate a new data set by using JCL in one step of a job and then try to issue the EXPORT command by using the batch SPOC in another step of the same job, the batch export will fail with return code 10 (environment error) and reason code 4118 (data set allocate error), followed by message DFS2503W with error reason code 210 (data set is allocated to another job). This is because IMS cannot obtain an exclusive enqueue on the newly allocated RDDS.
Generation data group (GDG) data sets are not fully supported for RDDSs. Relative generation numbers cannot be used when specifying an RDDS name. For example, if you specify RDDSDSN(IMS.EXP.GDG(0)) or RDDSDSN(IMS.EXP.GDG(+1)), the EXPORT command will fail with message DFS2503W and error reason code
35C(invalid parm specified in text unit). Specifying the absolute generation number for a GDG data set does work. For example, RDDSDSN(IMS.EXP.GDG.G0001V00) can be specified. - SET
- Specifies what actions are to be set.
- IMSID
- Specifies
one or more IMS IDs whose IMS resource lists are to be updated
by the EXPORT command.
An IMS resource list is a list of resource or descriptor names that is used to define the resources for an IMS system. IMS resource lists reside in the repository and are used during IMS cold start to identify all the resource and descriptor definitions that are to be read during the IMS cold start.
For each IMS system defined in the repository, one IMS resource list is created for each resource type defined for the IMS:- Databases
- Database descriptors
- Programs
- Program descriptors
- Routing codes
- Routing code descriptors
- Transactions
- Transaction descriptors
When a resource definition is written to the repository for an IMS, the resource name is added to the appropriate IMS resource list if it does not already exist in the list. If an IMS resource list does not exist for that IMS and resource type, an IMS resource list for that IMS and resource type is created, and the resource name is added to it.
For example, if the EXPORT DEFN TARGET(REPO) NAME(TRANABC) TYPE(TRAN) SET(IMSID(IMS1,IMS2,IMS3)) command is issued, the IMS resource lists for each IMS ID specified (IMS1, IMS2, and IMS3) might be updated along with the resource definition for transaction TRANABC. If TRANABC is not already in the transaction resource list for an IMS system, it is added to the list. If no transactions have been defined for the IMS, the IMS resource list for transactions is created for the IMS, and TRANABC is added to the list. If TRANABC is already in the resource list for the IMS, the resource list is not updated.
The IMSID value specified on the EXPORT command identifies the IMS resource lists that are to be created or updated when a stored resource definition is created or updated in the repository.
The IMSID value can be a specific IMS ID, a list of specific IMS IDs, a wildcard name of *, or a wildcard name with * or %. The IMSID must be a 1- to 4-alphanumeric character value, and can include any of the following special characters: # $ % * @
If the IMSID specified is a wildcard name other than *, the IMS resource lists for those IMS systems whose names match the IMSID wildcard name will be updated. The list of IMS IDs whose IMS resource lists are updated is returned in command output. If the repository is empty and there are no resource definitions in the repository, the EXPORT command fails.
IMSID(*) indicates that the IMS resource lists for all IMS systems defined in the repository are to be updated with the resource names of the exported definitions. In other words, the resource definitions being exported will belong to all IMS systems that currently have resource definitions in the repository. If the repository is empty and there are no resource definitions in the repository, the EXPORT command fails.
The IMSID value can also be specified as a list of one or more IMS IDs of the IMS systems for which the resource lists must be updated. When one or more IMS IDs are specified, only the IMS resource lists for the specified IMS IDs are updated in the repository. If the IMS resource lists for the IMS IDs specified do not exist, the IMS resource lists are created.
The IMSID value that is specified does not have to belong to an active IMS in the IMSplex. The IMSID of an IMS that is yet to be started can be specified.
When exporting definitions for a new IMS, you must issue the EXPORT command with a specific IMSID value to create resource definitions in the repository. When a specific IMSID value is specified, the IMS resource list is created for IMS even if the IMS is currently not registered to RM. If the resource definitions are created for an IMS in error, you can use the DELETE DEFN command with the FOR(imsid) option to delete the resource definitions and the IMS resource lists.
If SET(IMSID()) is not specified, the IMSID value defaults to the IMS ID of the command master IMS. An IMS resource list is created for the command master IMS if one does not exist. You are required to route or direct the command to each IMS by using the ROUTE keyword.
- STARTTIME
- Specifies the start time from which all new and modified runtime
resource definitions are to be gathered and exported to the repository.
STARTTIME is the local time and is specified in the following format:
where yyyy.ddd is required, and the rest of the parameters (hh, mm, ss, ms, and th) are optional and default to 0.yyyy.ddd hh:mm:ss.ms.thWhen the STARTTIME keyword is specified, all the resource definitions that have either a create time stamp or an update time stamp greater than or equal to the STARTTIME specified will be exported to the repository. If the ENDTIME, TYPE, or NAME keyword is specified with STARTTIME, the resource definitions that match all the specified keywords are exported to the repository.
The list of the resource names that are exported to the repository is provided on the command output.
When NAME(*) is specified with the STARTTIME keyword with or without the ENDTIME keyword, it is treated as if OPTION(ALLRSP) was specified, and all resource names that are exported to the repository are returned on the command response. If no resource names have any changes when NAME(*) is specified, no resources are exported, and the command results in an error reason code.
Consideration for daylight saving time: Consideration must be taken in specifying the STARTTIME parameter when there is a change in time for the Daylight Saving Time in regard to the current local time. For the spring time adjustment, time is adjusted forward by one hour at 2:00 a.m. If you want to export all the resources that have changed since 12:30 a.m. (before the time change), you would have to specify STARTTIME of 1:30 a.m. on the command because 12:30 a.m. (before time change) corresponds to 1:30 a.m. (after time change). For the fall time adjustment, time is adjusted backward by one hour at 2:00 a.m. If you want to export all resources that have changed since 12:30 a.m. (before the change), you would have to enter a STARTTIME of 11:30 p.m. on the prior day because 12:30 a.m. (before time change) corresponds to 11:30 p.m. (after time change). - TARGET()
- Specifies where resource and descriptor definitions are to be
exported.
- RDDS
- Specifies that resource and descriptor definitions are to be exported
to an RDDS. If the RDDSDSN() keyword is not used to specify the name
of a non-system RDDS, the system RDDS with the oldest data is used.
Even when IMS is enabled to use the repository, you can use the EXPORT DEFN TARGET(RDDS) command to export runtime resource and descriptor definitions to a system RDDS or a non-system RDDS if the RDDS is defined.
- REPO
- Indicates that the runtime resource definitions of
the resource names specified on the NAME keyword are to be exported
to the IMSRSC repository.
Only the resource definitions of the resource names that match the
NAME keyword are created or updated in the repository. If the resource
definition does not exist in the repository, it is created. If the
resource definition exists in the repository, it is replaced. TARGET(REPO)
is valid only when IMS is enabled
to use the repository.
A repository can maintain resource and descriptor definitions for up to 64 IMS systems in an IMSplex.
All resource definitions are exported to the repository as a single unit of work (UOW). If any resource results in an error being written to the repository, no resource definitions are written.
The system-defined descriptors are not exported to the repository. The HALDB partition databases are not exported to the repository when TYPE(ALL) or TYPE(DB) is specified.
If any RM CSLRPUPD request errors are returned for the EXPORT command, you must check to see if there are any in-doubts. If the error is before the UOW is committed, all updates to the repository are backed out. If the failure is during UOW commit and if the repository primary data set is updated, the UOW is committed. You must issue the QUERY xxx SHOW(DEFN) commands to verify if the changes are hardened in the repository, and if not, reissue the EXPORT command.
The EXPORT DEFN TARGET(REPO) command is processed only by the IMS that has been selected as the command master. All other IMS systems that receive the command return an IRSN_NOTMSTR return and reason code. In a cloned IMS configuration, the EXPORT command can be issued with SET(IMSID(*)) so that the exported definitions are written to the repository and all the IMS resource lists in the repository are updated. If a resource name does not exist in an IMS resource list and SET(IMSID(*)) is specified, the resource name is added to the IMS resource list. In a non-cloned IMS configuration, issue the EXPORT command to each IMS individually so that each IMS acts as the command master and exports its own resource and descriptor definitions. In this case, the EXPORT command with the default SET(IMSID()) keyword can be issued and the same command will be routed to each IMS in the IMSplex.
When an FP(E) transaction is created in the repository by the EXPORT DEFN command, the routing code for the FP(E) transaction will also be created in the repository by RM.
Recommendations:- Avoid issuing the EXPORT DEFN command with TARGET(REPO) NAME(*) TYPE(ALL) during peak hours because exporting all the resource definitions to the repository can incur a larger than normal command response time. However, while the resource definitions are being written to the repository, there is no impact to other work in IMS.
- In order to avoid incurring performance overhead of accessing resources in the repository that have not been updated, export to the repository only those resources that have been updated. If you do not know the names of the resources that have been updated recently and need to be exported, you can issue the EXPORT command with the STARTTIME keyword so that you can export all resources that have been updated since a specific time.
During the EXPORT DEFN TARGET(REPO) command processing, resource validation is performed in RM as follows:- When a new transaction or routing code definition is added to the repository, resource validation checking is done to ensure that a definition for the associated program either exists in the repository or is being added to the repository with the EXPORT command.
- When an existing program, transaction, or routing code definition is updated in the repository, resource validation checking is done to ensure that the attributes being updated do not conflict with the attributes of any associated resource definitions. For example, if the transaction is modified to FP(E), a check is done to ensure that the associated program is defined as FP exclusive.
- TYPE()
- Specifies the type of resource or descriptor definitions to export.
- ALL
- Specifies that all definitions for all resource and descriptor types (DB, DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN, and TRANDESC) are to be exported.
- ALLDESC
- Specifies that all definitions for all descriptor types (DBDESC, PGMDESC, RTCDESC, and TRANDESC) are to be exported. TYPE(ALLDESC) is not valid when exporting to a system RDDS or when exporting from an IMS that does not have DRD enabled.
- ALLRSC
- Specifies that all definitions for all resource types (DB, PGM, RTC, and TRAN) are to be exported. TYPE(ALLRSC) is not valid when exporting to a system RDDS.
- DB
- Specifies that one or more database definitions are
to be exported. TYPE(DB) is not valid when exporting to a system
RDDS. If TYPE(DB) is specified on a DCCTL system, completion code
10 (
NO RESOURCES FOUND
) is returned. - DBDESC
- Specifies that one or more database descriptor definitions
are to be exported. TYPE(DBDESC) is not valid when exporting to a
system RDDS or when exporting from an IMS that
does not have DRD enabled. If TYPE(DBDESC) is specified on a DCCTL
system, completion code 10 (
NO RESOURCES FOUND
) is returned. - PGM
- Specifies that one or more program definitions are to be exported. TYPE(PGM) is not valid when exporting to a system RDDS.
- PGMDESC
- Specifies that one or more program descriptor definitions are to be exported. TYPE(PGMDESC) is not valid when exporting to a system RDDS or when exporting from an IMS that does not have DRD enabled.
- RTC
- Specifies that one or more routing code definitions
are to be exported. TYPE(RTC) is not valid when exporting to a system
RDDS. If TYPE(RTC) is specified on a DBCTL system, completion code
10 (
NO RESOURCES FOUND
) is returned. - RTCDESC
- Specifies that one or more routing code descriptor
definitions are to be exported. TYPE(RTCDESC) is not valid when exporting
to a system RDDS or when exporting from an IMS that does not have DRD enabled. If TYPE(RTCDESC)
is specified on a DBCTL system, completion code 10 (
NO RESOURCES FOUND
) is returned. - TRAN
- Specifies that one or more transaction definitions
are to be exported. TYPE(TRAN) is not valid when exporting to a system
RDDS. If TYPE(TRAN) is specified on a DBCTL system, completion code
10 (
NO RESOURCES FOUND
) is returned. - TRANDESC
- Specifies that one or more transaction descriptor
definitions are to be exported. TYPE(TRANDESC) is not valid when exporting
to a system RDDS or when exporting from an IMS that does not have DRD enabled. If TYPE(TRANDESC)
is specified on a DBCTL system, completion code 10 (
NO RESOURCES FOUND
) is returned.
Usage notes
The EXPORT command can be issued through TSO SPOC, IBM® Management Console for IMS and DB2® for z/OS®, the Manage Resources options in the IMS Applications menu, or other user-written programs that issue commands through OM API. These commands can also be issued to an IMSplex by using the Batch SPOC utility.
The EXPORT DEFN TARGET(RDDS) command writes resource and descriptor definitions either to the data set specified by the RDDSDSN() keyword or, if the RDDSDSN() keyword is omitted, to the system RDDS containing the oldest data. A system RDDS is one of the RDDS data sets defined with the RDDSDSN= parameter in the DYNAMIC_RESOURCES section of the DFSDFxxx PROCLIB member. A system RDDS contains all of the resource and descriptor definitions for a single IMS. If using automatic import or automatic export, each IMS must have its own set of system RDDS data sets. When exporting to a system RDDS, all of the IMS resource and descriptor definitions must be exported. When exporting to a non-system RDDS, all or some of the IMS resource and descriptor definitions can be exported.
The EXPORT DEFN TARGET(REPO) command writes resource and descriptor definitions to the IMSRSC repository. The repository contains all of the resource and descriptor definitions for all IMS systems in the IMSplex that share the repository. When exporting to the repository, all or some of the IMS resource and descriptor definitions can be exported. During export to the repository, you can specify, by using the SET(IMSID()) keyword, a list of the IMS systems in the IMSplex to which the resource definitions must be defined. The specified resource definitions and the corresponding IMS resource lists in the repository are either updated or created. For more information about IMS resource lists, see the description for the SET(IMSID()) keyword.
The EXPORT DEFN TARGET(REPO) command does not delete resource definitions from the repository. To delete resource definitions from the repository, issue the DELETE DEFN command.
To check the contents of the repository, issue the QUERY DB | DBDESC | PGM | PGMDESC | RTC | RTCDESC | TRAN | TRANDESC commands with the SHOW(DEFN,GLOBAL), SHOW(IMSID), or SHOW(DEFN,IMSID,GLOBAL) keyword. If the repository is empty and contains no resource definitions, the QUERY command fails.
When exporting to a system RDDS, all definitions in the system RDDS are overwritten with the definitions being exported. When exporting to a non-system RDDS, the user has the option of overwriting the existing definitions with the new definitions, or appending the new definitions to the end of the data set. When the APPEND option is used, all of the definitions that meet the criteria specified on the EXPORT command are exported and appended to the existing definitions in the RDDS. If the export results in multiple definitions for the same resource in the RDDS, the last definition written to the RDDS is the definition used by the IMPORT command when creating the runtime resource definition for the resource or descriptor.
Definitions for IMS resources such as the Fast Path utility (DBF#FPU0) and the descriptors defined by IMS (DBFDSRT1, DFSDSDB1, DFSDSPG1, and DFSDSTR1) cannot be exported to the RDDS or the repository.
The EXPORT command is not allowed on an XRF alternate or an FDBR region.
Export to a system RDDS is allowed only in a DRD environment (DFSDFxxx or DFSCGxxx defined with MODBLKS=DYN). Export to a non-system RDDS is allowed in a non-DRD environment (DFSDFxxx or DFSCGxxx defined with MODBLKS=OLC, or MODBLKS not defined); however, descriptors do not exist and cannot be exported.
- When exporting to a system RDDS, the EXPORT command is processed by all IMS systems that receive the command. Each IMS that receives the command exports its resource and descriptor definitions to its own system RDDS. The system RDDSs are not shared among IMS systems, so all IMS systems that receive the command can process the command simultaneously without data set contention.
- When exporting to a non-system RDDS, the EXPORT command is treated as if the command was defined to OM as ROUTE=ANY. OM selects one IMS to be the command master. The command master IMS exports its resource and descriptor definitions to the specified non-system RDDS. All non-master IMS systems that receive the command return without exporting any definitions with an “IMS not master” return and reason code to OM. The export to the non-system RDDS is processed by only one IMS to avoid data set contention and to prevent the resource and descriptor definitions from being overwritten if the RDDS is shared between IMS systems.
- When exporting to the repository, the EXPORT command is treated as if the command was defined to OM as ROUTE=ANY. OM selects one IMS to be the command master. The command master IMS exports its resource and descriptor definitions to the repository. All non-master IMS systems that receive the command return without exporting any definitions with an "IMS not master" return and reason code to OM.
If the EXPORT command is to be processed by a specific IMS, the EXPORT command must be routed to that IMS.
- A Fast Path exclusive transaction definition is exported to the repository without its associated routing code definition
- The transaction definition is being created for the IMS
- A routing code definition with the same name already exists in the repository
- Either the PGM value or the INQ value in the routing code definition is different from the PGM or INQ value in the new transaction definition
If a Fast Path exclusive transaction definition is exported to the repository without its associated routing code definition and a definition for the transaction already exists in the repository for the IMS and either the PGM value or the INQ value is being updated, the PGM value, the INQ value, or both are automatically updated in the associated routing code definition.
If a routing code definition is exported to the repository without an associated transaction definition, the export process fails if the routing code already exists in the repository for the IMS and the routing code definition in the repository is associated with a Fast Path exclusive transaction definition.
Output fields
When
TARGET(RDDS) is specified, message DFS3404I is returned
by each IMS that processes the EXPORT command.
It indicates whether all, some, or none of the specified resource
or descriptors were successfully exported. It also contains the name
of the data set to which the resource or descriptor definitions were
exported. Each DFS3404I message is encapsulated in
a single set of <msg> </msg> XML tags.
When TARGET(REPO) is specified, the EXPORT command results in message DFS3406I, which indicates that the export to the repository was successful, or DFS3407E, which indicates that the export was not successful. These messages include the repository name and repository type. If the export to the repository is not successful due to a CSLRPUPD error, the DFS3407E message contains the CSLRPUPD request return code and reason code. The CSLRPUPD return and reason codes are described in the CSLRRR macro.
- Short label
- Contains the short label generated in the XML output.
- Long label
- Contains the long label generated in the XML output.
- Keyword
- Identifies keyword on the command that caused the field to be generated. The value error appears for output fields that are returned only in the case of an error. N/A (not applicable) appears for output fields that are always returned.
- Meaning
- Provides a brief description of the output field.
| Short label | Long label | Keyword | Meaning |
|---|---|---|---|
| CC | CC | N/A | Completion code. |
| CCTXT | CCText | error | Completion code text that briefly explains the meaning of the nonzero completion code. |
| ERRT | ErrorText | N/A | The error text that describes the error completion code. |
| MBR | MbrName | N/A | IMSplex member that built the output line. |
| NAME | Name | NAME | The name of the resource or descriptor definition that was created or updated in the repository, or the name of the IMS resource list that was created or updated in the repository. |
| TYPE | Type | TYPE | The resource or descriptor type, which can be DB, DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN, or TRANDESC; or LIST for IMS resource lists. |
Return, reason, and completion codes
The following table includes the return and reason codes and a brief explanation of the codes. The return or reason code returned for the command might also indicate an error from a CSL request.
| Return code | Reason code | Meaning |
|---|---|---|
| X'00000000' | X'00000000' | Command completed successfully. The command output contains a line for each resource, accompanied by its completion code. If NAME(*) is specified without OPTION(ALLRSP), no output lines are returned. See the completion code table for details. |
| X'00000004' | X'00001000' | The EXPORT command was not processed on the IMS system, because the IMS system is not the command master. No resource information is returned. |
| X'00000008' | X'0000211F' | Unable to determine the export data set name. The RDDSDSN() keyword was not specified on the command, and there are no system RDDSs defined. |
| X'00000008' | X'0000213A' | The data set specified for the RDDSDSN() keyword is a system RDDS. |
| X'00000008' | X'0000213B' | OPTION(OVERWRITE) is mutually exclusive with OPTION(APPEND). |
| X'00000008' | X'0000213C' | A value other than NAME(*) was specified. NAME(*) is required when exporting to a system RDDS. |
| X'00000008' | X'0000213D' | A value other than TYPE(ALL) was specified. TYPE(ALL) is required when exporting to a system RDDS. |
| X'00000008' | X'0000213E' | OPTION(APPEND) is not allowed when exporting to a system RDDS. |
| X'00000008' | X'0000213F' | OPTION(NOCHECK) can be specified only if OPTION(APPEND) is specified. |
| X'00000008' | X'00002146' | Invalid STARTTIME value. |
| X'00000008' | X'00002147' | TARGET(RDDS) and OPTION(CHANGESONLY) conflict. |
| X'00000008' | X'00002148' | TARGET(RDDS) and SET(IMSID()) conflict. |
| X'00000008' | X'00002149' | TARGET(RDDS) and STARTTIME conflict. |
| X'00000008' | X'0000214A' | TARGET(RDDS) and ENDTIME conflict. |
| X'00000008' | X'0000214B' | TARGET(REPO) and OPTION(APPEND) conflict. |
| X'00000008' | X'0000214C' | TARGET(REPO) and RDDSDSN conflict. |
| X'00000008' | X'0000214D' | Either an invalid ENDTIME value was specified or the ENDTIME value specified was less than or equal to the STARTTIME value specified. |
| X'00000008' | X'0000214F' | RM resource validation error. |
| X'0000000C' | X'00003000' | Command was successful for some resources but failed for others. The command output contains a line for each resource, accompanied by its completion code. If NAME(*) is specified without OPTION(ALLRSP), output lines are only returned for resources with nonzero completion codes. |
| X'0000000C' | X'00003004' | Command was not successful for any of the resources. The command output contains a line for each resource, accompanied by its completion code. See the completion code table for details. |
| X'00000010' | X'00004004' | No CQS address space. |
| X'00000010' | X'0000400C' | Command is not valid on the XRF alternate. |
| X'00000010' | X'00004018' | No resource structure, or resource structure is not available. |
| X'00000010' | X'00004100' | Resource structure is full. |
| X'00000010' | X'00004104' | No RM address space. |
| X'00000010' | X'00004108' | No SCI address space. |
| X'00000010' | X'00004114' | Unable to access the RDDS. The RDDS is either a system RDDS or the data set specified with the RDDSDSN() keyword. |
| X'00000010' | X'00004118' | Unable to allocate the RDDS. The RDDS is either a system RDDS or the data set specified with the RDDSDSN() keyword. |
| X'00000010' | X'0000411C' | The EXPORT command was issued to append definitions to an RDDS, but the RDDS contains invalid data. |
| X'00000010' | X'00004120' | Online change phase is in progress. |
| X'00000010' | X'00004300' | Command is not allowed, because online change for MODBLKS is enabled (DFSDFxxx or DFSCGxxx defined with MODBLKS=OLC, or MODBLKS not defined) and an RDDS was not specified with the RDDSDSN() keyword. |
| X'00000010' | X'00004302' | The RDDS is full. No more definitions can be written to the RDDS. |
| X'00000010' | X'0000432C' | Invalid value is specified for the TYPE() keyword. ALLDESC, DBDESC, PGMDESC, RTCDESC and TRANDESC are not allowed if online change for MODBLKS is enabled (DFSDFxxx or DFSCGxxx defined with MODBLKS=OLC, or MODBLKS not defined). |
| X'00000010' | X'00004330' | None of the system RDDSs defined in the DFSDFxxx PROCLIB member are available for export. |
| X'00000010' | X'00004334' | The RECFM of the RDDS is not VB. |
| X'00000010' | X'00004338' | Invalid RDDS block size. The RDDS must be defined with a block size 4096 - 32760. |
| X'00000010' | X'0000433C' | The RDDS specified with the RDDSDSN() keyword contains definitions written by another IMS. If new definitions are to be appended to the RDDS by a different IMS, OPTION(NOCHECK) must be specified. |
| X'00000010' | X'00004500' | IMS is not enabled to use the repository. |
| X'00000010' | X'00004502' | Repository is not available. |
| X'00000010' | X'00004504' | Repository spare recovery is in progress. |
| X'00000010' | X'00004505' | No IMS resource list. This return code can be returned if the EXPORT command with SET(IMSID(*)) is issued and the repository is empty. The SET(IMSID(*)) keyword cannot be processed because there are no IMS resource lists in the repository. Issue the EXPORT command again by specifying a list of IMS IDs, or issue the EXPORT command again without SET(IMSID()) so that the command defaults to the command master IMS. |
| X'00000010' | X'00004507' | Repository access denied. |
| X'00000010' | X'00004508' | Repository maximum put length exceeded. |
| X'00000010' | X'00004509' | RM data version is lower than the IMS data version. |
| X'00000010' | X'0000450A' | Repository Server is being shut down. |
| X'00000010' | X'0000450B' | Repository Server is not available. |
| X'00000010' | X'0000450C' | Repository Server is busy. |
| X'00000010' | X'0000450D' | RM failed to define some of the internal fields related to the IMSRSC repository. |
| X'00000010' | X'0000450E' | An IMSID list is required. |
| X'00000010' | X'0000450F' | Maximum number of IMSIDs for the repository was reached. |
| X'00000010' | X'00004510' | IMSID member table changed during command processing. |
| X'00000014' | X'00005000' | IMODULE GETSTOR error. |
| X'00000014' | X'0000500C' | AWE could not be obtained. |
| X'00000014' | X'00005004' | DFSOCMD response buffer could not be obtained. |
| X'00000014' | X'00005008' | DFSPOOL storage could not be obtained. |
| X'00000014' | X'00005010' | Unable to obtain latch. |
| X'00000014' | X'00005018' | Unable to obtain a 64-bit buffer. |
| X'00000014' | X'0000501C' | IMODULE GETMAIN error. |
| X'00000014' | X'00005100' | RM request error. |
| X'00000014' | X'00005104' | Unexpected CQS error. |
| X'00000014' | X'00005108' | SCI request error. |
| X'00000014' | X'00005110' | Repository error. |
| X'00000014' | X'0000551C' | A request to update the repository was rejected. Either a corrupted resource list was detected, or the update request was rejected to prevent a corruption of the resource list. Contact IBM Software Support. Send in the output from the command in error, a dump of the local RM address space where the command executed or the dump of all RM address spaces in the IMSplex. Also, send a copy of the IMSRSC repository RID and RMD data sets. |
| X'00000014' | X'00005FFF' | The EXPORT command could not be processed because of an internal error. |
Errors unique to the processing of this command are returned as completion codes. The following table includes an explanation of the completion codes.
| Completion code | Completion code text | Meaning |
|---|---|---|
| 0 | Command completed successfully for this resource or resource descriptor. | |
| 10 | NO RESOURCES FOUND | Resource or descriptor was not found, or the wildcard parameter specified does not match any resource or descriptor names. |
| 2E | NOT ALLOWED FOR RESOURCE | Export of resource or descriptor definition is not allowed. The definitions for IMS defined resources and HALDB partitions cannot be exported. |
| 36 | FP=E/FP=N PGM CONFLICT | The transaction is defined as Fast Path exclusive FP(E), and the program is defined as non-Fast Path FP(N). |
| 39 | FP=E TRAN FOR RTC EXISTS | The routing code definition is being updated, but the routing code is associated with a Fast Path exclusive FP(E) transaction. |
| 3E | FP=N/FP=E PGM CONFLICT | The transaction is defined as non-Fast Path FP(N), and the program is defined as Fast Path exclusive FP(E). |
| 3F | FP=P/BMPTYPE=Y CONFLICT | The transaction is defined as Fast Path potential FP(P), and the program is defined as program type batch BMPTYPE(Y). |
| 40 | PARLIM/SCHDTYPE=SERIAL CONFLICT | The transaction is defined with a PARLIM value other than 65535, and the program is defined as SCHDTYPE(SERIAL). |
| 48 | NOT ALLOWED FOR IMS RESOURCE | Command not allowed for IMS descriptors or IMS resources. DFSDSDB1, DFSDSPG1, DBFDSRT1, and DFSDSTR1 are examples of IMS descriptors. DBF#FPU0 is an example of an IMS resource. |
| 59 | MSC KEYWORD/FP=E PGM CONFLICT | The transaction is defined as remote, but the program is defined as Fast Path exclusive. |
| 5F | INVALID CHARACTERS IN NAME | Resource or descriptor name contains an invalid character. |
| 67 | NO PGM DEFINED | No program is defined. A program name is required for non-remote transaction definitions and routing code definitions. This error should not occur if the definition was created by a valid export or by a utility supplied by IBM. |
| 6A | FP=P/FP=E PGM CONFLICT | The transaction is defined as Fast Path potential FP(P), and the program is defined as Fast Path exclusive FP(E). |
| 6D | INVALID PROGRAM NAME | The program referenced by the transaction or routing code is not defined in the repository for the IMS or being exported for the IMS. A program definition is required for non-remote transaction and routing code definitions. |
| 7A | RTC/FP=N PGM CONFLICT | The program is defined as non-Fast Path FP(N), and a routing code definition that references the program either exists in the repository or is being exported. |
| 90 | INTERNAL ERROR | Resource or descriptor definition was not exported because of an internal error. |
| 94 | RM REQUEST ERROR | An RM request error occurred. The resource definition was not exported. |
| B5 | ROUTING CODE ALREADY EXISTS | A routing code with the same name as the transaction already exists in the repository for the IMS, but either the program name or the INQ value is different. The transaction definition cannot be exported for the IMS. |
| 121 | RESOURCE HAS NO CHANGE | The resource name specified has no changes since the last export. |
| 149 | STARTTIME/ENDTIME MISMATCH | The resource name specified does not match the specified STARTTIME or ENDTIME value. |
| 14D | INVALID CHARACTERS IN IMSID | The IMSID value contains an invalid character. |
| 1D0 | NOT DONE DUE TO ERROR | An error resulted in the command
not being processed for the resource name in the response line. The
resource name that had the error will show the error that was encountered.
All other resource names will have 1D0 completion
code because the export is aborted due to one error. All members are
exported as a single unit of work. |
| 1D1 | NO REPOSITORY DEFINED | No repository is defined. |
| 1D2 | RM VALIDATION ERROR | RM validation error. |
| 1D3 | MEMBER NOT FOUND | The specified resource name is not found. |
| 1D4 | MEMBER IN USE | The specified resource name is in use. |
| 1D5 | NO IMS RESOURCE LIST | No IMS resource list. |
| 1D6 | REPOSITORY ERROR | Repository error. |
| 1D7 | IMPORT CHANGE LIST ERROR | Resource or descriptor is in the process of being imported from the change list in the IMSRSC repository, or the import from the change list failed. The resource or descriptor cannot be exported until it is successfully imported. |
Examples
The following are examples of the EXPORT command:
Example 1 for EXPORT command
EXPORT DEFN TARGET(RDDS) Log for: EXPORT DEFN TARGET(RDDS)
IMSplex . . . . . : PLEX1
Routing . . . . . :
Start time. . . . : 2007.074 12:40:02.30
Stop time . . . . : 2007.074 12:40:03.32
Return code . . . : 00000000
Reason code . . . : 00000000
Reason text . . . :
Command master. . : IMS2
MbrName Messages
-------- -----------------------
IMS1 DFS3404I EXPORT COMMAND COMPLETE FOR ALL , DSN=IMSPLEX1.IMS1.RDDS1.DEFN
IMS2 DFS3404I EXPORT COMMAND COMPLETE FOR ALL , DSN=IMSPLEX1.IMS2.RDDS3.DEFNExplanation: The EXPORT command is routed to two IMS systems: IMS1 and IMS2. Each IMS exports all of its database, program, routing code, and transaction resource and descriptor definitions to its own system RDDS. Because OPTION(ALLRSP) is not specified, the list of exported resources is not returned.
<msg> </msg> tags
and is shown on the same TSO SPOC screen as the return and reason
codes. If the message does not fit on one screen, you might have to
scroll to the right to view the entire message.Example 2 for EXPORT command
EXPORT DEFN TARGET(RDDS) RDDSDSN(IMSPLEX1.IMS2.RDDS.DEFN) OPTION(ALLRSP)Name Type MbrName CC
DBDFLT DBDESC IMS2 0
DEDBJN01 DB IMS2 0
PGMDFLT PGMDESC IMS2 0
CDEBS PGM IMS2 0
RTCDFLT RTCDESC IMS2 0
SMQFP5A RTC IMS2 0
TRANDFLT TRANDESC IMS2 0
CDEBTRN1 TRAN IMS2 0
Log for: EXPORT DEFN TARGET(RDDS) RDDSDSN(IMSPLEX1.IMS2.RDDS.DEFN) OPTION(ALLRSP)
IMSplex . . . . . : PLEX1
Routing . . . . . :
Start time. . . . : 2007.074 12:40:02.30
Stop time . . . . : 2007.074 12:40:03.32
Return code . . . : 00000000
Reason code . . . : 00000000
Reason text . . . :
Command master. . : IMS2
MbrName Messages
-------- -----------------------
IMS2 DFS3404I EXPORT COMMAND COMPLETE FOR ALL , DSN=IMSPLEX1.IMS2.RDDS.DEFN Explanation: The EXPORT command is routed to IMS2. IMS2 exports all of its database, program, routing code, and transaction resource and descriptor definitions to RDDS IMSPLEX1.IMS2.RDDS.DEFN. Because OPTION(ALLRSP) is specified, the list of exported resources is returned.
Example 3 for EXPORT command
EXPORT DEFN TARGET(RDDS) TYPE(ALL) NAME(*) OPTION(ALLRSP)Name Type MbrName CC CCText
PART DB IMS2 0
PARTMAST DB IMS2 0
PGMD01 PGM IMS2 0
RTC001 RTC IMS2 0
TRND01 TRAN IMS2 0
TRND11 TRAN IMS2 0
TRND123 TRAN IMS2 0
TRND01 TRANDESC IMS2 0
Log for: EXPORT DEFN TARGET(RDDS) TYPE(ALL) NAME(*) OPTION(ALLRSP)
IMSplex . . . . . : PLEX1
Routing . . . . . :
Start time. . . . : 2007.074 12:40:02.30
Stop time . . . . : 2007.074 12:40:03.32
Return code . . . : 0200000C
Reason code . . . : 00003000
Reason text . . . : At least one request successful
Command master. . : IMS2
Return Reason
MbrName Code Code Description
-------- ------ ------ -----------
IMS1 00000010 00004330 No system RDDSs are available
MbrName Messages
-------- -----------------------
IMS2 DFS3404I EXPORT COMMAND COMPLETE FOR ALL , DSN=IMSPLEX1.IMS2.RDDS1.DEFN Explanation: The EXPORT command is routed to two IMS systems: IMS1 and IMS2. IMS1 attempts to export its resource and descriptor definitions to a system RDDS, but none of the system RDDSs are available for export. IMS2 successfully exports its resource and descriptor definitions to RDDS IMSPLEX1.IMS2.RDDS1.DEFN.
Example 4 for EXPORT command
EXPORT DEFN TARGET(RDDS) TYPE(DB, DBDESC, TRAN, TRANDESC, PGM, PGMDESC)
NAME(PART*, TRND*, PGMD*) RDDSDSN(IMSPLEX1.IMS2.RDDS.DEFN)Name Type MbrName CC CCText
PGMD* IMS2 10 NO RESOURCES FOUND
PART DB IMS2 0
PARTMAST DB IMS2 0
TRND11 TRAN IMS2 0
TRND120 TRAN IMS2 0
TRND123 TRAN IMS2 0
TRND123 TRANDESC IMS2 0 Log for . . : EXPORT DEFN TARGET(RDDS) TYPE(DB, DBDESC, TRAN, ... More:
IMSplex . . . . . : PLEX1
Routing . . . . . :
Start time. . . . : 2011.124 09:36:06.09
Stop time . . . . : 2011.124 09:36:06.17
Return code . . . : 0200000C
Reason code . . . : 0000300C
Reason text . . . : The command completed with warning(s).
Command master. . : IMS2
Return Reason
MbrName Code Code Reason text
-------- -------- -------- --------------
IMS2 0000000C 00003000 At least one request successful
IMS1 00000004 00001000 IMS not master, cmd ignored
MbrName Messages
-------- -----------------------
IMS2 DFS3404I EXPORT COMMAND COMPLETE FOR SOME, DSN=IMSPLEX1.IMS2.RDDS.DEFN
IMS1 DFS3404I EXPORT COMMAND COMPLETE FOR NONE, DSN=IMSPLEX1.IMS2.RDDS.DEFNCMD(EXPORT DEFN TARGET(RDDS) TYPE(DB, DBDESC, TRAN, TRANDESC, PGM, PGMDESC)
NAME(PART*, TRND*, PGMD*) RDDSDSN(IMSPLEX1.IMS2.RDDS.DEFN))<imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 16:36:06.112826</statime>
<stotime>2011.124 16:36:06.171441</stotime>
<staseq>C7B85E23C774F3FA</staseq>
<stoseq>C7B85E23D94B927E</stoseq>
<rqsttkn1>USRT011 10091756</rqsttkn1>
<rc>0200000C</rc>
<rsn>0000300C</rsn>
<rsnmsg>CSLN055I</rsnmsg>
<rsntxt>The command completed with warning(s).</rsntxt>
</ctl>
<cmderr>
<mbr name="IMS2 ">
<typ>IMS </typ>
<styp>DBDC </styp>
<rc>0000000C</rc>
<rsn>00003000</rsn>
<rsntxt>At least one request successful</rsntxt>
</mbr>
<mbr name="IMS1 ">
<typ>IMS </typ>
<styp>DBDC </styp>
<rc>00000004</rc>
<rsn>00001000</rsn>
<rsntxt>IMS not master, cmd ignored</rsntxt>
</mbr>
</cmderr>
<cmd>
<master>IMS2 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(RDDS) TYPE(DB, DBDESC, TRAN, TRANDESC, PGM,
PGMDESC) NAME(PART*, TRND*, PGMD*) RDDSDSN(IMSPLEX1.IMS2.RDDS.DEFN)
</input>
</cmd>
<cmdrsphdr>
<hdr slbl="NAME" llbl="Name" scope="LCL" sort="a" key="2" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="TYPE" llbl="Type" scope="LCL" sort="a" key="1" scroll="no"
len="8" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="3" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"
len="4" dtype="INT" align="right" skipb="no" />
<hdr slbl="CCTXT" llbl="CCText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
</cmdrsphdr>
<cmdrspdata>
<rsp>NAME(PART ) TYPE(DB) MBR(IMS2 ) CC( 0) </rsp>
<rsp>NAME(PARTMAST) TYPE(DB) MBR(IMS2 ) CC( 0) </rsp>
<rsp>NAME(TRND11 ) TYPE(TRAN) MBR(IMS2 ) CC( 0) </rsp>
<rsp>NAME(TRND120 ) TYPE(TRAN) MBR(IMS2 ) CC( 0) </rsp>
<rsp>NAME(TRND123 ) TYPE(TRAN) MBR(IMS2 ) CC( 0) </rsp>
<rsp>NAME(TRND123 ) TYPE(TRANDESC) MBR(IMS2 ) CC( 0) </rsp>
<rsp>NAME(PGMD* ) TYPE() MBR(IMS2 ) CC( 10) CCTXT(NO RESOURCES
FOUND) </rsp>
</cmdrspdata>
<msgdata>
<mbr name="IMS2 ">
<msg>DFS3404I EXPORT COMMAND COMPLETE FOR SOME,
DSN=IMSPLEX1.IMS2.RDDS.DEFN </msg>
</mbr>
<mbr name="IMS1 ">
<msg>DFS3404I EXPORT COMMAND COMPLETE FOR NONE,
DSN=IMSPLEX1.IMS2.RDDS.DEFN </msg>
</mbr>
</msgdata>
</imsout> Explanation: The EXPORT command is routed to two IMS systems: IMS1 and IMS2. Because the data set is a non-system RDDS, only the IMS that is selected as the command master can process the command. OM selects IMS2 as the command master. IMS2 exports a set of resource and descriptor definitions whose names match the PART* and TRND* wildcard values. No resources or descriptors were found matching the PGMD* wildcard value. IMS1 does not process the command because it is not the command master.
Example 5 for EXPORT command
EXPORT DEFN TARGET(RDDS) TYPE(ALL) NAME(*) Log for . . : EXPORT DEFN TARGET(RDDS) TYPE(ALL) NAME(*)
IMSplex . . . . . : PLEX1
Routing . . . . . : IMS1
Start time. . . . : 2011.124 14:22:57.39
Stop time . . . . : 2011.124 14:22:57.41
Return code . . . : 0200000C
Reason code . . . : 00003004
Reason text . . . : No requests were successful.
Command master. . : IMS1
Return Reason
MbrName Code Code Reason text
-------- -------- -------- --------------
IMS1 00000008 0000211F No system RDDSs defined, rddsdsn() required CMD(EXPORT DEFN TARGET(RDDS) TYPE(ALL) NAME(*))<imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 21:22:57.408936</statime>
<stotime>2011.124 21:22:57.409591</stotime>
<staseq>C7B8A25066BA8BF2</staseq>
<stoseq>C7B8A25066E37072</stoseq>
<rqsttkn1>USRT011 10142257</rqsttkn1>
<rc>0200000C</rc>
<rsn>00003004</rsn>
<rsnmsg>CSLN024I</rsnmsg>
<rsntxt>No requests were successful.</rsntxt>
</ctl>
<cmderr>
<mbr name="IMS1 ">
<typ>IMS </typ>
<styp>DBDC </styp>
<rc>00000008</rc>
<rsn>0000211F</rsn>
<rsntxt>No system RDDSs defined, rddsdsn() required</rsntxt>
</mbr>
</cmderr>
<cmd>
<master>IMS1 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(RDDS) TYPE(ALL) NAME(*) </input>
</cmd>
</imsout> Explanation: The EXPORT command is sent to IMS1. There are no system RDDSs defined in DFSDFxxx PROCLIB member of IMS1, and the RDDSDSN() keyword was not specified on the EXPORT command. The EXPORT command cannot be processed.
Example 6 for EXPORT command
EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) SET(IMSID(*)) Log for . . : EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) SET(I... More: >
IMSplex . . . . . : PLEX1
Routing . . . . . : IMS1
Start time. . . . : 2011.123 22:16:24.38
Stop time . . . . : 2011.123 22:16:28.15
Return code . . . : 00000000
Reason code . . . : 00000000
Reason text . . . :
Command master. . : IMS1
MbrName Messages
-------- -----------------------
IMS1 DFS3406I EXPORT COMMAND COMPLETE FOR ALL, REPOTYPE=IMSRSC, REPONAME=IMS_REPOS CMD(EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) SET(IMSID(*))) <imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 05:16:24.395621</statime>
<stotime>2011.124 05:16:28.150725</stotime>
<staseq>C7B7CA45F4365B32</staseq>
<stoseq>C7B7CA4988FC5C3A</stoseq>
<rqsttkn1>USRT011 10221624</rqsttkn1>
<rc>00000000</rc>
<rsn>00000000</rsn>
</ctl>
<cmd>
<master>IMS1 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) SET(IMSID(*)) </input>
</cmd>
<msgdata>
<mbr name="IMS1 ">
<msg>DFS3406I EXPORT COMMAND COMPLETE FOR ALL, REPOTYPE=IMSRSC,
REPONAME=IMS_REPOS </msg>
</mbr>
</msgdata>
</imsout> Explanation: All the runtime resource definitions for all the database, transaction, program, routing code resources and descriptors from IMS are exported to the repository as the stored resource definitions for all IMS systems in the IMSplex. The command is processed by the command master IMS, IMS1. The IMS resource lists for all IMS systems defined to use the repository are updated. The IMS resource lists that have been updated are also returned on the command response.
Example 7 for EXPORT command
EXPORT DEFN TARGET(REPO) NAME(TRANA,DBA,RTCA,PGMA) TYPE(ALL) SET(IMSID(IMS1,IMS3)) Response for: EXPORT DEFN TARGET(REPO) NAME(TRANA,DBA,RTCA,PG...
Name Type MbrName CC
DBA DB IMS1 0
IMS1 LIST IMS1 0
IMS3 LIST IMS1 0
PGMA PGM IMS1 0
RTCA RTC IMS1 0
TRANA TRAN IMS1 0 Log for . . : EXPORT DEFN TARGET(REPO) NAME(TRANA,DBA,RTCA,PG... More: >
IMSplex . . . . . : PLEX1
Routing . . . . . : IMS1
Start time. . . . : 2011.123 22:39:45.76
Stop time . . . . : 2011.123 22:39:45.96
Return code . . . : 00000000
Reason code . . . : 00000000
Reason text . . . :
Command master. . : IMS1
MbrName Messages
-------- -----------------------
IMS1 DFS3406I EXPORT COMMAND COMPLETE FOR ALL, REPOTYPE=IMSRSC, REPONAME=IMS_REPOSCMD(EXPORT DEFN TARGET(REPO) NAME(TRANA,DBA,RTCA,PGMA) TYPE(ALL) SET(IMSID(IMS1,IMS3)))<imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 05:39:45.784253</statime>
<stotime>2011.124 05:39:45.958539</stotime>
<staseq>C7B7CF7E6C1BD337</staseq>
<stoseq>C7B7CF7E96A8B4F7</stoseq>
<rqsttkn1>USRT011 10223945</rqsttkn1>
<rc>00000000</rc>
<rsn>00000000</rsn>
</ctl>
<cmd>
<master>IMS1 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(REPO) NAME(TRANA,DBA,RTCA,PGMA)
TYPE(ALL) SET(IMSID(IMS1,IMS3)) </input>
</cmd>
<cmdrsphdr>
<hdr slbl="NAME" llbl="Name" scope="LCL" sort="a" key="2" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="TYPE" llbl="Type" scope="LCL" sort="a" key="1" scroll="no"
len="8" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="3" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"
len="4" dtype="INT" align="right" skipb="no" />
<hdr slbl="CCTXT" llbl="CCText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
</cmdrsphdr>
<cmdrspdata>
<rsp>NAME(DBA ) TYPE(DB) MBR(IMS1 ) CC( 0) </rsp>
<rsp>NAME(PGMA ) TYPE(PGM) MBR(IMS1 ) CC( 0) </rsp>
<rsp>NAME(RTCA ) TYPE(RTC) MBR(IMS1 ) CC( 0) </rsp>
<rsp>NAME(TRANA ) TYPE(TRAN) MBR(IMS1 ) CC( 0) </rsp>
<rsp>NAME(IMS1 ) TYPE(LIST) MBR(IMS1 ) CC( 0) </rsp>
<rsp>NAME(IMS3 ) TYPE(LIST) MBR(IMS1 ) CC( 0) </rsp>
</cmdrspdata>
<msgdata>
<mbr name="IMS1 ">
<msg>DFS3406I EXPORT COMMAND COMPLETE FOR ALL, REPOTYPE=IMSRSC,
REPONAME=IMS_REPOS </msg>
</mbr>
</msgdata>
</imsout> Explanation: The runtime resource definitions for the database named DBA, transaction named TRANA, program named PGMA, and routing code named RTCA are exported to the repository as the stored resource definitions for IMS1 and IMS3.
The command is processed by the command master IMS. In this case, only IMS2 processed the command.
The IMS resource lists for IMS systems IMS1 and IMS3 are updated and are available for those IMS systems to import runtime resource definitions. The IMS resource list for the command master IMS2 is not updated in the repository because it is not specified in the SET(IMSID()) keyword.
This example shows how to use the EXPORT command to update the IMS resource list for another IMS in the IMSplex.
Example 8 for EXPORT command
EXPORT DEFN TARGET(REPO) NAME(*) TYPE(PGM,PGMDESC,TRAN,TRANDESC)
SET(IMSID(*))Log for . . : EXPORT DEFN TARGET(REPO) NAME(*) TYPE(PGM,PGMDES... More: +>
IMSplex . . . . . : PLEX1
Routing . . . . . : IMS2
Start time. . . . : 2011.124 14:05:50.22
Stop time . . . . : 2011.124 14:05:50.27
Return code . . . : 0200000C
Reason code . . . : 00003008
Reason text . . . : None of the clients were successful.
Command master. . : IMS2
Return Reason
MbrName Code Code Reason text
-------- -------- -------- --------------
IMS2 00000010 0000450B Repository Server is not available
MbrName Messages
-------- -----------------------
IMS2 DFS3407E EXPORT COMMAND COMPLETE FOR NONE, REQUEST=CSLRPUPD,
RC=03000014, RSN=00005508, ERRORTEXT=, MBR=RSC, REPOTYPE=IMSRSC, REPONAME=IMS_REPOS
CMD(EXPORT DEFN TARGET(REPO) NAME(*) TYPE(PGM,PGMDESC,TRAN,TRANDESC)
SET(IMSID(*)))<imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 21:05:50.248438</statime>
<stotime>2011.124 21:05:50.270743</stotime>
<staseq>C7B89E7CD31F676E</staseq>
<stoseq>C7B89E7CD891703C</stoseq>
<rqsttkn1>USRT011 10140550</rqsttkn1>
<rc>0200000C</rc>
<rsn>00003008</rsn>
<rsnmsg>CSLN054I</rsnmsg>
<rsntxt>None of the clients were successful.</rsntxt>
</ctl>
<cmderr>
<mbr name="IMS2 ">
<typ>IMS </typ>
<styp>DBDC </styp>
<rc>00000010</rc>
<rsn>0000450B</rsn>
<rsntxt>Repository Server is not available</rsntxt>
</mbr>
</cmderr>
<cmd>
<master>IMS2 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(REPO) NAME(*) TYPE(PGM,PGMDESC,TRAN,TRANDESC)
SET(IMSID(*)) </input>
</cmd>
<msgdata>
<mbr name="IMS2 ">
<msg>DFS3407E EXPORT COMMAND COMPLETE FOR NONE, REQUEST=CSLRPUPD,
RC=03000014, RSN=00005508, ERRORTEXT=, MBR=RSC, REPOTYPE=IMSRSC,
REPONAME=IMS_REPOS </msg>
</mbr>
</msgdata>
</imsout> Explanation: The export of the program and transaction resources and descriptors to the repository failed because the Repository Server was not available. The CSLRPUPD return and reason codes of 03000014/00005508 indicates that the Repository Server is not available. See the CSLRRR macro for a description of the return code and reason code.
Example 9 for EXPORT command
EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRANA) TYPE(ALL)
SET(IMSID(*)) OPTION(ALLRSP) Response for: EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRAN...
Name Type MbrName CC CCText
DBA DB IMS2 1D0 NOT DONE DUE TO ERROR
IMS1 LIST IMS2 1D0 NOT DONE DUE TO ERROR
IMS2 LIST IMS2 1D0 NOT DONE DUE TO ERROR
IMS3 LIST IMS2 1D0 NOT DONE DUE TO ERROR
PGMA PGM IMS2 1D0 NOT DONE DUE TO ERROR
RTCA RTC IMS2 1D0 NOT DONE DUE TO ERROR
TRANA TRAN IMS2 67 NO PGM DEFINED Log for . . : EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRAN... More: +>
IMSplex . . . . . : PLEX1
Routing . . . . . : IMS2
Start time. . . . : 2011.124 11:32:16.90
Stop time . . . . : 2011.124 11:32:17.19
Return code . . . : 0200000C
Reason code . . . : 00003008
Reason text . . . : None of the clients were successful.
Command master. . : IMS2
Return Reason
MbrName Code Code Reason text
-------- -------- -------- --------------
IMS2 0000000C 00003004 No requests were successful
MbrName Messages
-------- -----------------------
IMS2 DFS3407E EXPORT COMMAND COMPLETE FOR NONE, REQUEST=CSLRPUPD,
RC=0300000C, RSN=00003004, ERRORTEXT=00000000 03000008 00002514 00000000
00000000 00000000, MBR=RSC, REPOTYPE=IMSRSC, REPONAME=IMS_REPOSCMD(EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRANA) TYPE(ALL)
SET(IMSID(*)) OPTION(ALLRSP))<imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 18:32:16.943085</statime>
<stotime>2011.124 18:32:17.187129</stotime>
<staseq>C7B87C2A54FEDBEC</staseq>
<stoseq>C7B87C2A909390F0</stoseq>
<rqsttkn1>USRT011 10113216</rqsttkn1>
<rc>0200000C</rc>
<rsn>00003008</rsn>
<rsnmsg>CSLN054I</rsnmsg>
<rsntxt>None of the clients were successful.</rsntxt>
</ctl>
<cmderr>
<mbr name="IMS2 ">
<typ>IMS </typ>
<styp>DBDC </styp>
<rc>0000000C</rc>
<rsn>00003004</rsn>
<rsntxt>No requests were successful</rsntxt>
</mbr>
</cmderr>
<cmd>
<master>IMS2 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRANA)
TYPE(ALL)SET(IMSID(*)) OPTION(ALLRSP) </input>
</cmd>
<cmdrsphdr>
<hdr slbl="NAME" llbl="Name" scope="LCL" sort="a" key="2" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="TYPE" llbl="Type" scope="LCL" sort="a" key="1" scroll="no"
len="8" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="3" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"
len="4" dtype="INT" align="right" skipb="no" />
<hdr slbl="CCTXT" llbl="CCText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
</cmdrsphdr>
<cmdrspdata>
<rsp>NAME(DBA ) TYPE(DB) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(PGMA ) TYPE(PGM) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(RTCA ) TYPE(RTC) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(TRANA ) TYPE(TRAN) MBR(IMS2 ) CC( 67) CCTXT(NO PGM
DEFINED) </rsp>
<rsp>NAME(IMS1 ) TYPE(LIST) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(IMS2 ) TYPE(LIST) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(IMS3 ) TYPE(LIST) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR)</rsp>
</cmdrspdata>
<msgdata>
<mbr name="IMS2 ">
<msg>DFS3407E EXPORT COMMAND COMPLETE FOR NONE, REQUEST=CSLRPUPD,
RC=0300000C, RSN=00003004, ERRORTEXT=00000000 03000008 00002514
00000000 00000000 00000000, MBR=RSC, REPOTYPE=IMSRSC,
REPONAME=IMS_REPOS </msg>
</mbr>
</msgdata>
</imsout> Explanation: The export of the program, transaction, database, and routing code resource definitions to the repository failed because the definition for the program referenced by TRANA does not exist in the repository and is not being exported. A completion code of 1D0, Not done due to error, is returned for all members being updated in the repository except the one that failed. If the error is due to a resource, MBR=RSC is set in the DFS3407E message.
Example 10 for EXPORT command
EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRANA) TYPE(ALL)
SET(IMSID(IM1*)) OPTION(ALLRSP) Response for: EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRAN...
Name Type MbrName CC CCText
DBA DB IMS2 1D0 NOT DONE DUE TO ERROR
IM1* LIST IMS2 1D5 NO IMS RESOURCE LIST
PGMA PGM IMS2 1D0 NOT DONE DUE TO ERROR
RTCA RTC IMS2 1D0 NOT DONE DUE TO ERROR
TRANA TRAN IMS2 1D0 NOT DONE DUE TO ERROR Log for . . : EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRAN... More: +>
IMSplex . . . . . : PLEX1
Routing . . . . . : IMS2
Start time. . . . : 2011.124 12:21:47.67
Stop time . . . . : 2011.124 12:21:47.76
Return code . . . : 0200000C
Reason code . . . : 00003008
Reason text . . . : None of the clients were successful.
Command master. . : IMS2
Return Reason
MbrName Code Code Reason text
-------- -------- -------- --------------
IMS2 0000000C 00003004 No requests were successful
MbrName Messages
-------- -----------------------
IMS2 DFS3407E EXPORT COMMAND COMPLETE FOR NONE, REQUEST=CSLRPUPD,
RC=0300000C, RSN=00003004, ERRORTEXT=, MBR=LST, REPOTYPE=IMSRSC,
REPONAME=IMS_REPOS CMD(EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRANA) TYPE(ALL)
SET(IMSID(IM1*)) OPTION(ALLRSP))<imsout>
<ctl>
<omname>OM1OM </omname>
<omvsn>1.5.0</omvsn>
<xmlvsn>20 </xmlvsn>
<statime>2011.124 19:21:47.695676</statime>
<stotime>2011.124 19:21:47.758331</stotime>
<staseq>C7B8873B7663C765</staseq>
<stoseq>C7B8873B85AFBBEA</stoseq>
<rqsttkn1>USRT011 10122147</rqsttkn1>
<rc>0200000C</rc>
<rsn>00003008</rsn>
<rsnmsg>CSLN054I</rsnmsg>
<rsntxt>None of the clients were successful.</rsntxt>
</ctl>
<cmderr>
<mbr name="IMS2 ">
<typ>IMS </typ>
<styp>DBDC </styp>
<rc>0000000C</rc>
<rsn>00003004</rsn>
<rsntxt>No requests were successful</rsntxt>
</mbr>
</cmderr>
<cmd>
<master>IMS2 </master>
<userid>USRT011 </userid>
<verb>EXP </verb>
<kwd>DEFN </kwd>
<input>EXPORT DEFN TARGET(REPO) NAME(DBA,PGMA,RTCA,TRANA)
TYPE(ALL)SET(IMSID(IM1*)) OPTION(ALLRSP) </input>
</cmd>
<cmdrsphdr>
<hdr slbl="NAME" llbl="Name" scope="LCL" sort="a" key="2" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="TYPE" llbl="Type" scope="LCL" sort="a" key="1" scroll="no"
len="8" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="MBR" llbl="MbrName" scope="LCL" sort="a" key="3" scroll="no"
len="8" dtype="CHAR" align="left" />
<hdr slbl="CC" llbl="CC" scope="LCL" sort="n" key="0" scroll="yes"
len="4" dtype="INT" align="right" skipb="no" />
<hdr slbl="CCTXT" llbl="CCText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
<hdr slbl="ERRT" llbl="ErrorText" scope="LCL" sort="n" key="0"
scroll="yes" len="*" dtype="CHAR" skipb="yes" align="left" />
</cmdrsphdr>
<cmdrspdata>
<rsp>NAME(DBA ) TYPE(DB) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(PGMA ) TYPE(PGM) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(RTCA ) TYPE(RTC) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(TRANA ) TYPE(TRAN) MBR(IMS2 ) CC( 1D0) CCTXT(NOT DONE DUE TO ERROR) </rsp>
<rsp>NAME(IM1* ) TYPE(LIST) MBR(IMS2 ) CC( 1D5) CCTXT(NO IMS
RESOURCE LIST) </rsp>
</cmdrspdata>
<msgdata>
<mbr name="IMS2 ">
<msg>DFS3407E EXPORT COMMAND COMPLETE FOR NONE, REQUEST=CSLRPUPD,
RC=0300000C, RSN=00003004, ERRORTEXT=, MBR=LST, REPOTYPE=IMSRSC,
REPONAME=IMS_REPOS </msg>
</mbr>
</msgdata>
</imsout> Explanation: The export of the program, transaction, database, and routing code resource definitions to the repository failed because there are no IMS resource lists in the repository the match the wildcard value IM1*. A completion code of 1D0, Not done due to error, is returned for all the members being updated in the repository except the one that failed. MBR=LST indicates that the error is for an IMS resource list.