× 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.



The biggest danger when killing a save like that is damaged objects, potentially many of them. The danger is not the next time you run the save, it's right now when there are damaged objects.

The problem with IFS/DLO is save while active does not work (well at least) and is not available respectively. You are apparently getting the effects of SWA on the IFS not working well.

I think it will clean up the locks, but the damaged objects worry me a bit.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/11/2013 9:08 AM, J Franz wrote:
What (if any) are the consequences of a SAV command cancelled *immed-
it was cancelled after running couple hours (are the locks cleaned up?
Message . . . . : 17427 - SAV DEV('QSYS.LIB/TAP06.DEVD') OBJ(('/*' *INCLUDE) ('/ekdimage' *OMIT) ('/optmlb01' *OMIT) ('/qsys.lib' *OMIT) ('/qdls' *OMIT)) SAVACT(*YES) SAVACTOPT(*ALL) ENDOPT(*LEAVE) SAVACTMSGQ('/QSYS.LIB/QUSRSYS.LIB/OPERATOR.MSGQ') UPDHST(*YES) Any issues when run next time?
Jim
--

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.