I agree with Dan. Exclude it from your save since it is easily
recovered in other ways, and does not change very often. Your
monthly/Quarterly full system saves should be plenty. (or after a
Chief Technical Architect
Agile Technology Architects
On 1/29/2013 9:01 AM, Dan Kimmel wrote:
Don't worry about backing it up every day. It changes only via PTF. Itis easily recovered if necessary.
for Java as well as a whole bunch of java classes for accessing IBMi API's.
jt400.jar is the Toolkit for Java. It contains the JDBC database drivers
It might have been in use from iNav or one of the HTTPSVR instances.
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Tuesday, January 29, 2013 8:50 AMbe as much save-while-active (SWA) as possible (the subject of a rather
To: Midrange Systems Technical Discussion
Subject: jt400.jar in use
I've spent a couple of weeks re-engineering our nightly BRMS backup to
long thread here).
hiccup. This *LINK object, /QOpenSys/QIBM/ProdData/acsi/lib/jt400.jar, was
I put it in production today and it ran flawlessly except for one little
not saved because it was in use. This was at 4:19am with no users signed
on. Controlling subsystem would have been started about 1 hour earlier,
and subsystem QHTTPSVR would have been ended when the error occurred.
today, but does not give a time. There is no WRKOBJLCK equivalent for IFS
When I drilled down in Navigator, it did indicate the file had been used
files, but I found this online CALL QP0FPTOS PARM(*LSTOBJREF
'/ifspath/ifsfile' *FORMAT2) that showed me there were no locks on it now.
<g>10 days and this particular file never showed up as being in use. My
I had tested the *LINK save as SWA close to a dozen times over the past
question is, essentially, why today? Was this a fluke? How can I find out
what was using this file at that time?
to be applied the next IPL, if that makes a difference.
I did download and stage the latest Java group PTF yesterday afternoon,
company. Unless I say so.
I just don't want this file getting missed every day.
VP Information Systems
P.O. Box 13369
Ft. Wayne, IN 46868-3369
The opinions expressed are my own and not necessarily the opinion of my
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact