Control-D and Control-V Utilities

Some utilities prefixed by IOA replace corresponding utilities prefixed by CTD in previous versions. In such cases, the old utilities are supported for your convenience; however, you should use the IOA utilities.

BKPRESET – Reset the Backup Mission Status

The BKPRESET utility resets the pending backup or migration missions, and the backup and migration status of the related reports.

This utility affects backup or migration missions in IN PROCESS status, and resets them to ENDED status, but it does not affect the missions that have reached the stage of checking the results of their respective backup or migration jobs. It also resets the status of the reports affected by these missions to WAITING FOR BACKUP/MIGRATION. In addition, it resets the status of all the reports affected by those pending backup or migration missions that have already left the Active Mission File.

If the status of several pending missions, all which have the same name, require resetting, only one of these missions is reset. To reset the remaining missions with the same name, the utility must be invoked repeatedly, once for each mission.

This utility can be invoked in test mode. In this case, it does not change the Control-D repository, and only a simulation report is generated.

BKPRESET Parameters

Table 198 BKPRESET Parameters

Activating the BKPRESET Utility

The utility is activated by the BKPRESET JCL procedure. See the sample BKPRESET job in the Control-D JCL library.

Figure 74 BKPRESET Activation

//BKPRESET  EXEC  BKPRESET,                   
//          [ MODE={ RESET | TEST } ],                              
//          MISNAME={ ALL | NOMISSION | name },
//          [ MISTIME=time ],
//          [ MISODATE=date ]
//BKPRESET

Examples for BKPRESET

//BKPRESET  EXEC  BKPRESET,                   
//          MODE=RESET,                                            
//          MISNAME=BKP0007Y,
//          MISTIME=12054417,
//          MISODATE=261106

//BKPRESET  EXEC  BKPRESET,                   
//          MODE=RESET,                                            
//          MISNAME=ALL

//BKPRESET  EXEC  BKPRESET,                   
//                MODE=RESET,                                            
//                MISNAME=NOMISSION

BKPRESET  EXEC  BKPRESET,                   
//              MODE=TEST,                                            
//              MISNAME=ALL

CTDAPRV – Analyze and update reports approval status

The CTDAPRV utility runs as a batch job and can perform the following actions:

• Forcedly approve or reject the reports which have not been approved or rejected by the standard approval process using Control-D/WebAccess.

• Send email messages to those assigned to approve. For example: to remind them that they have not approved or rejected needed reports or to inform about reports that are forcedly approved by the utility.

• Print information about the reports involved in the approval process and that have not yet been approved or rejected or are being processed by the current utility running.

For more information on the report approval process, see the Control-D and Control-V User Guide.

CTDAPRV Parameters

The utility parameters are specified in the SYSIN DD input stream. They must be specified in the following order:

1. General parameters - define the utility's working mode. Refer to Table 199.

2. Command statements - commands that are specified in the input stream. Refer to Table 200.

Table 199 CTDAPRV general parameters

Command statements have the following syntax:

Command   DAYS=days
    [Command parameters]
INCLUDE
    Selection parameters
EXCLUDE
    Selection parameters

One or more commands can be specified in the input stream.

The following commands are supported:

• APPROVE - Approve reports satisfying the parameter DAYS and INCLUDE/EXCLUDE selection criteria. Changes the status of these reports to Forced Approved and sends an email message to those assigned to approve about the performed action (optional). The APPROVE status can be switched to the REJECT status.

• REJECT - Rejects reports satisfying the parameter DAYS and INCLUDE/EXCLUDE selection criteria. Changes the status of these reports to Forced Rejected. Sends an email message to those assigned to approve about the performed action (optional). The REJECT status can be switched to the APPROVE status.

• SHOUT - Sends Shout email messages to those assigned to approve regarding the reports satisfying the parameter DAYS and INCLUDE/EXCLUDE selection criteria.

• PRINT - Lists all reports satisfying the parameter DAYS and INCLUDE/EXCLUDE selection criteria. No command parameters are supported.

• CLEAN - Deletes orphan approval requests.

The parameter DAYS together with INCLUDE/EXCLUDE statements defines which reports should be selected for a command action. The command parameters specify the message text, urgency and email destination (optional). The email destination by default is taken from the corresponding Approval entry in the Approval Tree or optionally can be specified in the command parameters. See CTDCA2P Parameters in INCLUDE / EXCLUDE Statements for an explanation of these parameters.

Table 200 Parameter DAYS and command parameters

INCLUDE/EXCLUDE statement (CTDAPRV)

The INCLUDE statement defines the selection criteria for reports to be processed. The EXCLUDE statement defines the selection criteria for reports which are not to be processed.

The selection parameters which can be specified in the INCLUDE/EXCLUDE statements are described in Table 201.

The following rules apply to INCLUDE and EXCLUDE statements:

• Several INCLUDE and EXCLUDE statements can be specified.

• All selection parameters are optional. Each selection parameter can be specified several times in the INCLUDE and EXCLUDE statement. In an INCLUDE or EXCLUDE statement, similar selection parameters are related by logical OR, while different selection parameters are related by logical AND.

• CTDAPRV selects all reports that satisfy the parameter DAYS and selection parameters in the INCLUDE statements, except those that satisfy the selection parameters in the EXCLUDE statements.

• If the EXCLUDE statements are missing, all reports that satisfy the parameter DAYS and selection parameters in the INCLUDE statements are selected.

• If the INCLUDE statements are missing, all reports that satisfy the parameter DAYS, except those which satisfy the selection parameters in the EXCLUDE statements, are selected.

• If both the INCLUDE and EXCLUDE statements are missing, all Control-D reports that satisfy the parameter DAYS are selected.

• If DAYS=DATE the following parameters are mandatory in the selection stream: USER, REPNAME, DATE.

Table 201 CTDAPRV INCLUDE/EXCLUDE selection parameters

CTDAPRV Output

The CTDAPRV utility produces an output report to the file referred to by the DAREPORT DD statement.

The output report is issued for each command specified in the input stream. For the PRINT command, only the list of entries selected for the command is issued. For other commands, the list processed by the command report entries is issued.

Activating the CTDAPRV utility

//CTDAPRV EXEC CTDAPRV
//SYSIN DD *
    MODE= PROD|TEST
    [DATETYPE=ODATE|DECDATE]
                   
[APPROVE [DAYS=days]
    [MSG=message text]
    [URG=R|U]
    [EMAIL=email destination]
    [EMAILCC=email destination]
[INCLUDE
    <selection parameters>]
[EXCLUDE
    <selection parameters>]]
                  
[REJECT [DAYS=days]
    [MSG=message text]
    [URG=R|U]
    [EMAIL=email destination]
    [EMAILCC=email destination]
[INCLUDE
    <selection parameters>]
[EXCLUDE
    <selection parameters>]]
                  
