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



Thank you, JeanMichel!  Now I see the DIM, BIT, etc. information is stored
in the symbol table, not the program creation template, so I'll have to
modify my RTVMISRC and DSPSYMTBL utitilites to handle these items.
Occassionally we've seen symbol table entries from old programs with the
"array segment present" and "extension segment present" bits set; now we
know what it means.  Here's how the debugger shows multi-dimension arrays
from the following MI source code:

DCL DD AAA AUTO CHAR(24) INIT("ABCDEFGHIJKLMNOPQRSTUVWX");
DCL DD BBB DEF(AAA) POS(1) CHAR(1) DIM(3,8);

The debug command DSPPGMVAR 'BBB(1,*)' displays the following:

'A'  'B'  'C'  'D'  'E'  'F'  'G'  'H'

The debug command DSPPGMVAR 'BBB(*,1)' displays the following:

'A'  'I'  'Q'

Also I found the MI compiler accepts an LBL statement that references a
prior branch point like this:

HERE: CPYNV X,1;
      CPYNV X,2;
      LBL HERE;

If the LBL statement occurs before the branch point the compiler gives
fatal error CPF6313, "Label not declared before being referenced to in LBL
statement."  I don't know the purpose of LBL.


+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

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.