This option will display which disks and what flag settings are in use in a previously generated backup job. Use this in conjunction with option 4 to adjust your backup jobs as needed. In order to display the attributes of the backup, choose option 5, `Display backup attributes' from the `Modify/Create a BACKUP job' menu:

Selection (or ?) (1) : 5 Job name : INCREMENTAL1

Information similar to the following will be displayed. This may be modified using option 4 as described above.

Processing an Incremental Backup Backing up disks: DISK$ISE3: Adding information to the VAULT database Not using /VERIFY during backup BCKMGR Backup Procedures V4.0 August 1996 Help information is available for all prompts, just enter a ?.

12.2.4 Option 6: Change format

The COMPACT option creates a centralized multi-job command file, while the EXPANDED option uses a command file for each job. This enables any changes to the file to universally affect all jobs, if desired. Additionally, the EXPANDED command file will not be affected by any changes within MCL to the Backup job settings or the source disk list.

12.2.5 Option 10: Modify parameter settings

The backup job generation procedure is controlled by a group of parameters. All these parameters can be viewed and changed by using this option. In order to change any of the parameters that control the generation of a BACKUP job select option 6 `Modify Parameter Settings' from the `Modify/Create a BACKUP job'. After making this selection the following display is made.

Current parameter settings(from MEDIA_LIBRARY:BCKMGR_MAINT.PAR;) DEFAULTS Incremental Full Unloading 1. Name root INCREMENTAL BACKUP UNLOAD 2. Interval 1-00:00 7-00:00 30-00:00 3. Generations 7 4 9999 4. Verify No Yes Yes BACKUP features 5. Qualifiers 6. User name 7. Notify mode MAIL 8. Use in a recovery Yes 9. Add history records Yes VAULT features 10. Use VAULT default Yes 11. Batch queue 12. Start time +00:02 13. Create new files No 14. Add /ONLINE data Yes 15. Load another parameter file 16. EXIT Selection (16) :

The various parameters that can be changed are listed below:

1. DEFAULT - Name root: The default name root is used as a basis for creating a unique name to suggest whenever a new job is created. A number is appended to the end of this root. A different name (they can be the same) can be assigned to each of the three types of backups that the BCKMGR_MAINT procedure can generate.
2. DEFAULT - Interval: The default interval is the time between (INTERVAL style of job) jobs.
3. DEFAULT - Generations: The default generations parameter indicates how many generations of the media generated by this job to keep. One generation is one run of the job. The BCKMGR_MAINT procedure generates jobs using a generation mode of medium allocation. This can easily be changed after generating the job by using the BCKMGR MODIFY command.
4. DEFAULT - Verify: The default verify setting indicates whether a /VERIFY qualifier should be added to the BACKUP operations when the job is generated.
5. BACKUP - Qualifiers: Any optional Backup qualifiers can be specified here. This is any commonly used BACKUP qualifier (such as /BLOCK_SIZE=32000).
6. BACKUP - User name: The user name indicates what user name to create the BACKUP job with. Typically something like SYSTEM would be used. The user must have enough privileges to perform the requested backup.
7. BACKUP - Notify mode: The notify mode indicates how the MEDIA Job termination message is to be sent. The choices are MAIL (send via VMS MAIL), NOTIFY (broadcast or mail) or NONOTIFY (do not send a message).
8. BACKUP - Use in a recovery: The use in a recovery parameter indicates whether the backup job should be used in a disk recovery. The default is `Yes' and should only be changed to `No' if the job is not needed for a recovery.
9. BACKUP - Add history records: The add history records Choosing `Yes' for this parameter will produce a history record of the backup. This parameter is valid only if the `use in a recovery' parameter is also set to `Yes'.
10. VAULT - Use VAULT: The use VAULT parameter indicates whether or not the generated backup jobs should include all the needed steps to update the VAULT Database.
11. VAULT - Batch queue: The batch queue specifies which queue to put all the VAULT update jobs into. These jobs are created automatically at the end of each BACKUP job.
12. VAULT - Start time: The Start time parameter specifies the start time of the VAULT operation. This enables the process to be performed at a time other than during the BACKUP operation. By delaying the VAULT operation, the two processes do not need to run concurrently, thereby relieving the strain of two I/O intensive processes.
13. VAULT - Create new files: The create new files parameter causes the /NEW_FILE qualifier to be added to all the SORT operations. This option minimizes the size of the VAULT database at the expense of more I/O's.
14. VAULT - Add /ONLINE data: The /ONLINE data parameters causes the /ONLINE qualifier to be added to all ADD operations. When this option is set additional information about each file added to the VAULT database is obtained from the on-line copy of the file. I/O activity can be minimized by setting this parameter to NO.
15. Load another parameter file: Any number of parameter settings can be maintained. Each set is written into a file. Select this option whenever you wish to load another set.

12.2.6 Option 11: Enter rescheduling job into queue

In order to enter a rescheduling job into a queue, choose option 7, `Enter a rescheduling job into queue' from the `Modify/Create a BACKUP job' menu.

Selection (or ?) (1) : 7 Job name (INCREMENTAL1) : INCREMENTAL1

You will then be prompted for an interval and start time as shown below. If the job is successfully rescheduled the start message will be displayed on the screen as shown.

