Converting from ASG-TMON (for CICS) to BMC-Mainview (for CICS)
search cancel

Converting from ASG-TMON (for CICS) to BMC-Mainview (for CICS)


Article ID: 193443


Updated On:


MICS Resource Management


We are in the process to convert from ASG-TMON for CICS to BMC-Mainview for CICS. 

At CA-MICS we generate reports using the records that are received from TMON, but we are not sure as to what modifications (extensive or not) would need to be made in the CA-MICS Environment to generate the same reports but using Mainview.

We just did the upgrade of CA-MICS to Release 14.2 and we are running in a z/OS 2.2 soon to be z/OS 2.3.

Could you please provide us with some clues as to where to look for some documentation or details about this.


Release : 14.2



BMC Mainview, produces SMF 110 look-a-like records to the IBM CMF records.  So, while we don't specifically mention BMC Mainview in the documentation, it is to be treated as though its IBM CMF data.
Updates that will need to be made:
Update the OPTION statement.  Right now, you might have specified OPTION NOCMF MON .......  (rest of the options on the statement do not change)
You will need to change to OPTION CMF MON .......  and run a CICCGEN.  This will add any specific CMF elements to the database.
At some point in the future, maybe 6 months after total conversion to BMC, you can set the parameter to NOMON.
Then at the unit level, you need to follow the sections to add the CICS regions that are now BMC data to CICOPS. 
The documentation describes the syntax of the CICOPTS statements for MON and CMF.
After a CICOPS update, a CICPGEN is required.
Also, you will need to update the INPUTCIC member to specify the INPUTSMF DD pointing to the SMF input data set.  This is also described in chapter 7 in the CICS guide.  After an update to INPUTCIC, the DAILY and INCRCIC need to be regenerated.
MICS can process both TMON and CMF data at the same time.
As far as reports go, it depends on what data elements from the database you are reporting on.  A huge number are common across both data sources.  To know the real impact, if you have an inventory of all the elements you use from the MICS database in reporting, you can check the cluster code in CICGENIN.  If the cluster code is '00', the data element is common across all input sources.  In chapter 7.2.1, there is a table that describes the other cluster codes.