A batch job failed that issued a LOCK OPTION=MOVER on a database. Another job started later issuing a second LOCK OPTION=MOVER on the same database and went in a hang state as expected.
Is there a function available in Datacom to see what job issued the first LOCK OPTION=MOVER on a database, in this case the failed batch job? COMM OPTION=STATUS only displays the active job (second LOCK OPTION=MOVER)
Release : 15.1