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
called program).


(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.


Charles



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.


This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].