Device and Media Management

This section provides a reference of the Backup command lines to use for device and media management. Some of the commands pertain specifically to the devices contained in an autochanger or silo; some commands apply specifically to SCSI devices, either standalone or in an autochanger.

The SCSI device library is a set of interfaces that Backup uses to communicate with SCSI devices. The SCSI devices are named in a platform-independent manner. The name assigned to the SCSI device is essentially a combination of b.t.l, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI logical unit number (lun) on that target.

A logical SCSI bus number may not be related to any specific platform hardware bus number; it may be a dense positive integer address space, that persists from system reboot to system reboot if the system hardware configuration remains the same. Target and lun information is contingent on the attached SCSI peripheral devices and their settings. Some platforms may allow dynamic addition and removal of SCSI devices, but may require a flush of the cached device information.

Typically, if a device does not have a system driver, users have permission to send SCSI device library commands. If a device has a system driver (for example, a tape drive), system privileges are required to send a command.

changers

The changers program lists the SCSI autochangers that are attached to the system.

The following example describes the format and options available for the changers program:

changers [-dv] [-a b.t.l] 

• Use the -d option to determine the names and addresses of the autochanger's media elements (for example, tape drives).

• Use the -v option to list more detailed information about each autochanger. The details provided may indicate how many media transports (MT), storage transports (ST), import/export elements (IE), and data transport (DT) elements the autochanger contains. The -v option also provides information about the element movement matrix supported by the autochanger.

• Use the -a option to identify a specific ordinal SCSI address for which you want to list information.

hpflip

The hpflip program reads a Vendor Unique mode page from an HP Optical disk drive and toggles or "flips" the device type between OPTICAL and DIRECT ACCESS. Typically, most systems include drivers that can deal with removable DIRECT ACCESS device types (which are often limited to 512 byte/sector formatted disks). Systems with these device types often do not also have device drivers for OPTICAL device types. The hpflip program enables you to control how an HP Optical Disk Drive reports itself, and thus makes the OPTICAL device type available where it otherwise would have required an additional device driver.

The following example describes the format and options available for the hpflip program:

hpflip -a b.t.l [-r] 

• You must use the required -a b.t.l argument to select a specific ordinal SCSI address, where "b" is the logical SCSI bus, "t" is the SCSI target, and "l" is the SCSI lun on that target.

• Use the -r option to reset the named device to OPTICAL, regardless of its current state. If you do not specify the -r option, the device type simply changes to the opposite of the current state.

ielem

The ielem program sends an INITIALIZE ELEMENT STATUS command to the named SCSI device.

The following example describes the format and options available for the ielem program:

ielem -a b.t.l [-r element-address.number-of-elements] 

• You must use the required -a b.t.l argument to select a specific ordinal SCSI address, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target.

• If your autochanger supports the Vendor Unique EXABYTE autochanger INITIALIZE ELEMENT STATUS command, use the -r option to initialize the element status for a range of elements. Specify the starting element's decimal address and the number of elements whose status you want to read.

inquire

The inquire program (in /etc/LGTOuscsi on Solaris systems) lists SCSI devices available. The inquire program returns INQUIRY data either for the named SCSI device (with the -a option) or for all SCSI devices attached to the system.

The following example describes the format and options available for the inquire program:

inquire [-c] [-a b.t.l] 

• Enter the optional -a b.t.l argument to select a specific ordinal SCSI address, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target.

• Enter the optional -c argument to force an INQUIRY command to be sent (to avoid picking up cached data that may be stale).

  The inquire program always uses the built-in system drivers to test SCSI devices. The device type or pathname printed by the inquire program may be incorrect for devices that require special, third-party drivers.

  ---

  Caution -

  The inquire program is not supported on HP-UX systems.

  ---

jb_config

The jb_config must be running on the Backup server or storage node.

The script pauses periodically for you to enter a response to a prompt. If you want to accept the default choice displayed in braces, simply press Return. If you want to enter a different value, type the entry and press Return.

After you configure the autochanger, use the nsrcap command or the Registration window to enter the enabler code for your Autochanger Software Module. You must have a separate enabler for each autochanger you want to use with Backup.

