Control-M/Analyzer Utilities

This chapter provides a detailed description of the Control-M/Analyzer utilities.

Some utilities prefixed by IOA replace corresponding utilities prefixed by CTB in previous versions. In such cases, the old utilities are supported for your convenience; however, you should use the IOA utilities.

CTBABI – Initialize Active Balancing File

The CTBABI utility initializes both the Active Balancing file and its backup file, ABFBKP. Activate the CTBABI utility whenever the IOADBF utility reformats these files.

CTBABI Parameter

The following parameter must be specified in the EXEC statement that invokes the CTBABI JCL procedure:

Table 165 CTBABI Parameter

Parameter

Description

DBFILEB

Name of the file to initialize

  • ABF – Active Balancing file

  • ABFBKP – Backup file of the Active Balancing file

Activating the CTBABI Utility

Copy
//    EXEC CTBABI, DBFILEB=[ABF|ABFBKP]

CTBABI Return Codes

Table 166 CTBABI Return Codes

Code

Description

0

Operation successful

other

Operation failed

Example for CTBABI

Copy
//    EXEC CTBABI,DBFILEB=ABF

This utility is used by the JOBFABF and JOBFBKP jobs, located in the CTB.V6xx.JCL library, when the Active Balancing file and its backup file are created. For additional examples, see these jobs.

CTBCMP – Compile Rule Definitions

The CTBCMP utility checks the syntax of rule definitions. It is especially useful for checking rule definitions created using a standard editor.

CTBCMP Parameters

Copy
Parm='-irulename'

where rulename is the name of the rule definition that must be checked for syntax errors. The rule name is preceded by the prefix –i (that can be uppercase or lowercase). The rule name and the –i prefix must be specified between quotes.

Activating the CTBCMP Utility

Copy
//    EXEC CTBCMP,PARM='-irulename'

CTBCMP Return Codes

Table 167 CTBCMP Return Codes

Code

Description

0

No syntax errors were found.

other

Syntax errors were found.

Example for CTBCMP

Copy
//    EXEC CTBCMP,PARM='-ICOMPTOTS'
//DABRUL DD DISP=SHR,DSN=CTB.PROD.RULES

CTBDBCP – Increase Size of a Database File

This utility copies the contents of a specified source file to a specified target file. All relevant aspects of the file are copied, including (pointers to) variable definitions, variable generations, and group information.

The sizes of the source and target files can differ. Therefore, the CTBDBCP utility is useful for increasing the size of a file. Usually, this utility copies data from a source file to a larger target file.

Copying a file is composed of the following stages:

  • Create and format a new file (target file).

  • Copy the data from the source file to the newly created target file.

  • Delete the source file.

The CTBDBVCP utility can modify all Control-M/Analyzer database files simultaneously. However, the CTBDBCP utility is more efficient than the CTBDBVCP utility when modifying a single file.

CTBDBCP Parameters

The following parameters must be specified in the EXEC statement that invokes the CTBDBCP JCL procedure:

Table 168 CTBDBCP Parameters

Parameter

Description

DBFILE

Name of the file to be enlarged. (Add the suffix .OLD to the name of the input file before the JCL procedure is executed.) The specified name becomes the name of the enlarged output file. Mandatory.

Valid names must contain one of the following suffixes:

FILE TYPE

SUFFIX

  • Group

  • Database Variable

  • Variable Generation

  • Report

  • Rule Activity

  • GRP

  • MOD

  • VAR

  • REP

  • JAF

OLDQNAME

QNAME of the input file (for validity checking only). Mandatory.

KEY

Type of index file to be generated. Mandatory. Valid values are:

FILE TYPE

VALUE

  • Group

  • Database Variable

  • Variable Generation

  • Report

  • Rule Activity

  • KEYGRP

  • KEYDBM

  • KEYDBV

  • KEYREP

  • KEYJAFJ

The KEY value matches an existing descriptor member supplied in the Control-M/Analyzer PARM library.

DUAL

Indicates if a mirror image file is maintained. Mandatory. Valid values:

  • TRUE – Use this value if DUAL is set to Y (Yes) in the respective DEF* member in the INSTWORK library.

  • FALSE – Use this value if DUAL is set to N (No) (the default value) in the respective DEF* member in the INSTWORK library.

Activating the CTBDBCP Utility

Copy
//  EXEC IOADBF,FUNC=INIT,D=INSTWORK,M=DEFxxxD           allocate new file
//  EXEC CTBDBCP,DBFILE=xxx,OLDQNAME=qname,KEY=KEYyyy   copy old contents

Valid values for xxx and yyy are:

Table 169 CTBDBCP File Type Values

File Type

xxx

yyy

Group

GRP

GRP

Database Variable

