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

It just gets weirder:

This, so far as we've been able to determine, only happens with one particular user, and it doesn't happen consistently.

Some relevant snippets of the source code:

14 FMIMEBODY O E DISK USROPN EXTDESC('<censored>/QCLSRC')
15 F EXTFILE('QTEMP/MIMEBODY')
16 F EXTMBR('DFT')

. . .

636 C CALL(E) 'QCMDEXC'
637 C PARM CLRMIMEBODY
638 C PARM 25 CMDLEN 15 5
639 C IF %ERROR
640 C CALL 'QCMDEXC'
641 C PARM CRTMIMEBODY
642 C PARM 32 CMDLEN
643 C ENDIF
644 C OPEN MIMEBODY

. . .

772 C EVAL SRCDTA = ' City: ' + %TRIM(ADCITY)
773 C + ' State/Province: ' + %TRIM(ADPROV)
774 C WRITE QCLSRC

. . .

947=OQCLSRC
*-----------------------------------------------------------
* RPG record format . . . . : QCLSRC
* External format . . . . . : QCLSRC : <censored>/QCLSRC
*-----------------------------------------------------------
948=O SRCSEQ 6S ZONE 6,2
949=O SRCDAT 12S ZONE 6,0
950=O SRCDTA 92A CHAR 80

14-16 shows how the MIMEBODY file is declared, using QCLSRC as a template (and as the format name), and QTEMP/MIMEBODY.DFT as the actual file. 636 attempts to clear QTEMP/MIMEBODY.DFT, while 640 creates it, if it wasn't found. 774 is NOT the first write to the QCLSRC format (which is really mapped into QTEMP/MIMEBODY).

Then, from the user's joblog, annotated with time and statement:
First, a message is constructed successfully, and sent successfully:

09:33:21.580586 stmt 636: File MIMEBODY in library QTEMP not found.
09:33:21.591595 stmt 640: File MIMEBODY created in library QTEMP.
09:33:21.599482 stmt 640: Member DFT added to file MIMEBODY in QTEMP.

[MMAIL/EMLMSG called]

09:33:21.628347: Buffer length longer than record for member DFT.
Object changed.
Object copied.
Link removed.
XXXMAILSND - 19 valid, 0 invalid recipient email addresses for MIME
message /MMAIL/temp/Q000000000001380.txt
Path name cannot begin with *.
Error found on CPY command.
Errors occurred in command.
09:33:21.677709: XXXMAILSND - MIME message submitted to MSF

[MMAIL/EMLMSG completed]

Then, the program gets called again, in the same job, and this time, it fails while the message is being constructed:

09:35:06.003078 stmt 636: Member DFT file MIMEBODY in QTEMP cleared.
09:35:06.003425 stmt 950: Record format QCLSRC not in member DFT.
09:35:06.003574 stmt 774: I/O error CPF5152 was detected in file MIMEBODY.
09:35:06.003633 stmt 774: Function check. RNX1299 unmonitored by WTNOTIFYR at statement
0000000774, instruction X'0000'.
09:35:06.003740: I/O error CPF5152 was detected in file MIMEBODY (C G D F).

I vaguely recall something like this coming up before, but I can't remember what the problem turned out to be.

--
JHHL