Open topic with navigation

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

# SAPI (SYSOUT API)

With the SAPI interface, the Platform Server supports extracting data from a JES Spool and sending this data to a remote node. One of the more useful features of the Platform Server is the ability of sending the data to a remote system as a file rather than as a report. You can specify substitutable parameters to make the remote file unique.

Note: For more specific information on the SAPI parameters, review the parameters defined in the TIBCO Managed File Transfer Platform Server for z/OS Installation and Operation Guide.

When the Platform Server SAPI interface is enabled, the SAPI interface scans the NODE definition for SAPI selection criteria. If no selection criteria are defined, the next node is checked until all of the nodes are scanned. When a NODE definition is found with SAPI selection criteria defined, the Platform Server calls JES to see whether any output for the selection criteria exists. If output exists, the Platform Server queues a request to that node. Then, the request is processed and the data is sent to the remote system. When the request is completed, the spool data disposition depends on the NODE SAPI_DISP parameter.

Note: Data is not staged in the Platform Server SAPI interface. Data is read directly from the JES spool. The data is multi-threaded so that SAPI requests can be active to multiple nodes at the same time. However, for a single node, only one SAPI request can be active at a time, while other non-SAPI requests can be active with the same node at the same time.
Subtopics

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