|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] My RPGLE program is named the same as the command and it works great. Perhaps your program was compiled with debug(source) and not list. And you thought you were debugging the current version, but you weren't? Hard telling. We've had some pretty sharp cookies here mess up with which version of the program they thought they were debugging. I remember seeing Cozzi had something just last week. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Peter_Vidal@pall.com Sent by: midrange-l-admin@midrange.com 07/29/2002 02:53 PM Please respond to midrange-l To: midrange-l@midrange.com cc: Fax to: Subject: Re: Command works with CL CPP and not with an RPG CPP "Did you follow the whole program debugging? Can you see where it deposits a value into RTNCOD when debugging?" Yes Rob. What I was not noticing as an impact is that my command and my RPG program had the same name: CHKJOBSTS. I have used commands and CPP with the same name and I have never faced any problems like this one. However, this is the first time I use an RPG program as my CPP. Anyway, I renamed the RPG program to end with an "R", recompiled everything and now is working as intended. What you think that happened here? Peter Vidal PALL Aeropower Corp. Senior Programmer Analyst _______________________________________________ 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.