To verify that an Entire Event Management Server, identified by node number vrs, has been installed correctly, proceed as follows:

1. Check the environment defined for the Entire Event Management Server:

   • Verify the startup parameters defined in the library SYSSATU.

     • Logon to the library SYSSATU where you keep your master definitions for all Servers of the SAT family.

     • Check that the SATvrs entry in the member SATDIR points to the correct FNAT for the application SYSSAT.

     • Check member SATPvrs for the SATSTART entry with PRODUCT=NCL. The TYPE parameter must have the value SUBTASK; the APPLIB parameter must have the value SYSNCLSV, and the SERVSYSF parameter must point to the correct Entire Event Management System File 2 where the object definitions assigned to the Server are kept. PRODUCT and PREFIX together must identify the prefix of the parameter blocks specific to this Entire Event Management Server.

     • Check member SATPvrs and the member <NCLPARMS> indicated by the MEMBER parameter in SATPvrs for the SATENV parameter NATTASK. The value in effect for the Entire Event Management Server vrs must indicate the correct Natural subtask module which is intended to run the Entire Event Management Server.

       This Natural module must be correctly linked, marked REENTERABLE and REUSABLE, and must be accessible in the run time environment of the Entire System Server node vrs.

     • Check member SATPvrs and/or member <NCLPARMS> indicated by the MEMBER parameter for the parameter NCLSEQF in the NCLENV block. This parameter must point to two sequential files with the names <NCLSEQF>.SVvrs.BACKUP1 and <NCLSEQF>.SVvrs.BACKUP2 respectively. These files must be allocated and for the first startup must either both be empty or must consist of only one record containing the string NEW. On z/VSE, the sequential files <NCLSEQF>.SVvrs.BACKUP1.HD and <NCLSEQF>.SVvrs.BACKUP2.HD must also be allocated.

     • Check the member SATPvrs and/or the member <NCLPARMS> indicated by the MEMBER parameter for the SATENV parameters NSCUSER, NSCPSWD and ESYUSER. If you use Natural Security, <NSCUSER> must be defined as user and must have access to the library SYSNCLSV and to the Action Program libraries.

       If Entire Security Server is running with security, (i.e.: SECURITY<>NONE), the user ID indicated by <ESYUSER> must be defined in the external security system and have sufficient authorization.

   • Verify the Server Parameters defined with the object Server vrs.

     • Log on to the library SYSNCL and invoke the MENUNCL or MENU program (see Logging on to Entire Event Management for the First Time).

     • Type in the direct command MODIFY SERVER vrs. On the Modify Server Parameter screen verify that the Log DBID/FNR parameter points to the correct Entire Event Management System File 3, where the Server should log the console messages.

       Link at least one Logical Console to the Server.

     • Invoke the Miscellaneous window by typing MISC as a direct command and pressing Enter. The following window opens:

       Modify Server Parameters - Miscellaneous Server Parameters

       10:30:12 *** ENTIRE EVENT MANAGEMENT *** 30.05.06 - Modify Server Parameter - Server ... 148 P-ESY created ... 30.05.2006 > Comment ------------------------------------------------------------------- ! - Miscellaneous Server Parameters - ! Logical ! ! ! Write to (Udf) Console from . 00:00 to 00:00 ! ! ! ! API Receiver Service ........ ________________ ! ! Wait before retry ....... ___ ___ ! ! ! 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

     • To prepare for step (2) below, establish a non-empty time frame for logging messages to the (Udf) Console. The Server should then log all messages to its (Udf) Console which are not covered by your own Logical Console definitions.

2. Start the Entire Event Management Server.

   • In the Entire Event Management online system, type in the direct command MONITOR STATISTICS vrs to invoke the Server Statistic Monitor screen:

     Server Statistic Monitor

     10:35:22 *** ENTIRE EVENT MANAGEMENT *** 30.05.06 Srv * - Server Statistic Monitor - Server . . . 114 F-Mc NPR Lost Statistics: Refreshed Main API Receiver Interval +----------+ +----------+ ---->! INACTIVE ! ! UNKNOWN ! +----------+ +----------+ 0 v Collect Analyze Logging Action +----------+ +----------+ +----------+ +----------+ ! INACTIVE !---->! INACTIVE !---->! INACTIVE ! -->! INACTIVE ! +----------+ +----------+ ! +----------+ ! +----------+ -----------------> total 1/sec total 1/sec total 1/sec total 1/sec executed . . 0 0.0 0 0.0 0 0.0 0 0.000 suppressed . 0 0.0 0 0.0 Events . . . 0 0.000 Traffic . . 100 % . . 0.00 % . . 0.00 % . . 0.000 % NCL2255 Service by Server 114 not available. Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Auto Exit Flip Rfrsh Menu

   • If the status of the Server (directly under the heading Server Statistic Monitor) is NPR Lost (like in example above), proceed with step 3. to start the Entire Event Management Server together with the Entire System Server.

   • If the Status of the Server is NPR Act, proceed with step 4., below, to start the Entire Event Management Server online.

