|
<snip>*ALLTAPE) RSTDDEVRSC(*NONE)
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
test those changes there first before making any changes to production LPARAnd the rest have ALWDEVRSC(*UNRSTD) RSTDDEVRSC(*ALLOPT *ALLTAPE) ?
No, I've only made those changes on our development LPAR. I wanted to
It just may be on a different device name. In this case, OPT17.
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.
WRKIMGCLG shows it's ready in OPTVRT01. But a WRKOBTVOL on the host doesn't
Well, I thought the image catalog was loaded, verified, and ready. A
https://archive.midrange.com/midrange-l.
--
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
questions.
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
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.