IMPORT control statement

The IMPORT control statement specifies the "to" PDS or PDSE history file data set name followed by the "from" data set name.

Figure 1. Syntax

Description

The fault entries in the "from" data set are copied and their prefix characters set to the prefix of the "to" history file. When possible, the imported fault number is left the same, however, the fault number is altered where necessary to ensure no existing "to" history file fault entries are overwritten. If the DELETE option is in effect, the fault member is deleted in the "from" data set after a successful copy. DELETE is the default setting.

Any tightly coupled associated dump data sets are automatically attempted to be copied and linked with the new fault entries. This is necessary because Fault Analyzer maintains a unique link between a fault entry and its tightly coupled associated dump data set, both for access control and to enable the automatic deletion of the dump data set when the fault entry is deleted. For additional information about associated dump data sets, see Associated dump data sets.

The name of the copied dump data set is determined as follows:

Depending on the dump data set type, the appropriate IDIOPTLM configuration-options load module option specification of RFRDSN, XDUMPDSN, or SDUMPDSN. This is the default. For details, see Customize Fault Analyzer by using an IDIOPTLM configuration-options module.
Using an IDIUTIL Import user exit. For details, see IDIUTIL Import user exit.

If a single fault ID is included with the "from" data set specification, for example TEMP.HIST(F00234), then only that fault ID is imported and deleted.

This function allows fault members that have been sent using the TSO XMIT command from one system to be received into a staging data set and then imported to the required target history file. For an example of this, refer to Managing history files across MVS systems without shared DASD. The IMPORT user exit could be used with this function to notify users that the imported entries have arrived.

The PACKAGE option should only be used in these situations:

By the IDIROBOT exec (see IDIROBOT: sample REXX exec to receive fault entries).
When importing a fault entry package created using the P line command from the Fault Entry List display (see Packaging fault entries).
When importing a fault entry package created using the IDIXMIT formatting user exit (see On-demand implementation).

Regardless of which method was used to create the fault entry package, the IMPORT input data set must be untersed before running IDIUTIL.

When the PACKAGE option is used, Fault Analyzer performs additional checks on the IMPORT input data set and parameters to ensure that:

faultid has been specified.
from-data-set-name does not contain a $$INDEX member and is not managed by the IDIS subsystem.

The IDIUTIL Import user exit (see IDIUTIL Import user exit) can be used with the IMPORT control statement to further select the history file entries that should be imported.

An example showing the use of the IMPORT control statement is provided in Example 7. Importing history file entries.