Control parameters of the DFHSTUP program

You can use the parameters described here to control the output of statistics by the DFHSTUP program.

If you want the statistics output in uppercase only, you must code the UPPERCASE=YES parameter first in the parameter list. If you do not code any parameter, the DFHSTUP program formats all the collection types for all APPLIDs to a page size of 60 lines.

For information about the job that you use to run the DFHSTUP program, see Job to run the DFHSTUP program.

The DFHSTUP reports list statistics records in the following type order:
  • Statistics domain
  • Transaction manager
  • Transaction class
  • Dispatcher
  • MVS™ TCBs (not in summary report)
  • Recovery Manager
  • Enqueue Manager
  • Monitoring
  • Storage Manager DSA
  • Storage Manager task subpool
  • Storage Manager domain subpool
  • Loader
  • LIBRARY resources (not in summary report)
  • Temporary storage
  • Transient data
  • VTAM® (now z/OS® Communications Server)
  • Terminal Autoinstall
  • Program Autoinstall
  • System dump
  • Transaction dump
  • Table manager
  • Transaction
  • Program definitions
  • Program
  • File
  • LSRpool
  • LSRpool file
  • Transient data queue
  • Journalname
  • Logger
  • Logstream
  • IBM® MQ connection
  • IBM MQ monitor
  • DB2® connection
  • DB2 entries
  • TCP/IP
  • TCP/IP services
  • ASYNCSERVICE
  • IPCONN resources
  • BUNDLE resources
  • URIMAP resources
  • PIPELINE resources
  • WEBSERVICE resources
  • ATOMSERVICE resources
  • XMTRANSFORM resources
  • DOCTEMPLATE resources
  • Event processing
  • EVENTBINDING resources
  • CAPTURESPEC resources
  • JVMSERVER resources
  • JVMPROGRAM resources
  • Terminal
  • ISC/IRC system and mode entry
  • ISC/IRC attach time security
  • DBCTL
  • FEPI pool
  • FEPI connection
  • FEPI target
  • User domain

For resource types that are supported as private resources for applications deployed on platforms, statistics for both public and private resources are reported. The statistics for public resources of that type appear first, followed by the statistics for private resources of that type.

Parameters

UPPERCASE=YES

Specifies that the statistics output is to be in uppercase only. The parameter must be coded as shown in uppercase characters with no spaces between words. The parameter must be the first one coded in the parameter list. If you want output in mixed case (the default), do not code this parameter. This parameter is ignored in an EXTRACT report.

SELECT APPLID={applid|(applid1[,applid2]..[,applidN])}

Specifies the APPLIDs of the CICS® regions for which you want statistics to be formatted and printed. The parameter keywords must be coded as shown, with one blank between the two words. Code only one SELECT APPLID parameter or one IGNORE APPLID parameter, with up to 2000 APPLIDs. If you specify two or more APPLIDs, you must enclose them in parentheses, and separate them by commas. If you specify more than 2000 APPLIDs, the results are unpredictable.

If your CICS regions are defined with both generic and specific APPLIDs, it is the specific APPLID that you must specify on the SELECT APPLID parameter.

If you do not code this parameter, the DFHSTUP program reports statistics for all APPLIDs found in the DFHSTATS data set, other than those APPLIDs specified on an IGNORE APPLID parameter.

IGNORE APPLID={applid|(applid1[,applid2]..[,applidN])}

Specifies the APPLIDs of the CICS regions for which you want the statistics ignored. The parameter keywords must be coded as shown, with one blank between the two keywords. Code only one SELECT APPLID parameter or one IGNORE APPLID parameter, with up to 2000 APPLIDs. If you specify two or more APPLIDs, you must enclose them in parentheses, and separate them by commas. If you specify more than 2000 APPLIDs, the results are unpredictable.

If your CICS regions are defined with both generic and specific APPLIDs, it is the specific APPLID that you must specify on the IGNORE APPLID parameter.

If you do not code this parameter, the DFHSTUP program reports statistics for all APPLIDs found in the DFHSTATS data set, according to the SELECT APPLID parameter.

SELECT TYPE={type|(type1[,type2]...[,typeN])}
Specifies the resource types for which you want statistics to be formatted and printed. The parameter keywords must be coded as shown, with one blank between the two words. If you specify two or more resource types, you must enclose them in parentheses, and separate them by commas.

Code either the SELECT TYPE parameter or the IGNORE TYPE parameter, but not both.

If you do not code this parameter, the DFHSTUP program reports statistics for all resource types found in the DFHSTATS data set, other than those resource types specified on an IGNORE TYPE parameter.

