|
Were all the parms in the program being submitted defined as 15,5? When you do a SBMJOB or a CALL from the command line the system defaults numerics as 15,5. I suspect this is the cause of your problem. Scott Mildenberger > -----Original Message----- > From: Fran Denoncourt [mailto:BobNFran@escapees.com] > Sent: Tuesday, October 23, 2001 10:22 AM > To: midrange-l@midrange.com > Subject: RE: Recursive CL - Data decimal error > > > Made an attempt at going the data area route but it failed, > also. So, I > ended up changing the RPGLE / CL to pass/receive a character field > instead. But, still wanted to know why this happened. > Thanks > At 12:11 PM 10/23/2001 -0400, you wrote: > >This message is in MIME format. Since your mail reader does > not understand > >this format, some or all of this message may not be legible. > >-- > >[ Picked text/plain from multipart/alternative ] > >Fran, I don't know the answer for the truncation, but I > think you might be > >able to push the value to a dataarea if that is the the only issue? > > > >-----Original Message----- > >From: Fran Denoncourt [mailto:BobNFran@escapees.com] > >Sent: Tuesday, October 23, 2001 11:40 AM > >To: MIDRANGE-L@midrange.com > >Subject: Recursive CL - Data decimal error > > > > > >Is there a known bug with calling a CL recursively passing > decimal data as > >a parameter to the CL? > >I don't seem to have any problems with a character field. > But if I pass > >numeric and logical, part of the data seems to get truncated when the > >second pass is run. > >The first pass checks to see if it is an interactive job. If > so, it submits > >itself passing the two input parameters from an RPGLE > program: numeric > >(*DEC 9/0) and and indicator (*LGL). The error occurs when I > use a CHGVAR > >command with the numeric field. > >If I remove the SBMJOB code and let the execution drop through to the > >CHGVAR, no problem. > >Thanks, > >Fran Denoncourt > > > >_______________________________________________ > >This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > >To post a message email: MIDRANGE-L@midrange.com > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > >or email: MIDRANGE-L-request@midrange.com > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/midrange-l. > >_______________________________________________ > >This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > >To post a message email: MIDRANGE-L@midrange.com > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > >or email: MIDRANGE-L-request@midrange.com > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
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.