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, using the Transfer Object Facility.

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

### Creating an Export Task

To create an export task:

1. Enter the direct command `EXPORT` in the command line.

   The Object Export screen will be displayed.

2. On this screen, you specify which objects are to be exported. The fields are described below.

3. When you have made the specifications, press PF5.

Field | Explanation
--- | ---
Object type | Specify the type of object to be exported: `BU` = bundles, `CA` = calendars, `DL` = distribution lists, `NO` = mainframe nodes, `PH` = physical printers, `PR` = logical printers, `RP` = reports, `US` = user profiles, `UX` = 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 | Set this field to "Y" 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
      /*

## 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

This section covers the following topics:

- Invoking the Transfer Object Facility

- Related Objects

- Fields Common to All Screens

- Transferring Bundles

- Transferring Calendars

- Transferring Distribution Lists

- Transferring Logical Printers

- Transferring Physical Printers

- Transferring Reports

- Transferring Users

- Transferring Folders

### Invoking the Transfer Object Facility

To invoke the Transfer Object facility:

1. Enter `10` in the command line of the System Administration menu.

   The Transfer Object Menu is displayed.

2. On this menu, you select the object type to be copied:

        1 Bundle Definitions
        2 Calendar Definitions
        3 Distribution List Definitions
        4 Logical Printer Definitions
        5 Physical Printer Definitions
        6 Report Definitions
        7 User Definitions
        8 Folder Definitions

### Related Objects

Some objects have so-called "related" (that is, dependent) objects. Before you copy an object, you have to first copy its related objects into the target environment.

To see which are the related objects of an object, you mark it with the line command `XR` on the Copy ... to a Target Environment screen.

The related objects are different for each object type, as indicated in the function-specific descriptions below.

### Fields Common to All Screens

The following fields are common to all Copy ... to a Target Environment screens of the Transfer Object facility:

Field | Explanation
--- | ---
Source NOM-DB/FILE | These fields display the database ID and file number of the file from which the objects will be copied.
Target NOM-DB/FILE | In these fields, you specify the database ID and file number of the file to which the objects are to be copied.
Authorization (Y/N) | This field only applies to the following objects: bundles, distribution lists, logical printers, reports, folders. You can copy an object with or without its authorization list. To also copy the authorization list, you enter a `Y` in this field. The copying of an authorization list requires that all users who are on the authorization list exist in the target environment. To see which users are on the authorization list, mark the object with the line command `AU` on the Copy ... to a Target Environment screen.
exist (yes/no) | This field indicates whether the object already exists in the target environment. To display the information in this field, you have to specify the Target file (see above) first.
Msg | Possible values: "copied", "replaced", "error".

### Transferring Bundles

#### Related Objects

The related objects of a bundle, as shown with the line command `XR`, are:

Field | Explanation
--- | ---
First Window:
Coordinator | Name of the bundle coordinator.
Trigger Reports | Reports specified to trigger automatic bundle printing.
Printer | Printer(s) specified for automatic printing.
Second Window:
Seq | Sequence in which the report is printed within the specified group or bundle.
Report | Report name.

To copy a bundle to another environment:

1. Enter `1` in the command line of the Transfer Object Menu.

   The Copy Bundle to a Target Environment screen is displayed, listing all bundles which exist in the source environment.

   For every bundle, its name, its description and the number of reports contained in the bundle are displayed. With PF9 (Ext) you can switch to short names display.

   By using asterisk notation in the field above the names, you can restrict the list to contain only certain bundles.

2. Enter the line command `CO` next to the bundle to be copied.

   The bundle - and, if specified, its authorization list - will be copied to the specified target file.

### Transferring Calendars

To copy a calendar to another environment:

1. Enter `2` in the command line of the Transfer Object Menu.

   The Copy Calendar to a Target Environment screen is displayed, listing all calendars which exist in the source environment.

   For every calendar, its name and year are displayed.

   By using asterisk notation in the input field above the names, you can restrict the list to contain only certain calendars.

2. Enter the line command `CO` next to the calendar to be copied.

   The calendar will be copied to the specified target file.

### Transferring Distribution Lists

#### Related Objects

The related objects of a distribution list are its members, that is, the users and distribution lists it contains.

To copy a distribution list to another environment:

1. Enter `3` in the command line of the Transfer Object Menu.

   The Copy Distribution List to a Target Environment screen is displayed, listing all distribution lists which exist in the source environment.

   For every distribution list, the following is displayed: its name, a short description, the number of its members. An asterisk (*) in the field "Part of" indicates that the distribution list is part of another distribution list.

   By using asterisk notation in the input field above the names, you can restrict the list to contain only certain distribution lists.

2. Enter the line command `CO` next to the distribution list to be copied.

   The distribution list - and, if specified, its authorization list - will be copied to the specified target file.

### Transferring Logical Printers

#### Related Objects

The related object of a logical printer is the physical printer associated with it.

To copy a logical printer to another environment:

1. Enter `4` in the command line of the Transfer Object Menu.

   The Copy Printer to a Target Environment screen is displayed, listing all logical printers which exist in the source environment.

   For every logical printer, its ID, its description, and the location of the associated physical printer (as taken from the definition of the physical printer) are displayed.

   By using asterisk notation in the input field above the printer IDs, you can restrict the list to contain only certain printers.

2. Enter the line command `CO` next to the logical printer to be copied.

   The printer - and, if specified, its authorization list - will be copied to the specified target file.

### Transferring Physical Printers

To copy a physical printer to another environment:

1. Enter `5` in the command line of the Transfer Object Menu.

   The Copy Physical Printer to a Target Environment screen is displayed, listing all physical printers which exist in the source environment.

   For every physical printer, its VTAM ID (or SYSPRINT for system printers, or DISK for printing to disk) and its location are displayed.

   By using asterisk notation in the input field above the VTAM IDs, you can restrict the list to contain only certain printers.

2. Enter the line command `CO` next to the printer to be copied.

   The printer will be copied to the specified target file.

### Transferring Reports

#### Related Objects

The related objects of a report, as shown with the line command `XR`, are:

Field | Explanation
--- | ---
User/List | User or distribution list in the Distribute to ... field of the report definition.
Printer | Logical printer defined for automatic printing of the report.

To copy a report to another environment:

1. Enter `6` in the command line of the Transfer Object Menu.

   The Copy Report to a Target Environment screen is displayed, listing all reports which exist in the source environment.

   For every report, its name and description are displayed. With PF9 (Ext), you can toggle to short names display.

   By using asterisk notation in the input field above the report names, you can restrict the list to contain only certain reports.

2. Enter the line command `CO` next to the report to be copied.

   The report - and, if specified, its authorization list - will be copied to the specified target file.

### Transferring Users

To copy a user to another environment:

1. Enter `7` in the command line of the Transfer Object Menu.

   The Copy User to a Target Environment screen is displayed, listing all users which exist in the source environment.

   For every user, the user ID and name are displayed.

   By using asterisk notation in the input field above the user IDs, you can restrict the list to contain only certain users.

2. Enter the line command `CO` next to the user to be copied.

   The user will be copied to the specified target file.

### Transferring Folders

#### Related Objects

The related objects of a folder are the folders which are linked to it.

To copy a folder to another environment:

1. Enter `8` in the command line of the Transfer Object Menu.

   The Copy Folder to a Target Environment screen is displayed.

2. In the For User ID field, enter the ID of the user whose folders are to be copied. By default, the field contains your own user ID.

   All folders of the specified user which exist in the source environment will be listed.

   For every folder, its name and description are displayed.

   By using asterisk notation in the input field above the folder names, you can restrict the list to contain only certain folders.

3. Enter the line command `CO` next to the folder to be copied.

   The folder - and, if specified, its authorization list - will be copied to the specified target file.

### On this page

- Exporting Objects
- Importing Objects
- Transferring Objects Directly