Control-M for z/OS Application Server, CTMAS, issues messages IOAT00S FAILURE TO LOCK TRACE WS WORK  AREA.

Sample messages:

IOAT00S FAILURE TO LOCK TRACE WS WORK AREA

00:00:00 ---- IAT6853 THE CURRENT DATE IS MONDAY, 07 APR 2014 ----
00:00:00 ECAB42I ***** NEW DAY STARTED: 07/04/2014 *****
00:00:05 IOAL03I 042 kb OF IDL DATA SUCCESSFULLY SNAPPED AT(39D8C020-00:00:00-
06:00:19 CTM916W PROGRAM CTWDET WAITING FOR CTM.CKPT 10 SEC
06:01:16 CTWH67I DOWNLOAD PROCESS WILL TAKE PLACE SINCE ACTIVE JOBS FILE WAS FORMATTED
06:01:16 CTWJ51I LOGICAL CONNECTION SUSPENDED WHILE THE ACTIVE JOBS FILE IS BEING FORMATTED
06:01:23 CTWJ52I LOGICAL CONNECTION RESUMED
06:01:31 CTWH00I DOWNLOAD OF ACTIVE DATABASE STARTED
06:01:31 CTWH08I DOWNLOAD OF CONTROL-M ACTIVE JOBS FILE - STARTED
06:01:32 CTWH08I DOWNLOAD OF CONTROL-M ACTIVE JOBS FILE - ENDED
06:01:32 CTWH08I DOWNLOAD OF RES. FILE AND IOA COND. FILE STARTED
06:01:32 CTWH08I DOWNLOAD OF RES. FILE AND IOA COND. FILE ENDED
06:01:36 CTWH01I DOWNLOAD OF ACTIVE DATABASE ENDED SUCCESSFULLY
06:01:36 CTWH06I WORKSTATION DATABASE IS SYNCHRONIZED WITH THE MAINFRAME DATABASE
10:00:23 CTM916W PROGRAM CTWDET WAITING FOR CTM.CKPT 10 SEC
11:18:07 CTM916W PROGRAM CTWDET WAITING FOR CTM.CKPT 10 SEC
11:18:41 IOAT00S FAILURE TO LOCK TRACE WS WORK AREA
11:18:52 IOAT00S FAILURE TO LOCK TRACE WS WORK AREA

IOAT00S FAILURE TO LOCK WS TRACE WORK AREA
Explanation: The tracing facility failed to lock the internal (WS) trace work area.
The tracing request is ignored. Processing continues.
User response: Contact BMC Software Customer Support.

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