I used a PACK stage to make a VMFPLCD archive internet-friendly
and sent it to a client who uploaded it to his CMS system with
IND$FILE. Then, at my instruction, he did:
PIPE < fn ft1 fm | FBLOCK 1024 | unpack | > fn ft2 fm
Unfortunately, IND$FILE had padded with binary zeroes to a
multiple of 80 and neither FBLOCK nor UNPACK detected the
problem. I don't want to conceal the problem by either
padding or trimming the odd record. I want it reported.
My first thought is to leave the pipe paradigm with something
such as:
PIPE < fn ft1 fm | FBLOCK 1024 | > fn ft2 fm
COPYFILE fn2 ft2 fm (UNPACK REPLACE
which I believe will report the error. Is there an option
to either FBLOCK or UNPACK which will cause the error to
be reported.
I'm not very interested in adding a SPECS stage to detect
the odd record -- this is something I want the client to
be able to enter from the keyboard -- I place a premium on
minimum keystrokes.
I'm not very interested in VMARC, etc. Some clients may
balk at requirements beyond a pristine CMS system.
Thanks for any suggestions,
gil
