IMPORTANT KNOWLEDGE ARTICLES:

https://community.bmc.com/s/question/0D53n00007aDtMeCAK/controld-backup-mission-not-
flagging-reports-to-backed-up

--------------------------------------------------------------------------------------------------------------------------

I have to create a list of all reports that have been loaded during the last days for a
specific user. So I search the user reports (Active/Migrated) for user = xy and date from
281116 to 011216.
 
Use utility such as CTDUFPRT. Check the manuals for all the available options.
e.g.:
//STEP010  EXEC CTDUFPRT                                  
//DAREPORT DD DSN=dsname,DISP=(NEW,CATLG,DELETE),
//            SPACE=(CYL,(1,1),RLSE)                      
//SYSIN DD *                                              
FILE=ACT                                                  
RECORD=U                                                  
USER=xy                                               
DECFROM=28/11/16                                          
DECTO=01/12/16                                            
PRINTFORM=REPORT                                          
FIELD=JOBNAME                                             
FIELD=REPORT                                              
FIELD=DATE                                                
FIELD=PAGES

JCL Example:

//CTDUFPRT EXEC PGM=CTDUFPRT

 
//STEPLIB  DD DSN=LPL.IOA802IN.PXX.LOAD,DISP=SHR
 
//DAPARM   DD  DSN=LPL.IOA802IN.PXX.PARM,
 
//             DISP=SHR
 
//         DD  DSN=LPL.IOA802IN.PXX.IOAENV,
 
//             DISP=SHR
 
//DAPRINT  DD  SYSOUT=*
 
//DAACT    DD DSN=LPL.CTD802DB.PXX.ACT.E000,DISP=SHR
 
//DAACTI DD DSN=LPL.CTD802DB.PXX.ACTI.E000,DISP=SHR
 
//SYSPRINT DD  SYSOUT=*
 
//DAREPORT DD DSN=<output dsn>,
 
//            DISP=(NEW,CATLG,DELETE),SPACE=(CYL,(1,1),RLSE)
 
//SYSIN DD *
 
  FILE=ACT
 
  RECORD=U
 
  USER=LZ40*
 
  DECFROM=28/11/16
 
  DECTO=01/12/16
 
  PRINTFORM=REPORT
 
  FIELD=JOBNAME
 
  FIELD=REPORT
 
  FIELD=DATE
 
  FIELD=USER
 
  FIELD=PAGES
 
//*

https://community.bmc.com/s/question/0D53n00007aDn09CAC/controldv-export-index-result-to-
dsn

--------------------------------------------------------------------------------------------------------------------------------

1. JCL Job is executed through Scheduler like Control-M/TWS

2. JCL job generates output/reports on job execution completion
3. Define Control-D report decollating mission to process the Job output/reports
 4. You can define identify a character string that is unique to the specific recipient or recipients
(for example, a report header or title). Take note of the line and column ranges of the
identifying strings and create the decollating mission with this information.
5. Control-D report decollating mission should be there in active env before the JCL execution
to process report output in Control-D
6. Once report output is processed by Control-D report decollating mission, the output can be
viewed online, printed and archived using Control-D by respective report recipient.
7. Use report decollating mission parameter DO PRINT to specify which printing mission should
print the user's report. (Print mission should be defined using option M before specifying it in
report decollating mission)

IMP POINTS:

 Define one decollating mission per batch job

 Handle all reports generated by a batch in one decollating mission (One to Many)
 Identify Report Output Where Control-D can find report output, for example, if written to
compressed datasets, which datasets should be decollated. If written to spool, which class or
classes should be searched for the reports is specified.
 Control-D processes the reports when the job enters the output queue.
 Control-D decollates a non-held spool SYSOUT, the SYSOUT is removed from the spool to the
compressed SYSOUT dataset.
 When Control-V decollates a held spool SYSOUT, the SYSOUT is copied from the spool to the
