QUSRBRM.BACKUP_POLICY View

The QUSRBRM.BACKUP_POLICY view shows the BRMS backup policy attributes defined for the system.

The values returned for the columns in this view are similar to the values returned by the Work with Policies using BRM (WRKPCYBRM) command TYPE(*BKU).

Authorization:  

The authorization ID of the statement must include the following privileges:

  • *OBJOPR and *READ authority to the QUSRBRM/BKU_POLICY *FILE object.

Result Table

The following table describes the columns in the view.  The schema is QUSRBRM.

Column Name

System Column Name

Data Type

Description

POLICY_NAME

POLICY

VARCHAR(10)

Always *BKUPCY

FULL_MEDIA_POLICY

FULMEDPCY

VARCHAR(10)

The full media policy associated with this control group.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • media-policy-name The media policy to use

INCREMENTAL_MEDIA_POLICY

INCMEDPCY

VARCHAR(10)

The incremental media policy associated with this control group. 

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • media-policy-name The media policy to use

SUNDAY_BACKUP

SUNDAY

VARCHAR(11)

 

The control group backup to run on Sunday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

MONDAY_BACKUP

MONDAY

VARCHAR(11)

 

The control group backup to run on Monday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

TUESDAY_BACKUP

TUESDAY

VARCHAR(11)

 

The control group backup to run on Tuesday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

WEDNESDAY_BACKUP

WEDNESDAY

VARCHAR(11)

 

The control group backup to run on Wednesday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

THURSDAY_BACKUP

THURSDAY

VARCHAR(11)

 

 

The control group backup to run on Thursday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

FRIDAY_BACKUP

FRIDAY

VARCHAR(11)

 

The control group backup to run on Friday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

SATURDAY_BACKUP

SATURDAY

VARCHAR(11)

 

The control group backup to run on Saturday. 

The possible values are:

  • FULL Indicates a full backup activity.

  • INCREMENTAL Indicates an incremental backup activity.

  • NO Indicates no backup activity.

SIGNOFF_INTERACTIVE_USERS

SGNOFFUSR

VARCHAR(7)

Whether BRMS should automatically notify active users that a backup is about to occur and then sign them off for this backup control group.

This possible values are:

  • *SYSPCY Use the value from the system policy.

  • NO BRMS should not sign off interactive users.

  • YES BRMS should sign off interactive users.

SIGNOFF_MESSAGE_INTERVAL

SGNOFFMSG

VARCHAR(7)

The maximum time limit in minutes that BRMS automatically notifies users prior to automatically signing off active users for this control group.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • number-of-minutes Can range from 0 to 999.

DEVICE_NAMES

DEVICES

VARCHAR(43)

The device names used by the backup for this control group. 

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • *MEDCLS Devices are selected based on the device types that support the density for the media class specified in the media policy.

  • *SAVF Save files are being used.

  • device-names The names of the devices.

Note: The device-names string contains 10 character blank separated device names, up to a maximum of 4.

INCREMENTAL_TYPE

INCR_TYPE

VARCHAR(11)

Specifies the type of incremental (saved changed objects)
backup to be used during backup control group processing.

The possible values are:

  • CUMULATIVE All changed objects since the last full backup are included in the saved objects.

  • INCREMENTAL All changed objects since the last incremental backup are included in the saved objects.

FORCE_FULL_BACKUP_DAYS

FORCE_FULL

VARCHAR(5)

The number of days prior to the current incremental backup
which forces a full save of libraries rather than a save of changed
objects for this control group.

The possible values are:

  • NOMAX No limit exists for the number of days.

  • number-days The valid range for number of days is 0 to 365.

BACKUP_MEDIA_INFORMATION

BKUMEDINF

VARCHAR(7)

Whether you want to automatically save the media information needed for recovery each time you process this backup control group.

The possible values are:

  • LIBRARY Save library level media information.

  • OBJECT Save object level media information.

  • NONE No media information is saved.

SAVE_ACCESS_PATHS

SAVACCPTH

VARCHAR(3)

Whether the logical file access paths that are
dependent on the physical files being saved are also
saved.

The possible values are:

  • NO Only those objects specified on the command are saved. No logical file access paths are saved.

  • YES The selected physical files and all logical file access paths over them are saved.

SAVE_SAVEFILE_CONTENTS

SAVE_SAVF

VARCHAR(3)

Whether the description of a save file, or both the description and the contents of a save file, are saved.

The possible values are:

  • NO Only the description of a save file is saved.

  • YES The description and contents of a save file are saved.

SAVE_SPOOLED_FILE_DATA

SAVE_SPOOL

VARCHAR(3)

Whether to save the spooled file data and
attributes for saved output queues.

The possible values are:

  • NO No spooled file data or attributes are saved with saved output queues.

  • YES All available spooled file data and attributes are saved with saved output queues.

SAVE_DATA_QUEUE_DATA

SAVE_DATAQ

VARCHAR(3)

Whether the description of a data queue, or both the description and the contents of a data queue are saved.

