A ZOS Job where the JCL is NOT on the Automic job but on the ZOS Server cuts the line
search cancel

A ZOS Job where the JCL is NOT on the Automic job but on the ZOS Server cuts the line

book

Article ID: 244660

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The SYSIN looks like this from the provided input (SYSIN) of the job:

Aus dem mitgelieferten Input vom Job:
L GHU DS0089 (SCHL = 2035101)
L ISRT DS0090
L DATA ....AU 4029121 050.......J...J *
    CONT

The DATA Segment which should be added start with 00 00 00 00 C1 E4 40 F4 F0… and so on
at the asterisk '*' at point 72 the PGM shows that the data goes on at the CONT line

This is the output (SYSOUT) that comes out

L GHU DS0089 (SCHL = 2035101)
L ISRT DS0090
L DATA                                      \* this line has been cut at the x'00'*\
    CONT

We can see in the SYSOUT that the DATA Segment was truncated.
It looks like the execution in AE changes the output of the handled file
Seems that the x'00' is considered as a special character and the line is cut off there. Possibly it is interpreted by Agent/AE as EOL.

IMPORTANT: If the same JCL is executed from IMS outside of AE the execution works fine with no line truncation.

Environment

Release : 12.3.x and 21.x

Component : Agent MVS

Cause

The problem concerns JCLs triggered by One Automation where data is injected from SYSIN with internal x'00' hexadecimal characters and returned about SYSOUT.

Resolution

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

Fix version:
Component(s): Agent MVS
Automation.Engine 12.3.9 - Available
Automation.Engine 21.0.4 - Available

Additional Information

Problem description: SYSIN data lines cut at 0x00 hex characters

Solution details: A problem has been solved, where SYSIN data lines were cut at 0x00 hex characters.