|
Mike, Not what I had in mind, but I may have misread the original problem. Let me repeat it and you tell me where I've got it wrong: 1) you have an RPG program that calls a CL program. At this point everything is OK. Even if it passes a long (>32) char variable. 2) the above CL program calls another CL program which either creates or passes on a long (>32) char variable At this point everything is OK. 3) the second CL does a SBMJOB and tries to pass the long variable This is where the garbage comes in, and either the 'work around' or a command should solve the problem. You would have a SBMJOB cmd(newcommand var(&longvar)) instead of SBMJOB CMD(CALL CLPGM parm(&longvar)) HTH "Wills, Mike N. (TC)" wrote: > > Then just use QCMDEXEC to call it? > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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.