Jerry:  We had similar problems with both level12 and 13, but it was
much worse with level 13.  Turned out to be a TCPIP problem which caused
both ADMIN and BACKUP schedules to wait, since they both use the same
schedule manager in ADSM, who, it turns out, is waiting on TCPIP.
Unless the problem was cleared by either restarting TCPIP or ADSM, the
window would expire and the command/backup would be missed.  The APAR
is PQ06771 and was still open last time I checked.  Level 2 will send
you a temporary fix though, if asked.  The problem went away here after
applying that.
Sam Sheppard
San Diego Data Processing Corp.
shs AT sddpc.sannet DOT gov
-----------------------------------------------------------------------------
>
>
>I had a strange weekend - what was it Jerry Garcia used to say "What a
>strange journey this has been"?
>
>We began having TCP/IP troubles on Friday - we could establish sessions, but
>data transfers would hang after a few bytes were sent - they would timeout
>either as a communications timeout, or an idle wait, depending on when TCP
>decided to stop.  This didn't clear until 2:00 AM, when they bounced TCP/IP,
>but operations didn't recycle ADSM, so we were out of the water until mid
>morning Saturday when I happened to check it.
>
>Nothing much unusual there, but here is what had me confused.  Sometime on
>Friday, all of our Admin schedules stop executing - no indication as to why.
>Around noon on Friday, I had operations recycle ADSM, which went
>successfully.  When it came up, an admin schedule that was in the middle of
>its window kicked off, executed, and reported back a successful completion.
>I thought the problem was solved, but later Friday, I checked again, and the
>admin scheduler was out again.
>
>I cannot think of any relationship between  TCP/IP communications, and admin
>schedules.  Does anyone have any ideas?
>
>When I discovered the problem on Saturday, I again had them restart ADSM, and
>again it seemed to take off - reconnected to TCP/IP, and admin schedules
>seemed to be working.  Later that evening, though, not only had I lost
>communications again, but console traffic seemed to be gone as well.  Since
>we had an IPL scheduled for 7:00 AM Sunday, we decided to let it go, and
>since the IPL, all seems to be fine.  We did have a bad tape - actually 2
>tapes with the same TSN, but that didn't seem to contribute to this problem.
>This was all under release 12 of the MVS server - We are now under level 13,
>as it had been one of the planned upgrades on the IPL on Sunday morning.
>
>Anyone else see strange things like this?