Event Management Configuration › Run the Event Management Configuration Script

Run the Event Management Configuration Script

Include Event Management zFS in BPXPRMxx by updating your system BPXPRMxx member to include the new mount points for Event Management.

Adding the new mount points to your BPXPRMxx member allows the mounts to occur automatically when your system is IPLed.

If you selected Event Management for installation, run the configuration script to customize certain files to your specific system. The configuration script, fwsetup, can be found in the designated Event Management directory (/cai/nsmem by default).

Note: Messages and prompts differ depending on whether you are running the script for the first time, rerunning the script, or re-installing. Steps that do not run under all circumstances are appropriately identified.

To run the Event Management configuration script

1. Go into OMVS on your system and change to the Event Management directory.

   cd /cai/nsmem
   

2. Invoke the script with the following command:

   . fwsetup
   

   Note: fwsetup executes many tasks. Be patient during the execution of fwsetup. The text prompt will not automatically be seen on the screen. To see the text prompt, press PF10 to refresh the screen when the status of the session changes from RUNNING to INPUT. You can press the refresh key any number of times. If you see the text prompts, type your response and press Enter, or press Enter to accept the default. Follow these steps until you see CA Common Services installation has completed.

   Important! Do Not Press Enter unless you are responding to a prompt or accepting the default to a prompt. If you press enter, you bypass the text prompt and will not be able to choose a value for your response. Instead, you will be accepting the default value.

   The following messages display:

   Installing CA Common Services...
   

   Installing Event Management component...
   

3. Choose to activate Store and Forward or not.

   In the event that other Event Management nodes cannot be reached, the Event Management Store and Forward facility can save failed events for forwarding at a later time.

   Store and Forward (default: y)

4. Choose whether to create a rules file to restrict the use of certain message actions or allow all users to issue them.

   Default behavior allows UNIXCMD and UNIXSH message actions to be submitted to this node (assuming there is a CAICCI connection) by all users. Event Management allows these two message actions to be restricted. The rules for these message actions are maintained through a utility called caevtsec. For more information on caevtsec, see the Administration Guide.

   • For first time installations:

     If the script does not find an existing rules file, you must decide if you want to create one.

     Would you like to restrict the UNIXCMD and UNIXSH message actions for this host? 
     

     These actions were not restricted in Unicenter release 1.5.(y/n) (default: n)
     

     After you answer, the following message appears:

     Installing Star Server component...
     

   • When re-installing and rerunning the script:

     The script asks if you want to create a new rules file or use the existing one.

     A version of the Event Security rules file has been detected on your system.
     

     Answering y will preserve the original rules file (from the previous installation or upgrade) and will remove the restrictions of UNIXCMD and UNIXSH message actions for this host.
     

     Answering n (default) will assume the restrictions previously enacted.
     

     Would you like to recreate Event Security rules file? (y/n) (default: n)
     

     If you choose to create a new rules file, the script informs you that the rules have been updated and the original rules file has been saved.

     The original rules file has been preserved as /cai/nsmem/opr/config/<nodename>/actnode.prf.sav
     

5. Set environment variables.

   To use Event Management, certain environment variables need to be set, including PATH and LIBPATH.

   You can have the system file etc/profile automatically set the Event Management environment variables in the /cai/nsmem/PROFILE file when a user logs on.

   • If the environment variable UPDATE_ETC in the PROFILE file is set to Y (yes), /etc/profile is updated to run the PROFILE file automatically. Your EM environment variables are then set automatically when a user logs on .
   • If the environment variable UPDATE_ETC in the PROFILE file is set to N (no), /etc/profile is not updated and all users have to manually set the EM environment variables.
   • If the environment variable UPDATE_ETC was not set in the PROFILE file either during installation or subsequently, you are asked whether you wish to update /etc/profile.

     For first time installations you have the option to update /etc/profile to set variables automatically when users logon.

     Do you want to update /etc/profile? (y/n)
     

     • If you choose y (yes), /etc/profile is updated to set environment variables for all users when they logon.
     • If you choose n (no), you must run the tngprofile script before attempting to issue any commands

     When re-installing or rerunning the fwsetup script, if it is detected that /etc/profile has been previously updated to run the PROFILE file, you may receive the following messages and the option to update /etc/profile is bypassed.

     WARNING! /etc/profile has been previously updated. Please check the contents of /etc/profile to be sure the entry is valid for the current installation. If not, remove the update and re-run this fwsetup script.
     

     WARNING! /etc/csh.login has been previously updated. Please check the contents of the file to be sure the entry is valid for the current installation. If not, remove the update and re-run this fwsetup script.
     

6. The following message appears:

   CA Common Services installation has completed.
   

7. Verify that fwsetup has completed successfully.
   • If you indicated y to update /etc/profile, in that file you should see the updates inserted for Event Management.
   • Confirm that the /cai/nsmem/RW/config/ directory contains a subdirectory with the same name as the nodename for the system.