Previous | Contents |
2.1 DECwindow setup
To use the MEDIA Work Center subsystem as a DECwindows/Motif
application, just add the following definitions to the "Customizing
Applications Definitions":
Menu item: MEDIA MOTIF Work Center Menu command: @MEDIA_LIBRARY:MEDX_MOTIF option |
The "option" can be MEDIA, BCKMGR, VAULT, SEARCH or ENTIRE. This selects the first display that comes up. By creating one entry for each option a separate process will be created for each.
2.2 Cluster installation
If you are installing MEDIA in a homogeneous cluster, after
the installation is completed, be sure to issue the following command
on ALL OTHER NODES of the cluster.
$ @SYS$STARTUP:MEDIA_STARTUP NEWVERSION |
If this is the FIRST TIME the system is installed, leave off the
NEWVERSION in the above command.
2.3 Moving the MEDIA database
All files that make up the MEDIA database are located using one logical name, MEDIA_LIBRARY:. This logical is defined in the startup file MEDIA_STARTUP.COM in the SYS_$MANAGER: directory. To move the database, do the following steps.
There are some execptions to this sequence. If you have define the
parameter BGR_CENTRAL, CENTRAL, SVR_HOME or SVR_CENTRAL then some of
the files will be in the locations defined by these variables.
2.4 Program and data files
The MEDIA system uses the following files. All these files are contained in the MEDIA_LIBRARY: directory unless otherwise noted2.
Function | File name |
---|---|
VAULT subsystem files | VAULT_[VAX|AXP].EXE |
VAULT.HLP | |
VAULT_REBUILD.COM | |
*.ADR | |
Function | File name |
BCKMGR subsystem files | BCKMGR_[VAX|AXP].EXE |
BCKMGR.DAT | |
BCKMGR.HLP | |
BCKMGR_AUTO_SUBMIT.COM | |
BCKMGR_BACKUP.COM | |
BCKMGR_BACKUP.TEMPLATE | |
BCKMGR_BACKUP_*.COM | |
BCKMGR_BGRFDL.FDL | |
BCKMGR_BHTDEF.DTR | |
BCKMGR_BHTDEF.H | |
BCKMGR_BHTDEF.INC | |
BCKMGR_CREATE_SCHEDULE.COM | |
BCKMGR_HISTORY.COM | |
BCKMGR_HISTORY.DAT | |
BCKMGR_HISTORY_SEARCH_[VAX|AXP].EXE | |
BCKMGR_MAINT.COM | |
BCKMGR_MAINT_RMU.COM | |
BCKMGR_STANDARD_PROCS.COM | |
BCKMGR_V33_CVT_TO_V40.COM | |
BCKMGR_RESTORE_VIA_SEARCH.COM | |
BCKMGR_MOVE_MEDIA.COM | |
BGR_*.DAT | |
Function | File name |
Other files | AUX_OPS.COM |
CHECKOUT.COM | |
DYNAMIC.COM | |
FORMAT_[VAX|AXP].EXE | |
FORMAT.HLP | |
LIST_REQUIRED_MEDIA.COM | |
MDBKPSHR.EXE | |
MDBKPPAT.COM | |
OFFSITE_STORAGE.COM | |
PRINT_LABELS_[VAX|AXP].EXE | |
PRINT_LABELS.FOR | |
PRINT_LABELS.OBJ | |
SUMMUS_MAGNUS_JBL_INTERFACE.COM | |
TAPEQUE.COM | |
*.DECW$BOOK | |
*.DECW$BOOKSHELF | |
*.TXT | |
Function | File name |
MEDIA subsystem files | MDAMCLCLB.CLB |
MDAMCLHLB.HLB | |
MDAMCLSEC.LIST | |
MDAMCLSEC.SEC | |
MEDIA_[VAX|AXP].EXE | |
MEDIA.HLP | |
MEDIA.OLB | |
MEDIAMSG_[VAX|AXP].EXE | |
MEDIA.DAT | |
MEDIAS.DAT | |
MEDIAS_[VAX|AXP].EXE | |
MEDIAS.FDL | |
MEDIAS.HLB | |
MEDIASHR_[VAX|AXP].EXE | |
MEDIA_LOGIN.COM | |
MEDIA_AUDIT.COM | |
MEDIA_MCL_MAINT.COM | |
MEDIA_QUEUES.COM | |
MEDIA_QUEUES.DAT | |
MEDIA_REPORT.CLB | |
MEDIA_START.COM | |
MEDIA_TPEFDL.FDL | |
MEDIA_TPEDEF.H | |
MEDIA_TPEDEF.INC | |
MEDIA_TPEDEF.DTR | |
MEDX_MOTIF.COM | |
MEDX_MOTIF.DAT | |
MEDX_MOTIF[11|12]_[VAX|AXP].EXE | |
SYS$MANAGER:MEDIAS.LOG | |
SYS$MANAGER:MEDIA.VAR | |
SYS$MANAGER:MEDIA2.VAR | |
SYS$MANAGER:MEDIA_STARTUP.COM | |
*.BJL,*.SDR,*.TDR |
2 There are several parameters that can redirect the files to other locations. |
The entire MEDIA system can be removed from your system by executing the following command.
$ @SYS$STARTUP:MEDIA_STARTUP DELETE_ALL |
The file BCKMGR_BACKUP.COM is never replace by an installation. If you
have customized this file then those changes are left in place. Any
changes added by ISE to support new features are placed in the
BCKMGR_BACKUP.TEMPLATE file. Please compare this file with
BCKMGR_BACKUP.COM to see if any new changes need to be merged.
2.7 Conflict with diagnostic program
The media server process monitors the error activity on the system by using the system error mailbox. This can cause a problem when running diagnostic programs. If this becomes a problem, just terminate the server with the following command:
$ @SYS$MANAGER:MEDIA_STARTUP STOP |
If the server process is started and this mailbox is already in use,
then the server will continue and only disable the error monitoring
features.
2.8 Extra unload operations
Certain stackers when a volume is unloaded automatically advance to the next medium, ready it and make it on-line. The MEDIA_SERVER will (if the UNLOAD parameter is 1 or 3) at the end of a MEDIA job check that the device was left unloaded, if not an unload is performed.
If the stacker mechanism is fast enough it may have had time to ready the next volume. As a result the server unloads it. The appearance is that this volume is skipped. By setting the below parameter in the parameter file this server feature is suppressed.
PATCH4 = 1 |
The main data files used by the system can be positioned in an alternate location by defining any or all of the following logical names. The default locations are normally satisfactory.
File | Default Location | Logical Name |
---|---|---|
MEDIA.DAT | MEDIA_LIBRARY: | MEDIADAT |
SYSUAF.DAT | SYS$SYSTEM: | SYSUAF |
BCKMGR.DAT | MEDIA_LIBRARY: | BCKMGR |
Only the group and system logical name tables are searched. The entire
media library location is controlled by the logical name MEDIA_LIBRARY.
2.10 LOGOUT MOUNT count
As a result of the way the MEDIA Librarian works, the mount count that
is recorded during a logout for any media job is usually about 4 or 5
times the number of MEDIA MOUNT commands used. This is in comparison
with VMS MOUNT command which has a count of one.
2.11 File Optimization
Of the data files used by MEDIA and BCKMGR, two of them are RMS keyed files (MEDIA.DAT and BCKMGR.DAT). After adding many media and defining many jobs it is advantages to do a CONVERT/OPTIMIZATION operation on these files. A command procedure has been provided to do this. The command to use is:
$@MEDIA_LIBRARY:CHECKOUT.COM |
For more information just print that command procedure. This operation can significantly reduce the number of I/O operations used to access these files.
Previous | Next | Contents |