JB® V5.1.4—Release Notes

Copyright ©2007 Software Partners, Inc. All rights reserved.



These release notes are for customers who are upgrading to JB V5.1.4 from JB V3.0.X or higher.


Topics covered include:

·        Upgrade Instructions

·        New Features

·        Modifications



Questions or problems

Please email or call Software Partners, Inc. if you have any questions or comments about this version of JB. Our email address is tech_support@softwarepartners.com, and our telephone number is



Supported platforms

JB V5.1.4 supports OpenVMS V6.2 through V7.3 (VAX), OpenVMS V6.2 through V8.3 (Alpha), and OpenVMS V8.2 through V8.3 (Integrity)


Table of Contents

The following topics are covered in the release notes:




See Page



Upgrade Instructions




New Features in V5.1.X




Modifications in V5.1.1




Modifications in V5.1.2




Modifications in V5.1.3




Modifications in V5.1.4




Upgrade Instructions


Upgrade path

In order to upgrade to V5.1.X, you must be running JB V3.0.X or greater.



The procedure for upgrading JB is detailed below.








If using JB V3.0.5 or later, issue the @[JB]JBSTOP command.




Unpack the JB savesets using the following command:


_$ <disk:[directory]> <options>


where <disk:[directory]> is the location of the JB V5.1.X savesets and <options> are valid options for the VMSINSTAL procedure. An example option is awd=<optional_working_directory>, where <optional_working_directory> is an alternate temporary storage space for the install procedure.

JB V5.1.X will then be installed.




The startup file must then be executed to define logicals, install images, and convert the JBDRIVES file from V3.X format to V4.X/V5.X format:

$ @<disk>:[JB]JBSTART

If you are going to use JB V5.1 by itself (not in conjunction with TAPESYS V6.2 or with TAPESYS V6.2 and another product like HIERARCHY), skip on to step 5. Otherwise, proceed to step 4.



Upgrade Instructions, Continued



Issue the following command:

$ @<disk>:[JB]JBSTOP

The startup file must then be executed to define logicals and install images:

$ @<disk>:[JB]JBSTART <param>


If using JB V5.1.X . . .

Then <param> should be

. . . with TAPESYS V6.2.X,


. . . with TAPESYS V6.2.X and another product (like HIERARCHY),



Issue the following command:


where <disk:> is the disk device on which JBV5.1.X is installed. This is ONLY for upgrades from JB V3.X.

NOTE: This step IS REQUIRED if you are going to use JB in the TAPESYS database mode.


JB now has a key that is required for use of the product. The default location for the key is in diskname:[JB] as JB.KEY. However, a “central” key directory can be created, referenced by a logical such as SP32_KEY_DIR, and populated with a Software Partners key that is valid for several products. (If you have already set up your key file during the CONFIGURE_TAPESYS procedure, further action is not necessary.) For example, a top-level directory named SP32_KEY can be created and then a logical defined to point to it.


"SP32_KEY_DIR" [super] = "diskname:[SP32_KEY]"


The file SP32_MASTER.KEY can be edited in the new directory and populated with the contents of the key file provided with the product.


If you are upgrading from JB V4.1.X to V5.1.X, you do not need to do any conversion of the existing JB database. After installation of V5.1.X, simply start JB (with the TAPESYS_DATABASE parameter switch, if applicable) and start using the product.


New Features in JB V5.1.X



·        Compatibility with OpenVMS on Itanium

·        Compatibility with OpenVMS V8.2 on Alpha



Modifications in JB V5.1.1


Removal of JBSHR_MRU_jbname logical

With the MRU interface, JB now obtains the number of ports, slots, and drives directly from the robot instead of using the JBSHR_MRU_jbname logical. This logical no longer needs to be defined.


Addition of /NOREADER qualifier

Some jukeboxes insist on returning phantom garbage barcodes for volumes, even when they have no barcode reader at all or when barcode labels are not in use. This confuses JB and causes errors. Worse, the garbage barcodes make it into the database. Since the jukebox manufacturers can't/won't fix the problem, JB now blanks out all barcodes coming back from the jukebox if the /NOREADER flag is set on the jukebox record (by use of the DEFINE/SET JUKEBOX commands).


Modifications in JB V5.1.2


Unprivved users and extraneous banner messages

The JB banner message is normally only generated once per process creation. However, unprivileged users are not able to suppress the message because the crelnm system service will not allow them to create a supervisor mode logical name. Since user mode logicals do not survive image rundown, they get the banner on every JB command. For these users, JB now uses the lib$set_logical rtl routine, which requests a super-mode logical from the supervisor. This is what DCL DEFINE does.



DATABASE mode now the default

In the shipped setup file, JB now runs in TAPESYS_DATABASE mode by default, since nearly all JB customers use it with TAPESYS, and

there can be a lot of confusion when the command line parameter is

accidentally left off. The few customers who don't use JB with TAPESYS can set JB_OPTION to NATIVE_DATABASE in SETUP.PAR.


Modifications in JB V5.1.3


Change slot offset when using MRU

With MRU, JB now completely ignores the slot offset coming back from the jukebox. MRU wants slots to start at zero in movement commands and will convert to the physical slot internally.


Modifications in JB V5.1.4


VMS-version-specific directories

JB now places executable files in VMS-version-specific directories, so that multiple versions of VMS can share the same JB root tree.



Length and brand defaults

Default values for length and brand are now specified in JB_ADD_VOL.COM, which is used to add tapes to the TAPESYS database so that they can be converted into JB volumes.


Loading of tapes in JB DEFINE VOLUME/



With the command JB DEFINE VOLUME/AUTO, JB now loads tape(s) into the jukebox/tape library in question if door number(s) are specified by using the /FIRST_DOOR and /LAST_DOOR qualifiers.



New VALIDATE command

JB now has a new command, JB VALIDATE. The format of the command is


JB VALIDATE jukebox_name


This command allows the JB database to be validated against the current physical contents of the jukebox/tape library in question. The VALIDATE command requires barcode labels and a barcode reader.


Change to JB CONFIG/


With the JB CONFIG command, JB now aborts if there is a failure initializing volumes when the /BULK_INIT qualifier is used.



Error intercept in remote robot

JB now intercepts the occurrence of access violations in the master server process when the remote robot functionality is in use.


New /PURCHASE qualifier

The /PURCHASE qualifier has been added to the JB DEFINE VOLUME/AUTO command, allowing users to specify a desired purchase date of any volumes automatically added to the TAPESYS database.