Roll out them changes, smitty, s'il vous plait!
AnthonyEnglish 270000RKFN Visits (8394)
You have several Unix print queues to create. Some are of type HP JetDirect, others ASCII. Some have customised settings for page width, lines per page and so on. The best way is through SMIT, but it takes a long time to step through the menus. And you have to replicate this onto several LPARs.
The initial print queues on the first LPAR might take some time, but once you've got them all in place, you can rerun the SMIT commands on the target LPARs exactly as they were done on the source LPAR. Let me explain.
Whenever you run SMIT, the commands it invokes to make configuration changes are saved to the file smit.script (usually in your home directory). That's really a Korn shell script of all the SMIT commands since the last time the file was cleared out.
Better still, you can invoke smit from the command line with its own file to store the commands. Use smit -s and specify an alternate script file:
smit -s add_printers.ksh
You can then either copy that file to the remote LPARs and execute the script, or even run it from your local LPAR using ssh or dsh.
Using SMIT with its recording of all commands into a script is a simple way to roll out configuration changes. That way the hard work is only done on the first LPAR. As they say in Aix-en-Provence:
(Pardon the French.)
It's the first step that costs
It takes ages to set up a whole bunch of printers on the first LPAR, but every LPAR after that should be a breeze, as long as you use smit.scriptResources (English and French)