NAME

jb_config − jukebox resource enabler

SYNOPSIS

jb_config

DESCRIPTION

The jb_config command configures a NetWorker server with a jukebox.  The nsrcap command must be run after executing the jb_config command.  When prompting the user, the entry enclosed in braces ([default]) can be selected by pressing <RETURN>. 

The file /nsr/jbconfig is the jukebox models configuration file.  This file can be used to configure a non-standard list of jukebox models.  The format of the file is VECTOR-TYPE MODEL-NAME<NEWLINE>, where VECTOR-TYPE is one of SJI (the Standard Jukebox Interface) or ATL (RS232-based devices speaking the IGM-ATL protocol).  MODEL-NAME can be any string.  If the file does not exist, a pre-configured set of models is provided to the user.  The pre-configured set may include the following:
 

SJI ADIC
ATL ATL
SJI EXB-10i
SJI EXB-10e
SJI EXB-60
SJI EXB-120
SJI HP
ATL Lago Datawheel
SJI other

The first question jb_config asks the user is to select a jukebox model. 
 

Enter the letter corresponding to the type of jukebox you are installing:

a) ADIC
b) ATL
c) EXB-10i
d) EXB-10e
e) EXB-60
f) EXB-120
g) HP
h) Lago Datawheel
i) other
j) another jb

Choice? 

 
The user should enter the letter of the corresponding model, e.g. if one were installing an HP optical jukebox the letter ’g’ should be selected.

Once a control port is entered, jb_config checks to see if the model selected is a SCSI based, or SJI based, jukebox.  If the jukebox is an SJI device, the jukebox enabler checks for the existence of a device driver.  If no device driver is installed, jb_config will ask the user to verify the driver has been installed properly. 

Next, the jukebox enabler queries the user to enter the pathnames for all the media devices configured in the jukebox.  The user must add an entry for each device.  If the device has not yet been configured into the NetWorker system, then the user will be prompted to enter the media device type and the device will be configured for them. 

Finally, if the jukebox supports a bar code label reader, the user will be asked if the NetWorker support for it should be turned on. If support for the bar code label reader is turned on, then the user will be asked if the media volume labels should match the bar code labels on the media.  If this option is selected, the label templates will not be used by the jukebox and each media volume must have a readable bar code label. 

If everything goes well, the user will see the following message:
 

Jukebox has been added successfully

FILES

/nsr/jbconfig
jukebox models configuration file

EXAMPLES

User entries are in italics. 
 
# sun4/jb_config
Enter the letter corresponding to the type of jukebox
you are installing:
        a) ADIC
        b) ATL
        c) EXB-10i
        d) EXB-10e
        e) EXB-60
        f) EXB-120
        g) HP
        h) Lago Datawheel
        i) other
        j) another jb
Choice? c<RETURN>
Installing a EXB-10i jukebox.
Name you would like to assign to the jukebox device? Engineering<RETURN>
Pathname of the control port for the jukebox device? [/dev/sjid1u1] <RETURN>
Enter pathname of media drive 1: ? /dev/nrst8<RETURN>
 
Jukebox has been added successfully

SEE ALSO

jbexercise(8), nsr_device(5), nsr_jukebox(5), nsr(5), nsrcap(8). 

DIAGNOSTICS

’unknown model’ invalid choice for ’model’ (35022)
The NetWorker system does not recognize the model chosen.  If you added a /nsr/jbconfig∗ file after starting the daemons, you will see this error. The solution is to restart NetWorker.

NetWorker 4.1.2  —  Last change: May 1995