MOD

DBM

Variable Generation

VAR

DBV

Report

REP

REP

Rule Activity

JAF

JAFJ

CTBDBCP Return Codes

Table 170 CTBDBCP Return Codes

Parameter

Description

0

Copy operation performed successfully.

other

Descriptive execution error; copy operation failed.

Procedure CTBDBCP

Member CTBDBCP of the IOA PROCLIB library contains a procedure that calls a series of programs to automatically enlarge a database file. The following explanation assumes that the name of the file that needs to be enlarged is ...GRPD. Before using this procedure, perform the following steps:

  1. Rename the source input file from ...GRPD... to ...GRPD...OLD. For example, rename file CTB.V600.GRPD.E000 to CTB.V600.GRPD.E000.OLD

  2. If DUAL is set to Y (Yes) in member DEFGRPD in the INSTWORK library, rename file CTB.V600.GRPD.D000 to CTB.V600.GRPD.D000.OLD.

  3. Modify member DEFGRPD in the INSTWORK library by increasing the space allocated for the file.

  4. Run the job in member JOBFGRP of the CTB.V6xx.JCL library.

When the procedure described above is called, the following actions are performed:

  1. Program IOADBF formats a new pre-allocated IOA Access Method output file.

  2. Program CTBDBCP copies data from the input file to the output file.

  3. Program IOADIG verifies the integrity of the output file data component.

  4. Program IOADBF reformats the existing index component for the file.

  5. Program IOADIB rebuilds the index component.

  6. Program IOADPT prints index and data component control records to the output file.

For additional information, see sample member JDBCP in the JCL library.

CTBDBIB – Rebuild a Control-M/Analyzer Index File

The CTBDBIB utility rebuilds index files for various Control-M/Analyzer data files. The new index files correspond to information contained in the data files.

This utility rebuilds the indexes of a specific data file.

The index file that is to be rebuilt must be allocated and formatted prior to activating the utility.

This utility is used

  • When the space remaining for the existing index file is insufficient. In this case

Delete the index file.

Redefine the index file with the required amount of space.

Format the index file with the IOADBF utility.

Rebuild the index file with the CTBDBIB utility.

  • In case of index file integrity problems: Index file integrity problems can be detected using the IOADII utility, described later in this guide.

  • In case of data file integrity problems: Correct the data file and re-index it with the CTBDBIB utility to reproduce the corresponding index file.

CTBDBIB Parameter

The following parameter can be specified in the EXEC statement that invokes the CTBDBIB JCL procedure:

Table 171 CTBDBIB Parameter

Parameter

Description

DBFILE

Name of data file to be processed

SYSIN parameters are provided in the KEYyyy members in the Control-M/Analyzer PARM library for your convenience. File name specifications are hard coded (predefined) in these members.

Activating the CTBDBIB Utility

Copy
//     EXEC CTBDBIB,DBFILE=xxxD
//DADBS  DD DISP=SHR,DSN=CTB.PROD.xxxD.E000                       
//DAyyy  DD DISP=SHR,DSN=CTB.PROD.xxxI.E000                       
//SYSIN  DD DSN=CTB.PROD.PARM(KEYyyy),DISP=SHR

Valid values for xxx and yyy are:

Table 172 CTBDBIB Values

File Type

xxx

yyy

Group

GRP

GRP

Database Variable

MOD

DBM

Variable Generation

VAR

DBV

Report

REP

REP

Rule Activity

JAF

JAFJ

CTBDBIB Return Codes

Table 173 CTBDBIB Error Codes

Code

Description

0

Operation performed successfully

other

Operation failed

Example for CTBDBIB

Copy
//      EXEC  CTBDBIB,DBFILE=GRPD
//SYSIN   DD  DSN=CTB.PROD.PARM(KEYGRP),DISP=SHR
//DAGRP   DD  DSN=CTB.PROD.GRPI,DISP=SHR

The CTBDBIB utility is used by the following jobs in the JCL library. For additional examples, see the following jobs:

Table 174 CTBDBIB Jobs

Job

Description

JOBBDBM

Rebuilds the index of the Database Variable Basic file

JOBBDBV

Rebuilds the index of the Generation file

JOBBGRP

Rebuilds the index of the Group file

JOBBJAF

Rebuilds the index of the Rule Activity file

JOBBREP

Rebuilds the index of the Report file

CTBDBVCG – Change Number of Variable Generations

The CTBDBVCG utility changes the maximum number of generations specified for one or more database variables. It is useful whenever the number of generations must be changed but is most often used when changing the status (mode) of variables from test to production. The utility can be invoked in batch mode as described in "Activating the Utility."

The number of generations to be retained in the database can be increased or decreased. The content of existing variable generations can be retained or deleted. All other relevant aspects of the variables are retained, including definitions and group information.

