IBM Mainframe Forum

Hi,

I've followed the Omegamon's manual to set SMF_WRITE = YES in order to collect the VSAM file I/O details to SMF. According to the manual, the data would be logged in DBD. How can I extract the DBD dataset and use SAS (I use MXG) to extract the VSAM I/O statistics?

Thanks a lot!

The MXG output includes TYPE1415 which is a SAS data set containing I/O. Depending upon what you are doing, MXG also creates a number of SAS data sets dealing with VSAM data.

Robert,

Thank you for your reply.

I follow the document "Configuration and Customization Guide OMEGAMON II® for CICS Version 520" Chaper 12 Enabling Monitoring for User Defined Events (P.156) to specify SMF_WRITE for VSAM I/O under section Global Data Area. From my understanding, this would lead to logging of each VSAM statistics in DBD for each transaction (P.202). So, how can I get the DBD to generate reports for the VSAM detail statistics for each transaction?

MXG data is generated independently of the product, generally. We use Mainview at my site, not Omegamon. Hence, I have no idea on your question. The CICS transaction reports I generate all use MXG-created SAS data bases, not product data.

Robert,

Thank you for your reply again.

I've checked on related documentation available in my site. I suspect the data I would like to have should be located in "CICS Statistics datasets".

According the DOCPDB member in my site's MXG sourcelib, I learn the follow:

"CICS Statistics datasets are created in //WORK but
are not output to the PDB. You have choices:

- Write them to the "PDB" DDname as SMF is read,
unsorted. They will take no space in //WORK.
//SYSIN DD *
%LET CICSTAT=PDB;
_CICSTAT;
%INCLUDE SOURCLIB(BUILDPDB);

Macro _CICSTAT is a special purpose macro that
changes the &WCICddd and &PCICddd macro variable
values to the value of macro variable CICSTAT.

- Leave them written to //WORK, but use the exit
member EXPDBOUT to SORT them into your PDB:
In member EXPDBOUT, add:
%LET CICSTAT=PDB;
_CICSTAT;
_S110ST

Macros are defined in member VMAC110, for details."

From the about paragraph, I assume I should follow either one of the above methods to extract the type 110 SMF data. I've tried to follow the coding suggested but seems fail. Would you give me some suggestion?

Thank you very much!

MXG members ASUMUOW and ASUMCICX are used to create CICSTRAN.CICSTRAN, which is the SAS data base in MXG that contains detailed CICS transaction information. If your site is already generating ASUMUOW and ASUMCICX on the daily (or whatever) PDB file, then CICSTRAN will have the details of each CICS transaction. If your site is not generating ASUMUOW and ASUMCICX, then your best bet would be to raise an issue on the MXG web site to get some help with extracting the data directly from the SMF raw data. Look at members ADOCCICI, ADOCUOW, ASUMUOW and ASUMCICX in the MXG.SOURCELIB for more information about them.

Robert,

Many thanks to your reply! I will try to check and consult MXG.

Recently, I try to look into SMF type 112 record in order to get more information. Would anyone have experience on handle this SMF type?