Save while active, isn't

On that save that is running for half a day (we canceled it) the IBM guy
on the phone seems to think it was waiting on a lock.
I said that the SAV command is using the SAVACT(*SYNC). He said that he
has seen it wait 3 days on a lock until it skips it and goes on. No one
can seem to determine how long it waits on a lock. I used iNav and the
job locking that IFS entry has been running since July. We've not always
had this problem.

I am being a stubborn mule. I don't think this is the issue but if it is
then IBM needs to fix SAVACT. He keeps trying to get me to find out what
is locking the object and then kill the lock and go on. My argument is
that if I do that will it then wait days on the next entry? He says yes.
Sounds like the classic never ending loop: Lather, Rinse, Repeat.

I asked him why it took hours upon hours to get the first CPFA09E and then
a flurry of them all within seconds? (Many different directories
involved.) He keeps going on and on about having to fix the lock on the
first object.

In summary: It's the customers problem. IBM has no responsibility to
either save the IFS objects regardless of locking, or flag the objects as
not saved and go on in a timely fashion.
My response to that would probably be blocked by many of your programs
that check for offensive language.

Rob Berendt