Found the problem, Re: This is a weird one, re: email not getting out of our V6 box

Turns out that it was happening because I hadn't bothered to put a command front-end on the program.

The program (originally designed to be used as a module) accepts 4 parameters: 100-character sender, 100-character recipient, 100-character subject, and 20,000-character body.

No problem at all, when linking and calling it as a module. Big problem if calling it at the command line: the parameters were polluting each other!

And the polluted parameters were being passed on to QTmmSendMail, and essentially driving MSF insane. It wasn't returning an error message, but it wasn't sending anything, nor deleting the stream file (thankfully, the stream file name was coming from the fully-qualified jobname and the current time, not from the polluted parameters), and it apparently stopped up the pipeline for anything else trying to go through MSF.

I realized that late yesterday, when I finally got the idea to run the test program in the debugger, and the pollution became visible. This morning, I added a command front-end, and it immediately started working as if nothing had ever been wrong with it.

Out of morbid curiosity, what's the maximum parameter length a command front-end can prompt and pass to its CPP? I defined the "BODY" parameter as the full 20,000, and it compiled, but it isn't prompting no 20k.

--
JHHL