It is possible to change the number of generations of all variables, groups of variables (with a common group name prefix), or one or more variables of the same group (with a common variable name prefix) in one activation of the CTBDBVCG utility.

CTBDBVCG Parameters

The following parameters can be specified in the EXEC statement that invokes the CTBDBVCG JCL procedure. These parameters dynamically specify source (input) file names and indicate whether the current content of existing generations must be retained or deleted.

Table 175 CTBDBVCG EXEC Parameters

Parameter

Description

DIMOD

Prefix of the third qualifier of the name of the source (input) Database Variable Basic Data file

DIVAR

Prefix of the third qualifier of the name of the source (input) Database Variable Generation Data file

DIGRP

Prefix of the third qualifier of the name of the source (input) Group file

COPY

Valid values are:

  • Y (Yes) – Retain current contents of existing generations. Default.

  • N (No) – Delete current contents, if any, of existing generations.

Parameters can also be supplied using DD statement SYSIN. The following parameters are mandatory:

Table 176 CTBDBVCG SYSIN Parameters

Parameter

Description

GROUP

Group name (or prefix) of variables to be affected. A group name prefix can be specified only if parameter VARIABLE contains an asterisk (*).

Copy
GROUP—INV

Variables of group INV are changed.

Copy
GROUP—INV*

Variables of all groups that begin with INV (for example, INV, INVENTORY, INVESTMENTS) are changed.

To change the number of variables for all groups, the SYSIN input file must be empty (and no GROUP or VARIABLE names are specified).

Parameter GROUP can be specified only if an asterisk (*) is specified in parameter VARIABLE.

VARIABLE

Variable name (or prefix) of variables whose number of generations is changed.

GROUP=INV

VARIABLE=TOT
Variable TOT of group INV is changed.

GROUP=INV TOT

VARIABLE=TOT*
Variables of group INV that begin with TOT (for example, TOT, TOTAL, TOT01, TOT02) are changed.

NUMGEN

New number of generations to be specified for the variable. If not specified, NUMGEN is set to the default number of generations in System Variable SYSDBVARGENS.

Activating the CTBDBVCG Utility

Figure 64 CTBDBVCG Activation

Copy
//  EXEC CTBDBVCG,DIMOD=mod,DIVAR=var,DIGRP=grp,COPY=YES|NO
//SYSIN  DD *
  GROUP=group
  VARIABLE=variable
  NUMGEN=new-maximum-#-of-generations
//

CTBDBVCG Return Codes

Table 177 CTBDBVCG Return Codes

Code

Description

0

Operation performed successfully

other

Execution error, operation failed

Example for CTBDBVCG

Figure 65 CTBDBVCG – Example

Copy
//    EXEC  CTBDBVCG,DIMOD=MGMT,DIVAR=ACTG,DIGRP=TAX,COPY=YES
//SYSIN  DD *
  GROUP=BONDS
  VARIABLE=COST*
  NUMGEN=24
//

CTBDBVCP – Copy Variables or Groups to another File

The CTBDBVCP utility copies the contents of specified group or variable files (meaning, data from source files) to another set of group or variable files (meaning, target files). All relevant aspects of the variables are copied, including definitions, generations and group information.

The sizes of the source and target files can differ. Therefore, the CTBDBVCP utility is useful for increasing the size of variable files. Usually, this utility copies variables from source files to larger target files.

Copying variables is composed of the following stages:

  • Create and format a new set of group or variable files (target files).

  • Copy the data from the source files to the newly created target group or variable files.

  • Delete the source files.

It is possible to copy all variables, groups of variables (with a common group name prefix), or one or more variables of the same group (with a common variable name prefix) in one activation of the CTBDBVCP utility.

CTBDBVCP Parameters

The following parameters can be specified in the EXEC statement that invokes the CTBDBVCP JCL procedure. These parameters dynamically specify the prefix of the third qualifier for the source and destination files listed below:

Table 178 CTBDBVCP EXEC Parameters

Parameter

Description

DIMOD

Source (input) Database Variable Basic Data file

DIVAR

Source (input) Database Variable Generation Data file

DIGRP

Source (input) Group file

At least one of the above parameters must be specified. For each input file specified, the parameter (below) for the corresponding output file must also be specified.

DOMOD

Destination (output) Database Variable Basic file

DOVAR

Destination (output) Database Variable Generation file

DOGRP

Destination (output) Group file

REPLACE

Flag that indicates if the source variable overwrites an existing variable of the same name in the target. Optional.

  • YES – Overwrite the target variable. Default.

  • NO – Do not overwrite the target variable.

COPY

