Actually, I tend to agree. But not all programs called from the command line are expected to be called from the command line. In the case of development and program testing, it is common to simply dummy up a call and let 'er rip.... In these cases, the extra byte is an easy and effective means of overcomming this issue.
In cases where the program is EXPECTED to be called from the command line, then I agree whole-heartedly.
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
Sent: Tuesday, October 16, 2007 11:43 AM
To: Midrange Systems Technical Discussion
Subject: RE: Send Email from the AS400 - quit working!
One common workaround that can be easily tested from the
command line is to sepcify your 50 byte parm value with 51
characters, with the last character being a non-blank value.
This forces the command interpreter to allocate 51 bytes (50
bytes of real data, and one byte that never gets read by your
(not aiming this at you personally Eric)
IMHO, it's a pretty silly work around.
The right answer, is to build a *CMD front end for the program.
Build commands is so easy, I don't understand why people refuse to do so.
This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.