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



As Walden said, looks like the first part is the table of contents. Each entry 
appears to be 32 bytes long with the system value name in the first 10, then 
the offset past a base offset that is to be found in the first 2 bytes of the 
SPACE. Then the length of the data, then some stuff that probably indicates 
whether a list or a data type or whatever - none of which I am prepared to 
reverse-engineer. I've told you here my guesses in reverse-engineering, but 
this is just not a good idea, although a strange kind of fun.   ;-)

As an example, QSYSLIBL has offset 0 and length x96 (150 - duh, that means 15 
library names - whadya know?) The offset to QUSRLIBL is x98 - so what about the 
extra 2 bytes? Looks like they are how many elements there are in QSYSLIBL - 
this is 'way too much fun folks but unproductive. Use PRTSYSINF or RTVSYSVAL - 
and get something to check the history log for change messages.

Vern
-------------- Original message -------------- 
From: rob@xxxxxxxxx 

Initially the DMPSYSOBJ OBJ(QWMSYSVAL) CONTEXT(QSYS) looks like a possible 
way of getting the list of system values. Until you get way further down 
into that resultant spool file. Then the formatting doesn't look quite so 
pretty. What starts out as (after a few lines of fluff): 
+....9....+.. 
*QDECFMT 
*QDATFMT 
*QDATSEP 
*QDATE 
*QYEAR 
*QMONTH 
*QDAY 
*QTIME 
*QHOUR 
*QMINUTE 

quickly degenerates into: 
+....9....+....0....+....1....+....2 
*QLOGOUTPUT * 

*QALWJOBITP * 
* * 

*QSYS QSYS2 QHLPSYS QU* 
*SRSYS * 
* * 
* * 
* QTEMP * 
* QGPL * 
* * 

* QCTL QS* 
*YS UPS QUSRSYS *NON* 
*E /MDY ENUUS $0* 
*110200010000000000050000000002*D* 
*MPUSRJOB1 102EF8C*NONE * 

So counting on the format of this can be as ugly as parsing a spool file. 
Perhaps parse the WRKSYSVAL spool file to get the list of system values, 
then use the api, or RTVSYSVAL to stuff the values somewhere. 


Rob Berendt 
-- 
Group Dekko Services, LLC 
Dept 01.073 
PO Box 2000 
Dock 108 
6928N 400E 
Kendallville, IN 46755 
http://www.dekko.com 





"Walden H. Leverich" 
Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx 
06/08/2006 12:31 PM 
Please respond to 
Midrange Systems Technical Discussion 


To 
"Midrange Systems Technical Discussion" 
cc 

Subject 
RE: Where are system values stored? 






Thanks, everyone. Parseing Ye Old Spoole File is what I'll be doing. 

For 70-some-odd machines it's also not unreasonable to write a CL that 
does a RTVSYSVAL for each system value and drops the current value into 
a database -- possibly centralized. Then run this CL each day and keep a 
running history of system values and their changes. 

Getting a complete list of system values is rather trivial, just dump 
the space Al mentioned and you can copy/paste them right into a CL. 
Probably take 30 minutes to have the complete system up and running, and 
you won't be relying on the format of the system value print. 

-Walden 

-- 
Walden H Leverich III 
Tech Software 
(516) 627-3800 x3051 
WaldenL@xxxxxxxxxxxxxxx 
http://www.TechSoftInc.com 

Quiquid latine dictum sit altum viditur. 
(Whatever is said in Latin seems profound.) 

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list 
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options, 
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives 
at http://archive.midrange.com/midrange-l. 


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
To subscribe, unsubscribe, or change list options, 
visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
or email: MIDRANGE-L-request@xxxxxxxxxxxx 
Before posting, please take a moment to review the archives 
at http://archive.midrange.com/midrange-l. 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.