ldunld

The ldunld program sends a LOAD or UNLOAD command to the named tape device to load or unload media.

The following example describes the format and options available for the ldunld program:

ldunld {-u | -l} -a b.t.l 

There are three command options:

• You must use the required -a argument to select a specific ordinal SCSI address.

• Use the -l option to load media into a device.

• Use the -u option to unload media from a device.

libsji

The libsji program describes the Standard Jukebox Interface (SJI) Library. The location of the SJI library varies from platform to platform.

The SJI library is a public set of interfaces that Backup uses to communicate with jukeboxes. Generally, this library converts SJI commands (as formed by Backup) to the appropriate SCSI commands, but the underlying attachment to the jukebox is irrelevant to the function of this interface.

There are three entry points into the SJI library:

• void * sji_open (char * device-name)

  The sji_open entry point opens a channel to the SJI-compliant jukebox specified by device-name. A channel token of type void * is returned if successful, otherwise a NULL token is returned. You can express the device name as an ordinal SCSI type (for example, scsidev@b.t.l). The device name can also be a platform-specific style device name (for example, /dev/sjid1u1) for those platforms that do not use SunSoft device drivers.

• int sji_cmd (void *token, int cmd, void *arg)

  The sji_cmd entry point sends an SJI command to the device opened by sji_open.

• void sji_close (void *token)

  The sji_close entry point closes a channel to the device opened by the call to sji_open.

  The list of all the available commands and their arguments is too large to list here. Send e-mail to sji@legato.com to request more information on these interfaces.

lrescan

The lrescan program tells the underlying SCSI library to discard any cached information that it can and scan again for new devices.

lreset

The lreset program tells the underlying SCSI library to reset the named logical SCSI bus. You must have administrative privileges to execute this command, which has the following format:

lreset busnumber 

The lreset command can cause the destruction of vital data, because the command causes a SCSI bus reset. The command may also crash your system. You should only use the lreset command as an extreme last resort to quit a process that is not responding.

lusbinfo

The lusbinfo program prints out a limited amount of information about the SCSI buses attached to the system. If you use the optional -v argument, a verbose list of information about the devices in the attached SCSI buses is also printed. The following example shows the format to use for the lusbinfo program:

lusbinfo [-v] 

lusdebug

The lusdebug program sets a debug level for the underlying Backup SCSI device drivers. A debug level of 0 (zero) turns off debugging. Larger integers enable greater levels of debug information. If you enter an invalid debug level, the lusdebug program defaults to a debug level of zero. The following example shows the format to use for the lusdebug program:

lusdebug debug-level 

lusmode

The lusmode program prints a large amount of MODE information about the SCSI devices attached to the system.

msense

The msense program sends a MODE SENSE command to the named SCSI device and is only indented as input to the pmode command.

The following example describes the format and options available for the msense program:

msense -a b.t.l. [-p pagecode] 

• You must use the required -a b.t.l argument to select a specific ordinal SCSI address, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target.

• Use the -p option to select a specific mode page. If you do not specify a specific mode page, all pages are fetched (code 0x3f). You must specify the pagecode argument in hexadecimal notation.

nsrjb

The nsrjb program manages autochangers for Backup servers. Use the nsrjb command, rather than the nsrmm command, to label, load, and unload the volumes contained in an autochanger. Only one nsrjb command can access an autochanger at a time.

The nsrjb program attempts to determine which autochanger to use based on the options -j, -f, or a volume name. If one or more of these options do not uniquely identify an autochanger and one must be selected, the nsrjb program prompts you to choose an autochanger. Alternatively, you can set the NSR_JUKEBOX environment variable to the name of the autochanger you want the nsrjb program to use by default.

The following example describes the format and options available for the nsrjb program:

nsrjb [-C] [-j autochanger-name] [-v]

[-f media-device] [-S slots] [volume-name]
nsrjb -L [-j autochanger-name] [-gnqvM] [-R | -B]

[-Y | -N] [-b pool] [-f media device] [-e expire]

[-c capacity] [-o mode] [-S slots | -T tags]

[volume-name]
nsrjb -l [-j autochanger-name] [-nvqrMR]

