Configuring Event Monitoring › Configure Connection Event History Recording

Configure Connection Event History Recording

CA NetMaster NM for TCP/IP stores and records details of all IP, FTP, and Telnet connections in the IPLOG database for the last seven days. This data is useful for problem determination and planning. It can also be useful for audit and security purposes.

Important! To record connection events, you must ensure that your server is set up to generate SMF records. For more information, see the Installation Guide.

To configure connection event history recording to suit your requirements, you must do the following:

1. Define the connection event history data set details.
2. Define the stack event processing options.

Define the Connection Event History Data Set

This procedure defines the data set where the connection events are stored, how long they are retained, and the time of day that expired events are deleted.

Note: Connection events from a busy network can occur in large numbers and at high rates. This results in high VSAM activity and high file record and space requirements. IPLOG does reorganize itself using the IPLOGSEQ data set. However, if you have a large or busy network, we recommend that you review the space and extent allocations of IPLOG and IPLOGSEQ.

To define the connection event history data set

1. Enter /PARMS at the prompt.

   The Customizer : Parameter Groups panel appears.

2. Enter U beside the IPFILES parameter group in the FILES category.

   The IPFILES - TCP/IP File Specifications panel appears.

3. Complete the following fields:

   IPLOG Event History Dataset

   Defines the database to which the events are logged.

   Keep IPLOG data for

   Specifies the number of days to retain the events in the IPLOG database.

   Range: 0-7 days

   Delete expired IPLOG data at

   Specifies the time of day when the IPLOG data that is older than the specified retention period is deleted.

   IPLOGSEQ Reorg Dataset

   Defines the sequential data set used by the IPLOG reorganization process.

4. Press F6 (Action).

   The details are applied (but not saved).

5. Press F3 (File).

   The details are saved.

Define Stack Event Processing

This procedure defines the type of events to log in the activity log and the type of events to save in the IPLOG database.

Note: If you do not intend to look for these events on the activity log or in the event history, do not perform this procedure because it can consume CPU resources.

To define stack event processing

1. Enter /PARMS at the prompt.

   The Customizer : Parameter Groups panel appears.

2. Enter U beside the IPEVENT parameter group in the MONITORS category.
3. Specify YES for each type of event that you want to log or save, or both.
4. Press F6 (Action).

   The details are applied (but not saved).

5. Press F3 (File).

   The details are saved.