Flag that indicates whether entire records or only variables are copied. Optional.

  • YES – Copy entire records from the Group file.

  • NO – Copy only variables. Default.

Parameters can also be supplied using DD statement SYSIN. Only one parameter can be specified on each line.

Table 179 CTBDBVCP SYSIN Parameters

Parameter

Description

GROUP

Group name (or prefix) of variables to be copied. Mandatory. A group name prefix can be specified only if parameter VARIABLE contains an *.

Copy
INV 


Variables of group INV are copied. Mandatory.

Copy
INV* 


Variables of all groups that begin with INV (for example, INV, INVENTORY, INVESTMENTS) are copied.

Parameter GROUP can be specified only if ‘*’ is specified in parameter VARIABLE.

VARIABLE

Variable name (or prefix) to be copied.

Copy
GROUP=INV VARIABLE=TOT


Variable TOT of group INV is copied.

Copy
GROUP=INV VARIABLE=TOT*


Variables of group INV that begin with TOT (for example, TOT, TOTAL, TOT01, TOT02) are copied.

NUMGEN

Number of generations to be created for the variable during the copy. If not specified, the number matches the source variable’s number of generations. Do not specify more than the number of existing generations.

FROMGEN

Most recent generation to copy from the source to the target. If FROMGEN is not specified, Control-M/Analyzer begins copying with the current (most recent) source generation.

TOGEN

Oldest generation to copy from the source to the target. If TOGEN is not specified, Control-M/Analyzer. Copies successively older generations until the number of generations copied equals the existing value of TOGEN – FROMGEN + 1.

GROUP=INV

VARIABLE=TOT

NUMGEN=20

FROMGEN=5

TOGEN=10

Assume the source variable has at least 10 generations.

The target variable can have a maximum of 20 generations. The first six generations of the target variable contain the values of the 5th through 10th generations of the source variable.

Activating the CTBDBVCP Utility

Copy
// EXEC CTBDBVCP [DIMOD, DIVAR, DIGRP, DOMOD, DOVAR, DOTRP, 
REPLACE=YES|NO, COPY=YES|NO]

CTBDBVCP Return Codes

Table 180 CTBDBVCP Return Codes

Code

Description

0

Copy operation performed successfully

other

Descriptive execution error, copy operation failed

Example for CTBDBVCP

Figure 66 CTBDBVCP – Example

Copy
//      EXEC CTBDBVCP,DIMOD=MOD,DIVAR=VAR,DIGRP=GRP,
//      DOMOD=TARGMOD,DOVAR=TARGVAR,DOGRP=TARGGRP
//  SYSIN DD*
  GROUP=CURRENCY
  VARIABLE=TOT*
//

For additional information, see sample member JOBDBVCP in the JCL library.

CTBDBVDL – Delete Variables or Groups from Variable or Group Files

The CTBDVBDL utility deletes specified records from Control-M/Analyzer Database Variable files. Mandatory.

The CTBDVBDL utility cannot be run while any online user is using the Database Variable Definition Facility (screen BV).

CTBDBVDL Parameters

The following parameters can be specified in the EXEC statement that invokes the CTBDBVDL JCL procedure. These parameters provide dynamic specification of source and destination file names:

Table 181 CTBDBVDL EXEC Parameters

Parameter

Description

DMOD

Prefix of the third qualifier of the name of the Database Variable Basic file

DVAR

Prefix of the third qualifier of the name of the Database Variable Generation file. Mandatory.

DGRP

Prefix of the third qualifier of the name of the Group file. Mandatory.

DELGR

Flag that indicates if the entire group is deleted. Valid values are:

  • Y (Yes) – Delete the entire group if no variables exist for this group.

  • N (No) – Do not delete the entire group. Default.

Parameters can also be supplied using DD statement SYSIN. Only one parameter can be specified on each line.

Table 182 CTBDBVDL SYSIN Parameters

Parameter

Description

GROUP

Group name (or prefix) of variables to be deleted. A group name prefix can be specified only if parameter VARIABLE contains an *.

GROUP=INV Variables of group INV are deleted.

GROUP=INV* Variables of all groups that begin with INV (for example, INV, INVENTORY, INVESTMENTS) are deleted.

GROUP=* cannot be specified.

VARIABLE

Variable name (or prefix) to be deleted

Parameter VARIABLE can be specified only if ‘*' is not specified for parameter GROUP.

GROUP=INVVARIABLE=TOT
Variable TOT of group INV is deleted.

VARIABLE=TOT*
Variables of group INV that begin with TOT (for example, TOT, TOTAL, TOT01, TOT02) are deleted.

Activating the CTBDBVDL Utility

Copy
// EXEC CTBDBVDL

CTBDBVDL Return Codes

Table 183 CTBDBVDL Return Codes

