× 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.



Regarding the virtual devices, the answer is no, you must set it up the
proper restrictions. Email me privately if you want code examples or search
the archives. I've posted samples in the past.


--
Jim Oberholtzer
Agile Technology Architects

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

Rob,

On Thu, May 09, 2019 at 11:18:33AM +0000, Rob Berendt wrote:

Summarized: You configure multiple NWSD's for each guest.

One NWSD per guest serves up only tape and optical.
CHGNWSD NWSD(DOMTEST0) ALWDEVRSC(*ALLOPT *ALLTAPE) PWRCTL(*NO)

All the other NWSD's per guest serves up only disk.
CHGNWSD NWSD(DOMTEST1) ALWDEVRSC(*UNRSTD) RSTDDEVRSC(*ALLOPT *ALLTAPE)

It looks like I have a little work to do. Our host has two NWSD's
configured for each guest. From their descriptions it looks like one of
each pair was intended for disk and the other for tape. But they're both
configured with ALWDEVRSC(*UNRSTD) RSTDDEVRSC(*NONE). I wish we could
virtualize our tape library. But, from a document linked to in another
recent thread, with our tape library and SAS controllers we would only be
able to virtualize the library in serial mode. We'd loose all the library
functionality.

We have three guests, and multiple optical drives appear on each guest. The
host has one physical and one virtual optical drive. Each guest has three
or four type 632C virtualized optical drives showing up. One guest has one
optical drive with type *OPT. And each guest has one type 632B virtual
optical drive, which I think is local to each guest, not virtualized.

On this page:


https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzam4/rzam4clien
tvirtdevices.htm

it says:

If you define multiple Network Server descriptions, then you must use
the RSTDDEVRSC or ALWDEVRSC parameters to prevent the same device from
appearing multiple times on the client partitions.

I think I've also seen recommendations against that in some recent threads
here. Is there a better way to prevent the same device from appearing
multiple times on the guest partitions?





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.