HELP INITIALIZE — VMS 5.2
The INITIALIZE commands perform the following functions: o Format and write a label on a mass storage device (see Device). o Create or initialize a print or batch queue (see /QUEUE).
Additional information available:
Device
Formats a disk or magnetic tape volume and writes a label on the
volume. At the end of initialization, the disk is empty except for
the system files containing the structure information. All former
contents of the disk are lost.
Requires VOLPRO privilege for most INITIALIZE operations.
Format:
INITIALIZE device-name[:] volume-label
Additional information available:
ParametersCommand QualifiersExamples
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 currently allocated; 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 alphanumeric characters; for a magnetic tape volume, you can specify a maximum of 6 alphanumeric characters. Letters are automatically changed to uppercase. Nonalphanumeric characters are not allowed in the volume-label specification on disk. In order to use ANSI "a" characters on the volume-label on magnetic tape, the volume name must be enclosed in quotation marks. For an explanation of ANSI "a" characters, see the description of the /LABEL qualifier.
Command Qualifiers
Additional information available:
/ACCESSED/BADBLOCKS/CLUSTER_SIZE/DATA_CHECK
/DENSITY/DIRECTORIES/ERASE/EXTENSION/FILE_PROTECTION
/GROUP/HEADERS/HIGHWATER/INDEX/LABEL/MAXIMUM_FILES
/OVERRIDE/OWNER_UIC/PROTECTION/SHARE/STRUCTURE
/SYSTEM/USER_NAME/VERIFIED/WINDOWS
/ACCESSED
/ACCESSED=n Requires OPER (operator) privilege. Specifies, for disk volumes, the number of directories to be maintained in system space for ready access. Legal values for n are 0 through 255. If /ACCESSED is not specified, the INITIALIZE command uses the default value of 3. This value is ignored by VMS, but is present for use on RSX systems.
/BADBLOCKS
/BADBLOCKS=(area[,...])
Specifies, for disk volumes, specific areas on the volume that are
faulty. The INITIALIZE command marks the areas as allocated so that
no data will be written in them.
You can specify one or more areas, using one or both of the formats
shown below. If you specify only one area, you can omit the
parentheses.
lbn[:count] Specifies a logical block number on the
disk volume, and optionally a count of
logical blocks beginning with the logical
block specified, to be marked as
allocated
sector.track.cyl[:count] Specifies a specific sector, track, and
cylinder on the disk volume, and
optionally a count of blocks, beginning
with the first block specified, to be
marked as allocated
All media supplied by DIGITAL and supported on the VMS operating
system, except floppy disks 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 VMS Bad Block Locator
Utility Manual.
/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 one-hundredth the
size of the volume; the minimum size you can specify is calculated
with the formula:
disk size (number of blocks)
-----------------------------
255*4096
For Files-11 Structure Level 2 disks, the cluster size default
depends on the disk capacity; disks that are 50,000 blocks or larger
have a default cluster size of 3, while those smaller than 50,000
blocks have a default value of 1.
For Files-11 Structure Level 1 disks the cluster size must always be
1.
/DATA_CHECK
/DATA_CHECK[=(option[,...])] Defines a default for data check operations following all reads and/or writes to the volume. You can specify one or both of the following options: READ Performs checks following all read operations WRITE Performs checks following all write operations If you specify /DATA_CHECK without specifying an option, the system assumes the default of /DATA_CHECK=WRITE. If you do not specify /DATA_CHECK, the system performs no checking as the default. You can override the checking you specify at initialization for disks when you issue a MOUNT command to mount the volume. If you specify only one option, you can omit the parentheses.
/DENSITY
/DENSITY=density-value
The /DENSITY qualifier is not applicable to the TK50 tape device.
For floppy diskette volumes that are to be initialized on RX02 or
RX33 diskette drives, specifies the density at which the floppy disk
is to be formatted.
RX02 dual-density diskette drives allow floppy diskettes to be
initialized at single or double density. RX33 diskette drives allow
floppy diskettes to be initialized at double density only. To
specify single-density formatting of a floppy diskette, specify the
density value SINGLE. To specify double-density formatting of a
floppy diskette, specify the density value DOUBLE.
If you do not specify a density value for a floppy diskette being
initialized on an RX02 or RX33 drive, the system leaves the volume
at the density to which the volume was last formatted.
For magnetic tape volumes, specifies the density in bytes per inch
(bpi) at which the magnetic tape is to be written.
For magnetic tape volumes, 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. 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.
NOTE
Floppy diskettes formatted in double density cannot be
read or written by the console block storage device (an
RX01 drive) of a VAX/780 until they have been reformatted
in single density.
RX33 floppy diskettes cannot be read or written by RX50
disk drives. RX50 floppy diskettes can be read and written
by RX33 disk drives; they cannot be initialized by RX33
disk drives.
/DIRECTORIES
/DIRECTORIES=n Specifies, for disk volumes, the number of entries to preallocate for user directories. The number of entries must be an integer between 16 and 16000. The default value is 16.
/ERASE
/ERASE /NOERASE (default) Physically destroys deleted data (by writing over it). Controls the Data Security Erase (DSE) operation on the volume before initializing it. The /ERASE qualifier applies to ODS-2 disk 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. If you specify /ERASE, a DSE operation is performed on the volume. For disk devices, the ERASE volume attribute is set. In effect, each file on the volume is erased when it is deleted. Note that the amount of time taken by the DSE operation depends on the volume size; INITIALIZE/ERASE is always slower than INITIALIZE /NOERASE.
/EXTENSION
/EXTENSION=n Affects Files-11 Structure Level 1 disks ONLY 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. You can specify a value in the range 0 through 65,535. If you do not specify a default extension size, the INITIALIZE command uses a value of 5. Note that this attribute is not used when the volume is being used on a VMS system, but is provided to control the process's use of the volume on RSX-11M systems. In VMS, the default file extension is specified using the SET RMS command.
/FILE_PROTECTION
/FILE_PROTECTION=code Affects Files-11 Structure Level 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 VMS DCL Concepts Manual. 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 a VMS system, but is provided to control the process's use of the volume on RSX-11M systems. VMS systems always use the default file protection. Use the SET PROTECTION/DEFAULT command to change the default file protection.
/GROUP
/GROUP Defines a group volume. The /GROUP qualifier applies protection of RWED to all ownership categories unless /GROUP is specified with /NOSHARE, in which case the volume protection is RWED for all but the world category. The owner UIC of the volume defaults to your group number and a member number of 0.
/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. This qualifier 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.
/HIGHWATER
/HIGHWATER (default) /NOHIGHWATER Affects Files-11 Structure Level 2 disks ONLY. Sets the file highwater mark (FHM) volume attribute, which guarantees that a user cannot read data that he has not written. You cannot specify /NOHIGHWATER for magnetic tape. The /NOHIGHWATER qualifier disables FHM for a disk volume.
/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
/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 VMS 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, VMS provides a routine that checks this field in the
following manner.
o If the magnetic tape was created on a version of VMS 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 VMS 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.
/MAXIMUM_FILES
/MAXIMUM_FILES=n
Restricts, for disk volumes, the maximum number of files that the
volume can contain (overriding the default value). The default is
calculated from the volume size in blocks as follows:
volume size
-----------------------
(cluster factor + 1) *2
The maximum size you can specify for any volume is:
volume size
--------------------
(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.
/OVERRIDE
/OVERRIDE=(option[,...])
Requests the INITIALIZE command to ignore data on a magnetic tape
volume that protects it from being overwritten. You may 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,
VMS provides a routine that checks this field in
the following manner. If the magnetic tape was
created on a version of VMS that conforms to
Version 3 of ANSI, this option must be used to
override any character other than an ASCII space.
If a VMS protection is specified and the magnetic
tape conforms to an ANSI standard that is later
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 may need to do this for magnetic tapes
that were created before VMS Version 4.0 on
DIGITAL operating systems using the D% format in
the volume Owner Identifier field. You must have
the user privilege VOLPRO to override volume
protection, or your UIC must match the UIC written
on the volume.
OWNER_IDENTIFIER Allows you to override the processing of the Owner
Identifier field of the volume label.
If you specify only one option, you may 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.
/OWNER_UIC
/OWNER_UIC=uic Specifies an owner UIC for the volume. The default is your default UIC. Specify the UIC using standard UIC format as described in the VMS DCL Concepts Manual. 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.
/PROTECTION
/PROTECTION=(ownership[:access],...) Applies the specified protection to the volume. Specify ownership as SYSTEM, OWNER, GROUP, or WORLD and access as R (read), W (write), E (execute), and D (delete). 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 a VMS- specific volume label. The system only applies read and write access restrictions; execute and delete access are meaningless. Moreover, the system and the owner are always given both read and write access to magnetic tapes, regardless of the protection code you specify. See the VMS DCL Concepts Manual for more information on specifying protection code. Any attributes not specified are taken from the current default protection. When you specify a protection code for an entire disk volume, access type E (execute) indicates create access.
/SHARE
/SHARE (default) /NOSHARE Permits all categories of access by all categories of ownership. The /NOSHARE qualifier denies access to group (unless /GROUP is also specified) and world processes.
/STRUCTURE
/STRUCTURE=level Specifies whether the volume should be formatted in Files-11 Structure Level 1 or Structure Level 2 (the default). 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 R (read) access to all other users.
/SYSTEM
/SYSTEM Requires a system UIC or SYSPRV 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.
/USER_NAME
/USER_NAME=string
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.
/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 /VERIFIED for disks with 4096 blocks or more and /NOVERIFIED for disks with less than 4096 blocks.
/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 through 80. The default is 7.
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:[ARCHIE]
The previous 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.
/QUEUE
Creates or initializes queues. You use this command to create queues
and to assign them names and attributes. The /QUEUE qualifier is
required. The /BATCH qualifier is required to create a batch queue.
Requires OPER privilege.
Format:
INITIALIZE/QUEUE queue-name[:]
Additional information available:
ParametersCommand QualifiersExample
Parameters
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.
Command Qualifiers
Additional information available:
/BASE_PRIORITY/BATCH/BLOCK_LIMIT/CHARACTERISTICS
/CLOSE/CPUDEFAULT/CPUMAXIMUM/DEFAULT/DEVICE
/DISABLE_SWAPPING/ENABLE_GENERIC/FORM_MOUNTED/GENERIC
/JOB_LIMIT/LIBRARY/ON/OPEN/OWNER_UIC
/PROCESSOR/PROTECTION/RECORD_BLOCKING/RETAIN
/SCHEDULE/SEPARATE/START/TERMINAL/WSDEFAULT
/WSEXTENT/WSQUOTA
/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 through 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.
/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 or 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 /[NO]BATCH qualifier of the INITIALIZE/QUEUE command has superseded the /[NO]BATCH qualifier of the START/QUEUE command. DIGITAL recommends that you use the INITIALIZE/QUEUE/[NO]BATCH command to determine queue type. DIGITAL also recommends that you update command procedures that use START/QUEUE/[NO]BATCH. The /BATCH and /DEVICE qualifiers are mutually exclusive; the /NOBATCH and /NODEVICE qualifiers also cannot be used together.
/BLOCK_LIMIT
/BLOCK_LIMIT=([lowlim,]uplim) /NOBLOCK_LIMIT (default) Limits the size of print jobs that can be processed on an output execution queue. This 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 two double quotation marks 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 /BLOCK_LIMIT setting for that queue.
/CHARACTERISTICS
/CHARACTERISTICS=(characteristic[,...]) /NOCHARACTERISTICS (default) Specifies one or more characteristics for processing jobs on an execution queue. If a queue does not have all the characteristics that have been specified for a job, the job remains pending. If you specify only one characteristic, you can omit the parentheses. Each time you specify /CHARACTERISTICS, 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 through 127 or a characteristic name that has been defined by the DEFINE /CHARACTERISTIC command. The /NOCHARACTERISTICS qualifier cancels any /CHARACTERISTICS settings previously established for that queue.
/CLOSE
/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, stalled). When a queue is marked closed, jobs executing continue to execute. Jobs pending in the queue continue to be candidates for execution.
/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 SYSGEN parameter PQL_MCPULM. The time cannot exceed the CPU time limit set by the /CPUMAXIMUM qualifier. For information on specifying delta time, see the VMS DCL Concepts Manual.
/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 SYSGEN parameter PQL_MCPULM. For information on specifying delta times, see the VMS DCL Concepts Manual. 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 and/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.
/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 commands. 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. See also /FORM_MOUNTED.
[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 attributes, see the
description of the /SEPARATE qualiifer. For information on
specifying default queue attributes, see the Guide to Maintaining a
VMS System.
/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,
/DEVICE=PRINTER 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 also cannot be used together.
/DISABLE_SWAPPING
/DISABLE_SWAPPING /NODISABLE_SWAPPING (default) Controls whether batch jobs executed from a queue can be swapped in and out of memory.
/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.
/FORM_MOUNTED
/FORM_MOUNTED=type Specifies the mounted form for an output execution 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. 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. In both cases, jobs remain 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.
/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 /DEVICE qualifiers. If you specify neither /BATCH nor /DEVICE on creation of a generic queue, the queue becomes a generic printer queue by default.
/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 0 to 255. The job limit default value for n is 1.
/LIBRARY
/LIBRARY=file-name /NOLIBRARY Specifies the file name for the device control library. When you are initializing a output queue, you can use the /LIBRARY qualifier to specify an alternate device control library. The default library is SYS$LIBRARY:SYSDEVCTL.TLB. Only a file name can be used as the parameter of the /LIBRARY qualifier. The system always assumes that the location of the file is in SYS$LIBRARY and that the file type is TLB.
/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. The node name is used only in VAXcluster systems; it must match the node name specified by the SYSGEN parameter SCSNODE for the VAX computer on which the queue executes.
/OPEN
/OPEN 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, use the /CLOSE qualifier. Whether a queue will accept or reject new job entries is independent of the queue's state (such as paused, stopped, stalled).
/OWNER_UIC
/OWNER_UIC=uic Enables you to change the user identification code (UIC) of the queue. Specify the UIC using standard UIC format as described in the VMS DCL Concepts Manual. The default UIC is [1,4].
/PROCESSOR
/PROCESSOR=file-name /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 /PROCESSOR setting and causes SYS$SYSTEM:PRTSMB.EXE to be used.
/PROTECTION
/PROTECTION=(ownership[:access],...) Specifies the protection of the queue. Ownership categories are SYSTEM, OWNER, GROUP, WORLD; each category can be abbreviated to its first character. Access categories are R (READ), W (WRITE), E (EXECUTE), and D (DELETE); a null access specification means no access. The default protection is: (SYSTEM:E, OWNER:D, GROUP:R, WORLD:W). If you include only one protection code, you can omit the parentheses. For more information on specifying protection codes, see the VMS DCL Concepts Manual. For more information on controlling queue operations through UIC-based protection, see the Guide to Maintaining a VMS System.
/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 /NORECORD_BLOCKING, the symbiont sends each formatted record in a separate I/O request to the output device. For the standard VMS print symbiont, record blocking can have a significant performance advantage over single-record mode.
/RETAIN
/RETAIN[=option]
/NORETAIN (default)
Holds jobs in the queue in a retained status after they have
executed. The /NORETAIN qualifier enables you to reset the queue to
the default. Possible options are as follows:
ALL (default) Holds all jobs in the queue after execution
ERROR Holds in the queue only jobs that complete
unsuccessfully
/SCHEDULE
/SCHEDULE=[NO]SIZE Specifies whether pending jobs in an output execution queue are scheduled for printing based on the size of the job. When the default, /SCHEDULE=SIZE, is in effect, shorter jobs print before longer ones. When /SCHEDULE=NOSIZE is in effect, jobs are printed in the order they were submitted, regardless of size. If you enter this command while there are pending jobs in any queue, its effect on future jobs is unpredictable.
/SEPARATE
/SEPARATE=(option[,...])
/NOSEPARATE (default)
Specifies the mandatory queue attributes, 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 each time a
job reset occurs. 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 /SEPARATE=BURST, 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 attributes that can be
overridden, see the description of the /DEFAULT qualifier.
For more information on specifying mandatory queue attributes, see
the Guide to Maintaining a VMS System.
/START
/START /NOSTART (default) Starts the queue being initialized by the current INITIALIZE/QUEUE command.
/TERMINAL
/TERMINAL /NOTERMINAL (default) Indicates that the output queue is a terminal queue. The /NOTERMINAL qualifier cancels the effect of a previous /TERMINAL qualifier on the same command. It is supported in this release for compatibility with VMS V4.n. The /[NO]DEVICE qualifier has superseded the /[NO]TERMINAL qualifier. DIGITAL recommends that you use the /[NO]DEVICE qualifier to determine queue type. DIGITAL also recomends that you use this qualifier to update command procedures that use INITIALIZE/QUEUE/[NO]TERMINAL.
/WSDEFAULT
/WSDEFAULT=n Defines for a batch job a working set default, the default number of physical pages that the job can use. You also can specify this qualifier for an output execution queue. Used in this context, /WSDEFAULT establishes the working set default of the symbiont process for an output execution queue when the symbiont process is created. 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. 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 included).
/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. You also can specify this qualifier for an output execution queue. Used in this context, /WSEXTENT establishes the working set extent of the symbiont process for an output execution queue when the symbiont process is created. 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. 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 included). A working set default size and a working set quota (maximum size) are included in each user record in the system user authorization file (UAF). You can specify a working set default and a working set quota for individual jobs and/or for all jobs in a given queue.
/WSQUOTA
/WSQUOTA=n Defines for a batch job a working set quota, the amount of physical memory that is guaranteed to the job. You also can specify this qualifier for an output execution queue. Used in this context, /WSQUOTA establishes the working set quota of the symbiont process for an output execution queue when the symbiont process is created. 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. 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 included). A working set default size and a working set quota (maximum size) are included in each user record in the system user authorization file (UAF). You can specify a working set default and a working set quota for individual jobs and/or for all jobs in a given queue. Working set default, working set quota, and working set extent values are included in each user record in the system user authorization file (UAF). You can specify working set values for individual jobs or and/or for all jobs in a given queue. The decision table (Table DCL-2 in the DCL Dictionary) shows the action taken for different combinations of specifications that involve working set values.
Example
1. $ 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 2000.
2.$ INITIALIZE/QUEUE/START/DEFAULT=(FLAG,TRAILER=ONE/ON=LPA0: LPA0_PRINT)
$ INITIALIZE/QUEUE/START/DEFAULT=(FLAG,TRAILER=ONE/BLOCK_LIMIT=(1000,"")
$ INITIALIZE/QUEUE/START/GENERIC=(LPA0,LPB0) SYS$PRINT
$ INITIALIZE/QUEUE/START/FORM_MOUNTED=LETTER/BLOCK_LIMIT=50 LQP /ON=TXA5:
In this example, the first three INITIALIZE/QUEUE commands sets up
printer queues. Both queue LPA0 and LPB0 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 has a minimum block size of
1000. Thus 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 or LPB0. Jobs that are too small to run
on LPB0 will be queued from SYS$PRINT to LPA0.
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 letter-head paper. The
block size limit is 50, indicating that this queue is reserved for
jobs smaller than 51 blocks.