1 / 25

CICS Transaction Measurement with no Pain

Abstract. A new approach for measuring CICS transactions using SMF exits to collect and buffer the data in memory. The data is sent on real-time to SQL databases on open platforms via TCP/IP protocol. Totally eliminates the need for DASD space and I/O channel bandwidth on the mainframe.. To

evelina
Download Presentation

CICS Transaction Measurement with no Pain

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


    1. CICS Transaction Measurement with no Pain Luiz Eduardo Gazola

    2. Abstract A new approach for measuring CICS transactions using SMF exits to collect and buffer the data in memory. The data is sent on real-time to SQL databases on open platforms via TCP/IP protocol. Totally eliminates the need for DASD space and I/O channel bandwidth on the mainframe.

    3. Topics CICS Transaction Measurement SMF Overview Proposed Model Key Concepts Implementation Topics Conclusion Questions

    4. CICS CICS is by far the most commonly used IBM transaction monitor

    5. CICS does NOT address: Number of transactions; Response times; Resource usage; Peek times; Charge-back.

    6. CICS Transaction Measurement CICS uses SMF type 110 records to report transaction usage: Generate a lot of records; Requires additional software:

    7. CICS Measurement Products

    8. SMF Characteristics General purpose log file for z/OS components: Strange format (VBS); Records in binary data; Very large datasets; Usually offline (on tapes); Read many times; Retained for many years.

    9. SMF Data Flow The component issues SMFETWM macro; SMF write record on SYS.MANx; IFASMFDP utility copy records to SMF dump datasets; SMF extractors read dump files and save the data on their own formats.

    10. Proposed model Intercept the SMF record before written to SYS.MANx; Copy the record to a buffer in CSA and discard it; Process it on another address space; Send to a remote process to load it on the database.

    11. Key Concepts CICS Monitoring Facility Monitoring Control Table (MCT) CICS Dictionary SMF Exits Dynamic Exits Facility

    12. CICS Monitoring Facility (CMF) Colect the trasactions counters; Build the SMF 110 record; And invoke the SMF macro to write the record.

    13. Monitoring Control Table (MCT) Select the fields to log: From 12 to more than 250 transactions per record

    14. CICS Dictionary Informs the layout of the performance records accordingly to the MCT: Field name; Field type; Offset; Size.

    15. SMF Exits The SMF exits (IEFU8x) are called by the SMFEWTM macro to: View or modify records; Discard records.

    16. Dynamic Exits Facility Manages the activation and deactivation of system exists dynamically: Add and remove; Chain of exits; Deactivate if abend.

    17. IEFU84 - SMF Exit The exit name depend on the parmlib(SMFPRMxx):

    18. Implementation Topics Intercepting the Records Record Processor Producer and Consumer Data Transfer Remote Data Loader

    19. Intercepting the Records IEFU84 exit: Check the record type; Copy the record to a circular buffer; Return with RC=04 to discard record.

    20. Record Processor Address space responsable to consume the records on the circular buffer: Runs on its own address space; May allocate any sort of resources; Do not interfere on the CICS regions.

    21. Producer and Consumer Should care: Synchronization; Enough buffers on the circular buffer to avoid loosing records; May have many streams of consumers.

    22. Data Transfer Much better: Non-persistent queues on MQ-Series; TCP/IP sockets for message exchange.

    23. Remote Data Loader Loads the data directly into the database: Do NOT use INSERT; Use bulk commands: 10,000 records/s; Use a table for the raw data; Consolidate data on historical tables (< 5%).

    24. On the database, everything gets easier

    25. Conclusion Do not stress your mainframe trying to figure out what is going inside the box. Managing outside the box saves CPU, DASD and Channel resources. The mainframe will run even more transactions.

    26. Questions Special thanks to: Christian Nielsen Wells Fargo Bank Luiz Eduardo Gazola gazola@optimize-software.com.br

More Related