Defining the Physical Environment

The Entire Event Management Physical Environment consists of the following object types:

• Entire System Server Node

• Server Parameters

This document contains a full description of all parameters that can be specified for each Entire Event Management object in the Physical Environment. An explanation of each object type is contained in the Concepts and Facilities documentation.

This document covers the following topics:

• First Steps

• Defining an Entire System Server Node

• Defining Server Parameters

First Steps

To begin

• Select the object types for Environment by placing the cursor on the Environment option under the heading Administration on the Main Menu and pressing Enter.

  The Environment Menu appears:

  14:57:32 *** ENTIRE EVENT MANAGEMENT *** 16.07.06 - Environment Menu - Physical Environment 1 Entire System Server Node 2 Server Logical Environment 3 Message Range 4 Logical Console 5 Logical Console Layout . Exit ? Help * Commands Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Menu

Defining an Entire System Server Node

An Entire System Server Node number identifies an Entire System Server Nucleus to Entire Event Management. Depending on the requirements of your installation, more than one Entire System Server Node can be installed under one operating system.

List Entire System Server Nodes

To ADD, COPY, DELETE, DISPLAY, MODIFY or RENAME an Entire System Server Node

• Place the cursor on the Entire System Server Node option under the heading Physical Environment on the Environment Menu and press Enter.

  The List Entire System Server Node screen appears:

  List Entire System Server Node

  12:52:05 *** ENTIRE EVENT MANAGEMENT *** 16.07.06 - List Entire System Server Node - Cmd Node Name Time modified Comment ___ _________ ____ ________ ________________________________ ** *********************** top of data *********************** __ 069 Prod Eber 00 h 04.06.96 E-Machine __ 148 Prod Eber 00 h 04.06.96 F-Machine __ 250 Devl Eber 00 h 08.07.96 F-Machine ** ********************** bottom of data ********************* Command => _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add Exit Flip Rfind Down Menu

  This screen lists all Entire System Server Nodes that have already been defined.

Available Local Commands: List Entire System Server Node

Add
Down
Find
Locate
Rfind
Top

Available Line Commands: List Entire System Server Node

Field Descriptions: List Entire System Server Node

• Cmd
  In the command line preceding the node you want to process, enter DI to display, MO to modify or DE to delete it. Press Enter.

• Node
  The Entire System Server Node number.

• Name
  The name of the node.

• Time
  The time difference from the location in the system which is assigned hour 0.

• modified
  The date of the last update.

• Comment
  The first line of a short comment about the node.

Add an Entire System Server Node

To ADD an Entire System Server Node

1. Press PF2 (Add).

   The Add Entire System Server Node screen appears:

   Add Entire System Server Node

   12:56:34 *** ENTIRE EVENT MANAGEMENT *** 16.07.06 - Add Entire System Server Node - Node ..... ___ created ... > Comment .. ________________________________ modified .. Name ..................... ____________________ Time Difference .......... __ hour NCL0644 Please enter Number to add Entire System Server Node. Command => _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Menu

   Available Local Commands: Add Entire System Server Node

   +Comment
   Do

2. Enter a valid Entire System Server Node number in the Node field and press Enter.

   You can now enter data for the other fields. You can ZOOM on the Comment field to enter more data (see the subsection ZOOM Feature in section Using Entire Event Management).

   Field Descriptions: Add Entire System Server Node

   • Node
     Enter an Entire System Server Node number.

   • Time Difference/hour
     If your system extends over more than one time zone, assign hour 0 to one of your locations, then + or - hours to the locations in other time zones. For example, if you have machines in New York, London and Frankfurt and assigned hour 0 to London, you would enter 0 for the node in London, +1 for the node in Frankfurt and -5 for the node in New York.

3. When you have finished entering data, press PF5 (Do) or enter DO on the command line and press Enter.

   A message confirms that the new node has been saved:

   New Entire System Server Node (number) created.