Code

Description

0

Operation performed successfully

other

Operation failed

Example for CTBDBVDL

Figure 67 CTBDBVDL – Example

Copy
// EXEC CTBDBVDL,DMOD=MOD,DVAR=VAR,DGRP=GRP,DELGR=YES
// SYSIN DD *
  GROUP=CURRENCY
  VARIABLE=TOT*
//

For additional information, see sample member JOBDBVDL in the JCL library.

CTBDBVIG – Check the Integrity of Variable or Group Files

The CTBDBVIG utility checks the integrity of the Database Variable Basic and Generation files. The utility reports errors that are detected in the logical organization of these files. Optionally, CTBDBVIG corrects errors that are detected. File integrity errors are listed in the sysout of the job.

CTBDBVIG Parameters

You can specify the following parameters in the EXEC statement that invokes the CTBDBVIG JCL procedure:

Table 184 CTBDBVIG EXEC Parameters

Parameter

Description

ACT

Flag that indicates if integrity errors are corrected. Valid values are:

  • R – Report errors, but do not correct them. Default.

  • W – Report errors and correct them.

Index file integrity is not checked. Therefore, after running the CTBDBVIG utility, run the JOBBDBM and JOBBDBV jobs to rebuild the index files according to the corrected state of the data file. You should first run the CTBDBVIG utility without requesting corrections (with ACT set to R) and make a backup copy of Database variable files before running the CTBDBFIG utility with ACT set to W.

Activating the CTBDBVIG Utility

Copy
// EXEC CTBDBVIG DMOD=dmod,DVAR=dvar,DGRP=dgrp[,DELGR=YES|NO]

CTBDBVIG Return Codes

Table 185 CTBDBVIG Return Codes

Code

Description

0

Operation performed successfully

other

Operation failed

Example for CTBDBVIG

Copy
// EXEC CTBDBVIG,ACT=R

CTBFRM – Compress the Active Balancing File

The CTBFRM utility compresses the Active Balancing file. The utility usually runs as part of the New Day procedure before potential missions are placed as entries in the Active Balancing file. The utility can also be run as a stand-alone job when parameter FORCE is set to Y.

The utility deletes entries from the Active Balancing file that are no longer processed by Control-M/Analyzer. The Active Balancing file is then compressed.

A backup of the Active Balancing file is created automatically by this utility.

CTBFRM Parameters

Table 186 shows the values that are valid for the parameters specified in the EXEC statement that invokes the CTBFRM JCL procedure.

Table 186 CTBFRM Parameters

Parameter

Valid Values

DBABFB

Third qualifier of the Active Balancing file name. Mandatory.

Default: ABF

DBBKPB

Third qualifier of backup file name. Mandatory.

Default: ABFBKP

FORCE

Indicates whether the utility is being run in stand-alone mode (forced) or being invoked by the New Day procedure. Optional.

  • Y (Yes) – The utility is being run in stand-alone mode without checking dates in member CTBDATE in the Control-M/Analyzer PARM library.

  • N (No) – The utility is being invoked by the Control-M/Analyzer New Day procedure. Default.

Activating the CTBFRM Utility

Copy
// EXEC CTBFRM,DATABFB=balfile,DTBBKPB=backup file,FORCE={Y|N}

CTBFRM Return Codes

Table 187 CTBFRM Return Codes

Code

Description

0

Operation performed successfully

other

Operation failed

Example for CTBFRM

Copy
// EXEC CTBFRM,FORCE=N,DBABFB=ABF,DBBKPB=ABFBKP

For additional information, see sample member JOBFRM in the JCL library.

CTBJAFCP – Copies Entries in Rule Activity or Report Files

The CTBJAFCP utility copies invocation and report entries to other Rule Activity and/or Report files.

CTBJAFCP Parameters

Table 188 CTBJAFCP Parameter

Parameter

Description

FILE

File to be copied. Mandatory.

JAF

Only the Rule Activity file is copied.

REP

Only the Report file is copied.

ALL

Both the Rule Activity file and corresponding reports from the Report file are copied.

The following parameters can be specified in the EXEC statement that invokes the CTBJAFCP JCL procedure:

Table 189 CTBJAFCP EXEC Parameter

Parameter

Description

DBJAFI

Prefix of the third qualifier of the source (input) Rule Activity file name.

DBREPI

Prefix of the third qualifier of the source (input) Report file name.

DBJAFO

Prefix of the third qualifier of the destination (output) Rule Activity file name.

DBREPO

Prefix of the third qualifier of the destination (output) Report file name.

INCLUDE / EXCLUDE Statements (CTBJAFCP)

INCLUDE / EXCLUDE statements are supplied using DD statement SYSIN. The suffix * is permitted at the end of any of these parameters. * represents any number of characters (including no characters).