Interval (1-00:00) : 1-00:00 Start time : 1-JAN-1996 17:53 Job INCREMENTAL1_START (queue MWS$BATCH, entry 404) started on MWS$BATCH

12.2.7 Option 12: Add to SCHEDULE database

Choosing this option adds the job to the SCHEDULE database. This gives the user the ability to use the more sophisticated scheduling capabilities available with SCHEDULE. In order to add a job to the SCHEDULE database, choose option 8, `Add to SCHEDULE database' from the `Modify/Create a BACKUP job' menu.

Selection (or ?) (1) : 8 Job name (INCREMENTAL1) : INCREMENTAL1

You will next be prompted for SCHEDULE job name, Interval and Start time as shown below. Upon entering this data, you will receive a confirmation message indicating the job has been added to the SCHEDULE database.

SCHEDULE job name ([SCHED]INCREMENTAL1) : [SCHED]INCREMENTAL1 Interval (1-00:00) : 1-00:00 Start time : 1-JAN-1996 15:30

12.3 Creating jobs using DCL commands

There are two other ways of creating a job from the command line. Either of these can be used to create any job, but you will find that each has its advantages for certain types of jobs.

1. BCKMGR CREATE is the general purpose command that can optionally prompt you for the basic elements of a job definition.
2. BCKMGR COPY is useful when there is an existing job similar to the one you want to set up. You can use BCKMGR COPY to copy the existing job to another name and then make whatever modifications are necessary to the copy.

Adding a job to the BCKMGR database is a simple matter of adding the basic components. The steps to follow are:

• Create an entry: First create a control entry in the BCKMGR database. Adjust the control entry to have the desired repeat and reschedule parameters set. Specify what batch queue to use.
• Add in DCL commands: Add in the VMS DCL commands that the job is to execute at run time. Any number of commands can be added. A command list could be as short as one RUN statement or as long as an entire backup job.

12.3.1 BCKMGR CREATE

BCKMGR CREATE is the basic command for building backup jobs. The real power of this command is in the multiplicity of qualifiers, which set various parameters. The format of BCKMGR CREATE command is:

$ BCKMGR CREATE JOB_NAME/QUALIFIERS

The most commonly used qualifier is /PROMPT. Which causes an interactive query of all the essential parameters needed for a job definition. The format of the BCKMGR CREATE/PROMPT command is:

$ BCKMGR CREATE JOB_NAME/PROMPT/QUALIFIERS

You can set the flags for submit options, which affect what the conditions are inside the VMS queue. Possible Submit Options are specified in Table 12-2.

Table 12-2 Submit options

Submit Option	Description
[NO]KEEP	Do not keep log file. The log file is generally kept even without the /LOG qualifier, which displays the log to the user. (KEEP is the default.)
[NO]PRINT	Print log file. (FLAG=NOPRINT is the default.)
[NO]RESTART	Job can be restarted if it terminates prematurely. (NORESTART is default.)

12.3.2 BCKMGR COPY

BCKMGR COPY is the simplest way to create a job, but also the most limited, in that there must already be a similar job available to copy. You use BCKMGR COPY to copy the existing job to another name called the target job. BCKMGR COPY copies everything about the source job to the target job: parameters and DCL commands. Then you can make whatever modifications you want to the copy, using the commands MODIFY, INSERT or EDIT, as discussed in the next section.

The format for COPY is:

$ BCKMGR COPY SOURCE_JOB TARGET_JOB/QUALIFIERS

The only qualifiers allowed are the general BCKMGR qualifiers, /CONFIRM and /LOG.

If a user wants to use the job BACKUP_JOB1 as her template for a similar job and wants to call the new job BACKUP_JOB3, she enters:

$ BCKMGR COPY BACKUP_JOB1 BACKUP_JOB3

12.4 Modifying jobs

The command MODIFY can be used to change any of the fields defined in a job definition. Any of the field parameters discussed under those commands can be changed using MODIFY. MODIFY cannot be used to make changes to the lists of commands in a job definition.

The command format is:

$ BCKMGR MODIFY JOB_NAME/QUALIFIERS

The general qualifiers, /LOG and /CONFIRM, can be used. These qualifiers have all been discussed in detail under the individual commands for creating job definitions. Review the sections on commands for more information about the individual qualifiers.

For example, a user who has created the job definition BACKUP_JOB3 using BCKMGR COPY from another job may decide to change the number of generations of the job to keep. To change it to six he would enter:

$ BCKMGR MODIFY BACKUP_JOB3/GENERATIONS = 6

If he also wants to modify the comment for the job he could enter:

$BCKMGR MODIFY BACKUP_JOB3/COMMENT = "Incremental backup job 12-2-92"

12.4.2 BCKMGR INSERT

$BCKMGR INSERT JOB_NAME INPUT_FILE_NAME

If a user wants to change the commands for the job BACKUP_JOB3, she can build a command file called COMFILE.COM and then type in:

$ BCKMGR INSERT BACKUP_JOB3 COMFILE.COM

An alternate way to change a list using INSERT is to give the file name SYS$INPUT as your input file name. This lets you type the list in directly from the console. Press CONTROL/Z to exit. For example, to change the list of commands for the job BACKUP_JOB1, type:

$ BCKMGR INSERT BACKUP_JOB1 SYS$INPUT