AAI Integration for IWSz

AAI can integrate with the IBM IWS schedulers, to receive execution events, job definitions, and workload planning periods. AAI uses that to define jobstreams, forecast and track process executions that happen on the IWS mainframe, and present them with easily digestible visualizations and aggregations. This section covers all the information you need to implement the integration between AAI and IWS schedulers.

The Main Components in the Integration

AAI supports integrations with two types of IWS systems:

  • IWSz, the IBM scheduler on the zOS mainframe
  • IWSd, the IBM scheduling solution for distributed systems

AAI provides two ways to configure and implement the integration with the backend zOS mainframe where the job data is maintained and execution events are tracked:

More importantly, AAI provides a custom solution that performs the majority of the IWSz and IWSd data processing functions and makes the processed data available to the AAI Server via a web http connection.

Who Should Read These Topics?

Implementing IWS Connector and the IWSz Server for AAI and establishing the connection to the AAI server requires the collaboration between mainframe specialists and AAI administrators. To accomplish these tasks, a deep understanding of both mainframe environments and of AAI is required.

Types of Data Retrieved by the IWSz Server for AAI

The IWSz Server for AAI retrieves two types of data from IWSz:

  • Definition data

    This data comprises Applications and Operation details, Calendars and Periods that are defined in IWSz.

    Two files make up the IWSz Definition Data set. They provide all the details that AAI needs to create and maintain AAI jobstream definitions.

    Usually these files are created, delivered and processed by AAI once per day. The creation and delivery of the files can be scheduled in the IWSz Server for AAI. AAI will, by default, process the Definition Data files at 01:00 so the scheduled time in the IWSz Server for AAI should set sufficiently earlier than that time to allow the files to be delivered prior to the 01:00 processing time.

  • IWSz Current Plan data

    These are the details of the Current Plan of Operations in use by IWSz and tracking audit data for the previous Plan period.

    Two files make up the Current Plan Data feed that enable AAI to determine the IWSz workloads that will be executing during the next Plan Period, including workloads carried over from the previous Plan Period. The data should be generated every time a Plan Extend or Plan Re-Plan process occurs in IWSz.

    Note:

    Tracking of IWSz workloads in AAI will be suspended following a Plan Extend or Re-Plan until details of the new Current Plan of Operations data file and the associated audit data file are delivered to the AAI system.

  • Event data

    These are the details of the executions of the IWSz managed workload.

    One file makes up the IWSz Event Data feed. It provides all the details of the ongoing IWSz activity around the submission and tracking of the IWSz Applications and Operations that enables AAI to provide near real-time status of the progress of jobstreams that AAI defines and then monitors.

    This file is created and delivered by the IWSz Server for AAI as often as is possible, with each file containing data based on a minute boundary. Frequency of the creation and delivery of this file depends on the run time of the EQQBATCH process that extracts the audit data from the JTnn logging files and is related to the amount of data being generated by IWSz during each Event Cycle. The IWSz Server for AAI provides an Event Run Time Analysis function to monitor the time taken for Event Data generation.

See also: