Hi,

Here is another reply of mine to Jerry re. system vars:

On Oct 11, 11:51am, Jerry Fochtman wrote:
> Subject: (Fwd) Re: (Fwd) Re: Design for System CI vars (long)

I wrote:
> >  >:showvar aa,bb ;format=detail
> >>
> >>VarName       Type      Scope     Owner        Access       Value
> >>AA            INT       JOB                                 1
> >>BB            STR[1]    SYS       MANAGER.SYS  R-only       2

Paul C. wrote:
> >How about placing the 'variable length' items on the right side:
> >
> >:setvar DEFAULT_MENU "APPL_MAINTENANCE"
> >
> >:showvar aa,bb,def@ ;format=detail
> >
> >Type      Scope   Owner          Access    VarName|Value
> >INT       JOB                              AA|1
> >STR[1]    SYS     MANAGER.SYS    R-only    BB|2
> >STR[16]   JOB     MGR.USRACCT    R-only    DEFAULT_MENU|APPL_MAINTENANCE

Jerry wrote:
> Would be better if we had an intrinsic API as well so parsing the CI output
> was not an issue, but given effort/etc., the CI-output is better than
> nothing!  I tend to agree with Paul's suggesting in terms of placement of
> the variable length components....
>

Agreed.  I have thought about a varinfo() function.  Or maybe individual
functions like varaccess(), varscope(), varowner(), etc. are more
useful?  Anyway, I don't know what the extra cost is to implement these
functions but I will consider them!


thanks,
Jeff

--