|
Peter: The only reasonable thing I can think of is that you missed a detail someplace and were not executing the program object that you expected. If simply changing the name of the compiled RPG program caused it to work (and I have to assume you changed the command definition object to match), then I don't see any other alternative. Library list problem maybe, authority to an existing compiled program maybe, but just changing the name? Doesn't make sense. Peter Dow's suggestion to alter or remove the *PSSR is useful, though it'll most likely only eliminate one or two possibilities (because you say it already works with no change except the name). If you can clearly demonstrate that the name change was the real culprit, I'd sure like to hear about it. Rename the compiled RPG program back to the original and change the command back too. Verify that only one *PGM object exists of that name and that the authority of the user running the command isn't changing things somewhere. Tom Liotta On Mon, 29 July 2002, Peter_Vidal@NSpall.com wrote: > 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? -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.