Copy an Entire System Server Node

To copy an Entire System Server Node

1. On the List Entire System Server Node screen, enter CO in the two-character command line preceding the node you want to modify and press Enter.

   The Copy Entire System Server Node window opens:

2. Enter the target node number in the field provided and press Enter.

   A message confirms that the node has been copied.

   Note:
   For your convenience, a related Server is also copied.

Delete an Entire System Server Node

To delete an Entire System Server Node

1. On the List Entire System Server Node screen, enter DE in the two-character command line preceding the node you want to delete and press Enter. Depending on the confirmation level, you may be asked to confirm by entering "Y "(yes) or "N" (no) or by typing the node number again.

2. Type the node number again in the field provided and press Enter. A message confirms that the node has been deleted.

   Note:
   A related Server is also deleted.

Display an Entire System Server Node

To display an Entire System Server Node

• On the List Entire System Server Node screen, enter DI in the two-character command line preceding the node you want to display and press Enter.

  The Display Entire System Server Node screen appears.

  In DISPLAY mode you can only view the object parameters. You cannot enter data because all fields are protected.

Modify an Entire System Server Node

To modify an Entire System Server Node

• On the List Entire System Server Node screen, enter MO in the two-character command line preceding the node you want to modify and press Enter.

  The Modify Entire System Server Node screen appears.

  Proceed as described in the subsection Add an Entire System Server Node.

Rename an Entire System Server Node

To rename an Entire System Server Node

1. On the List Entire System Server Node screen, enter RN in the two-character command line preceding the node you want to rename and press Enter.

   The Rename Entire System Server Node window opens:

2. Enter the new node number in the field provided and press Enter.

   A message confirms that the node has been renamed.

   Note:
   For your convenience, a related Server is also renamed.

Defining Server Parameters

For every Server in the Entire Event Management environment, you must define Server Parameters. The Server consists of the Entire System Server Nucleus and several service tasks. For an explanation of the Server, see the section Server in the Concepts and Facilities documentation.

To establish a runtime environment for the Server

1. Select an Entire System Server Node under which the Server is to run.

2. Link Logical Consoles to the Server. Up to 30 consoles can be served.

3. Define the physical location (DBID/FNR) of the Logging Database;

4. Install backup files where the Server keeps a local copy of the database definitions. These enable the Server to run without the Definition Database being active.

5. Define the location of the Action Program Library under the Automation Parameters option. Here you provide your own Natural programs, which can be executed by the Server when an Event occurs.

   You can also change the default settings for various other parameters.

List Server Parameters

To ADD, COPY, DELETE, DISPLAY, MODIFY or RENAME Server Parameters

• Place the cursor on the Server option under the heading Physical Environment on the Environment Menu and press Enter.

  The List Server Parameters screen appears:

  12:25:22 *** ENTIRE EVENT MANAGEMENT *** 16.07.06 - List Server Parameter - Cmd Srv Machine Wait Time ET Threshold Console U ___ ________ _________ ____________ *_______ _ ** **************** top of data ***************** __ 023 aaa 3 SEC 3 MIN/8 Adabas __ 114 F/M NC3 1 SEC 3 MIN/10 +....... __ 148 F Prod 3 SEC 3 MIN/8 ** *************** bottom of data *************** Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Add Exit Flip Rfind Down Menu

  This screen lists all Entire System Server Nodes for which Servers have already been defined.

Available Local Commands: List Server Parameters

Add
Down
Find
Locate
Rfind
Top

Available Line Commands: List Server Parameters

Field Descriptions: List Server Parameters

• Cmd
  In the command line preceding the Server you want to process, enter DI to display, MO to modify or DE to delete it. Press Enter.

• Srv
  The Entire System Server Node number for which a Server is defined.

• Machine
  The name of the Server.

• Wait Time
  The time the Collect Task "sleeps" between two processing cycles.

• ET Threshold
  The Adabas End Transaction Threshold: Maximum Time/Maximum Messages.