compressed SYSOUT dataset. The original SYSOUT remains on a JES2 spool but is deleted
from a JES3 spool.
 Note: When Control-V decollates a generic job, the SYSOUT is always deleted from the spool.
 ON CLASS decollates all the sysouts of the specified class (held and non-held). (For generic
decollating missions, only the non-held sysouts are processed.)
 At least one ON CLASS statement must be specified for a generic decollating mission. This
class must be defined as a generic class in the Control-V installation parameters. All other
classes are rejected (for a generic job). A generic decollating mission can contain only ON
CLASS statements for generic classes.
 ON DSN decollates all compressed sysouts that meet the selection criteria specified in the ON
DSN field. The selection criteria specified must be valid Compressed Dataset Access Method
(CDAM) control parameters (such as PREFIX, PGMSTEP or PROCSTEP) that can be used for
retrieval.
 If an ON SYSOUT statement is specified and held SYSOUT exists for the job, Control-V reads
all the held SYSOUT and selects output for processing based on the specified selection criteria
in the ON SYSOUT subparameters.
 If an ON SYSOUT statement is specified with an ON CLASS statements, ON SYSOUT
processes non-held output selected by the ON CLASS statements. However, if only an ON
SYSOUT statement is specified, the non-held sysout is ignored.
 Backup missions for the same class should be from longest to shortest retention order.
 print a list of all the output managed by Control D to a file or data set using
CTDUFPRT.
 FTO is the component in Control-D responsible for collecting reports from other
platforms.
 One sysout can have multiple reports.
 A XEROX printer must be defined as XER in member CTDPARM in the IOA PARM library.
  Defining Printer Syntax:
DEFPRTS PRINTER=(PR_NAME,DEST,6000,OPEN, CHUNKSIZE,PR_TYPE,000)
e.g.

 For more information about moving reports to the History file, check out utility
CTDDELRP
 For more information about removing reports from the History file, check out
utility CTDCLHST.
 
PRINT/CDAM PARMS = ALLOCOPT=JOBSDSN1

Combines all Sysout gathered by this mission into one CDAM file.

DO NAME= %%JOBNAME(1,8)

Sets the report name to the first eight characters of the job name for each report.

DO INDEX= JOBNAME_DDNAMES

Creates a special index structure that consists of a primary index named JOBNAME and a sub-index
named DDNAMES. The primary index has a single value comprised of fixed-length fields separated
by blanks, as listed in the next table below.

 Assign Defaults
First define the default parameters for the job. The job defaults apply to all the reports that
you are handling from the batch job. If you want different default values for specific reports
within the job, you can override job defaults with report defaults.

CDAM KA:

1. By default, the CTDPARM member with parameter JB1PREF is used to create CDAMs in
the following format:C900DJ1.JOBSDB.J05768.D2420943.S91.N000500
 2. The other place to use is the PRINT/CDAM PARMS parameter in the Decollation
Definition.
Example: PRINT/CDAM PARMS = PREFIX=C123DJ1
The CDAM will look like: C123DJ1.JOBSDB.J05768.D2420943.S91.N000500

Note: You should have an Alias for the prefixes that will be created.
------------------------------------------------------------------

The BLOCKs parameter in CTDPARM specifies 1000.

ALLOCOPT=JOBSDSN1 is specified in the PRINT/CDAM parms so all sysouts should go to the
same CDAM.

When the CDAM file is initially created the space allocation is not 1000 blocks so lots of small
CDAMS are being created by these generic missions.
CAUSE
Optional - Specific technical discrepancy if known, only if it will help reader determine if the
article applies.
Incorrect setting of parameter EAVUSE#D in CTDPARM
SOLUTION
Numbered list of steps to perform to resolve issue.
The problem is parameter EAVUSE#D=OPT in CTDPARM. After changign it to NO and re-cycling
the CDAM subsystem (IOATERM/IOASINIT) the CDAM datasets went back to being 1000 blocks
and multi-job.
Noted that the dataset attributes have changed too, with OPT they have the SMS extended
attribute flag set to OPT and this is blank when EAVUSE#D=NO.

