Re: savact consequences if job cancelled immed

I'll try & get the RCLLNK run before next save (have
to submit request to operations).
Thanks
Jim


________________________________
From: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, September 11, 2013 10:30 AM
Subject: Re: savact consequences if job cancelled immed


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