Jobs fail with "Index 2 out of bounds" on Java-based z/OS (MVS) Agent v24.4.x.
search cancel

Jobs fail with "Index 2 out of bounds" on Java-based z/OS (MVS) Agent v24.4.x.

book

Article ID: 434765

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine Automic SaaS

Issue/Introduction

After installing or upgrading to the Java-based z/OS (MVS) Agent version 24.4.x, jobs fail to execute. While the Agent starts successfully and connects to the Automation Engine (AE), any standard z/OS jobs assigned to run on it fail immediately.

The same jobs execute successfully on previous versions (e.g., v21) of the classic MVS agent without any changes.

The Automation Engine reports the following job status and error code:

  • error code 62 (Loscon).

The Agent logs display the following exceptions:

  • java.lang.IndexOutOfBoundsException: "Index 2 out of bounds for length 2" at jdk.internal.util.Preconditions.outOfBounds():64.

  • Repeated java.util.NoSuchElementException: "No value present" exceptions during Agent startup.

  • java.nio.file.NoSuchFileException referring to job reports (e.g., ABC.UC4.JOBREP.TXT).

Environment

 

  • Product: CA Automic Workload Automation - Automation Engine

  • Component: Java-based z/OS (MVS) Agent

  • Versions Affected: 24.4.2, 24.4.3

 

Cause

This issue occurs when custom z/OS HEADER.MVS and TRAILER.MVS include objects are modified and lack the required separator strings.

The Java-based MVS agent uses these specific separators to split the JCL content into three distinct parts. If these separators are missing from the custom scripts, the JCL generator fails to correctly assemble the final JCL (including the job card and the job body), which triggers the IndexOutOfBoundsException.

This behavior has been identified as a defect and is tracked under Defect ID: DE181288.

Resolution

Update to a fixed version listed below or a newer version if available.
 
Component: Agent MVS
 
Automic Automation Engine 24.4.4 - Available
 

Public Title:
Jobs fail to execute on Java-based z/OS Agent

Public Description:
An issue has been resolved where job execution on the Java-based z/OS agent failed when the HEADER.MVS and TRAILER.MVS include objects were modified.

Workaround: If an immediate upgrade is not possible, you can bypass the issue by ensuring the required separator strings are present in your custom scripts.

 

  1. Review your custom HEADER.MVS script and ensure a separator line similar to the following is present at the very end:

    • //* <--- END HEADER ---> 

  2. Review your custom TRAILER.MVS script and ensure a separator line similar to the following is present at the very beginning:

    • //* <--- BEGIN_TRAILER --->

       

       

Additional Information

Article title: How to register to Broadcom Software Product updates and Critical Alerts

https://knowledge.broadcom.com/external/article?articleId=133819

Powered by Wolken Software