The resource types that you can code on the SELECT TYPE parameter are shown in the following list:
  • ASYNCSERVICE
  • ATOMSERVICE
  • AUTOINSTALL
  • BUNDLE
  • CAPTURESPEC
  • CONNECTION
  • DBCTL
  • DB2
  • DB2CONN (a subset of DB2, including DB2 Connection statistics but omitting DB2 Entry statistics)
  • DISPATCHER
  • DOCTEMPLATE
  • ENQUEUE
  • EPADAPTER
  • EVENTBINDING
  • EVENTPROCESS
  • FEPI
  • FILE
  • JOURNAL
  • JVMPROGRAM
  • JVMSERVER
  • LIBRARY
  • LOADER (a subset of PROGRAM, including Loader Global statistics but omitting Program statistics)
  • LOGSTREAM
  • LSRPOOL
  • MONITOR
  • MQCONN
  • MQMONITOR
  • MVSTCB
  • OVERVIEW (a summary comprising Transaction Manager Global statistics, Dispatcher Global statistics, Loader Global statistics, and Storage Manager DSA statistics)
  • PIPELINE
  • PROGAUTO
  • PROGRAM
  • PROGRAMDEF
  • STATS
  • STORAGE
  • SYSDUMP
  • TABLEMGR
  • TCPIP
  • TCPIPSERV
  • TDQUEUE
  • TERMINAL
  • TRANCLASS or TCLASS
  • TRANDATA (a subset of TDQUEUE, including Transient Data Global statistics but omitting Transient Data Resource (Queue) statistics)
  • TRANDUMP
  • TRANMGR (a subset of TRANSACTION, including Transaction Manager Global statistics but omitting Transaction Manager Resource statistics)
  • TRANSACTION
  • TSQUEUE
  • URIMAP
  • USER
  • VTAM (now z/OS Communications Server)
  • WEBSERVICE
  • XMLTRANSFORM

For resource types that are supported as private resources for applications deployed on platforms, statistics for both public and private resources are reported when you select a resource type. The statistics for public resources of that type appear first in the report, followed by the statistics for private resources of that type.

When you use SELECT TYPE, if you want to reduce the size of your statistics reports you can code the summary resource types DB2CONN, LOADER, TRANMGR, and TRANDATA instead of the complete resource types DB2, PROGRAM, TDQUEUE, and TRANSACTION. To get an overview statistics report, comprising Transaction Manager Global statistics, Dispatcher Global statistics, Loader Global statistics, and Storage Manager statistics, code the OVERVIEW resource type.

IGNORE TYPE={type|(type1[,type2]...[,typeN])}
Specifies the resource types for which you want the statistics ignored. The parameter keywords must be coded as shown, with one blank between the two keywords. If you specify two or more resource types, you must enclose them in parentheses, and separate them by commas.

Code either the SELECT TYPE parameter or the IGNORE TYPE parameter, but not both. When you use IGNORE TYPE, you can code most of the resource types listed above for the SELECT TYPE parameter, except for the OVERVIEW resource type and the summary resource types (DB2CONN, LOADER, TRANMGR, and TRANDATA). The IGNORE TYPE parameter can only be used to ignore complete resource types; it does not ignore resource types that are subsets or combinations of other resource types.

If you do not code this parameter, the DFHSTUP program reports statistics for the resource types found in the DFHSTATS data set, depending on the SELECT TYPE parameter.

COLLECTION TYPE={ALL|[,INT][,EOD][,REQ][,RRT][,USS]}
Specifies the statistics records to be included in the formatted reports for the selected APPLIDs, according to their collection type. The parameter keywords must be coded as shown, with one blank between the two words. The operands are as follows:
ALL
Format the statistics for all types of collections, for all the specified APPLIDs. This is normally the default. However, if you specify the EXTRACT control parameter but not COLLECTION TYPE, only the extract exit is invoked and no other statistics output is produced.
INT
Format the statistics that were collected at specified intervals, for all of the selected APPLIDs.
EOD
Format end-of-day type statistics for all of the selected APPLIDs. The end-of-day collection type is another interval collection, being the final collection of statistics for the last interval at the time of shutdown or logical end-of-day. Because the specified interval over which interval statistics are being collected might not have elapsed, the actual interval spanning the end-of-day collection can be a short interval.
REQ
Format requested statistics for all of the selected APPLIDs.
RRT
Format requested reset statistics for all of the selected APPLIDs. These are statistics asked for by using the CEMT or EXEC CICS PERFORM STATISTICS RESETNOW command or, when changing the statistics recording status, the CEMT or EXEC CICS SET STATISTICS ON|OFF RECORDNOW RESETNOW command.
USS
Format unsolicited statistics for all of the selected APPLIDs. Unsolicited statistics are collected by CICS for dynamically allocated and deallocated resources. For a complete description of the unsolicited statistics record types, see Introduction to CICS statistics.
EXTRACT USERPROGRAM=progname
Specifies a user program that can process statistics records to create reports of statistics data allowing you to produce tailored statistics reports.
PROGNAME
The name of the user-written program that is to process the data retrieved by the EXTRACT command. You must supply a PROGNAME value.

Specifying the EXTRACT exit command changes the default DFHSTUP report settings. If you specify only the EXTRACT exit, only the extract exit is driven; other DFHSTUP reports are suppressed. If the EXTRACT control statement is specified, other statistics report control statements, such as SUMMARY, must also be specified to ensure that the appropriate reports are produced. See The DFHSTUP extract statistics reporting function for guidance.