• Console
  The Logical Consoles served by the Server.

  If there is only one Logical Console served, the name appears in this column.

  If more than one Logical Console is served, a plus sign (+) is displayed in this field.

• U
  If marked with "X", logging to (Udf) Undefined Console is active.

  This console contains all undefined messages.

Add Server Parameters

To ADD Server Parameters

1. Press PF2 (Add) on the List Server Parameters screen.

   The Select Entire System Server Node window opens on the right with a list of all Entire System Server Nodes which do not already have a Server:

   List Server Parameters - Select Entire System Server Node

   12:25:42 *** ENTIRE EVENT MANAGEMENT *** 16.07.06 - List Server Parameter - Cmd Srv Machine Wait Time ET Threshold Console U ___ ________ _________ _______ ------------------------------------------ ** **************** top of data ! - Select Entire System Server Node - ! __ 023 aaa 3 SEC 3 MIN/8 ! ! __ 114 F/M NC3 1 SEC 3 MIN/1 ! Sel Node Machine Time modified ! __ 148 F Prod 3 SEC 3 MIN/8 ! ___ ________ ____ ________ ! ** *************** bottom of data ! ** ****** top of data ****** ! ! __ 023 aaa - 0.2 17.10.95 ! ! __ 045 x + 0.0 02.03.95 ! ! __ 114 F/M NC3 + 0.0 02.07.95 ! ! __ 145 sdaf + 0.0 31.07.95 ! ! __ 148 F Prod + 0.0 07.04.95 ! ! ** **** bottom of data ***** ! ! ! ! ! ! ! ------------------------------------------ NCL0701 Please select Entire System Server Node to work with. Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Down Menu

   The Server you are creating must run under an Entire System Server Node.

2. In the Select Entire System Server Node window, place the cursor on the number of the node you want and press Enter.

   The Add Server Parameters screen appears, with the node number you selected written in the Server field:

   Add Server Parameters

   11:21:15 *** ENTIRE EVENT MANAGEMENT *** 28.05.06 - Modify Server Parameter - Server ... 145 created ... 14.05.1996 > Comment .. ________________________________ modified .. 14.05.1996 Logical Console .... ADABAS__ CICS____ COMPLCMD COMPLETE OPERATOR PROCESS_ SECURITY XCMD____ NETWORK_ HKA-TEST TMON____ NCLAPI__ UKSJUC-1 UKSJUC-2 ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ Log DBID/FNR ....... __9 _79 (NCLSYSF3) + Suppressed Messages ET Threshold ....... _1 Msg or __1 MIN Delimiters ......... ,=;()_____ + Automation Parameters Collect Wait Time .. __1 SEC + Installation Backup File Msgid Exit ......... YMSGID__ Init. Exit ......... ________ + Miscellaneous Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Menu

   Available Local Commands: Add Server Parameters

   +Auto
   +Comment
   Do
   +InsFile
   +Misc
   +SuprMsg

   You can now enter data for all fields. ZOOM on Suppressed Messages, Automation Parameters, Installation Backup Files and Miscellaneous to open windows with data input fields for these options. You can also ZOOM on the Comment field to enter more data. For more information, (see the subsection ZOOM Feature).

   Field Descriptions: Add Server Parameters

   • Server
     The Entire System Server Node number for which you are defining the Server.

   • Logical Console
     Enter the names of up to 30 Logical Consoles to be served by the Server. Only the Logical Console definitions specified in the Server Parameters are considered by the system. Logical Consoles not linked to any Server are ignored by the system.

   • Log DBID/FNR
     Enter the physical location of the Logging Database.

   • ET Threshold
     In the Msg field, enter the maximum number of messages to be logged before the Server writes an ET (End Transaction in Adabas) to the database. In the next two fields, enter the maximum elapsed time before an ET. Enter the number of seconds or minutes in the first three-character field. In the second three-character field enter MIN for minutes or SEC for seconds.

   • Delimiters
     The Server uses these delimiters to separate the message text into tokens. They affect the way you can set up filtering criteria for the messages. Comma (,), equal sign (=) and semicolon (;) are assigned as defaults. Blanks are always used as delimiters. Enter further delimiters here.

   • Collect Wait Time
     Enter the time the Collect Task "sleeps" between two processing cycles. This value affects Server performance. The default value is 1 SEC. Enter a 1-, 2,- or 3-digit number in the first input field and SEC for seconds or MIN for minutes in the second field. If you run the Server under MVS/370, 3 seconds or longer is recommended as a more reasonable value.

   • Msgid Exit
     Enter the name of the CALLNAT program to be used in the Collect Task for constructing the message ID from the message text. YMSGID in the SYSNCLSVlibrary provides an example which uses the first token of the message text as ID.

   • Init Exit
     Enter the name of the CALLNAT program to get control during startup of the Collect Task. The YINIT subprogram in the SYSNCLSV library provides an example which forwards an initialization message to the Analysis Task via the Event API .

   • Suppressed Messages, Automation Parameters, Installation Backup Files, Miscellaneous
     To define these parameters, see the immediately following subsections.

