HELPLIB.HLB  —  INITIALIZE
    Formats a disk or magnetic tape volume, writes a label on the
    volume, and leaves the disk empty except for the system files
    containing the structure information. All former contents of the
    disk are lost.

    Requires VOLPRO (volume protection) privilege for most INITIALIZE
    command operations.

    To create or initialize a queue, use the /QUEUE qualifier.

    Format

      INITIALIZE  device-name[:] volume-label

1  –  Parameters

 device-name[:]

    Specifies the name of the device on which the volume to be
    initialized is physically mounted.

    The device does not have to be allocated currently; however,
    allocating the device before initializing it is the recommended
    practice.

 volume-label

    Specifies the identification to be encoded on the volume. For a
    disk volume, you can specify a maximum of 12 ANSI characters;
    for a magnetic tape volume, you can specify a maximum of 6
    alphanumeric characters. Letters are automatically changed
    to uppercase. VSI strongly recommends that a disk volume label
    should only consist of alphanumeric characters, dollar signs ($),
    underscores (_), and hyphens (-).

    To use ANSI "a" characters on the volume label on magnetic tape,
    you must enclose the volume name in quotation marks (" ").  For
    an explanation of ANSI "a" characters, see the description of the
    /LABEL qualifier.

2  –  Description

    The default format for disk volumes in the OpenVMS operating
    system is called the Files-11 On-Disk Structure Level 2. The
    default for magnetic tape volumes is based on Level 3 of the
    ANSI standard for magnetic tape labels and file structure for
    informational interchange (ANSI X3.27-1978).

    The INITIALIZE command can also initialize disk volumes in the
    Files-11 On-Disk Structure Level 1 format.

    You must have VOLPRO privilege to initialize a volume, except in
    the following cases:

    o  A blank disk or magnetic tape volume; that is, a volume that
       has never been written

    o  A disk volume that is owned by your current user
       identification code (UIC) or by the UIC [0,0]

    o  A magnetic tape volume that allows write (W)  access to your
       current UIC that was not protected when it was initialized

    After the volume is initialized and mounted, the SET SECURITY
    command may be used to modify the security profile. When you
    initialize a disk volume, the caching attribute of its root
    directory (000000.DIR;1) is set to write-through. This means
    that by default, all the files and directories that you create in
    the volume will inherit a caching attribute of write-through. To
    change the caching attribute, use the SET FILE command with the
    /CACHING_ATTRIBUTE qualifier.

    When the INITIALIZE command initializes a magnetic tape volume,
    it always attempts to read the volume. A blank magnetic tape can
    sometimes cause unrecoverable errors, such as the following:

    o  An invalid volume number error message:

       %INIT-F-VOLINV, volume is invalid

    o  A runaway magnetic tape (this frequently occurs with new
       magnetic tapes that have never been written or that have
       been run through verifying machines). You can stop a runaway
       magnetic tape only by setting the magnetic tape drive off line
       and by then putting it back on line.

    If this type of unrecoverable error occurs, you can initialize
    a magnetic tape successfully by repeating the INITIALIZE command
    from an account that has VOLPRO (volume protection) privilege and
    by specifying the following qualifier in the command:

    /OVERRIDE=(ACCESSIBILITY,EXPIRATION)

    This qualifier ensures that the INITIALIZE command does not
    attempt to verify any labels on the magnetic tape.

    If you have VOLPRO privilege, the INITIALIZE command initializes
    a disk without reading the ownership information. If you do
    not have VOLPRO privilege, the INITIALIZE command checks the
    ownership of the volume before initializing the disk. A blank
    disk or a disk with an incorrect format can sometimes cause a
    fatal drive error. If a blank disk or a disk with an incorrect
    format causes this type of error, you can initialize a disk
    successfully by repeating the INITIALIZE command with the
    /DENSITY qualifier from an account that has VOLPRO privilege.

    Many of the INITIALIZE command qualifiers allow you to specify
    parameters that can maximize input/output (I/O) efficiency.

3  –  Qualifiers

3.1    /ACCESSED

       /ACCESSED=number-of-directories

    Affects Files-11 On-Disk Structure Level 1 (ODS-1) disks only.

    Specifies that, for disk volumes, the number of directories
    allowed in system space must be a value from 0 to 255. The
    default value is 3.

3.2    /BADBLOCKS

       /BADBLOCKS=(area[,...])

    Specifies, for disk volumes, faulty areas on the volume. The
    INITIALIZE command marks the areas as allocated so that no data
    is written in them.

    Possible formats for area are as follows:

    lbn[:count]       Logical block number (LBN) of the first block
                      and optionally a block count beginning with the
                      first block, to be marked as allocated

    sec.trk.cyl[:cnt] Sector, track, and cylinder of the first block,
                      and optionally a block count beginning with the
                      first block, to be marked as allocated

    All media supplied by VSI and supported on the OpenVMS operating
    system, except diskettes and TU58 cartridges, are factory
    formatted and contain bad block data. The Bad Block Locator
    utility (BAD) or the diagnostic formatter EVRAC can be used
    to refresh the bad block data or to construct it for the media
    exceptions above. The /BADBLOCKS qualifier is necessary only
    to enter bad blocks that are not identified in the volume's bad
    block data.

    DIGITAL Storage Architecture (DSA) disks (for example, disks
    attached to UDA-50 and HSC50 controllers) have bad blocks handled
    by the controller, and appear logically perfect to the file
    system.

    For information on how to run BAD, see the OpenVMS Bad Block
    Locator Utility Manual (available on the Documentation CD-ROM).

3.3    /CLUSTER_SIZE

       /CLUSTER_SIZE=number-of-blocks

    Defines, for disk volumes, the minimum allocation unit in blocks.
    The maximum size you can specify for a volume is 16380 blocks, or
    1/50th the volume size, whichever is smaller.

    For Files-11 On-Disk Structure Level 5 (ODS-5) disks, the default
    cluster size is 16. In this case the minimum value allowed by the
    following equation is applied:

    (disk size in number of blocks)/(65535 * 4096)

    Any fractional values must be rounded up to the nearest integer
    and, by default, are rounded up to the next multiple of 16.

    For Files-11 On-Disk Structure Level 2 (ODS-2) disks, the default
    cluster size depends on the disk capacity; disks with less than
    50,000 have a default of 1. Disks that are larger than 50,000
    have a default of either 16 or the result of the following
    formula, whichever is greater:

    (disk size in number of blocks)/(255 * 4096)

    Any fractional values must be rounded up to the nearest integer
    and, by default, are rounded up to the next multiple of 16.

                                   NOTE

       For Version 7.2 and later, you can specify a cluster size
       for ODS-2 volumes smaller than allowed by the ODS-2 formula;
       however, if you try to mount this volume on a system running
       a version prior to 7.2, the mount fails with the following
       error:

         %MOUNT-F-FILESTRUCT, unsupported file structure level

       If you choose the default during the initialization of an
       ODS-2 disk, your disk can be mounted on prior versions of
       OpenVMS.

    For ODS-1 disks, the cluster size must always be 1.

                                   NOTE

       If you specify /LIMIT and do not specify a value for
       /CLUSTER_SIZE, a value of /CLUSTER_SIZE=16 is used.

3.4    /DATA_CHECK

       /DATA_CHECK[=(option[,...])]

    Checks all read and write operations on the disk. By default,
    no data checks are made. Specify one or both of the following
    options:

    READ    Checks all read operations.

    WRITE   Checks all write operations; default if only the /DATA_
            CHECK qualifier is specified.

    To override the checking you specify at initialization for disks,
    enter a MOUNT command to mount the volume.

