Re: Is there an easy way to list the sizes of all the members of a source PF?

Hello James,

in addition, because you feel your src pfs seem rather big: Every line
(record) occupies the given maximum length at CRTSRCPF time, no matter if
there's just one character or more. Src pfs are not varlen enabled. Thus,
they tend to become filled with mostly *BLANKS, depending on which kind of
text is saved there.

If you create src pfs with a "better safe than sorry" maximum record
length, then this effect becomes worse.

A clear plus for positional RPG! Yeah! :-D

SCNR ;-)

You can work around this effect with not relying on src pfs at all, but
place all source files in the IFS in the unix-compatible tree (/ or
/QOpenSys). Since this isn't record oriented, this kind of wasted space
cannot happen.

(There might be other kinds of space wasting, though. Like a minimum file
size: One char, and the smallest file is already allocated a certain size.
Additional space is usually allocated in that particular block size. On V4
this was as big as 64kBytes. Duh! IBM was most likely happily selling
bigger disks because a simple 500 Bytes HTML page for "eCommerce" was
allocated 65536 Bytes. In 7.2, it's 8KBytes.)

:wq! PoC

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com