|
Is anyone else
having this problem? I am using MMAIL procedures to send Spool files in
various formats. I have a Data-Q handling program
that sits on a
Data-Q that is populated by Outq entry's getting to the ready state. I am
having 2 problems. I believe one is causing the other.
I see in the job log
of the Data-Q handler that a pgm message of Msgtype '*Esc' (Not a valid
type) is trying to be sent to the pgm message queue.
This is
happening from Subprocedure MimeSplPdf, I believe because the
spool file is no longer around (I don't know why it is gone). Subroutine
MakeSplNbr is having a hard crash because the RtvSplA Api Returned Nothing and
the SPLA data structure is not initialized and the blanks for the binary
fields equate to 077952576, and field SplASplNbr is attempted to be evaled
into field SplNbr5N + 1 with size of 5,0. The error
is Receiver
value too small to hold result. Now I only believe this is happening
because the Spool file no longer exists, but I don't believe there should be a
hard crash from the call to MimeSplPdf. I also think the message telling me the
Spool file does not exist should be able to be
sent.
Here is copy of a piece of a joblog that show this
happening
XXXMAILSND - MIME message submitted to MSF Library MMAIL already exists in library list. Object changed. '*ESC ' not valid for parameter MSGTYPE. Error found on SNDPGMMSG command. Object QIPS in library *LIBL not found. Library QFNTCPL added to library list. Library AFPTOOL added to library list. Receiver value too small to hold
result.
Function check. MCH1210 unmonitored by SENDMAIL at statement 0000165100, instruction X'0000'. The call to $SND_ESPL1 ended in error (C G D F). Job 532780/QPGMR/EMAIL held by user WACHE with option SPLFILE(*NO). Job 532780/QPGMR/EMAIL released by user WACHE. Below is the Job Log detail
info for *EXC not valid parameter
for msgtype type that was absorbed Message ID . . . . . . : CPD0084 Severity . . . . . . . : 30 Message type . . . . . : Diagnostic Date sent . . . . . . : 01/16/06 Time sent . . . . . . : 13:15:04
Message . . . . : '*ESC ' not valid for parameter MSGTYPE. Cause . . . . . : The value specified is not allowed by the command. Recovery . . . : Enter one of the values that is defined for the parameter, and try the command again. More information on parameters and commands can be found in the CL Reference manual or the appropriate licensed program manual. From program . . . . . . . . . : QCAFLD From library . . . . . . . . : QSYS Instruction . . . . . . . . : 0C65
To program . . . . . . . . . . : SENDMAIL To library . . . . . . . . . : CGILIB To module . . . . . . . . . : XXXPGMMSG1 To procedure . . . . . . . . : XXXPGMMSG1 To statement . . . . . . . . : 1100
Time sent . . . . . . . . . . : 13:15:04.546672 Below is the Job Log detail
info for Receiver Value too small Message ID . . . . . . : MCH1210 Severity . . . . . . . : 40 Message type . . . . . : Escape Date sent . . . . . . : 01/16/06 Time sent . . . . . . : 13:15:04
Message . . . . : Receiver value too small to hold result.
Message ID . . . . . . : MCH1210 Severity . . . . . . . : 40 Date sent . . . . . . : 01/16/06 Time sent . . . . . . : 13:15:04 Message type . . . . . : Escape From . . . . . . . . . : QPGMR CCSID . . . . . . . . : 65535
From program . . . . . . . . . : SENDMAIL From library . . . . . . . . : CGILIB From module . . . . . . . . : XXXMIME From procedure . . . . . . . : MIMESPLPDF From statement . . . . . . . : 165100
To program . . . . . . . . . . : SENDMAIL To library . . . . . . . . . : CGILIB To module . . . . . . . . . : XXXMIME To procedure . . . . . . . . : MIMESPLPDF To statement . . . . . . . . : 165100 Thanks,
Wayne Achenbaum
This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. This email message does not constitute a legal and binding agreement unless signed and authorized by an executive of the company. If you have received this email in error, please contact our email administrator directly by sending an email to [EMAIL PROTECTED]. YAHOO! GROUPS LINKS
|
