RPG Object verification

25 pts.
Tags:
AS/400
iSeries RPG programming
RPG
Hi, I need to verify if a RPG object on our production AS/400 is the same as on our test box. I used to to look at object size, but it doesn't always seem to be a consistent way to determine if two objects are the same. Any other way, to determine if two RPG ojects are the same?

Answer Wiki

Thanks. We'll let you know when a new response is added.

If you STRDBG on the programs, you can see if the source is the same.

Discuss This Question: 5  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    Is it OPM RPG or ILE RPG? Tom
    125,585 pointsBadges:
    report
  • DeonFourie
    Thanks , it is a RPGLE object. I also found when I do: DSPPGM PGM (objectname ) DETAIL(*MODULE) I get the Module creation date/time, which should be the same if the objects are the same. Regards Deon
    25 pointsBadges:
    report
  • TomLiotta
    I get the Module creation date/time... That's a reasonable place to look, but looking at the module description with option 5 is much better. To automate, review the List ILE Program Information (QBNLPGMI) API. Also, it's important to read and to understand the 'help' text for the UPDPGM MODULE() parameter. What you see with DSPPGM is not necessarily what you get. Tom
    125,585 pointsBadges:
    report
  • DeonFourie
    Thanks for the help and the information ! Had a look at the API, we will incorporate it into a batch program to verify the objects. Regards Deon
    25 pointsBadges:
    report
  • TomLiotta
    I create a list of *PGM objects in a library, then pass each one through the API to get a list of *MODULEs back. From each of those, I extract bits like source file name, source change date, etc., and INSERT records into a basic table. I run that utility against a number of production libraries on a regular basis. Every once in a while, I need either to locate where some module is used or to verify source dates or whatever. A simple SELECT ... WHERE... with the module name brings up a list immediately. The utility rarely takes more than a minute or so to "document" every program in a library, so there's little cost in running it often. (I also have a similar setup for *SRVPGMs.) The API can go a long way towards answering many kinds of questions. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following