First, thanks everybody for the popup input. Setting that aside, I wonder if anybody has noticed problems with global dictionary functions?
In AREV, my routine for selecting ACCESSIBLE_COLUMNS first says "not a linear hash table, building list…" and then proceeds to select all dictionary items for all attached tables. When I run this routine in OI, I get only the dictionary items for the alphabetically first attached table.
The RList/OpenList documentation says that table MYTABLE serves as a global dictionary which is checked if a column name is not in the local table dictionary. This may have been added as a workaround when DICT.VOC went away, but how far does it go? For example, will dictionary items for MYTABLE be executed by the braces function {}?
In AREV, I believe DICT.VOC was a global dictionary for everything except the MERGE processor. At one time, RTI promised better access to execution of global dictionaries as a design goal. Hmm. As usual, comments welcome.
Gerald
Gerald,
Have you attempted to use SYSDICT for your global dictionary entries?
Of course I didn't try to use SYSDICT, Don. Thanks for mentioning it. So why is "MYTABLE" in the RList documentation? Or does "MYTABLE" use SYSDICT for its dictionary? Probably SYSDICT/MYTABLE is all a documentation controversy, which could be solved with a modest proposal from Ira.
My real problem was that the SELECT opcode of RTP59 is broken in OI, so that selecting ACCESSIBLE_COLUMNS does not work.
Gerald