That's why they are so cryptic. Why TIU for documents instead of DOC? Why Mag 
for images instead of IMG? Every time I see the list of Routines I feel lost.

Alberto

Quoting Kevin Toppenberg <[EMAIL PROTECTED]>:

> Alberto,
> 
> You probably already know this, but the reason the module names are so
> cryptic is because the first 3-4 characters are used for the namespace
> (i.t. TIU for documents, MAG for imaging etc.)  and then they have to
> fit their entire module name into 4-5 characters.
> 
> Kevin
> 
> 
> On 9/28/05, Jim Self <[EMAIL PROTECTED]> wrote:
> > The Fileman files with numbers in the range between 9 and 10 seem to be
> > intended as part
> > of what you are asking for.
> >
> >
> http://vista.vmth.ucdavis.edu/query?
dbfile=FILE&format=NAME&index=FileNo&find=9.4:9.8
> >
> > File number 9.8 (ROUTINE) fields for brief and extended descriptions as
> well
> > as for
> > globals referenced, local variables used, tags and parameters, routines
> > invoked, routines
> > invoked by etc.
> >
> >
> http://vista.vmth.ucdavis.edu/query?dbfile=ROUTINE&format=EXTENDED&index=Name
> >
> > Unfortunately, all of these are blank in my OpenVistA installations.
> Anyone
> > here know what
> >  to invoke to update this data from current routine sources?
> >
> > Alberto Odor wrote:
> > >Tens of thousands of VistA routines are stored in Cache (in the
> database)
> > >and in GT.M (in the file system), their names are really cryptic to say
> > the
> > >less.
> > >
> > >
> > >
> > >Is there some way to know what each routine does without having to open
> > >each of them and try to find out? Is there some document which has this
> > >info in some ordered way?
> > >
> > >
> > >
> > >If not, is there some way to make a "Map" of how the routines interact
> > with
> > >each other? UML? Something else?
> > >
> > >
> > >
> > >Alberto Odor
> > >Mexico City
> >
> > ---------------------------------------
> > Jim Self
> > Systems Architect, Lead Developer
> > VMTH Computer Services, UC Davis
> > (http://www.vmth.ucdavis.edu/us/jaself)
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads, discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > Hardhats-members mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Hardhats-members mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> 




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to