I introduced that bug into my program. I wanted to use the IFSIO_H /COPY member that you had published from another article (or your IFS tutorial) for the write prototype rather than define it within the program like the example in the Communicating Through a Pipe article. In the IFSIO_H /COPY member, the data parameter for the write prototype is defined as a pointer, but in the article the prototype defined it as 32767A const options(*varsize) variable.
So when I changed the write statements for my program after following the example, I just wrapped the data parameter with the %addr BIF and didn't account for the length prefix that is part of the varying cmdtext variable.
Thanks again, Scott
________________________
Scott A. Schollenberger
Director, Research & Development
Schools division
Harris Computer Systems
2011 Renaissance Blvd, Suite 100
King of Prussia, PA 19406
Phone: 610-239-9988 x305
Fax: 610-239-9995
CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole use of the intended recipient(s) and contains confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.