HP3000-L Archives

October 1996, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Vance <[log in to unmask]>
Reply To:
Jeff Vance <[log in to unmask]>
Date:
Fri, 11 Oct 1996 15:45:58 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Forwarded to list with Jerry's permission:

Subject: Re: Design for System CI vars (long)

>Forwarded from Paul Christidis:

/snip

>  >:showvar aa,bb ;format=detail
>>
>>VarName       Type      Scope     Owner        Access       Value
>>AA            INT       JOB                                 1
>>BB            STR[1]    SYS       MANAGER.SYS  R-only       2
>
>[snip]
>
>>Obviously the columns won't line up with long varnames, but you get the idea.
>
>
>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

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

/jf


--

ATOM RSS1 RSS2