OPTIONS

The OPTIONS instruction gives you a choice of process options; you can specify options to be used when performing PIF requests. You can use these options to automatically resolve dependencies when adding current plan or long-term plan occurrences with INSERT. 
ACTION=OPTIONS,ADOICHK=adoichk,
                       ADVERS=advers,
                       BL=batchl,
                       BLPRT=blprt,
                       CPDEPR=cpdepr,
                       ERROR=error,
                       LTDEPR=ltdepr,
                       LTP=ltp,
                       RETRY=number_of_retries;
adoichk
Y or N(char(1)). Specify whether or not you want AD/OI consistency checks to be made every time an application is deleted or modified. Consistency checks involve looking in the application description data base for matches for all the operator instructions in the application. Any operator instructions without match are deleted. Default: N.
advers
Y or N (char(1)).

When Y is specified, in all the cases in which the running of the requested command impacts the AD database for applications having more than one validity period, BCIT ensures that the resulting different versions of the application have consecutive validity intervals, preserving the same logic used by the ISPF dialogs.

Note: Mixed use of ADVERS=Y and ADVERS=N is not allowed. Before running any BCIT command with ADVERS=Y, you must update the versions affected using the ISPF dialogs ensuring the basic versioning rule is followed. If any ADID has only one version in a given status, its value must be 711231; if there are more versions in a given status, the more recent one must a value of 711231. Default: N.
batchl
Y or N (char(1)). Ask the batchl format.
  • If BL=Y and BLPRT=Y, the commands LIST ADCOM or OICOM produce the following output:
    • AD (OI) statements (in the format that can be used in input to the batch loader utility) are written in the file referenced by the BATCHL DD card. Note that the PREJOBN keyword will never be produced because the BL utility accepts it as an alternative to PREOPNO, which is always supplied for all the predecessors.
    • AD (OI) keys are written in the file referenced by the AD (OI) DD card.
  • If BL=Y and BLPRT=N, only AD and OI keys are written inside their corresponding file (referenced by DD AD or DD OI calls)
  • If BL=Y, the LIST CPOC or CPOPCOM result is written in referenced file (CPOC or CPOP). Default: N
blprt
Y or N (char(1)) write AD or OI keys in AD and OI files if BL=Y and BLPRT=N. Default: Y if BL=Y.
cpdepr
Y or N (char(1)) resolve automatically external dependences (extra application) during an insert of a new occurrence in a current plan. Default: N
error
Y or N (char(1)) when Y is specified, processing of SYSIN statements stops in case of failure. Default: N
ltdepr
Y or N (char(1)) resolve automatically external dependencies (extra application) during an insert of a new occurrence in an long-term plan. Default: N
ltp
Y or N (char(1)). When Y is specified, if INSERT or DELETE actions are requested for resource CPOC and the input arrival time specified or defaulted is later than the current plan end time, the requested action will be performed on the long-term plan. Default: N
number_of_retries
Integer (integer(4)): allowed values from 0 to 9999. Specifies the number of times that BCIT tries to update an operation or occurrence that is being modified by another user, before it ends in error. The default value is 3; the value 0 is replaced by the default 3.