JCL to generate a deployment analysis report
The following JCL produces a cold start compare report, where the candidate resource definitions are stored in a combination of CSD file and CICSPlex® SM data repository. A version of this JCL (with additional comments and examples) is supplied in the member CCVX0006 of the sample library SCCVSAMP.
//CCVJOB JOB your job statement information
//STEP EXEC PGM=CCVBMAIN
//STEPLIB DD DISP=SHR,DSN=ccvhlq.SCCVAlang 1
// DD DISP=SHR,DSN=ccvhlq.
SCCVLINK
//CCVPRINT DD SYSOUT=*
//CCVREPRT DD SYSOUT=*
//CCVFLTEX DD SYSOUT=* 2
//CCVPARMS DD * 3
CONNECT IPADDRESS=ip_address,PORT=ip_port_number
DEPLOY PHASE=COLLECT,
REPORTSET=1,
TYPE=CANDIDATES,
CONFIGURATION=PRODACSD,
GRPLIST=DFHLIST,
GRPLIST=START*,
LOCALSYSID=PRDA,
PHASE=COLLECT,
REPORTSET=1,
TYPE=CANDIDATES,
CONFIGURATION=PRODAPLX,
SCOPE=PRODAPLX,
PHASE=COLLECT,
REPORTSET=2,
TYPE=RUNTIME,
CONFIGURATION=PRODAPLX,
SCOPE=PRODAPLX,
PHASE=REPORT,
TYPE=COLDSTARTCOMPARE,
FILTERDATASET=MYID.CCV.DAFILTER 2
/*
- 1
- The STEPLIB concatenation must contain the CICS® Configuration
Manager
national language support (NLS) load module library
SCCVAlang and the program load module library. If you connect to the CICS Configuration Manager server via an authenticated port, you must also enable PassTicket processing. For details, see Optional: Enable PassTicket processing.
- 2
- If you specify the optional ddname CCVFLTEX in your report JCL, the job output includes a filter file that contains a filter statement for each item in the generated report. To suppress an item from future reports, copy and paste the corresponding filter statement from this file to your own filter file. For details, see Filtering resource definitions from deployment analysis reports.
- 3
- The CCVPARMS input stream must consist of a CONNECT statement
followed by a DEPLOY statement. The CONNECT statement identifies the CICS Configuration
Manager server that will
prepare the report. The DEPLOY statement specifies the details of
the report, consisting of one or more collection phases and one report
phase. This example contains three collection phases:
- Collects candidate resource definitions from a CSD file. The CONFIGURATION parameter for this collection phase specifies a CICS configuration that refers to a CSD file. The two GRPLIST parameters specify lists in the CSD file.
- Collects candidate resource definitions from a CICSPlex SM data repository. The CONFIGURATION parameter for this collection phase specifies a CICS configuration that refers to a context. The SCOPE parameter specifies the target scope.
- Collects runtime resource definitions from an active CICS region. The CONFIGURATION parameter for
this collection phase specifies a CICS configuration
that refers to a context (the same CICS configuration
as the previous collection phase).
This CONFIGURATION parameter, together with the presence of the SCOPE parameter, instructs CICS Configuration Manager to collect the runtime resource definitions via the CICSPlex SM agent. If the CONFIGURATION parameter had specified a CICS configuration that referred to a CSD file, and you specified a CONNECTION parameter instead of a SCOPE parameter, then CICS Configuration Manager would collect the runtime resource definitions via the CICS Configuration Manager agent.
The REPORTSET=1 parameters on the first two collection phases instruct CICS Configuration Manager to combine the candidate resource definitions from the CSD file and the CICSPlex SM data repository into a single set.
For details of the syntax of the CONNECT command, see CONNECT.
For details of the syntax of the DEPLOY command, see DEPLOY.
For additional general information on writing JCL for the batch command program, see JCL to invoke the batch command program.