3.5    /DENSITY

       /DENSITY=density-value

    Allows you to specify the format density value for certain tapes
    and disks.

    For magnetic tape volumes, specifies the density in bits per inch
    (bpi) at which the magnetic tape is to be written. The density
    value specified can be 800 bpi, 1600 bpi, or 6250 bpi, as long as
    the density is supported by the magnetic tape drive.

    If you do not specify a density value for a blank magnetic tape,
    the system uses a default density of the highest value allowed
    by the tape drive. If the drive allows 6250-, 1600-, and 800-bpi
    operation, the default density is 6250 bpi.

    If you do not specify a density value for a magnetic tape that
    has been previously written, the system uses the density of the
    first record on the volume. If the record is unusually short, the
    density value will not default.

    The /DENSITY qualifier does not apply to any TF tape device.

    Valid tape density values are:

    Keyword     Meaning

    DEFAULT     Default density
    800         NRZI 800 bits per inch (BPI)
    1600        PE 1600 BPI
    6250        GRC 6250 BPI
    3480        IBM 3480 HPC 39872 BPI
    3490E       IBM 3480 compressed
    833         DLT TK50: 833 BPI
    TK50        DLT TK50: 833 BPI
    TK70        DLT TK70: 1250 BPI
    6250        RV80 6250 BPI EQUIVALENT
    NOTE: Only the keywords above are understood by TMSCP/TUDRIVER
    code prior to OpenVMS Version 7.2. The remaining keywords in this
    table are supported only on Alpha systems.
    TK85        DLT Tx85: 10625 BPI - Cmpt III - Alpha/Integrity
                servers only
    TK86        DLT Tx86: 10626 BPI - Cmpt III - Alpha/Integrity
                servers only
    TK87        DLT Tx87: 62500 BPI - Cmpt III - Alpha/Integrity
                servers only
    TK88        DLT Tx88: (Quantum 4000) - Cmpt IV - Alpha/Integrity
                servers only
    TK89        DLT Tx89: (Quantum 7000) - Cmpt IV - Alpha/Integrity
                servers only
    QIC         All QIC drives are drive-settable only -
                Alpha/Integrity servers only
    8200        Exa-Byte 8200 - Alpha/Integrity servers only
    8500        Exa-Byte 8500 - Alpha/Integrity servers only
    DDS1        Digital Data Storage 1 - 2G - Alpha/Integrity servers
                only
    DDS2        Digital Data Storage 2 - 4G - Alpha/Integrity servers
                only
    DDS3        Digital Data Storage 3 - 8-10G - Alpha/Integrity
                servers only
    DDS4        Digital Data Storage 4 - Alpha/Integrity servers only
    AIT1        Sony Advanced Intelligent Tape 1 - Alpha/Integrity
                servers only
    AIT2        Sony Advanced Intelligent Tape 2 - Alpha/Integrity
                servers only
    AIT3        Sony Advanced Intelligent Tape 3 - Alpha/Integrity
                servers only
    AIT4        Sony Advanced Intelligent Tape 4 - Alpha/Integrity
                servers only
    DLT8000     DLT 8000 - Alpha/Integrity servers only
    8900        Exabyte 8900 - Alpha/Integrity servers only
    SDLT        SuperDLT1 - Alpha/Integrity servers only
    SDLT320     SuperDLT320 - Alpha/Integrity servers only

    Note that tape density keywords cannot be abbreviated.

    To format a diskette on RXnn diskette drives, use the
    INITIALIZE/DENSITY command. Specify the density at which the
    diskette is to be formatted as follows:

    Keyword     Meaning

    single      RX01 - 8 inch
    double      RX02 - 8 inch
    dd          double density: 720K - 3 1/2 inch
    hd          high density: 1.44MB - 3 1/2 inch
    ed          extended density: 2.88MB - 3 1/2 inch

    If you do not specify a density value for a diskette being
    initialized on a drive, the system leaves the volume at the
    density to which the volume was last formatted.

                                   NOTE

       RX33 diskettes cannot be read from or written to by RX50
       disk drives. RX50 diskettes can be read from and written to
       by RX33 disk drives; they cannot be formatted by RX33 disk
       drives.

3.6    /DIRECTORIES

       /DIRECTORIES=number-of-entries

    The effect of this qualifier depends on the disk structure:

    o  For ODS-1, /DIRECTORIES allows space for the specified number
       of directory entries to be reserved in 000000.DIR (the MFD).

    o  For ODS-2 and ODS-5, /DIRECTORIES allows the initial size of
       the MFD to be set. The specified number is divided by 16, to
       produce the number of blocks to preallocate. This number is
       then rounded up to a whole number of clusters.

    The number-of-entries value must be an integer between 16 and
    16000. The default value is 16.

3.7    /ERASE

       /ERASE[=keyword]
       /NOERASE (default)

    Specifies whether to perform a data security erase (DSE) and, on
    disk volumes only, whether to set the volume characteristic to
    ERASE_ON_DELETE.

    The /ERASE qualifier applies to Files-11 On-Disk Structure
    Level 2 (ODS-2) and Level 5 (ODS-5) disks and ANSI magnetic tape
    volumes, and is valid for magnetic tape devices that support the
    hardware erase function, such as TU78 and MSCP magnetic tapes.

    For tape volumes, /ERASE physically destroys deleted data by
    writing over it.

    For disk volumes, when /ERASE is specified with no keywords, this
    command does the following:

    o  Performs a data security erase (DSE) by writing the system-
       specified erase pattern into every block on the volume before
       initializing it. The amount of time taken by the DSE operation
       depends on the volume size.

    o  Sets the volume characteristic to ERASE_ON_DELETE so that each
       file on the volume will be erased by a DSE when it is deleted.

    For disk volumes, two optional keywords allow you to
    independently specify just one of the actions noted above.

    o  /ERASE=INIT

       Performs a data security erase (DSE) operation on the
       volume before initializing it, but does not set the volume
       characteristic to ERASE_ON_DELETE. This operation takes longer
       than specifying /ERASE=DELETE and is equivalent to performing
       SET VOLUME/NOERASE_ON_DELETE.

    o  /ERASE=DELETE

       Sets the ERASE_ON_DELETE volume characteristic, but does not
       perform a DSE operation on the disk.

    If neither (or both) keywords are specified, both actions are
    performed. That is, /ERASE is equivalent to /ERASE=(INIT,DELETE).

3.8    /EXTENSION

       /EXTENSION=number-of-blocks

    Specifies, for disk volumes, the number of blocks to use as a
    default extension size for all files on the volume. The extension
    default is used when a file increases to a size greater than its
    initial default allocation during an update. For Files-11 On-Disk
    Structure Level 2 and Level 5 disks, the value for the number-
    of-blocks parameter can range from 0 to 65,535. The default value
    is 5. For Files-11 On-Disk Structure Level 1 disks, the value can
    range from 0 to 255.

    The OpenVMS operating system uses the default volume extension
    only if no different extension has been set for the file and no
    default extension has been set for the process by using the SET
    RMS_DEFAULT command.

3.9    /FILE_PROTECTION

       /FILE_PROTECTION=code

    Affects Files-11 On-Disk Structure Level 1 (ODS-1) disks only.

    Defines for disk volumes the default protection to be applied to
    all files on the volume.

    Specify the code according to the standard syntax rules described
    in the VSI OpenVMS Guide to System Security. Any attributes not
    specified are taken from the current default protection.

    Note that this attribute is not used when the volume is
    being used on an OpenVMS system, but is provided to control
    the process's use of the volume on RSX-11M systems. OpenVMS
    systems always use the default file protection. Use the
    SET PROTECTION/DEFAULT command to change the default file
    protection.

3.10    /GPT

       /GPT (default for Integrity servers)
       /NOGPT (default for Alpha)

    Applies to Files-11 On-Disk Structure Level 2 (ODS-2) and Level 5
    (ODS-5) disks only.

                                   NOTE

       If you specify /GPT, the disk might not mount on some
       systems running older versions of OpenVMS.

    When /GPT is specified, the system file [000000]GPT.SYS is
    created. GPT.SYS contains partition/boot information needed
    by the IA64 console software. (GPT is an abbreviation for GUID
    Partition Table, where GUID stands for Global Unique Identifier.)

    The BACKUP utility recognizes GPT.SYS and maintains its contents
    in a save/restore operation.

    If /NOGPT is specified, the pre-Version 8.2 VBN layout of
    [000000]INDEXF.SYS is used. The VBN layout is described in
    the Guide to OpenVMS File Applications and in VMS File System
    Internals by Kirby McCoy (ISBN 1-55558-056-4, 1990).

3.11    /GROUP

    Used in conjunction with the /NOSHARE qualifier to create
    a group volume. The group volume allows access by system
    (S),  owner (O), and group (G)  accessors. The protection is
    (S:RWCD,O:RWCD,G:RWCD,W).

    The owner user identification code (UIC) of the volume defaults
    to your group number and a member number of 0.