[-f media-device] {-S slots | -T tags | volume-name}
nsrjb -u [-j autochanger-name] [-qvM]

[-f media-device] [-S slots -T tags] [volume-name]
nsrjb -I [-j autochanger-name] [-Ev]

[-f media-device] [-S slots | -T tags]
nsrjb -p [-j autochanger-name] [-v]

[-f media-device] [-S slots -T tags]
nsrjb -o mode [-j autochanger-name] [-Y]

{-S slots | media device}
nsrjb -H [-j autochanger-name] [-E] [-v]
nsrjb -h [-j autochanger-name] [-v]
nsrjb -U uses [-j] [-S slots | -T tags]
nsrjb -V [-j autochanger-name] [-v]
nsrjb -d [-j autochanger-name] [-v] [-S slots]

[-P port] [volume-name]
nsrjb -w [-j autochanger-name] [-v] [-S slots]

[-P port] [volume-name]
nsrjb -a [-j autochanger-name] [-v] -T tags
nsrjb -x [-j autochanger-name] [-v] -T tags
nsrjb -F [-j autochanger-name] [-v] -f media-device 

• Use the -b option to specify the pool to which you want to assign the volume. If you omit this option, the volume is automatically assigned to the Default pool.

• Use the -B option to verify that the volume does not already have a readable Backup label. If you specify this option and the volume has a Backup label, the label operation is canceled and an error message is displayed.

• Use the -c option to override the volume's default capacity.

• Use the -C option to display the current volumes in the autochanger and the associated devices. The -C option does not perform an actual inventory.

• Use the -d option to deposit (load into the jukebox) a cartridge from the cartridge access port (CAP).

• Use the -e option to override the default volume expiration date.

• Use the -E option to initialize element status for autochangers that provide this feature. You can use this option in conjunction with the -I or -H options.

• Use the -f option to specify a media device rather than the jukebox control port. Use the pathname of the media device displayed in the NSR jukebox resource.

• Use the -h option to display the actions and results of the past 100 autochanger commands issued.

• Use the -H option to reset the autochanger hardware (and the Backup database that represents the autochanger) to a consistent state. The autochanger clears the transport, and then unmounts and unloads volumes from the drives to slots. An inventory is not done (see the -I option). If the autochanger senses that the inventory is out-of-date, it prints an appropriate message.

• Use the -I option to perform an inventory on the autochanger's contents. The volumes in the specified slots are loaded into a device and their labels are read. Use this option to ensure that the mapping between slot number and volume name is correct. This option may take a long time to complete.

  For jukeboxes that have the element status capability (for example, the EXB-120, EXB-60, or HP optical models), you can use the -E option in conjunction with the -I option to reinitialize the autochanger's inventory state. The -E option increases the time it takes to inventory the autochanger, because the hardware must check every component, including all slots and drives, for the presence of media. You only need to use this option if you manually swap media in or out of an autochanger.

  Volumes from slots that are reserved for cleaning cartridges are not loaded during the inventory. If your autochanger does not support the element status or barcode reader features, you must use the -U option to enter a cleaning cartridge into the autochanger's inventory. If your autochanger does support either of these features, the cleaning cartridge is indicated in the inventory with the volume name "cleaning tape."

• Use the -j option to specify a particular autochanger for the nsrjb program to use. The given name is the one that you assigned when you created the NSR jukebox resource for the autochanger. If you supply the -j option, the NSR_JUKEBOX environment variable is overridden.

• Use the -l option to load and mount a volume. You must also specify a volume name or slot number.

• Use the -L option to label the volumes in the specified slots. If you do not specify any slots, the range of slots described in the NSR jukebox resource for the autochanger is used. If the autochanger has a barcode label reader and you set the NSR jukebox resource attributes "barcode reader" and "match barcode labels," the volume label is derived from the barcode label on the media, and the media barcode label will be stored in the Backup media database. If you set the NSR jukebox resource attribute "match barcode labels," the volume label is derived from the label template, although the media barcode label is stored in the Backup media database so that it can be used during inventory operations. You cannot label volumes that are in slots reserved for cleaning cartridges.

