Error: U00063016 - File does not exist when transferring GDG base name on z/OS Java Agent

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When migrating from legacy C-based z/OS agents to Java-based agents (v21/v24), file transfers (JOBF) using Generation Data Group (GDG) base names fail. This issue occurs because the Java agent does not implicitly resolve the base name to the current generation.

Symptoms: The file transfer fails with the following error in the job report: U00063016 FT '####': The file 'DATASET.NAME.BASE' does not exist.

Environment

Automic Automation Engine 21.x and 24.x

z/OS Java Agent (Agent MVS)

Generation Data Groups (GDG)

Cause

The Java-based z/OS agent strictly follows IBM dataset naming conventions. Unlike the legacy agent, it does not support using the GDG base name to represent all generations or the current generation implicitly. A specific generation or wildcard must be provided.

Workaround solution

Use explicit generation notation in the source filename:

1. Open the File Transfer (JOBF) object.
2. Update the source filename to include the desired generation. Use (0) for the current generation: DATASET.NAME.BASE(0)

Resolution

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): 

Automation.Engine - Agent MVS

 

Automation.Engine 24.4.4