× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



At the breakpoint, do a DSPJOB.  Look at open files - your production file is probably open.  Look at active job overrides, to see if something is slipping in somehow.  Check the program stack, just to be sure the right programs are running.  DSPJOB (or WRKJOB) is as valuable for debugging this sort of problem as STRDBG, in my world.


I see your test libraries have the *PROD attribute, so you can't debug with UPDPROD(*NO).  Can you change them?  CHGLIB command.  The error message when the job tries to update the production file will give you extra detail, especially if there's something like a trigger program over a file that's interfering somehow (yes, far-fetched, but could happen).

 
Dave Shaw


________________________________
From: John McKee <jmmckee@xxxxxxxxxxxxxx>
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Sent: Tuesday, September 17, 2013 12:31 PM
Subject: Re: File opens in RPG III


Recompiled program.  NO optimization, LSTDBG.

STRDBG update production files, OPMSRC(*YES)

Set breakpoints on every UPDAT.

Stopped on one.  Did F21, DSPLIBL.  Only TST libraries in library list.
Production file modified.

Program ended, and still library list shows only test libraries.

Now what?

The job was submitted to a job queue in the test environment.  I do not
understand this at all.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.