The scope of the copy can be limited by one or more INCLUDE / EXCLUDE statements. Each INCLUDE / EXCLUDE statement contains job name prefixes that limit the entries that are copied. If one or more INCLUDE statements are specified, only entries specified in the INCLUDE statements are copied. If one or more EXCLUDE statements are specified, the entries specified in the EXCLUDE statements are not copied. There is an OR relationship between multiple INCLUDE statements and between multiple EXCLUDE statements.

Each INCLUDE / EXCLUDE statement must be listed on a separate line.

Parameter JOBNAME can be specified in INCLUDE / EXCLUDE statements. This parameter represents the job name.

If the SYSIN file contains no INCLUDE / EXCLUDE statements, all records from the source file are copied.

Activating the CTBJAFCP Utility

Copy
// EXEC CTBJAFCP FILE={JAF|REP|ALL}
// SYSIN DD       *
//

CTBJAFCP Return Codes

Table 190 CTBJAFCP Return Codes

Code

Description

8

Syntax error in the input parameters stream (SYSIN cards)

12

Insufficient memory to run the utility

16

Unable to open a Control-M/Analyzer Database file

100+

Internal error

108

ENQ of the Rule Activity and Report files failed. Run the utility again later.

Example for CTBJAFCP

Figure 68 CTBJAFCP – Example

Copy
// EXEC CTBJAFCP,FILE=ALL,DBJAFI=JAF,DBREPI=REP,DBJAFO=JAFNEW,DBREPO=REPNEW
// SYSIN  DD *
  INCLUDE JOB2*
  EXCLUDE JOB22
  EXCLUDE JOB23*
//

To copy the files, perform the following steps:

  1. Allocate a new set of Rule Activity and Report files using the CTBCRDF utility.

  2. Copy the existing files, or a portion of these files (for example, only relatively new invocations), into the new files using the CTBJAFCP utility.

  3. Delete the old files.

  4. Rename the new files to the names of the original files.

For additional information, see sample member JOBJAFCP in the JCL library.

CTBJAFDL – Deletes Entries from Rule Activity or Report Files

The CTBJAFDL utility cleans unnecessary entries from the Rule Activity file and/or the Report file.

CTBJAFDL Parameters

The following parameters can be specified in the EXEC statement that invokes the CTBJAFDL JCL procedure:

Table 191 CTBJAFDL EXEC Parameters

Parameter

Description

DBJAFB

Prefix of the third qualifier of the Rule Activity file name

DBREPB

Prefix of the third qualifier of the Report file name

PRINT

Flag that indicates if deleted entries are printed

PRINT

Information about deleted entries is printed

NOPRINT

Information about deleted entries is not printed

The following parameters are supplied using DD statement SYSIN. The suffix * is permitted at the end of any of these parameters. * represents any number of characters (including no characters).

Table 192 CTBJAFDL SYSIN Parameters

Parameter

Description

DAYS

Non-negative number of days to retain entries in the Rule Activity file or Report file. To delete all entries, specify 0. Mandatory.

INCLUDE or EXCLUDE

The scope of the deletion can be limited by one or more INCLUDE or EXCLUDE statements. Each INCLUDE or EXCLUDE statement contains job name prefixes that limit the entries that are deleted. If one or more INCLUDE statements are specified, only entries specified in the INCLUDE statements are deleted. If one or more EXCLUDE statements are specified, the entries specified in the EXCLUDE statements are not deleted. There is an OR relationship between multiple INCLUDE statements and between multiple EXCLUDE statements.

Parameter JOBNAME can be specified in INCLUDE or EXCLUDE statements. This parameter represents the job name.

Each INCLUDE or EXCLUDE statement must be listed on a separate line.

Activating the CTBJAFDL Utility

Figure 69 CTBJAFDL Activation

Copy
// EXEC  CTBJAFDL,DBJAFB=jaf prefix,DBREPB=rep prefix,PRINT=PRINT|NOPRINT
// SYSIN  DD *
 DAYS n
 [INCLUDE {PARAMETERS}]
 [EXCLUDE {PARAMETERS}]
//

CTBJAFDL Return Codes

Table 193 CTBJAFDL Return Codes

Code

Description

0

Operation performed successfully.

104

ENQ of the Rule Activity and Report files failed. Run the utility again later.

other

Operation failed.

Example for CTBJAFDL

Figure 70 CTBJAFDL – Example

Copy
// EXEC CTBJAFDL,DBJAFB=JAF,DBREPB=REP,PRINT=PRINT
// SYSIN DD *
  DAYS 4
  INCLUDE JOB2*
  EXCLUDE JOB22
  EXCLUDE JOB23*