• Use the -n option, in combination with the -l option, to load a volume without mounting it. This allows the nsrjb program to control an autochanger that contains non-Backup volumes.

• Use the -N option, in combination with the -LR options, to tell nsrjb to skip the confirmation prompt. When Backup recycles volumes, you normally receive a prompt to confirm that it is okay to overwrite any volumes that Backup considers nonrecyclable.

• Use the -o option to set the mode of a volume or range of slots. Choose one of the following mode values: [not]recyclable, [not]read-only, [not]full or [not]manual. The [not]manual modes are the only valid modes when used with the -l option. If you do not give the -Y option, you are prompted to confirm the operation for each volume. See "nsrim " for a discussion of the per-volume flags.

• Use the -p option to verify and print a volume's label.

• Use the -P option to specify the CAP to load or unload a volume from.

• Use the -q option to run the nsrjb program in quiet mode. You can only use this option in conjunction with the -L, -l, and -u options.

• Use the -R option to recycle the volumes. If a volume is recyclable, you are not prompted to confirm the recycle operation.

• Use the -r option to load a volume as read-only. You can only use this option in conjunction with the -l option.

• Use the -S option to specify a slot or range of slots to operate on. The -l and -u options only accept one slot: the other options accept a range of slots. Specify the slot range in low to high integer order. The range is checked for validity against the Jukeboxes resource that describes the autochanger. You can only specify one slot range at a time.

• Use the -u option to unload a volume from a device or slot.

• Use the -U option with the uses argument to set the number of times a cleaning cartridge may be used. You can use the -T option in conjunction with the -U option to add cleaning cartridges to a silo, which also reserves a slot in the silo for each cleaning cartridge added.

• Use the -v option to tell nsrjb to display verbose information about the commands executed.

• Use the -V option to display vendor-specific status information. When you combine the -V option with the -v option, the configuration of the autochanger is also displayed.

• Use the -w option to withdraw (unload from the jukebox) a cartridge to the CAP.

• Use the -Y option to disable the prompt for confirmation.

  The following options are only valid for Silo Tape Libraries (STL):

• Use the -a option, in conjunction with the -T option, to allocate volumes in an STL for use by a Backup server or storage node. You must allocate a volume before you label it for Backup to use. You can add the -d option for silos that support the deposit (also known as importing or entering) of tapes through the silo's I/O port. The -d option must appear after the -a option on the command line. This function is usually handled by the silo management software, but is provided here for ease of use. The deposit option may not be supported on all the silos that Backup supports. See the -x option for a description of how the volumes are removed from an STL's list of volumes available for use by a Backup server.

• Use the -F option to release a shared device contained in an STL. This option is only available for tape libraries that support shared devices.

• Use the -T option to specify the tags or barcodes of volumes contained in an STL. You can specify a single volume tag or a volume tag template, which is similar to a regular Backup label template. The volume tag template consists of a list of template fields separated by slashes (/), whereas a Backup label template consists of an alphanumeric string or alphabetic or numeric range.

• Use the -x option, in conjunction with the -T option, to remove volumes from the STL's list of volumes available for use by a Backup server or storage node. You can add the -w option for silos that support the withdrawal or ejection of tapes through the silo's I/O port. The -w option must appear after the -x option on the command line. The silo management software usually handles this function, but it is provided here for ease of use. The withdrawal option may not be supported on all the silos that Backup supports. See the -a option for a description of how the volumes are allocated to an STL's list of volumes available for use by a Backup server.

nsrmm

The nsrmm program provides a command line interface to manage the media and backup devices used by Backup servers and storage nodes.

The following examples describe the format and options available for the nsrmm program:

nsrmm [-C] [-v | -q] [-s server] [-f device]
nsrmm -m [-v | -q] [-s server] [-f device] [-r]

[volume-name]
nsrmm -l [-v | -q] [-s server] [-f device] [-myB] [-e expiration] [-c
capacity] [-o mode] [-b pool] [-R | volume-name]
nsrmm {-u | -j} [-v | -q] [-s server] [-y]

