JBCFG(4) CLIX JBCFG(4)
NAME
JBCFG - Optical disk jukebox configuration file
DESCRIPTION
The JBCFG configuration file describes the configuration of the Jukebox
Manager (JBM). The file specifies the following:
⊕ The location of JBM programs.
⊕ The program startup options.
⊕ The terminal device names for the robotics.
⊕ The generic Small Computer System Interface (SCSI) character device
names for the optical drives controlled by the jukeboxes.
⊕ Logical names for the jukeboxes and the optical drives.
When JBM is initialized, the configuration file is read to obtain
information necessary for the JBM subtasks to operate successfully. If
JBM cannot understand the configuration file's contents, it is not
successfully initialized. A sample JBM configuration is included with the
Jukebox Manager product.
The JBCFG file can be edited and changed any time, even when JBM is
running. However, changes will not take effect until JBM is shut down and
restarted.
The general format for JBCFG is as follows, where keyword = value may be a
literal or an aggregate consisting of one or more keyword = value,
enclosed within the braces ( { } ).
Keywords are separated by commas. The major sections of the configuration
are as follows:
JIMS = {
keyword=value ...
},
ROUTER = {
keyword=value ...
},
DATABASE = {
keyword=value ...
},
JUKEBOX = {
keyword=value ...
},
OPERATOR = {
keyword=value ...
2/94 - Intergraph Corporation 1
JBCFG(4) CLIX JBCFG(4)
},
ERRORLOG = {
keyword=value ...
}
One JUKEBOX entry is required for each jukebox that JBM manages. Other
keywords are nested within this generalized framework, with secondary and
tertiary nesting of additional keywords, as necessary. Keywords may be in
either upper or lowercase, whereas the information following the keyword
is case-sensitive. A description of the current valid keywords and their
legitimate values follows:
JIMS The valid keyword for the JIMS entry is in the JBM
configuration file as follows:
JIMS = {
checkpoint = ON
},
This specifies whether checkpointing is to be turned on or off.
Checkpointing consists of writing the volume database at each
change. It is needed for the WARM start capability of JBM.
ROUTER The valid keyword for the ROUTER entry is in the JBM
configuration file as follows:
ROUTER = {
filename = RTR.chkpt
},
The filename is the pathname of the file that contains the
request checkpoint file. If no directory is specified, it
defaults to /usr/ip32/jbm.
DATABASE The three valid keywords for the DATABASE entry are in the JBM
configuration file as follows:
DATABASE = {
path = /usr/ip32/jbm,
module = VRSmain,
filename = /usr/ip32/jbm/vdb
},
The path describes the directory where the module is located.
The module is the name of the executable file that maintains
the volume resolution subsystem database. The filename is the
pathname of the file that contains the VRS database. If
2 Intergraph Corporation - 2/94
JBCFG(4) CLIX JBCFG(4)
filename is only a basename, the database is located in the
user's current working directory. The path and module are
required for JBM to operate. The path defaults to
/usr/ip32/jbm if path is not supplied. The filename defaults
to vdb if filename is not supplied.
JUKEBOX The valid keywords for the JUKEBOX entry are in the JBM
configuration file as follows:
JUKEBOX = {
path = /usr/ip32/jbm,
module = JBCmain,
name = JB01,
JBC = {
JBD = {
path = /usr/ip32/jbm,
module = JBDmain
},
JBI = {
path = /usr/ip32/jbm,
module = JBImain,
device = /dev/tty02
},
filename = /usr/ip32/jbm/JB01.chkpt,
series = 560
exchange = NOEXCHANGE,
mount = VERIFY,
unmount = VERIFY,
export = VERIFY,
drive = {
device = /dev/gs/s3u0,
name = OD30,
status = ONLINE
},
drive = {
device = /dev/gs/s4u0,
name = OD40,
status = ONLINE
}
}
},
The path and module are the same as the path and module
described for database, except that in this context they refer
to the Jukebox Control (JBC) module. The name is the ASCII
name of the jukebox that JBM uses internally. Currently, JBM
can support 10 jukeboxes.
The JBD entry has two valid keywords: path and module. The
Jukebox Interface (JBI) entry has three valid keywords: path,
2/94 - Intergraph Corporation 3
JBCFG(4) CLIX JBCFG(4)
module, and device. The device is the name of the "tty port"
that the jukebox robotics is connected to.
The drive entry has three valid keywords: device, name, and
status. The device is the name of the generic SCSI character
device for the optical drives that the jukebox controls. The
name is the ASCII name of the drive that JBM uses internally.
The status is the default status of the drive when JBM is
started. Valid values are ONLINE and OFFLINE.
Other valid keywords in the JUKEBOX JBC entry are as follows:
filename The name of the checkpoint file used in a WARM
start.
series 560 (for a 5 1/2 inch drive jukebox) or 1800 (For a
12-inch drive jukebox)
exchange NOEXCHANGE is the only valid value keyword at this
time.
mount VERIFY or NOVERIFY is for the optical disk labels
when cartridge mounting is requested.
unmount VERIFY or NOVERIFY is for the optical disk labels
when cartridge unmounting is requested.
export VERIFY or NOVERIFY is for the optical disk labels
when cartridge export is requested.
OPERATOR Three valid keywords for the OPERATOR entry are in the JBM
configuration file as follows:
OPERATOR = {
path = /usr/ip32/jbm,
module = OPMmain,
filename = /usr/ip32/jbm/OPMlogfile
},
The path and module were described previously. The filename is
the name of the output file containing operator messages.
ERRORLOG
Two valid keywords for the ERRORLOG entry are in the JBM
configuration file as follows:
ERRORLOG = {
filename = /usr/ip32/jbm/error.log,
debug = OFF
}
4 Intergraph Corporation - 2/94
JBCFG(4) CLIX JBCFG(4)
The filename is the name of the output file containing error
messages. The debug defines the modules that print debug output.
The value of debug can be "all" if all modules are to print debug
messages or the first three letters of a module name as follows:
RTR RTRmain
VRS VRSmain
OPM OPMmain
JBC JBCmain
JBI JBImain
JBD JBDmain
If debug messages are needed from more than one module, list the
module prefixes separated by semicolons. If debug has no value, no
debug messages are written to the error log.
FILES
/dev/gs/* Generic SCSI device files.
/usr/ip32/jbm/JBCFG Jukebox configuration file.
RELATED INFORMATION
Commands: jbconfig(1), jbstart(8)
2/94 - Intergraph Corporation 5