|
It appears to be there from Eclipse (or WDS). IBM still working on this.I pinned the timing down to around the end of the INZSYS after doing the V5R4 upgrade.
The cume was started about 5 minutes later. jim----- Original Message ----- From: <vhamberg@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, November 21, 2006 1:08 PM Subject: Re: SAV with SAVACT(*YES) halted on Eclipse objects
Not sure why a CUME would do this, but it might not be the case. To clarify, I was not saying that Eclipse or WDSC were ever run on this box. I was suggesting that someone may have chosen to put their workspace on this box, either through a mapped network drive or with the network locator. I'm not sure how to find out who might be doing it - might be an owner on the objects. There might be something inside that folder, too, to give you a clue, such as filter names, other config stuff.HTH Vern-------------- Original message -------------- From: "Jim Franz" <franz400@xxxxxxxxxxxx>>don't put Eclipse or WDSC workspaces in the IFS... Vern - I didn't... WDSC or an Eclipe has never run on this box. Websphere server never setup. This is old fashioned SEU & RPG II,III,IV. The timestamps on these files indicate they came from cume C6192 ptfs (including hiper & db2 groups) I installed after the V5R4 release. jim----- Original Message ----- From: "Vernon Hamberg"To: "Midrange Systems Technical Discussion" Sent: Tuesday, November 21, 2006 8:55 AM Subject: Re: SAV with SAVACT(*YES) halted on Eclipse objects > Uffda! All I can say is, don't put Eclipse or WDSC workspaces in the > IFS - someone is bound to have WDSC left open on their PC. And this > means not to put workspaces on a drive mapped to the IFS, of course. > > At 07:50 AM 11/21/2006, you wrote: > >>Is there something I need to shut down before SAV? >>V5R4 - this is 1st save after release upgrade that was not a >>dedicated system. >>(have not started any WDS or Eclipse functions that I know of. >>Have not had this problem on other V5R4 systems. >> >> >>5705 - SAV DEV('/QSYS.LIB/TAP01.DEVD') OBJ(('/*') ('/QSYS.LIB' *OMIT) >> ('/QDLS' *OMIT)) SAVACT(*YES) SAVACTOPT(*NONE) ENDOPT(*UNLOAD) >> UPDHST(*YES) >>Object in use. Object is >> /QIBM/UserData/Eclipse/workspace/.metadata/.applicationlock. >>Cannot open object >> /QIBM/UserData/Eclipse/workspace/.metadata/.applicationlock. >>Object in use. Object is >> >> /QIBM/UserData/Eclipse/workspace/.metadata/.plugins/org.eclipse.tomcat/c >> atalina.2006-11-19.log. >>Cannot open object >> >> /QIBM/UserData/Eclipse/workspace/.metadata/.plugins/org.eclipse.tomcat/c >> atalina.2006-11-19.log. >>Ownership of object QZLSCKSVR in QTEMP type *USRSPC changed.>>40703 blocks processed for sequence 401, volume IBMIRD, on device >>TAP01.>>107969 objects saved. 2 not saved. >>Function check. CPF3837 unmonitored by NITSAV at statement 5705, >> instruction X'0055'. >>CPF3837 received by NITSAV at 5705. (C D I R) >> >>jim franz>>-- >>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, >>visit: http://lists.midrange.com/mailman/listinfo/midrange-l >>or email: MIDRANGE-L-request@xxxxxxxxxxxx >>Before posting, please take a moment to review the archives >>at http://archive.midrange.com/midrange-l. >> -- > 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, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.--This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.