[-f device | volume-name]
nsrmm -p [-v | -q] [-s server] [-f device]
nsrmm {-d | -o mode} [-v | -q] [-s server] [-Py] [S ssid[/cloneid] |
-V volume-id | volume-name...] 

• Use the -B option to verify that the volume you want to label does not have a readable Backup label. If you specify this option and the volume has a valid Backup label, the label operation is canceled and an error message is displayed.

• Use the -b pool option to specify the pool to which the volume should be assigned. If you omit this option, the volume is automatically assigned to the Default pool. If you specify a pool name without specifying a volume name, the next volume name associated with the pool's label template resource is used.

• Use the -C option to display a list of Backup-configured devices and the volumes currently mounted in them. The information is gathered from what the server inventory shows, and does not perform an actual volume operation, unlike the -p option described later. The -C option is the default.

• Use the -c option to override a volume's default capacity. Backup normally uses built-in default capacities, based on the device's type. The format of the specification is number multiplier. Number may be any value, including an integer or real number, with up to three decimal places. Multiplier may be one of "K" (1024 bytes), "M" (1000K), or "G" (1000M). Lowercase letters are acceptable, as are extra characters.

• Use the -d option to delete the client file indexes and media database entries from the Backup databases. This action does not destroy the data contained on the volume: instead, it removes all references used by Backup to the volume and the user files contained on it. You can use this option to control the size of the Backup databases.

• Use the -e expiration option to set the expiration date for volume relabel. This option overrides the default label expiration, which is two years. The value of expiration is entered in the format described in a special value of forever that is used for migration and archive volumes means that the volume label never expires.

• Use the -f device option to explicitly specify a device. When you configure more than one device, the nsrmm program selects the first device by default.

• Use the -j option to eject a volume from the device. This is similar to performing an unmount operation, except that the volume is also physically ejected from the device, if possible. This option is not available with many devices and media types.

• Use the -l option to label a volume for Backup to recognize and use. You must physically load the volume into the device, either by an operator or autochanger, before the label operation can proceed.

• Use the -m option to mount a volume in a device. The mount operation is performed after the volume is placed in the device and labeled; therefore, only labeled volumes can be mounted. You can combine the label and mount operation in one command line.

• Use the -o mode option to set the mode of a volume, save set, or save set instance (clone). Choose one valid mode value: [not]recyclable, [not]readonly, [not]full, [not]manual, or [not]suspect. The [not]recyclable mode applies to volumes or save sets, but not to clones. The [not]readonly, [not]full, and [not]manual modes are the only valid modes you can use with the -l option. The [not]suspect mode applies only to clones. You must specify the [not]suspect mode if you use the -S option with an ssid/cloneid specification. You do not need to specify the [not]suspect mode if you only specify ssid with the -S option. The suspect flag is set automatically when a recover operation encounters a media error when attempting to recover data from a particular save set clone.

• Use the -P option in conjunction with the -d option to purge the corresponding client file index entries, without deleting the entries in the media database. You can then use the scanner command to recover the file index entries.

• Use the -p option to verify and print a volume's label. When you use this option, mounted volumes are unmounted to verify the label.

• Use the -R option to relabel a volume. This option rewrites the volume's label and purges the client file index entries for all of the user files saved on the volume. Some of the volume usage information is maintained.

• Use the -r option to mount a volume as read-only. Volumes that are marked as full and volumes whose mode is set as read-only with the -o option are automatically mounted as read-only.

• Use the -s server option to specify the Backup server on which you want to invoke nsrmm.

• Use the -S ssid option with the -o option to change or the -d option to remove a save set from the Backup databases. The save set is specified by an ssid. A save set instance (clone) can only be specified with the -o option, using the format ssid/cloneid. You can use the mminfo program to determine the ssid and cloneid values.

• Use the -u option to unmount a volume. You should always unmount a volume before you unload it from a device.

• Use the -V volid option in conjunction with the -d option to remove a volume from the Backup server's media database. You can determine the value of the volume identifier (volid) with the mminfo program.

• Use the -v option to run the nsrmm program in verbose mode.

• Use the -y option to turn off confirmation of potentially destructive operations before nsrmm performs them. Use this option with extreme caution.

pmode

