Re: Weirdness with EXTDESC, EXTFILE, EXTMBR, and a CPF5152

On 2014-06-16 16:31, James H. H. Lampert wrote:

...
It seems that in the real program, a WRITE QCLSRC will, for no apparent
reason, and after several successful WRITE QCLSRC statements were
already executed (otherwise it wouldn't have gotten that far), it will
throw a CPF5152.

The file is blocked, so the WRITE operations aren't going out to database until the block is full. At that time, the missing record format will be detected.

If you add BLOCK(*NO), you'll get the error on the first WRITE.

For the case of writing to source files, using a program-described file would probably be easier.

chg FMIMEBODY O F 92 DISK USROPN
F EXTFILE('QTEMP/MIMEBODY')
F EXTMBR('DFT')
add D mimeDs ds 92
add D seq 6a inz('000000')
add D date 6a inz('000000')
add D srcdta 80a
...
C EVAL SRCDTA = 'Sch...'
chg C WRITE MIMEBODY mimeDs