3. When you have finished entering data on this screen for Server Parameters, press PF5 (Do) or enter DO on the command line and press Enter.

   A message confirms that the Server Parameters have been saved:

   New Server Parameters (number) created.

Suppressed Messages

To define Suppressed Messages for the Server

1. Place the cursor on Suppressed Messages and press Enter.

   The Suppressed Messages window opens:

   Add Server Parameters - Suppressed Messages

   11:50:22 *** ENTIRE EVENT MANAGEMENT *** 28.05.06 - Add Server Parameter - Server ... 145 created ... 14.05.1996 > Comment ------------------------------------------------------------------- ! - Supressed Messages - ! Logical ! ! ! Message__ Comment___________________________________________ ! ! ********* *************_ top of data ********************** ! ! ESYOPREX_ Messages generated by ESY Operator Exit___________ ! ! ********* ***********_ bottom of data ********************* ! ! _________ __________________________________________________ ! Log DBID ! _________ __________________________________________________ ! ET Thres ! _________ __________________________________________________ ! Delimite ! _________ __________________________________________________ ! ! _________ __________________________________________________ ! Collect ! _________ __________________________________________________ ! Msgid Ex ! _________ __________________________________________________ ! Init. Ex ! _________ __________________________________________________ ! ------------------------------------------------------------------- Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Up Down Menu

   Available Local Commands: Suppressed Messages

   Bottom
   Do
   Down
   Top
   Up

   Field Descriptions: Suppressed Messages

   • Message
     Enter the ID(s) of the message(s) to be suppressed. Up to 86 message IDs can be defined here. The message ID must be fully specified, wildcards are not allowed. This is the earliest point in the whole system to suppress messages which are of no interest. Entering message IDs here causes them to be suppressed by the Collect Task and reduces stress on the system to a minimum (see the section Server in the Concepts and Facilities documentation).

     By defining a small number of frequently-appearing messages to be filtered out here, you can achieve a high suppression rate.

   • Comment
     Enter a short description of the message.

2. When you have finished entering data, press PF3 (Exit) to return to the Add Server Parameters screen.

Automation Parameters

To define Automation Parameters

• Place the cursor on +Automation Parameters and press Enter.

  The Automation Parameters window opens:

  Add Server Parameters - Automation Parameters

  11:53:51 *** ENTIRE EVENT MANAGEMENT *** 28.05.06 - Add Server Parameter - Server ... 145 created ... 14.05.1996 > Comment ------------------------------------------------------------------- ! - Automation Parameters - ! Logical ! ! ! Rule Timeout .......... _60 SEC Loop Criterion 2 ! ! Rule Locktime ......... _20 SEC Loop Frequency _10 ! ! Resumetime ... __5 MIN ! ! Action Program Library ! ! Database Nr ......... ___ ! Log DBID ! File Nr ............. ___ ! ET Thres ! Library ............. ________ ! Delimite ! ! ! Initial Size of Active Queues ! Collect ! Root Events ......... _________ ! Msgid Ex ! Dependent Events .... _________ ! Init. Ex ! ! ------------------------------------------------------------------- Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Menu

