AutoSys Agent Upgrade Fails on IBM i (iSeries) due to Trinity Guard Exit Point Configuration or Disk Space Errors

Products

• Workload Automation Agent

Issue/Introduction

When attempting to upgrade or install the AutoSys Workload Automation Agent (version 24.1 or similar) on IBM i LPARs, the process fails. The failure may manifest as a generic "unexpected exception" or an incorrect "insufficient disk space" error, even when the system has ample free storage.

Symptoms

• Installer Denial: The installation log or terminal shows: Agent Install Library: Library check failed. Reason: Unexpected exception: Exit program denied request.
• False Disk Space Errors: The upgrade fails reporting No space left on device or similar disk space warnings in the /autosys directory.
• Binary Deletion: The cybAgent.bin file may be removed from the installation directory after a failed upgrade attempt, preventing the agent from being restarted.
• Communication Failure: After a successful-looking install, the agent fails to connect if the wrong port was selected or if encryption keys were not restored.

Environment

• Operating System: IBM i (iSeries / AS400)
• Product: AutoSys Workload Automation Agent
• Security Software: Trinity Guard (or similar exit point monitoring tools)

Cause

The primary cause is environmental security software (specifically Trinity Guard) monitoring IBM i exit points.

The software identifies the installer's internal communications from the localhost (127.0.0.1) as unauthorized and denies the request. Additionally, the upgrade process may fail to properly overwrite existing binaries if permissions or locks are held by security exit programs.

Resolution

Step 1: Adjust Trinity Guard Exit Point Rules

To allow the installer to communicate with the system, configure a rule to allow the AutoSys user profile:

1. Access the Trinity Guard menu (TGMENU).
2. Navigate to Option #2 (Intrusion Detection/Exit Points) -> Option #1 (Configuration).
3. In the Exit Point Configuration:
   • Set Alert Status to *NONE.
   • Set Collector Status to *FAIL.
4. Under Incoming Transactions, create or modify a rule for the AUTOSYS user:
   • Source IP: 127.0.0.1
   • Action: *ALL
   • Description: Allow localhost transactions for Agent installation/upgrade.

Step 2: Address False Disk Space/Upgrade Errors

If the in-place upgrade continues to fail:

1. Backup Configuration: Save the agentparm.txt and cryptkey.txt files.
2. Clean Install: Instead of an upgrade, stop the agent and delete the contents of the /autosys library.
3. Run Installer: Execute the setup.jar from the i5_ppc_32 directory of the Agent ISO.
4. Restore Keys: Copy the backed-up cryptkey.txt into the new installation folder to restore connectivity with the AutoSys Manager.

Step 3: Verification

1. Ensure the agent is configured to listen on the correct port (default is often 7520).
2. Verify the agent starts successfully by checking the logs or using the ./cybAgent -vv command in a PASE terminal.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.