RE: Virtual Ethernet and NFS Image Catalogs

One of the reasons I dislike the virtual optical support vs. the NFS
approach is each time the NWSD is varied off/on it "might" create a new
virtual optical resource on the target (hosted) system. To combat that
problem, I almost always remove all the virtual optical devices on the
target and then recreate them by vary off/on the NWSD from the host.

Now I have what it created just then in front of me.

Be sure all the other optical devices on the host are varied off. I suspect
you might be getting duplicate copies of the virtualization and the system
gets confused about which one to read.


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Wednesday, May 15, 2019 8:09 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Virtual Ethernet and NFS Image Catalogs

Good luck with that. Open a PMR?

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Kevin
Monceaux
Sent: Wednesday, May 15, 2019 9:00 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Virtual Ethernet and NFS Image Catalogs

Rob,

If I check an image catalog's entries right after loading it, one shows to
be mounted. But if I then refresh that display a few moments later they all
just show to be loaded. Shortly after loading an image catalog something
appear to be unloading the loaded image.

On Wed, May 15, 2019 at 11:28:20AM +0000, Rob Berendt wrote:

<snip>
But a WRKOBTVOL on the host doesn't find any volumes, and a DSPOPT
*MOUNTED OPTVRT01 says OPTVRT01 is empty </snip> No.
Not only does the
WRKIMGCLG CUME
need to show
Image ASP
Catalog Status Type Threshold Device
CUME Ready Optical *CALC OPTVRT01
But the
WRKIMGCLGE CUME
Also needs to show one entry mounted, as in
Index Status Image File Name
*AVAIL
1 Mounted CUME_3.bin
2 Loaded CUME_4.bin
3 Loaded CUME_5.bin
4 Loaded CUME_6.bin
5 Loaded CUME_7.bin
6 Loaded DB2S6216V01.BIN
7 Loaded CUME_1.bin

Then it will appear in WRKOPTVOL

Volume Device
C5450886_01 OPTVRT01

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Kevin Monceaux
Sent: Tuesday, May 14, 2019 4:08 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Virtual Ethernet and NFS Image Catalogs

Rob,

On Tue, May 14, 2019 at 07:45:00PM +0000, Rob Berendt wrote:

Did you change all your NWSD's to only have one with ALWDEVRSC(*ALLOPT

*ALLTAPE) RSTDDEVRSC(*NONE)

And the rest have ALWDEVRSC(*UNRSTD) RSTDDEVRSC(*ALLOPT *ALLTAPE) ?

No, I've only made those changes on our development LPAR. I wanted to

test those changes there first before making any changes to production LPAR
NWSD's.

As soon as I run the following on the host:
LODIMGCLG IMGCLG(V7R3CUME) DEV(V7R3CUME) WRKOPTVOL I immediately see
the same thing I saw in WRKOPTVOL on the host appearing on the guest.

It just may be on a different device name. In this case, OPT17.

Well, I thought the image catalog was loaded, verified, and ready. A

WRKIMGCLG shows it's ready in OPTVRT01. But a WRKOBTVOL on the host doesn't
find any volumes, and a DSPOPT *MOUNTED OPTVRT01 says OPTVRT01 is empty.
Could our production LPAR's NWSD's that still need adjusting be causing
this?

--

Kevin
http://www.RawFedDogs.net
http://www.Lassie.xyz
http://www.WacoAgilityGroup.org
Bruceville, TX

What's the definition of a legacy system? One that works!
Errare humanum est, ignoscere caninum.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at

https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com