Defining the CONFIG Parameter

You can define the CONFIG parameter in the PARM field in a JCL statement to allow Platform Servers to submit requests to a Platform Server for z/OS. This is a usage of the PARM override facility.

Required Parameter

CONFIG: Defines the name of the CONFIG entry within the FUSCFG configuration entry. It can contain up to 24 characters, and it must match the CONFIG parameter within the FUSCFG member of the FUSCFG DD statement.

The FUSCFG CONFIG entry can be defined to communicate through TCP, SNA, or Cross Memory Services. The advantage of using these methods of communication is that all configuration data for communicating to the Platform Server started task is controlled within a single file. If the connectivity information for a started task changes, the FUSCFG entry can be changed so that individual batch jobs do not have to be changed.

Note: The FUSCFG file used by the Batch interface is the same as the FUSCFG information used by the ISPF and REXX interfaces. The same file can be used by the Batch interface as well as by the ISPF and REXX interfaces. For more information on the FUSCFG file, see TIBCO® Managed File Transfer Platform Server for z/OS Installation and Operation Guide.

Example of Defining the CONFIG Parameter

//STEP0001 EXEC PGM=OSIUB000,
//PARM='CONFIG=CONFIGENTRYNAME'