Available Local Commands: Automation Parameters

Do

Field Descriptions: Automation Parameters

• Rule Timeout
  Enter the number of seconds or minutes in the first three-character field. In the second three-character field enter MIN for minutes or SEC for seconds. The value you enter here sets a default time limit for Events and Event Trees in the following way:

  This value sets the maximum time the automation process will wait for outstanding Events of the currently active Event Tree. This means that all dependent Events can only occur within this time limit. Whenever a message fulfills the conditions defined along with the Root Event of an Automation Rule, this Automation Rule becomes an active Event or, if there are dependent Events, an active Event Tree. After the Rule Timeout has expired, the active Event or Event Tree is discarded.

  If a new Server is added, a default value of 30 seconds is assigned, but it is best to estimate how often and for how long most of your defined rules can be active. If the maximum estimate for this value is different from 30 seconds, then you should enter the estimated value here.

  The Server uses this timeout definition only if you have not entered a value for the Timeout field of the Automation Rule; i.e. the value you enter for the Timeout field of the Automation Rule overrides your entry here (see the Timeout field description under the heading Add an Automation Rule in section Defining an Automation Rule).

• Rule Locktime
  Given an active Root Event, this specifies how long a new message with the same text and job ID as the active Root Event cannot trigger a new Root Event. Default = Rule Timeout. 999 MIN is interpreted as no Rule Locktime.

• Loop Criterion
  This determines how message loops will be detected. Enter "1" or "2":

  • "1" = Loop is assumed when the same message text occurs n times within Rule Timeout even when issued by different jobs.

    "2" = Loop is assumed only when the same message text is issued n times within Rule Timeout by the same job. Default = 2.

• Loop Frequency
  Defines the threshold for the occurence of identical messages. If a message issued by the same job occurs n times during the Rule Timeout defined above, the Event definition is removed from the automation process and ignored. In this way CPU time is occupied with useful work and not blocked by Event loops. This situation is reported by a Server (Log) record written to the targets you define in Miscellaneous Server Parameters. See the subsection Miscellaneous Server Parameters.

• Resumetime
  When a looping Event is detected, the associated Automation Rule is disabled. Resume time specifies after how much time the Automation Rule is enabled again. Default: 10 minutes.

Action Program Library

These are defaults for Actions which execute Natural programs (NAT Actions). For further details, see the subsection Defining an Action for an Event in section Defining an Automation Rule.

• Database Nr
  Enter the ID of the database in which NAT Actions are stored.

• File Nr
  Enter the file number within the database in which NAT Actions are stored.

• Library
  Enter the library of the database where NAT Actions are stored.

Initial Size of Active Queues

• Root Events
  This is the initial size of the Active Root Event Queue (ARE Queue), that is, the number of ARE Queue Elements (storage capacity) which is allocated during Server startup. The ARE Queue is used to hold all active Root Events in the Server.

  Enter no value here to begin with. The number of queue elements is set to the number of defined Root Events. If more elements are needed during the automation process, the Server allocates a second extent equal to half the size of the first extent. If this extent is not available, the storage request is repeated with half the size of the last storage request. This is repeated until the request is satisfied.

  If the request is not satisfied or available storage is too small to hold at least one active Root Event, the Server is terminated and an activity log record is written to the targets you define in Miscellaneous Server Parameters (see the subsection Miscellaneous Server Parameters).

  Up to 2 times the original extent (2x value you enter above) can be automatically allocated by Entire Event Management to the ARE Queue. Should this situation occur, you should enter a value here to increase the storage capacity to be allocated during Server startup.