3.12    /HEADERS

       /HEADERS=number-of-headers

    Specifies, for disk volumes, the number of file headers to be
    allocated for the index file. The minimum and default value
    is 16. The maximum is the value set with the /MAXIMUM_FILES
    qualifier. However, if /LIMIT is specified and no value is
    specified for /HEADERS or /MAXIMUM_FILES, the following defaults
    apply:

    o  /MAXIMUM_FILES: 16711679 files

    o  /HEADERS: 0.5 percent of the size of the current device
       MAXBLOCK (an F$GETDVI item code)

       For example, for a 33GB disk, the default number of
       preallocated header blocks would be approximately 355000.

    /HEADERS is useful when you want to create a number of files
    and want to streamline the process of allocating space for that
    number of file headers. If you do not specify this qualifier, the
    file system dynamically allocates space as it is needed for new
    headers on the volume.

                                   NOTE

       The default value for the /HEADERS qualifier is generally
       insufficient for ODS-2 and ODS-5 disks. To improve
       performance and avoid SYSTEM-F-HEADERFULL errors, VSI
       recommends that you set this value to be approximately the
       number of files that you anticipate having on your disk;
       however, grossly overestimating this value will result in
       wasted disk space.

    The /HEADERS qualifier controls how much space is initially
    allocated to INDEXF.SYS for headers. Each file on a disk requires
    at least one file header and each header occupies one block
    within INDEXF.SYS. Files that have many Access Control Entries
    (ACE) or are very fragmented may use more than one header.

    The default value of 16 leaves room for less than 10 files to be
    created before INDEXF.SYS must extend; therefore, try to estimate
    the total number of files that will be created on the disk and
    specify it here. This will improve disk access performance.
    Overestimating the value may lead to wasted disk space. This
    value cannot be changed without reinitializing the volume.

    INDEXF.SYS is limited as to how many times it may extend. When
    the map area in its header (where the retrieval pointers are
    stored) becomes full, file creation fails with the message
    "SYSTEM-W-HEADERFULL."

3.13    /HIGHWATER

       /HIGHWATER (default)
       /NOHIGHWATER

    Applies to Files-11 On-Disk Structure Level 2 (ODS-2) and Level 5
    (ODS-5) disks only.

    Sets the file high-water mark (FHM) volume attribute, which
    guarantees that users cannot read data that they have not
    written. You cannot specify the /NOHIGHWATER qualifier for
    magnetic tape.

    The /NOHIGHWATER qualifier disables FHM for a disk volume.

3.14    /HOMEBLOCKS

       /HOMEBLOCKS=option

    Applies to Files-11 On-Disk Structure Level 2 (ODS-2) and Level 5
    (ODS-5) disks only.

    Specifies where the volume's homeblock and spare copy of the
    homeblock are placed on disk. The value of option can be one of
    the following:

    o  GEOMETRY

       Causes the homeblocks to be placed at separate locations on
       disk, to protect against failure of a disk block. Placement
       depends on the reported geometry of the disk.

    o  FIXED (default)

       Causes the homeblocks to be placed at separate fixed locations
       on the disk. Placement is independent of the reported geometry
       of the disk. This caters to disks that report different
       geometries according to which type of controller they are
       attached to.

    o  CONTIGUOUS

       Causes the homeblocks to be placed contiguously at the start
       of the disk. When used with the /INDEX=BEGINNING qualifier,
       this setting allows container file systems to maximize the
       amount of contiguous space on the disk, for example, to hold
       one large file, such as a database.

3.15    /INDEX

       /INDEX=position

    Specifies the location of the index file for the volume's
    directory structure. Possible positions are as follows:

    BEGINNING  Beginning of the volume
    MIDDLE     Middle of the volume (default)
    END        End of the volume
    BLOCK:n    Beginning of the logical block specified by n

3.16    /INTERCHANGE

    Specifies that the magnetic tape will be used for interchange in
    a heterogeneous vendor environment. The /INTERCHANGE qualifier
    omits the ANSI VOL2 labels. Under OpenVMS, the ANSI VOL2 labels
    contain OpenVMS specific security attributes.

    For more information on the /INTERCHANGE qualifier and on
    magnetic tape labeling and tape interchange, see the VSI OpenVMS
    System Manager's Manual, Volume 1: Essentials.

3.17    /LABEL

       /LABEL=option

    Defines characteristics for the magnetic tape volume label, as
    directed by the included option. The available options are as
    follows:

    o  OWNER_IDENTIFIER:"(14 ANSI characters)"

       Allows you to specify the Owner Identifier field in the
       volume label. The field specified can accept up to 14 ANSI
       characters.

    o  VOLUME_ACCESSIBILITY:"character"

       Specifies the character to be written in the volume
       accessibility field of the OpenVMS ANSI volume label VOL1
       on an ANSI magnetic tape. The character may be any valid
       ANSI "a" character. This set of characters includes numeric
       characters, uppercase letters, and any one of the following
       nonalphanumeric characters:

       ! " % ' ( ) * + , - . / : ; < = > ?

       By default, the OpenVMS operating system provides a routine
       that checks this field in the following manner:

       o  If the magnetic tape was created on a version of the
          OpenVMS operating system that conforms to Version 3
          of ANSI, then this option must be used to override any
          character other than an ASCII space.

       o  If a protection is specified and the magnetic tape conforms
          to an ANSI standard that is later than Version 3, then this
          option must be used to override any character other than an
          ASCII 1.

       If you specify any character other than the default, you
       must specify the /OVERRIDE=ACCESSIBILITY qualifier on the
       INITIALIZE and MOUNT commands in order to access the magnetic
       tape.

3.18    /LIMIT

       /LIMIT[=n]

    Applies to Files-11 On-Disk Structure Level 2 (ODS-2) and Level 5
    (ODS-5) disks only.

    Specifies that the volume should be initialized with volume
    expansion. n defines the maximum growth potential of the volume
    in blocks. If no value is specified, the maximum expansion
    potential is set up.

    The maximum value depends on the value specified for /CLUSTER_
    SIZE:

    /CLUSTER_SIZE   8  1TB of expansion is set up.
    /CLUSTER_SIZE < 8  Expansion limit is set to
                       65535*4096*Cluster_value because the maximum
                       size of the bitmap is 65535 blocks.

    For more information about volume expansion, see the VSI Volume
    Shadowing for OpenVMS manual.

    The minimum allowed value is the largest of the following values:

    o  The value supplied with /LIMIT

    o  The physical disk size

    o  The size resulting from a 256-block BITMAP.SYS file (that is,
       256 * 4096 bits/block * Disk Cluster Value)

    If a value less than the minimum is supplied, the value is
    increased to the minimum. This value is displayed (in blocks) as
    the "Expansion Size Limit" in the output from a SHOW DEVICE/FULL
    command.

                                   NOTE

       If you specify /LIMIT and do not explicitly set a value for
       the following parameters, the defaults for these parameters
       are set as follows:

       o  /CLUSTER_SIZE: 16

       o  /MAXIMUM_FILES: 16711679 files

       o  /HEADERS: 0.5 percent of the size of the current device
          MAXBLOCK (an F$GETDVI item code)

          For example, for a 33GB disk, the default number of
          preallocated header blocks would be approximately 355000.

3.19    /MAXIMUM_FILES

       /MAXIMUM_FILES=n

    Restricts the maximum number of files that the volume can
    contain. The /MAXIMUM_FILES qualifier overrides the default
    value, which is calculated as follows:

    (volume size in blocks)/((cluster factor + 1) * 2)

                                   NOTE

       If /LIMIT is specified and no value is set for /MAXIMUM_
       FILES, the default is 16711679 files.

    The maximum size you can specify for any volume is as follows:

    (volume size in blocks)/(cluster factor + 1)

    The minimum value is 0. Note that the maximum can be increased
    only by reinitializing the volume.

                                   NOTE

       The /MAXIMUM_FILES qualifier does not reserve or create
       space for new file headers on a volume. The file system
       dynamically allocates space as it is needed for new headers.

3.20    /MEDIA_FORMAT

       /MEDIA_FORMAT=[NO]COMPACTION

    Controls whether data records are automatically compacted and
    blocked together on any device that supports data compaction.
    Data compaction and record blocking increase the amount of data
    that can be stored on a single tape cartridge.

    Note that once data compaction or noncompaction has been selected
    for a given cartridge, that same status applies to the entire
    cartridge.

3.21    /OVERRIDE

       /OVERRIDE=(option[,...])

    Requests the INITIALIZE command to ignore data on a magnetic tape
    volume that protects it from being overwritten. You can specify
    one or more of the following options:

    ACCESSIBILITY   (For magnetic tapes only.) If the installation
                    allows, this option overrides any character
                    in the Accessibility field of the volume. The
                    necessity of this option is defined by the
                    installation. That is, each installation has the
                    option of specifying a routine that the magnetic
                    tape file system will use to process this field.
                    By default, OpenVMS provides a routine that
                    checks this field in the following manner. If the
                    magnetic tape was created on a version of OpenVMS
                    that conforms to Version 3 of ANSI, this option
                    must be used to override any character other than
                    an ASCII space. If a protection is specified and
                    the magnetic tape conforms to an ANSI standard
                    that is higher than Version 3, this option must
                    be used to override any character other than an
                    ASCII 1. To use the ACCESSIBILITY option, you
                    must have the user privilege VOLPRO or be the
                    owner of the volume.

    EXPIRATION      (For magnetic tapes only.) Allows you to write
                    to a tape that has not yet reached its expiration
                    date. You must have the user privilege VOLPRO
                    to override volume protection, or your UIC must
                    match the UIC written on the volume.

    OWNER_          Allows you to override the processing of the
    IDENTIFIER      Owner Identifier field of the volume label.

    If you specify only one option, you can omit the parentheses.

    To initialize a volume that was initialized previously with the
    /PROTECTION qualifier, your UIC must match the UIC written on the
    volume or you must have VOLPRO privilege.

    You can initialize a volume previously initialized with
    /PROTECTION if you have control access.

