3.1 Version 4.0 changes and additions

• MEDIA Librarian
  • A MCL menu/window user interface has been added.
  • The MEDIA database has been expanded.
  • An ACL control list has been added to all MEDIA database entries.
  • Two identifiers (MEDIA_OPERATOR and MEDIA_MANAGER) can be used to grant particular users elevated MEDIA access independently of OPER and SYSPRV.
  • Support for operator selected scratch tapes (vs system selected scratch tapes) and scratch templates has been added.
  • The MEDIA call interface has been expanded.
  • Support for Dynamic Devices has been added.
• BCKMGR - Backup Manager Utility
  • BCKMGR - Backup manager utility has been added.
  • A MCL menu/window user interface has been added.
  • An ACL control list has been added to all BCKMGR database entries.
  • A common BACKUP action routine has been added.
  • Support for RDB backups has been added.
  • Patches to VMS BACKUP are included to allow BACKUP to utilize the MEDIA system to mount/dismount volumes.
• Other Features
  • A new documentation set has been added. The manuals are: User Guide, Operations Guide, Reference Manual and Command Summary.
  • SCHEDULE - has been removed and is available as a separate product.

This was a maintenance release with many corrections and modifications included.

3.3 Version 4.2 changes and additions

The main change made in this version are listed below.

• Added support for the ALPHA AXP OpenVMS machines.
• A MCL menu interface to VAULT. This allows for viewing and the selection of files out of the VAULT database to be restored.
• Full support for DEVICESHARE¹. This allows for the fully automatic BACKUPs of remote disks on other OpenVMS systems. Files can be selectively restored via the VAULT facility.

3.4 Version 4.3.7 changes and additions

The main change made in this version are listed below.

• Added backup modes 13, 14, 15 and 16. These modes append several runs to one backup medium.
• Added backup modes 17, 18, 19 and 20. These modes support backing up the disk drives in a remote PC's over either MicroSoft's LAN Manager or Novell's NetWare using LANutil².
• The procedure BCKMGR_RESTORE_VIA_SEARCH.COM has been added to facilitate selected file restores for users who are NOT using the VAULT subsystem.
• The procedure BCKMGR_MOVE_MEDIA.COM has been added to facilitate moving and reorder the assigned media list associated with any BCKMGR job.

3.5 Version 4.3.8 changes and additions

The main change made in this version are listed below.

• Added backup modes 21, 22, 23 and 24. These modes support backing up disk drives on any UNIX, WindowsNT or OpenVMS NFS file server using any of the available TCP/IP packages.
• The procedure BCKMGR_RESTORE_NFS_VIA_SEARCH.COM has been added to facilitate selected file restores for remote NFS servers for users who are NOT using the VAULT subsystem.
• SCRATCH MODE is now supported on both ALPHA and VAX OpenVMS systems.
• Added backup mode 25. This mode supports centrally managed remote backups on WindowsNT systems using the XSagent software³.

3.6 Version 4.4 changes and additions

The main changes made in this version are listed below:

• A complete DECwindows/MOTIF interface has been added.
• Added backup mode 26. This mode supports centrally managed remote backups on remote UNIX systems using the XSagent software.
• A new documentation set. Included in the distribution are a PostScript, Bookreader and Plain Text formats of the entire documentation set.

The main changes made in this version are listed below:

• The Introductory Guide has been rewritten to include all commonly referenced information.
• All software can now be installed from a CD.

Certain errors have been discovered and corrected in the previous version of the MEDIA Librarian System. They are listed below.

• MEDIA V4.3.3 - 1
  Problem: SCHEDULE jobs that start up a BCKMGR backup job need to run a tightly coupled style..
  Solution: The "create schedule" COM file has been expanded to create jobs that use the P2 parameter to indicate either LOOSE or TIGHT synchronization modes.
• MEDIA V4.3.3 - 2
  Problem: In some cases the parameter field of the BCKMGR database is too short.
  Solution: Continuation lines have been added. For example, to continue parameter 1 just start parameter 2 with a dash and the continuation text.
