Event Management › Event Management Utilities › Route z/OS Console Messages to Event Management Utilities

Route z/OS Console Messages to Event Management Utilities

You may wish to obtain messages from the system console to be processed under Event Management or CA NSM. Event Management Utilities (CAS9FEMS) uses a method that incorporates an MPF exit on the mainframe to trap the messages and forward them to the Event Management Utilities.

Once the message is in FEMS, you have the option of how and where to treat the message.

To trap messages on the mainframe and forward them to FEMS

1. Test the FEMS server.
   1. Ensure that CAICCI is active on the system.
   2. Create the DEST and CRIT DD files as documented in the Administration Guide.
   3. Update CAW0JCL member CAS9FEMS to match your installation standards.
   4. Use the parms -t -v to run a test in verbose mode.
2. Start the FEMS server. After the server has been tested successfully it should be converted into an STC. Remember to use a user ID that has a valid OMVS segment in the security record. If using Event Management store-and-forward in conjunction with CAS9FEMS, the user ID should belong to the same OMVS security group as the ID that was used to install Event Management.
3. Activate the MPF exit. Update the MPFLSTxx member to include the desired messages. The message should include the USEREXIT(CATNMPEX) operand to call the exit to process the message. For example, to trap message IEF450I you would code:

   “IEF450I,SUP(NO),USEREXIT(CATNMPEX)”
   

4. Update the CRIT and DEST files to handle the additional messages. For example, to capture an IEF450 message, add the following to the CRIT file and a corresponding line:

   CON11: text("^IEF450") lang(*) sev(*)
   

   Add one of the following to the DEST file to send it to Event Management.

   • To reach the local node:

     CON11: driver(/cai/nsmem/bin/casyfem1)
     

   • To reach a remote node XYZNODE:

     CON11: driver(/cai/nsmem/bin/casyfem1) drvropts(-n XYZNODE)
     

5. Test the exit. Create the messages on the console and verify that they reach the desired destination.

   When testing is complete, you must issue a STOP command to terminate the CAS9FEMS job. From the MVS console, issue /P TESTJOB where TESTJOB is the jobname.

6. Write message actions. This step may be required if the message is reaching Event Management.

   If messages reach Event Management on the local node, you may direct them to remote Event Management nodes by defining Message Actions. Alternatively, messages may be sent directly to other Event Management nodes by using the drvropts parameter in the DEST.DAT file.

This process can be used to open a help desk issue based on console messages. Once this process is working to your satisfaction, you can forward the desired messages to Event Management, where a CA NSM Advanced Help Desk (AHD) issue can be opened. For more information on opening issues, see the Unicenter TNG Administration Guide.