Importing Entire Event Management Objects

The import function loads Entire Event Management objects from storage to your Entire Event Management database.

An object type can be imported, only if it conforms to external data format of Entire Event Management.

Warning: Use the import function with care. It can add or update definitions to your database. Be sure that the Natural session parameter DC is set to "." (period).

To import one or more Entire Event Management objects

1. Enter IMPORT in the Command===> line of any screen.

2. Press Enter.

3. The Import Object window opens:

   Import Object

   11:18:58 *** ENTIRE EVENT MANAGEMENT *** 95-04-13 +---------------------------------------------------------------------------+ ! - Import Object - ! ! ! ! Location ==> SEQ ! ! Library ==> ________ ! ! Dsname ==> ______________________________________________________ ! ! Volser ==> ______ ! ! Node ==> ___ ! ! ! ! Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--P ! ! Help End ! ! ! +---------------------------------------------------------------------------+ 5 Authorization 6 Calendars . Exit ? Help * Commands Command ===> import___________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Menu

4. Enter values for the input fields as described below:

   Fields: Import Object

   The input fields in the Import Object window are explained in the following table:

   Field	Description
   Location	This is the location of the input file to be imported. Possible values: NAT Natural Source. SEQ Sequential file (default value). Use this when importing a large number of objects.
   Library	If Location is NAT, enter a Library which contains the exported objects. If Natural Security is installed and you are importing with Location NAT, you must also be authorized in NSC for the Library from which you are importing. If Location is SEQ, leave this field blank.
   Dsname	If Location is SEQ, you must enter a sequential file name. The file must be allocated and catalogued. If Location is NAT, leave this field blank.
   Volser	If Location is SEQ and the operating system is z/VSE, you must enter a valid VOLSER. If Location is NAT, leave this field blank.
   Node	If Location is SEQ, you must enter a valid node number. If Location is NAT, leave this field blank.

5. Press Enter.

   The Objects Exported window opens:

   Objects Exported Window

   +---------------------------------------------------------------------------+ ! ! ! 16.04.95 ENTIRE EVENT MANAGEMENT IMPORT/EXPORT UTILITY 10:40:12 ! ! Objects exported Userid KBE ! ! ------------------------------------------------------------------------ ! ! C Run Date Time Type Name ! ! ------------------------------------------------------------------------ ! ! __ 1 21/03/95 15:53:03 Rule V* * ! ! __ 1 24/03/95 13:28:13 * * ! ! __ 2 25/03/95 09:09:25 Profile * ! ! __ 1 25/03/95 09:34:58 User * ! ! __ 2 25/03/95 09:59:38 User * ! ! __ 1 25/03/95 10:21:53 Console V* ! ! __ 1 25/03/95 10:22:14 Node * ! ! ! ! ! ! ! ! Initial mode for import ==> A ! ! Stop after 5 errors ! ! Display parsing information ==> N ! ! Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--P ! ! Help End Impor Up Down ! +---------------------------------------------------------------------------+

   If Location is NAT, this window contains a list of the previous export runs. Each entry in the Type column indicates a Natural member and the type of the objects contained.

   If Location is SEQ, the list consists of only one line, which indicates the:

   • date and time of the last export run that used the sequential data set and

   • type of objects contained in the data set.

   The input fields and column headings are explained under the headings Fields: Objects Exported and Column Headings: Objects Exported.

   Note:
   If you have used a data set (Location SEQ) for export and the export run failed, an error message is displayed, if you attempt import this data set.

   PF Keys: Objects Exported

   You can perform the following functions from the Objects Exported window using these PF keys:

   Key	Name	Function
   PF1	Help	Display a help screen for this window.
   PF3	End	Return to the Entire Event Management screen.
   PF5	Impor	Start the import function.
   PF7	Up	Scroll towards the top of the list of exported objects.
   PF8	Down	Scroll towards the bottom of the list of exported objects.

   Fields: Objects Exported

   The input fields in the lower half of the Objects Exported Window are explained in the following table:

   Fields	Description
   Initial mode for import	Enter one of the following values: A Add (default). Adds new objects to Entire Event Management database. Does not overwrite objects with same name. S Scan. Does not import objects, but lists contents of sequential file or member on the screen. For more information, see SCAN Mode. U Update. Overwrites objects with same name.
   Stop after __ errors	Enter number of errors (1-99) permitted before terminating the import. Default is 5.
   Display parsing information	Enter one of the following values: N No (default). Y Yes. During import a window displays current object type, name, parsed value, format, length and line. For more information, see Parsing Information.

   Notes:

   1. Object type Rule imports only in mode A or S, because of its complex structure.
   2. Object type Message Log also imports only in modes A or S.

   All values entered are checked for their validity.

   Column Headings: Objects Exported

   The following table explains the column headings for the data listed in the Objects Exported Window:

   Column	Description
   C	To select an export run, enter an "x" or "X" in this field.
   Run	Run number of the export = number times the object type has already been exported.
   Date	Date of the export run for this object type.
   Time	Time of the export run for this object type.
   Type	Object type selected by the export function. When the whole environment was exported, this field contains an asterisk (*).
   Name	Object name or name range for objects of the export run. When the whole environment or all objects of a type were exported, the field contains an asterisk (*).