3.22    /OWNER_UIC

       /OWNER_UIC=uic

    Specifies an owner user identification code (UIC) for the volume.
    The default is your default UIC. Specify the UIC using standard
    UIC format as described in the VSI OpenVMS Guide to System
    Security.

    For magnetic tapes, no UIC is written unless protection on the
    magnetic tape is specified. If protection is specified, but no
    owner UIC is specified, your current UIC is assigned ownership of
    the volume.

3.23    /PROTECTION

       /PROTECTION=(ownership[:access][,...])

    Applies the specified protection to the volume:

    o  Specify the ownership parameter as system (S),  owner (O),
       group (G),  or world (W).

    o  Specify the access parameter as read (R),  write (W), create
       (C),  or delete (D).

    The default is your default protection. Note that the /GROUP,
    /SHARE, and /SYSTEM qualifiers can also be used to define
    protection for disk volumes.

    For magnetic tape, the protection code is written to an OpenVMS
    specific volume label. The system applies only read (R)  and
    write (W)  access restrictions; create and delete (D) access are
    meaningless. Moreover, the system and the owner are always given
    both read (R)  and write (W) access to magnetic tapes, regardless
    of the protection code you specify.

    For more information on specifying protection code, see the VSI
    OpenVMS Guide to System Security. Any attributes not specified
    are taken from the current default protection.

    When you specify a protection code for an entire disk volume, the
    access type E (execute) indicates create access.

3.24    /SHADOW

       /SHADOW=(device_name_1, device_name_2, device_name_3) label
       (Alpha/Integrity servers only)

    Initializes multiple members of a future shadow set. Initializing
    multiple members in this way eliminates the requirement of a full
    copy when you later create a shadow set.

    When both the /SHADOW and /ERASE qualifiers are specified, the
    INITIALIZE command performs the following operations:

    o  Formats up to six devices with one command, so that any three
       can be subsequently mounted together as members of a new host-
       based shadow set

    o  Writes a label on each volume

    o  Deletes all information from the devices except for the system
       files and leaves each device with identical file structure
       information. All former contents of the disks are lost.

    VSI strongly recommends that you use the /ERASE qualifier. When
    /ERASE is specified, a merge operation is substantially reduced.
    However, using /ERASE has two side effects that are important
    considerations for volume shadowing: the setting of the ERASE
    volume attribute and the time it takes to initialize a volume
    using /ERASE.

    If /ERASE is specified with /SHADOW, the disks are erased
    sequentially, which effectively doubles or triples the time
    it takes for the command to complete. If the disks are large,
    consider performing multiple, simultaneous INITIALIZE/ERASE
    commands (without /SHADOW) to erase the disks. Once all of
    those commands have completed, then execute an INITIALIZE/SHADOW
    command (without /ERASE).

    Once you have initialized your devices using /ERASE and /SHADOW,
    you can then mount up to three of these devices as members of a
    new host-based shadow set.

    Note that the INITIALIZE/SHADOW command should not be used to
    initialize a disk to be added to an existing shadow set, as no
    benefit is gained.

    For more information about volume shadowing, see the VSI Volume
    Shadowing for OpenVMS manual.

3.25    /SHARE

       /SHARE (default)
       /NOSHARE

    Permits all categories of access by all categories of ownership.
    The /NOSHARE qualifier denies access to group (unless the /GROUP
    qualifier is also specified) and world processes.

3.26    /SIZE

       /SIZE=n

    When /SIZE=n is specified for a magnetic disk, n specifies the
    size (in blocks) of the logical volume (the space available for
    the file system). This allows you to INITIALIZE a disk with a
    file system size that is less than the physical volume size,
    which can be useful if you plan to create a shadow set using this
    disk and a smaller physical disk. The value of n is displayed
    (in blocks) as "Logical Volume Size" in the output from a SHOW
    DEVICE/FULL command.

    For DECram disks, /SIZE specifies the size (in blocks) of the
    disk (device type DT$_RAM_DISK) to be allocated from available
    memory. The size of the device is created at disk initialization
    time.

    To deallocate space, specify /SIZE=0. All resources specifically
    allocated to the DECram disk are returned to the system.

    Note that n cannot exceed 524,280 blocks on versions of DECram
    prior to Version 2.3. DECram Version 2.3 running on an Alpha
    system supports up to 67,108,864 blocks, equivalent to 32GB.

3.27    /STRUCTURE

       /STRUCTURE=level

    Specifies whether the volume should be formatted in Files-11
    On-Disk Structure Level 1, 2 (the default), or 5.

    Structure Level 1 is incompatible with the /DATA_CHECK and
    /CLUSTER_SIZE qualifiers. The default protection for a Structure
    Level 1 disk is full access to system, owner, and group, and read
    (R) access to all other users.

    Note that Alpha does not support ODS-1 disks, and specifying 1 on
    Alpha results in an error.

    See the VSI OpenVMS System Manager's Manual, Volume 1: Essentials
    for more information about ODS-5 disks.

3.28    /SYSTEM

    Requires a system UIC or SYSPRV (system privilege) privilege.

    Defines a system volume. The owner UIC defaults to [1,1].
    Protection defaults to complete access by all ownership
    categories, except that only system processes can create top-
    level directories.

3.29    /USER_NAME

       /USER_NAME=name

    Specifies a user name to be associated with the volume. The name
    must be 1 to 12 alphanumeric characters. The default is your user
    name.

3.30    /VERIFIED

       /VERIFIED
       /NOVERIFIED

    Indicates whether the disk has bad block data on it. Use the
    /NOVERIFIED qualifier to ignore bad block data on the disk. The
    default is the /VERIFIED qualifier for disks with 4096 blocks or
    more and the /NOVERIFIED qualifier for disks with less than 4096
    blocks.

3.31    /VOLUME_CHARACTERISTICS

       /VOLUME_CHARACTERISTICS=([[NO]HARDLINKS,] [[NO]ACCESS_
       DATES[=delta-time]],[NO]SPECIAL_FILES)

    Applies to Files-11 On-Disk Structure Level 5 (ODS-5) disks only.

    Enables or disables hardlinks and automatic updates of access
    dates on ODS-5 volumes.

    The default value for delta-time is 1 second, chosen to comply
    with the "seconds since EPOCH" time interface required by
    POSIX st_atime. A site can choose a larger delta time to reduce
    overhead if 1-second granularity is not required.

    Note that the NOACCESS_DATES option affects only the node on
    which the command is issued. Other nodes are not affected by the
    change until the next time the volume is mounted.

    See the Guide to OpenVMS File Applications for additional
    information.

    The volume characteristic [SPECIAL_FILES] allows you to disable
    symlinks. This eliminates file access failure audits that may
    occur due to symlinks being enabled for all processes in the
    current implementation.

3.32    /WINDOWS

       /WINDOWS=n

    Specifies the number of mapping pointers (used to access data in
    the file) to be allocated for file windows. The value can be an
    integer in the range of 7 to 80. The default is 7.

