If the *MODULE was compiled with DBGVIEW(*LISTING) or (*ALL), the debug view can be used to access a copy of source. ILE programs don’t have source; they are created from compiled modules. The modules have source. The module attributes point back to the location of source at compile time.
There have been one or two vendors that have claimed the capability, though I haven’t seen a claim for objects compiled after V5R2. Comments that I’ve seen indicate a cost high enough that it’s economical for many programs; but for one or two programs, it’s cheaper to rewrite them.
I can’t think of a reason programs would not all be compiled with DBGVIEW(*ALL) during the past ten years or more. ISVs, of course, would be different; but in 7.1, the debug view can be encrypted.
I dont have authority to debug this rpgle object
How can you sufficiently test your code if you don’t have authority to debug it? You don’t have to be the one. Get one of your coworkers to do it. — Tom
we have a rbo job which will be run to get all the log of the jobs run per that day.
when we go into the RBO job we could see this RPGLE pgm is been called. so want to see that pgm. we dont have the code fot that.
There is no known way to retrieve ILE source for a HLL module, except for debug views. If this isn’t your program, you’re probably in violation of your license by attempting to access source. There’s probably a “reverse-engineering/decompile/etc.” clause. — Tom
we have a requirement to create a program with a parameters as a date and it should work similar to rbo job. so want to see the code of that object
It doesn’t matter why you want to see it. If it’s not your program, you can’t see it unless the vendor lets you see it. Since you already know what the program should do, you need to write your own. That’s why programmers are hired. — Tom