× 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 Mon, Sep 15, 2014 at 11:43 AM, <rob@xxxxxxxxx> wrote:
Thank you. But wouldn't PN be the key I'm looking for?
....+....1....+....2..
GRES GKEY GDES
PN * *
PC 08 *
PP
Do I have to substring this out and convert to binary?

Dawn's instructions were geared toward displaying things "with a few
clicks of the mouse". Doesn't sound like what you're doing here. ;)

Judging by the docs, it does seem that PN would be the key you want,
and that you have to do the conversion yourself.

However, out of idle curiosity, I looked for this file on my system at
work, and it doesn't seem (based on DSPPFM) that this file is properly
updated on my system.

First, there are four instances of QAPMCONF on each partition (we are
at 7.1, with one host, which has our production database; and one
guest, which has our testing/development database). The four
libraries are QMPGDATA, QPFRDATA, QSYS, and QSYSV5R4M0. Only the
first one has any data. The second one is a different format (with 14
fields).

On both partitions, the PN value is a single null byte, followed by
blanks (that is, x'00' followed by nine x'40'). Also, PC is a zoned
'01' (x'F0F1') followed by blanks.

Now, it must be said I have virtually no understanding of system
configuration or indeed any administrator tasks. Are the values I'm
seeing normal for our setup? Does something have to be run in order
to repopulate the file?

John Y.

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.