4  –  Examples

    1.$ INITIALIZE/USER_NAME=CPA $FLOPPY1 ACCOUNTS

      Initializes the volume on $FLOPPY1, labels the volume ACCOUNTS,
      and gives the volume a user name of CPA.

    2.$ ALLOCATE DMA2:  TEMP
        _DMA2: ALLOCATED
      $ INITIALIZE  TEMP:  BACK_UP_FILE
      $ MOUNT  TEMP:  BACK_UP_FILE
      %MOUNT-I-MOUNTED, BACK_UP_FILE mounted on _DMA2:
      $ CREATE/DIRECTORY  TEMP:[GOLDSTEIN]

      This sequence of commands shows how to initialize an RK06/RK07
      volume. First, the device is allocated, to ensure that no
      one else can access it. Then, when the volume is physically
      mounted on the device, the INITIALIZE command initializes
      it. When the volume is initialized, the MOUNT command makes
      the file structure available. Before you can place any files
      on the volume, you must create a directory, as shown by the
      CREATE/DIRECTORY command.

    3.$ ALLOCATE MT:
        _MTB1:  ALLOCATED
      $ INITIALIZE MTB1:  SOURCE
      $ MOUNT MTB1:  SOURCE
      %MOUNT-I-MOUNTED, SOURCE mounted on _MTB1:
      $ COPY *.FOR  MTB1:
      $ DIRECTORY MTB1:
         .
         .
         .
      $ DISMOUNT MTB1:

      These commands show the procedure necessary to initialize a
      magnetic tape. After allocating a drive, the magnetic tape is
      loaded on the device, and the INITIALIZE command writes the
      label SOURCE on it. Then, the MOUNT command mounts the magnetic
      tape so that files can be written on it.

    4.$ BACKUP filespec MUA0: ... /MEDIA_FORMAT=NOCOMPACTION-
      _$/REWIND

      This example creates a BACKUP tape with compaction and record
      blocking disabled.

    5.$ INITIALIZE/ERASE/SHADOW=($4$DKA1300, $4$DKA1301) NONVOLATILE

      $MOUN/SYS DSA42 /SHAD=( $4$DKA1300 , $4$DKA1301 ) NONVOLATILE
      %MOUNT-I-MOUNTED, NONVOLATILE MOUNTED ON _DSA42:
      %MOUNT-I-SHDWMEMSUCC, _$4$DKA1300: (WILD3) IS NOW A VALID MEMBER OF THE SHADOW SET
      %MOUNT-I-SHDWMEMSUCC, _$4$DKA1301: (WILD4) IS NOW A VALID MEMBER OF THE SHADOW SET
      $SHO DEV DSA42:

      DEVICE              DEVICE          ERROR    VOLUME         FREE  TRANS MNT
       NAME               STATUS          COUNT     LABEL        BLOCKS COUNT CNT
      DSA42:              MOUNTED             0  NONVOLATILE    5799600     1   1
      $4$DKA1300: (WILD3) SHADOWSETMEMBER     0  (MEMBER OF DSA42:)
      $4$DKA1301: (WILD4) SHADOWSETMEMBER     0  (MEMBER OF DSA42:)

      This example shows correct use of the INITIALIZE/ERASE/SHADOW
      command. Note that the command specifies multiple devices on
      the same line.

5    /QUEUE

    Creates or initializes queues. You use this command to create
    queues and to assign them names and options. The /BATCH qualifier
    is required to create a batch queue.

    Requires OPER (operator) privilege to create queues and manage
    (M) access to modify queues.

    Format

      INITIALIZE/QUEUE  queue-name[:]

5.1  –  Parameter

 queue-name[:]

    Specifies the name of an execution queue or a generic queue. The
    queue name may be a string of 1 to 31 characters. The character
    string can include any uppercase and lowercase letters, digits,
    the dollar sign ($),  and the underscore (_), and must include at
    least one alphabetic character.

5.2  –  Qualifiers

5.2.1    /AUTOSTART_ON

       /AUTOSTART_ON=(node::[device][,...])

    Designates the queue as an autostart execution queue and
    specifies the node, or node and device, on which the queue can
    be located. For batch queues, only node is applicable.

    In a cluster, you can specify more than one node (or node and
    device) on which a queue can run, in the preferred order in which
    nodes should claim the queue. This allows the queue to fail over
    to another node if the node on which the queue is running leaves
    the cluster.

    When you enter the INITIALIZE/QUEUE command with the /AUTOSTART_
    ON qualifier, you must initially activate the queue for
    autostart, either by specifying the /START qualifier with the
    INITIALIZE/QUEUE command or by entering a START/QUEUE command.
    However, the queue will not begin processing jobs until the
    ENABLE AUTOSTART/QUEUES command is entered for a node on which
    the queue can run.

    This qualifier cannot be used in conjunction with the /ON
    or /GENERIC qualifier. However, if you are reinitializing an
    existing queue, you can specify the /AUTOSTART_ON qualifier for a
    queue previously created or started with the /ON qualifier. Doing
    so overrides the /ON qualifier and makes the queue an autostart
    queue.

    For more information about autostart queues, see the chapter
    about queues in VSI OpenVMS System Manager's Manual, Volume 1:
    Essentials.

5.2.2    /BASE_PRIORITY

       /BASE_PRIORITY=n

    Specifies the base process priority at which jobs are initiated
    from a batch execution queue. By default, if you omit the
    qualifier, jobs are initiated at the same priority as the base
    priority established by DEFPRI at system generation (usually 4).
    The base priority specifier can be any decimal value from 0 to
    15.

    You also can specify this qualifier for an output execution
    queue. In this context the /BASE_PRIORITY qualifier establishes
    the base priority of the symbiont process when the symbiont
    process is created.

5.2.3    /BATCH

       /BATCH
       /NOBATCH (default)

    Specifies that you are initializing a batch queue. If you
    are reinitializing an existing queue, you can use the /BATCH
    qualifier only if the queue was created as a batch queue.

    A batch queue is classified as either an execution queue or a
    generic queue. By default, the /BATCH qualifier initializes
    an execution queue. To specify a generic batch queue, use the
    /GENERIC qualifier together with the /BATCH qualifier.

    The /BATCH and /DEVICE qualifiers are mutually exclusive; the
    /NOBATCH and /NODEVICE qualifiers cannot be used together.

5.2.4    /BLOCK_LIMIT

       /BLOCK_LIMIT=([lowlim,]uplim)
       /NOBLOCK_LIMIT (default)

    Limits the size of print jobs that can be processed on an output
    execution queue. The /BLOCK_LIMIT qualifier allows you to reserve
    certain printers for certain size jobs. You must specify at least
    one of the parameters.

    The lowlim parameter is a decimal number referring to the minimum
    number of blocks accepted by the queue for a print job. If
    a print job is submitted that contains fewer blocks than the
    lowlim value, the job remains pending until the block limit for
    the queue is changed. After the block limit for the queue is
    decreased sufficiently, the job is processed.

    The uplim parameter is a decimal number referring to the maximum
    number of blocks that the queue accepts for a print job. If a
    print job is submitted that exceeds this value, the job remains
    pending until the block limit for the queue is changed. After the
    block limit for the queue is increased sufficiently, the job is
    processed.

    If you specify only an upper limit for jobs, you can omit the
    parentheses. For example, /BLOCK_LIMIT=1000 means that only jobs
    with 1000 blocks or less are processed in the queue. To specify
    only a lower job limit, you must use a null string ("")  to
    indicate the upper specifier. For example, /BLOCK_LIMIT=(500,"")
    means any job with 500 or more blocks is processed in the queue.
    You can specify both a lower and upper limit. For example,
    /BLOCK_LIMIT=(200,2000) means that jobs with less than 200 blocks
    or more than 2000 blocks are not processed in the queue.

    The /NOBLOCK_LIMIT qualifier cancels the previous setting
    established by the /BLOCK_LIMIT qualifier for that queue.

5.2.5    /CHARACTERISTICS

       /CHARACTERISTICS=(characteristic[,...])
       /NOCHARACTERISTICS (default)

    Specifies one or more characteristics for processing jobs on
    an execution queue. If you specify only one characteristic,
    you can omit the parentheses. If a queue does not have all the
    characteristics that have been specified for a job, the job
    remains pending. Each time you specify the /CHARACTERISTICS
    qualifier, all previously set characteristics are cancelled. Only
    the characteristics specified with the qualifier are established
    for the queue.

    Queue characteristics are installation specific. The
    characteristic parameter can be either a value from 0 to
    127 or a characteristic name that has been defined by the
    DEFINE/CHARACTERISTIC command.

    The /NOCHARACTERISTICS qualifier cancels any settings previously
    established by the /CHARACTERISTICS qualifier for that queue.

5.2.6    /CLOSE

    Prevents jobs from being entered in the queue through PRINT or
    SUBMIT commands or as a result of requeue operations. To allow
    jobs to be entered, use the /OPEN qualifier. Whether a queue
    accepts or rejects new job entries is independent of the queue's
    state (such as paused, stopped, or stalled). When a queue is
    marked closed, jobs executing continue to execute. Jobs pending
    in the queue continue to be candidates for execution.