The possible values are:

  • NO Only the description of a data queue is saved.

  • YES The description and contents of a standard data queue are saved. Only the description of a Distributed Data Management (DDM) data queue is saved.

DATA_COMPRESSION

COMPRESS

VARCHAR(6)

Whether data compression is used.

The possible values are:

  • DEVICE If the save is to tape and the target device supports compression, hardware compression is performed.

  • HIGH Software data compression is performed with the LZ1 algorithm.

  • LOW Software data compression is performed with the SNA algorithm.

  • MEDIUM Software data compression is performed with the TERSE algorithm.

  • NO No data compression is performed.

  • YES If the target device supports compression, hardware
    compression is performed. If compression is not supported, software compression is performed.

  • ZLIB Software data compression is performed with the ZLIB deflate algorithm.

DATA_COMPACTION

COMPACT

VARCHAR(3)

Whether data compaction is used.

The possible values are:

  • NO No data compaction is performed.

  • YES Data compaction is performed if the data is saved to tape and all devices used for the backup support the compaction feature.

TARGET_RELEASE

TGTRLS

VARCHAR(8)

The release of the operating system on which you intend to restore the objects being saved.

The possible values are:

  • CURRENT The objects are to be restored on a system that is
    running the same release of the operating system currently running on your system.

  • PREVIOUS The objects are to be restored on a system that is
    running on the previous release of the operating system.

  • target-release The release in the format VxRxMx, where Vx is the version, Rx is the release, and Mx is the modification level.

UPDATE_HISTORY_OBJECTS

UPDHSTOBJ

VARCHAR(3)

Whether the save history information of each saved object is
changed with the date, time, and location of this save operation.

The possible values are:

  • NO The save history information contained in the description of each object saved is not updated.

  • YES The last save date, time, and location is updated in each object
    saved.

UPDATE_HISTORY_DIRECTORIES

UPDHSTDIR

VARCHAR(9)

Specifies whether to update the file system save history on the objects saved with
this save operation.

The possible value are:

  • NO The save operation will not be updated in the save history of the selected file system objects.

  • YES The save history is updated. For local file systems, the system save history is updated. For remote file systems, the PC save history is updated.

  • SYSTEM The local file system save history is updated.

  • PC The PC file system save history is updated.

  • SYSTEM PC The local file system save history and PC file system save history are updated.

CLEAR

CLEAR

VARCHAR(5)

Whether uncleared volumes or save files encountered during the save operation are automatically cleared.

The possible values are:

  • AFTER All the uncleared volumes after the initial volume are
    automatically cleared.

  • ALL All the uncleared volumes or save files encountered
    during the save operation are automatically cleared.

  • NONE None of the uncleared volumes or save files encountered during the save operation are automatically cleared.

OBJECT_PRECHECK

OBJPRECHK

VARCHAR(3)

Whether the save operation ends if any of the selected objects cannot be saved.

The possible values are:

  • NO The save operation for a library continues, saving only those objects that can be saved.

  • YES If after all specified objects are checked, one or
    more objects cannot be saved, the save operation for a library ends before any data is written. If multiple libraries are specified, the save operation continues
    with the next library.

APPEND_TO_MEDIA

APPEND_MED

VARCHAR(3)

Whether to add data files on existing media with active files or to begin a new volume.

The possible values are:

  • NO The saved data files are started on a new volume.

  • YES The saved data files can be added to media already containing active data files. Files are written to the volume immediately following the last active file.

END_OF_MEDIA_OPTION

END_OPTION

VARCHAR(6)

The operation that is automatically done on the tape or optical volume after the save operation ends.

The possible values are:

  • LEAVE The volume does not rewind or unload after the operation ends. It remains at the current position on the device.

  • REWIND The volume is rewound, but not unloaded.

  • UNLOAD The volume is automatically rewound and unloaded after the save operation ends.

JOURNALED_OBJECTS

JRN_OBJS

VARCHAR(3)

Whether to save changed objects that are currently being journaled and that have been journaled since the date and time specified on the REFDATE and REFTIME parameters on the save command.

The possible values are:

  • NO Objects being journaled are not saved.

  • YES Objects whose changes are entered in a journal are saved.

USE_OPTIMUM_BLOCK

USEOPTBLK

VARCHAR(6)

Specifies whether or not the optimum block size is use for the save operation.

The possible values are:

  • DEVICE Use the value specified on the WRKDEVBRM display for the Use optimum block size value.

  • NO The optimum block size supported by the device is not used. Save commands use the default block size supported by all device types.

  • YES The optimum block size supported by the device is used for Save commands.

IPL_AFTER_BACKUP

IPL_AFTER

VARCHAR(7)

Whether you want to start the system after a
backup control group completes its processing.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • NO Do not start the system after the backup control group completes processing.

  • YES Start the system after the backup control group completes processing.

IPL_END_JOBS

IPL_ENDJOB

VARCHAR(10)

Whether the system allows the IPL to end
processing of active jobs in a controlled manner or whether the system ends the jobs immediately.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • CONTROLLED The subsystems active jobs are ended in a controlled manner.

  • IMMEDIATE The subsystems ends all active jobs immediately.