6. Select an export run for an object or range of objects, by entering an "X" in the line command field (C column) preceding the Run number.

7. Enter values for the input fields on the bottom half of the screen as described under the heading Fields: Objects Exported.

8. Press PF5 (Impor) to start the import.

   Warning: Do not press any key while import is running.

9. If you select "Y" for parsing, see the subsection Parsing Information for further information.

10. If import terminates successfully, the Information on Import screen appears with the message Import successful, the number of Objects imported and the Duration of the whole process:

    Information on Import (Import successful)

    16.04.1995 ENTIRE EVENT MANAGEMENT IMPORT/EXPORT UTILITY 17:23:40 Mode ADD Import successful Userid BRY All Objects: 1 total( 1 accepted/ 0 rejected) Objects: 1 total( 1 accepted/ 0 rejected) Duration: 00:00:02 Error/warning: 0 / 0 ------------------------------------------------------------------------------ Type Name Console Errors/Warnings Duration ------------------------------------------------------------------------------ Last accepted Object type: CONSOLE Name: KBEADA Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help End

    If any errors occurred, this screen appears as described in the subsection Error Handling during Import. For an explanation of all output fields, see Fields: Information on Import - not modifiable, for column headings, see Column Headings: Information on Import.

11. Press PF3 (End) to exit the import function and return to Entire Event Management.

Parsing Information

If you selected "Y" for "Display parsing information" (see Objects Exported Window and Fields: Objects Exported), the Parsing Information window opens at the bottom of the Objects Exported screen during import:

Objects Exported

  +---------------------------------------------------------------------------+
  !                                                                           !
  !  16.04.95    ENTIRE EVENT MANAGEMENT IMPORT EXPORT UTILITY    17:24:28    ! 
  !                        Objects exported                 Userid KBE        ! 
  !  ------------------------------------------------------------------------ ! 
  !   C  Run Date      Time     Type                 Name                     ! 
  !  ------------------------------------------------------------------------ ! 
  !   X_  1 16/04/95   14:36:33 *                    *                        ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  !                                                                           ! 
  +---------------------------------------------------------+                 ! 
  !                                                         !                 ! 
  !     Type: NODE                  Name: 29                !                 ! 
  !  Keyword: CREATION-TIME=       Value: 13.10.1994 17:35: ! --PF10--PF11--P ! 
  !            Format: DT Length:       Line: 7             !                 ! 
  +---------------------------------------------------------+ ----------------+ 

Fields: Parsing Information

The output fields in the Parsing Information window are explained in the following table:

Error Handling during Import

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 did not exist.

• The value of a field exceeds valid length.

• A non-existent object type was specified.

Syntax Warning

• Object already exists.

  These errors should not occur when importing an unchanged exported member.

  If you edit the exported member online or create a new member manually, these errors could occur.

Logical Errors

• Value has correct syntax but does not meet the requirements of Entire Event Management.

• The field has a special range (e.g. only "Y" or "N").

• Adding an object which already exists in Entire Event Management.

  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 limit is reached, the whole import is terminated.

  The Import Utility has the following 3 levels of error severity:

  • Warnings
    Warnings are displayed and cause the object to be rejected, because the object already exists (when import mode is ADD). Warnings do not cause termination of the import. Import continues with the next object within the file.

  • 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 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.

Whenever an object is rejected it is saved in the member ERR-MEBR of the SYSNCLIE library. This member contains the rejected objects and the errors which caused the rejection.

If the error limit is reached, the whole import is terminated and the following window opens:

Error limit

Page      5                                                                    
                                                                                
 OBJECT=...........................................................NODE         
 KEY=................................................................38         
 NAME-L=........................................................H60-BS2         
 MAINTENANCE-USERID=................................................HKA         
 MAINTENANCE-TIME=..................................16.04.1995.17:26:12         
 CREATION-TIME=..... +---------------------------------------+ 17:26:12         
 END-OBJECT......... !                                       ! ........         
                     !   Error limit was reached during      !                  
        Press PF3 to !   the importation process.            !                  
                     !                                       !                  
                     !     Import will be stopped.           !                  
                     !                                       !                  
                     +---------------------------------------+                  

After an import with errors, press Enter.

The Information on Import screen appears (example):

