Importing auxiliary trace data sets into the profiler

You can use the C\Prof import utility to import your auxiliary trace data sets into the transaction profiler. This can be useful, for example, if you created auxiliary trace data sets from either the record or snapshot features of C\Prof but would like to view the trace from an application perspective.

Note: The C\Prof Region List will only display auxiliary trace data sets that have been registered in a C\Prof checkpoint data set. If you cannot see your auxiliary trace data sets in the list, review the data set name you have specified on the CHECKPT control statement in your C\Prof configuration file (accessible from the primary option menu) to ensure that it matches the data set used when collecting the data.

If you have an auxiliary trace data set created outside of C\Prof, or one that has not been registered in a checkpoint data set, use C\Prof primary option menu 3 Trace to import the data set. For more information, see Opening personal auxiliary trace data sets for ad hoc analysis.

To import auxiliary trace data sets registered to C\Prof, complete the following steps:

  1. On the C\Prof primary option menu, select option 1 Regions.

  2. To view all auxiliary trace data sets associated with a single CICS region, enter line action X next to the CICS region. To view all auxiliary trace data sets associated with a group of CICS regions, use line action XG.

    Note: You can create a group of CICS regions by inserting additional control statements into your C\Prof configuration file. For more information, see GROUP.

  3. Select your data sets. To import a single data set, enter line action L. To import multiple data sets at once in a single job, select a block by enter line action LL on the first data set and the last data set in the block, or select each one individually using line action L.

  4. Review the following configuration control statements generated by the dialog:

    • IMPORT

      Set the collection mode of the C\Prof utility to IMPORT This mode is used to import auxiliary trace data sets into C\Prof archive data sets so they can be viewed using the C\Prof profiler.

    • INDD=ddname-pattern

      The DD name pattern used to supply input auxiliary trace data sets to the import utility.

    • LEVEL

      The LEVEL control statement controls the amount of information that C\Prof will retain from the auxiliary trace data set during import. LEVEL=3 provides the most detail. All trace events associated with the transaction will be imported.

    • CHECKPT

      Specifies a checkpoint data set used to register the archive data sets created by the import utility. The C\Prof ISPF dialog will use this checkpoint data set to locate the resulting transaction data in the C\Prof transaction profiler.

    • ARCHDSN

      The naming pattern for new data sets created by the import utility. Each new archive data set that is created must have a unique name. Rules that govern the naming of data sets can be found in ARCHDSN=pattern.

    • SUMMARY and DETAIL

      Defines allocation attributes for the two types of archive data sets created by the import utility. You can change the allocation attributes for these data sets using the information supplied in SUMMARY, DETAIL, and AUXILIARY.

    • GROUP=name MRO=YES (multiregion operation only)

      Treat the CICS regions found in the input auxiliary trace data sets as a group that uses multiregion operation (MRO). When the MRO option is specified, transactions in one CICS region that link to a remote program in another CICS region will be reported in C\Prof as a single transaction. More information about the MRO option can be found in Collecting from CICS regions that use multiregion operation (MRO).

  5. Once your changes are complete, submit the JCL to run the import utility.

To view the resulting transaction data, use line action S on the C\Prof Region List.

Note: A complete set of configuration options for importing auxiliary trace data sets can be found in Control statement summary.

results matching ""

    No results matching ""