5.2.7    /CPUDEFAULT

       /CPUDEFAULT=time

    Defines the default CPU time limit for all jobs in this batch
    execution queue. You can specify time as delta time, 0, INFINITE,
    or NONE (default). You can specify up to 497 days of delta time.

    If the queue does not have a specified CPUMAXIMUM time limit and
    the value established in the user authorization file (UAF) has
    a specified CPU time limit of NONE, either the value 0 or the
    keyword INFINITE allows unlimited CPU time. If you specify NONE,
    the CPU time value defaults to the value specified either in the
    UAF or by the SUBMIT command (if included). CPU time values must
    be greater than or equal to the number specified by the system
    parameter PQL_MCPULM. The time cannot exceed the CPU time limit
    set by the /CPUMAXIMUM qualifier. For information on specifying
    delta time, see the OpenVMS User's Manual or the online help
    topic Date.

5.2.8    /CPUMAXIMUM

       /CPUMAXIMUM=time

    Defines the maximum CPU time limit for all jobs in a batch
    execution queue. You can specify time as delta time, 0, INFINITE,
    or NONE (default). You can specify up to 497 days of delta time.

    The /CPUMAXIMUM qualifier overrides the time limit specified
    in the user authorization file (UAF) for any user submitting a
    job to the queue. Either the value 0 or the keyword INFINITE
    allows unlimited CPU time. If you specify NONE, the CPU time
    value defaults to the value specified either in the UAF or by
    the SUBMIT command (if included). CPU time values must be greater
    than or equal to the number specified by the system parameter
    PQL_MCPULM.

    For information on specifying delta times, see the OpenVMS User's
    Manual or the online help topic Date.

    A CPU time limit for processes is specified by each user record
    in the system UAF. You also can specify the following: a default
    CPU time limit or a maximum CPU time limit for all jobs in a
    given queue, or a default CPU time limit for individual jobs in
    the queue. The following table shows the action taken for each
    value specified and possible combinations of specifications.

                  Default
    CPU Time      CPU Time    Maximum CPU
    Limit         Limit       Time Limit
    Specified by  Specified   Specified
    the SUBMIT    for the     for the
    Command?      Queue?      Queue?        Action Taken

    No            No          No            Use the UAF value.

    Yes           No          No            Use the smaller of SUBMIT
                                            command and UAF values.

    Yes           Yes         No            Use the smaller of SUBMIT
                                            command and UAF values.

    Yes           No          Yes           Use the smaller of SUBMIT
                                            command and queue's
                                            maximum values.

    Yes           Yes         Yes           Use the smaller of SUBMIT
                                            command and queue's
                                            maximum values.

    No            Yes         Yes           Use the smaller of
                                            queue's default and
                                            maximum values.

    No            No          Yes           Use the maximum value.

    No            Yes         No            Use the smaller of UAF
                                            and queue's default
                                            values.

5.2.9    /DEFAULT

       /DEFAULT=(option[,...])
       /NODEFAULT

    Establishes defaults for certain options of the PRINT command.
    Defaults are specified by the list of options. If you specify
    only one option, you can omit the parentheses. After you set an
    option for the queue with the /DEFAULT qualifier, you do not have
    to specify that option in your PRINT command. If you do specify
    these options in your PRINT command, the values specified with
    the PRINT command override the values established for the queue
    with the /DEFAULT qualifier.

    You cannot use the /DEFAULT qualifier with the /GENERIC
    qualifier.

    Possible options are as follows:

    [NO]BURST[=keyword]   Controls whether two file flag pages
                          with a burst bar between them are printed
                          preceding output. If you specify the value
                          ALL (default), these flag pages are printed
                          before each file in the job. If you specify
                          the value ONE, these flag pages are printed
                          once before the first file in the job.

    [NO]FEED              Controls whether a form feed is inserted
                          automatically at the end of a page.

    [NO]FLAG[=keyword]    Controls whether a file flag page is
                          printed preceding output. If you specify
                          the value ALL (default), a file flag page
                          is printed before each file in the job. If
                          you specify the value ONE, a file flag page
                          is printed once before the first file in
                          the job.

    FORM=type             Specifies the default form for an output
                          execution queue. If a job is submitted
                          without an explicit form definition, this
                          form is used to process the job. If no
                          form type is explicitly specified with
                          the FORM keyword, the system assigns the
                          form DEFAULT to the queue. See also the
                          description of the /FORM_MOUNTED=type
                          qualifier.

    [NO]TRAILER[=keyword] Controls whether a file trailer page is
                          printed following output. If you specify
                          the value ALL (default), a file trailer
                          page is printed after each file in the job.
                          If you specify the value ONE, a trailer
                          page is printed once after the last file in
                          the job.

    When you specify the BURST option for a file, the [NO]FLAG option
    does not add or subtract a flag page from the two flag pages that
    are printed preceding the file.

    For information on establishing mandatory queue options, see the
    description of the /SEPARATE qualifier. For more information on
    specifying default queue options, see the chapter on queues in
    the VSI OpenVMS System Manager's Manual.

5.2.10    /DESCRIPTION

       /DESCRIPTION=string
       /NODESCRIPTION (default)

    Specifies a string of up to 255 characters used to provide
    operator-supplied information about the queue.

    Enclose strings containing lowercase letters, blanks, or other
    nonalphanumeric characters (including spaces) in quotation marks
    (" ").

    The /NODESCRIPTION qualifier removes any descriptive text that
    may be associated with the queue.

5.2.11    /DEVICE

       /DEVICE[=option]
       /NODEVICE

    Specifies that you are initializing an output queue of a
    particular type. If you are reinitializing an existing queue,
    you can use the /DEVICE qualifier only if the queue was created
    as an output queue. Possible options are as follows:

    PRINTER     Indicates a printer queue.

    SERVER      Indicates a server queue. A server queue is
                controlled by the user-modified or user-written
                symbiont specified with the /PROCESSOR qualifier.

    TERMINAL    Indicates a terminal queue.

    If you specify the /DEVICE qualifier without a queue type, the
    /DEVICE=PRINTER qualifier is used by default.

    An output queue is classified as either an execution or generic
    queue. By default, the /DEVICE qualifier initializes an execution
    queue of the designated type. To specify a generic printer,
    server, or terminal queue, use the /GENERIC qualifier with the
    /DEVICE qualifier.

    You specify the queue type with the /DEVICE qualifier for
    informational purposes. When an output execution queue is
    started, the symbiont associated with the queue determines
    the actual queue type. The standard symbiont examines device
    characteristics to establish whether the queue should be marked
    as printer or terminal. By convention, user-modified and user-
    written symbionts mark the queue as a server queue. The device
    type of a generic queue need not match the device type of its
    execution queues.

    The /DEVICE and /BATCH qualifiers are mutually exclusive; the
    /NODEVICE and /NOBATCH qualifiers cannot be used together.

5.2.12    /DISABLE_SWAPPING

       /DISABLE_SWAPPING
       /NODISABLE_SWAPPING (default)

    Controls whether batch jobs executed from a queue can be swapped
    in and out of memory.

5.2.13    /ENABLE_GENERIC

       /ENABLE_GENERIC (default)
       /NOENABLE_GENERIC

    Specifies whether files queued to a generic queue that does
    not specify explicit queue names with the /GENERIC qualifier
    can be placed in this execution queue for processing. For more
    information, see the description of the /GENERIC qualifier.

5.2.14    /FORM_MOUNTED

       /FORM_MOUNTED=type

    Specifies the mounted form for an output execution queue.

    If no form type is explicitly specified, the system assigns the
    form DEFAULT to the queue.

    If the stock of the mounted form does not match the stock of the
    default form, as indicated by the /DEFAULT=FORM qualifier, all
    jobs submitted to this queue without an explicit form definition
    enter a pending state and remains pending until the stock of the
    mounted form of the queue is identical to the stock of the form
    associated with the job.

    If a job is submitted with an explicit form and the stock of the
    explicit form is not identical to the stock of the mounted form,
    the job enters a pending state and remains pending until the
    stock of the mounted form of the queue is identical to the stock
    of the form associated with the job.

    To specify the form type, use either a numeric value or a form
    name that has been defined by the DEFINE/FORM command. Form
    types are installation-specific. You cannot use the /FORM_MOUNTED
    qualifier with the /GENERIC qualifier.

5.2.15    /GENERIC

       /GENERIC[=(queue-name[,...])]
       /NOGENERIC (default)

    Specifies a generic queue. Also specifies that jobs placed in
    this queue can be moved for processing to compatible execution
    queues. The /GENERIC qualifier optionally accepts a list of
    target execution queues that have been previously defined. For a
    generic batch queue, these target queues must be batch execution
    queues. For a generic output queue, these target queues must be
    output execution queues, but can be of any type (printer, server,
    or terminal). For example, a generic printer queue can feed a
    mixture of printer and terminal execution queues.

    If you do not specify any target execution queues with the
    /GENERIC qualifier, jobs can be moved to any execution queue
    that (1)  is initialized with the /ENABLE_GENERIC qualifier, and
    (2)  is the same type (batch or output) as the generic queue.

    To define the queue as a generic batch or output queue, you use
    the /GENERIC qualifier with either the /BATCH or the /DEVICE
    qualifier. If you specify neither /BATCH nor /DEVICE on creation
    of a generic queue, the queue becomes a generic printer queue by
    default.

    You cannot use the /SEPARATE qualifier with the /GENERIC
    qualifier.

