Transferring Objects

#### Search Results

Search

# Transferring Objects

To transfer Entire Output Management objects from one environment to another (for example, from a mainframe to a UNIX system), you can export them from the originating environment to an XML file, and then import this XML file into the target environment.

Or you can transfer objects directly within you network environment from one Entire Output Management system file to another.

This section covers the following topics:

- Exporting Objects

- Importing Objects

- Transferring Objects Directly

Note
Active data (active reports, active bundles, printout-queue elements, default definitions) cannot be transferred.

## Exporting Objects

To export objects, you define an export task in the originating environment. This task creates an XML file and writes the data to be exported to this file. In the export task, you specify which objects are to be written to which export file and when.

From an export file, the data can then be loaded into the target environment, as described below under Importing Objects.

This section covers the following topics:

- Creating an Export Task

- Modifying an Export Task

- Deleting an Export Task

- Browsing an Export File

### Creating an Export Task

To create a new export task:

1. Select the System Administration > Export Task node in the object workspace.

2. Invoke the context menu and choose Maintain.

   A list of all export tasks which have been created but have not yet been executed is displayed.

3. Invoke the context menu and choose New.

   A window is displayed in which you can specify the task details. The fields are described below.

Field | Explanation
--- | ---
Object type | Select the type of object to be exported: bundles, calendars, distribution lists, mainframe nodes, physical printers, logical printers, reports, user profiles, UNIX nodes.
Object name | Specify a character string, optionally with the wildcards "*" (for any number of characters) and "?" (for a single character), to export all objects of the specified type whose names contain this character string.
Export node | Specify the destination of the export file. For a mainframe node, enter a node number; for a UNIX node (as defined in the UNIX defaults) enter a node name.
Export file | Specify a name for the file.
Execution time | Specify a date and time for the export to be performed by the monitor. The monitor will then end its cycle and start the export function as soon as all monitor tasks are idle.
Write detailed log | Select this field if you wish the execution of each object to be logged in the monitor log.

Alternatively, you can create an export task in batch mode in the Entire Output Management server environment.

To export objects in batch mode:

- Execute a batch job which invokes the program `REXPORT` with the following parameters (using the current input delimiter):

  `object-type,name,log-Y/N,schedule-date (YYYY-MM-DD),schedule-time (HH:MM),export-node,export-file`

  Enter a line for each object type, and after that a line with a period (.).

  #### Example for z/OS:

      //CMSYNIN  DD  *
      SYSNOM;user-ID;password
      REXPORT
      PR,PRINTER*,N,2014-12-12,11:28,npr_unix,$SAG/exppr.xml
      US,USER*,N,2014-12-12,11:30,npr_unix;$SAG/expus.xml
      CA,*,N,2014-12-12,11:30,148,ESM.NOM.EXPORT.CALENDAR
      .
      FIN
      /*

### Modifying an Export Task

To modify an export task:

1. Select the System Administration > Export Task node in the object workspace.

2. Invoke the context menu and choose Maintain.

   A list of all export tasks which have been created but have not yet been executed is displayed.

3. Select the desired export task, invoke the context menu and choose Open.

   A window is displayed in which you can change the task specifications. The fields are described under Creating an Export Task above.

### Deleting an Export Task

To delete an export task:

1. Select the System Administration > Export Task node in the object workspace.

2. Invoke the context menu and choose Maintain.

   A list of all export tasks which have been created but have not yet been executed is displayed.

3. Select the desired export task, invoke the context menu and choose Delete.

   The task will be deleted.

### Browsing an Export File

This function is used to see which data are contained in an export file.

To browse an export file:

1. Select the System Administration > Export Task node in the object workspace.

2. Invoke the context menu and choose Browse export file.

3. A window is displayed, in which you enter the name and path of the desired file.

   The contents of the file will be displayed.

## Importing Objects

The importing has to be done in the Entire Output Management server environment.

To import objects:

- In the target environment, execute a batch job which invokes the program `RMIMPORT` in the library `SYSNOM`.

  On UNIX systems, you can use the script `nomimport.bsh` as a template for invoking `RMIMPORT`.

  `RMIMPORT` must be invoked with the parameters described below, and the export file must be assigned to Work File 1.

  `RMIMPORT` reads all object data from Work File 1 and imports them into the target environment.

#### RMIMPORT Parameters

Parameter | Possible Values | Function
--- | --- | ---
1st parameter: Overwrite objects | `Y` or `N` | Determines whether or not existing objects in the target environment are to be overwritten by objects of the same names loaded from the export file.
2nd parameter: Trace | `Y` or `N` | Determines whether a trace is to be written or not.
3rd parameter: Container file database ID | `dbid` or `0` | Specify the database ID of the container file to be used. Specify `0` if the database ID is to be the same as the one from which the objects were exported.
4th parameter: Container file number | `fnr` or `0` | Specify the file number of the container file to be used. Specify `0` if the file number is to be the same as the one from which the objects were exported.

## Transferring Objects Directly

With this function, you can copy objects to a target environment on another database, for example, to transfer objects from a test environment to a production environment.

You can transfer the following objects:

- bundles,

- calendars,

- distribution lists,

- folders,

- logical printers,

- physical printers,

- reports,

- users.

The transfer procedure is the same for all types of objects.

To transfer objects:

1. Select the System Administration > Transfer Objects node in the object workspace.

2. Invoke the context menu and choose Transfer.

   The Transfer Objects to a Target Environment window is displayed.

3. Select an object type.

   The transfer dialog for that object type is displayed, listing all objects of the selected type, and offering the appropriate options and filter possibilities.

4. In the to target DBID / FNR fields, enter the database ID and file number of the Entire Output Management file to which the objects are to be copied.

5. In addition, you can select the following options:

   Option | Explanation
   --- | ---
   Overwrite objects if they already exist in target environment | If an object is copied and an object of the same name already exists in the target environment, the copied object will replace the existing object.
   Copy with authorization | If an object has an authorization list, this will also be copied (not applicable to users, calendars and physical printers).
   Copy report in bundle if report not defined in target environment | This option is only available for bundles: If a report contained in a bundle does not yet exist in the target environment, this report will also be copied.

   Select the desired options.

6. If you do not want to transfer all objects, specify selection criteria in the Filter fields, and then choose the Search button.

   Now only the objects which satisfy the selection criteria are listed, and only these will be copied.

7. Choose the Transfer button.

   The selected objects are copied to the specified target environment.

   If any objects could not be copied, these will be listed, also stating the reason why they could not be copied.

8. To copy further objects, choose the Further selection button.

   Then repeat Steps 4 to 7.

### On this page

- Exporting Objects
- Importing Objects
- Transferring Objects Directly