AAI Mainframe STC Fails to Start After z/OS 3.1 Upgrade

Products

• Automation Analytics & Intelligence

Issue/Introduction

After upgrading the mainframe operating system from z/OS 2.5 to z/OS 3.1, the CA 7 Server for AAI Started Task (STC) fails during the initialization phase. The following error messages are observed in the STDOUT/STDERR logs:

AI7.SXP3S: Call to AISZSFTP failed RC=4 - Check STDERR for messagesAI7.DV03S: Verification of SFTP Data Delivery failed - Check messagesAI7.TM07I: CA 7 Server for AAI FAILED during Configuration at line 326AI7.TM08I: CA 7 Server for AAI Terminated

The failure log for AISZSFTP indicates that the SFTP invocation was verified but the exit status could not be parsed:

Environment

Product: Automation Analytics & Intelligence (AAI)
Component: Mainframe Data Provider (MDP) for CA 7
Version: R2.0 Build 230207 and earlier
Environment: z/OS 3.1

Cause

The issue is caused by a change in the default output format of IBM OpenSSH in z/OS 3.1.

1. SFTP Log Prefix: In z/OS 3.1, verbose SFTP output now includes a debug1: prefix (and potentially a timestamp prefix) on status lines.
2. Parser Failure: The MDP R2.0 REXX code uses a fixed-position parser that expects the string "Exit status" to appear at the very beginning of the line. Because the new prefixes shift the position of this text, the parser fails to recognize the successful connection, resulting in a Return Code 4 and STC termination mainframe AAI STC will not start under zOS 3.1.

Additionally, even if the startup is bypassed, R2.0 contains a separate defect (DE181377) that causes an "Unexpected PROCEDURE error" after the first processing cycle completes on z/OS 3.1.

Resolution

The only viable resolution is to upgrade the Mainframe Data Provider to version 24.2.2 or later. This version includes a modernized parser that uses the POS function to locate status messages regardless of prefixes, ensuring compatibility with z/OS 3.1 mainframe AAI STC will not start under zOS 3.1.

Upgrade Summary

1. Backup: Perform a backup of your CAIZISPF, CAIZLOAD, and CUSTLIB datasets, as well as the USS execution path.
2. Installation: Run the AISZ_Installer from the 24.2.2 package. When prompted, ensure you do not overwrite the existing CUSTLIB to preserve your site-specific JCL.
3. Instance Migration:
   • Open the Instance Management System (IMS) using AI7CPRIM.
   • Select Update Instance Definition (U) for your instance and press Enter to migrate internal settings.
   • Go to Configure Instance (C) > Option 3 and press Enter then PF3 to force-apply the new configuration parameters.
4. Verification: Start the STC and confirm the version in the log: ================== CA 7 Server for AAI R24.2.2 Build 260120 =================== mainframe AAI STC will not start un

Additional Information

There is no configuration-based workaround (such as environment variables) for the R2.0 version on z/OS 3.1. The upgrade is mandatory for operational stability on the new OS version.