Exporting an object can invoke the transformation of records from the Entire Operations database into an external format.
Exporting objects via Entire Operations is only possible if your monitor is running. The execution of all imports and exports is performed asynchronously.
This document covers the following topics:
To export single objects
Enter 2
in the Option field of the
Import/Export Main Menu and press ENTER.
A Select Export Target Version window prompts you to enter the export target version:
19.03.16 *** Entire Operations Import/Export *** 19:05:46 Main Menu Userid SAG -------------------- +--------------------------------------------------+ ---- Option ==> 2 | | | Select Export Target Version | | | 1 Import | Current Version ==> 5.4.3.3 | 2 Export | | 3 Export | Target Version ==> 5.4.3.3_____________ | | | | A + behind the current version means | | that the current version was updated | | by further corrections. | | | | | | | | | | Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7--- | | Help End Apply | +--------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End |
The target version has the format VRSCF, where:
VRS | Existing Entire Operations version. |
CF | Cumulative fix. |
Valid values are from 51114 till current (or next) VRSCF. The highest allowed value is preset as default.
You may enter an asterisk (*) in the Target Version field to select value from the list.
About the current version:
If there is a correction in export/import that brings at least one
new keyword and the current Entire Operations version is 53106, for example,
then export will show the current version as 53106+
. This is to
show that there may be problems when importing to pure version 53106. If you
specify the target version as 53107, export will run with all new keywords. If
you specify the target version as 53106, then new keywords will not appear in
export file but some data loss may occur if new definitions/settings are in use
because export will convert them to older version.
When a service pack (cumulative fix) is completed, the plus sign
(+
) will be eliminated, and the import/export version will be
brought to the same level as the rest of Entire Operations.
After this, press PF5 to continue.
The Export Objects screen appears:
19.03.16 *** Entire Operations Import/Export *** 18:49:00 Export Objects Userid SAG ------------------------------------------------------------------------------ Please select object type to be exported: 1 NETWORK-MASTER 11 MAILBOX-DEFINITION 2 NETWORK-VERSION-USAGE 12 MAILBOX-ENTRY 3 JOB-MASTER 13 NODE-DEFINITION 4 GLOBAL-EXIT 14 RESOURCE-DEFINITION 5 EOJ-CHECK-MASTER 15 USER-DEFINITION 6 DESCRIPTION 16 DEFAULTS 7 SCHEDULE 17 OWNER 8 CALENDAR 18 CONDITION-ACTIVE 9 TO-ACTIVATE 19 RESOURCE-PREREQ 10 SYMBOL-MASTER 20 SYMBOL-VERSION-USAGE Your Selection ===> __ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- |
Select the desired object type by entering the appropriate number in the field after Your Selection ===>.
Press ENTER.
An Export Objects window similar to the example below opens:
27.02.17 *** +----------------------------------------------------+ | | ----------------------- | - Export Object - | | Origin Version ==> 5.4.3.7 | Pleas | Object Type ==> NETWORK-MASTER | | Owner ==> __________ | 1 NETWORK-MASTER | Network ==> __________ | 2 NETWORK-VERSION- | Version ==> __________ | 3 JOB-MASTER | | 4 GLOBAL-EXIT | | 5 EOJ-CHECK-MASTER | | 6 DESCRIPTION | Target Version ==> 5.4.3.7 | 7 SCHEDULE | Location ==> NAT | 8 CALENDAR | Library ==> ________ | 9 TO-ACTIVATE | Member ==> _____ (Prefix) | 10 SYMBOL-MASTER | Export Mode ==> N (A,N,R) | | Passwords ==> N (Y,N) | | with Schedules ==> Y (Y,N) | | with Calendars ==> N (Y,N) | | with Symbols ==> N (Y,N) | | with Grants ==> N (Y,N) | | Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF | | Help End Exprt | +----------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End |
The data collected for the selected object is output in the specified export file or Natural object. For the information provided during the export process, see Export Process Information.
The syntax that applies to the entries in the output file (or object) is explained in Syntax in Import/Export Files and Object Processing Rules.
Note:
If your Entire Operations system contains a large amount
of data, you should invoke the Export whole environment
function in batch mode. For more information, see Using the
Import/Export Utility in Batch Mode.
To export the whole environment
Enter 3
in the Option field of the
Import/Export Main Menu and press ENTER
.
A Select Export Target Version window described earlier prompts you for a target version.
Enter the required target version and press PF5 to continue.
An Export whole environment window similar to the example below opens:
27.02.17 *** Entire Operations Import/Export *** 17:14:05 Main Menu Userid SAG -------------------- +--------------------------------------------------+ ---- Option ==> 3 | | | Select Export Target Version | | | 1 Import | Current Version ==> 5.4.3.7 | 2 Export | | 3 Export | +------------------------------------------+ | | | | | | | - Export whole environment - | | | | | | | | Origin Version ==> 5.4.3.7 | | | | | | | | Target Version ==> 5.4.3.7 | | | | Location ==> NAT | | | | Library ==> ________ | | | | Member ==> _____ (Prefix) | -- | | | Export Mode ==> N (A,N,R) | | +- | Passwords ==> N (Y,N) | ---+ | with Schedules ==> Y (Y,N) | | with Calendars ==> N (Y,N) | | with Symbols ==> N (Y,N) | | with Grants ==> _ (Y,N) | | Enter-PF1---PF2---PF3---PF4---PF5---PF6- | | Help End Exprt | +------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End |
Enter the required definitions.
The input fields are described in Fields and Options: Export Objects Window. The To fields are the same. The From fields are omitted.
When you are finished press ENTER or PF5 (Exprt).
The data collected for the selected environment is output in the specified export file or Natural object. For the information provided during the export process, see Export Process Information.
The syntax that applies to the entries in the output file (or object) is explained in the remainder of this chapter.
During the export, a window opens which informs you about the currently exported object.
This window displays name and type of the exported object, the number of lines the object has and the total number of lines written during the export run.
Do not press a key while the export is running. When it is finished, a message appears on the screen which informs you about the way the export ended. This information is also written to the export object, so that you can check whether or not all specified objects were written. For some reasons, the export process could terminate abnormally. This could happen, for example, if you attempt to write more than 999 objects.
The fields and options provided in the Export Objects or Export whole environment window are described in the following table.
Field/Option | Description | ||
---|---|---|---|
From: | |||
Origin Version | The current Entire Operations version from which the objects are exported. | ||
Object type | An output field that displays the object type previously specified. | ||
... | The remaining From fields differ according to the object type selected. For further information, see Object Type to be Exported: Key Fields of the Objects in the section Export Commands for Batch Processing. | ||
To: | |||
Location | The location of the export file
to be created.
Enter one of the following values: |
||
NAT |
Export to a Natural text object. | ||
PC |
Export to a PC file. Entire Connection must be installed and the desired PC file must be assigned to Work File 7. | ||
WRK |
Export to Natural work file. Work File 1 has to be defined. | ||
Notes:
|
|||
Library | Only for NAT locations.
Enter the name of the library that contains the Natural text
object used for export. Leave this field blank if the
location is not |
||
Member | Only for NAT locations.
Enter the prefix (maximum is 5 alphanumeric characters) of the Natural text object that contains the export data. Single or multiple text objects with the specified prefix can exist depending on the amount of data to be exported. For example: The prefix Leave this field blank if the location is not
|
||
Export Mode | Only for NAT locations.
Determine how to handle the export data contained in the Natural text object(s) specified with the prefix in the Member field. Possible values are: |
||
A
|
Enter this value to append the data to be exported to the specified text object. Text object with the specified prefix must exist. |
||
N
|
Enter this value to save the data in a new text object. If a text object with the specified prefix already exists, an appropriate message is returned. This is the default setting. |
||
R |
Enter this value to replace the data in the specified text object. | ||
Passwords | Only for object types which
contain passwords (e.g. password of a protected data set).
Enter one of the following values: |
||
Y
|
Export passwords. | ||
N
|
Do not export passwords. | ||
with Schedules | If you also export the schedules,
the imported networks will get the same schedule definitions as the exported
networks. (They can be modified after the import.)
Enter one of the following values: |
||
Y |
Export schedules (default). | ||
N
|
Do not export schedules. | ||
with Calendars | If you export object(s) with
calendars, all referenced calendars will be exported after objects, each
calendar once.
Enter one of the following values: |
||
Y
|
Export calendars. | ||
N
|
Do not export calendars (default). | ||
with Symbols | If you export object(s) with
symbols, all referenced symbol tables will be exported after objects, each
symbol table once.
Enter one of the following values: |
||
Y
|
Export symbols. | ||
N
|
Do not export symbols (default). | ||
with Grants | If you export networks, you can
determine whether access rights granted to users/owners in the source
environment are also exported.
Enter one of the following values: |
||
Y |
Export granted access rights. | ||
N |
Do not export granted access rights (default). |
Depending on the object type you have selected, you have to fill in related key fields as required (see also Object Type to be Exported: Key Fields of the Objects). If you are going to import from a source location which was previously written by an export process of Entire Operations, these fields have been filled in correctly.
For the fields Owner, Network and Job, you can enter an asterisk
(*
) in one of these fields and press ENTER to open a
window from which you can select an object from a supplied list.
For all other fields, you can use an asterisk (*
) as a
wildcard to delimit the range of objects to be exported. For example, if you
enter WILD*
in the Job field of the object type
JOB-MASTER
and press ENTER, the jobs WILD, WILDxxxx,
WILD-1, and so on are exported. If you enter *
in all selection
fields, all objects of this object type are exported.
For some object types some descriptors are optional. If you do not wish
to use an optional field, enter a hyphen (-
) to ignore it. For
example: a job or a network can have a DESCRIPTION
.
To export the DESCRIPTION of a network only
Enter Owner and Network name and enter a hyphen (-
) for
Job name. All values entered are checked for their validity.
Press PF3 to cancel the export.
Press PF5 to perform the export.
Note:
All objects that are related to the selected objects (see the
section Hierarchical Order for
Object Processing) are also exported.