5.2.16    /JOB_LIMIT

       /JOB_LIMIT=n

    Indicates the number of batch jobs that can be executed
    concurrently from the queue. Specify a number in the range 1
    to 65535. The job limit default value for n is 1.

5.2.17    /LIBRARY

       /LIBRARY=filename
       /NOLIBRARY

    Specifies the file name for the device control library. When you
    initialize an output execution queue, you can use the /LIBRARY
    qualifier to specify an alternate device control library. The
    default library is SYS$LIBRARY:SYSDEVCTL.TLB. You can use only a
    file name as the parameter of the /LIBRARY qualifier. The system
    always assumes that the file is located in SYS$LIBRARY and that
    the file type is .TLB.

5.2.18    /NAME_OF_MANAGER

       /NAME_OF_MANAGER=name

    Identifies the name of the queue manager to control the queue.
    Once the queue is created, the queue manager assignment may not
    be altered.

    If the /NAME_OF_MANAGER qualifier is omitted, then the default
    name SYS$QUEUE_MANAGER is used.

    If the INITIALIZE/QUEUE command is used to modify a queue, and
    that queue is not controlled by the default queue manager, then
    the name of the controlling queue manager should be specified
    with the /NAME_OF_MANAGER qualifier. Alternately, the logical
    name SYS$QUEUE_MANAGER can be defined to be the correct queue
    manager, making that queue manager the default for the current
    process.

5.2.19    /NO_INITIAL_FF

       /NO_INITIAL_FF
       /NONO_INITIAL_FF (default)

    Allows user to specify whether a form feed should be sent to a
    printer device when a queue starts. To suppress the initial form
    feed, use the /NO_INITIAL_FF qualifier.

    The /NONO_INITIAL_FF qualifier sends a form feed to the output
    device to ensure the paper is at the top of a page before
    printing begins.

5.2.20    /ON

       /ON=[node::]device[:] (printer, terminal, server queue)
       /ON=node:: (batch queue)

    Specifies the node or device, or both, on which this execution
    queue is located. For batch execution queues, you can specify
    only the node name. For output execution queues, you can include
    both the node name and the device name. By default, a queue
    executes on the same node from which you start the queue. The
    default device parameter is the same as the queue name.

    You can specify an IP address and port number, in quotation
    marks, for the device. For more information about specifying
    IP addresses, see the TCP/IP Services for OpenVMS documentation.

    The node name is used in OpenVMS Cluster systems; it must match
    the node name specified by the system parameter SCSNODE for the
    OpenVMS computer on which the queue executes.

    You cannot use the /ON qualifier with the /AUTOSTART_ON or
    /GENERIC qualifier; however, if you are reinitializing an
    existing queue, you can specify the /ON qualifier for a queue
    previously created or started with the /AUTOSTART_ON qualifier.
    Doing so overrides the /AUTOSTART_ON option and makes the queue a
    nonautostart queue.

5.2.21    /OPEN

       /OPEN (default)

    Allows jobs to be entered in the queue through PRINT or SUBMIT
    commands or as the result of requeue operations. To prevent
    jobs from being entered in the queue, use the /CLOSE qualifier.
    Whether a queue accepts or rejects new job entries is independent
    of the queue's state (such as paused, stopped, or stalled).

5.2.22    /OWNER_UIC

       /OWNER_UIC=uic

    Enables you to change the user identification code (UIC) of the
    queue. Specify the UIC by using standard UIC format as described
    in the VSI OpenVMS Guide to System Security. The default UIC is
    [1,4].

5.2.23    /PROCESSOR

       /PROCESSOR=filename
       /NOPROCESSOR

    Allows you to specify your own print symbiont for an output
    execution queue. You can use any valid file name as a parameter
    of the /PROCESSOR qualifier. The system supplies the device and
    directory name SYS$SYSTEM and the file type .EXE. If you use this
    qualifier for an output queue, it specifies that the symbiont
    image to be executed is SYS$SYSTEM:filename.EXE.

    By default, SYS$SYSTEM:PRTSMB.EXE is the symbiont image
    associated with an output execution queue.

    The /NOPROCESSOR qualifier cancels any previous setting
    established with the /PROCESSOR qualifier and causes
    SYS$SYSTEM:PRTSMB.EXE to be used.

5.2.24    /PROTECTION

       /PROTECTION=(ownership[:access],...)

    Specifies the protection of the queue:

    o  Specify the ownership parameter as system (S),  owner (O),
       group (G),  or world (W).

    o  Specify the access parameter as read (R),  submit (S), manage
       (M),  or delete (D).

    A null access specification means no access. The default
    protection is (SYSTEM:M, OWNER:D, GROUP:R, WORLD:S). If you
    include only one protection code, you can omit the parentheses.
    For more information on specifying protection codes, see the
    VSI OpenVMS Guide to System Security. For more information on
    controlling queue operations through UIC-based protection, see
    the chapter on queues in the VSI OpenVMS System Manager's Manual.

5.2.25    /RAD

       /RAD=n

    Specifies the RAD number on which to run batch jobs assigned
    to the queue. The RAD value is validated as a positive integer
    between 0 and the value returned by the $GETSYI item code, SYI$_
    RAD_MAX_RADS.

    RAD is supported on AlphaServer GS series systems and starting
    from OpenVMS Version 8.4, support is extended to NUMA capable
    Integrity servers.

5.2.26    /RECORD_BLOCKING

       /RECORD_BLOCKING (default)
       /NORECORD_BLOCKING

    Determines whether the symbiont can concatenate (or block
    together) output records for transmission to the output device.
    If you specify the /NORECORD_BLOCKING qualifier, the symbiont
    sends each formatted record in a separate I/O request to the
    output device. For the standard OpenVMS print symbiont, record
    blocking can have a significant performance advantage over
    single-record mode.

5.2.27    /RETAIN

       /RETAIN[=option]
       /NORETAIN (default)

    Holds jobs in the queue in a retained state after they have
    executed. The /NORETAIN qualifier enables you to reset the queue
    to the default. Possible options are as follows:

    ALL            Holds all jobs in the queue after execution.
    (default)

    ERROR          Holds in the queue only jobs that complete
                   unsuccessfully.

    A user can request a job retention option for a job by specifying
    the /RETAIN qualifier with the PRINT, SUBMIT, or SET ENTRY
    command; however, the job retention option you specify for a
    queue overrides any job retention option requested by a user for
    a job in that queue.

5.2.28    /SCHEDULE

       /SCHEDULE=SIZE (default)
       /SCHEDULE=NOSIZE

    Specifies whether pending jobs in an output execution queue are
    scheduled for printing based on the size of the job. When the
    default qualifier /SCHEDULE=SIZE is in effect, shorter jobs print
    before longer ones.

    When the /SCHEDULE=NOSIZE qualifier is in effect, jobs are not
    scheduled according to size.

    If you enter this command while there are pending jobs in any
    queue, its effect on future jobs is unpredictable.

