Generating a performance dictionary record using DFHMNDUP

A performance dictionary record holds specific information about each data field in a performance data record. It derives its information from predefined CICS® fields, and from any user-defined fields in the MCT specified for the CICS run. For programming information about the performance dictionary and data records, see the CICS Customization Guide. For information about the MCT definitions, see the CICS Resource Definition Guide.

To enable you to process SMF data sets that contain performance data records but not a dictionary record, DFHMNDUP writes a dictionary record to a sequential data set. The dictionary record is written to a data set specified on a DD statement with a ddname of SYSUT4. You must put this data set in front of any data set(s) you are processing and which contain performance data. You provide control information for the DFHMNDUP program in the SYSIN data set so that it can generate the correct dictionary record for the performance data you are processing. The values that are specified are used to construct the fields in the SMF Header and Product section. The relationship of DFHMNDUP SYSIN parameters to SMF fields is shown in Table 5.

Table 5. Relationship of DFHMNDUP SYSIN parameters to SMF fields
SYSIN PARM SMF Dsect field Meaning
DATE SMFMNDTE Date record moved
GAPPLID SMFMNPRN Product name (Generic APPLID)
JOBDATE SMFMNRSD Job execution date
JOBNAME SMFMNJBN Jobname of CICS job
JOBTIME SMFMNRST Job execution time
SAPPLID SMFMNSPN Specific APPLID
SYSID SMFMNSID System identification
TIME SMFMNTME Time record moved
UPPERCASE n/a Uppercase output
USERID SMFMNUIF User identification

You specify control information for the DFHMNDUP program on the following parameters:

DATE=yyddd or DATE=yyyyddd
specifies the Julian date to be included in the dictionary record, where:
yy
represents the year of the twentieth century (for example 98 for 1998).
yyyy
represents the year (for the twenty-first century the year must be represented by yyyy. If yy is coded the twentieth century is assumed).
ddd
represents the day, in the range 1 through 366.

For example 96354 represents the 20th December 1996 and the date 2005354 represents the 20th December 2005. If you do not specify a date, the current date is used.

GAPPLID=name
specifies the APPLID specified on either the APPLID= system initialization parameter, or the generic_applid in an XRF environment for which you are analyzing performance data.
Note:
It is important not to confuse the term "generic applid" with "generic resource name".

Remember that "generic" and "specific" applids apply only to systems that use XRF. CICS systems that do not use XRF have only one applid, which is the value defined in the "APPLID=3D" parameter.

  • For XRF, a CICS system's generic applid is defined on the APPLID system initialization parameter and is the name by which CICS is known in the network. (That is, it is the name quoted by remote CICS systems, on the NETNAME option of CONNECTION definitions, to identify this CICS.)
  • A CICS system's specific applid is used to distinguish between the pair of XRF systems. It is the name quoted on a VTAM® APPL statement, to identify this CICS to VTAM.
  • A CICS system's generic resource name is defined on the GRNAME system initialization parameter, and enables CICS to become a member of a VTAM generic resource group.

Note, in particular, that you cannot use both VTAM generic resources and XRF. If you use VTAM generic resources, you should specify only one name on the APPLID system initialization parameter.

JOBDATE=yyddd or JOBDATE=yyyyddd
specifies the MVS™ job date (in Julian date format) to be included in the dictionary record.
yy
represents the year of the twentieth century (for example, 98 for 1998).
yyyy
represents the year (for the twenty-first century the year must be represented by yyyy. If yy is coded the twentieth century is assumed).
ddd
represents the day, in the range 1 through 366.

For example, the date 96354 represents the 20th December 1996 and the date 2005354 represents the 20th December 2005. If you do not specify a date, the current date is used.

JOBNAME=xxxxxxxx
specifies an MVS job name for the CICS region to be included in the dictionary record.
JOBTIME=hhmmss
specifies a time stamp, as six numeric characters, for MVS job to be included in the dictionary record.
hh
the number of hours, in the range 00 through 24.
mm
the number of minutes, in the range 00 through 59.
ss
the number of seconds, in the range 00 through 59.

If you do not specify a time, the current time is used.

MCT=xx
specifies the suffix of the monitoring control table (MCT) used in the CICS run for which you are analyzing performance data. If your CICS region ran with the system initialization parameter MCT=NO (which results in a default MCT dynamically created by CICS monitoring domain) you should specify MCT=NO for DFHMNDUP also. Alternatively, you can indicate that your CICS used a default MCT by specifying ‘MCT=’ or ‘MCT=,’.
Note:
Using DFHMNDUP to generate a performance dictionary record, means that you must use two-character suffixes for MCTs. If you create an MCT with only a single-character suffix, it is accepted by CICS but rejected by DFHMNDUP.
SAPPLID=name
specifies the specific VTAM APPLID of the CICS region for which you are analyzing performance data. If you omit this parameter, the value you specify on the GAPPLID parameter is taken as the specific APPLID also.
SYSID=xxxx
specifies the system identifier of the MVS system that owns the SMF data sets.
TIME=hhmmss
specifies a time stamp for the dictionary record. If you do not specify a time, the current time is used.
UPPERCASE
specifies that you want the statistics output in uppercase only. If you want output in mixed case (the default), do not code this parameter.
USERID=xxxxxxxx
specifies eight alphanumeric characters that represent the user identification of the MVS job to be included in the dictionary record. The user identification value xxxxxxxx, must correspond to any values that you have set up in your MVS IEFUSI exit, but does not have to be a real userid. For information on the MVS job step initiation exit IEFUSI, see the z/OS MVS Installation Exits manual, SA22-7593.

You can enter each parameter on a separate line, with the parameter keyword starting in column one. Alternatively, you can enter all of the parameters on a single line, starting in column one, with each parameter separated by a comma. If your CICS used a default MCT, you can enter the MCT parameter as ‘MCT=NO’, ‘MCT=’, or ‘MCT=,‘.

For example, you can use the following three methods to specify the same control information for the DFHMNDUP program:

Related concepts
Introduction to CICS monitoring

Related reference
Monitoring dictionary utility program (DFHMNDUP)
Sample job illustrating the use of DFHMNDUP
[[ Contents Previous Page | Next Page Index ]]