RE: Return error to FTP RCMD

Steve,

If you DSPCMD SNDPGMMSG you'll see that *EXEC is not allowed for it, so you
can't execute it via QCMDEXC (the reason is that there's a parameter on the
command, KEYVAR, which returns a value).  Even if it worked, you'd get an
error on the call to QCMDEXC in your RPG, which would either get mugged by
RPG error handling or ignored, depending on what you tell the program to do.
There may be a way to get what you want without a CL, but I don't know how -
I'll be just as interested as you in any answers you get on that.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC
To subscribe to the MAPICS-L mailing list send email to
MAPICS-L-SUB@midrange.com or go to www.midrange.com and follow the
instructions.

-----Original Message-----
From: Steve Moland [mailto:Steve@Accessp.com]

I've an ILE RPG program which is called from FTP via RCMD and the RPG pgm
does various things based on the value of parameters.
 
Sometimes there are reasons the RPG pgm cannot complete it's tasks and I
want to raise some error message process so that an FTP's 550 message will
contain the text of a message I prepare from within the RPG pgm. For various
reasons I do not want to call the RPG pgm by calling a CL first.
 
I've tried used Qcmdexc from with the RPG pgm to do the following  SNDPGMMSG
MSGID(CPF9898) MSGF(QCPFMSG)  MSGDTA('THIS PGM FAILED') MSGTYPE(*ESCAPE)

 
After executing this I ended the RPG pgm normally. FTP got a 250 message for
a successful execution. I put the SNDPGMMSG in a CL pgm and called it
directly from FTP and my error text message appeared in an FTP 550 message.
 
Any ideas on why I can't accomplish sending back the error message from
within the RPG pgm. 
 
Steve Moland 
 
 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---