|
Stephen, In a message dated 98-01-06 10:07:25 EST, you write: > I'm passing a parameter to a CLP that is later used as a command for > QCMDEXC. The parameter is defined as having a length of 256. However, > there appears to be a lot of garbage trailing after the value that is > passed. > > I'm sure I've seen a workaround for this, but have had no luck in finding > it. Be careful passing between CLP and RPG programs. If you pass, say 2, 256 byte parameters from an RPG program to a CLP then to another RPG, the second RPG program parameters will "walk over" each other if all 256 bytes of the first parameter are not filled out. BPCS uses a CLP to submit RPG programs from other RPG programs, and checks the last byte of the first parameter to see if it is blank -- if so, it places an "X" in the last byte of the first 256 byte parameter to prevent "walk over"... HTH, Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-Mail: DAsmussen@aol.com "It is impossible to make anything foolproof, because fools are so ingenious." -- Anonymous +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.