You would use an XCOM PreProcessing or Post Processing script when you want to have some work performed before a transfer starts or at the conclusion of a transfer. What kind of work is performed is determined in part by which script you choose to execute, and by what instructions you code into that script. How a script is kicked off is determined by two things:
Whether the script is enabled in your XCOM.GLB file, whether a transfer event that invokes the script has occurred and in case of the XCOMPRE script the setting for XCOMPRE_LOCAL in xcom.glb.
Script | Controls... | Invoked | Default XCOM.GLB setting |
XCOMPP | user-defined post-transfer processing | Upon successful incoming transfer completion | XPPCMD=%XCOM_HOME%\xcompp.bat |
XCOMEND | user-defined post-transfer processing | Upon completion of any transfer, whether successful or not | XENDCMD=%XCOM_HOME%\xcomend.bat |
XCOMLP | print spooling | After a print job (report) is received | XLPCMD=%XCOM_HOME%\xcomlp.bat |
XCOMNTFY | notification | When a transfer completes. | XNOTIFYCMD=%XCOM_HOME%\xcomntfy.bat |
XCOMPRE | user-defined pre-allocation processing | Before a transfer begins, subject to global parameter XCOMPRE_LOCAL* | XPRECMD=%XCOM_HOME%\xcompre.bat |
Release: CA-XCOM Data Transport
Component:
Details for customizing the script are in the sample script itself. For more information refer to sections "How to Use the Pre-allocation Script" and "How to Use CA XCOM Data Transport Scripts" in our online documentation.
See "Create the CA XCOM Data Transport Batch Interactive Group" in our online documentation.