OK... the changer spec, "TAPE.CHANGERS", sez:
##########################
<tpchanger> -info
Outputs to stdout three fields: the current slot string, the
number of slots, and whether the changer can go backwards (0
if it can't, 1 if it can). Same error handling as above.
Example:
% chg-multi -info
0 10 1 # exit code returned is 0
| | |
| | |
| | +--- Backwards capable (boolean-like value)
| |
| +------ Number of slots for this configuration (int-like)
|
+-------- Current Slot (int-like)
##########################
From the John Jackson notes that exist on the site previously known
as backupcentral, if the changer's configuration file specifies the
gravity flag as false, then the changer can perform what is called
"backwards" motion.
My question:
1) Is the notion of a current-slot undefined for all changers that
are capable of bidirectional (i.e. random access?) transport behavior
(i.e. the changer can go backwards)?
2) If current-slot is undefined, would it be OK to substitute "0"
for the value of $curslot in the "-info" command? If not, what value
should the changer script write out for the current_slot value when
backwards is true?
Thanks again...
J
