| Previous | Contents | Index |
The ERROR parameter indicates whether the MEDIA Server process is to monitor error activity on your system. By default, all messages sent to the ERRFMT process are also forwarded to the server. Only messages relevant to known mounted volumes are used and tabulated.
ERROR = O (no) or 1 (yes)(D)
| #1 |
|---|
ERROR = 0
If this monitoring process causes any problems with the running
of diagnostic programs, just reset this flag and restart the
server.
|
The INCORE parameter is a yes / no variable. It determines whether the INCORE temporary medium definition can be used. INCORE records need OPCOM reply on each mount, since each record is not necessarily unique in the MEDIA database.
INCORE = O (no) or 1 (yes)(D)
| #1 |
|---|
INCORE = 1
|
The INITIALIZE parameter controls how medium are labeled and protected when they are initialized.
INITIALIZE = SYSTEM or OWNER(D)
| #1 |
|---|
INITIALIZE = SYSTEM
|
The values have the following affect on how labels are written.
- SYSTEM: This will cause all medium to be initialize as owned by UIC [2,7] and with a protection map of "S:RWED,O:RWED,G,W".
- OWNER: This will cause all medium to be initialize and protected as indicated in the online database.
By allowing all media to be owned by the system it prevents an ordinary user from doing an uncontrolled VMS MOUNT operation on the medium. The MEDIA MOUNT command can mount such tapes after checking the online database that the user is allowed access. VMS BACKUP (VMS 5.0) requires that tapes that it uses be owned by the UIC (of the user running the backup job) for its label checking to work properly.
The INTERACTIVE parameter is a yes / no variable. It determines whether any device command can be executed interactively.
INTERACTIVE = O (no) or 1 (yes)(D)
| #1 |
|---|
INTERACTIVE = 1
|
Users with the OPERATOR privilege can always use the device commands interactively regardless of this setting.
The LOCK_DEVICES parameter indicates whether the SERVER process should allocate all the known devices (known to MEDIA) and only release them to proper requests from the MEDIA program. This will prevent any user from allocating these devices.
LOCK_DEVICES O (no) or 1 (yes)(D)
| #1 |
|---|
LOCK_DEVICES = 1
|
Enabling this feature allows the MEDIA Librarian to fully control the access and use of tape drives and disk drives thus increasing the security of the installation.NOTE: THIS PARAMETER IS ONLY USED DURING THE INITIAL CREATION OF THE MEDIAS.DAT CONTROL FILE.
After the initial setup use the
to change the lock characteristic.
MEDIAS> SET/DEVICE MTA0:/LOCK MEDIAS> SET/DEVICE MTA0:/UNLOCK
The MNT_MESSAGE parameter controls the format of any OPCOM messages that are generated when a mount request is made to the operator.
MNT_MESSAGE = max_len [,DENSITY] [,LOCATION]
default = 70,DENSITY,LOCATION
| #1 |
|---|
MNT_MESSAGE = "70,LOCATION"
|
The max_length is the length of the longest OPCOM message that the system will create. There are two types of messages that can be created, verbose and abbreviated. The system will try to choose the longest one that will fit into the maximum length. If the abbreviated message is too long to fit into the specified length it is truncated on the right.The inclusion or exclusion of the words DENSITY and/or LOCATION will control whether that portion of the generated message is included or not.
The basic format of the OPCOM mount message is:
Verbose format:
%%%%%%%%%%%% OPCOM 29-MAR-1996 08:29:00.12 %%%%%%%%%%% Request 18, from user SMITH Please mount volume 1829 in device _MUA0: External label 1829, density 6250 bpi, from CABINET 3, for writingAbbreviated format:
%%%%%%%%%%%% OPCOM 29-MAR-1996 08:29:00.12 %%%%%%%%%%% Request 18, from user SMITH Please mount volume 1829 in device _MUA0: External 1829, 6250 bpi, CABINET 3, writingThe format of the fourth line is affected by this parameter.
The MOUNT_RETRIES_DISK parameter sets the number of times an automatic retry is carried out on a disk before an OPERATOR is notified.
MOUNT_RETRIES_DISK = n
Default =
| #1 |
|---|
MOUNT_RETRIES_DISK = 3
|
The number of retries carried out can help to limit read attempts on a multiple disk device when searching an internal label. All devices can be limited in retries to avoid loop situations while mounting and unmounting disks.
The MOUNT_RETRIES_TAPE parameter sets the number of times an automatic retry is carried out on a tape before an OPERATORis notified.
MOUNT_RETRIES_TAPE = n
Default =
| #1 |
|---|
MOUNT_RETRIES_TAPE = 4
|
The number of retries carried out can help to limit read attempts on a multiple tape device when searching an internal label. All devices can be limited in retries to avoid loop situations while mounting and unmounting tapes.
The OPCOM parameter controls whether a message is sent to the operator on submission of a tape job.
OPCOM O (no)(D) or 1 (yes)
| #1 |
|---|
OPCOM = 1
|
The QUEUE parameter defines which queue is to be used during a job command to submit the specified medium for processing. Each queue can be associated with up to ten different media types.
QUEUEn = queue_name , device_type1... device_type10
| #1 |
|---|
QUEUE0 = SYS$TAPE,TAPE
|
| #2 |
|---|
QUEUE1 = BIGDISK,RP06
|
| #3 |
|---|
QUEUE2 = ALLTAPES,BIGTAPE,SMALLTAPE
|
The device type is in turn associated with physical drives via the TYPE parameter described below.
Each queue mentioned must be initialized and started in the system start up file. As distributed, the SYS$MANAGER:MEDIASTRT.COM contains the needed commands to create one queue, SYS$TAPE. Any additional queue commands should be placed in the site specific start up file SYS$MANAGER:SYSTARTUP_V5.COM.
The JOBLIMIT specified with a particular queue should be equal to the number of drives associated with it. There is one useful exception to this. For example, if one tape drive can handle 6250 and 1600 BPI and two other tape drives are only capable of 1600 BPI. Here two queues would allow 1600 BPI jobs to be placed in a separate queue from the 6250 BPI jobs thus allowing the OPERATOR to stop or start the queues as needed. The required definitions would be:
QUEUE0 = TAPE6250,HIDEN,LODEN QUEUE1 = TAPES,HIDENThe device types HIDEN and LODEN would subsequently be defined with a type parameter as to which drive is associated with each type.
In this case, where queues have overlapping device lists, it is important to increase the TIMEOUT parameter. This will allow an active job to wait longer for the completion of another current job before quitting due to a device already allocated condition.
The SVR_HOME parameter specifies the home directory for the server process. All temporary command files created by the server during the process of submitting jobs into a batch queue are placed in this directory. In most cases the default value is satisfactory.
SVR_HOME = device:[directory]
Default = "SYS$COMMON:[SYSMGR]"
| #1 |
|---|
SVR_HOME == "DUA0:[COMTEMP]"
|
In a cluster this directory needs to be equally accessible from all members of the cluster. It is also REQUIRED that this directory specification NOT explicitly or implicitly include a logical name search list. Thus such names as SYS$MANAGER: (in a cluster) cannot be used.
The SVR_CENTRAL parameter is an alternate way of locating the MEDIA SERVER shared data file. It is essential that all servers running in a cluster use the same file. In most cases the default value is satisfactory.
SVR_CENTRAL = location
Default = "MEDIA_LIBRARY:MEDIAS.DAT"
| #1 |
|---|
SVR_CENTRAL == "DUA0:[COMTEMP]"
|
In certain cases, it is very useful to define device name synonyms.
SYNONYM = device_name
synonym_name Is an alternate name for the device. device_name Is a device name used in a device type declaration.
| #1 |
|---|
BIGDK0 = DISK,$2$DJA0
ALPHA$DJA0 = $2$DJA0
BETA$DJA0 = $2$DJA0
|
Note
Leave all leading underscores and trailing colons off of both names.In the above example, the device type BIGDK is a dual ported disk attached to both nodes ALPHA and BETA. The disk has been associated with an allocation class of 2. In this case, there are three possible names associated with this disk: $2$DJA0:, ALPHA$DJA0: and BETA$DJA0:. These parameter settings will allow the server to properly identify these three names as representing the same device.
The TIMEOUT parameter controls the maximum wait allowed for an allocation request to complete.
TIMEOUT = n (minutes)
Default =
| #1 |
|---|
TIMEOUT = 10
|
The default value is adequate in most cases. In cases where the number of active medium jobs is always equal to the number of available drives, a smaller time out can be used. For situations where queue definitions allow an excess number of active jobs, this number may need to be increased. The same is true on systems where interactive allocations of a drive is allowed. On such systems, this number may need to be increased to prevent lengthy interactive allocations from aborting the media batch job.
For each device type specified in a QUEUE parameter or used anywhere in the medium database, a corresponding definition must be supplied. This parameter associates physical devices with the more generic name used in the database.
ALIAS_nnnn = [TAPE,]device_name:[,LENGTH=n] [,DENSITY=(m,..)][,LOCK][,UNLOAD] or DISK,device_name:[,LOCK][,UNLOAD]
ALIAS = devalias
Attribute Meaning type|n device type and member number TAPE indicates a sequential tape device DISK indicates a direct access disk device device_name: can be either ddcu:, the physical name of a device or @com_file:[param]:, a com file which manages the ALLOCATION/DEALLOCATION of a device defined as a dynamic device(for information on how to create such a com file, see Appendix C) LENGTH=n maximum length specified tape drive can handle LOCK request server to allocate this device UNLOAD unload the volume on dismount DENSITY=m available densities (800, 1600, 3200, 6250, 6666, 10000, 39782, 42500 or 79564)
| #1 |
|---|
TAPE0 = TAPE,MTA0:,DENSITY=(800,1600)
|
| #2 |
|---|
TAPE1 = TAPE,MSA0:,LENGTH=1200,DENSITY=1600,LOCK
|
| #3 |
|---|
RP060 = DISK,DBA0:
|
| #4 |
|---|
RP061 = DISK,DBA1:
|
| #5 |
|---|
DYN01 = DISK@DYNAMIC:ABC
|
| #6 |
|---|
TK500 = TAPE, MUA0:
|
| #7 |
|---|
TK501 = TAPE, MUA0:
|
The device selection process performed during the allocation step examines the LENGTH and DENSITY specifications (if supplied) and compares them with the known attributes for the medium being used. Only a drive which meets the known requirements will be selected. If this turns out to create an impossible situation, the request is aborted and a message is issued to that effect.
The LOCK parameter will allow for selective locking of devices by the MEDIA-SERVER process. This will cause the server process to allocate the drive and only release it to a MEDIA ALLOCATE command. This differs from LOCK_DEVICES parameter which will lock all devices known to the MEDIA Librarian. The lock condition will prevent any allocation of the specified drive from being performed without using the MEDIA Librarian.
The 6666 density applies to TK50 cartridges and 10000 applies to TK70 cartridges. The 39782 density applies to a TA90 cartridge. The 42500 density applies to TF85 cartridges. The 79564 density applies to a TA90E cartridge.
Previous Next Contents Index