If the IOAT00S message appears sporadically and if the number of messages is low, this can be considered as an "accident".
This may be linked to problems on the CONTROL-M monitor side.
Sample already seen events:
In a CONTROL-M monitors messages like the following were displayed:
CTM916W PROGRAM CTWDET WAITING FOR CTM.CKPT
and in parallel in CTMAS the following messages appeared:
IOAT00S FAILURE TO LOCK TRACE WS WORK AREA for CTMAS.
If those IOAT00S messages occur frequently at a high rate then.
- SET a SLIP trap to dump the CTMAS, Sample:
SLIP SET,ENABLE,ID=<slipID>,ACTION=SVCD,J=<jobname>,MSGID=IOAT00S,SDATA=(CSA,GRSQ,SUM,RGN,TRT),END
- Open an issue to BMC Support and provide the following data:
1. The SLIP DUMP - must be sent in compressed format. Use AMATERSE utility with PARM=SPACK
2. The full CTMAS sysout
3. The full CONTROL-M monitor sysout
4. The IOA LOG in compressd format. Use AMATERSE utility with PARM=SPACK
5. The z/OS and IOA level using a screenshot of the IOA ONLINE INFO command