×
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.
On 10-Dec-2015 09:56 -0600, CRPence wrote:
<<SNIP>> I suppose a RUNQRY *N QUSRSYS/QAMOVAR2 might just show the
/same/ data the WRKOPTVOL presents.?
OK, not so much; the msg CPF4234 is expected, so would prevent that.
No matter. There is a way to cheat, to enable seeing the data; aside
from Service Tools. Probably though, sufficient to just verify there is
a row\record of physical data, using the DSPFD [for *MBR info] of the
based-on physical named in the DSPFD of the logical; if there is an
active row and the WRKOPTVOL output should be empty, then probably that
record is whence the incorrect output is obtained. And if after the
relations are ensured to be proper, then there exists the option [after
taking a backup] of just Clear Physical File Member (CLRPFM) for which
the file /capabilities/ are ignored [verified by test]; of course, only
if the status remains, that the Work With Optical Volumes (WRKOPTVOL)
should present an empty list, should the member be cleared.
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.
midrange.com
