Warning: You should use the import function with care. It can delete definitions from or add definitions to your database. |
To import objects
Enter 1
in the Option field of the
Import/Export Main Menu.
An Import Objects window similar to the example below opens:
01.04.16 *** +--------------------------------------------------+ | | ----------------------- | - Import Objects - | - Option ==> 1 | | | From: | | Location ==> NAT | 1 Import Ob | Library ==> ________ | 2 Export Ob | Member ==> ________ (Prefix) | 3 Export wh | Initial Mode ==> A | | | | Owner ==> __________ | | Network ==> __________ | | Job ==> __________ | | | | Stop after ==> 5____ errors | | or ==> 10___ warnings | | Keyword Gap ==> 5____ lines | | | | Display parsing information ==> N | | | | Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7--- | | Help End Imprt | +--------------------------------------------------+ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End |
The values you enter in this window determine the conditions for the import process.
The fields contained in the window are described in Fields and Options: Import Objects Window.
Press PF3 (End) to cancel the import.
Press PF5 (Imprt) to perform the import.
The data collected for the selected object is output in the specified import file or Natural object. For the information provided during the import process and possible error handling, see Import Process Information and Error Handling during Import.
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.
This document covers the following topics:
During the import, a window opens which informs you about the imported objects.
This window displays number, name and type of the imported object, the mode which was used for this object, the amount of lines the object had, the time needed to import the object, the status (accepted or failed), name of error object (if the object was rejected).
Additionally the total elapsed time, total number of lines, total number of errors/warnings occurred is shown in the window. This window shows only least information about the last ten processed objects. The screen scrolls automatically forward.
Do not press a key while the import is running. When the import is finished, a message appears which informs you whether or not the import ended successfully.
The import ended successfully if all objects were processed and the error/warning limit was not exceeded. If this was not the case, the import was cancelled due to too many errors or warnings.
The fields and options provided in the Import Objects window are described in the following table.
All values entered in this window are checked for their validity. If a Natural object is specified as import file, the file existence is also checked.
Field | Description | |
---|---|---|
Location | The location of the file to be
imported.
Enter one of the following values: |
|
NAT |
Import from a Natural text object. See also the fields Library and Member. | |
PC |
Import from a PC file. Entire Connection must be installed and the desired PC file must be assigned to Work File 7. | |
WRK |
Import from work file. Work File 1 is used. | |
Library | Only for NAT locations.
Enter the name of the library, where the Natural objects
reside. Leave this field blank, if the location is not
|
|
Member | Only for NAT locations.
Enter the prefix of the Natural object you want to import. Leave this field blank, if the location is not
|
|
Initial Mode | The mode to be used when starting
to import the object definitions contained in the file to the Entire Operations
database. The mode can change during import if the file contains mode commands.
Enter one of the following values: |
|
C
|
Check syntax of objects. | |
A
|
Add objects to the database (default). | |
U
|
Update objects on the database. | |
R |
Replace objects on the database, or add them if they do not exist. | |
D
|
Delete object from the database. | |
Owner
Network Job |
These fields can be used to define a range of objects to be imported from the import file. | |
Enter the required owner, network
and job.
If you use a wildcard ( Notes:
|
||
Stop after ... errors | Enter the number of errors which can occur before terminating the import process. Valid range is 1 through 99999. Default is 5. | |
or ... warnings | Enter number of warnings which can occur before terminating the import process. Valid range is 1 through 99999. Default is 10. | |
Keyword Gap | Enter the number of lines, within which the next keyword is expected. | |
Display parsing information | If you enter Y here,
a window appears during the import process, which informs you about the current
object type, name of object, parsed keyword, value, format, length and line. If
you enter N , the window displays, simply: Please waitThe import process is much faster with N .
|
If at least one error occurs within the object, the whole object is rejected. Errors and warnings are counted for single objects during the import. If the error or warning limit is reached, the whole import is cancelled.
Whenever an object is rejected, it is saved with prefix
ERR-
and an ascending number (ERR-0001
,
ERR-0002
, ...). These objects contain the rejected object and the
errors which caused the rejection. The error text is written directly above the
line which contains the error.
Note:
You have to specify a Natural library name for storing these
objects. Otherwise, errors are only protocolled in the job log.
In addition, a header is written to the object informing you about the:
Number of errors or warnings in this object;
User who started the import;
Date and time when the object was rejected.
(See also Date and Time Formats in the User's Guide.)
You can edit these error objects manually and reimport them again.
This section covers the following topics:
There are three levels of error severity:
Warnings
Warnings are displayed, but do not cause the rejection of the
object.
Errors
Errors cause rejection of the object but do not cause termination of
the import. Import continues with the next object within the file, if the
error/warning limit has not been reached.
Fatal errors
Fatal errors are serious problems which cannot be ignored and cause
immediate termination of the import. A fatal error occurs, for example, when it
is impossible for the parser to continue at a new point.
If errors or warnings occur during import, some of the possible causes could be, for example:
- Syntax Errors
A value has invalid format.
A character in a numeric field.
A keyword was invalid or non-existing.
The value of a field exceeds valid length.
A non-existing object type was specified.
These errors should not occur when importing an unchanged exported object. If you edit the exported object online or create a new object manually, these errors could occur.
- Logical Errors
Value has correct syntax but does not meet the requirements of Entire Operations.
A Job type is specified, which is not allowed in Entire Operations.
The field has a special range (e.g. only
Y
orN
).Adding an object to Entire Operations which already exists.
Deleting a non-existing object.
With this function you can reimport objects which were rejected during
a previous import attempt. The rejected objects reside in the SYSEOR library
and have the prefix ERR-
followed by an ascending number.
Before using this function you should edit these objects and remove the errors or warnings which occurred during the last run. Note that you have to specify the desired mode in the first line of the first error object. (This function is not yet implemented.)