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



Hi Keith!.
Yep, you're right!, because I just realized that few minutes after I sent
this question to the MI400 list.
In fact, I followed these steps to figure out where those offset were
located:

For the *LIBL offset:
1 - DSPLIBL and then write down the first library on the list
2 - DMPSYSOBJ OBJ(*PCS)
3 - DSPSPLF FILE(QPSRVDMP) SPLNBR(*LAST)
4 - Search for the library name you wrote down and you'll find the offset to
the beginning of the *LIBL

For the QTEMPPOS offset (this trick is valid for any release >= V5R1):
1 - DMPSYSOBJ OBJ(*PCS)
2 - DSPSPLF FILE(QPSRVDMP) SPLNBR(*LAST)
3 - Search for this pattern: "0000010C 00000000"
4 - Once you found it, write down the offset value of the eighth byte next
to the pattern. This is the QTEMPPOS offset.
Here an example:

001DE0 0000010C 00000000 00000000 00040008
------------------------------ ---
| |
| |
Search pattern QTEMPPOS offset

So, the final offset list is:

DCL DD LIBLPOS450 BASPCO POS(H'4FF') BIN(2);
DCL SYSPTR .LIBL450(25) BASPCO POS(H'511');

DCL DD LIBLPOS510 BASPCO POS(H'1D6F') BIN(2);
DCL SYSPTR .LIBL510(250) BASPCO POS(H'1D81');

DCL DD LIBLPOS520 BASPCO POS(H'1DEF') BIN(2);
DCL SYSPTR .LIBL520(250) BASPCO POS(H'1E01');

DCL DD LIBLPOS530 BASPCO POS(H'1DEF') BIN(2);
DCL SYSPTR .LIBL530(250) BASPCO POS(H'1E01');

DCL DD LIBLPOS540 BASPCO POS(H'218F') BIN(2);
DCL SYSPTR .LIBL540(250) BASPCO POS(H'21A1');

Regards,
Matias.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.