Not enough of a problem to be worth reporting, but a bit of a curiosity, and 
I'm wondering if anyone else has seen this.

We have a 3584 logically partitioned by ALMS into two libraries: gobi, with 10 
LTO-4 drives and around 150 LTO-4 tapes; and sahara, with 6 LTO-2 drives and 
about 250 LTO-2 tapes.

All the LTO-4 volsers start 444 and the LTO-2s start 333 - and we have ALMS set 
to do library auto-assign for the I/O door content based on the first three 
digits of the tape label.

We have two tapes that NEVER auto-assign and always end up in the ALMS 
'unassigned' logical library. But the ALMS I/O slot display shows the proper 
volser (333026L2 and 333063L2 are the trouble-makers). We just select them, use 
action assign, and run our normal checkin with no problem.

I just find it a bit fascinating that the 3584 can scan the volser  correctly, 
report it properly to ALMS, and ALMS can report it properly to TSM - but ALMS 
doesn't seem to recognise these two volsers for the auto-assign function. It 
doesn't matter how many tapes are in the I/O station, nor which I/O station 
these two are in (we have the four-station option on our 'D' modlue, and we 
have run in up to 96 tapes at one time - with these being the only two 
unassigned).

Jus an idle curiosity -

Tom Kauffman
NIBCO, Inc

________________________________
CONFIDENTIALITY NOTICE: This email and any attachments are for the
exclusive and confidential use of the intended recipient. If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.