The pmode program parses the data output by the msense program and prints the output in a format that you can read.

The following example describes the format and options available for the pmode program:

pmode [-f filename]

• Use the -f filename option to specify the input file to use for the pmode program (the file output from the msense program). If you do not specify the input, standard input is assumed.

  The output from the pmode program is similar to the following:

  mars# msense -a 0.0.0 -p 0x03 | pmode Mode Header: mdl=35 mtype=0x0 dparm=0x10 bdlen=8 Block Desc[0]: dens=0x0 nblks=3933040 blklen=512 Fixed Page, code 0x03 (Format Device): tracks_per_zone: 0xf alt_sectors_per_zone: 0x22 alt_tracks_per_zone: 0x0 alt_tracks_per_vol: 0x0 sectors_per_track: 0x5e data_bytes_per_sect: 0x200 interleave: 0x1 track_skew_factor: 0x8 cylinder_skew_factor: 0x11 SSEC: 0x0 HSEC: 0x1 RMB: 0x0 SURF: 0x0

relem

The relem program sends a READ ELEMENT STATUS command to all changers, or to the (optionally, with the -a option) named device.

The following example describes the format and options available for the relem program:

relem [-a b.t.l] [-fvtb] [-m {0|1|2}] [-r element-address.number-of-elements] 

• Use the -a b.t.l option to select a specific ordinal SCSI address, where "b" is the logical SCSI bus, "t" is the SCSI target, and "l" is the SCSI lun on that target (for example, scsidev@0.4.0).

• Use the -b option to have the returned element status data dumped as ASCII hexadecimal codes, rather than decoded information.

• Use the -f option to receive full, somewhat verbose output.

• Use the -m {0|1|2} option to indicate the method for obtaining element status data. If you specify -m 1, element status data is fetched for each element type (for example, all drive elements are read at once, then all slot elements, and so forth). If you specify the default method -m 2, element data is fetched on a per element basis.

