HSM s not working properly
yes it is, it works according to Your parametrization not an hsm fault if You/Your support are incompetent==> do not know how to setup properly HSM
You might not ( be incompetent ) ...
blaming HSM for a poor parametrization shows certainly a poor approach to problem solving
and for sure a poor approach in asking help for Your issues
steps to take...
1st) get proper training in hsm, in reading and researching the manuals, lurking thru the ARC members in SYS1.SAMPLIB
2nd) check the <HSM> installation manuals on how to configure ARC... and friends for the proprer tape handling
3rd) last resort
SETSYS PARTIALTAPE(MARKFULL)
Migration and backup tapes that are partially filled during tape output processing are marked full. This enables a scratch tape to be selected the next time the same function begins. Marking tapes full enables full exploitation of the cartridge loaders because the cartridge loaders can be filled with scratch tapes between tape processing windows. MARKFULL should be used in a virtual tape environment to improve performance and improve backstore tape utilization.
When the total tape-media use and reducing recycle overhead are more important than cartridge-loader exploitation, PARTIALTAPE(REUSE) can be specified. In a REUSE environment, tapes are fully utilized and the amount of recycle processing is reduced. For more information about the PARTIALTAPE parameter, see Selecting a Scratch Pool Environment.
Because a request to recall a data set can “take away†a migration volume that is currently associated with a migration task, such a partial migration tape is created as if you had specified PARTIALTAPE(REUSE).
and my usual suggestion when I see such poorly worded questions
to make the most out of the questions You ask and to
forecast the comments You might receive it would be wise for You to read and meditate on
how to ask questions the smart way
here
http://catb.org/~esr/faqs/smart-questions.html or .. for a more PC language
here
http://support.microsoft.com/kb/555375