3. Start the Entire Event Management Server automatically with Entire System Server.

   If the SATSTART block for the Entire Event Management Server in the SYSSATU member SATPvrs is provided correctly, the Server is started automatically with the Entire System Server node vrs.

   • Start Entire System Server node vrs.

     • The successful start of the Entire System Server is indicated by the console message:

       Entire System Server IS READY - X-COM NODE vrs IS INITIALIZED

     • The successful start of the Entire Event Management Server is indicated by the following console message sequence:

       NCL5001 CS0000-P Task NCMAINlllllkkkkk invoked successfully
       NCL5001 CS0000-P Task NCLOGGlllllkkkkk invoked successfully
       NCL5001 CS0000-P Task NCACTNlllllkkkkk invoked successfully
       NCL5001 CS0000-P Task NCANLSlllllkkkkk invoked successfully
       NCL5001 CS0000-P Task NCGETMlllllkkkkk invoked successfully
        

       where lllll and kkkkk indicate the DBID and FNR of Entire Event Management System File 2

   • If this sequence does not appear after a while:

     • Check the SYSOUT files of the Entire System Server node, if it is running on the z/OS or z/VSE operating systems.

     • If the Entire Event Management Server is running on BS2000/OSD, check the SYSLST protocol files matching the following naming convention - the file name must contain the substring:

       L.NCLxxvrs

       where xx stands for the Entire Event Management subtask and vrs for the Server number.

       xx = MA   Main Task
            LO   Logging Task
            AC   Action Task
            AN   Analysis Task
            GE   Collect Task
        

   • Proceed with step 5.

4. Start the Entire Event Management Server online.

   • In the Entire Event Management online system, type the direct command START SERVER vrs and press Enter. The Start Server window opens:

     Server Start

     10:36:50 *** ENTIRE EVENT MANAGEMENT *** 30.05.06 Srv * - Main Menu - Console ------------------------------------------------------------------- ! - Server Start - ! 1 Log ! ! 2 Ser ! Server . . . . . . 114 F-Mc MVS/ESA NPR Act ! ! ! ! Task States ! Adminis ! Main Task . . . . INACTIVE ! ! Collect Task . . INACTIVE ! 3 Env ! Analysis Task . . INACTIVE ! 4 Aut ! Logging Task . . INACTIVE ! 5 Aut ! Action Task . . . INACTIVE ! 6 Cal ! ! ! Backup File . . . . NCL.SYSF.SV114.BACKUP2 ! . Exi ! Renewed . . . . . . 96-05-29 15:42:36 ! ? Hel ! ! * Com ------------------------------------------------------------------- NCL2262 Please Confirm execution. Command ===> _________________________________________________________________ Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12--- Help Exit Flip Conf Menu

   • Confirm your start request by typing the direct command CONFIRM and pressing Enter.

   • Proceed with step 5.

5. Monitoring the Entire Event Management Server.

   • In the Entire Event Management online system, type the direct command MONITOR STATISTICS vrs and press Enter. The Server Statistic Monitor screen appears.

     • After a while the status of each Server subtask should be indicated in the appropriate box as either RUNNING or WAITING and the status of the Entire Event Management Server in total should be indicated as NCL Act directly under the heading Server Statistic Monitor.

     • In addition, since you have enabled (Udf) Console in step 1, the statistic line executed should, after a short delay, show values greater than 1 under the Collect, Analyze and Logging boxes.

   • If the subtask status and values do not change, issue any operator command to the Entire System Server node vrs by typing the direct command:

     OPER vrs <operator command>

   • If the Monitor still shows no message traffic, the interface to the system console is most probably not installed correctly. Therefore, make sure that the Entire System Server view CONSOLE is correctly installed (see the section Verify Entire Event Management Interfaces for Message Collection).