5.2.29    /SEPARATE

       /SEPARATE=(option[,...])
       /NOSEPARATE (default)

    Specifies the mandatory queue options, or job separation options,
    for an output execution queue. Job separation options cannot be
    overridden by the PRINT command.

    You cannot use the /SEPARATE qualifier with the /GENERIC
    qualifier.

    The job separation options are as follows:

    [NO]BURST              Specifies whether two job flag pages with
                           a burst bar between them are printed at
                           the beginning of each job.

    [NO]FLAG               Specifies whether a job flag page is
                           printed at the beginning of each job.

    [NO]TRAILER            Specifies whether a job trailer page is
                           printed at the end of each job.

    [NO]RESET=(module[,...]Specifies one or more device control
                           library modules that contain the job reset
                           sequence for the queue. The specified
                           modules from the queue's device control
                           library (by default SYS$LIBRARY:SYSDEVCTL)
                           are used to reset the device at the end
                           of each job. The RESET sequence occurs
                           after any file trailer and before any job
                           trailer. Thus, all job separation pages
                           are printed when the device is in its
                           RESET state.

    When you specify the /SEPARATE=BURST qualifier, the [NO]FLAG
    separation option does not add or subtract a flag page from the
    two flag pages that are printed preceding the job.

    For information on establishing queue options that can be
    overridden, see the description of the /DEFAULT qualifier.

    For more information on specifying mandatory queue options, see
    the chapter on queues in the VSI OpenVMS System Manager's Manual.

5.2.30    /START

       /START
       /NOSTART (default)

    Starts the queue being initialized by the current
    INITIALIZE/QUEUE command.

    For autostart queues, this qualifier activates the queue for
    autostart. The queue begins processing jobs when autostart is
    enabled with the ENABLE AUTOSTART/QUEUES command on any node on
    which the queue can run.

5.2.31    /WSDEFAULT

       /WSDEFAULT=n

    Defines for a batch job a working set default, the default number
    of physical pages that the job can use.

    The value set by this qualifier overrides the value defined in
    the user authorization file (UAF) of any user submitting a job to
    the queue.

    Specify the value of n as a number of 512-byte pagelets on Alpha
    systems. Note that OpenVMS rounds this value up to the nearest
    CPU-specific page so that the actual amount of physical memory
    allowed may be larger than the specified amount on Alpha. For
    further information, see the VSI OpenVMS System Manager's Manual.

    If you specify 0 or NONE, the working set default value defaults
    to the value specified in the UAF or by the SUBMIT command (if it
    includes a WSDEFAULT value).

    You also can specify this qualifier for an output execution
    queue. Used in this context, the /WSDEFAULT qualifier establishes
    the working set default of the symbiont process for an output
    execution queue when the symbiont process is created.

5.2.32    /WSEXTENT

       /WSEXTENT=n

    Defines for the batch job a working set extent, the maximum
    amount of physical memory that the job can use. The job only
    uses the maximum amount of physical memory when the system has
    excess free pages. The value set by this qualifier overrides the
    value defined in the user authorization file (UAF) of any user
    submitting a job to the queue.

    Specify the value of n as a number of 512-byte pagelets on
    Alpha. Note that OpenVMS rounds this value up to the nearest
    CPU-specific page so that the actual amount of physical memory
    allowed may be larger than the specified amount on Alpha.

    If you specify 0 or NONE, the working set extent value defaults
    to the value specified in the UAF or by the SUBMIT command (if it
    includes a WSEXTENT value).

    You also can specify this qualifier for an output execution
    queue. Used in this context, the /WSEXTENT qualifier establishes
    the working set extent of the symbiont process for an output
    execution queue when the symbiont process is created.

5.2.33    /WSQUOTA

       /WSQUOTA=n

    Defines for a batch job a working set quota, the amount of
    physical memory that is guaranteed to the job.

    The value set by this qualifier overrides the value defined in
    the user authorization file (UAF) of any user submitting a job to
    the queue.

    Specify the value of n as a number of 512-byte pagelets on
    OpenVMS Alpha. OpenVMS rounds this value up to the nearest
    CPU-specific page so that the actual amount of physical memory
    allowed may be larger than the specified amount on OpenVMS Alpha.
    For further information, see the VSI OpenVMS System Manager's
    Manual.

    If you specify 0 or NONE, the working set quota value defaults
    to the value specified in the UAF or by the SUBMIT command (if it
    includes a WSQUOTA value).

    You also can specify this qualifier for an output execution
    queue. Used in this context, the /WSQUOTA qualifier establishes
    the working set quota of the symbiont process for an output
    execution queue when the symbiont process is created.

    Working set default, working set quota, and working set extent
    values are included in each user record in the system UAF. You
    can specify working set values for individual jobs or for all
    jobs in a given queue. The decision table shows the action taken
    for different combinations of specifications that involve working
    set values.

    Is the SUBMIT    Is the
    command value    queue value
    specified?       specified?      Action taken

    No               No              Use the UAF value.

    No               Yes             Use value for the queue.

    Yes              Yes             Use smaller of the two values.

    Yes              No              Compare specified value with UAF
                                     value; use the smaller.

5.3  –  Examples

    1.$ INITIALIZE/QUEUE/PROCESSOR=TELNETSYM -
      _$ /ON="192.168.1.101:9100" SYS$PRINT

      This example initializes the SYS$PRINT print queue, specifying
      the TELNETSYM print symbiont, for the printer with the IP
      address 192.168.1.101 at TCP port 9100. For more information
      about TELNETSYM, see the TCP/IP Services for OpenVMS Management
      Guide.

    2.$ INITIALIZE/QUEUE/BATCH/START -
      _$ /AUTOSTART_ON=(DATA::, WARF::, DEANNA::) BATCH_1

      The INITIALIZE/QUEUE command in this example creates the
      batch queue BATCH_1, and designates it as an autostart queue
      capable of executing on node DATA, WARF, or DEANNA. The /START
      qualifier activates the queue for autostart. The queue will
      begin executing on the first node (in the list of nodes
      specified) for which the ENABLE AUTOSTART/QUEUES command is
      entered.

      If the node on which BATCH_1 is executing is taken out of the
      OpenVMS Cluster, the queue will be stopped on that node and
      will fail over to the first available node in the node list
      on which autostart is enabled for a queue manager SYS$QUEUE_
      MANAGER.

      As long as autostart is enabled on one of the nodes in the
      list, this queue will be started and available to execute batch
      jobs. If all three nodes in the example are shut down or if
      autostart is disabled, the queue will remain stopped until
      one of the three nodes in the node list joins the cluster and
      executes the ENABLE AUTOSTART/QUEUES command.

      The ENABLE AUTOSTART/QUEUES and INITIALIZE/QUEUE commands
      affect only the queues managed by the default queue manager
      SYS$QUEUE_MANAGER because the /NAME_OF_MANAGER qualifier is not
      specified.

    3.$ INITIALIZE/QUEUE/START/BATCH/JOB_LIMIT=3 SYS$BATCH
      $ INITIALIZE/QUEUE/START/BATCH/JOB_LIMIT=1/WSEXTENT=2000 BIG_BATCH

      In this example, the first INITIALIZE/QUEUE command creates
      a batch queue called SYS$BATCH that can be used for any batch
      job. The /JOB_LIMIT qualifier allows three jobs to execute
      concurrently. The second INITIALIZE/QUEUE command creates
      a second batch queue called BIG_BATCH that is designed for
      large jobs. Only one job can execute at a time. The working
      set extent can be as high as 125 pages on OpenVMS Alpha (on a
      system with 8KB pages).

    4.$ INITIALIZE/QUEUE/START/DEFAULT=(FLAG,TRAILER=ONE)-
      _$ /ON=LPA0: LPA0_PRINT
      $ INITIALIZE/QUEUE/START/DEFAULT=(FLAG,TRAILER=ONE)-
      _$ /BLOCK_LIMIT=(1000,"")/ON=LPB0: LPB0_PRINT
      $ INITIALIZE/QUEUE/START/GENERIC=(LPA0_PRINT,LPB0_PRINT) SYS$PRINT
      $ INITIALIZE/QUEUE/START/FORM_MOUNTED=LETTER-
      _$ /BLOCK_LIMIT=50/ON=TXA5: LQP

      In this example, the first three INITIALIZE/QUEUE commands set
      up printer queues. Both queue LPA0_PRINT and LPB0_PRINT are
      set up to put a flag page before each file within a job and a
      trailer page after only the last page in a job. In addition,
      LPB0_PRINT has a minimum block size of 1000; therefore, only
      print jobs larger than 1000 blocks can execute on that queue.
      SYS$PRINT is established as a generic queue that can direct
      jobs to either LPA0_PRINT or LPB0_PRINT. Jobs that are too
      small to run on LPB0_PRINT will be queued from SYS$PRINT to
      LPA0_PRINT.

      The last INITIALIZE/QUEUE command sets up a terminal queue on
      TXA5. A job queued with a form that has a stock type other
      than the stock type of form LETTER remains pending in the
      queue until a form with the same stock type is mounted on the
      queue, or until the entry is deleted from the queue or moved
      to another queue. LETTER has been established at this site to
      indicate special letterhead paper. The block size limit is 50,
      indicating that this queue is reserved for jobs smaller than
      51 blocks.

    5.$ INITIALIZE/QUEUE/ON=QUEBID::/BATCH/RAD=0   BATCHQ1

      $ SHOW QUEUE/FULL BATCHQ1
      Batch queue BATCHQ1, stopped, QUEBID::
       /BASE_PRIORITY=4 /JOB_LIMIT=1 /OWNER=[SYSTEM]
       /PROTECTION=(S:M,O:D,G:R,W:S) /RAD=0

      This example creates or reinitializes the batch queue BATCHQ1
      to run on node QUEBID. All jobs assigned to this queue will run
      on RAD 0.
Close Help