• Dependent Events
  This is the initial size of the Active Non-Root Event Queue (ANE Queue), that is, the number of ANE Queue Elements (storage capacity) which is allocated during Server startup. The ANE Queue is used to hold all active Non-Root Events in the Server.

• Enter no value here to begin with. The ANE Queue is handled in the same way as the ARE Queue above. If storage proves to be too small, you should enter a value here to increase the storage capacity to be allocated during Server startup.

Installation Backup Files

The definitions needed by the Server for the automation and logging process are loaded in two steps:

1. They are first loaded to a local file (local relative to the Server) from the Definition Database. This step overwrites the oldest backup copy.

2. The local file is then used in a second step to load the definitions in main memory. This step uses the newest backup copy. Since the backup copy of the last downloading is used, the Server can be started at a local node without being connected to a control (i.e. central) definition database.

For the above operation, two files are used with fixed suffixes: SVnnn.BACKUP1 and SVnnn.BACKUP2 where nnn is the node number.

If the Entire System Server is currently running, under which the Server is going to be installed, you can allocate these files by placing the cursor on +Installation Backup Files and pressing Enter. The Install Backup Files window opens for the operating system used by Entire System Server:

z/OS

Add Server Parameters - Install Backup Files (z/OS)

 10:54:13               *** ENTIRE EVENT MANAGEMENT ***                12.06.06
                          - Modify Server Parameter -

   Server ... 114 F-Mc                         created ... 01.03.1994
 > Comment  -------------------------------------------------------------------
            !                    - Install Backup Files -                     !
   Logical  !                                                                 !
            !   Prefix ...... NCL___________________________                  !
            !                                                                 !
            !   Definition File 1                                             !
            !     Name ...... NCL.SV114.BACKUP1                               !
            !     Status ....                                                 !
   Log DBID !     Volume .... ______   Space .... ___ ___ ___                 !
   ET Thres !                                                                 !
   Delimite !   Definition File 2                                             !
            !     Name ...... NCL.SV114.BACKUP2                               !
   Collect  !     Status ....                                                 !
   Msgid Ex !     Volume .... ______   Space ....                             !
   Init. Ex !                                                                 !
            -------------------------------------------------------------------
NCL2262 Please Confirm execution.
 Command ===> _________________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
      Help        Exit  Flip  Conf                                      Menu

Available Local Commands: Install Backup Files

Confirm

Field Descriptions: Install Backup Files - z/OS

• Prefix
  Enter the prefix for the backup file names.

Definition File 1/2

• Name (output field)
  Full name of the backup file appears here. The full name consists of the Prefix entered above followed by the suffix SVnnn.BACKUP1 or SVnnn.BACKUP2.

• Status (output field)
  The successful file allocation process is confirmed here by an Entire System Server status message.

• Volume
  Enter the volume on which the backup file is located.

• Space
  Space Enter the amount of primary and secondary space to be allocated for the backup file. Enter primary space in the first field, secondary space in the second field and type of space in the last field: CYL for cylinders, TRK for tracks or BLK for blocks.

z/VSE

Add Server Parameters - Install Backup Files (z/VSE)

11:49:40                 *** ENTIRE EVENT MANAGEMENT ***              06-09-27
                           - Modify Server Parameter -

    Server ... 172 vsee2                        created ... 27.09.1996
  > Comment  -------------------------------------------------------------------
             !                    - Install Backup Files -                     !
    Logical  !                                                                 !
             !   Prefix ...... NCL___________________________                  !
             !   Definition File 1                                             !
             !     Name ...... NCL.SV172.BACKUP1                               !
             !     Volume..... SYSWK3  Ext. Start __________ Space __________  !
             !     Status .... ESY5996 Volume not online.                      !
    Log DBID !     Cylinders .         Tracks                                  !
    ET Thres !   Definition File 2                                             !
    Delimite !     Name ...... NCL.SV172.BACKUP2                               !
             !     Volume.....         Ext. Start __________                   !
    Collect  !     Status .... ESY5996 Volume not online.                      !
    Msgid Ex !     Cylinders..         Tracks                                  !
    Init. Ex !                                                                 !
             -------------------------------------------------------------------
 NCL0516 Please enter Space.
  Command ===> _________________________________________________________________
   Confirm
   Bar      Cancel   Exit     Flip     Help     Keys     Menu     Quit     Tech

