** CROSS-POST from CICS-L **
Soliciting interest for CICS / CMF related RFE asking IBM to add OPROG (originating region PROGRAM), similar to what was added with CICS/TS 4.2 OTRAN, OAPPLID and other O-prefix CMF transaction data-fields, making OPROG available for data-capture in the CICS/CMF SMF 110 subtype 1 data.
The information proves most beneficial with CICS application-transaction reporting in MRO environments, where the "mirror" transaction is identified but not the TOR-initiated application PROGRAM. The alternative method (manual correlation) involves sorting the CMF detail transaction records to associate TOR/AOR/FOR records based on NETNAME/UOWID, which is tedious.
Here's a link to the RFE request where you can go to vote:
Scott BarrySBBWorks, Inc.
Sadly IBM rejected the CICS RFE (Request for Enhancement) to add OPROG, so MICS CICS Analyzer clients/admins will want to continue capturing the TOR-related PROGRAM value in a CICACTn variable (using MSACCOUNT feature, in CICOPS) in order to accurately support the CICS/MRO environment.
Otherwise without this MICS "customization", it will be impossible to associate the "heaving lifting" transactions that get executed in AOR (Application-Owning) or FOR (File-Owning) Region's "mirror" transaction (such as those observed with TRANCODE="CSMI", PROGRAM="DFHMIRS").
Today, consider also that the Merrill MXG software provides a supplemental ASUMUOW process to correlate the various CICS-related and other disparate subsystem transactions (those from DB2, MQ) in order to create a complete end-to-end picture for a business-application transaction execution (at the detail level of course).