//

CTBJAFIG – Check the Integrity of Rule Activity or Report Files

The CTBJAFIG utility checks the integrity of Rule Activity and Report files. The utility reports errors detected in the logical organization of these files. If requested, utility CTBJAFIG corrects the errors that are detected. File integrity errors are listed in the sysout of the job.

CTBJAFIG Parameters

The following parameters can be specified in the EXEC statement that invokes the CTBJAFIG JCL procedure:

Table 194 CTBJAFIG EXEC Parameters

Parameter

Description

FILE

File to be checked or corrected. Mandatory. Valid values are

  • JAF – Rule Activity file. Default.

  • REP – Report file

  • BTH – Both of the files (without logical links)

  • ALL – Both the Job Activity and Report files (and their logical links)

C

Flag to indicate if integrity errors must be corrected. Optional. Valid values are:

  • Y (Yes) – Correction is requested

  • N (No) – Correction is not requested. Default.

Index file integrity is not checked. Therefore, after running the CTBJAFIG utility with option C set to Y (Yes), run jobs JOBBJAF and JOBBREP to rebuild the index files based on the corrected data file. You should first run the CTBJAFIG utility without requesting correction (C set to N), and be sure to make a backup copy of the files before running the CTBJAFIG utility with C set to Y (Yes).

Activating the CTBJAFIG Utility

Copy
// EXEC CTBJAFIG FILE={JAF|REP|BTH|ALL}[C={Y|N}]

CTBJAFIG Return Codes

Table 195 CTBJAFIG Return Codes

Code

Description

0

Operation performed successfully

other

Operation failed

Example for CTBJAFIG

Copy
//  EXEC CTBJAFIG,FILE=ALL,C=N

For additional information, see sample member JOBJAFIG in the JCL library.

CTBVXRF – Cross-Reference Utility

The CTBVXRF utility produces a report that cross-references database variables and the rules by which they are created and accessed. This utility gives the user more control over rule definition and maintenance.

CTBVXRF Parameters

This utility receives parameters using DD statement DACMD.

All parameters are mandatory. The order of the parameters must be as specified under "Activating the CTBVXRF Utility".

Table 196 CTBVXRF Parameters

Parameter

Description

LIB

Specifies the library that contains the rules that are cross-referenced

RULE

Specifies the rule members to be cross-references. Mask characters * and? are supported.

  • RULE=RUL* – Process all rules (in the library specified in parameter LIB) whose names start with characters RUL.

  • RULE=RUL?BC – Process all rules in the library specified in parameter LIB whose names start with characters RUL followed by any single character, and then followed by characters BC.

SORT

Determines the format and order of the output report. Valid values are:

  • RULE – Output is formatted in chapters, one rule per chapter, sorted by rule name. Variables in the rule are sorted by variable name.

  • VAR – Output is formatted as a list of variables. Each entry is a Database variable that is accessed by one of the specified rules. The list is sorted by Database variable name.

BLOCKS

Specifies the level of detail in the output report. Valid values are:

  • YES – The cross-reference report relates to individual blocks within each rule (meaning,if a Database variable is referenced by two or more blocks of the same rule, the report contains one line for each block).

  • NO – The report contains one reference per Database variable name per rule.

CTBVXRF Report Format

The cross-reference report is formatted according to the SORT parameter, as described above.

Each report line contains the following items:

Table 197 CTBVXRF Report Formats

Format

Description

VARIABLE

Database variable name. The name is printed as it appears in the rule. Variables names referenced in the rule definition that include the AutoEdit symbol are not resolved; these variables are printed with the%% prefix (for example, DB_VAR%%NUM).

If a variable is accessed that is not associated with a group name but the rule definition that accesses the variable does specify a group name, this group name is printed between parentheses as part of the variable name (for example, DB_(CTB_DEMO).VAR).

RULE

Rule name (when parameter SORT is set to VAR)

BLOCK

Block name (when parameter BLOCKS is set to YES)

EXTRACT or SET or USED

Counters indicating the number of times the variable was extracted, set or accessed within a rule.

When BLOCKS is set to YES, only references to the variable within the current block are counted. When BLOCKS is set to NO, all references to the variable within the rule are counted.

Activating the CTBVXRF Utility

Figure 71 provides an example of CTBVXRF activation syntax.

Figure 71 CTBVXRF Activation

Copy
// EXEC CTBVXRF
// DACMD DD *
  LIB=rule-library
  RULE=rule-list
  SORT=sort-option
  BLOCKS=YES/NO
//