Field Descriptions: Install Backup Files - z/VSE

Definition File 1/2

• Name
  Name of the respective Backup File.

• Volume
  Enter volume on which the Backup Files are located.

• Ext. Start
  Enter the start FBA block number or CKD track number for the sequential files <prefix>.SV<nnn>.BACKUP1.HD and <prefix>.SV<nnn>.BACKUP2.HD respectively. If you leave this field blank, z/VSE selects the block or track number for the backup files; alternatively, you must specify a block or track number for Backup File 2 according to the required space.

• Space
  Enter the number of tracks needed for the sequential file. The following sequential files are then allocated with the space indicated:

  Sequential Files	Number of Tracks
  <prefix>.SV<nnn>.BACKUP1.HD	1 track
  <prefix>.SV<nnn>.BACKUP1	as required
  <prefix>.SV<nnn>.BACKUP2.HD	1 track
  <prefix>.SV<nnn>.BACKUP2	as required

  The space entered for Backup File 1 is also taken by Backup File 2.

• Status
  An output field which shows the status of the respective Backup File.

BS2000/OSD

Add Server Parameters - Install Backup Files (BS2000/OSD)

12:05:57                  *** ENTIRE EVENT MANAGEMENT ***              06-09-27
                             - Add Server Parameter -

    Server ... 031 H60                          created ... 27.09.1996
  > Comment  -------------------------------------------------------------------
             !                    - Install Backup Files -                     !
    Logical  !                                                                 !
             !   Prefix ...... $NCL.NCL______________________                  !
             !                                                                 !
             !   Definition File 1                                             !
             !     Name ...... .SV031.BACKUP1                                  !
             !     Status .... ESY5565 Syntax error in data set name.          !
    Log DBID !     Space ..... ___ ___ ___                                     !
    ET Thres !                                                                 !
    Delimite !   Definition File 2                                             !
             !     Name ...... .SV031.BACKUP2                                  !
    Collect  !     Status .... ESY5565 Syntax error in data set name.          !
    Msgid Ex !     Space .....                                                 !
    Init. Ex !                                                                 !
             -------------------------------------------------------------------
 NCL0516 Please enter Space.
  Command ===> _________________________________________________________________
   Confirm
   Bar      Cancel   Exit     Flip     Help     Keys     Menu     Quit     Tech
 

Field Descriptions: Install Backup Files - BS2000/OSD

Definition File 1/2

• Name
  Name of the respective Backup File.

• Status
  An output field which shows the status of the respective Backup File.

• Space
  Enter the amount of primary and secondary space to be allocated for the backup files. Enter primary space in the first field, secondary space in the second field and type of space in the last field - PAM (PAM pages for BS2000/OSD). The values you provide apply to both backup files.

Miscellaneous Server Parameters

In this window you can define a time window for the (Udf) console and the targets to which (Log) Messages are written.

To define Miscellaneous Server Parameters

