Error: CAUAJM_E_10302 Database Change WAS NOT Successful when j2ee_parameter exceeds token limit - Autosys

Products

• Autosys Workload Automation

Issue/Introduction

Updating a POJO (Plain Old Java Object) job type in Autosys v24.1.01 fails when the j2ee_parameter attribute contains a large number of comma-separated tokens. This typically impacts jobs migrated from v12.1 where the sapdi.Payload contains extensive data. The failure manifests as a database change error, often accompanied by misleading messages regarding non-existent machines or invalid fields.

Symptoms:

• JIL returns the following error: CAUAJM_E_10302 Database Change WAS NOT Successful! CAUAJM_E_10281 ERROR for Job: #### < machine '####' does not exist >
• WCC displays: CAUAJM_E_10676 The requested server operation failed because one of the specified fields was invalid.

Environment

Product: Autosys Workload Automation 24.1.01
Operating System: All supported Operating Systems
Job Type: POJO Job Type

Cause

A hard-coded limitation in the JIL processor restricts the j2ee_parameter field to a maximum of 64 comma-separated tokens. Definitions exceeding this limit cause the parser to fail, impacting the processing of subsequent attributes.

 

Resolution

Tentative Fix: Apply APAR 99112758 to the Autosys 24.1.01 environment.

Download 99112758.tar.Z from the Broadcom Support Portal.
Follow the installation instructions in the accompanying text file.

This issue is targeted to be fixed in a future release.

Workaround: Reduce the number of comma-separated values in the j2ee_parameter field to 64 or fewer.

Additional Information

Contact Broadcom Support for assistance if the APAR is not visible in your downloads.