Follow-up processing operates in BS2000 under the user’s own TSN. Temporary files and temporary job variables can only be accessed for follow-up processing if they belong to this TSN. Access to temporary files of job variables of the TSN under which the actual FT request was carried out is not possible. It is however possible to access permanent files and job variables.
openFT generates a file in BS2000 for the execution of follow-up processing with the name $userid.S.FT-BS2.instance name.transfer-id.JOB, which is automatically deleted after the ENTER-JOB. This file is created by openFT with the catalog attribute DESTROY=YES and started with the following operands:
ERASE=YES,FLUSH=NO,RERUN=NO
If a job class JBCLJOB is set for the user whose ID is being used for the follow-up processing, the follow-up processing is executed under this job class. Otherwise the user’s default job class will be used.
*DELETE as a special form of follow-up processing
This character string *DELETE can be specified as follows:
as remote follow-up processing for synchronous and asynchronous receive requests,
as local follow-up processing for asynchronous send requests or with FTP partners.
*DELETE causes openFT itself to delete the sent file in the sending system after the termination of the FT request without it being necessary to start a batch job. However, as in the case of "genuine" follow-up processing that consists of system commands, *DELETE does not form part of the job scope. This means there is no response message indicating whether or not the file has been successfully deleted. “Genuine” follow-up processing can be additionally specified via an FTAC profile.