Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

IBM IMS

 

The IBM Information Management System (IMS) DSM for JSA allows you to use an IBM mainframe to collect events and audit IMS database transactions.

To integrate IBM IMS events with JSA, you must download scripts that allow IBM IMS events to be written to a log file.

Overview of the event collection process:

  1. The IBM mainframe records all security events as Service Management Framework (SMF) records in a live repository.

  2. The IBM IMS data is extracted from the live repository using the SMF dump utility. The SMF file contains all of the events and fields from the previous day in raw SMF format.

  3. The qeximsloadlib.trs program pulls data from the SMF formatted file. The qeximsloadlib.trs program only pulls the relevant events and fields for JSA and writes that information in a condensed format for compatibility. The information is saved in a location accessible by JSA.

  4. JSA uses the log file protocol source to retrieve the output file information for JSA on a scheduled basis. JSA then imports and processes this file.

Configuring IBM IMS

You can integrate IBM IMS with JSA:

  1. From the https://support.juniper.net/support/downloads/, download the following compressed file:

    QexIMS_bundled.tar.gz

  2. On a Linux-based operating system, extract the file:

    tar -zxvf qexims_bundled.tar.gz

    The following files are contained in the archive:

    • qexims_jcl.txt - Job Control Language file

    • qeximsloadlib.trs - Compressed program library (requires IBM TRSMAIN)

    • qexims_trsmain_JCL.txt - Job Control Language for TRSMAIN to decompress the .trs file

  3. Load the files onto the IBM mainframe by using the following methods:

    Upload the sample qexims_trsmain_JCL.txt and qexims_jcl.txt files by using the TEXT protocol.

  4. Upload the qeximsloadlib.trs file by using BINARY mode transfer and append to a pre-allocated data set. The qeximsloadlib.trs file is a tersed file that contains the executable (the mainframe program QexIMS). When you upload the .trs file from a workstation, pre-allocate a file on the mainframe with the following DCB attributes: DSORG=PS, RECFM=FB, LRECL= 1024, BLKSIZE=6144. The file transfer type must be binary mode and not text. Note

    QexIMS is a small C mainframe program that reads the output of the IMS log file (EARLOUT data) line by line. QexIMS adds a header to each record that contains event information, for example, record descriptor, the date, and time. The program places each field into the output record, suppresses trailing blank characters, and delimits each field with the pipe character. This output file is formatted for JSA and the blank suppression reduces network traffic to JSA. This program does not need much CPU or I/O disk resources.

  5. Customize the qexims_trsmain_JCL.txt file according to your installation-specific information for parameters.

    For example, jobcard, data set naming conventions, output destinations, retention periods, and space requirements.

    The qexims_trsmain_JCL.txt file uses the IBM utility TRSMAIN to extract the program that is stored in the qeximsloadlib.trs file.

    An example of the qexims_trsmain_JCL.txt file includes:

    The .trs input file is an IBM TERSE formatted library and is extracted by running the JCL, which calls the TRSMAIN. This tersed file, when extracted, creates a PDS linklib with the qexims program as a member.

  6. You can STEPLIB to this library or choose to move the program to one of the LINKLIBs that are in LINKLST. The program does not require authorization.
  7. The qexims_jcl.txt file is a text file that contains a sample JCL. You must configure the job card to meet your configuration.

    The qexims_jcl.txt sample file includes:

  8. After the output file is created, you must make one of the following choices:
    • Schedule a job to transfer the output file to an interim FTP server.

    • Each time the job completes, the output file is forwarded to an interim FTP server. You must configure the following parameters in the sample JCL to successfully forward the output to an interim FTP server:

    For example:

    Where:

    • <target server> is the IP address or host name of the interim FTP server to receive the output file.

    • <USER> is the user name required to access the interim FTP server.

    • <PASSWORD> is the password required to access the interim FTP server.

    • <IMSOUT> is the name of the output file saved to the interim FTP server.

    For example:

    PUT 'Q1JACK.QEXIMS.OUTPUT.C320' /192.168.1.101/IMS/QEXIMS.OUTPUT.C320

    Note

    You must remove commented lines that begin with //* for the script to properly forward the output file to the interim FTP server.

    You are now ready to configure the log file protocol.

  9. Schedule JSA to retrieve the output file from IBM IMS.

    If the mainframe is configured to serve files through FTP, SFTP, or allow SCP, then no interim FTP server is required and JSA can pull the output file directly from the mainframe. The following text must be commented out using //* or deleted from the qexims_jcl.txt file:

    You are now ready to configure the log file protocol.

Log File Log Source Parameters for IBM IMS

If JSA does not automatically detect the log source, add an IBM IMS log source on the JSA Console by using the Log File protocol.

When using the Log File protocol, there are specific parameters that you must use.

The following table describes the parameters that require specific values to collect Log File events from IBM IMS:

Table 1: Log File Log Source Parameters for the IBM IMS DSM

Parameter

Value

Log Source type

IBM IMS

Protocol Configuration

Syslog

Log Source Identifier

Type the IP address or host name for the log source. The log source identifier must be unique for the log source type.