What is being reported is that the slot being accessed by the process was
reported as  address 99 when ADSM first booted (or when the library was
defined), but now that slot is being reported by the library as 0 when you try
to run your checkin/audit.

Did you do a library re-configuration, or microcode change of any kind?   The
information from the library is received via the basic ReadElementStatus SCSI
command.  You can run that command by using the lbtest facility, select options
1, 6, 8, and 9. The output from option 9 will be for each slot and will tell
among other things the address.  That may help you figure out the problem.

You can recycle ADSM to rebuild it's list of slot addresses, provided that the
library is reporting them correctly.  Otherwise, you're going to need to
contact service.

Craig Bell