Pre-Loading CA7 Event Data for AAI

The Mainframe Data Provider includes an Historical Event Data Pre-Load function that enables you to load archived event data from the history GDG before starting the CA7 Server for AAI. This functionality is purely optional, and is available because when theCA7 Server for AAI starts up, it will push only event data that currently resides in the live log files.

Important Planning Considerations

Pre-loading event data is, as its name implies, a preparatory step. If you choose to pre-load archived event data in preparation for installing a new CA7 Server for AAI, be aware of the following:

  • You must finish executing this pre-load step before you start your new instance of CA7 Server for AAII.

  • If you choose to use the pre-load function for an instance of CA7 Server for AAI that is already running, you must first stop the CA7 Server for AAI instance before running the pre-load jobs.

  • You can use the pre-load function for any instance of CA7 Server for AAI (old or new), but you most often use it for new instances. It may also make sense to use it for old instances that have been shutdown for extended periods.

  • Before you run the Historical Event Data Pre-Load function, make sure that the Data Delivery Method you have defined in your instance configuration of the CA7 Server for AAI is working correctly, as this delivery method is what the Pre-Load function uses to deliver files.

  • The provided JCL is set up to run as if it were the Primary Server STC, because it has to run under the same User ID as the Primary STC would run.

Pre-Loading Event Data

Use the following steps to pre-load historical event data in preparation to installing a new instance of the CA7 Server for AAI.

  1. Start the Instance Management System (IMS) ISPF based UI and define the new CA7 Instance. For information, see Configuring an Instance of the CA7 Server for AAI.

  2. Copy the JCL Procedure member AIZTxxxy in the CUSTLIB to the Primary Server STC member in your Procedure Library.

    This procedure performs a Test Data Delivery to verify that your Delivery process from the mainframe to the AAI server is working. Modify the TESTDSN= parameter to reference a dataset to use for the test delivery.

    Hint: A good example of a test dataset to deliver is the SRVRSCFG dataset for the Instance.

  3. Start the Primary STC that would then execute the Test Delivery JCL. Verify that a file called DELIVERY_TEST appears in the target CA7 Data directory on the AAI server and is readable.

  4. Modify the JCL member AI7Lxxxy in the CUSTLIB to create a suitable JOB card for executing the CA7 History Log Analysis function. The output from this job provides you with information on every GDG dataset in the CA7 History Log GDG Base, providing Start and End Date and Time information for each dataset. Submit this JOB under any User ID that has READ access to the CA7 History Log GDG datasets.

  5. Use the output from the History Log Analysis Job to identify a Start Date (YYDDD format) and End Date (YYDDD format) to use as the Date Range parameters for executing the Event Data Pre-Load function.

  6. Copy the JCL Procedure member AI7Pxxxy in the CUSTLIB to the Primary Server STC member in your Procedure Library. This procedure performs the Historical Event Data Delivery to the target CA7 Data directory on your AAI server. Modify the // SET LDRSTART= and // SET LDREND= statements to specify a YYDDD format start and end date range for the execution.

  7. Start the Primary STC which would then execute the Event Data Pre-Load JCL to deliver the daily Event Data files to the AAI server, one for each day in the date range specified.

    Note:

    Depending on the number of days in the date range provided and the amount of Event Data that has to be processed and delivered for each day, this execution could take some considerable time to complete.

  8. Once the Historical Event Data Pre-Load execution has completed and the historical Event Data files are stored on the AAI server you are ready to start the Primary STC for running the CA7 Server for AAI in real-time delivery mode.

  9. Copy the Primary Server STC JCL Procedure member AI7Sxxxy in the CUSTLIB to the Primary Server STC member in your Procedure Library to run the CA7 Server for AAI Primary Server process.

  10. Before the AAI system can process the historical Event Data the CA7 Instance must be defined into AAI, as described in the documentation, and a full Definition Data Delivery Request should be performed.

  11. Start the Primary STC which will start the CA7 Server for AAI process and start delivering Event Data files in real-time.

  12. Once the CA7 Server for AAI is active you can then use the Instance Management System ISPF based UI to manually Request a Definition Data Delivery to occur, as described in the documentation.

  13. Once the Definition Data is received by AAI and loaded to the AAI database, AAI should then process the Historical Event Data files delivered previously to pre-load execution information for the jobs now defined in the AAI database.