The CA7 Server for AAI (Mainframe Data Provider) task terminates with Return Code 12 and AI7.XXXXX when event recovery requires access to history log GDGs stored on tape. This occurs during the main event data delivery cycle when live logs are older than the last checkpoint.
Error message:
AI7.EV-INFO: ALLOC on LOG History GDG failed. dyncmd=ALLOC FI(HLOG) DA('####.LOG.HIST.G####V00') SHR MOUNT dynrc=34603008AI7.XXXX: Call to AIS7XEVT for event data file generation failed. RC=12 Server will terminate.AI7.XXXX: CA 7 Server for AAI has failed at line 838 - Review LOG messages
Product: Automation Analytics & Intelligence version 24.x, AAI CA7 version 24.x
The User ID assigned to the AAI Started Task lacks a TSO segment or the required MOUNT authority in the security product. Without a TSO segment, the system cannot perform allocations that require tape mounts or specific TSO-environment resources.
1. Get the system log around the failure window
Gather the SYSLOG/OPERLOG (or SDSF LOG) on system SYTX / LPAR SYCX. We need the specific allocation message (usually IEF, IGD, or IKJ56) tied to CAI.CA7.TSTPLX12.LOG.HIST.XXXXX — it will name the exact reason (busy/in-use, volume not mounted, catalog issue, etc.) that the dynrc=34603008 only points to generically.
2. Identify what else was touching that GDG
What other jobs/tasks reference CAI.CA7.TSTPLX12.LOG.HIST?
3. Check for recurrence / pattern
Has this happened before with AI7SAAIX or other AAI server instances, and if so, was it always around the same time of day or tied to a specific batch window (e.g., nightly backups)?"