Retrieve RPGLE source from object

[jamief]

Just found this thought it could be of some use (attachment)
by JR Friedman

It is possible to retrieve source from RPG programs if the program has been
 compiled with the correct parameters. The following procedure will retrieve the 
source from single-module RPGLE programs compiled with CRTBNDRPG with
 DBGVIEW(*LIST).

We have changed our command default to this option to allow debugging on our 
production machine, which does not contain program source. The program could 
be modified to handle RPG III programs compiled with OPTION(*LSTDBG) and 
multiple module ILE programs. As far as I know, the retrieval works with the
exception of list directives (i.e. /EJECT) and color/highlight special characters.

[gwilburn]

Just found this thought it could be of some use (attachment)
by JR Friedman

It is possible to retrieve source from RPG programs if the program has been
 compiled with the correct parameters. The following procedure will retrieve the 
source from single-module RPGLE programs compiled with CRTBNDRPG with
 DBGVIEW(*LIST).

We have changed our command default to this option to allow debugging on our 
production machine, which does not contain program source. The program could 
be modified to handle RPG III programs compiled with OPTION(*LSTDBG) and 
multiple module ILE programs. As far as I know, the retrieval works with the
exception of list directives (i.e. /EJECT) and color/highlight special characters.

Jamie - is this safe to use? I need to retreive CLLE source

[GLS400]

Hi gwilburn:

try the command rtvclsrc

Best of Luck
GLS

[gwilburn]

This does not work with CLLE only CLP

[GLS400]

I think rtvrpgsrc is rpg specific. (not sure)......Try debug and copy/paste.

Best of Luck
GLS

[JonBoy]

I think rtvrpgsrc is rpg specific. (not sure)......Try debug and copy/paste.

Best of Luck
GLS

It is.

Just to offer a suggestion - a lot of people do not like debugging at the listing level - finding that there is just too much "stuff". This retrieval method works if the *LIST view is present - which is why I recommend the use of *ALL for the debug view. The resulting object is very slightly larger, but as usual there is no effect on run time memory usage. This way you can debug using either *Source or *List views and have the ability to recover the source.

Also worth pointing out that this is a lousy substitute for a backup and version control strategy - way too dangerous as it can be screwed by any programmer who sets up their own custom PDM compile option and specifies their own personal favorite for the debug view.