Open topic with navigation

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

# Dataset Name Initiation (DNI)

TIBCO MFT Platform Server for z/OS provides the DNI interface from which you can initiate data transfer requests by simply creating a dataset. You do not have to issue any calls to Platform Server programs or APIs, and you do not have to run any batch jobs or submit any JCL. To use the DNI interface, you only have to configure the DNI interface when installing the Platform Server. The configuration can also be easily updated at anytime.

The following example shows how the Platform Server DNI works:

The Platform Server administrator sets up the following configuration in a file referenced by the DNICFG DD statement in the Platform Server startup JCL:

    REQUEST=SEND
    DSN=TESTDNI.FILE1
    REMOTE_FILE=TESTDNI.NEW.FILENAME
    NODE=NYNODE
    FAIL_ACTION=RENAME
    FAIL_NEWDSN=TESTDNI.FAIL.FILE1
    GOOD_ACTION=RENAME
    GOOD_NEWDSN=TESTDNI.GOOD.FILE1

The Platform Server scans the z/OS catalog for a dataset called TESTDNI.FILE1. When this dataset is found, the Platform Server waits until it is no longer allocated to a job. The Platform Server then initiates a SEND transfer to the NYNODE node. When the transfer is completed, the Platform Server checks the status of the transfer request. If the transfer is successful, the Platform Server renames the dataset to TESTDNI.GOOD.FILE1. If the transfer is unsuccessful, the Platform Server renames the dataset to TESTDNI.FAIL.FILE1.

This is a simplified example, because the Platform Server has a powerful set of substitutable parameters and wildcards that can be used to reduce the amount of configuration parameters that must be created.

Subtopics

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