Strange behavior when using !, * or _ in Unix or Windows Jobs, JCL is created incorrectly

Document ID : KB000087910
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

A problem has been fixed where the concatenation character set by script function JCL_CONCAT_CHAR remains active for subsequent jobs if the script of subsequent jobs was processed in the same worker process.

Steps to reproduce
:JCL_CONCAT_CHAR "_"
echo line1
echo juhu hallo _
echo line2

So remain JCL_CONCAT_CHAR active for all processes.

You can manually deactivate this by calling the function again at the end without parameter
:JCL_CONCAT_CHAR "_"
echo line1
echo juhu hallo _
echo line2
:JCL_CONCAT_CHAR
Cause:
Cause type:
Defect
Root Cause: Bug
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Automation Engine 11.2.2 - already available
Automation Engine 11.1.3 - already available
Additional Information:
Workaround :
1. Create an object type Job - Include in client '0' like HEADER.WINDOWS.USER.PRE (this naming convention is obliged) 2. Put the line :JCL_CONCAT_CHAR in those Includes 3. Make sure 'DISABLE_USER_HEADER' is not set in the UC_SYSTEM_SETTINGS