DELAY_TIME

DELAY_TIME

VARCHAR(7)

The amount of time, in seconds, that the system allows a controlled end to be performed by the active subsystems.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • NOLIMIT The system does not power-down until the last job is complete.

  • delay-time The maximum amount of delay time, in seconds, in which a controlled end can be performed. The valid range is 1 to 99999.

RESTART_AFTER_POWER_DOWN

RESTART

VARCHAR(7)

Whether the system ends and powers down, or whether the system ends and then starts again in unattended mode of operation.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • NO The system ends and powers down.

  • YES The system ends and then starts again in unattended mode of operation.

IPL_SOURCE

IPL_SOURCE

VARCHAR(7)

Whether an initial program load (IPL) is started from the A-source or B-source of the system.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • A The system is started from the A-source.

  • B The system is started from the B-source.

  • PANEL The system is started from the source that is currently shown on the operator's display, either the A-source or the B-source.

IPL_RESTART_TYPE

IPL_TYPE

VARCHAR(7)

The point from which the initial program load (IPL) restarts.

The possible values are:

  • *SYSPCY Use the value from the system policy.

  • FULL All portions of the system, including the hardware, are restarted.

  • IPLA The value specified on the Change IPL Attributes (CHGIPLA) command is used.

  • SYSTEM The operating system is restarted. The hardware will only be restarted when required by the system.

EXIT_PROGRAM_LIBRARY

EXITLIB

VARCHAR(10)

Nullable

The name of the library containing the exit program.

The possible values are:

  • library-name The name of the library containing the exit program.

Contains the null value to indicate that no exit program is being used.

EXIT_PROGRAM

EXITPGM

VARCHAR(10)

Nullable

The name of the exit program called following processing of one or more backup items in backup control groups.

The possible values are:

  • program-name The exit program name.

Contains the null value to indicate that no exit program is being used.

EXIT_PROGRAM_FORMAT

EXITFMT

VARCHAR(8)

Nullable

The name of the format defining the information passed to
the exit program about processed backup items.

The possible values are:

  • BKUI0100 The exit program will run after each backup item in the control group.

  • BKUI0200 The exit program will only run at the end of the control group.

  • BOTH Formats BKUI0100 and BKUI0200 are to be used when passing backup item information to the exit program. The exit program will run after each backup item and again at the end of the control group.

Contains the null value to indicate that no exit program is being used.

MISSED_OBJECT_POLICY

MISOBJPCY

VARCHAR(10)

Specifies the name of backup control group used to track missed objects during backup control group processing.

The possible values are:

  • *NONE No tracking of missed objects occurs during the backup control group processing.

  • policy-name The name of backup control group used to track missed objects during backup control group processing.

CLEAR_MISSED_OBJECTS

CLRMISOBJ

VARCHAR(3)

Whether the missed object policy is cleared of previous missed objects when backup control group processing begins.

The possible values are:

  • NO The missed object policy is not cleared of previous missed
    objects before backup control group processing begins.

  • YES The missed object policy is cleared of previous missed
    objects before backup control group processing begins.

ASYNCHRONOUS_BRING

ASYNCBRING

VARCHAR(3)

Whether objects should be asynchronously brought into memory
during the save processing.

The possible values are:

  • NO Objects are not asynchronously brought into memory.

  • YES Objects are asynchronously brought into memory.

LIBRARY_ORDER

LIB_ORDER

VARCHAR(4)

The order libraries will be written to media
when more than one library is included in a save operation.

The possible values are:

  • NAME Libraries are saved in the order the names are specified.

  • SIZE Libraries are saved in the order of the total library size, from largest to smallest.

VIRTUAL_VOLUME_SIZE

VRTVOLSIZ

INTEGER

Specifies the image size that BRMS will use when creating image files in an image catalog. The size is in megabytes.

The possible values are:

  • volume-size 48 - 1,000,000 (megabytes)

NUMBER_OF_VOLUMES

VRTVOLQTY

SMALLINT

Specifies the number of image files to create in the image catalog.

The possible values are:

  • number-of-volumes 1 - 75

VIRTUAL_VOLUMES_ASP

VRTVOLASP

VARCHAR(10)

Specifies the system (1), basic auxiliary storage pool (2-32), or independent auxiliary storage pool (33-255) where virtual media are created.

The possible values are:

  • *SYSTEM Specifies to use the system (1) auxiliary storage pool.

  • auxiliary-storage-pool-number Specifies the system or auxiliary storage pool number to use (1-32).

  • auxiliary-storage-pool-name Specifies the name of the basic user auxiliary storage pool (2-32) or independent auxiliary storage pool (33-255) to use.

 

Privacy Policy | Cookie Policy | Impressum
From time to time, this website may contain technical inaccuracies and we do not warrant the accuracy of any posted information.
Copyright © Fortra, LLC and its group of companies. All trademarks and registered trademarks are the property of their respective owners.