There are several runtime parameters that you can pass to the file maintenance utility at its startup, all of which are optional. You can specify these parameters using any combination of the following methods:
The file maintenance utility searches for startup parameters, and processes them, in the following way:
The runtime parameters enable you to:
The runtime parameters are described in detail as follows:
If you omit this option, you must specify the CBKCNTL DD statement in the batch job step of the file maintenance utility. The file maintenance utility uses the data set name specified on the CBKCNTL DD statement to perform a reverse lookup of the control file table (CBKCFTBL) to find the corresponding CICS region applid.
If you omit both APPLID and the CBKCNTL DD statement, the job step terminates with an error message (see message CBKxx7010 ).
Note that if the allocated buffer is too small for the command being processed, the command fails and the file maintenance utility issues message CBKxx7310. For example, if you issue a LIST command with only the generic character as the identifier, the volume of data returned could be quite large if the region control file contains multiple object records of the specified resource type.
When the file maintenance utility is terminating, its final step is to compare the value of the return code with the value of the MSGLEVEL option. If the return code is greater than or equal to MSGLEVEL, the job step is terminated with abend code U3502 and takes a dump. Thus by default, any return code of 16 or greater causes the utility to abend and produce a dump.
MSGLEVEL is intended primarily for support and diagnosis purposes. For example, if Technical Support need a dump when you have a condition where the utility is terminating with return code 8, you can specify EXEC PGM=CBKFMAIN,PARM='MSGLEVEL(8)', and run the job again to force an abend and a dump.