• Place the cursor on +Miscellaneous and press Enter.

  The Miscellaneous Server Parameters window opens:

  Add Server Parameters - Miscellaneous Server Parameters

  11:20:59 *** ENTIRE EVENT MANAGEMENT *** 12.06.06 - Modify Server Parameter - Server ... 114 F-Mc created ... 01.03.1994 > Comment ------------------------------------------------------------------- ! - Miscellaneous Server Parameters - ! Logical ! ! ! Write to (Udf) Console from . 00:00 to 00:00 ! ! ! ! API Receiver Service ........ ncl-api_________ ! ! Wait before retry ....... __5 MIN ! ! ! Log DBID ! Perform SYS3-Cleanup at ..... 06:00 Trace the Cleanup _ ! ET Thres ! ! Delimite ! Prefix of (Log) Messages .... NCL ! ! Write (Log) Messages ! Collect ! to Logical Consoles .............. X ! Msgid Ex ! to Physical Console .............. _ ! Init. Ex ! to Server Task Sysout ............ X ! ------------------------------------------------------------------- Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Do Menu

Available Local Commands: Miscellaneous Server Parameters

Do

Field Descriptions: Miscellaneous Server Parameters

• Write to (Udf) Console from
  If you enter a time interval here, then during this interval the Server logs all messages to the (Udf) Console which are not suppressed and do not fulfill range conditions of any Logical Console.

• API Receiver Service
  Enter the name of the receiver service which takes care of event messages which you would like to forward to the Entire Event Management Server. This service will then be started as a subtask during Server startup.

  Note:
  The name you enter here must be registered in the SATSR directory member of the SYSSATUlibrary.

• Wait before retry
  Enter the time the API Receiver Service should wait in case of errors before resuming work.

• Perform SYS3-Cleanup at
  Enter the time of day when the SYS3 cleanup task should be started automatically.

• Trace the Cleanup
  Mark with "X", if you want the SYS3 cleanup process to be traced.

• Prefix of (Log) Messages
  Enter a prefix to identify (Log) messages from the Server.

Write (Log) Messages

These messages contain Server status information. You can retrieve this information in the (Log) Console.

Enter data for one or more of the fields below:

• to Logical Consoles
  Mark with an "X" if you want the (Log) messages to be logged to the (Log) Console. Some important (Log) messages can be logged to all Logical Consoles.

• to Physical Console
  Mark with an "X", if you want the (Log) messages to be sent to the Physical Console by issuing WTOs.

• to Server Task Sysout
  Mark with an "X" if you want the (Log) messages to be written to SYSOUT protocol files associated with the Server tasks.

Copy Server Parameters

To copy server parameters

1. On the List Server Parameters screen, enter CO in the two-character command line preceding the Server you want to copy and press Enter.

   The Copy Server Parameters window opens:

2. Enter the target Server number in the field provided and press Enter.

   A message confirms that the Server has been copied.

   Note:
   If the related target Entire System Server Node does not yet exist, it is created automatically from the related source Entire System Server Node for your convenience.

Delete Server Parameters

To delete server parameters

1. On the List Server Parameters screen, enter DE in the two-character command line preceding the Server you want to delete and press Enter. Depending on the confirmation level, you may be asked to confirm by entering "Y" (yes) or "N" (no) or by typing the node number again.

2. Make the appropriate entry in the field provided and press Enter.

   A message confirms that the Server has been deleted.

Display Server Parameters

To display server parameters

• On the List Server Parameters screen, enter DI in the two-character command line preceding the Server you want to display and press Enter.

  The Display Server Parameters screen appears.

  In DISPLAY mode you can only view the object parameters. You cannot enter data because all fields are protected.

Modify Server Parameters

To modify server parameters

• On the List Server Parameters screen, enter MO in the two-character command line preceding the Server you want to modify and press Enter.

  The Modify Server Parameters screen appears.

  Proceed as described in the subsection Add Server Parameters.

Rename Server Parameters

To rename server parameters

1. On the List Server Parameters screen, enter RN in the two-character command line preceding the Server you want to rename and press Enter.

   The Rename Server Parameters window opens:

2. Enter the new Server number in the field provided and press Enter. A message confirms that the Server has been renamed.

   Note:
   If an Entire System Server Node with a number identical to the new Server number already exists, the rename request is refused. Otherwise, the related Entire System Server Node is renamed automatically to the new number.