topic Re: lost printer--model script connections in migrate in Operating System - HP-UX

lost printer--model script connections in migrate

Lisa Sorbo — Tue, 13 May 2003 23:43:36 GMT

migrating from box1 10.20 to box2 11.0. used SAM to save & restore printers. the association between printer id & model seems to be lost - i have to delete & re-add the printer and re-choose the model id in order for it to work.
Did I miss a step?
When I use hppi and select modify - there is no modelscript shown for the printer. is there a way to fix this on a large scale or transfer it over?

Lisa

Re: lost printer--model script connections in migrate

Bill Hassell — Wed, 14 May 2003 01:26:37 GMT

Make suere HPPI was installed on the 11.0 system (it isn't by default depending on how old your 11.0 install CD might be. I don't know whether SAM was updated to handle HPPI configratio s correctly at 10.20 (10.20 is obsolete next month and most of it's life, JetAdmin was the JetDirect support application). However, it is very easy to delete and re-add the printers without using the interactive menu. Just use removequeue and addqueue:

cd /opt/hpnpl/bin
./removequeue -qprinter1
./addqueue -qprinter1 -h12.34.56.78

Re: lost printer--model script connections in migrate

Lisa Sorbo — Wed, 14 May 2003 06:05:48 GMT

yes, hppi is installed. I've gone to modify the printer - but I don't have the choice to select the modelscript - if I delete it (with sam) and then add it again (with sam or directly hppi) I can choose the model name and it all works. I can't see from your example how/when to select the modelscript and that seems to be what causes the hang-up.

Re: lost printer--model script connections in migrate

Lisa Sorbo — Wed, 14 May 2003 06:07:51 GMT

also - I've got easily 100+ definitions to do and no printed documentation about which printer model goes with each (though I could guess I suppose) - which is why I was looking for a way to bring over that info from box1 to box2.

Re: lost printer--model script connections in migrate

Bill Hassell — Wed, 14 May 2003 10:37:12 GMT

The association of the printer and the model script is automatic with addqueue. That's why the printer must be online. addqueue queries the printer type and then picks the right model script. Model scripts are very simple prepend/postpend filters so an exact match is not necessary. That's why the new crop of printers in the last couple of years all use the generic net_ljx000 script.

You might also look at transferqueue which is designed to move large JetDirect queues. transferqueue is in the /opt/hpnpl/bin directory and has a man page. Another useful tool is multiaddqueue and to see the printer script automatic associations, use:

/opt/hpnpl/bin/multiaddqueue -l

Re: lost printer--model script connections in migrate

Lisa Sorbo — Wed, 14 May 2003 15:38:19 GMT

Perfect!
the removequeue / addqueue sequence worked great - but before I wrote a script to do this for all printers, I used the transferqueue utility and it worked for all printers (at least, for the ones I've sent test prints to so far).

Thanks for your help!