Does XCOM support different scripting languages for exits like xcompp? e.g. xcompp in Perl and xcompre in KSH

Products

• XCOM Data Transport
• XCOM Data Transport - Windows
• XCOM Data Transport - Linux PC
• XCOM Data Transport - z/OS

Issue/Introduction

CA XCOM Data Transport triggers scripts when any of following scripts is specified:

    XENDCMD= 
    XPRECMD= 
    XLPCMD= 
    XNOTIFYCMD= 
    XPPCMD= 

The scripts are run by the command that is specified with the xcom.gbl SHELL_CMD parameter. "/usr/ksh" is the default command in UNIX/LINUX and "cmd.exe" is the default in Windows system.

Environment

Release: ESBXCM99000-11-CA-XCOM Data Transport-Extended Support Basic
Component:

Resolution

To use a different scripting language for the exits, set SHELL_CMD= parameter in xcom.glb and recycle xcomd process.  A mixture of different types of scripts is NOT allowed because all XCOM scripts are run by SHELL_CMD command. 

Examples;

SHELL_CMD=cmd.exe for Windows batch file SHELL_CMD=wscript.exe for Windows host script that generates windowed output SHELL_CMD=cscript.exe for Windows host script that output to the command window SHELL_CMD=/usr/ksh or /usr/bash for UNIX/LINUX shell script SHELL_CMD=/usr/bin/perl for Perl script SHELL_CMD=/usr/bin/python for Python script Note: [xcomend.bat] ... if NOT /%use_echo%/ == /YES/ GOTO SKIP_ECHO_4 echo File parameters: echo fileaction: %fileaction% echo datasettype: %datasettype% echo recfm: %recfm% echo lrecl: %lrecl% echo remote_reqno: %remote_reqno% echo truncation_flag: %truncation_flag% pause :SKIP_ECHO_4 ... Wscript.exe %XCOM_HOME%\Scripts\movefile.vbs ...