Copied Code Parameters › Advantages

Advantages

Frequently used portions of CA Culprit code can be stored and accessed by several reports or users. By using stored code, the number of parameters input at run time is reduced, and standard file definitions and procedures are established. For example, users can store INPUT and REC parameters that define a shared input file. Users can also store type 7 and type 8 process parameters that perform an operation common to several reports.

Stored Code

Stored code, which can be inserted in a parameter stream at run time, can be maintained in card decks, the data dictionary, partitioned data sets in a z/OS environment, source statement libraries in a z/VSE environment, CA Panvalet libraries, or CA Librarian libraries. At a z/VM installation, the source can be retrieved from a z/VM MACLIB or a z/OS partitioned data set. The stored code is inserted during the precompile phase of CA Culprit processing.

Three parameters are available to copy and modify stored code, as follows:

• USE
• =COPY
• =MACRO

Inline code can also be modified by using these parameters. Although the copied or inline code is modified for a particular CA Culprit run, the modifications do not alter the code that is stored.

Capabilities of Copied Code Parameters

The following table highlights the capabilities of each copied code parameter. Each parameter is discussed separately below, followed by a discussion of the =MACRO AMLIST routine, which can be used to list the fields of input records.

More information:

Introduction