RRTJOB is used so infrequently, it isn't surprising even Barbara Morris and Scott Klement don't know what it does.
RRTJOB basically restarts the job. It deallocates EVERYTHING the job had allocated to that point and restarts the job. If the RRTJOB command is encountered in a CL program, the CL program effectively exits on the command. You can use it to switch the job to a different storage pool or a different class (eg, interactive or batch).
RRTJOB would surely end and clean up the jvm. The behavior described is not a bug. However, to work for the OP, there would have to be a special routing entry made that would start a program to handle the application of the updates and then reroute the job back to it's original routing to restart the rpg program.
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Wednesday, November 03, 2010 7:05 AM
To: Java Programming on and around the IBM i
Subject: Re: .jar files in use on a restore
I'd say that the only reliable way to end the JVM is to end the job.
Reading through that thread, nobody (including Barbara Morris and Scott Klement) seems to understand why RRTJOB would have the effect of cleaning up the JVM. It seems to have been back on v5r3, so perhaps it was a bug that has been fixed by now.
On Tue, Nov 2, 2010 at 5:35 PM, Dan Kimmel <dkimmel@xxxxxxxxxxxxxxx> wrote:
I did some poking around and found this reference:
Apparently the only reliable way to end the jvm and clean up all the references as you need it to is RRTJOB.
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l
As an Amazon Associate we earn from qualifying purchases.