In the case of preprocessing only the command’s SYSLST or %TEMPFILE output is transferred. The SYSLST or %TEMPFILE output is temporarily stored in a file prefixed by S.PP. 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 automatically deleted as soon as transfer and/or preprocessing and postprocessing are completed.
If the FT subsystem is closed down before a file can be deleted, then the information concerning the file for deletion is lost and automatic deletion is no longer possible.
If pre- or postprocessing are running in BS2000, the commands will be executed as a batch job:
During preprocessing, data output to SYSLST or the %TEMPFILE variable must occur. If you specify %TEMPFILE then the file can have a file format other than SAM-V. The batch job uses this output to create a help file, which is then transferred to the partner system. Because the file attributes of the generated file are not known when the request is accepted, they must either be passed as request parameters (RECORD-SIZE, RECORD-FORMAT) or the transfer must be performed transparently if the systems are homogeneous.
During postprocessing, the data is read from SYSDTA by default. In this case, it must have a format which can be processed by SYSDTA (SAM-V or ISAM-V). It is also possible, however, to explicitly address the transferred file using the variable %TEMPFILE. For this, the file can be of a different file format than SAM-V or ISAM-V. openFT makes the transferred data available to the first command and waits until processing is complete ("postprocessing").
Each individual BS2000 command must be preceded by a forward slash ’/‘.
Preprocessing and postprocessing in the BS2000 system runs under a separate TSN. If an ENTER-JOB command is encountered during preprocessing, this command is subject to the usual definitions for the user ID that initiated preprocessing. openFT generates a JOB file with the name $userid.S.VV.FT.unique-string.JOB which is automatically deleted after the ENTER-JOB. If a job class JBCLJOB has been declared for the user under whose ID the pre/postprocessing is being performed, then pre/postprocessing is performed under this job class. Otherwise the user’s default job class is used.
If the %JOBCLASS variable is used, preprocessing and postprocessing can be started under a selected job class by inserting the following command in the pre/postprocessing operation:
/REMARK %JOBCLASS=<jobclass>
When choosing the job class, you should note that pre/postprocessing operations should be started as quickly as possible as otherwise resources (transport connections, server tasks) may block and, in the worst scenario, may be aborted after 15 minutes.