The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.
For a list of other such plugins, see the Pipeline Steps Reference page.
BMC DevOps for CFA Plugin
: BMC DevOps for CFAserver
String
port
String
user
String
jclContent
String
chkfreq
String
jobCard
String
acctno
String
thresh
String
sortby
String
pswd
String
prilog
String
cfaLoadLibs
lib
String
cfaSldsLibs
sldsname
String
sldsver
String
sldsunit
String
sldsvolser
String
cfaDliLibs
dliname
String
dliver
String
dliunit
String
dlivolser
String
cfaJobnames
jobname
String
cfaReconSets
recon1
String
recon2
String
recon3
String
goodRC
String
bmcSlds
You can use the SLDS keyword on the ANALYZE control statement to identify explicitly an input log data set to use as input to the analysis process. SLDS=(dataSetName,Rvr, unit,volser) If you want CFA to read multiple log data sets, specify multiple instances of the SLDS keyword.
Example: IMSA is an IMS version 14.1 system and creates generations of SLDSs that use the naming convention imsid.SLDS.Ddate.GENnnn. The SLDSs are cataloged. To analyze log records that IMSA wrote to generations 10 through 12 on March 29, 2015, specify the following keywords on the ANALYZE control statement:
SLDS=(IMSA.SLDS.D2008088.GEN010, R141)
SLDS=(IMSA.SLDS.D2008088.GEN011, R141)
SLDS=(IMSA.SLDS.D2008088.GEN012, R141)
boolean
bmcDb2log
You can use the DB2LOG keyword on the ANALYZE control statement to identify a DB2 log data set that was created by a DB2 subsystem.
Note: If you specify the DB2LOG keyword, do not specify the DB2BSDS keyword.
boolean
db2log
String
db2bsds
String
limit
String
skip
String
maxlogs
If you specify a value from 1 through 999, Log Analyzer stops reading log data sets after it reaches the specified number of log data sets. If Log Analyzer does not read other log data sets because the specified limit was reached, a warning message indicates the number of log data sets that were not read.
If you want Log Analyzer to read all log data sets, specify MAXLOGS=999.
The default is MAXLOGS=100 (Log Analyzer reads a maximum of 100 log data sets).
String
bmcDb2bsds
You can use the DB2BSDS keyword on the ANALYZE control statement to identify a DB2 bootstrap data set (BSDS).
Specify the fully qualified data set name. This name should refer to a VSAM key-sequenced data set (KSDS).
Do not specify the name of a BSDS archive copy, which is not a VSAM KSDS. BSDS cannot be a TAPE dataset.
Note:
boolean
bmcLimit
You can use the LIMIT keyword (or the LIM abbreviation) on the ANALYZE control statement to set a limit on the number (1 through 9999999999) of log records to process from an input log data set.
Note:
boolean
bmcSkip
You can use the SKIP keyword on the ANALYZE control statement to specify a number (1 through 9999999999) of log records in an input log data set to skip before CFA begins to process records.
The default is SKIP=0, which skips no records.
Note:
If you specify the SKIP keyword, you must specify one SLDS keyword. The SLDS keyword is required, and multiple SLDS keywords are not allowed.
boolean
bmcActiveOlds
boolean
bmcImsid
You can use the IMSID keyword on the ANALYZE control statement to specify one or more IMSIDs.
If you do not check this option,then the the default IMSID=ALL will be taken and all log records for all IMS systems that are associated with the input RECON data set (or data sets) will be considered.
Note:
If you specify the SLDS keyword, you cannot specify the IMSID keyword. The IMSID keyword applies only if CFA is reading RECON data sets to determine which log data sets to process.
boolean
bmcDlilog
You can use the DLILOG keyword on the ANALYZE control statement to identify explicitly an input dli log data set to use as input to the analysis process.
Specify the keyword values as follows:
DLILOG=(dataSetName,Rnn)
DLILOG=(dataSetName,Rvr,unit,volser)
Notes:
boolean
bmcMaxlogs
Use this keyword when you are using implicit specification of log data sets and Log Analyzer is reading RECON data sets to determine which log data sets to process. In this case, the number of log data sets to be processed is unknown. The MAXLOGS keyword can help you prevent a problem that could result from processing an excessive number of log data sets.
The MAXLOGS keyword works differently, depending on how you specify the value:
boolean
bmcJobname
You can use the JOBNAME keyword on the ANALYZE control statement to specify one or more JOBNAMEs. Each JOBNAME (one to eight characters) identifies a Job name. Log Analyzer uses the JOBNAME when determining which dli log data sets to use as input.
To process log records for all Job names that are associated with the input RECON data set (or data sets), specify JOBNAME=ALL.
If you omit the JOBNAME sub-keyword, Log Analyzer uses the default value ALL.
Note:
boolean
cfaImsids
imsid
String
bmcRecon
You can use the RECON keyword on the ANALYZE control statement to specify the names of a set of RECON data sets to examine during the CFA job.
If you want CFA to examine multiple sets of RECON data sets, you must specify each set with a separate RECON keyword.
If you specify the RECON keyword, your user ID must have Security Access Facility (SAF) READ access to the RECON data sets.
You can specify from one to three data set names. One of the specified data set names must be designated as COPY1 by IMS.
Example:
The RECON data sets for the IMSA system are named IMSA.RECON1 and IMSA.RECON2, and the RECON data sets for the IMSB system are named IMSB.RECON1 and IMSB.RECON2. To examine IMSA and IMSB RECON data sets in the CFA job, specify the following keywords on the ANALYZE control statement:
RECON=(IMSA.RECON1, IMSA.RECON2)
RECON=(IMSB.RECON1, IMSB.RECON2)
Note:
If you specify the RECON keyword, you must specify the INTERVAL control statement with a START time value and a STOP time value.
boolean
bmcTimezone
boolean
bmcStartInterval
You can use the START keyword on the INTERVAL control statement for the following purposes:
boolean
bmcStopInterval
You can use the STOP keyword on the INTERVAL control statement for the following purposes:
� Specify the end of a range of log records to identify as candidates for the record selection process
� Control the end of range of log data sets to allocate from RECON information
� Reduce the overall number of log records that are selected from input SLDS or extract files
boolean
start
value
String
startDate
String
startlogSeq
String
stop
value
String
stopDate
String
stoplogSeq
String
tz
value
String
timezoneoffset
String
jobInclude
String
jobExclude
String
psbInclude
String
psbExclude
String
maxlogsRc
If you specify a value from 1 through 999 followed by literal R and a return code (08 through 99), Log Analyzer issues the specified return code and terminates the job step if more than the specified number of log data sets would be read. Log Analyzer issues the return code at the conclusion of the RECON analysis phase without reading any input log data sets.
Example:
If you want Log Analyzer to issue return code 16 and terminate the job step if more than 10 log data sets would be read, specify the following keyword on the ANALYZE control statement:
MAXLOGS=(10,R16)
String
maxlogsAbend
If you specify a value from 1 through 999 followed by an abend code (1 through 4095), Log Analyzer issues a user abend code and terminates the job step if more than the specified number of log data sets would be read. Log Analyzer issues the user abend at the conclusion of the RECON analysis phase without reading any input log data sets.
Example:
If you want Log Analyzer to issue a user abend, with abend code U4000, if more than 120 log data sets would be read, specify the following keyword on the ANALYZE control statement:
MAXLOGS=(120,4000)
String
bmcJobInc
boolean
bmcJobExc
boolean
bmcPsbInc
boolean
bmcPsbExc
boolean
bmcChkfreq
boolean
bmcThresh
boolean
bmcPrilog
You can use the PRILOG keyword on the ANALYZE control statement to specify the logs type associated with the input RECON data set (or data sets) to use as input to the analysis process.
You can select one of the following values:
boolean
bmcAppcheck
boolean
bmcAll
boolean
bmcLsec
boolean
chkfreqval
String
bmcPlanInc
boolean
planInclude
String
bmcPlanExc
boolean
planExclude
String
bmcSortby
boolean
bmcCsv
boolean
bmcFullreport
boolean
Please submit your feedback about this page through this quick form.
Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?
See existing feedback here.