Jump to main content
IBM Logo Product Documentation
  • Products
  • Support
CICS Interdependency Analyzer for z/OS, 6.3
  1. Home icon
  2. Welcome
  3. The structure of the CICS® IA database
  4. The structure for the Detailed resource objects

    This section describes the structure for the Detailed resource objects.
  • Preface

    This information describes the IBM® CICS® Interdependency Analyzer for z/OS®. It explains what the program does and how to set up and run its various components.

  • What's new in CICS® IA Version 6.3

    CICS® IA Version 6.3 maintains broad functionality and provides full support for the new CICS Transaction Server 6.3. Building on previous releases, it includes updates for commands whose threadsafe status has been enhanced in CICS Transaction Server 6.3, enabling more applications to run without switching to QR TCB mode

  • Overview of the CICS® Interdependency Analyzer

    This section gives an overview of the CICS® Interdependency Analyzer (CICS IA), and describes its components.

  • Getting Started with the CICS® IA plug-in for CICS Explorer®

    The CICS® Interdependency Analyzer plug-in for CICS Explorer® provides an Eclipse-based interface to analyze your CICS IA data. It also provides cheat sheets that guide you through the steps required to configure and install CICS IA. It is recommended that you download the CICS IA plug-in and follow the steps in the cheat sheets.

  • Configuring CICS® IA

    This section describes what you need to do before you can use CICS® IA.

  • Running the Collector

    You run the CICS® IA Collector to look for instances of program commands that might cause resource dependencies or transaction affinities.

  • Updating the Dependency and Affinity database objects

    The Dependency database objects contain accumulated data about your applications and the resources that they use. Update the database objects regularly to add new information recorded by the Collector in the VSAM dependency files.

  • Managing your CICS® IA data

    With each new release CICS® IA captures more data. In volatile development environments this data can soon become out of date. If you have out of date data, the CICS IA plug-in might retrieve more data than you need. The presence of unwanted data might impede your analysis and provide confusing results.

  • The CICS® IA UDB database

    CICS® IA provides jobs to unload CICS IA data into CSV files. These files can be used to populate the IBM® supported UDB databases.

  • Running the Reporter
  • Running the Program Threadsafe report

    The threadsafe report can be run from the CICS IA Explorer plug-in or as a batch job using the sample CIUJTSQ2 that can be found in SCIUSAMP.CICS. The report runs the Db2® stored procedure CIUSPTSR.

  • Running the Load Module Scanner

    The Load Module Scanner scans load modules for instances of program commands that could cause resource dependencies or transaction affinities.

  • Running the CSECT Scanner

    The CICS® IA CSECT Scanner scans load modules for information that can be used to identify the version of each CSECT.

  • Running the Builder

    The CICS® IA Builder runs as a batch job to build affinity-transaction-group definitions suitable for input to the CICS system management product, CICSPlex SM.

  • Running the sample Db2® query

    This section describes how to run the sample CICS® IA batch query job CIUJSAMP.

  • Solving problems

    This section helps you to isolate and determine the cause of CICS® IA problems.

  • Details of dependencies and affinities collected
  • Correlating Load Module Scanner and Dependency Reporter output to source
  • The structure of the CICS® IA database
    • The structure of the Dependency database objects

      This section describes the tables and views defined in the Dependency database.

    • The structure of the Affinity objects

      This section describes the tables and views defined in the set of Affinity database objects.

    • The structure of the Load Module Scanner objects

      This section describes the tables and views defined in the Load Module Scanner database objects.

    • The structure of the CSECT Scanner objects

      This section describes the tables and views defined in the CSECT Scanner database.

    • The structure of the CICS® regions objects

      This section describes the structure of the CICS® regions objects.

    • The structure for the Detailed resource objects

      This section describes the structure for the Detailed resource objects.

      • Connections table

        Use the information in the CIU_CONNECTIONS table to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • File resource table

        Use the information in the CIU_FILE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • Program resource table

        Use the information in the CIU_PROGRAM_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • Transaction resource table

        Use the information in the CIU_TRANSID_DETAIL tables to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • Transient Data queue resource table

        Use the information in the CIU_TDQUEUE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • Temporary Storage queue resource table

        Use the information in the CIU_TSQUEUE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • Web service resource table

        Use the information in the CIU_WEBSERV_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • GLUE and TRUE exit resource table

        Use the information in the CIU_EXIT_INFO tables to write your own SQL applications to query the tables; these applications must use native SQL queries.

      • Event table

        Use the information in the CIU_EVENT_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.

    • The structure of the CICS® IA plug-in for IBM® CICS Explorer™ resource objects

      This section describes the CIU_RESOURCE table. This table is used by the CICS® IA plug-in to improve performance and combine resource tables.

    • The structure of the Version objects

      This section describes the CIU_VERSION table. This table is used by the CICS IA plug-in for CICS® Explorer to synchronize the CICS IA plug-in version being used and the base IA database objects.

    • The structure of the Command Flow table objects

      This section describes the Command Flow base table that contains records for each command that is issued by the transactions. You can write your own SQL applications to query the table; these applications must use native SQL to write the queries.

    • The Structure of the Program Flows table objects

      This section describes the structure of two CICS IA tables that are used only to generate the program flows report in the CICS IA plug-in for the CICS Explorer.

    • Type and Function mapping for monitored commands

      Learn about the correspondence between resource type and command function for the monitored CICS® commands.

  • Messages and codes

    This section describes the messages that the Collector, Query interface, Dependency Reporter, Affinities Reporter, Load Module Scanner, CSECT Scanner, and Builder can issue, and the transaction abend codes that the Collector can produce.

  • CICS® IA space considerations
  • CICS® IA security
  • CICS® IA External Interfaces

    The Appendix describes available Stored Procedures and Command Flow user exit.

  • Collecting dynamic COBOL calls

    CICS® IA detects dynamic COBOL calls, which are collected by the Dependency and Command Flow Data collectors.

  • Accessibility

    Accessibility features help a user who has a physical disability, such as restricted mobility or limited vision, to use software products successfully

  • Download PDF

    Download the PDF format documentation for CICS Interdependency Analyzer for z/OS 6.3

 Feedback

The structure for the Detailed resource objects

This section describes the structure for the Detailed resource objects.

  • File resource table
  • Program resource table
  • Transaction resource table
  • Transient Data queue resource table
  • Temporary Storage queue resource table
  • Web service resource table
  • Threadsafe table
  • GLUE and TRUE exit resource table
  • Connections table
    Use the information in the CIU_CONNECTIONS table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • File resource table
    Use the information in the CIU_FILE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Program resource table
    Use the information in the CIU_PROGRAM_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Transaction resource table
    Use the information in the CIU_TRANSID_DETAIL tables to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Transient Data queue resource table
    Use the information in the CIU_TDQUEUE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Temporary Storage queue resource table
    Use the information in the CIU_TSQUEUE_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Web service resource table
    Use the information in the CIU_WEBSERV_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • GLUE and TRUE exit resource table
    Use the information in the CIU_EXIT_INFO tables to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Event table
    Use the information in the CIU_EVENT_DETAIL table to write your own SQL applications to query the tables; these applications must use native SQL queries.
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences