Retrieve Operational Information

Note: Before you retrieve operational information, you must configure the z/OS® connection. If you associate the z/OS connection to a project only but you do not configure it, you cannot retrieve the data. For more information, see topic Configuring the z/OS Connection.

Go to IBM® Application Discovery Build Configuration, select the Projects tab, select the project, select the z/OS node, right-click to display the menu, and select the Retrieve Operational Information option to display the following window.

This image shows the Query Operational Information Tasks window.
Note: If you do not configure the z/OS connection for the selected task, a warning message is presented, indicating the entries for which the configuration is missing.
A list of available tasks is presented grouped by categories: You can choose to Retrieve schedulers information, Retrieve TP monitor information, Retrieve Database information, or Retrieve other information. Make the selections then click OK to run Query Operational Information.
Note: The available options depend on the type of project you create.

Control-M

If the Control-M task is selected, it brings information about the Control-M jobs for the selected project based on the z/OS Connection configuration. For more information, see Configuring Control-M tab. The retrieved information is in XML format and it is automatically added by the task in the project's ControlM folder.

Considering that you can attach more than one z/OS Connection to a project, an XML file is retrieved for each connection.

After the task is successfully executed, for a proper Control-M analysis, the IBM AD project needs to be built. Instructions for performing a Build of the project can be found at Building Projects.

Following is a list of entities/objects for which Connect for mainframe brings information:
  • Adabas
    The Connect for mainframe gives information about a total of three entities:
    1. Adabas Database.
    2. Adabas File.
    3. Adabas Field.
    The information refers to physical allocations, defined files that include file fields.
  • CA Workload Automation CA 7 Edition
    The Connect for mainframe gives information about a total of two entities:
    1. CA 7 Jobs.
    2. Datasets.

    The information refers to triggering and dependencies.

    The following two options are provided for CA-7 Workload Automation:
    Full CA-7 import
    Removes the existing information that is stored in the repository, and then imports the information from the mainframe into the repository as configured.
    Update CA-7 information with the differences since the last import
    Import only the changes from the mainframe into the repository as configured.
    Note: A full import must be run before an update. Otherwise, the update will not have the correct results.
    For more information about the CA-7 configuration in AD Connect for Mainframe, see Configuration for CA-7.
  • CSD (CICS®)
    The Connect for mainframe gives information about a total of seven entities:
    1. CICS Region
    2. CICS Group
    3. CICS List
    4. CICS File
    5. CICS Map
    6. CICS Program
    7. CICS Transaction

    The information refers to all CICS regions, including defined programs\transactions\maps\files, hierarchy of groups and lists, and performance information for transactions such as Elapsed time, IO count, and DB2® count.

  • DB/2
    Connect for mainframe brings information about a total of 14 entities:
    1. Db2® Database.
    2. Db2 Table.
    3. Db2 Column.
    4. Db2 Index.
    5. Db2 Key.
    6. Db2 Package.
    7. Db2 Package List.
    8. Db2 Plan.
    9. Db2 Storage Group.
    10. Db2 Stored Procedure.
    11. Db2 Table Space.
    12. Db2 Trigger.
    13. Db2 View.
    14. Db2 Volume.

    The information refers to all databases, tables, columns, table spaces, triggers, views, plans storage groups.

    The operational information data about Db2 is only stored in the repository and it is not downloaded on the disk. The Mainframe Layout graph, from IBM AD Analyze Client, is showing basic details coming from Db2.

  • Devices and Physical files
    The Connect for mainframe gives information about the following entities:
    1. Physical files
    2. Devices

    The information refers to all devices connected to the LPAR, and all physical data sets on disk devices.

  • Hardware
    The Connect for mainframe gives information about one entity:
    1. CPU
  • IMS
    The Connect for mainframe gives information about a total of three entities:
    1. IMS Database.
    2. IMS Transaction.
    3. IMS Program.

    The information refers to databases, programs, and transactions of IMS.

  • LPAR and SYSPLEX
    The Connect for mainframe gives information about a total of two entities:
    1. LPAR Information.
    2. Sysplex Information.

    The information refers to LPARS, SYSPLEXS, the relationships, and links to other entities (CPU, installed software)

  • MQ Series
    The Connect for mainframe gives information about a total of three entities:
    1. Queue Manager
    2. Queue
    3. Channel

    The information refers to Queue Managers, Queues, and Channels.

  • Predict
    The Connect for mainframe gives information about a total of two entities:
    1. Predict file.
    2. Predict field.

    The information refers to predict files and fields.

  • SMF
    The Connect for Mainframe gives information about a total of three entities:
    1. SMF JCL information.
    2. SMF JCL Step information.
    3. SMF JCL Step IO.

    The information refers to scheduled jobs, including total CPU consumption, IO count, and CPU count per steps, and used physical files.

  • Tivoli® Workload Scheduler
    The Connect for mainframe gives information about a total of two entities:
    1. TWS Applications.
    2. TWS Jobs.

    The information refers to TWS defined applications, jobs, and their dependencies.

    Before you retrieve the information, a confirmation window is displayed. Click Yes to start the selected query operation.

    After the operation is finished, 2 log files are generated: One containing the errors (if applicable), the other detailing the operations undertaken. These log files are stored in the following location: project name/zOS/logs/zOS name.

Retrieve operational information in the background

IBM AD Build Client provides an option to retrieve operational information in the background. To force the retrieve operation information to run in the background, follow the steps:
  1. Click Start, select Run then type cmd followed by ENTER to open the command window.
  2. Go to the folder where your IBM AD Build Client is installed and locate IBMApplicationDiscoveryBuildConfiguration.exe.
  3. Drag IBMApplicationDiscoveryBuildConfiguration.exe file into the command window then type /? and press ENTER. A window is displayed containing detailed instructions about how to retrieve operational information in the background. In the command prompt enter the following command:
    C:\Program Files\IBM Application Discovery Build Client\Bin\Release\IBMApplicationDiscoveryBuildConfiguration.exe /ba <fully qualified file name>

    The <fully qualified file name> points to an INI file that contains information about actions that are executed in headless mode.

    A sample for the configuration INI file is found in C:\Program Files\IBM Application Discovery Build Client\Bin\Release\Samples\BuildConfigurationBASample.ini. You can use the sample INI file or create a new configuration file.

    The format of <fully qualified file name> is as follows:
    [OperationalInformation]
;CA7IMPORT=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;CA7UPDATE=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;TWS=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;CSD=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;IMS=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;Adabas=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;DB2=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;Predict=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;SMF=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;MQ=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]...
;CONTROL_M=[<ProjectName1>, <zOSConnectionName1>],[<ProjectName2>, <zOSConnectionName2>]
    Attention: In order for the operational information to be taken into account, the comment tag ; must be removed.
    Predefined values for <Operational task>:
    • Schedulers information: CA7IMPORT, CA7UPDATE, TWS
    • TP monitor information: CSD, IMS
    • Databases information: ADABAS, DB2, Predict
    • Other information: MQ, SMF
  4. A log file is generated in C:\Program Files\IBM Application Discovery Build Client\Bin\Release\Log folder. The name of the log file is ADBuildConfiguration_datetime.log.