Script in boot sequence

Hi ,
I have some problems with my library when the sytem boot :

When HPUX is booting, HPUX and STAPE claim the drive initially. HPUX assigns an instance

number. The instance number is tied to the hardware path. Near the end of the boot, the ATDD driver claims the drive from

STAPE based upon the Inquiry ID (either ULTRIUM-TDx or ULT3580.TDx, where x=1, 2 or 3 depending on the drive

generation.) When ATDD claims the drive, it generates the special file based on the instance number. This is the standard

way devices are handled with HPUX. If a drive is moved, host is rebooted or for other undefined reasons HPUX will assign

a different instance number, which will generate a new special file when ATDD claims the drive.

For some reason that is not understood, HPUX will sometimes claim a drive, or number of drives, with a different instance

number, even if the hardware path does not change. When this happens the new instance numbers do not match up with

the existing special files, and the customer has a problem. Although, it is not understood why this happens, but this is not

an uncommon problem for a HPUX customer to have.

====>
Answer from IBM :
The following commands can be run manually or scripted to run during bootup
So as an example, if they want to assign the instance number for the following two drives.

tape 90 1/0/0/0.97.19.255.2.6.0 atdd CLAIMED DEVICE IBM 03590E11

tape 35 1/0/0/0.97.20.255.2.7.0 atdd CLAIMED DEVICE IBM 03592J1A

You do this for each drive: STEP 1

rmsf -H 1/0/0/0.97.19.255.2.6.0

rmsf -H 1/0/0/0.97.20.255.2.7.0

ioscan -M atdd -H 1/0/0/0.97.19.255.2.6.0 -I 1 <=this change it to instance number 1

ioscan -M atdd -H 1/0/0/0.97.20.255.2.7.0 -I 2 <=this change it to instance number 2

Then you do this: STEP 2

/opt/atdd/bin/atdd_claim

These steps could be automated by creating a script and putting the new script in the boot up sequence."

Question :
====> Can you confirm me that i have to create my script with the differents drives .I have to create a sh file with the rmsf commands of my differents hardware path and ioscan with the new instance number.
It's only that?

Thanks

     DElphine

I have never heard of the atdd driver before your post. Some googling revealed a lot of people having problems with this driver and HP-UX. I don't have your IBM tape drive nor your driver, but I think I understand the problem. The problem is that the stape driver is not compatible with the IBM tape drive. stape is willing to claim the drive but then cannot use it. Does atdd sit on top of stape? Or do you also have other tape drives that use stape? I would simply remove stape from the kernel.
kmsystem -S /path/to/system-file -c N stape
followed by rebuilding the kernel should do that with HP-UX 11.0 or 11i. This seems very easy but I can't find any instance of anyone else suggesting it, so there may well be a problem with it.

If stape and atdd must co-exist in the same kernel, I would give up on autoconfig fot atdd tape drives. This post suggests:

I can't test that. But that would be my second choice for something to try.