×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
<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?
midrange.com
