Control statements for managing archive and auxiliary trace data sets The control statements to the left control the allocation of data sets, data set attributes, and the registration of data set in a checkpoint data set. Introduction ► What is Rocket C\Prof? Multiple trace capture modes Import CICS auxiliary trace data sets and dump files Enterprise-wide data capture and control Measurement across the application lifecycle A complete understanding of your CICS application Minimum operating requirements About this document Initial Setup ► Getting started Before you begin Setup procedure For C\Prof ISPF users and systems administrators ► Enterprise-wide data collection and analysis ► Profiling CICS transactions Recording the CICS internal trace for transaction profiling Displaying transactions recorded in a CICS region Browsing the transaction list Diving into transaction and program detail ► Creating and analyzing C\Prof auxiliary trace data sets Taking a snapshot of the CICS internal trace Recording to auxiliary trace data sets Opening registered auxiliary trace data sets Browsing trace entries Importing auxiliary trace data sets into the profiler Creating and viewing your own trace entries Automatic problem capture with event-driven snap ► Managing data collection across a sysplex Expanding your collection topology to CICS regions in other LPARs Reviewing collection status across your topology Collecting from CICS regions that use multiregion operation (MRO) Splitting collectors for operational management Configuring automatic internal trace control for specific CICS regions Cleaning up old collection data via housekeeping Configuring for optimum performance Controlling the collector via operator commands ► Working with auxiliary trace data sets Personal view Registered view Creating an auxiliary trace data set report. ► Ad hoc batch data collection Snap the CICS internal trace Record for transaction profiling Record to auxiliary trace data sets Import an auxiliary trace data set into the profiler Create an auxiliary trace data set from a CICS dump using IPCS ► Collector reference Sample JCL ► Configuration files Discover CICS regions and create a configuration file Performing a syntax check of your configuration file ► Collection modes (modes of operation) Multi-user data collection (SERVER) Ad hoc batch data collection Control statement summary ► Control statement reference ► Control statements for managing archive and auxiliary trace data sets CHECKPT=data-set-name ARCHDSN=pattern AUXTRSW=option +PREFIX=data-set-name-prefix SUMMARY, DETAIL, and AUXILIARY OUTDD=ddname-pattern BLKSIZE=value INDD=pattern ► Control statements to define CICS regions and assign groups CICS=jobname GROUP=name and GROUPEND ► Control statements for client request processing SOCKET=zFS-path-name PERMISSIONS=octal-numeric-value XCFGROUP=group-name MAXDURATION=value units WRAP ► Control statements for collector startup and shutdown SERVICE=service-class-name LIMIT=value units ► Control statements that set the level of detail for profiling LEVEL=value SIZE=value ► Control statements for internal trace data collection and control TRACECONTROL ACTIVATETRACE=(level [,START [,upsize][,recording-mode]) RESETTRACE=(level [,RESET] | [,STOP | START [,downsize]]) STNTRxx=level ► Control statements for transaction filtering TRAN=(name1,name2, ) EXCLUDETRAN=(name1,name2, ) PROGRAM=(name1,name1,...) RESPONSE=(minimum,maximum) ABEND=option ► Control statements for multiregion operation (MRO) MRO=YES | NO ► Additional control statements WORKFILE For C\Prof Web UI users ► C\Prof Web UI Logging on and off Selecting a region layout Recording CICS transactions ► Analyzing recorded transactions Transaction list Application and trace events Program analysis Taking a snap of the CICS internal trace Column configurations References ► Troubleshooting Messages and Codes ► Web UI application server Starting and stopping Configuration Generating a keyring Glossary Summary of changes