For each Entire Event Management Server in your system configuration, you must perform the following steps:
Add the Node with the direct command ADD NODE<vrs>. The following screen appears:
12:56:34 *** ENTIRE EVENT MANAGEMENT *** 30.05.06
- Add Entire System Server Node -
Node ..... ___ created ...
> Comment .. ________________________________ modified ..
Name ..................... ____________________
Time Difference .......... __ hour(s)
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
|
In the Machine field, enter the machine name used in the Machine column of the Logical Console (see also the section Add a Logical Console Layout in the section Defining the Logical Environment of the Entire Event Management User's Guide).
To save the Node definition
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.
Define a Server on this Node with the direct command ADD SERVER<vrs>. The following screen appears:
09:39:04 *** ENTIRE EVENT MANAGEMENT *** 30.05.06
- Add Server Parameter -
Server ... 148 P-ESY created ...
> Comment .. ________________________________ modified ..
Logical Console .... ________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
________ ________ ________ ________ ________ ________
Log DBID/FNR ....... ___ ___ (NCLSYSF3) > Suppressed Messages
ET Threshold ....... 10 Msg or __3 MIN
Delimiters ......... ,=;_______ + Automation Parameters
Collect Wait Time .. __1 SEC + Installation Backup File
Msgid Exit ......... ________
Init. Exit ......... ________ + Miscellaneous
Command ===> _________________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Do Menu |
You must enter parameters for the following fields:
Logical Console
Enter the Logical Consoles to be served by the Server.
Log DBID/FNR
Enter Log DBID/FNR (System File 3) to which Server routes messages to
be logged. Make certain that this pointer coincides with the pointer to System
File 3, which is provided with the appropriate LFILE assignment in the NATENV
parameter block (see the section Mandatory Parameter Blocks and
Parameters for Entire Event Management).
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 SYSNCLSV
library provides an example which uses the first token of the message text as
ID.
BS2000/OSD: For BS2000/OSD, the Exit YID-BS2 is provided and should be specified here.
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.
Save the Server definition with the command DO.
For every Server defined in Entire Event Management, two Backup Files must be installed to temporarily hold the Server definitions. You can allocate these files online, if the Entire System Server indicated by the Server node number is currently running.
Place the cursor on +Installation Backup Files on the Add Server Parameters screen and press Enter.
A window opens according to the operating system on which the Entire System Server runs. In this window you can allocate files online :
09:54:24 *** ENTIRE EVENT MANAGEMENT *** 30.05.06
- Add Server Parameter -
Server ... 148 P-ESY created ... 30.05.2006
> Comment -------------------------------------------------------------------
! - Install Backup Files - !
Logical ! !
! Prefix ...... ______________________________ !
! !
! Definition File 1 !
! Name ...... .SV148.BACKUP1 !
! Status .... !
Log DBID ! Volume .... ______ Space .... ___ ___ ___ !
ET Thres ! !
Delimite ! Definition File 2 !
! Name ...... .SV148.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
|
09:54:24 *** ENTIRE EVENT MANAGEMENT *** 30.05.06
- Add Server Parameter -
Server ... 148 si14 created ... 30.05.2006
> Comment -------------------------------------------------------------------
! - Install Backup Files - !
Logical ! !
! Prefix ...... $SAG.NCL____________________ !
! !
! Definition File 1 !
! Name ...... $SAG.NCL.SV148.BACKUP1 !
! Status .... ESY5722 Requested data set not found. !
Log DBID ! Space ..... _5_ _5_ ___ !
ET Thres ! !
Delimite ! Definition File 2 !
! Name ...... $SAG.NCL.SV148.BACKUP2 !
Collect ! Status .... ESY5722 Requested data set not found. !
Msgid Ex ! 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
|
Enter the prefix for the name of the Backup Files. This must be identical to the value of the NCLENV parameter <NCLSEQF> (see the section Define Environment for Entire Event Management Server).
For example, $SAG.NCL is the prefix in NCLENV for the above shown BS2000/OSD environment.
The following fields are operating-system-dependent:
Enter the value for the primary space in the first field.
Enter the value for the secondary space in the second field.
Enter the unit for the given values in the third field.
Enter the value for the primary space in the first field.
Enter the value for the secondary space in the second field.
Leave the third field blank.
Enter the volume on which the sequential files are to be allocated.
Enter the start FBA block number or CKD track number for the sequential files <prefix>.SV<vrs>.BACKUP1.HD and <prefix>.SVvrs.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.
Enter the number of tracks needed for the sequential file. The following sequential files are then allocated with the space indicated:
| Sequential File | Number of Tracks |
|---|---|
| <prefix>.SV<vrs>.BACKUP1.HD | 1 track |
| <prefix>.SV<vrs>.BACKUP1 | as required |
| <prefix>.SV<vrs>.BACKUP2.HD | 1 track |
| <prefix>.SV<vrs>.BACKUP2 | as required |
Confirm the allocation by entering CONFIRM in the Command ===> line and pressing Enter.
Note:
The Entire System Server node <vrs>
must be active to perform this file installation.
If you use another method of allocating the files, use the following attributes:
| File Allocation | Attribute |
|---|---|
| File name | <prefix>.SV<vrs>.BACKUP1 and BACKUP2 (vrs=node number of server) |
| DSORG | PS |
| LRECL | 253 |
| BLKSIZE | 253 (must be the same as LRECL for the moment) |
| RECFM | FB. |
The following table should be used to estimate the space required. (If you do not want to estimate the space, start with a value of 1CYL). It gives the number of records needed for each type of object definition contained in the data base:
| Entity Definition | No. of Records |
|---|---|
| Server Parameter | 8 |
| Message Range | 4 |
| Logical Console | 1 |
| Event | 4 |
| Action | 1 |
In addition on z/VSE, the sequential header files <prefix>.SV<vrs>.BACKUP1.HD and <prefix>.SV<vrs>.BACKUP2.HD must be allocated with the same attributes and with one track for each file.
If you want to use NET-type Actions that must interface with Entire Operations, define the Entire Operations System Library (SYSEOR) as a STEPLIB for SYSNCL and SYSNCLSV.
If you want to use NAT-type Actions, you must define a default Action Library.
To do this
Place the cursor on +Automation Parameters and press Enter.
The following window opens:
10:21:57 *** ENTIRE EVENT MANAGEMENT *** 30.05.06
- Add Server Parameter -
Server ... 148 P-ESY created ... 30.05.2006
> Comment -------------------------------------------------------------------
! - Automation Parameters - !
Logical ! !
! Rule Timeout .......... _30 SEC Loop Criterion _ !
! Rule Locktime ......... ___ ___ Loop Frequency _10 !
! Resumetime ... ___ ___ !
! 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
|
Enter Database Nr, File Nr and Natural Library name of the FUSER where NAT-type Actions are located.
If you omit Database Nr and File Nr, the FUSER currently defined takes effect.
Copy the program EXNAT--P from the SYSNCLSV library to your defined Action Library using the Natural SYSMAIN utility. Use this as a program frame or as an example to build your own NAT-type Actions.
If Natural Security is installed, the User ID indicated by the <NSCUSER> parameter must be linked to the Action Library if the Action Library is defined as people-protected.