Clarification on Hiper fix SO10450 (OPS 13.5) and SO10458 (OPS 13.0)

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

We would like clarification on SO10450 and SO10458:

1) Is the only pre-requisite for the problem to happen that multiple events to run simultaneously?

2) What kind of events (AOF rules)?

3) Which address space held the latch (OPSMAIN)?

4) The SQL tables in question are OPS/MVS SQL tables, right?

Environment

Release : 13.5 and 13.0

Component : OPS/MVS

Cause

It is possible for a task to go thru EOT when multiple events were in flight simultaneously, resulting in process block cleanup that may miss the fact that one of the processes held a latch.

Once the latch is left on it will be held until the address space terminates. If it is a latch used to protect SQL tables, then depending upon automation present, this may cause all automation to cease once all process blocks are held.

Resolution

This hiper fix resolves a problem when a task is going thru end of task, while multiple events are still flowing for that task, which may then cause a latch to be missed and hence left on. The exposure is there when SQL is used heavily in AOF rule processing. It may occur in whichever address space had multiple events occur in a task when EOT occurred. The SQL tables in question are OPS/MVS SQL tables.

Additional Information

The system may grind to a halt, with no real work being dispatched.

The impact will be that an IPL may need to be performed.