Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Preprocessing and postprocessing

&pagelevel(3)&pagelevel

You should construct command sequences using the TSO WHEN command, e.g.:

command1;WHEN SYSRC(< 12) command12;WHEN SYSRC(< 12) command13;...

In the case of preprocessing only the command’s SYSPRINT or %TEMPFILE output is transferred. The SYSPRINT or %TEMPFILE output is temporarily stored in a file which is deleted following transfer. This file is created with a unique file name in order to prevent conflicts between file processing operations that are running in parallel. The ID under which preprocessing is running must possess sufficient space for the creation of the temporary file as otherwise preprocessing will be aborted.

The temporary files that are created for pre/postprocessing are all of type "Variable Blocksize (VB)", and are automatically deleted as soon as transfer and/or preprocessing and postprocessing are completed.

Preprocessing and postprocessing jobs generated by openFT

If you specify a TSO command (or a sequence of TSO commands) for preprocessing or postprocessing, openFT generates a job that is responsible for processing. The FT administrator can predefine the basic structure of the job. This is done in the elements TSOVVJOB, TSONVJOB and TSOVFJOB of the openFT parameter library. For more information see the manual "openFT (z/OS) - Installation and Operation".

If preprocessing or postprocessing are performed in z/OS, then the commands are started as a TSO job:

  • If you specify a preprocessing command on send, then the specified commands are initially started as a TSO job. The data is output via SYSPRINT or %TEMPFILE to a temporary file that is passed to the partner (“preprocessing”). If the data is passed with SYSPRINT, you must explicitly specify OUTPUT=*STDOUT to prevent the output from being written to job logging (if SYSTSPRT DD SYSOUT=* was previously specified in the batch job) and instead write it to the specified file (or stdout, see example).

    Examples

    1. NSTATUS in z/OS as preprocessing for a request submitted in the Unix system

      ncopy part!"|nstatus output=*STDOUT" file transadm

    2. LISTCAT in z/OS as preprocessing for a request submitted in the Unix system

      ncopy part!"|listcat ofile(sysprint)" file transadm

  • If you specify a postprocessing command on receive, openFT supplies the first command with the transferred data via the %TEMPFILE variable or via SYSUT1 and waits until processing has been concluded (“postprocessing”).