• MEDIA V4.3.6 - 3
  Problem: In an RMU backup the volume sets are built up incorrectly.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 4
  Request: Expand BCKMGR_CREATE_SCHEDULE.COM to allow an existing job to be updated to include the TIGHTLY coupled mode.
  Response: The procedure has been expanded.
• MEDIA V4.3.7 - 5
  Problem: BCKMGR backup procedures is truncating long (greater then 100 characters) source names.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 6
  Problem: The BCKMGR_AUTO_SUBMIT.COM procedure computes the next start based on the end time instead of the submit time.
  Solution: This has been changed.
• MEDIA V4.3.7 - 7
  Problem: Append mode backups do not properly chech the MEDIA_LIBRARY location when it has been redefined by the CENTRAL parameter.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 8
  Request: Enhanced BCKMGR jobs to allow for comments and continuation lines on the source disk list.
  Response: The symbols "!" and "-" have been added.
• MEDIA V4.3.7 - 9
  Problem: The DCL and MCL trim media functions do not work the same way.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 10
  Problem: Backups in scratch mode is sometimes leaving medium with the BCKMGR status bit still on.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 11
  Problem: When a backup job in generation mode releases an OFFSITE medium the medium never gets recycled.
  Solution: This has been fixed. When a OFFSITE medium is pushed off of a backup job it is left in the allocated pool with an expiration date set. When the medium is properly marked as onsite again the system will automatically move it to the RELEASED pool.
• MEDIA V4.3.7 - 12
  Problem: A medium with LABEL=NONE is not properly handled when released.
  Solution: This has been corrected. When such a medium is released it is also marked as BLANK now.
• MEDIA V4.3.7 - 13
  Problem: MEDIA /OUT=file allows any user to create an output file anywhere.
  Solution: This has been corrected to properly test the user's access rights before creating a file.
• MEDIA V4.3.7 - 14
  Problem: A Control-Y during a MEDIA INIT command leaves the user with the privilege VOLPRO.
  Solution: This has been corrected.
• MEDIA V4.3.7 - 15
  Problem: A MEDIA MODIFY/OFF_SEND=TODAY does not mark the interior volumes of a set with the specified date.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 16
  Problem: A MEDIA MODIFY/EXPIRE=TODAY does not mark the interior volumes of a set with the specified date.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 17
  Problem: The BCKMGR_RESTORE_VIA_SEARCH.COM does not properly handle concealed logicals.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 18
  Problem: BCKMGR_RESTORE_VIA_SEARCH.COM should mount medium READONLY.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 19
  Problem: A MEDIA DIRECTORY command truncates long dates.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 20
  Problem: Location field of a scratch template should be case insensitive.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 21
  Problem: Append backup modes are not properly handling a second volume.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 22
  Problem: MCL/MEDIA erroneously allows lower case letters in an alias name or user name field.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 23
  Problem: BCKMGR_RESTORE_VIA_SEARCH.COM does not handle a two (or more) volume set properly during restore.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 24
  Problem: The OFFSITE_STORAGE.COM does not clear the OFF_SEND and OFF_DURATION fields when a medium is returned onsite.
  Solution: This has been fixed.
• MEDIA V4.3.7 - 25
  Problem: In a backup job the elapse time summary information incorrectly handles the computation if the job spans midnight.
  Solution: This has been fixed.
• MEDIA V4.3.8 - 26
  Problem: A group restore procedure to do a NFS restore is needed.
  Solution: The procedure BCKMGR_RESTORE_NFS_VIA_SEARCH.COM has been added.
• MEDIA V4.3.8 - 27
  Problem: Backup jobs running in TIGHTLY coupled mode are generating two completion mail messages.
  Solution: This have corrected so that only one message is sent.
• MEDIA V4.3.8 - 28
  Problem: Expand NFS support to work properly with UCX, TCPware and MultiNET.
  Solution: This has been added.