Information on Import - Import ended with warnings

  16.04.1995   ENTIRE EVENT MANAGEMENT IMPORT/EXPORT UTILITY           17:32:31
  Mode ADD               Import ended with warnings              Userid BRY
                         All Objects: 13 total( 0 accepted/ 13 rejected)
                         Objects: 13 total( 0 accepted/ 13 rejected)
                         Duration: 00:00:27
  Page: 1                Error/warning: 0 / 13
 ------------------------------------------------------------------------------
  Type                 Name            Console   Errors/Warnings       Duration
 ------------------------------------------------------------------------------
  CONSOLE              ADABAS                                          00:00:03
                                                object already exists
  CONSOLE              CICS                                            00:00:01
                                                object already exists
  CONSOLE              COMPLCMD                                        00:00:01
                                                object already exists
  CONSOLE              COMPLETE                                        00:00:01
                                                object already exists




 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        End                     Up    Down

This screen lists the warnings which occurred during the import if the import was not completely successful. The column headings are explained under the heading Column Headings: Information on Import and the output fields under the heading: Fields: Information on Import - not modifiable.

Information on Import - Import failed

  16.04.1995   ENTIRE EVENT MANAGEMENT IMPORT/EXPORT UTILITY           17:32:59
  Mode ADD               Import failed                           Userid BRY
                         All Objects: 2 total( 1 accepted/ 1 rejected)
                         Objects: 2 total( 1 accepted/ 1 rejected)
                         Duration: 00:00:05
  Page: 1                Error/warning: 1 / 0
 ------------------------------------------------------------------------------
  Type                 Name            Console   Errors/Warnings       Duration
 ------------------------------------------------------------------------------
  CONSOLE              KBE456                                          00:00:02
                                                wrong length of KW








                 Last accepted Object type: CONSOLE
                                      Name: KBE123
 Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
       Help        End                     Up    Down

This screen lists errors and warnings which occurred during import:

• if at least one error has occurred and the import was not successful, or

• if the error limit was reached and the import was terminated. In this case, the Error limit window opens first. When you press Enter, the screen above appears.

The column headings of the screen above are explained under the heading Column Headings: Information on Import and the output fields under the heading Fields: Information on Import (not modifiable).

PF Keys: Information on Import

You can perform the following functions from the Information on Import screen using these PF keys:

Fields: Information on Import - not modifiable

The output fields on the Information on Import screen are explained in the following table:

Column Headings: Information on Import

If the import was not completely successful or if the error limit was reached, the errors or warnings which occurred are listed in the columns on the Information on Import screen. These are explained below:

SCAN Mode

If you entered "S" in the Initial mode for import field, the following screen appears when you press PF5 (Impor):

Note:
The SCAN function does not import objects.

SCAN mode

 Page      1                                                                    
                                                                                
 OBJECT=...........................................................NODE         
 KEY=................................................................17         
 NAME-L=........................................................Example         
 SHORT-DESCRIPTION=..............................................test17         
 SHORT-DESCRIPTION=.......................................first.example         
 MAINTENANCE-USERID=................................................HKA         
 MAINTENANCE-TIME=..................................16.04.1995.17:24:43         
 CREATION-TIME=.....................................22.10.1994.13:49:20         
 END-OBJECT............................................................         
                                                                                
        Press PF3 to exit or any to continue                                    
                                                                                
                                                                                
                                                                                
                                                                                

The SCAN function lists the contents of the Natural member or sequential file according to object type. If you started a batch job, the list is written to SYSOUT.

Press Enter until you have listed all the objects in the file or member. When you press Enter after the last object, the Information on Import screen appears.

The SCAN function checks for syntax errors only, not for data integrity violations. All errors are added up and if the error limit is reached, the SCAN is stopped. For further information on error handling, see the subsection Error Handling during Import.

To interrupt the import during scanning and return to Entire Event Management

• Press PF3 (End).

Additional Tips for Using the Import Function

You should keep in mind the following when importing to an Entire Event Management file:

• If the object already exists in the target, it may be rejected, depending on the import mode. Required fields are necessary for an ADDition.

• For ADD or UPDATE, the related object types must be available or the object will be rejected.

• Only complete objects can be imported. All required fields must be supplied.

• Invalid representations of numbers, date and time fields, etc. must be rejected. This causes the whole object to be rejected.

• The fields MAINTENANCE-TIME and MAINTENANCE-USER are always accepted but are replaced with MAINTENANCE-USER 'IMPORT' and MAINTENANCE-TIME= (time when the import is performed).

• When you are updating periodic groups or multiple fields, all fields which build the periodic identifier of the new group are compared with all entries of the group in the database. If no entry with same identifier exists, the new group is deleted, otherwise, the already existing group is modified.

• Objects with invalid keywords must be rejected.

• The parser always registers if a keyword which does not belong to a multiple field or periodic group occurred more than once within the object - an error occurs.

• Numeric values are accepted with up to 2 decimals. Using more digits is no error.

• The keyword OBJECT must be immediately followed by an equal sign (=) and the name of the object type. See Entire Event Management Object Types in the Concepts and Facilities documentation for an explanation of object types.