TIME START=hh.mm.ss,STOP=hh.mm.ss,ELAPSED|DAILY
Specifies that the DFHSTUP program is to print only the statistics collected during the specified period. The period is determined by a combination of the START time to STOP time, the ELAPSED|DAILY keyword, and the DATE parameter, as follows:
ELAPSED
This is the default. If ELAPSED is coded, the DFHSTUP program processes every statistics record between the DATE START and TIME START until the DATE STOP and TIME STOP.
DAILY
If DAILY is coded, the DFHSTUP program processes every statistics record between the TIME START and TIME STOP for each day between the specified DATE START and DATE STOP.
If no DATE parameter is coded, statistics collected during the specified period are printed regardless of the date on which they were collected. The parameter keywords must be coded exactly as shown, with one blank between the first two words, and with both START and STOP times specified. The start and stop times must be specified as:
hh.mm.ss
where:
  • hh = number of hours (24 hour clock notation)
  • mm = number of minutes
  • ss = number of seconds.
Note:
  1. If the specified period (START time to STOP time) spans across midnight, you must also code the DATE parameter.
  2. If interval statistics are not collected and written to the SMF data set during the specified period (START time to STOP time), the DFHSTUP reports might not show the information you are looking for. To see a specific item of information, ensure that your specified period covers a statistics collection that includes the item you want.

    For example, you might want to see statistics relating to a transaction that was run at 10:15. If your recording interval is set at the default of 1 hour, interval statistics are written to the SMF data set at 10:00, and again at 11:00. If you run the DFHSTUP program and specify a START time of 09:30 and a STOP time of 10:30, the DFHSTUP reports will not show the statistics relating to the transaction that was run at 10:15, because the SMF data set during that period contains only the interval statistics that were collected at 10:00. The statistics relating to the transaction that was run at 10:15 are written to the SMF data set at the next statistics collection, at 11:00.

    The times of statistics collections are controlled by the STATINT and STATEOD system initialization parameters. You can also perform a statistics collection at any time by using the CEMT or EXEC CICS command PERFORM STATISTICS RECORD. For example, to avoid waiting until 11.00 to see statistics relating to a transaction that was run at 10:15, you can use the PERFORM STATISTICS RECORD command to record statistics immediately, and then run the DFHSTUP program, specifying a period that includes the time when you entered the command.

Examples
  1. To process every statistics record written between 10th September 2011 at 10:00 hours and 16th September 2011 at 20:00 hours, you can code the following TIME and DATE control statements:

    TIME START=10.00.00,STOP=20.00.00,ELAPSED

    DATE START=09/10/2011,STOP=09/16/2011

  2. To process every statistics record written between 10:00 hours and 20:00 hours each day starting on 10th September 2011 and stopping on 16th September 2011, you can code the following TIME and DATE control statements:

    TIME START=10.00.00,STOP=20.00.00,DAILY

    DATE START=09/10/2011,STOP=09/16/2011

DATE START=mm/dd/yy or mm/dd/yyyy,STOP=mm/dd/yy or mm/dd/yyyy
Specifies that the DFHSTUP program is to print only statistics collected during the specified period (START date to STOP date). This parameter should be used with the TIME parameter. If no TIME parameter is coded, statistics collected at any time during the specified period are printed. The parameter keywords must be coded exactly as shown, with one blank between the first two words, and with both START and STOP dates specified. The start and stop dates must be specified as:
mm/dd/yy or mm/dd/yyyy
where:
  • mm = month of the year
  • dd = day of the month
  • yy = year of the twenty-first century
  • yyyy = year

If yy is coded the twenty-first century is assumed. For example, a date of 12/20/16 is for the 20th December 2016 and a date of 12/20/1996 is for the 20th December 1996.

PAGE SIZE=number
Specifies the number of lines to be formatted per page, in the range 20 - 99. The default page size is 60 lines.
SUMMARY
Specifies that the DFHSTUP program is to produce a summary report for each APPLID selected. A summary report is composed by adding the statistics contained in the interval, requested reset, end-of-day, and unsolicited collections. The summary report statistics are listed in almost the same order as interval and end-of-day reports. The only difference is that DBCTL statistics appear at the end of the summary. DBCTL statistics are unsolicited only, so you do not get them for interval, requested reset, or end-of-day collections.
Note: The statistics produced in the summary report for SELECT TYPE(LSRPOOL) do not contain buffer information for individual LSR pools.

If the SMF data set (or data sets) contain CICS statistics from several runs of CICS with the same APPLID, you must use the TIME parameter, and if necessary the DATE parameter, to produce the summary report for one run of CICS. If you do not use the TIME and DATE parameters to specify one of several runs of CICS, the results are unpredictable.

You can reduce the output significantly if you code this parameter and omit the COLLECTION TYPE parameter.

If this parameter is not coded, a summary report is not produced.