When you have 15 lpars and you want to avoid customizing instructions for each lpar, it helps. The alternative is to update the instructions to make it a "teaching moment". However most of those people are just helping me out and only do this admin type stuff once a quarter and I'm grateful for that. The teaching moment might be lost. I've also found they tend to often ignore the paragraphs before instructions, preferring to copy/paste the commands from the PDF into the command line. I often get notes which are covered in the preceding paragraph. Again, I'm grateful for the help.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin Monceaux
Sent: Tuesday, May 14, 2019 10:11 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Renaming Resources (Was: Troubleshooting failure of new virtual optical drives on IBM i Host lpar failing to appear on IBM i guest lpar)
Rob,
On Fri, Apr 05, 2019 at 02:16:13PM +0000, Rob Berendt wrote:
I've even used STRSST to rename resource names to suit me.
I might be inclined to do the same thing, after some research on the subject. I recently tweaked our development LPAR's NWSDs to eliminate the "extra" virtualized optical drives. On the DEV LPAR that left me with OPTVRT01, local to the guest, and OPT02 and OPT03 virtualized from the host.
The optical drives on the host are OPTVRT01 and OPT01. I'd at the very least like to rename the devices on the guest, though the OCD in me might be tempted to go through the trouble of renaming the resources also.
midrange.com
