Hi Dave,
Not sure if this is you issue or not but we do have an APAR OA63738 that
affects FSM when migrating to WORM tapes where we have seen what you describe.
Take a look. If you still need help let me know the case # and I will look
into it.
Max Smith
DFSMS Development
-
On Mon, 6 Mar 2023 22:20:59 -0500, Rob Schramm wrote:
>Is CICS involved?
>
>Rob
>
>On Mon, Mar 6, 2023, 13:41 Joel C. Ewing wrote:
>
>> I see two possibilities:
>>
Hey there Rob.That's where it was detected first, however we've been able
to recreate outside of CICS. I now believe the pro
Is CICS involved?
Rob
On Mon, Mar 6, 2023, 13:41 Joel C. Ewing wrote:
> I see two possibilities:
>
> Either IAM is somehow managing to update the file in a way that doesn't
> end up with the changed bit set for the file -- might possibly happen if
> the file is never properly closed by the task
I see two possibilities:
Either IAM is somehow managing to update the file in a way that doesn't
end up with the changed bit set for the file -- might possibly happen if
the file is never properly closed by the task that updates it-- maybe if
the file is opened for update the changed bit only
Try VTOC backups after Recall 3 and update 5 and restore 7 and compare.
On Mon, Mar 6, 2023 at 11:08 AM Dave Jousma
<01a0403c5dc1-dmarc-requ...@listserv.ua.edu> wrote:
>
> All,
>
> We just learned that we have a problem with IAM (Innovation Access Method)
> the high perf replacement for VSAM.
All,
We just learned that we have a problem with IAM (Innovation Access Method) the
high perf replacement for VSAM. No idea how long it has been going on, and I
have tickets open with both BMC and IBM on this. Seems to only affect IAM
files, and exists in both z/OS V2.4, and V2.5, and multi
