At 10:29 AM 4/14/98 -0700, Gavin Scott wrote:
>> On Apr 12, 12:02am, Jeff Vance wrote:
>> I can add:
>> S - being stored (or otherwise backed-up)
>
>That would be useful.
Agreed!
<snip>
>One question on the access column is whether the flags should be
>left justified in the field, or should there be an R column, a W
>column etc. Separate columns would make programmatic parsing and
>possibly visual scanning of a group of open files easier. Example:
>
>:listf @,11
>Account= A2345678 Group= OTHER
> RecSize EOF Limit Disk-Space
>Name---- RWES Code- ---(B) Type ---------(B) ---------(B) (K-1024-B)
>LARGE R 80 FA 500 1234567890 40
>LARGE1 RW 80 FA 12345678902 12345678902 987654313
>L2345678 WE AAAAA 999998 FBxx 999999999999 999999999999 9999999999
>STORE1 S 80 FA 12345678902 12345678902 987654313
>STORE2 S AAAAA 999998 FBxx 999999999999 999999999999 9999999999
Question: Is the "E" column for "Exclusive" or for "Execute"?
I'll vote for separate columns, and I'd add LOCK. I'm sure that many could
also make a good case for GMULTI, Mapped, and MultiRecord, and if there are
enough columns, maybe that should be considered. By the way, can't the
display go beyond column 72? I can't think of any reason for limiting the
output records to 71 bytes these days.
The RecSize display in units of bytes (as opposed to the old byte length
suffixed by "B" or word length suffixed by "W") is fine with me. Both the
old and new formats are fine by me.
I'd also like to see the file type field expanded to be positional as well.
After all, you have indicators for record format (F=Fixed, V=Variable,
U=Undefined, B=Bytestream, and perhaps redundantly S=SpoolerBlock), record
type (A=ASCII, B=Binary), file structure (K=KSAM, R=RIO, O=Circular,
M=Message, S=Spoolfile), and CCTL.
Below is another possible output format. Notice that:
- in the first header line, the "Account=" now begins in column 3 (so
the first character in the first three heading lines is a blank,
"Account=" is aligned over "Name", and "Group=" is aligned above
"Recsize"),
- there is a blank line following the "Account=" line for readability,
- the third header line begins with " Name " (so it like the preceeding
header lines begins with a blank),
- the fourth header line begins with "--------" so that another
non-alphanumeric character (the "-") begins the fourth header line
and now all four header lines begin with a non-alphanumeric character
and begin with either " " or "-",
- that I've expanded the access flags field to include columns for Lock,
GMulti, Mapped access, MultiRecord, and Copy access (but now have two
columns with an "R" heading - the first for Read, the second for
MultiRecord) and I'm using the first column of the access field (the
"E" column) for Exclusive and the column "X" for Execute access,
- and that the output record is now 74 bytes.
:listf @,11
Account= A2345678 Group= OTHER
Name Access FCode Record Type EOF File Limit Disk-Space
-------- ERWXLGMRCS ----- ------ ---- ------------ ------------ (K-1024-B)
BYTESTRM R 1 BA 12234 1234567890 12234
GMULTI RW LG 2048 VA 256 256 12345
LARGE R 80 FA 500 1234567890 40
LARGE1 RW 80 FA 12345678902 12345678902 987654313
L2345678 WX NMPRG 256 FB 99999999999 999999999999 9999999999
LOGFILE W G 4096 FAO 1122 2233 444
MAPPED RW L M 16384 FB 23456 23456 987654
MESSAGE W G 2048 VAM 1234 1234 2222
MSGCOPY R C 256 VAM 222 3333 3333
MULTIREC RW L R 128 FB 128 234565 1234545
OUTFL 133 VAC 11223 334455 334455
SPOOLFL OUTSP 1008 VACS 222 222 12345
STORE1 S 80 FA 12345678902 12345678902 987654313
STORE2 S NMPRG 256 FB 999999999999 999999999999 9999999999
....:....1....:....2....:....3....:....4....:....5....:....6....:....7....
John
--------------------------------------------------------------
John Korb email: [log in to unmask]
Innovative Software Solutions, Inc.
The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.
|