• MEDIA V4.3.8 -29
  Problem: The procedure BCKMGR_CREATE_SCHEDULE.COM generates DCL command files that contain an error.
  Solution: This has been corrected.
• MEDIA V4.3.8 - 30
  Problem: The procedure LIST_REQUIRED_MEDIA.COM should have the ability to prompt for information.
  Solution: This has been added.
• MEDIA V4.3.8 - 31
  Problem: More purging options are needed inside the procedure BCKMGR_HISTORY.COM.
  Solution: This has been added.
• MEDIA V4.3.8 - 32
  Problem: Support for SCRATCH MODE on ALPHA OpenVMS systems is needed.
  Solution: This has been added.
• MEDIA V4.3.8 - 33
  Problem: The BCKMGR REBUILD/ADD/LOG command under certain circumstances does not work as documented.
  Solution: This has been corrected.
• MEDIA V4.3.8 - 34
  Problem: If a QUEUE parameter is specified with more then 10 types the server process exits with an "access violation".
  Solution: This has been corrected.
• MEDIA V4.3.8 - 35
  Problem: Using the MCL/CONFIGURATOR interface to modify the CENTRAL value can cause these values to be truncated.
  Solution: This has been fixed.
• MEDIA V4.3.8 - 36
  Problem: A NFS BCKMGR mode is needed to backup remote NFS servers either WindowsNT or UNIX.
  Solution: Mode numbers 21, 22, 23 and 24 have been added to this.
• MEDIA V4.3.8 - 37
  Problem: The MDBKPPAT.com procedure should be expanded to support backup V6.1-008.
  Solution: This has been added.
• MEDIA V4.3.8 - 38
  Problem: The SCHEDULE trigger job should put a copy of the BCKMGR job into its log file.
  Solution: This has been added.
• MEDIA V4.3.8 - 39
  Problem: A MEDIA DIRECTORY command of a tape that is attached comes back with "None found" unless the /ATTACHED qualifier is present. This can be missleading.
  Solution: This has been changed to indicated that an attached volume was referenced rather then "None found".
• MEDIA V4.3.8 - 40
  Request: Support for XSagent control remote backups on WindowsNT system is needed.
  Response: This has been added.
• MEDIA V4.3.7 - 41
  Problem: The procedure BCKMGR_CREATE_SCHEDULE.COM fails.
  Solution: This has been fixed.
• MEDIA V4.3.8 - 42
  Problem: During a backup operation MEDIA should gain control of the job during a volume change.
  Solution: This has been added. The AUX_OPS_COM parameter is used to control this added function.
• MEDIA V4.3.9 - 43
  Problem: A backup job run in the TIGHT mode does not return a status code.
  Solution: This has been fixed.
• MEDIA V4.3.10 - 44
  Problem: The MCL interface does not pickup the MEDIA_MANAGER identifier.
  Solution: This has been fixed.

Certain errors have been discovered and corrected in the previous version of the MEDIA Librarian System. They are listed below.

• MEDIA V4.4.6 - 1
  Problem: Add support for using Agent to backup remote NFS Unix servers.
  Solution: Backup Mode 26 has been added for this purpose.
• MEDIA V4.4.8 - 2
  Problem: The CACHE_TD parameter is visible via MCL/MEDIA.
  Solution: This has been fixed.
• MEDIA V4.4.8 - 3
  Problem: BCKMGR SUBMIT creates temporary COM files using only the first 9 characters of the job name.
  Solution: This has been changed to use the entire name.
• MEDIA V4.4.9 - 4
  Problem: RESTORE_VIA_SEARCH.COM can not deal with concealed logicals.
  Solution: This has been fixed.
• MEDIA V4.4.9 - 5
  Problem: The RESTORE_VIA_SEARCH.COM functionality is not available via the MCL or GUI interface.
  Solution: This has been added to both the MCL and MOTIF interfaces.
• MEDIA V4.4.10 - 6
  Problem: The Restore via Search volume list disappears between selections.
  Solution: This has been fixed.

Contents