• Use the -r element-address.number-of-elements option to read a range of addresses, where element-address is the starting decimal address (in the autochanger's numbering sequence) of the element to start from and number-of-elements is the number of elements of status to read.

• Use the -t option to print any volume tags encountered.

• Use the -v option to receive verbose output.

sjidopen

The sjidopen program tests the SJIDOOROPEN command on SJI-compliant autochangers. The SJIDOOROPEN command tests the open/close capability of the main door to the autochanger. If an autochanger does not support this feature, an error message is returned. The following example shows the correct usage for the sjidopen program:

sjidopen device-name

The device-name option used with the sjidopen program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, "t" is the SCSI target, and "l" is the SCSI lun on that target (for example, scsidev@0.4.0).

sjiielm

The sjiielm program tests the SJIIELEM command on SJI-compliant Jukeboxes. The SJIIELEM command tests the Initialize Element Status interface for an autochanger. If the autochanger does not support the element status feature, an error messages is returned. The following example shows the correct usage for the sjiielm program:

sjiielm device-name [{drive | slot | inlt | mt} address number-of-elements]

The device-name option used with the sjiielm program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target (for example, scsidev@0.4.0).

The additional options described next are for use with autochangers that support the initilization of a specific range of elements. If the autochanger supports this feature, select one of the following element types:

• drive

• slot

• inlt (import/export element)

• mt (media transport)

  Specify the SJI normalized address (for example, starting from 1) and the number of elements to initilize.

sjiinq

The sjiinq program tests the SJIINQ command on SJI-compliant autochangers. The SJIINQ command returns a string that identifies an autochanger. If the autochanger does not support this feature, an error message is returned. The following example shows the correct usage for the sjiinq program:

sjiinq device-name

The device-name option used with the sjiinq program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target (for example, scsidev@0.4.0).

sjirdp

The sjirdp program tests the SJIRDP command on SJI-compliant autochangers. The SJIRDP command reads SJI ordinal device positions from an autochanger. The following example shows the correct usage for the sjirdp program:

sjirdp device-name

The device-name option used with the sjirdp program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, tis the SCSI target, and l is the SCSI lun on that target (for example, scsidev@0.4.0).

The following example represents typical output from the SJIRDP command:

scsidev@0.4.0 has 2 DATA TRANSPORT Elements starting at address 1

scsidev@0.4.0 has 1 MEDIA TRANSPORT Element starting at address 1

scsidev@0.4.0 has 25 STORAGE Elements starting at address 1

scsidev@0.4.0 has 1 IMPORT/EXPORT Element starting at address 1

sjirdtag

The sjirdtag program tests the SJIRTAG command on SJI-compliant autochangers. The SJIRTAG command reads media presence and tag data from an autochanger. The following example shows the correct usage for the sjirdtag program:

sjirdtag device-name

The device-name option used with the sjirdtag program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target (for example, scsidev@0.4.0).

The following example represents typical output from the SJIRTAG command:

Tag Data for 0.4.0, Element Type DATA TRANSPORT:

Elem[001]: tag_val=0 pres_val=1 med_pres=1 med_side=0

Tag Data for 0.4.0, Element Type STORAGE:

Elem[001]: tag_val=0 pres_val=1 med_pres=1 med_side=0

Elem[002]: tag_val=0 pres_val=1 med_pres=1 med_side=0

Elem[003]: tag_val=0 pres_val=1 med_pres=1 med_side=0

Elem[004]: tag_val=0 pres_val=1 med_pres=1 med_side=0

Elem[005]: tag_val=0 pres_val=1 med_pres=0 med_side=0

Elem[006]: tag_val=0 pres_val=1 med_pres=1 med_side=0

Elem[007]: tag_val=1 pres_val=1 med_pres=1 med_side=0

VolumeTag=<00000098>

Tag Data for 0.4.0, Element Type MEDIA TRANSPORT:

Elem[001]: tag_val=0 pres_val=1 med_pres=0 med_side=0

sjirelem

The sjirelem program tests the SJIRELEM command on SJI-compliant autochangers. The SJIRELEM command reads media presence and origin data from an autochanger. The following example shows the correct usage for the sjirelem program:

sjirelem device-name

The device-name option used with the sjirelem program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target (for example, scsidev@0.4.0).

The following example represents typical output from the SJIRELEM command:

Element Data for 0.4.0, Element Type DATA TRANSPORT:

Elem[001]: pres_val=1 med_pres=1 med_side=0

Origin: type STORAGE, address 5

Element Data for 0.4.0, Element Type STORAGE:

Elem[001]: pres_val=1 med_pres=1 med_side=0

Elem[002]: pres_val=1 med_pres=1 med_side=0

Elem[003]: pres_val=1 med_pres=1 med_side=0

Elem[004]: pres_val=1 med_pres=1 med_side=0

Elem[005]: pres_val=1 med_pres=0 med_side=0

Elem[006]: pres_val=1 med_pres=1 med_side=0

Elem[007]: pres_val=1 med_pres=1 med_side=0

Element Data for 0.4.0, Element Type MEDIA TRANSPORT:

Elem[001]: pres_val=1 med_pres=0 med_side=0

sjirjc

The sjirjc program tests the SJIRJC command on SJI-compliant autochangers. The SJIRJC command reads internal configuration information and options about an autochanger and prints it out. The following example shows the correct usage for the sjirjc program:

sjirjc device-name

The device-name option used with the sjirjc program represents any device name that can be used to reach an SJI-compliant autochanger driven by the system, typically in the form b.t.l, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target (for example, scsidev@0.4.0).

The following example represents typical output from the SJIRJC command:

Device: scsidev@0.4.0

Number of Drives: 1

Number Drive Pairs: 1

Number of Import/Export Elements: 0

Number of Import/Export Pairs: 1

Number of Slots: 7

Number of Slot Pairs: 1

Number of Transport Elements: 1

Number of Transport Pairs: 1

Initialize Element Status Supported

Auto Eject Supported

tur

The tur program sends a TEST UNIT READY command to all SCSI devices attached to the system, or, if the optional -a b.t.l argument is specified, then the device at the specified ordinal SCSI address, where b is the logical SCSI bus, t is the SCSI target, and l is the SCSI lun on that target. The following example shows the format to use for the tur program:

tur [-a b.t.l]