When you activate the CTBVXRF utility, you must observe the following rules:

  • Ensure that you do not use ISPF numbers in the DACMD sysin to this utility. Otherwise, the following message is issued:

    CTBA31E- INVALID LINE, "RULE=VALUE" EXPECTED

  • Ensure that you do not specify the name of a library that does not exist. Otherwise, the following message is issued:

    CTB0B7S- Internal error in CTBXMEM

  • Columns 73 to 80 must not contain line numbers. Use the ISPF UNNUM command to remove them.

Examples for CTBVXRF

CTBVXRF Example 1

Figure 72 CTBVXRF – Example 1

Copy
INPUT FOR CROSS REFERENCE REPORT:LIB=CTBP.PROD.RULES
RULE=ARWARN*
SORT=RULE
BLOCKS=YES
   
CONTROL-M/Analyzer-B VERSION 6.3.01  DATABASE VARIABLE CROSS-REFERENCE REPORT 
         TUE MAR 02 2000 16:52:31   PAGE 1
BMC SOFTWARE, INC.
RULES IN CTBP.PROD.RULES (ARWARN*)
                     ************
                     * ARWARN01 *
                     ************
NO DATABASE VARIABLES FOUND.
                     ************
                     * ARWARN02 *
                     ************
NO DATABASE VARIABLES FOUND.
                     ************
                     * ARWARN03 *
                     ************
NO DATABASE VARIABLES FOUND.
                     ************
                     * ARWARN04 *
                     ************
          VARIABLE                    | BLOCK    EXTRACT    SET    USED
--------------------------------------+---------------------------------
DB_(INTRAC).COST%%D                   | ENDJOB               1
DB_(INTRAC).INVAMT%%D                 | ENDJOB               1
DB_(INTRAC).PROCESS_MONTH             | CHKDETL                      1
--------------------------------------+---------------------------------
                     ************
                     * ARWARN05 *
                     ************
          VARIABLE                    | BLOCK    EXTRACT    SET    USED
--------------------------------------+---------------------------------
DB_(INTRAC).COST01                    | ACCUMSLS                     1
DB_(INTRAC).COST02                    | ACCUMSLS                     1
DB_(INTRAC).COST03                    | ACCUMSLS                     1
DB_(INTRAC).INVAMT01                  | ACCUMSLS                     1
DB_(INTRAC).INVAMT02                  | ACCUMSLS                     1
DB_(INTRAC).INVAMT03                  | ACCUMSLS                     1
--------------------------------------+---------------------------------
                     ************
                     * ARWARN06 *
                     ************
NO DATABASE VARIABLES FOUND
                     ************
                     * ARWARN4A *
                     ************
          VARIABLE                    | BLOCK    EXTRACT    SET    USED
--------------------------------------+---------------------------------
DB_(INTRAC).COST%%D                   | ENDJOB               1
DB_(INTRAC).INVAMT%%D                 | ENDJOB               1
DB_(INTRAC).PROCESS_MONTH             | CHKDETL                      1
------------------------------------------------------------------------
END OF REPORT

Figure 73 CTBVXRF – Example 2

Copy
INPUT FOR CROSS REFERENCE REPORT:
LIB=CTBP.PROD.RULES
RULE=ARWARN*
SORT=VAR
BLOCKS=YES
   
CONTROL-M/Analyzer-B VERSION 6.3.01  DATABASE VARIABLE CROSS-REFERENCE REPORT 
                TUE MAR 02 2000 16:53:19   PAGE 1
BMC SOFTWARE, INC.
RULES IN CTBP.PROD.RULES (ARWARN*)
   
          VARIABLE                    | RULE      BLOCK    EXTRACT    SET    USED
--------------------------------------+-------------------  ----------------------
DB_(INTRAC).COST%%D                   | ARWARN04  ENDJOB               1
DB_(INTRAC).COST%%D                   | ARWARN4A  ENDJOB               1
DB_(INTRAC).COST01                    | ARWARN05  ACCUMSLS                     1
DB_(INTRAC).COST02                    | ARWARN05  ACCUMSLS                     1
DB_(INTRAC).COST03                    | ARWARN05  ACCUMSLS                     1
DB_(INTRAC).INVAMT%%D                 | ARWARN04  ENDJOB               1
DB_(INTRAC).INVAMT%%D                 | ARWARN4A  ENDJOB               1
DB_(INTRAC).INVAMT01                  | ARWARN05  ACCUMSLS                     1
DB_(INTRAC).INVAMT02                  | ARWARN05  ACCUMSLS                     1
DB_(INTRAC).INVAMT03                  | ARWARN05  ACCUMSLS                     1
DB_(INTRAC).PROCESS_MONTH             | ARWARN04  CHKDETL                      1
DB_(INTRAC).PROCESS_MONTH             | ARWARN4A  CHKDETL                      1
--------------------------------------+------------------------------------------
   
END OF REPORT