Wayne,
The MCT is only required for CICS monitoring records which have a
dictionary. CICS statistics SMF 110 records are fixed.
On 2020-05-27 11:54 AM, Wayne Bickerdike wrote:
You'll need a CICS MCT entry (Monitor control table).
Sample JCL:
//DELIT EXEC PGM=IDCAMS
//SYSIN DD *
DELETE SYS.CICSTS54.CICS.MNDUPREC
SET MAXCC=0
/*
//SYSPRINT DD SYSOUT=A
//MNDUP EXEC PGM=DFHMNDUP
//STEPLIB DD DSN=SYS3.CICSTS54.CICS.SDFHLOAD,DISP=SHR
//SYSUT4 DD DSN=SYS.CICSTS54.CICS.MNDUPREC,DISP=(NEW,CATLG),
// UNIT=SYSDA,SPACE=(TRK,(1,1))
//SYSPRINT DD SYSOUT=A
//SYSUDUMP DD DUMMY
//SYSIN DD *
MCT=WB
SYSID=MVS1
GAPPLID=CICS54T
SAPPLID=CICS54T
DATE=2018316
TIME=000100
//SMFUNLD EXEC PGM=IFASMFDP
//* INDD1 DD DSN=SYS1.MAN1,DISP=SHR,AMP=('BUFSP=65536')
//INDD1 DD DSN=SYS6.SMFDATA.BACKUP(0),DISP=SHR
// DD DSN=SYS6.SMFDATA.BACKUP(-1),DISP=SHR
// DD DSN=SYS6.SMFDATA.BACKUP(-2),DISP=SHR
//OUTDD1 DD DSN=&&TEMP,DISP=(NEW,PASS),SPACE=(CYL,(20,20)),
// UNIT=SYSDA
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
INDD(INDD1,OPTIONS(DUMP))
OUTDD(OUTDD1,TYPE(110(1)))
/*
//*
//DEL2 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
DELETE USER.DFHMOLS.UNLOAD
SET MAXCC=0
/*
//PRNT EXEC PGM=DFH$MOLS
//STEPLIB DD DSN=SYS1.USER.LOAD,DISP=SHR
// DD DSN=SYS3.CICSTS54.CICS.SDFHLOAD,DISP=SHR
//INPUT DD DSN=SYS.CICSTS54.CICS.MNDUPREC,DISP=SHR
// DD DSN=&&TEMP,DISP=(OLD,DELETE),UNIT=SYSDA
//SYSUT2 DD DSN=&&XPND,DISP=(NEW,PASS),UNIT=SYSDA,
// SPACE=(CYL,(25,10))
//SYSUT4 DD DSN=USER.DFHMOLS.UNLOAD,DISP=(,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(25,10))
//SORTWK01 DD SPACE=(CYL,(5,1)),UNIT=SYSDA
//SORTWK02 DD SPACE=(CYL,(5,1)),UNIT=SYSDA
//SORTWK03 DD SPACE=(CYL,(5,1)),UNIT=SYSDA
//SORTWK04 DD SPACE=(CYL,(5,1)),UNIT=SYSDA
//SORTWK05 DD SPACE=(CYL,(5,1)),UNIT=SYSDA
//SORTDIAG DD SYSOUT=A
//SYSOUT DD SYSOUT=A
//SYSPRINT DD SYSOUT=A
//SYSABEND DD SYSOUT=A
//SYSUDUMP DD SYSOUT=A
//SYSIN DD *
OPTION LOCAL
*
RESOURCE ALL
PRINT ALL
UNLOAD
Sample output lots of fields including USER ID::
********************************* TOP OF DATA
**********************************
*** DFH$MOLS - CICS 7.1.0 - MONITORING DATA LISTING PROGRAM *** DATE
2020
OPTION LOCAL
*
RESOURCE ALL
PRINT ALL
UNLOAD
********************************************************************************
* SMF HEADER * TIME = 0:01:00.00 DATE = 2018/316 SYSTEM-ID
= MV
* * REC TYPE = 110 REC SUBTYPE = 1 NO OF
TRIPLETS = 2
* * PROD SECT OFFSET = 44 PROD SECT LENGTH = 114
NU
* * DATA SECT OFFSET = 158 DATA SECT LENGTH =
10218 NU
********************************************************************************
* SMF PRODUCT SECTION * REC VERSION = 0710 REC MAINT IND = 0 G-APPLID
= CI
* * JOB NAME = ENTRY DATE = 2019/005
ENTRY TI
* * 1ST CONN. OFFSET = 0 CONNECTOR LENGTH = 0
NU
* * 1ST DATA OFFSET = 158 DATA ROW LENGTH = 26
NU
* * COMPRESSED DATA LENGTH = 0
* * LOCAL TIME ZONE = 00000D69 LEAP SECOND OFFSET =
00000
********************************************************************************
FIELD-NAME SIZE CONNECTOR OFFSET NICKNAME NEW
IN-COR
DFHTASK C001 4 X'0001' X'0000' TRAN
DFHTERM C002 4 X'0002' X'0004' TERM
DFHCICS C089 8 X'0003' X'0008' USERID
DFHTASK C004 4 X'0004' X'0010' TTYPE
DFHCICS T005 8 X'0005' X'0014' START
DFHCICS T006 8 X'0006' X'001C' STOP
DFHTASK P031 4 X'0007' X'0024' TRANNUM
DFHTASK A109 4 X'0008' X'0028' TRANPRI
DFHTASK C166 8 X'0009' X'002C' TCLSNAME
DFHTERM C111 8 X'000A' X'0034' LUNAME
DFHPROG C071 8 X'000B' X'003C' PGMNAME
DFHTASK C097 20 X'000C' X'0044' NETUOWPX
DFHTASK C098 8 X'000D' X'0058' NETUOWSX
DFHCICS C130 4 X'000E' X'FFFF' RSYSID
On Wed, May 27, 2020 at 1:46 PM Wayne Bickerdike <wayn...@gmail.com> wrote:
CICS SMF 110. You could probably use DFH$MOLS to analyse, it takes some of
the hard work out of breaking the SMF into readable stuff.
On Wed, May 27, 2020 at 7:13 AM Matthew Stitt <mathwst...@bellsouth.net>
wrote:
CICS statistics. Make sure they are turned on.
The CICS statistics are written as SMF 110 records.
It is possible to analyze them using various tools.
toot toot> Check CBT file 529. You will also need CBT file 527 for a
sub-program or two.
Matthew
On Tue, 26 May 2020 16:59:28 -0400, Bob Bridges <robhbrid...@gmail.com>
wrote:
I'm not a CICS jock, but at many of the installations I've worked at
I've had occasion to analyze a record of who used which CICS transactions
over the past weeks or years. The datasets have had varying formats, but
I've gradually come to believe that CICS must track such things and keep a
log somewhere. The alternative is to believe that every installation
reinvents this useful wheel independently, which I'm inclined to doubt.
Now I'm at a new place, and the guy I take to be the local CICS sysprog
(but I may be mistaken) says he's not aware of such a function. Is this
something easy I can point out to him, or am I mistaken about it being a
feature available to all CICS installations?
For that matter, is it something I can maybe find myself, without even
bothering him?
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/* Be careful of your thoughts; they may become words at any moment.
-Ira Gassen */
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
--
Wayne V. Bickerdike
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
