Codepage issue on the RA REST Agent with MFES Agent Solution 2.1 (Microfocus Interface ESMAC)

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The special character “§” in the JCL was interpreted as “§” in the microfocus Interface ESMAC .

Original JCL :

//FTP01 EXEC GETPARS$,
// PARM='§,Q2=ERW,F1=_AUSTNEU,DE=TXT,Q3=&UMGP',
// MEMBER=RNVPFTP&UK,
// TEMPDSN='&&FTP01'
//FTP02 EXEC EDF$ABS
//WAIT.SYSUTIN DD DISP=(SHR,DELETE,DELETE),DSN=&&FTP01

JCL in UC4

:
//SETUMG INCLUDE MEMBER=SETDFSL
//FTP01 EXEC GETPARS$,
// PARM='§,Q2=ERW,F1=_AUSTNEU,DE=TXT,Q3=&&UMGP',
// MEMBER=RMVPDTP&&UK,
// TEMPDSN='&&&&FTP01'
//FTP02 EXEC EDF$ABS

In the UC4 export of the JCL Job, we find the "§" character again.  

But in the filesystem, following content can be found the directory:

/var/abshost/tmp/uc4 

//******************************************************************
//SETUMG   INCLUDE MEMBER=SETDFSL
//FTP01    EXEC  GETPARS$,
//            PARM='§,Q2=ERW,F1=_AUSTNEU,DE=TXT,Q3=&UMGP',
//            MEMBER=RMVPDTP&UK,
//            TEMPDSN='&&FTP01'
//FTP02    EXEC  EDF$ABS
//WAIT.SYSUTIN      DD DISP=(SHR,DELETE,DELETE),DSN=&&FTP01
//******************************************************************
//*
//* TRANSFER SPäTERE BEGINNE AUS POLICIERUNG

Special characters are not decoded as they should be. The modification makes the execution of the script running wrong.

Environment

RA Core version 12.1

MFES solution : 2.1

Cause

This is due to the use of standard codepage. This is a parameter issue.

Resolution

In Service Manager edit the starting commande of the MFES RA agent and force the 8-bit codepage 1252 by adding the following parameter:

-Dfile.encoding=Cp1252