This is the default for version 9.0.00 and above.

Please note the following in the User Guide:

The EAVUSE parameter initiates the special primary space calculation for the CDAM files. The size
of the primary space is calculated to include the entire decollated sysout. The special primary
space calculation is not initiated if the BLOCKS parameter is explicitly specified for the
corresponding ON CLASS or ON TRNCLASS block.

As a workaround you can specify BLOCKS=1000 in the mission until you can make the change to
the EAVUSE parameter.
-----------------------------------------------
Figure 11 Default Parameter Lines
DEF COPIES LVL USER DEST MAX COPIES
===========================================================================

If there are any unidentified pages, you can assign them to recipient UNIDENT (defined during Phase
2). The UNIDENT recipient can act as a central collection point for all unassigned pages. If you do not
specify a default recipient name for unidentified pages (here or in the report defaults), then your
decollating mission will be flagged as ended NOTOK in the Active Missions file (although it may have
decollated the output successfully), and any unidentified pages will be assigned to the user in the top
level of the tree.

Decollating Mission Specifies:

 Which reports or report pages should be given to which recipients.

 How many copies of the report should be printed (by default).
 The destination to which the report output will be directed.
 Which printing characteristics will be assigned to the report (if different from the original).
 What name should be assigned to the processed reports.
 How reports will be printed (what printing mission will print the reports).
 How compressed datasets will be archived (what backup mission will backup the reports).

Types of decollating missions:

1. Report Decollation Mission

2. Print Decollation Mission
3. Backup Mission

Define Print Mission:

1. Go to Mission Definition Entry Panel using =m option.

2. Enter the mission name and type of the mission
3. Define the mission category, owner, task type, dest etc. parameters
4. Save the print mission
5. Specify option F/O against print mission to order the print mission
6. Check the status of print mission in Active Missions Environment (use =a)

Assign User and Print Mission to a Report:

1. Go to User Reports Entry Panel using =u option.

2. Specify the job name and press enter
3. Enter p against Report name.
4. In print dialog box enter option 2, specify the number of copies, pages required and print
mission name

Print Mission Categories:

SEQL: Prints data to a specified dataset. E.g. SEQL=your.dataset.name

SEQL-FILE: Prints data to a default dataset ctdprt following ctdprt.mission-name.Dddmmyy.Thhmmss

naming convention.

MAIL: Prints data to an recipient users email address

ONDSN: Searched for String in specified dataset

ON DSN should be specified like below:

ON DNS = PREFIX=PREFIX, JOBNAME=JOBNAME, JOBID=JOBID

Printing to an Email:

Pre-requisites:
1. SMTP should be configured
2. Logical mail printer should be defined in CTDPARM like below
DEFPRTS PRINTER=(PRT6,SMTPC2,2000,OPEN,00000,MAIL,000)
3. Email Address should be defined in Recipient Definition of a particular user (in ADDRESS
field)

The reports are produced in class D. If this class is not convenient, change it to a different
output class. Be sure to choose a class whose reports are not printed or purged before
Control-D gains control. Do not use the same class that was used for the generic decollating
mission.

Decollation Mission commands:

P Print
V View
U Update
I Insert
A Add Info
Q Quick Access
E Edit

di a -- Shows report information

Report Decollation Mission Parmeters:

1. Category: Category can be anything like PROD, TEST, DAILY etc. You can use the CATEGORY
parameter to create multiple decollating mission definitions for the same job. This helps in
identification. E.g. if JOB6 running on different schedules like daily, weekly and monthly, we
can set up three different decollating mission definitions to handle the various reports:
DAILY (Handles daily reports)
WEEKLY (Handles weekly reports)
MONTHLY (Handles monthly reports)
1. CLASS: Name of the report class
2. User: Recipient User
3. WHEN LINE: Used to specify the start line and end line to search a string
4. COL: Used to specify the start col and end col to search a string
5. STRING: Used to specify string to be searched