Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# Running Scripts within Platform Server Started Task

Apart from scheduling scripts requests in an address space separate from the Platform Server address space, you can also schedule a script request in the Platform Server address space.

Typically, scripts are executed in an address space separate from the Platform Server address space. You submit a job, and the job executes the script. The script job can then submit file transfer requests to the Platform Server to process, and gets the response from the Platform Server. When the script terminates, the job also terminates. Besides, you can also schedule a script request in the Platform Server address space. When a request is scheduled in the Platform Server address space, the batch job that schedules the request typically terminates when the script is scheduled. The script itself is executed within the Platform Server address space.

The following example shows a sample JCL that submits a script to run in the Platform Server address space:

    //FUSJOB   JOB   ,CLASS=A,MSGCLASS=X
    //OSIUB000 EXEC PGM=OSIUB000,PARM='SERVER=FUSION'
    //STEPLIB  DD DISP=SHR,DSN=FUSION.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //SYSIN  DD *
      PROCESS,RUNSCRPT,TRANSFER,SCRIPT
      SCRIPT="MY.SCRIPT.LIB(SCRIPT)"
    //

The JCL schedules the script in MY.SCRIPT.LIB(SCRIPT1) in the Platform Server started task called FUSION. The file transfer requests also run in the FUSION started task.

You can run the script in one Platform Server started task, and the file transfers in another started task. Use the SERVER parameter to define the Platform Server started task that will run the file transfers.

In the following example, the JCL schedules a script to run in STC FUSION; while, the file transfers will run in STC FUSION1.

    //FUSJOB   JOB   ,CLASS=A,MSGCLASS=X
    //OSIUB000 EXEC PGM=OSIUB000,PARM='SERVER=FUSION'
    //STEPLIB  DD DISP=SHR,DSN=FUSION.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //SYSIN  DD *
      PROCESS,RUNSCRPT,TRANSFER,SCRIPT
      SCRIPT="MY.SCRIPT.LIB(SCRIPT1),SERVER=FUSION1"
    //

Symbolic variables can also be passed to the script to be executed. The following JCL shows how symbolic variables can be passed to a script:

    //FUSJOB   JOB   ,CLASS=A,MSGCLASS=X
    //OSIUB000 EXEC PGM=OSIUB000,PARM='SERVER=FUSION'
    //STEPLIB  DD DISP=SHR,DSN=FUSION.LOADLIB
    //SYSPRINT DD SYSOUT=*
    //SYSIN  DD *
      PROCESS,RUNSCRPT,TRANSFER,
      SCRIPT="MY.SCRIPT.LIB(SCRIPT1),SERVER=FUSION1,%LDSN=MY.DSN"
    //

In this example, the JCL creates a symbolic parameter called %LDSN, and assigns the value of `MY.DSN` to it. This information is passed to the script when the script executes.

Subtopics

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.