Re: What's wrong with this picture?

There are two NWSDs here but all devices are restricted on the first one.

FYI Everything works fine once I deleted them and created my own. (I
wanted a different name anyway.) It's just a curious that there were two
appearing when I really didn't think that was even possible.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 1/25/2013 2:28 PM, Evan Harris wrote:

I've seen something similar to this (duplicate device names) when
there is more than one NWSD and the devices aren't restricted on
either of them.

I've also ended up with additional devices on the guest when restoring
storage spaces; seems like the old devices get restored and new ones
get created based on the virtual scsi connections.

I managed to clean some of it up by deleting the descriptions, varying
off the NWSD allocated for tape, then varying it back on.

Dunno which, or if any of this applies in your situation but for what
it's worth...

On Sat, Jan 26, 2013 at 6:11 AM, DrFranken <midrange@xxxxxxxxxxxx>

wrote:

IBM i 7.1 on POWER7 with TR5. This is a guest partition with an IBM i

host.

Work with Device Descriptions

2=Change 3=Copy 4=Delete 5=Display 6=Print 7=Rename
8=Work with status 9=Retrieve source


Device Type Text
TAP01 3580 CREATED BY AUTO-CONFIGURATION
TAP02 3580 CREATED BY AUTO-CONFIGURATION
TAP03 3580 CREATED BY AUTO-CONFIGURATION
TAP03 3580 CREATED BY AUTO-CONFIGURATION
TAP04 3580 CREATED BY AUTO-CONFIGURATION


This is only one object in QSYS with the name TAP03 however.

Any attempt to vary it on results in CPD8EB4 "Device vary on failed."

Deleting one of them also deleted the other.

Curious.....
--

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.