×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
WO11BWFR2 (SQLRPGLE):
fqsysprt o f 80 printer
c *entry plist
c parm parms 39
c except exc01
c eval *inlr = *on
oqsysprt e exc01
o '>'
o parms
o '<'
Let's suppose that the combined value of &parms in WO11C is "300000YLAAPY0620012 " (that's 20 blank trailing spaces)
Now, here's the weird stuff:
If I run WO11C like you see, WO11BWFR gets this for variable parms: "300000YLAAPY0620012 "
If I change the call to a SBMJOB:
SMBJOB CMD(CALL PGM(WO11JQ0) PARM(&PARMS))
BO11BWFR gets this for parms: "300000YLAAPY0620012 CALLf " (that's 14 blanks before CALLf, 1 after)
If I change the SBMJOB to this:
SBMJOB CMD(CALL PGM(WO11JQ0) PARM('300000YLAAPY0620012 '))
WO11BWFR gets the parm correctly.
What am I overlooking?
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.