[SHOUT [DAYS=days]
    MSG=message text
    [URG=R|U]
    [EMAIL=email destination]
    [EMAILCC=email destination]
[INCLUDE
<selection parameters>]
[EXCLUDE
<selection parameters>]
[PRINT [DAYS=days]
[INCLUDE
<selection parameters>]
[EXCLUDE
<selection parameters>]]              

CTDAPRV Return codes

Table 202 provides a description of the return codes of the CTDAPRV utility.

Table 202 Return codes for the CTDAPRV utility

Examples for CTDAPRV

//CTDAPRV EXEC CTDAPRV
//SYSIN DD *
MODE=PROD
*
APPROVE DAYS=SLA+3
MSG='Report %%REPNAME FROM %%ODATE RECIPIENT=%%USER is
                 forcedly approved'
        EMAIL=address1@net.com
        EMAILCC=address2@net.com
    INCLUDE  USER=USER1
*
REJECT DAYS=SLA+7
    EXCLUDE
        USER=USER1
*
SHOUT DAYS=SLA-2
        MSG='Report %%REPNAME FROM %%ODATE should be approved till %%SLADATE'
        URG=U
//

//CTDAPRV EXEC CTDAPRV
//SYSIN DD *
MODE=PROD
*
PRINT DAYS=0

CTDAUTR – Create list of recipients and reports authorized for a specific User ID

The CTDAUTR utility enables Control-D administrators to get a list of recipients and available reports which are authorized for a specific User ID.

The authorization is checked in the user and security exits based on the Control-D Recipient tree and security environment (such as RACF, TOP-Secret, or ASF2) definitions. Depending on the input parameters, the utility uses the exits invoked in the online environment for accessing via 3270 interface (CTDX004, CTDSE04) or exits invoked under the IOA Application Server for users working via Control-D WebAccess (CTDX024, CTDSE24).

The following reports are available from the CTDAUTR utility:

• list of recipients authorized for a specific User ID

• list of available Control-D reports authorized for viewing or printing by specific User ID. The reports can be selected from the Active, Migrated or/and History User files depending on the input parameters. By default, all authorized reports from the specified User file are printed to the list. Optionally, it is possible to specify INCLUDE/EXCLUDE parameters to select reports.

CTDAUTR Parameters

The input parameters for the utility are specified in the stream referred by the SYSIN DD statement. They must be specified in the following order:

1. General parameters

2. INCLUDE

3. Selection parameters

4. Repeat INCLUDE with other Selection parameters, if needed.

5. EXCLUDE

6. Selection parameters

7. Repeat EXCLUDE with other Selection parameters, if needed.

The general parameters are described in Table 203.

Table 203 CTDAUTR general parameters

Table 204 describes selection parameters that can be specified in the INCLUDE and EXCLUDE statements.

The following rules apply to the INCLUDE and EXCLUDE statements:

• Several INCLUDE and EXCLUDE statements can be specified.

• All selection parameters are optional. Each selection parameter can be specified several times in the INCLUDE and EXCLUDE statements. In an INCLUDE or EXCLUDE statement, similar selection parameters are related by logical OR, while different selection parameters are related by logical AND.

• CTDAUTR selects all reports that satisfy the selection parameters in the INCLUDE statements, except those that satisfy the selection parameters in the EXCLUDE statements.

• If the EXCLUDE statements are missing, all reports that satisfy the selection parameters in the INCLUDE statements are selected.

• If the INCLUDE statements are missing, all reports, except those which satisfy the selection parameters in the EXCLUDE statements, are selected.

• If both the INCLUDE and EXCLUDE statements are missing, all Control-D reports from the specified User file are selected.

Table 204 CTDAUTR selection parameters

CTDAUTR Report output

The utility writes the report data to the file referred to by the DAREPORT DD statement.

List of Recipients

LIST OF RECIPIENTS AUTHORIZED FOR USER ID - user_id
Recipient_1
Recipient_2
...
Recipient_n

List of Reports

Activating the CTDAUTR Utility

Figure 75 shows a template for the JCL to run the CTDAUTR utility.

Figure 75 CTDAUTR activation

//EXEC CTDAUTR
//SYSIN DD *
    [ACTION=RECIPIENTS|REPORTS]
    [ENV=ONLINE|WEB]
    [FILE=[ACT][,MIG][,HST]]
    {USERID=user_id1}
    [USERID=user_id2]
    ...
    [INCLUDE]
    [RECIPIENT=recipient_name]
    [REPNAME=report_name]
    [JOBNAME=job name]
    ...
    [EXCLUDE]
    [RECIPIENT=recipient_name]
    [REPNAME=report_name]
    [JOBNAME=job name]
    ...

CTDAUTR Return codes

Table 205 shows an explanation for the return codes for the CTDAUTR utility.

Table 205 CTDAUTR Return Codes

Examples for CTDAUTR

//EXEC CTDAUTR
//SYSIN  DD   *
    USERID=USER1
/*

//EXEC  CTDAUTR
//SYSIN   DD   *
    ACTION=REPORTS
    ENV=WEB
    FILE=ACT,MIG
    USERID=USER1
    USERID=USER2
/*

//EXEC  CTDAUTR
//SYSIN   DD   *
    FILE=MIG
    USERID=USER1
    INCLUDE
        JOBNAME=ARCHIVE
    EXCLUDE
        RECIPIENT=RECIP1
        RECIPIENT=RECIP2
/*

CTDBLXRP – Rebuild Print Control Records in the Active User File

Print control records are used by printing missions to create print plans.

The CTDBLXRP utility deletes all existing print control records in the Active User Reports file and rebuilds them. These records are rebuilt by scanning the Active and Migrated User Reports file, creating new print control records and inserting pointers to reports in WAIT PRINT status.

Use this utility if

• Reports that have WAIT PRINT status are not selected for printing.

• Many CTD908S error messages with a return code of 16 are issued when a printing mission is building a print plan.

This utility can be run in parallel with other Control-D activities (decollation, printing, online viewing, and so on.)

CTDBLXRP Parameter

The following parameter, described in Table 206, can be specified in the EXEC statement for the utility:

Table 206 CTDBLXRP input parameter

Activating the CTDBLXRP Utility

The CTDBLXRP utility is activated by the following EXEC statement:

//  EXEC CTDBLXRP

CTDBLXRP Return Codes

Table 207 CTDBLXRP Return Codes

CTDCAMF – Compress or Copy Active Missions File

The CTDCAMF utility can compress or copy the Active Missions file (AMF), or change its size.

Message CTDF63W is issued if the AMF is about to become full. Message CTD533S is issued if the AMF does become full. There are two solutions: increase the size of the file or compress the file.

The CTDCAMF utility receives control parameters using DD statement DACOPPRM (or SYSIN). The parameters designate the required function (compress or copy).

Compressing the Active Missions File

The AMF contains entries for jobs that are no longer required, such as missions whose status is DELETED or ENDED OK. By removing the unneeded entries from the file, the CTDCAMF utility provides space for new entries.

//COMP EXEC CTDCAMF  
  COMPRESS
//

Copying the Active Missions File

The AMF can be copied

• to another system

• to another user

• to create a backup

//CAMF EXEC D54FRM,NEWAMF='CTDP.V504.NEWAMF',OUTDUMP=X

For an example of how to implement this utility, see sample job CTDCAMF in the Control-D JCL library.

Changing the Size of the Active Missions File

Begin

Perform the following steps to change the size of the AMF:

1. Rename the current AMF—which is the input file for the copy operation and its backup file—using, for example ISPF 3.2 or 3.4.

   The backup Active Missions file suffix is AMB.

2. Perform the following steps:

   1. Enter ICE and select Customization.

   2. In the Customization screen, set Product ID to CTD.

   3. Select major step 6, "Customize Control-D Data Set Parameters."

   4. Select minor step 2, "Control-D Data Set Parameters."

   5. Change the size of the new AMF by modifying the value of the AMFSIZE parameter from, for example, 1100 blocks to 1200 blocks.

   6. Select minor step 3, "Save Parameters into Product Libraries."

   7. Select minor step 4, "Format the Active Missions File."

   8. Set the TYPE parameter to NEWAMF/NEWAMB.

   9. Submit the job and create a new Active Missions file (with the suffix NEWAMF).

3. Edit the CTDCAMF member in the Control-D JCL library. Change the OLDAMF parameter to match the name specified in Step 1, as follows:

   Copy

   //CAMF EXEC CTDAMF,OLDNAME=’old-dsname’,NEW AMF=’new-dsname’
   COPY
   //

   where

   • old-dsname is the name specified in Step 1.

   • new-dsname is the new DSN with the suffix NEWAMF.

4. Run the CTDCAMF utility to copy the current AMF to the new AMF. You must terminate the utility with a return code of 0.

5. Restart the Control-D monitor and resume operations.

CTDCATF – Compress or Copy Active Transfer File

The CTDCATF utility can compress or copy the Active Transfer file (ATF), or change its size.

If the ATF becomes full, there are two solutions: increase the size of the file or compress the file.

The CTDCATF utility receives control parameters using the EXEC statement. The parameters designate the required function (compress or copy).

Compressing the Active Transfer File

The ATF often contains entries for packets that are no longer required (for example, packets whose status is DELETED or TRANSFERRED OK). By removing the unneeded entries from the file, the CTDCATF utility provides space for new entries.

//COMP EXEC CTDCATF
//

Copying the Active Transfer File

The ATF can be copied

• to another system

• to another user

• to create a backup

//CATF EXEC D51CATF,OUTATF='CTDP.V514.ATF',P=COPY,DEL='DUMMY ', 
//             INATF='CTDP.V310.ATF'

Changing the Size of the Active Transfer File

Begin

Perform the following steps to change the size of the ATF:

1. Rename the current ATF—which is the input file for the copy operation and its backup file—using, for example, ISPF 3.2 or 3.4.

   The backup Active Transfer file suffix is ATB.

2. Perform the following steps:

   1. Enter ICE and select Customization.

   2. In the Customization screen, set Product ID to CTD.

   3. Select major step 6, "Customize Control-D Data Set Parameters."

   4. Select minor step 2, "Control-D Data Set Parameters."

   5. Change the size of the new ATF by modifying the value of the ATFBLK parameter from, for example, 300 blocks to 400 blocks.

   6. Select minor step 3, "Save Parameters into Product Libraries."

   7. Select minor step 6, "Format the A.T.F. File."

3. Edit the CTDCATF member in the Control-D JCL library. Change DD statement INATF to match the name specified in Step 1, as follows:

   Copy

   // EXEC CTDCATF,P=COPY,
   // INATF='old-dsname', OLD ACTIVE TRANSFER FILE
   // OUTATF='new-dsname'

   where

   • old-dsname is the name specified in Step 1.

   • new-dsname is the new DSN.

4. Run the CTDCATF utility to copy the current ATF to the new ATF. You must terminate the utility with a return code of 0.

5. Restart the Control-D monitor and resume operations.

CTDCA2P – Copy Active User Report File to Permanent

The CTDCA2P utility copies new user, report, job or category entries from the Active User Report List file to the Permanent User Report List file. The Permanent User Report List file contains a list of all the reports that each user can receive at any point in time. When a new report is defined, or when a user becomes a report recipient (because of new data from the application), this information is placed in the Active User Report List file after decollation.

This utility copies new entries from the Active User Report List file to the Permanent User Report List file. In this way, the list of reports that the user can receive is maintained automatically.

Records already existing in the Permanent User Report List file with the same JOBNAME, REPORT NAME, RECIPIENT NAME, CATEGORY, FROM USER are not updated.

It is recommended that you run the CTDCA2P utility on a daily basis. For more information, see the Control-D and Control-V chapter in the INCONTROL for z/OS Administrator Guide.

INCLUDE / EXCLUDE Statements (CTDCA2P)

The scope of the copy can be limited by one or more INCLUDE / EXCLUDE statements. Each INCLUDE / EXCLUDE statement contains parameters that limit the user or report list entries that are copied. For information about prefixing, masking and the INCLUDE / EXCLUDE logic used to determine record selection, see Record Selection Logic (INCLUDE / EXCLUDE Statements) (CTM)).

CTDCA2P Parameters in INCLUDE / EXCLUDE Statements

The parameters that can be specified in INCLUDE / EXCLUDE statements:

Table 208 CTDCA2P Parameters

Activating the CTDCA2P Utility

//  EXEC CTDCA2P
    [INCLUDE {parameters}]
    [EXCLUDE {parameters}]

The new report entries are assigned the current Control-D working date (not the computer system date).

This utility can be run simultaneously with the Control-D monitor.

CTDCA2P Return Codes

Table 209 CTDCA2P Return Codes

Example for CTDCA2P

//  EXEC CTDCA2P
    INCLUDE REPNAME=PROD-JCL

--USER--  ------REPORT-------  ---JOB--  ----CATEGORY----
ACCTSRCV  ACCOUNTS-RECEIV-REPT  D4ACCRCV  QUARTERLY
ACCTSRCV  ACCOUNTS-RECEIV-REPT  D4ACCRCV  WEEKLY
BRANCH01  DAILY-BALANCE-REPORT  D4DAILYB  DAILY
BRANCH02  DAILY-BALANCE-REPORT  D4DAILYB  MONTHLY

--USER--  -------REPORT-------  ---JOB--  ----CATEGORY---
BRANCH01  DAILY-BALANCE-REPORT  D4DAILYB  DAILY
BRANCH02  DAILY-BALANCE-REPORT  D4DAILYB  MONTHLY
BRANCH03  DAILY-BALANCE-REPORT  D4DAILYB  DAILY

--USER--  -------REPORT-------  --JOB--   ----CATEGORY--
ACCTSRCV  ACCOUNTS-RECEIV-REPT  D4ACCRCV  QUARTERLY
ACCTSRCV  ACCOUNTS-RECEIV-REPT  D4ACCRCV  WEEKLY1
BRANCH01  DAILY-BALANCE-REPORT  D4DAILYB  DAILY
BRANCH02  DAILY-BALANCE-REPORT  D4DAILYB  MONTHLY2
BRANCH03  DAILY-BALANCE-REPORT  D4DAILYB  DAILY

CTDCCFRS – Create or Update Resource File from XEROX Resource Tape

Create and/or update a CCF Resource file according to resources extracted from a XEROX printer tape.

The CTDCCFRS utility receives control parameters using the CCIFRES DD statement. The corresponding output file must be created with the following characteristics: logical record length 8192, block size 8192, record format FB.

CCIFRES Output File

The CCIFRES output file can contain any valid resources. If some input resources are already located in the Resource file, the new resources replace the ones currently in the Resource file.

Resources can be added to the Resource file using the CCF Manager. Note that any resources added by this method are also deleted if this utility is run afterwards using the NEW parameter. For information, see CTDCCFRS Parameters.

The resource FONTS.TXT must be added to the Resource file by one of the following methods:

• Using this utility

  FONTS MAPPING must be defined in the FONTS DD statement

• Using the CCF Manager in RECORD-ORIENTED mode.

  If the utility is run in New mode, or in Update mode while adding or replacing FONTS.TXT, *.JSL or *.JSI members, the Resource file must be transferred to the PC without translation and without CRLF.

  Member FONTS.TXT must be defined according to the DVS ruler. If there is no input DD statement under the FONTS DD statement, no changes are made in the existing FONTS.TXT member. This DD statement is optional.

  In the PC, the CCF Resource file must be processed by the CCF Manager to add required resources and to be recompiled (PDL, PDI and PDF compiler). Once this has been done, it must be returned to the mainframe where it is ready for use.

  If the Resource file was processed in update mode and no FONTS.TXT, *.JSL or *.JSI members were added or replaced, the Resource file is ready to be used as is, without processing by the CCF Manager.

XERRES Input Tape

The tape is created using the following XEROX commands:

Figure 82 CTDCCFRS XEROX Commands

TAPE VOLINT 6250
COPY TAPE WRITE LABEL *.JSL
COPY TAPE WRITE LABEL *.FNT
COPY TAPE WRITE LABEL *.FRM
COPY TAPE WRITE LABEL *.IMG
COPY TAPE WRITE LABEL *.LGO
COPY TAPE WRITE LABEL *.ICT
TAPE ENDFILE
END

Activating the CTDCCFRS Utility

The CTDCCFRS utility is activated by the following EXEC statement:

//  EXEC CTDCCFRS

CTDCCFRS Parameters

Table 210 CTDCCFRS EXEC Parameters

Parameters are also passed to the utility using the SYSIN DD statement.

Table 211 CTDCCFRS SYSIN Parameters

INCLUDE RES_NAME.EXT1, RES_NAME.EXT2
EXCLUDE RES_NAME.EXT1, RES_NAME.EXT2

CTDCCU – Delete Unneeded CDAM Files

The CTDCCU utility identifies CDAM files that are not referenced by the Active User Report List file (as SYSDATA entries) and optionally deletes them.

CDAM files created using the JCL parameter SUBSYS are not always decollated. Since they are not referenced by the Active User Report List file (ACTUSR), CTDDELRP does not delete these CDAM files. This utility identifies or deletes these CDAM files.

This utility also identifies, and optionally deletes, Control-V index files that are not referenced (as INDEX entries) by the Active User Report List file or the Migrate User Report List file. Since they are not referenced by a Control-V database, they cannot be deleted by the CTDDELRP, CTVCLMIG, or CTVDELI utilities.

CTDCCU Parameters

Table 212 CTDCCU Parameters

IDC3332I ** INSUFFICIENT MAIN STORAGE

Activating the CTDCCU Utility

Figure 83 CTDCCU Activation

//    EXEC CTDCCU
    DATE=fromdate [- todate]
    PREFIX=prefix[,CAT=dsname]
    [SIMULATION={YES|NO}]
    [VERIFY-IN-HISTORY={YES|NO}]

CTDCLHST – Clean History User Report List File

The CTDCLHST utility cleans entries from the History User Report List file. The History User Report List file contains entries describing backed up user reports. Each report has a retention period. The utility scans the History User Report List file for all the reports whose retention period has passed (meaning, the backup is no longer needed), and then deletes them.

The utility also produces a list of all tapes that are no longer needed and can therefore be returned to the global tape pool.

CTDCLHST MODE parameter

This optional parameter in the EXEC statement determines whether the CTDCLHST utility is run in production mode (PROD) or simulation mode (TEST). If the parameter is not specified, the default is production mode. You should run this utility in simulation mode before running it in production mode.

Table 213 CTDCLHST – MODE parameter values

CTDCLHST NOSYS parameter

This optional parameter in the EXEC statement determines whether the CTDCLHST utility checks for USER or INDEX records with missing SYSDATA records, or for SYSDATA records with missing USER records.

Table 214 CTDCLHST – NOSYS parameter values

Activating the CTDCLHST utility

// EXEC CTDCLHST [MODE=TEST|PROD,NOSYS=Y|N|S]

CTDCLHST Return codes

Table 215 CTDCLHST return codes

Resolving insufficient memory problems (CTDCLHST)

The CTDCLHST utility processes History User Report List entries by JOBNAME. The utility allocates memory to read all SYSDATA records for each of these JOBNAMEs. If there are too many SYSDATA records and not enough memory to read them, the DSH948E message is issued. To resolve this problem, run the utility with the NOSYS parameter set to N, and only then run it with the NOSYS parameter set to Y or S.

For further information about regulating the processing of SYSDATA records, see optional wish WD2403.

CTDCP2A – Copy Permanent User Report File to Active

The CTDCP2A utility copies job, user, report, or category entries from the Permanent User Report List file to the Active User Report List file. This process is performed once a day to create new empty entries (in WAIT DECOLLATION status) for each job, user, report, category, odate (original scheduling date).

Any job, user, report, category, or ODATE entries that are already present in the Active User Report List file are not copied (meaning, are not duplicated).

INCLUDE / EXCLUDE Statements (CTDCP2A)

The scope of the copy can be limited by one or more INCLUDE / EXCLUDE statements. Each INCLUDE / EXCLUDE statement contains parameters that limit the user or report list entries that are copied. For information about prefixing, masking and the INCLUDE / EXCLUDE logic used to determine record selection, see Record Selection Logic (INCLUDE / EXCLUDE Statements) (CTM).

CTDCP2A Parameters in INCLUDE / EXCLUDE Statements

The parameters that can be specified in INCLUDE / EXCLUDE statements:

Table 216 CTDCP2A Parameters

Activating the CTDCP2A Utility

//     EXEC CTDCP2A
    [INCLUDE {PARAMETERS}]
    [EXCLUDE {PARAMETERS}]

The new report entries are assigned the current Control-D working date (not the computer system date). It is possible to specify a specific date by setting parameter PARM to date (format mmddyy, ddmmyy, or yymmdd, depending on the site standard defined by the DATETYP parameter).

The utility can be run simultaneously with the Control-D monitor.

CTDCP2A Return Codes

Table 217a CTDCP2A Return Codes

Example for CTDCP2A

// EXEC CTDCP2A,PARM=date
    INCLUDE REPNAME=PROD-JCL

--USER--  -------REPORT-------  ---JOB--  ----CATEGORY---
BRANCH01  DAILY-BALANCE-REPORT  D4DAILYB  DAILY
BRANCH02  DAILY-BALANCE-REPORT  D4DAILYB  MONTHLY
BRANCH03  DAILY-BALANCE-REPORT  D4DAILYB  DAILY

-USER--  ------REPORT------ --JOB--      --CATEGORY-        -ODATE-
ACCTSRCV  ACCOUNTS-RECEIV-REPT D4ACCRCV  QUARTERLY           070700
ACCTSRCV  ACCOUNTS-RECEIV-REPT D4ACCRCV  WEEKLY              070700
BRANCH01  DAILY-BALANCE-REPORT D4DAILYB  DAILY               070700
BRANCH02  DAILY-BALANCE-REPORT D4DAILYB  MONTHLY             070700

--USER--  -------REPORT-------   ---JOB--  ----CATEGORY----  -ODATE-
ACCTSRCV  ACCOUNTS-RECEIV-REPT   D4ACCRCV  QUARTERLY         070700
ACCTSRCV  ACCOUNTS-RECEIV-REPT   D4ACCRCV  WEEKLY            070700
BRANCH01  DAILY-BALANCE-REPORT   D4DAILYB  DAILY             070700
BRANCH02  DAILY-BALANCE-REPORT   D4DAILYB  MONTHLY           070700
BRANCH02  DAILY-BALANCE-REPORT   D4DAILYB  MONTHLY           070700
BRANCH03  DAILY-BALANCE-REPORT   D4DAILYB  DAILY             070700

CTDDELRD – Delete Reports that are not needed

The CTDDELRD utility performs the same operations and it is managed in the same manner as the CTDDELRP utility. The difference is that the CTDDELRD utility invokes the system service IDCAMS, instead of Control-D program CTDDCD, to remove unneeded CDAM and index data sets from DASD.

Refer the delivered IOA PROCLIB library for the exact difference between the JCL procedures.

CTDDELRP – Delete Reports that are not needed

The CTDDELRP utility cleans unneeded user, report, and job entries from the Active User Report List file and erases from the disk the compressed (CDAM) data sets that have no entries in the Active User Report List file. The utility can also move a report entry from the Active User Report List file to either the History User Report List file or the Migrated User Report List file. To do this, the following must be true:

• The DASD retention period for that report has expired or the number of report generation that can be kept on DASD is exceeded.

• The report has been backed up or migrated successfully.

The utility determines which reports are no longer needed for backup, migration, Online viewing, or printing, by means of user-specified selection groups. A selection group consists of a DAYS or GENERATIONS statement and optional INCLUDE / EXCLUDE statements. The DAYS statement contains a retention period that specifies the number of days that the reports remain online, after which they are deleted by the utility. The GENERATIONS statement specifies the number of the latest report generations to keep in the Active User file. All other report generations will be deleted by the utility. The optional INCLUDE / EXCLUDE statements further qualify which reports belong to the selection group. Several DAYS and GENERATIONS selection groups can be specified in the input stream for the utility. At least one DAYS or GENERATIONS statement must be specified.

By specifying multiple selection groups, each with its own retention period and INCLUDE / EXCLUDE statements, groups of entries with differing retention periods can be deleted by a single execution of the CTDDELRP utility. Selection groups are scanned sequentially. The processing of a report is determined by the selection groups whose INCLUDE / EXCLUDE criteria match the report.

The CTDDELRP utility performs the following steps:

1. Records to be deleted from the Active User Report List file are selected according to the parameters specified for the utility, and written to a temporary file.

   Records for reports that have been backed up are written to the History User Report List file. CDAM files to be deleted are written to an intermediate file.

2. The temporary file is read and the records it contains are deleted from the Active User Report List file.

3. CDAM files stored in the intermediate file, in Step 1, are deleted.

CTDDELRP Parameters

Table 218 CTDDELRP Parameters

//DAREPLA DD DISP=MOD,DSN=&OLPREFD..REPLA, SPACE=

CTDDELRP DAYS Statement

The DAYS statement can contain the following parameters:

Table 219 CTDDELRP DAYS Parameters

CTDDELRP GENERATIONS Statement

The first obligatory parameter, n, in the GENERATIONS statement specifies the number of the latest report generations that will be kept in the Active User Report List file. All other report generations will be deleted by the utility. The maximum value is 9999. If 0 is specified, all report generations of the reports selected according to other parameters are deleted. The other parameters in the GENERATIONS statement are the same as in the DAYS statement (see Table 219 in CTDDELRP DAYS Statement).

INCLUDE / EXCLUDE Statements (CTDDELRP)

Each INCLUDE / EXCLUDE statement must be specified on a separate line.

Multiple INCLUDE / EXCLUDE statements can be specified with a DAYS statement. They make up an INCLUDE / EXCLUDE block. Each statement can contain any or all of the parameters listed in Table 220, separated by a space. Each parameter can appear no more than once in each statement.

A report complies with an INCLUDE/EXCLUDE statement when it complies with all parameters specified in the statement. A report complies with an INCLUDE/EXCLUDE block if it complies any INCLUDE statement in the block and does not comply with any EXCLUDE statement in the block. If no INCLUDE statement is coded in an INCLUDE/EXCLUDE block, a report complies with such a block when it does not comply with any EXCLUDE statement in the block. A report always complies with an empty INCLUDE/EXCLUDE block.

A report complies with a selection group when it complies with all parameters specified in the DAYS statement and also complies with the related INCLUDE/EXCLUDE block.

A report is deleted from the Active User Reports List file by the CTDDELRP utility if the report matches the search criteria of any selection group in the utility input stream.

CTDDELRP Parameters in INCLUDE / EXCLUDE Statements

Each INCLUDE / EXCLUDE statement must contain at least one of the following parameters:

Table 220 CTDDELRP Parameters

By default, the values specified for JOBNAME, USER, and REPNAME are treated as prefixes. To prevent a value from being considered a prefix, place the special character < after the value.

Wildcards, ?, and * characters are allowed in values specified for USER, REPNAME, CATEGORY, JOBNAME, JOBID, PGMSTEP, PROCSTEP and DDNAME.

CTDDELRP Deletion Rules

Control-D and Control-V reports are identified by user entries, SYSDATA entries, and CDAM compressed data sets. Each user entry can point to one or more SYSDATA entries. Each SYSDATA entry points to one CDAM data set. Each CDAM data set is pointed to by one or more SYSDATA entries.

When deleting reports, CTDDELRP maintains the integrity of this data structure according to the following rules:

• A CDAM compressed data set is deleted when all SYSDATA entries pointing to it are deleted.

• A SYSDATA entry is deleted when all user entries pointing to it are selected for deletion.

• A user entry is deleted:

• when all SYSDATA entries to which it points are selected for deletion, or

• when every SYSDATA entry to which it points no longer exists, meaning, the SYSDATA entries were deleted using the Control-D or Control-V Online facility

The CTDDELRP utility issues a message if it finds a SYSDATA entry that is not pointed to by any user entry, meaning, the user entries were deleted using the Control-D or Control-V Online facility. If parameter NOREPORT was specified, this SYSDATA entry is automatically deleted.

Activating the CTDDELRP Utility

Figure 88 CTDDELRP Activation

//         EXEC CTDDELRP[,MODE=TEST|PROD]
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
|DAYS|
|GENERATIONS| n [FORCE] [WAITPRINT] [WAITDE|NOTWD] [RESTORED|NOTRST][NOREPORT]
            [KEEPDSN] [NOTUSED=m] [WAITAPRV] [REJECTED]
  [INCLUDE  [JOBNAME=Job name] [JOBID=jobid] [USER=user] [CLASS=class]
            [REPNAME=repname]  [PGMSTEP=pgmstep] [PROCSTEP=procstep]
            [DDNAME=ddname]
            .
            .
            .
 [EXCLUDE   [JOBNAME=Job name] [JOBID=jobid] [USER=user] [CLASS=class]
            [REPNAME=repname]  [PGMSTEP=pgmstep] [PROCSTEP=procstep]
            [DDNAME=ddname]
            .
            .
            . 
[
  |DAYS|GENERATIONS| statement
  [INCLUDE statement]
            .
            .
            .
  [EXCLUDE statement]
            .
    ]

Examples for CTDDELRP

//S1 EXEC CTDDELRP
DAYS 3

//S1 EXEC CTDDELRP
DAYS 0 WAITPRINT

//S1 EXEC CTDDELRP
DAYS 5
INCLUDE REPNAME=PROD-JCL

//S1 EXEC CTDDELRP
DAYS 0 FORCE
INCLUDE JOBNAME=Y99BUP01 JOBID=J01923

//S1 EXEC CTDDELRP
DAYS 0
INCLUDE REPNAME=ACCT*

//S1 EXEC CTDDELRP
DAYS 0
INCLUDE REPNAME=ACCT<

//S1 EXEC CTDDELRP
DAYS 0 WAITPRINT
EXCLUDE REPNAME=PROD-JCL
EXCLUDE CLASS=X
EXCLUDE JOBNAME=P00*

//S1 EXEC CTDDELRP
DAYS 7 WAITPRINT
INCLUDE JOBNAME=PROD*
DAYS 3 FORCE
INCLUDE JOBNAME=TEST*

//S1 EXEC CTDDELRP
DAYS 3 WAITPRINT RESTORED
DAYS 1 WAITDEC
DAYS 10 WAITPRINT NOT RST NOT WD
DAYS 0
INCLUDE USER=SCRAP

//S1 EXEC CTDDELRP
DAYS 4 NOREPORT

//S1 EXEC CTDDELRP
DAYS 30
INCLUDE JOBNAME=PROD*
INCLUDE JOBNAME=FIRST*
DAYS 15 WAITPRINT
INCLUDE JOBNAME=TEST*
DAYS 5  FORCE
EXCLUDE JOBNAME=PROD*
EXCLUDE JOBNAME=FIRST*
EXCLUDE JOBNAME=TEST*

//S1 EXEC CTDDELRP
DAYS 7 NOTUSED=3

//S1 EXEC CTDDELRP,MODE=PROD
GENERATIONS 5 WAITPRINT
INCLUDE REPNAME=REPORT1
//

CTDDIB – Rebuild Index Component of a User Report List File

The CTDDIB utility is used to rebuild a Control-D User Report List file's index component. The new index component corresponds to information currently contained in the IOA Access Method file's data component. Previous contents of the index component are erased. The main index and alternative index components are rebuilt together or separately.

This utility is used when integrity problem is detected in an IOA Access Method file's index component or when an alternative index component is created.

In case of an integrity problem:

• Delete and reallocate the index component.

• Format the index component with the IOADBF utility.

• Rebuild the index component with the CTDDIB utility with parameter ALT=blank/ALL

In case of an alternative index creation:

• Format the index component with the IOADBF utility.

• Activate the alternative index component with the CTDUFANX utility.

• Build the alternative index component with the CTDDIB utility with parameter ALT=ONLY.

CTDDIB Parameters

The following parameters can be specified to the utility in the EXEC statement that invokes the CTDDIB JCL procedure:

Table 221 CTDDIB Parameters

Activating the CTDDIB Utility

//BUILD    EXEC    CTDDIB, DBFILE={ACT|PRM|HST|MIG|MG1|..|MG9}

Example for CTDDIB

//BUILD    EXEC    CTDDIB,DBFILE=HST

CTDDIG – User Report List File Integrity Check

The CTDDIG utility checks the integrity of the User Report List files (that is, Active, Permanent, History, and Migration Report List files) by comparing the data and index components of these files. Optionally, detected errors can be corrected. The utility checks data, main, and all alternative index components. This utility can detect and correct the following types of errors:

• More than one data record exists with the same key.

• A data record exists without a corresponding index record.

• An index record exists without a corresponding data record.

• A data record and its corresponding index record do not have the same update timestamp.

The CTDDIG utility is executed in two sequential stages, as follows:

Table 222 CTDDIG Stages

This utility can be run while Control-D and the Online monitors are active. However, it locks the specified User Report List file so other applications cannot modify it.

• If MODE is set to TEST or TESTMRK, the specified file is locked during only Stage 1.

• If MODE is set to CHANGE, the specified file is locked during both Stage 1 and Stage 2.

You should run this utility in TEST or TESTMRK mode before running it in CHANGE mode.

CTDDIG Parameters

The following parameters can be specified in the EXEC statement that invokes the CTDDIG JCL procedure:

Table 223 CTDDIG Parameters

Activating the CTDDIG Utility

// EXEC CTDDIG,DBFILE={ACT|PRM|HST|MIG|MG1|..|MG9}[,MODE=TEST|TESTMRK|CHANGE]

JCL for executing this utility is in member CTDUFDIG in the Control-D JCL library.

CTDDIP – Delete Pages from CDAM Files and Delete Index Values from Index Files and DB2 Global Indexes Database

The CTDDIP utility enables you to delete pages in CDAM files that are associated with specific Control-D reports. If the pages are deleted by an index, the corresponding index values can be removed from the index file and the global index database as well. The utility determines which report pages and index values should be deleted, based on the selection criteria in the input stream data. Only page level main indexes are supported.

The CTDDIP utility can be used to irreversibly delete confidential data in all copies of a report, and from its index files. The utility uses special characters to override the data to be deleted.

The CTDDIP utility works on Control-D reports that are located in the Active and Migrated User files.

The utility handles

• active CDAM files

• active index files

• CDAM files that were migrated to DASD

• index files that were migrated to DASD

• resident index files for migrated reports

• index files that were copied from migrated index files

• DB2 Global Index Database

The CTDDIP utility processes migrated files when the last migration stage has produced DASD media. It processes migrated files regardless of whether the CTDDELRP utility has already executed. The CTDDIP utility does not process the files created during previous migration stages, but these files can be deleted by the CTVCLMIG utility.

Regardless of whether the CDAM pages will be deleted by reference from specified report entries and indexes, you should expect that the pages will not be available by reference from

• other page level indexes of specified report entries

• the index values contained in the record level indexes of specified report entries, if these values refer to deleting CDAM pages

• other report entries that refer to deleting CDAM pages

WARNING: The results of the utility are irreversible. For this reason, BMC recommends that you first run the CTDDIP utility in TEST mode before running it in PROD mode.

CTDDIP Parameters

The CTDDIP utility uses

• EXEC statement parameters

• Input Data Stream parameters

CTDDIP EXEC Statement Parameters

The CTDDIP utility EXEC statement includes the parameters shown in Table 224.

Table 224 CTDDIP EXEC Statement Parameters

To store the results of each phase, the CTDDIP utility uses two work data sets, DAWRK and DAWRKD. The utility creates these data sets during first its execution.

If execution of the utility is interrupted, it should be attempted once again. In each case the process will be continued from the beginning of the interrupted phase. To force continuation from the very outset, you must delete all records from the DAWRKD work data set.

CTDDIP Input Stream Data Parameters

Place the input stream data in a special data set. This data set should be created with following parameters:

DCB=(RECFM=F or FB, LRECL=190)

The special data set should be specified in the DAINP DD statement. Each record of the input data set contains one input or comment statement. Comment statements begin with an asterisk (*). Input statements contain positional parameters separated by a single blank.

The input stream data should be created using a text editor, according to the structure described in Table 225 below. You can create input stream data with a user program according to the structure described in the CTDDIP (for Assembler) or CTDDIPC (for Cobol) members of the IOA MAC library.

Use the CTDDIP utility under either of the following circumstances to create the template of the input stream data set that contains comment statements that describe the input stream data structure:

• when there is no DAINP DD statement

• when the DAINP DD statement specifies an empty data set

To select needed report entries, set the following parameters to the same values as those set for them in Screen U, or in Control-D/Web Access Server:

• USERNAME

• JOBNAME

• REPORTNAME

• CATEGORYNAME

• ORIGINALSCHEDULINGDATE

To select a unique report entry you can use the STAMP EXEC parameter to specify the decollation time stamp or record time stamp (Record ID) in the TIME STAMP parameter. You can see the record time stamp (Record ID) in the RECORD ID field of Screen U, displayed in A-mode, and described in CTDDIP Example 3. You can see the decollation time stamp in offset 000164 of the DATA RECORD field of the DATRACE output of the CTDUFDPT utility, as described in CTDDIP Example 4.

The CTDDIP utility Input Stream Data statement includes the parameters shown in Table 225.

Table 225 CTDDIP Input Stream Data Parameters

Input Statement and Selected Report Lists (CTDDIP)

If the REPLIST parameter is specified two lists are produced into an output file, as defined by the REPLIST DD statement.

• The input statement list contains the following:

  • DIP93PI message

  • field titles

  • sequential statement number

  • input statement, in two lines

• The selected report list contains the following:

  • DIP93QI message

  • field titles

  • sequential statement number

  • FLAGS field (which describes the types of deleted objects)

  • identification fields of selected report

  • DIP93RI message

• The values that may be shown in the FLAGS field are defined below:

FLAGS field values

Activating the CTDDIP Utility

Use the following syntax to activate the CTDDIP utility:

//      EXEC CTDDIP[,MODE=TEST|PROD[,CHAR=str]][,STAMP=REC|DEC]
//           [,REPLIST=Y|N][,PORTION=n]
//DAINP DD DSN=input_stream_data_set_name

Examples for CTDDIP

//            EXEC CTDDIP,MODE=PROD
//DAINP DD DSN=AAA.INPUT

*M:User    :Job     :Report name         :|   |Decoll.time stamp:Index name          :Index value
*  12345678 12345678 12345678901234567890 |   |12345678 12345678 12345678901234567890 1234567890..
 M          Q23*     SEQURITY REPORT      |   |                  FIRST_NAME           JONSON

O USER     REPORT NAME                                        JOB      JOBNUMB
  MKT      SEQURITY REPORT                                    Q23ACDAM J0024615
  Category: VJOBDSN1               Fromuser:
  Ordered: 06/11/02  Run:          00:00 To: 00:00 Decollated: 06/11/02 14:19 
  Status : Decollated                                          View: V        
  Remarks :
  Copies : 001 Form : STD           Class: T        P-     1264 L-    13224   
  Dest:                             WTR:               Note:                  
  Record  ID        : B87D514E 0DB67A40 RBA: 01003810 UPDT: B87D51AC 061739C0 
  Print   Missions  :                                                         
  Restore Mission   :                                                         
  Pagedef:         Formdef:         Output:           Chars: ****             
  Additional Users  :                                                         

// EXEC CTDDIP,MODE=PROD,STAMP=REC

*M:User    :Job     :Report name         :|   |Decoll.time stamp:Index name          :Index value
* 12345678 12345678 12345678901234567890  |   |12345678 12345678 12345678901234567890 1234567890..
  MKT      Q23ACDAM SEQURITY REPORT       |   |B87D514E 0DB67A40 FIRST_NAME           JONSON     

KEY                                                              
    00000000  E5C5D5C1 40404040 D8F2F3C1 C3C4D4C5  *MKT     Q23ACDME*
    00000010  B8A97123 DE1CA700 001EB8A9 7123DE1C  * z    x    z    *
    00000020  A7001007 000E13D9 E200D8F2 F3C1C3C4  *x      RS Q23ACD*
    00000030  D4C5C3C4 D4C50000 00000000 00000000  *MECDME          *
                                                                                 
DATA RECORD                                                      
    00000000  02700013 00000000 E5C5D5C1 40404040  *        MKT     *
    00000010  D8F2F3C1 C3C4D4C5 B8A97123 DE1CA700  *Q23ACDME z    x *
…
    00000160  00009AF8 B8A97122 9911FB80 00000000  *   8 z  r       * 

// EXEC CTDDIP,MODE=PROD,STAMP=DEC

*M:User    :Job     :Report name         :|   |Decoll.time stamp:Index name          :Index value
*  12345678 12345678 12345678901234567890 |   |12345678 12345678 12345678901234567890 1234567890..
  MKT      Q23ACDME SEQURITY REPORT       |   |B8A97122 9911FB80 FIRST_NAME           JONSON

*M:User    :Job     :Report name         :|   |Decoll.time stamp:Index name        :Index value
*  12345678 12345678 12345678901234567890 |   |12345678 12345678 12345678901234567890 1234567890..
M MKT      Q23AAAA  SEQURITY*             |   |                 

CTDFRESL – CTD RESLIB library allocation

Control-D uses the CTD RESLIB library to store resources used for Control-D Transformer. The name of the CTD RESLIB library is saved in the User file, which causes a limitation during upgrade (you need to use a constant data set name in all releases). To prevent incorrect use of different CTD RESLIB library names, Control-D installs RESLIB with an incorrect RECFM parameter.

Following installation, adding new members to the CTD RESLIB library generates error message CTDE12E, due to incorrect allocation of the CTD RESLIB library.

If you did not previously work with transformers, you need to create a new CTD RESLIB file for resource management, as follows:

1. Delete the CTD RESLIB allocated during installation.

2. Run CTDFRESL, which allocates the CTD RESLIB with correct RECFM and LRECL.

Activating the CTDFRESL utility

The job for executing this utility is in member CTDFRESL in the Control-D JCL library.

CTDFRPGC – Format Page Counter File

The CTDFRPGC utility is available for formatting the Page Counter file (PGC).

Running CTDFRPGC is recommended when one of the following messages is issued in the decollation monitor log:

• CTD7A0S—PAGE COUNTER FILE FULL. PAGE COUNTING TERMINATES

  This message is issued if issued if the PGC file is almost full.

• CTD7A2S—INTERNAL ERROR IN FUNCTION func. PAGE COUNTING TERMINATES

  This message is issued if the PGC file does become full or corrupted. If the PGC is corrupted, run CTDFRPCG for reallocation (with no need to increase file size). If the PGC is full, run CTDFRPCG for reallocation, increasing the size.

Activating the CTDFRPGC utility

The job for executing this utility is in member CTDFRPGC in the Control-D JCL library.

CTDFRPGC Parameters

Most of the parameters used by this utility are documented in the JCL.

The PGCSIZE parameter determines the number of tracks in the PGC file. Default 1.

//FORMPGC  EXEC CTDFRPGC,
//   DISP1=NEW,     1. DISP PARAMETER
//   DISP2=CATLG,   2. DISP PARAMETER
//   DISP3=DELETE,  3. DISP PARAMETER
//   PGCSIZE=3      SIZE PARAMETER --> PGCSIZE parameter is changed.
//

CTDNRC – Propagate category to note and ruler records

The CTDNRC utility propagates the category field from user records to the corresponding note and ruler records in Active, Migrated, and History User databases. The utility prepares the User files for using the category field as the key instead of JOBNAME this is in accordance with optional wish WD1164 set to APPLY=YES, DATAC=CAT.

The CTDNRC utility processes a sequential file unloaded from the User files and creates a new sequential file containing corrected records, which are loaded to the User files. In addition, the utility creates a sequential User List file that contains a list of user records.

The notes and rulers, which are created when WD1164 is applied include the category field. For this reason, the CTDNRC utility should be performed once.

To apply optional wish WD1164, perform the following steps:

1. Unload Active, Migrated, and History databases to sequential files using the IOADUL utility (job CTDUFDUL).

2. Propagate the category to note and ruler in all of the files generated in step 1 using the CTDNRC utility (job CTDNRC).

3. Set optional wish WD1164 to APPLY=YES,DATAC=CAT.

4. Restore Active, Migrated, and History databases from sequential files using the CTDUFRST job.

If there are rulers in the Active User file whose reports are already migrated (backed up) it is necessary to propagate the category from the Migrated (History) User database to the appropriate rulers in the Active User database. The CTDNRCM job creates a Migrated User List file using the CTDNRC utility with special DAUSR DD statements in the first step, and then propagates the category from the created file to rulers of the Active User database, using the CTDNRC utility with the SORTIN DD statement in the second step (see CTDNRC Example 2).

CTDNRC Parameters

The following parameters are specified in the EXEC statement that invokes the CTDNRC JCL procedure:

Table 226 CTDNRC Parameters

CTDNRC Data sets

The following data sets are used in the CTDNRC utility and are described in the CTDNRC JCL procedure:

Table 227 CTDNRC data sets

Activating the CTDNRC utility

// EXEC CTDNRC,SEQI=seqfilenameI,SEQO=seqfilenameO[
//             [,DBPREFD=prefix_filename][,DISPO=jcl_disp_val]
//             [,UNITO=unit_name][,VOLO=vol_name]

Examples for CTDNRC

//NRCACT     EXEC CTDNRC,DBPREFD='CTDP.V600',SEQI=BKPACT,SEQO=NRCACT

//*                                               
//* CREATE MIGRATED USER LIST
//*                                                     
//NRCMIG     EXEC CTDNRC,SEQI=BKPMIG            
//DAOUT      DD DUMMY                                              
//DAUSR      DD DSN=&USER                                          
//SORTIN     DD DUMMY                                              
//*                                                                
//* PROPAGATE CATEGORY TO ACTIVE NOTES AND RULERS  
//*                                               
//NRCACT     EXEC CTDNRC,SEQI=BKPACT,SEQO=NRCACT
//SORTIN     DD DSN=*.NRCMIG.NRC.DAUSR,DISP=(MOD,DELETE)   

CTDNREOR – Translate Notepad records to new format

A new format of Notepad records in Control-D User files is supported from Control-D release 8.0.00. It improves performance of accessing reports containing notes and decreases the space on DASD occupied by the Notepad records. The new Control-D reports created in Control-D release 8.0.00 and later have the new format for the Notepad records.

The CTDNREOR utility translates the old Notepad records, which were created in the Control-D releases earlier than 8.0.00, to the new format. The utility scans the specified User file, finds the reports containing old Notepad records and creates corresponding Notepad records in the new format. The old Notepad records are deleted.

This utility can be submitted once (or several times if the MAXREPNUM parameter is specified) for each User file after upgrading to Control-D release 8.0.00 or later. It is not neceassary to run this utility, since the new programs can access both the old and the new Notepad record formats and the difference in the formats is entirely transparent to the end users. However, it is recommended that customers who are actively working with reports containing Notepad records with the old format, run CTDNREOR to improve performance and resources usage.

CTDNREOR Parameters

The following input parameters are specified in the SYSIN DD input stream and define the User file and number of report entries to be processed by the utility:

Table 228 CTDNREOR utility input parameters

Activating the CTDNREOR utility

//CTDNREOR EXEC CTDNREOR
//SYSIN DD *
FILE=ACT|MIG|HST
MODE=PROD|TEST
[MAXREPNUM=n]
/*
//

Example for CTDNREOR

//CTDNREOR EXEC CTDNREOR
//SYSIN    DD   *
FILE=ACT
//  
//*                                                                

CTDNREOR Return codes

Table 229 shows an explanation for the return codes for the CTDNREOR utility.

Table 229 CTDNREOR Return Codes

CTDREPUS – Control-D report usage analysis

The CTDREPUS utility provides customers with information about Control-D report usage. This information can help find those Control-D reports, which are no longer required by customers, but which continue to be automatically decollated, backed up, or migrated, utilizing expensive resources.

The utility prints the results of the analysis in a usage output report. Using the report, the customer can decide to discontinue decollating, archiving, or migrating reports. Similarly, by deleting obsolete reports from the repository and discontinuing job runs that produce these reports, the customer can reduce unnecessary expenses.

The utility scans the User Report List files and analyzes the report usage parameters (last update date, view, print, and restore indicators) for each report entry. For purposes of this analysis, all Control-D report entries created by the same decollation mission and having the same report name, job name, category, and user attributes are considered as being the same Control-D report. The entries of the same Control-D report can be created periodically (daily, weekly, or monthly). As long as the end user views or prints a report or restores it from the History or Migrated User file, the report is considered in use.

The utility can either analyze all Control-D report entries from all Control-D User files (Active, Migrated, and History files) or report entries selected according to specified selection criterion. The selection criterion and other parameters for the utility are specified in the SYSIN DD input stream and described in the Table 230.

The usage output report is printed to the file referred by the DAREPORT DD statement. Each record of the output report contains usage information about one Control-D report. The format of the usage output report is described CTDREPUS Output.

CTDREPUS Parameters

The utility input parameters specified in the SYSIN DD input stream define which report entries will be selected for analysis. All parameters are optional. If no selection parameters are specified, the utility selects for analysis all Control-D reports from all Control-D User files (Active, Migrated, and History). The parameters are described in Table 230.

Table 230 CTDREPUS utility input parameters

CTDREPUS Output

The output report produced by the CTDREPUS utility has the following header:

CTDREPUS output report header (columns 1 to 10)

Control-D Report Usage Information

CTDREPUS output report header (columns 11 to 16)

Each output report line that follows the header contains usage information about one Control-D Report. The meaning of each output report column is described in Table 231.

Table 231 CTDREPUS output report column description

Activating the CTDREPUS Utility

Figure 89 CTDREPUS Activation

//CTDREPUS EXEC CTDREPUS
//SYSIN DD *
[FILE=([ACT[,MIG[,HST]])
[REPNAME=report_name]
[JOBNAME=job name]
[CATEGORY=category]
[USER=recipient_name]
[DECFROM=dd/mm/yy|mm/dd/yy|yy/mm/dd]
[DECTO=dd/mm/yy|mm/dd/yy|yy/mm/dd]
[NOTUSDAYS=nnnnn]
[BKPMIS=backup mission name]
[MIGMIS=migration mission name]
[MIGMEDIA=migration media name]
[CDAM=CDAM file name]
[VOLSER=volume serial number]
[SORTBY=(n,A)|(n,D)]
/*
//

CTDREPUS Return codes

Table 232 shows an explanation for the return codes for the CTDREPUS utility.

Table 232 CTDREPUS return codes

Example for CTDREPUS

//CTDREPUS   EXEC    CTDREPUS
//SYSIN DD *
FILE=(ACT,MIG)
REPNAME=REPORT*
//

CTDRETC – Control-D report retention

The CTDRETC utility provides retention control of Control-D reports. For example, a customer can preserve Control-D reports, exempting them from being deleted from the Control-D for z/OS repository, even though their retention period has expired.

Retention control is useful for customers in special situations, such as if a company is obliged to keep all data that is relevant to a case that is under debate in court,   although it is passed the expiration dates of the relevant reports.

Currently the report retention period is defined in the migration and backup mission definitions. The clean-up utilities (CTVCLMIG and CTDCLHST) delete the reports whose retention period is expired. The CTDRETC utility enables retention control of migrated or backed-up Control-D reports.

The CTDRETC utility enables the customers to

• preserve migrated and backed-up reports selected according to various selection criteria

• free preserved reports selected according to selection criteria

• delete selected report entries even though their retention period is not yet expired

• change the retention period of selected reports

• print information about the retention of selected reports and datasets

CTDRETC Parameters

Parameters are specified in statements in the SYSIN DD input stream. They must be specified in the following order:

1. General parameters

2. INCLUDE

3. Selection parameters

4. Repeat INCLUDE with other Selection parameters if needed.

5. EXCLUDE

6. Selection parameters

7. Repeat EXCLUDE with other Selection parameters if needed.

General parameters are specified in the beginning of the input stream. They define the utility's action, working mode and list of printed reports. The general parameters are described in the Table 233:

Table 233 CTDRETC general parameters

Table 234 describes selection parameters that can be specified in the INCLUDE and EXCLUDE statements.

The following rules apply to the INCLUDE and EXCLUDE statements:

• Several INCLUDE and EXCLUDE statements can be specified.

• All selection parameters are option. Each selection parameter can be specified several times in the INCLUDE and EXCLUDE statements. In an INCLUDE or EXCLUDE statement, similar selection parameters are related by logical OR, while different selection parameters are related by logical AND.

• CTDRETC selects all reports that satisfy the selection parameters in the INCLUDE statements, except those that satisfy the selection parameters in the EXCLUDE statements.

• If the EXCLUDE statements are missing, all reports that satisfy the selection parameters in the INCLUDE statements are selected.

• If the INCLUDE statements are missing, all reports, except those which satisfy the selection parameters in the EXCLUDE statements, are selected.

• If both the INCLUDE and EXCLUDE statements are missing, all Control-D reports are selected.

Table 234 CTDRETC selection parameters

CTDRETC Output

The CTDRETC utility produces output reports specified by the LIST parameter for the file referred to in the DAREPORT DD statement. The following reports can be printed:

• List of selected records (LIST=RECORDS)

• List of selected reports (LIST=REPORTS)

• List of selected datasets (LIST=FILES)

• List of history and migrated files selected volumes (LIST=VOLS)

List of selected records (LIST=RECORDS)

This report lists the selected VSA records related to the selected Control-D reports. The records are grouped in blocks for their associated report. The records that can be included with the report are represented in Table 235.

Table 235 LIST=RECORDS record representations

Available record types for User records: R = primary

The second line is printed for Migrated User file only.

List of selected reports (LIST=REPORTS)

This report lists the selected Control-D reports.

Only the User record is printed for each selected report with the same representation as for LIST=RECORDS, as shown in Table 235.

List of selected datasets (LIST=FILES)

This report lists the CDAM and the Index datasets related to the selected reports. The records are represented in Table 236.

Table 236 LIST=FILES record representations

List of history and migrated files selected volumes (LIST=VOLS)

This report lists the volumes where the selected reports reside. It is issued for the action EXPORT REPORTS from the History or Migrated User files only. The records are represented in Table 237.

Table 237 LIST=VOLS record representations

Activating the CTDRETC Utility

Figure 90 CTDRETC Activation

//CTDRETC EXEC CTDRETC
//SYSIN DD *
PRESERVE|FREE|DELREP|CHANGE|PRINT
 [REPLIST=NO | YES]
 [RETPD=ddddd]
DBFILE=HST|MIG
MODE=PROD|TEST
 [LIST=([RECORDS|REPORTS,][FILES,][VOLUMES,][RULERS])|ALL]
 [INCLUDE]
    [USER=recipient_name]
    [REPNAME=report_name]
    [JOBNAME=job name]
    [JOBID=job number]
    [CATEGORY=category]
    [ODATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [CDAMDSN=CDAM file name]
    [GENERATIONS=nnnn]
    [INDEXDSN=index file name]
    [INDEXNAME=main index name]
    [BKPMIS=backup mission name]
    [BKPUTIL=backup utility type]
    [MIGMIS=migration mission name]
    [MIGMEDIA=migration media name]
    [EXPDATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [DECDATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [VOLSER=volume serial number]
    [PRESERVED=YES|NO]
    [RETPD=ddddd]
    [APRVSTAT= WAITAPRV|REJECTED|APPROVED]
 [EXCLUDE]
    [USER=recipient_name]
    [REPNAME=report_name]
    [JOBNAME=job name]
    [JOBID=job number]
    [CATEGORY=category]
    [ODATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [CDAMDSN=CDAM file name]
    [INDEXDSN=index file name]
    [INDEXNAME=main index name]
    [BKPMIS=backup mission name]
    [BKPUTIL=backup utility type]
    [MIGMIS=migration mission name]
    [MIGMEDIA=migration media name]
    [EXPDATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [DECDATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [VOLSER=volume serial number]
    [PRESERVED=YES|NO]
    [RETPD=ddddd]
    [APRVSTAT= WAITAPRV|REJECTED|APPROVED]
/*
//

CTDRETC Return codes

Table 238 shows an explanation for the return codes for the CTDRETC utility.

Table 238 CTDRETC return codes

Examples for CTDRETC

The following examples illustrate the use of the utility's control statements:

//CTDRETC   EXEC    CTDRETC
//SYSIN DD *
PRESERVE    DBFILE=MIG
            MODE=PROD
            LIST=ALL
INCLUDE     CATEGORY= CAT1*
            DECDATE=10/01/09
            DECDATE=25/01/09
INCLUDE     CATEGORY= CAT2*
            DECDATE=01/02/09-28/02/09
              

//CTDRETC   EXEC    CTDRETC
//SYSIN DD *
FREE           DBFILE=MIG
            MODE=PROD
            LIST=REPORTS
INCLUDE     CATEGORY= CAT1*
            CATEGORY= CAT2*
EXCLUDE     MIGMIS=MIG0365

//CTDRETC   EXEC    CTDRETC
//SYSIN DD *
DELREP      DBFILE=HST
            MODE=TEST
INCLUDE     USER=USER1

//CTDRETC   EXEC    CTDRETC
//SYSIN DD *
CHANGE      RETPD=3650 DBFILE=MIG
            MODE=PROD
            LIST=(FILES,VOLS)
INCLUDE     MIGMEDIA=CART
            VOLSER=T*
            ODATE=01/01/02-31/12/05
EXCLUDE     VOLSER=T00852

//CTDRETC   EXEC    CTDRETC
//SYSIN DD *
PRINT       DBFILE=MIG
            LIST=(REPORTS,FILES)
INCLUDE        PRESERVED=YES
            USER=USER1

//CTDRETC   EXEC    CTDRETC
//SYSIN DD *
DELREP MODE=TEST DBFILE=MIG
INCLUDE REPNAME=REPORT1
    GENERATIONS=20
//

CTDRSD – Delete orphan resource records

During report decollation using the transformation option (ON TRNDSN/TRNCLASS decollation), Resource Set records and Resource records associated with the report are created in the Permanent User File. The key to Resource Set records is stored in associated SYSDATA records. The Resource Set record references all Resources used by the decollated report. The Resources themselves are stored in the corresponding member of the Control-D RESLIB library. The utility identifies

• Resource Set records that are not referenced by SYSDATA records

• Resource records that are not referenced by Resource Set records

• members of the Control-D RESLIB library that are not referenced by Resource records

If the MODE parameter is set to PROD, the utility deletes the orphan records and members.

If the MODE parameter is set to TEST and orphan records or members are found, the utility issues error messages indicating that there are orphan Resource Set records, Resource records, or Control-D RESLIB library members.

CTDRSD Parameter

Table 239 CTDRSD Parameter

Activating the CTDRSD utility

//CTDRSD EXEC CTDRSD,MODE=TEST

CTDRSD Return codes

Table 240 CTDRSD Return Codes

CTDRSTMS – Massive Restore Request

The CTDRSTMS utility performs a restore request for a large number of previously backed up or migrated reports. The utility selects reports that must be restored according to selection criteria specified in the input parameters. The status of the selected reports changes to WAIT RESTORE.

To perform the restore after this utility is run, a restore mission should be activated. The restore mission is specified as one of the CTDRSTMS utility input parameters.

You can specify a restore mission, with the option of specifying a print mission name, as input parameters for the CTDRSTMS utility. After running the utility you can then print the restored reports by activating the print mission whose name you specified in the PRTMIS input parameter.

CTDRSTMS Parameters

The input parameters for the CTDRSTMS utility are supplied in the file referred to by the SYSIN DD statement. Input parameters are keyword formatted. They can be specified in random order, but each parameter can be specified only once.

There are two groups of input parameters:

• Parameters that define actions for the utility, as described in Table 241.

• Parameters that define report selection criteria, as described in Table 242.

Table 241 CTDRSTMS action definition parameters

Table 242 CTDRSTMS report selection criteria parameters

Activating the CTDRSTMS Utility

//CTDRSTMS EXEC CTDRSTMS
//SYSIN DD *
[MODE= PROD|TEST]
FILE= MIG|HST
[LIST= YES|NO]
RSTMIS= restore mission name
[PRTMIS= print mission name]
*
[FROMDATE = dd/mm/yy]
[TODATE = dd/mm/yy]
[USER = [-]user name]
[JOBNAME= [-]job name]
[REPNAME= [-]report_name]
[JOBID= [-]jobid]
[BKPMIS= [-]backup_mission_name]
[BKPFROM= dd/mm/yy]
[BKPTO= dd/mm/yy]
[MIGMIS= [-]migration_mission_name]
[MIGFROM= dd/mm/yy]
[MIGTO= dd/mm/yy]
[MIGMEDIA= [-]migration_media_name}
[VOLSER= [-]volser]

Examples for CTDRSTMS

//CTDRSTMS EXEC CTDRSTMS
//SYSIN  DD  *
FILE=HST
RSTMIS=RSTTODS
PRTMIS=PRTTODS
FROMDATE=01/01/05  TODATE=10/01/05
/*

//CTDRSTMS EXEC CTDRSTMS
//SYSIN  DD  *
FILE=HST
RSTMIS=RSTFDR
*
USER=USER01
FROMDATE=01/01/06
/*

//CTDRSTMS EXEC CTDRSTMS
//SYSIN  DD  *
FILE=MIG
RSTMIS=RSTMIGM
*
MIGMIS=MIG007D
MIGFROM=01/01/06 MIGTO=01/01/06
JOBNAME=-JOBARC
/*

CTDSMFRP – Paper Usage Report for Defined Users

The CTDSMFRP utility creates a paper usage report by user (recipient). The report is available in detail format with page and line count data for each report, or in summary format with the same data summarized by user.

CTDSMFRP Parameters

Table 243 CTDSMFRP Parameters

Prefixes can be specified in the USER, REPNAME, CATEGORY and ACCOUNT parameters. In the event that a specific name is also a prefix, all reports with that prefix are included. To prevent the name from being considered a prefix, place the special character < after the specified name.

Activating the CTDSMFRP Utility

// EXEC CTDSMFRP
    {parameters}

Example for CTDSMFRP

// EXEC CTDSMFRP
// DASYSIN DD *
    REPTYPE D
    USER MGT
    CATEGORY ACCT

CTDSMFRP Sample Reports

Figure 91 Sample Report 1

BMC SOFTWARE, INC.           CONTROL-D SMF REPORT (VER 6.3.01)    DATE 08/08/00          TIME 23.56        PAGE    6
                   
                                   CONTROL-D: SMF RECORDS FOUND FOR USER - MGT
                                         ------------------------------------------------
                   
          PAGES- NO. OF PAGES         LINES- NO. OF LINES           COPY- NO. OF COPIES
                       FORM- FORM NUMBER             ACCOUNT- ACCOUNT INFO FROM JOBCARD
                   
DATE     TIME   JOB NAME REPORT NAME         CATEGORY NAME        PAGES   LINES     COPY ODATE   FORM    ACCOUNT
-------- -------- -------- -------------------- -------------------- ------ ------------- ---- -------- ---- -------
08/08/00 10:15:17 PBNKRPT2 BANKING REPORT       BI-WEEKLY                49          2542    3 08/08/00 STD
08/08/00 10:15:20 PEMPRPT  EMPLOYEES REPORT-S   DAILY                     1            10    1 08/08/00 STD
08/08/00 11:02:21 PBRNCHLS BRANCH LISTS         DAILY                  5631        269029    1 08/08/00 STD
08/08/00 11:25:05 PMONUPDT MONTHLY UPDATE       MONTHLY                1086         52191    1 08/08/00 STD
08/08/00 15:26:14 PBRNMGRS BRANCH MGRS REP      WEEKLY                   24          1002    1 08/08/00 STD
08/08/00 15:28:47 MSURGRFS MKT SURVEY GRAFHS    WEEKLY                    8           401    5 08/08/00 SPL
08/08/00 19:42:20 GLRPT17A GENERAL LEDGER       DAILY                   293         15866    1 08/08/00 STD
08/08/00 19:30:23 PTBAL1A  TRIAL BALANCE        DAILY                    76          3764    1 08/08/00 STD
08/08/00 21:01:58 PRINVRPT INVENTORY REPORT     DAILY                     9           427    1 08/08/00 STD
08/08/00 21:19:14 ACCSUMRS SUMMARY ACC REPORT   DAILY                   236         11872    1 08/08/00 STD
08/08/00 21:20:32 ACCEXCPR EXCEPTION ACC REPORT DAILY                    53          1697    1 08/08/00 STD
08/08/00 23:06:02 ACCDAILY DAILY ACCOUNTS       DAILY                   468         20171    1 08/08/00 STD
08/08/00 23:12:51 SLRRPTR1 SALARY REPORT RUN #1 WEEKLY                  107          5705    1 08/08/00 STD
08/08/00 23:54:55 SLRRPTR2 SALARY REPORT RUN #2 WEEKLY                  108          5724    2 08/08/00 STD

-------------------------------------------------------------------------------------------------------------------
*****   TOTAL PAGES AND LINES PRINTED FOR USER - MGT                8149        390401
               

Figure 92 Sample Report 2

  BMC SOFTWARE, INC.     CONTROL-D SMF REPORT (VER 6.3.01)     DATE 08/08/00 TIME 23.57      PAGE   29
      
  CONTROL-D: SUMMARY SMF REPORT
          -------------------------------------
       
       
REPORTS - NO. OF REPORTS      DATES - DATES OF FIRST AND LAST REPORTS
PAGES - NO. OF PAGES          LINES - NO. OF LINES
        
   USERS         REPORTS         PAGES          LINES         D A T E S
-------------  -------------  -------------  -------------  -------------------
BR126                      7             63          3,184  08/08/00 - 08/08/00
BR126FC                    4            182          7,095  08/08/00 - 08/08/00
BR126LO                    2             49          2,553  08/08/00 - 08/08/00
BR126SA                    6          2,590        133,479  08/08/00 - 08/08/00
BR127                      7             51          2,336  08/08/00 - 08/08/00
BR127FC                    4            129          4,602  08/08/00 - 08/08/00
BR127LO                    2             35          1,614  08/08/00 - 08/08/00
BR127SA                    6          1,203         53,237  08/08/00 - 08/08/00
BR128                      7             62          3,293  08/08/00 - 08/08/00
BR128FC                    4            194          8,114  08/08/00 - 08/08/00
BR128LO                    2             48          1,683  08/08/00 - 08/08/00
BR128SA                    6          2,008         94,733  08/08/00 - 08/08/00
BR129                      7             41          1,498  08/08/00 - 08/08/00
BR129FC                    4            115          5,321  08/08/00 - 08/08/00
BR129LO                    2            138          5,632  08/08/00 - 08/08/00
BR129SA                    6          1,996         67,682  08/08/00 - 08/08/00
BR130                      7             67          3,663  08/08/00 - 08/08/00
BR130FC                    4            221         10,569  08/08/00 - 08/08/00
BR130LO                    2            196         10,930  08/08/00 - 08/08/00
BR130SA                    6          2,804        135,006  08/08/00 - 08/08/00
BR131                      7             62          1,988  08/08/00 - 08/08/00
BR131FC                    4            198          7,117  08/08/00 - 08/08/00
BR131LO                    2            245          9,285  08/08/00 - 08/08/00
BR131SA                    6          2,053         73,194  08/08/00 - 08/08/00
BR132                      8          1,012         38,449  08/08/00 - 08/08/00
BR132FC                    4            176          5,667  08/08/00 - 08/08/00
BR132LO                    2             98          4,214  08/08/00 - 08/08/00
BR132SA                    6          1,916         59,480  08/08/00 - 08/08/00
BR133                      7             59          1,672  08/08/00 - 08/08/00
BR133FC                    4            238          8,363  08/08/00 - 08/08/00
BR133LO                    2            172          5,118  08/08/00 - 08/08/00
BR133SA                    6          2,141         81,336  08/08/00 - 08/08/00
BR134                      7             66          2,757  08/08/00 - 08/08/00
BR134FC                    4            198          8,452  08/08/00 - 08/08/00
BR134LO                    2            206          6,220  08/08/00 - 08/08/00
BR134SA                    6          1,391         58,413  08/08/00 - 08/08/00
BR135                      7             65          2,352  08/08/00 - 08/08/00
BR135FC                    4            222          9,221  08/08/00 - 08/08/00
BR135LO                    2            201          7,264  08/08/00 - 08/08/00
BR135SA                    6          1,870         71,095  08/08/00 - 08/08/00
DEV                       12            392         13,659  08/08/00 - 08/08/00
GEN-MNGR                   4             48          2,447  08/08/00 - 08/08/00
MGT                       29            495         20,794  08/08/00 - 08/08/00
MKT                       16            125          6,998  08/08/00 - 08/08/00
PROD                       8            197         10,562  08/08/00 - 08/08/00
PRODCNTL                  72            441          8,668  08/08/00 - 08/08/00


------------------------------------------------------------------------------
 T O T A L               1452        276,516     13,274,601
     

Figure 93 Sample Report 3

 BMC SOFTWARE INC.IOA KEY-STROKE REPORTING LANGUAGE (VER 6.3.01)
DATE 08/08/00 TIME 16.49 PAGE 000001
              L I S T    O F   T H E   R E P O R T S
                   F O R  T H E   U S E R
   
   
                          =========
                             MGT
                          =========
   
  ----------------------------------------------------------------------
  :        REPORT       :       STATUS       : COPIES : PAGES :  LINES :
  ----------------------------------------------------------------------
  : EMPLOYEES REPORT-S  : PRINTED-WAIT BKP   :  001   :     1 :     10 :
  ----------------------------------------------------------------------
  : BANKING REPORT      : DECOLLATED         :  000   :    49 :   2542 :
  ----------------------------------------------------------------------
  : BRANCH LISTS        : DECOLLATED         :  000   :  5631 : 269029 :
  ----------------------------------------------------------------------
  : MONTHLY UPDATE      : PRINTED-WAIT BKP   :  001   :  1086 :  52191 :
  ----------------------------------------------------------------------
  : BRANCH MGRS REP     : WAIT PRINT         :  001   :    24 :   1002 :
  ----------------------------------------------------------------------
  : GENERAL LEDGER      : PRINTED-WAIT BKP   :  001   :   293 :  15866 :
  ----------------------------------------------------------------------
  : TRIAL BALANCE       : PRINTED            :  001   :    76 :   3764 :
  ----------------------------------------------------------------------
  : INVENTORY REPORT    : PRINTED-WAIT BKP   :  001   :     9 :    427 :
  ----------------------------------------------------------------------
  : SUMMARY ACC REPORT  : WAIT PRINT         :  002   :   236 :  11872 :
  ----------------------------------------------------------------------
  : EXCEPTION ACC REPORT: DECOLLATED         :  000   :    53 :   1697 :
  ----------------------------------------------------------------------
  : DAILY ACCOUNTS      : WAIT PRINT         :  001   :   468 :  20171 :
  ----------------------------------------------------------------------
  : SALARY REPORT RUN #1: PRINTED            :  001   :   107 :   5706 :
  ----------------------------------------------------------------------
  : SALARY REPORT RUN #2: PRINTED            :  003   :   108 :   5724 :
              ----------------------------------------------------------------------

Figure 94 Sample Report 4

BMC SOFTWARE, INC.    IOA KEY-STROKE REPORTING LANGUAGE (VER 6.3.01)     DATE 08/08/00 TIME 18.24 PAGE 000001
C O N T R O L   -   D   A C T I V E   E N V I R O N M E N T   -   M I S S I O N S   L E  F T
                   
PRODREPS 080800 REP M24A     WAIT SCHEDULE
PRDKPL03 080800 REP M18      WAIT SCHEDULE
PRDKPL06 080800 REP M18      WAIT SCHEDULE
GPLIR16B 080800 REP M22A     WAIT SCHEDULE
PYHIZNRS 080800 REP M01      WAIT SCHEDULE
PBUPDRR  080800 REP M24      HELD WAIT PROCESS
BLUEFORM 080800 PRT M22      WAIT SCHEDULE
BKP0031D 080800 BKP M22      WAIT PROCESS
RST0060M 080800 CRS M22      WAIT PROCESS
RSTADHOC 080800 RST M22      WAIT PROCESS
               
                   
                   
C O N T R O L   -   D   A C T I V E   E N V I R O N M E N T   -   M I S S I O N S   L E  F T

CTDUFANX – Activate or Deactivate Alternative Index Components of a User Report List File

The CTDUFANX utility is used to activate or deactivate a Control-D User file’s alternative index components and print the component’s definitions. To activate the new alternative index component, the CTDUFANX utility writes the component’s definition to the data component of the corresponding User Report List file. To delete the alternative index component, the utility deletes the component’s definition from the data component of the corresponding User file.

Alternative Index Component Definition (CTDUFANX)

To define an alternative index component, create the special DEFALTI member with alternative index identification and key structure. The list and order of the keys should be fit to the most frequently used fields in the filter for report list request in IOA online and Control-D Web Access sessions.

The DEFALTI member should contain one ALT and one KEY statement for each alternative index.

In the component definition:

• The ALT statement defines the index letter.

  Copy

  ALT=index_letter

  The specified index_letter is the alternative index identification. The letter used for the alternative index can be any letter A-Z, excluding I. The index letter is used in DDNAME field for Alternative Index Component.

• The KEY statement defines key list of alternative index.

  Copy

  KEY= key_letter,start_pos,length,seq,…

• or

  Copy

  KEY= (key_letter,start_pos,length[,seq]),…

• The specified key_letter is defined the key field. The possible values of key_letter are shown in Table 244.

  • start_pos is defined as the start position of the key in the field.

  • length is defined as the length of the key.

  • seq is defined as the native sequence of values in report list (A for ascending, Dfor descending)

    Use descending sequence (D) for fields containing dates such as Order, Run, or Decollation date only.

• The keys should be defined according to the following rules:

  • The recipient name (U-key: U,1,8,A) is mandatory.

  • The maximum number of keys is 20.

  • The maximum total of key lengths is 56.

Table 244 Alternative Index Key Fields

ALT=J                  ALT INDEX LETTER                
KEY=(C,1,20),(N,1,20,A),(U,1,8,A)             KEYLEN=56
    (CATEGORY,REPORT(20),USER)

ALT=J                  ALT INDEX LETTER               
KEY=(C,1,20),(M,1,8),(D,1,6,D),(U,1,8,A)      KEYLEN=50
    (CATEGORY,JOBNAME,ODATE,USER)

ALT=J                  ALT INDEX LETTER               
KEY=(M,1,8),(C,1,20),(D,1,6,D),(U,1,8,A)      KEYLEN=50
    (JOBNAME,CATEGORY,ODATE,USER)

ALT=J                  ALT INDEX LETTER               
KEY=(D,1,6,D),(N,1,20),(Y,1,14),(U,1,8,A)     KEYLEN=56
    (ODATE,REPORT(20),REMARK2(14),USER)

CTDUFANX Parameters

The following parameters can be specified for the CTDUFANX utility in the EXEC statement that invokes the CTDUFANX JCL procedure:

//BUILD EXEC CTDUFANX, 
FUNC={ADD|DELETE|PRINT},FILE={ACT|HST|MIG|MG1|…|MG9},M=def_member,
//                         D=def_suffix,ALT={ALL|letter…letter}

Table 245 CTDUFANX Parameters

For an example of how to activate alternative index component, see sample job CTDUFANX in the Control-D JCL library.

//ADD EXEC CTDUFANX,FUNC=ADD,FILE=ACT,M=DEFALTI,D=INSTWORK,ALT=ALL

Creation of Alternative Index Component

1. Define the alternative index in the DEFALTI member of the IOA INSTWORK library.

2. Define the alternative index files in the DEF’s members for Active, History, and Migrated User files of the IOA INSTWORK library.

   The index key length defined in the KEYLEN field of the DEF’s members should be equal to the sum of the key’s length defined in DEFALTI member +8. If MUF partitions are used, the alternative index files should be created for all MUF partitions.

3. Use the CTDUFDBF job in the Control-D JCL library with parameter FUNC=INIT to allocate and format new alternative index files for Active, History, Migrated User files, and Migrated User files partitions.

4. Stop all Control-D monitors, Control-D Applications, IOA Archive Server monitors, and IOA online sessions.

5. Update the IOADSNL, ALCCTDJB, ALCCTD, ALCCTVJB, ALCCTV, and ALCDOLV members in the IOA PARM library, in accordance with the new alternative index files.

   If the IOADSNL, ALCCTDJB, ALCCTD, ALCCTVJB, ALCDOLV, and ALCCTV members do not exist in the IOA PARM library, copy the ALCCTDJB, ALCCTD, ALCCTVJB, ALCCTV, ALCDOLV, and IOADSN members from the IOA IOAENV library to the IOA PARM library. Then rename the IOADSN member to IOADSNL.

   To change the IOADSNL, ALCCTDJB, ALCCTD, ALCCTVJB, ALCCTV, and ALCDOLV members in the IOA PARM library:

   1. Add the following lines in the IOADSNL member:

      Copy

      DATASET DA&FILE&ALT,
              SEQ=1,
              DD=DA&FILE&ALT,
              DSN=%DBPREFD%.&DBTYPE.&ALT.E000

      In this step, &FILE is changed to a specifically used Data Component, &DBTYPE is changed to a specifically used qualifier, and &ALT is changed to an alternative index letter that is defined in the ALT statement of the DEFALTI member. Separate DATASET statements should be defined for each Active, History, and Migrated User files, and Migrated User file partitions.

      Copy

      DATASET DAACTJ,
              SEQ=1,
              DD=DAACTJ,
              DSN=%DBPREFD%.ACTJ.E000

   2. Add the following line to the ALCCTDJB, ALCCTD, ALCCTVJB, ALCCTV, and ALCDOLV members:

      Copy

      KEY=DA&FILE&ALT

      In this step, &FILE is to be changed to a specifically used Data Component, and &ALT is to be changed to a alternative index letter that is defined in the ALT statement of the DEFALTI member, A separate KEY statement should be defined for each Active, History, and Migrated User files, and Migrated User file partitions.

      Copy

      KEY=DAACTJ

6. Build alternative indexes using the CTDDIB utility with parameter ALT=ONLY for each user file.

7. Activate alternative index using CTDUFANX utility with parameter FUNC=ADD for each user file.

8. Start all Control-D monitors, Control-D applications, IOA Archive Server monitors, and IOA online sessions.

Deactivation of Alternative Index Component

Use the CTDUFANX utility with parameter FUNC=DELETE to delete alternative indexes.

//DEL EXEC CTDUFANX,FUNC=DELETE,FILE=ACT,M=DEFALTI,D=INSTWORK,ALT=J

Redefinition of key list in alternative index component

1. Stop all Control-D monitors, Control-D applications, IOA Archive Server monitors, and IOA online sessions.

2. Deactivate the alternative index component.

3. Delete the alternative index component files.

4. Edit the DEFALTI member.

5. Create the alternative index component with a new key list.

6. Start all Control-D monitors, Control-D applications, IOA Archive Server monitors, and IOA online sessions.

CTDUFEXP – Transfer data between Control-D Repositories

The CTDUFEXP utility enables the customer to transfer metadata and objects (such as viewing rulers and notes) associated with Control-D reports from one Control-D for z/OS repository to another Control-D for z/OS repository.

This process is useful for customers

• re-defining their Control-D repositories to reflect changes in their business or IT structure

• merging their Control-D repositories to reduce their production cost

• splitting their Control-D repositories to improve system performance

CTDUFEXP is submitted separately for each exported Control-D User file (Permanent, Active, Migrated, or History). For each User file, the CTDUFEXP utility does the following:

• exports metadata from a Control-D for z/OS repository to a sequential file.

• The data is unloaded to the sequential file pointed by DAEXP DD statement. The name of the sequential file is %DBPREFD%.PACKAGE.DBFILE, where %DBPREFD% is the Control-D files prefix defined in the source repository. The PACKAGE and DBFILE values are taken from the input parameters described below. Using the CTDUFRST and CTDUFLD utilities, the customer can import the metadata from the sequential file to another Control-D for z/OS repository.

• creates a list of the unloaded reports, rulers, CDAM and Index datasets, and tape volumes related to the extracted Control-D reports.

• The lists are helpful for transferring the datasets or volumes to another Control-D repository.

• deletes User and Notepad records from the exported Control-D User files.

• Other objects associated with the exported files can be deleted later by the CTDDELRP, CTDCLHST, and CTVCLMIG utilities.

CTDUFEXP Parameters

The parameters specified in the EXEC statement are listed in the Table 246. These parameters are used in the procedure to create the unloaded dataset name.

Table 246 CTDUFEXP EXEC parameters

Other statements are specified in the SYSIN DD input stream. They must be specified in the following order:

1. General parameters

2. INCLUDE

3. Selection parameters

4. Repeat INCLUDE with other Selection parameters if needed.

5. EXCLUDE

6. Selection parameters

7. Repeat EXCLUDE with other Selection parameters if needed.

General parameters are specified in the beginning of the input stream. They define the utility's action, working mode and list of printed reports. The general parameters are described in the Table 247:

Table 247 CTDUFEXP general parameters

Table 248 describes selection parameters that can be specified in the INCLUDE and EXCLUDE statements.

The following rules apply to the INCLUDE and EXCLUDE statements:

• Several INCLUDE and EXCLUDE statements can be specified.

• All selection parameters are option. Each selection parameter can be specified several times in the INCLUDE and EXCLUDE statements. In an INCLUDE or EXCLUDE statement, similar selection parameters are related by logical OR, while different selection parameters are related by logical AND.

• CTDUFEXP selects all reports that satisfy the selection parameters in the INCLUDE statements, except those that satisfy the selection parameters in the EXCLUDE statements.

• If the EXCLUDE statements are missing, all reports that satisfy the selection parameters in the INCLUDE statements are selected.

• If the INCLUDE statements are missing, all reports, except those which satisfy the selection parameters in the EXCLUDE statements, are selected.

• If both the INCLUDE and EXCLUDE statements are missing, all Control-D reports are selected.

Table 248 CTDUFEXP selection parameters

CTDUFEXP Output

The CTDUFEXP utility produces output reports specified by the LIST parameter for the file referred to in the DAREPORT DD statement. The following reports can be printed:

• List of exported or deleted records (LIST=RECORDS)

• List of exported or deleted reports (LIST=REPORTS)

• List of exported datasets (LIST=FILES)

• List of exported volumes (LIST=VOLS)

• List of exported rulers and logical views (LIST=RULERS)

List of exported or deleted records (LIST=RECORDS)

This report lists the exported or deleted VSA records related to the selected Control-D reports. The records are grouped in blocks for their associated report. The records that can be included with the report are represented in Table 249.

Table 249 LIST=RECORDS record representations

Available record types for User records: R = primary; C = continuation; U = default.

Available record types for Notepad records: N = primary; C = continuation.

Available note types for Notepad records: G = general note; T = tag note.

The second line is printed for Migrated User file only.

List of exported or deleted reports (LIST=REPORTS)

This report lists the exported or deleted Control-D reports.

Only the primary or default User record is printed for each selected report with the same representation as for LIST=RECORDS, as shown in Table 249.

List of exported datasets (LIST=FILES)

This report lists the CDAM and the Index datasets related to the selected for export reports. It is issued for the action EXPORT REPORTS only. The records are represented in Table 250.

Table 250 LIST=FILES record representations

For the ACT and MIG DBFILE types, the size of the total space on DASD and CENTERA which occupied by the selected datasets is printed at the end of report.

To obtain a space utilization report, submit CTDUFEXP in TEST mode with LIST=FILES.

If the report has resident Indexes, the original Index file name also is included in the list.

List of exported volumes (LIST=VOLS)

This report lists the volumes where the selected reports reside. It is issued for the action EXPORT REPORTS from the History or Migrated User files only. The records are represented in Table 251.

Table 251 LIST=VOLS record representations

List of exported rulers and logical views (LIST=RULERS)

This report lists the exported ruler records. It is issued for the action EXPORT RULERS from the Active User file only. The records are represented in Table 252.

Table 252 LIST=RULERS record representations

Activating the CTDUFEXP Utility

Figure 95 CTDUFEXP Activation

//CTDUFEXP EXEC CTDUFEXP,PACKAGE=package_name,DBFILE=ACT|MIG|HST|PRM
//SYSIN DD *
EXPORT|CLEANUP [REPORTS,][RULERS]
MODE=PROD|TEST
[LIST=([RECORDS|REPORTS,][FILES,][VOLUMES,][RULERS])|ALL]
[INCLUDE]
    [USER=recipient_name]
    [REPNAME=report_name]
    [JOBNAME=job name]
    [JOBID=job number]
    [CATEGORY=category]
    [ODATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [CDAMDSN=CDAM file name]
    [INDEXDSN=index file name]
    [INDEXNAME=main index name]
    [BKPMIS=backup mission name]
    [BKPUTIL=backup utility type]
    [MIGMIS=migration mission name]
    [MIGMEDIA=migration media name]
    [EXPDATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [VOLSER=volume serial number]
    [RULNAME=ruler/logical_view name]
    [RULTYPE=VIEW|PRINT|LOGVIEW]
[EXCLUDE]
    [USER=recipient_name]
    [REPNAME=report_name]
    [JOBNAME=job name]
    [JOBID=job number]
    [CATEGORY=category]
    [ODATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [CDAMDSN=CDAM file name]
    [INDEXDSN=index file name]
    [INDEXNAME=main index name]
    [BKPMIS=backup mission name]
    [BKPUTIL=backup utility type]
    [MIGMIS=migration mission name]
    [MIGMEDIA=migration media name]
    [EXPDATE=dd/mm/yy|mm/dd/yy|yy/mm/dd[-dd/mm/yy|mm/dd/yy|yy/mm/dd]]
    [VOLSER=volume serial number]
    [RULNAME=ruler/logical_view name]
    [RULTYPE=VIEW|PRINT|LOGVIEW]
                   
/*
//

CTDUFEXP Return codes

Table 253 shows an explanation for the return codes for the CTDUFEXP utility.

Table 253 CTDUFEXP return codes

Examples for CTDUFEXP

The following examples illustrate the use of the utility's control statements.

//CTDUFEXP   EXEC    CTDUFEXP,PACKAGE=PACK1,DBFILE=ACT 
//SYSIN DD *
EXPORT  REPORTS RULERS
        MODE=PROD
        LIST=ALL
INCLUDE OBNAME=JOB#1
        JOBNAME=JOB#2
        ODATE=01/01/02-31/12/05
EXCLUDE USER=USER#1

//CTDUFEXP   EXEC    CTDUFEXP,PACKAGE=PACK2,DBFILE=HST
//SYSIN DD *
EXPORT REPORTS
        MODE=TEST
        LIST=(REPORTS,FILES,VOLS)
INCLUDE REPNAME=’MY REPORT*’
        BKPMIS=BKPMIS1
EXCLUDE VOLSER=VOL111

//CTDUFEXP   EXEC    CTDUFEXP,PACKAGE=PACK3,DBFILE=MIG
//SYSIN DD *
EXPORT REPORTS
        MODE=PROD
        LIST=(FILES,VOLS)
INCLUDE MIGMEDIA=CART1
        EXPDATE=01/01/10-31/12/50

//CTDUFEXP   EXEC    CTDUFEXP,PACKAGE=PACK1,DBFILE=ACT
//SYSIN DD *
CLEANUP    REPORTS
           MODE=PROD
           LIST=ALL
INCLUDE    JOBNAME=JOB#1
           JOBNAME=JOB#2
           ODATE=01/01/02-31/12/05
EXCLUDE    USER=USER#1

//CTDUFEXP   EXEC    CTDUFEXP,PACKAGE=PACK1,DBFILE=PRM
//SYSIN DD *
EXPORT     RULERS
           MODE=PROD
           LIST=ALL
INCLUDE    USER=USER#1
EXCLUDE    USER=MASTER
//

//CTDUFEXP   EXEC    CTDUFEXP,PACKAGE=PACK1,DBFILE=PRM
//SYSIN DD *
EXPORT    RULERS
        MODE=PROD
        LIST=ALL
INCLUDE    USER=USER#1
//

CTDUFMDV - Separate Migrated User Report List file to different partitions

This utility physically separates the Migrated User Report List file to different partitions, based on the CDAM creation date.

If, for any reason, the CTDUFMDV utility was submitted with the PART parameter failed, the old MUF cannot be updated, and neither a migration mission nor the CTDDELRP utility can work with the old MUF.

To restore full accessibility of the old MUF, submit the CTDUFMDV utility with the RESET parameter.

If the IOADSNL, ALCCTDJB, ALCCTV, and ALCDOLV members in the IOA PARM library were already changed according to this guide, restore their previous conditions.

CTDUFMDV Parameters

Table 254 CTDUFMDV EXEC statement parameters

To separate the existing Migrated User Report List file to different partitions

1. Allocate and format new Migrated User Report List file partitions

   1. Create DEFMIGx and DEFMIGxI members in the IOA INSTWORK library for all Migrated User Report List file partitions.

   2. Run the IOADBF utility (the CTDUFDBF job in the Control-D JCL library) with the FUNC parameter set to INIT, which will allocate and format the new partitions.

   3. Run the IOADBF utility twice for each new Migrated User Report List file partition, once for the Data component and a second time for the Index component.

      An alternative index can be built, activated, and created for a new Migrated User Report List file only after the separation of the original Migrated User Report List file into partitions, using CTDUFMDV. If you create alternative indexes for new empty MIG User files and afterwards submit CTDUFMDV, the utility will take a very long processing time. If you use an alternative index for the new Migrated User Report List file, a corresponding alternative index must be created separately for each Migrated User Report List file partitions data set. After creating the new Migrated User Report List file partitions data set, activate the alternative index with CTDUFANX and rebuild it with CTDUFDIB.

2. Modify the CTDUFMDV job in the CTD JCL library

   1. Remove unneeded DATMx and DATMxI DD statements.

      The DATMP DD statement is used to allocate the data component of the main MIG partition. The DATMPI DD statement is used to allocate the index component of the main MIG partition.

      The DATM# and DATM#I DD statements are used to allocate the data and index components of the corresponding MIG partitions.

   2. Change the &DBTYPE parameter of the remaining DATMx and DATMxI DDstatements, to conform with policies of your site.

3. Propagate a real CDAM creation date to all VSA records that were created in versions prior to 6.3.xx. If you do not have data created in earlier versions, skip to step 4.

   Tomodify VSA records from versions earlier than 6.3.xx

   1. First run the CTDUFMDV utility with the Active User Report list data parameter (ACT). This will update VSA records in the Active User Report List file.

   2. Next run the CTDUFMDV utility with either of the following parameters (the order does not matter), followed by the other:

      • Migrated User Report list data parameter (MIG)
        This will update VSA records in the Migrated User Report List file.

      • >History User Report list data parameter (HST)
        This will update VSA records in the History User Report List file.

   A large amount of memory is required when you run the CTDUFMDV utility with any of the ACT, MIG, or HST parameters. If the utility fails with a memory limitation problem, a VSA record processed by one cycle limit can be supplied in the SYSIN stream, as follows:

   Copy

   //SYSIN    DD 
   *      #########

   ######### is the maximum number of VSA records processed by one cycle, and allocated memory is ######### x 16. The maximum value of ######### is nine digits, with a default value of 100,000,000.

   When you provide a memory limitation the required amount of storage is decreased but the running time can be increased. However, when you run the CTDUFMDV utility with any of the ACT, MIG, or HST parameters, it does not influence regular Control-D work.

4. Separate the old Migrated User Report List file to different partitions, by submitting the CTDUFMDV utility with the PART parameter.

   When CTDUFMDV is running with the PART parameter, any other application that can update the Migrated User Report List file, such as migrations missions or the CTDDELRP or CTVCLMIG utilities, cannot work.

   Depending on the size of the Migrated User Report List file, when CTDUFMDV is running with the PART parameter a considerable amount of time (days or even weeks) can be used. Since neither a migration mission nor the CTDDELRP utility can work at the same time, you should ensure that you have enough disk space to enable decollations to continue during this period.

   Input for the PART parameter is shown below:

   Copy

   //SYSIN    DD *
           20010101
           20040630
           20061231
           99999999

   Each YYYYMMDD line is the last current partition date, and 99999999 means the end of parameters.

   Assume that the PART parameter used the following input:

   Under this example, all reports for CDAMs created

   Copy

   //SYSIN    DD *
           YYYYMMDD
           YYYYMMDD
           99999999

   before January 1, 2001 will be directed to the Migrated User Report List file partition 1

   between January 1, 2001 and June 30, 2004 will be directed to Migrated User Report List file partition 2

   between June 30, 2004 and December 31, 2006 will be directed to Migrated User Report List file partition 3

   after December 31, 2006 will be directed to the main partition

5. If you intend to use alternative indexes for the new Migrated User Report List file partitions data set, format, activate, and rebuild them at this stage.

6. After separation to the new Migrated User Report List file partitions, change the IOADSNL, ALCCTDJB, ALCCTV, and ALCDOLV members in the IOAPARM library.

   If the IOADSNL, ALCCTDJB, ALCCTV, and ALCDOLV members do not exist in the IOAPARM library, copy the ALCCTDJB, ALCCTV, ALCDOLV, and IOADSN members from the IOAIOAENV library to the IOAPARM library. Then rename the IOADSN member to IOADSNL.

   To change the IOADSNL, ALCCTDJB, ALCCTV and ALCDOLV members in IOA PARM library

   1. Remove the following lines in the IOADSNL member:

      Copy

      DATASET DAMIG,
          SEQ=1,
          DD=DAMIG,
          DSN=%DBPREFD%.MIG.E000
      DATASET DAMIGI,
          SEQ=1,
          DD=DAMIGI,
          DSN=%DBPREFD%.MIGI.E000

   2. Add the following lines in the IOADSNL member:

      Copy

      DATASET DAMIG,                 
          SEQ=1,
          DD=DAMIG,              
          DSN=%DBPREFD%.&DBTYPE..E000
      DATASET DAMIGI,                
          SEQ=1,                 
          DD=DAMIGI,             
          DSN=%DBPREFD%.&DBTYPE.I.E000
      DATASET DAMG1,                 
          SEQ=1,                 
          DD=DAMG1,              
          DSN=%DBPREFD%.&DBTYPE.1.E000
      DATASET DAMG1I,                
          SEQ=1,                 
          DD=DAMG1I,             
          DSN=%DBPREFD%.&DBTYPE.1I.E000
      ……………………………………………
      DATASET DAMG#,                 
          SEQ=1,                 
          DD=DAMG#,              
          DSN=%DBPREFD%.&DBTYPE.#.E000
      DATASET DAMG#I,                
          SEQ=1,                 
          DD=DAMG#I,             
          DSN=%DBPREFD%.&DBTYPE.#I.E000

      In this step, where &DBTYPE is to be changed to a specifically used qualifier, # represents the maximum number of used Migrated User Report List file partitions. A separate DATASET statement should be defined for every Migrated User Report List file partition. If you intend to use an alternative index for the new Migrated User Report List file, define a separate DATASET statement for each alternative index of each Migrated User Report List file partition.

   3. Add the following lines to the ALCCTDJB, ALCCTV, and ALCDOLV members:

      Copy

      KEY=DAMG1
      KEY=DAMG1I
      …………….
      KEY=DAMG#
      KEY=DAMG#I

      In this step, # represents the maximum number of used Migrated User Report List file partitions. Separate pairs of DAMGx and DAMGxI statements should be defined for every Migrated User Report List file partition. If you intend to use an alternative index for the new Migrated User Report List file, define a separate DAMGx&ALT statement for each Migrated User Report List file partition (&ALT – alternative Index letter).

7. Change the DATM# and DATM#I DD statements in CTDUFMDV job – they should refer old Migrated User Report List file. Submit the CTDUFMDV utility with the COPYNEW parameter. It will copy to the new Migrated User Report List file all VSA records created or updated by end-users via on-line environment (for example NOTEs) after CTDUFMDV was submitted with PART parameter.

   If it is required to define specific date instead of last CTDUFMDV run date, define COPYNEW parameter as MODE=(COPYNEW,DATE). In this case date for compare will be taken from SYSIN stream as the following:

   Copy

    //SYSIN      DD *
        PARTDATE=YYYYMMDD

8. If for any reason you need to fall back, it can be done if neither CTDDELRP nor Migration Mission worked with new separated Migrated User file (MUF).

   To fall back

   1. Restore the IOADSNL, ALCCTDJB, ALCCTV, and ALCDOLV members in the IOA PARM library to their previous conditions.

   2. Submit the CTDUFMDV job with the RESET parameter. It will restore full accessibly to the original MUF.

   3. Restore the DATM# and DATM#I DD statements in CTDUFMDV job to their previous conditions – they must refer to the new partitioned Migrated User Report List file.

   4. Submit the CTDUFMDV job with the COPYNEW parameter. It will copy all the VSA records, which were created or updated by end-users via the on-line environment (for example, NOTE records) in the new partitioned MUF, to the current (original) Migrated User Report List file.

CTDUFMPR - Repartition of the Migrated User Report List File in place

This utility reorganizes Migrated User Report List file (MUF) partitions in place according to the new partition date ranges specified in the input parameters.

The MUF can be separated into several partitions based on the CDAM creation date by using the CTDUFMDV utility (described in CTDUFMDV - Separate Migrated User Report List file to different partitions). For example, the last (main) partition contains data for the last year, one partition before it contains data for the two previous years, and so on. The date ranges of the MUF partitions are kept in the special MIGPART record, which is located in the main partition of the MUF. Using partitions improves performance of the report list request from the MUF, because most of requests are performed from the last partition, which is a relatively small part of the entire MUF.

When Control-V works with a partitioned MUF, the new reports are usually migrated to the last (main) partition. As the main partition grows, periodically it is necessary to reorganize the MUF partitions according to the new partition date ranges. It can be done using this utility. The MUF records, which are located in the partitions that do not match the new partition date ranges, are moved to the appropriate partitions. The remaining MUF records are not moved. CTDUFMPR does not change the number of partitions.

To repartition the Migrated User Report List file (MUF)

1. Run CTDUFMPR with the COPY function. The MUF records, which are located in the partitions that do not match the new date ranges specified in the SYSIN input parameters, are copied to the corresponding partitions. The copied records are not deleted from the original partitions in this step. The Control-D end users continue working with the original copies of the records during this step. At the end of this step, the MIGPART record is updated with the new partition date ranges.

2. To enable end users to work with the new partitions distribution, perform the steps described in the Utility CTDUFMPR section, in the INCONTROL for z/OS Administrator Guide.

3. Run CTDUFMPR with the DELETE function. The MUF records, which were copied to other partitions in the step 1, are now deleted from the original partitions.

If the MUF is very large (perhaps containing many dozens of millions of records) and many records must be moved to other partitions, the utility might be required to run for an extended period of time, perhaps even days, to process all the required records. It is possible to limit the utility’s working time using the TIMELIM parameter, which specifies the maximum time per run. This parameter can be specified for both the COPY and the DELETE functions. When TIMELIM is specified, if the utility did not have time to process all the required records during the specified time, the utility ends with RC=4 and the CTDMRFW warning message is displayed. In this situation, the utility can be restarted with the same function to process the remaining records. It can be restarted several times, if necessary, until the utility ends with RC=0, indicating that all the required records have been processed.

The Control-D/WebAccess and 3270 terminal end users can continue working with MUF during the entire repartition process. If any records, which were copied during repartition, are updated by end users in the old location, these records are copied to the new partitions by the COPY NEW process. The COPY NEW process automatically starts at the end of the COPY step and, again, immediately at the beginning of the DELETE step.

The Control-V components that perform massive updating of the MUF (such as migration missions, CTDDELRP, CTVCLMIG, and several others) cannot work in parallel with the CTDUFMPR utility, while it is performing the COPY process until CTDUFMPR ends with RC=0. If any of these components are activated when the COPY is in progress, or if CTDUFMPR is started when one of these components is working with the MUF, an error message is issued and the job is not started.

All Control-D components can be started in parallel with CTUFMPR DELETE step.

For more information about synchronization of the repartition process with other Control-D and Control-V components, see the section about synchronization of Control-V components with the repartition process in the INCONTROL for z/OS Administrator Guide.

CTDUFMPR Parameters

The general input parameters are specified in the EXEC statement of the CTDUFMPR job. These parameters are described in the following table:

Table 255 CTDUFMPR EXEC statement parameters

The new partition periods must be specified in the SYSIN DD stream for the function COPY.

The number of statements must be equal to the number of existing MUF partitions.

Each statement can be specified as YYYYMMDD or as -N, where:

•    YYYYMMDD    - the new last date of the corresponding partition,

•    -N                 - number of days back from today of the last partition date.

The first statement must specify the last date of partition 1. The second statement must specify the last date of partition 2. And so on. The last statement always must be 99999999 instead of the last date of the main partition M.

Activating the CTDUFMPR Utility

Figure 96 CTDUFMPR Activation

//  EXEC CTDUFMPR,
//       FUNCTION=COPY|DELETE, MODE=PROD|TEST [,TIMELIM=HHMM]
//SYSIN DD *
    YYYYMMDD or  -NNN
    YYYYMMDD or  -NNN
        …………….
    99999999
/*
//

CTDUFMPR Return codes

The following table shows an explanation for the return codes for the CTDUFMPR utility:

Table 256 CTDUFMPR return codes

Example for CTDUFMPR

MUF consists of the following three partitions:

• The first partition contains reports related to CDAMs created until 31/12/2008.

• The second partition contains reports related to CDAMs created from 01/01/2009 to 31/12/2011.

• The last main partition contains reports related to CDAMs created from 01/01/2012 until the present date.

If today is 31/12/2013, it means that the reports from the last 2 years are in the main partition, the reports from the previous 3 years are in partition 2, and older reports are in partition 1.

We want to reorganize the MUF, so that the main partition only contains the reports from the last year, partition 2 contains the reports from the previous 3 years, and partition 1 contains older reports.

The first partition will contain reports related to CDAMs created until 31/12/2009.

The second partition will contain reports related to CDAMs created from 01/01/2010 to 31/12/2012.

The last main partition will contain reports related to CDAMs created from 01/01/2013 until today.

In the first step, CTDUFMPR is submitted with the following parameters:

// EXEC CTDUFMPR,
//      FUNCTION=COPY,MODE=PROD,TIMELIM=1600
//SYSIN DD *
  20091231
  20121231
  99999999

or the same with SYSIN DD parameters:

//SYSIN DD *
  -1461
  -366
  99999999

The utility will copy the reports for the year 2012 from the main partition to partition 2. The reports for the year 2009 will be copied from partition 2 to partition 1. TIMELIM=1600 means that we allow the utility to work a maximum of 16 hours in one run.

If all the required records are copied in 16 hours, the utility ends with RC=0 and the X'FE'MIGPART record with the new partition distribution is stored in the MUF. If the utility does not have time to copy all the required records during 16 hours, it will end with RC=4 and the following warning message:

CTDMRFW UTILITY IS STOPPED BECAUSE THE TIME LIMIT 1600 HAS BEEN EXHAUSTED

In this case we must submit the utility with the COPY function again, even several times, until all the required records have been copied.

After the utility with the COPY function ends with RC=0, we must perform the actions described in the INCONTROL for z/OS Administrator Guide to enable end users to work with the new partition distribution.

The final step is to submit the utility with the DELETE function to remove the old records, which were copied to the other partitions, from MUF. Use the following command:

// EXEC CTDUFMPR,
//       FUNCTION=DELETE,MODE=PROD,TIMELIM=1600

If all the required records are deleted in 16 hours, the utility will end with RC=0 and the repartition process is completed. If the utility ends with RC=4 and the CTDMRFW warning message, it must be submitted again, even several times, until all the required records are deleted.

CTDUFPRT – Print data from Control-D user files

Using the CTDUFPRT utility you can print records from the Control-D Active, Migrated, History or Permanent User files. The utility selects records for printing according to selection criteria you specify in the input parameters.

The utility prints the selected records either in a SNAP dump format or in a report format based on input parameters. Depending on the format specified, the utility uses one of the following statements to determine the output file:

• DATRACE DD - specifies the output file for SNAP dump format

• DAREPORT DD - specifies the output file for the report format

CTDUFPRT Parameters

The CTDUFPRT utility uses two levels of parameters for input. Basic parameters, (described in Table 257) indicate the file to be used, the type of records to be selected, and how the records are processed. The second level (described in Table 258) are parameters specific to the selected record type. These parameters, sub-parameters of the RECORD parameter, narrow the selection of records to be processed.

Table 257 Basic CTDUFPRT Parameters

Table 258 Record-Type-Specific CTDUFPRT Selection Parameters

Table 259 User Record fields available for printing

Table 260 SYSDATA Record fields available for printing

Table 261 Index Record fields available for printing

Table 262 INP Record fields available for printing

Table 262a NOTE Record fields available for printing

Activating the CTDUFPRT Utility

//CTDUFPRT EXEC CTDUFPRT
//SYSIN DD *
FILE=ACT|MIG|HST|PRM
[RECORD=U|S|I|N|P|B|M|R|O|L|D]
[JOBNAME=jobname]
[JOBID=jobid]
REPNAME=report name]
[CATEGORY=category]
[DECFROM=DD/MM/YY,HH:MM:SS]
[DECTO=DD/MM/YY,HH:MM:SS]
[PRTMIS=print mission name]
[BKPFROM=dd/mm/yy]
[BKPTO=dd/mm/yy]
[BKPMIS=backup mission name]
[MIGMIS=migration mission name]
[MIGFROM=dd/mm/yy]
[MIGTO=dd/mm/yy]
[MIGMEDIA=migartion media name]
[VOLSER=volser]
[INDNAME=index name]
[CDAM=CDAM file name]
[INDFIEL=index file name]
[DEST=CTDS destination]
[PRINTFORM=DUMP|REPORT]
[FIELD=field name]
[PRINT=YES|NO]
/*
//

Examples for CTDUFPRT

//CTDUFPRT EXEC CTDUFPRT
//SYSIN  DD  *
FILE=ACT
RECORD=U
USER=USER01
REPNAME='TEST NEW*'
DECFROM=01/06/04 DECTO=31/07/04
/*

//CTDUFPRT EXEC CTDUFPRT
//SYSIN  DD  *
FILE=HST
RECORD=S
JOBNAME=K06*
BKPMIS=BKP007D
/*

//CTDUFPRT EXEC CTDUFPRT
//SYSIN  DD  *
FILE=MIG
RECORD=I
VOLSER=VVVVVV
MIGFROM=01/05/04
/*

//CTDUFPRT EXEC CTDUFPRT
//SYSIN  DD  *
FILE=MIG
RECORD=S
CDAM=CTD.D61.K06OAMT1.J03014.D1371206.S91.N000A00
/*

//CTDUFPRT EXEC CTDUFPRT
//SYSIN DD  *
FILE=ACT
RECORD=N
JOBID=11111
/*

//CTDUFPRT EXEC CTDUFPRT
//SYSIN  DD  *
FILE=PRM
PRINT=NO
/*

//CTDUFPRT EXEC CTDUFPRT
//SYSIN  DD  *
FILE=ACT
RECORD=U
* SELECTION CRITERIA
USER=U*
FROMDATE=01/01/07
TODATE=12/31/07
* PRINT PARAMETERS
PRINTFORM=REPORT
FIELD=USER
FIELD=REPORT
FIELD=JOBNAME
FIELD=DATE
FIELD=COPIES
FIELD=PAGES
FIELD=LINES
/*

CTDUFUPD – Global Scan or Change of User Files

The CTDUFUPD utility is primarily used to update History, Migration, Active, or Permanent User files. Selection parameters are used as criteria for selecting records to be changed. Change parameters specify the fields to be updated and the values for those fields.

This utility can also be used to print and/or delete User file records that meet the selection criteria.

The utility receives SELECT control statements followed by either CHANGE TO statements or a DELETE statement.

The utility scans the files that are specified using FILE parameters, selects the records that match the selection criteria, and either modifies those records according to the parameters specified after the CHANGE TO statement, or deletes the selected records if a DELETE statement is present.

Selection Criteria Processing (CTDUFUPD)

There are 31 fields that you can use to specify selection criteria. Of these fields, 26 fields can be modified by CHANGE TO processing, as described in the following material.

There is no predefined order in which selection criteria must be listed. Values specified for different fields are connected by a logical AND. Different values specified for the same field are connected by a logical OR.

Examples for CTDUFUPD

SELECT
FILE=ACT
USER=ANDY
REPORT=MYREPORT

SELECT
FILE=ACT
USER=ANDY
USER=MARY
REPORT=MYREPORT

"Change To" Processing (CTDUFUPD)

All values specified after a CHANGE TO statement, until the end of the JCL stream or until the next SELECT statement, replace the existing values in the selected records. The ? wild-character can be used when specifying "change to" values.

For example

CHANGE TO
USER=a???????

means that the first character in the USER field is replaced with ‘a’ and the remaining 7 characters are not changed

USER=a?b?????

means that the first character in the USER field is replaced with ‘a’, the third character is replaced with ‘b’, and the other 6 characters are not changed.

Activating the CTDUFUPD Utility

Figure 97 CTDUFUPD Activation

//UFCH EXEC  CTDUFUPD //SYSIN  DD *        
SELECT               
[FILE=ACT]
[FILE=HST]
[FILE=MIG]
[FILE=PRM]
[PRINT=DETAILS|SHORT]
[PRINT_LIMIT=nnn]
[SIMULATE=YES]
[WRITE_TO_FILE]
[USERFILE=DD_NAME]
                   
[USER     = user    ]
[DEC_TIME = ddmmyy[,hhmm][ - ddmmyy[,hhmm]]]
[TYPE     = type    ]
[JOBNAME  = jobname ]
[JOBID    = jobid   ]
[ODATE    = odate   ]
CHANGE TO           
[USER     = user    ]
[REPORT   = report  ]
[CATEGORY = category]
[REMARK   = remark  ]
[MASKRUL  = maskrul ]
[CLASS    = class   ]
[DEST     = dest    ]
[UDEST    = udest   ]
[EXTWTR   = extwtr  ]
[FORM     = form    ]
[OUTPUT   = output  ]
[PAGEDEF  = pagedef ]
[FORMDEF  = formdef ]
[FROMUSER = fromuser]
[CHARS    = chars   ]
[COPY     = copies  ]
[MAXCOPY  = maximum copies ]
[OVERCLAS = overriding class]
[OVERFORM = overriding form]
SELECT              
[FILE=ACT]
[FILE=HST]
[FILE=MIG]
[FILE=PRM]
[PRINT=DETAILS]
[USER     = user    ]
[REPORT   = report  ]
[DEC_TIME = ddmmyy[,hhmm][ - ddmmyy[,hhmm]]]
[TYPE     = type    ]
[JOBNAME  = jobname ]
[JOBID    = jobid   ]
[ODATE    = odate   ]
DELETE
//

CTDUFUPD Parameters

CTDUFUPD Selection Parameters

The following parameters can be specified after the SELECT statement:

Table 263 CTDUFUPD SELECT Parameters

Fields for After a CTDUFUPD SELECT Statement

Table 264 CTDUFUPD SELECT Fields

date, time( - date,time)

date[ - date]

Fields for After CTDUFUPD SELECT and CHANGE TO Statements

The following table lists the statements that can be specified after either the SELECT or the CHANGE TO statement or after only the CHANGE TO statement.

Table 265 CTDUFUPD SELECT and CHANGE TO Statements