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



All,
I am having some difficulties with retrieving the list of exported procedures with api QBNLMODI.
I want to use the format MODL0100
Here is what the documentation says :

The MODL0100 format lists the symbols defined in the module and that are exported to other modules. The following table shows how this information for each module is organized. For detailed descriptions of the fields in the list,
**Note:* Do not use the generic header entry size for this format. Use the Size of this entry field returned in this format for the size of each entry.*

Offset Type Field
Dec Hex
0 0 BINARY(4) Size of this entry
4 4 CHAR(10) Module name
14 E CHAR(10) Module library name
24 18 CHAR(1) Exported defined symbol type
25 19 CHAR(3) Reserved
28 1C BINARY(4) Offset to exported defined symbol name
32 20 BINARY(4) Length of exported defined symbol name
36 24 CHAR(10) Uses argument optimization (ARGOPT)
46 2E CHAR(*) Reserved
Module information through offsets
CHAR(*) Exported defined symbol name


This format is different than the one I use usually as I cannot retrieve the header first.
I cannot use QUSRTVUS to retrieve the list.
Would anyone have an example of how to work with a format like this ?
Thanks in advance,

Regards,
Manuel

Ps: Thanks Mihael.

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.