Open topic with navigation

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

# Suggestions for DNI Dataset Names

For best results, you can create a new high-level qualifier (HLQ) and use it solely for the Platform Server DNI. Although the Platform Server can utilize high-level qualifiers that are shared with other systems, there exists the potential for files to inadvertently be created with a name that matches the DNI DSN qualifier.

For example, if you want to send the ACCT.CUSTDATA.CUST1 and ACCT.CUSTDATA.CUST2 files to remote nodes, you can specify `DSN=ACCT.CUSTDATA.CUST*`; if another user creates the ACCT.CUSTDATA.CUSTLIST file, this qualifier matches the DSN qualifier specified and a transfer will be queued as a result.

This example shows how a problem might occur. Wildcard parameter *, %, and ** can be combined to form complicated templates, which must be understood by all users creating datasets. This is why it is a good idea to reserve an HLQ for DNI.

It is a good practice to use a qualifier that includes the words GOOD and FAIL (or a similar representation) just after the HLQ. In such cases, it is easy for a user to see whether any requests failed by performing a dataset scan through ISPF 3.4 or LISTCAT on HLQ.FAIL.

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