GLOBAL Startup Parameters

When a user submits a file transfer request on a z/OS system, by default the local user ID is sent to the remote system.

The valid values are YES or NO. The default value is NO.

This parameter applies to these platform server interfaces: batch, script, API, REXX and ISPF, and does not apply to transfers scheduled by Command Center.

This parameter applies to these platform server interfaces: batch, script, API, REXX and ISPF, and does not apply to transfers managed by Command Center. Management requests are typically ISPF or REXX transfer inquiries.

Defines the APPLID for VTAM.

You must have this parameter defined for the platform server to initialize SNA communications. If this parameter is not defined, the platform server does not attempt to start platform server SNA communications.

The valid values are applid or FUSNAPPL.

If this parameter is defined without the necessary SYSPLEX software and hardware support, a message is displayed indicating that SYSPLEX support is disabled. The valid value is an 8 character VTAM generic name.

This parameter only applies when an error is retried. When the retries are exhausted, the platform server always writes an audit record when the request is purged from the active queue.

The valid values are:

Specifies the name of a FACILITY resource used to determine if a user is authorized to administer the work queue or maintain profile information.

This parameter contains two subparameters. The first subparameter defines the conditions that U7SVC is called for initiator requests, while the second subparameter defines the conditions that U7SVC is called for responder tasks. The default value is NO,NO.

For example, CA7=YES,ALL indicates that U7SVC is called when an initiator creates a file, and when a responder creates or replaces a file.

The valid values are a 32 byte facility name or $CCC.ADMIN. This must be an RACF or ACF2 or Top Secret facility name. If the facility name is not defined, then no user has Command Center administrative capabilities.

The valid values are a 32 byte facility name or $CCC.ALTER. This must be an RACF or ACF2 or Top Secret facility name. If the facility name is not defined, then users are not authorized to alter transfers.

The valid values are a 32 byte facility name or $CCC.BROWSE. This must be a RACF or ACF2 or Top Secret facility name.

If the facility name is not defined, then all validated users are authorized to view transfers. If this facility is not defined to RACF or ACF2 or Top Secret, then all validated users are authorized to view transfers. If a validated Command Center user is not authorized for this facility, then that user can only view transfers initiated by his own user ID.

The valid values are a 32 byte facility name or $CCC.TRANSFER.This must be a RACF or ACF2 or Top Secret facility name.

If the facility name is not defined, then all validated users are authorized to initiate transfers. If this facility is not defined to RACF or ACF2 or Top Secret, then all validated users are authorized to initiate transfers.

The valid values are a member name or CONFIG. The default member name is CONFIG. For more information, see Defining Remote Systems in Configuration Library.

The CRCCHECK parameter on the Node and batch parameters will override the Global CRCCHECK settings.

The valid values are any number from 0 to 255. The default value 0 indicates that platform server does not set the MVS volume count and therefore uses the volume count defined by the DATACLASS.

This name must match a COS entry that is enabled at startup or through the ENABLE operator command.

This parameter has no default value. As such, if this parameter is not entered, no default COS can be used. Therefore, if you want to use the platform server COS facility, you must define the node DEFAULT_COSNAME or the batch COSNAME parameter.

This parameter is also known as EFFECT.

A request that ends with a network or temporary file error can be retried. This parameter is only used when the RETRY/TRY count defined by the batch interface is set to 0.

The default setting is to try a request 7 times before terminating the transfer with a permanent error. If the try count is exceeded for transfers that receive recoverable file errors, transfers are terminated regardless of the FILE_ERROR_TRY_COUNT setting.

The valid values are from 1 to 9999.

The default value 1 indicates the platform server waits for one minute between scanning the catalog for new data sets. The valid values are from 1 to 1440.

By using the default value of STC, all DNI functions are run under the ACEE of the started task.

By specifying a valid z/OS user ID, all DNI functions are run under this user ID's authorization, including scanning the catalog for requests, processing the request, and performing post processing actions on the file.

The maximum field length is 64 characters including any semicolons. As an alternative, an email distribution list defined in the organization email system can be used to specify multiple email addresses to receive this notification.

This parameter has no default value, which means that no email notification takes place when a request fails.

The maximum field length is 64 characters including any semicolons. As an alternative, an email distribution list defined in the organization's email system can be used to specify multiple email addresses to receive this notification.

This parameter has no default for this parameter, which means that no email notification takes place when a request is successful.

You can enter 1 to 58 characters in this field. In addition to the fixed information, tokens can be defined to add dynamic information to the subject.

The maximum length of the subject field after token substitution is 230 bytes.

You can enter 1 to 58 characters in this field. In addition to the fixed information, tokens can be defined to add dynamic information to the subject.

The maximum length of the subject field after token substitution is 230 bytes.

If PASSONLY operand is used, then only the password is encrypted using the encryption algorithm specified. The data is not encrypted. PASSONLY is valid only for z/OS to z/OS transfers.

NO: Uses SYSDSN ENQ to limit access to files while the files are allocated. This is the default value.

YES: Uses ENQ for the file being transferred for the life of the transfer, including Post Processing Actions.

The default value is4. You can specify as many as you want. It is good practice that you leave this parameter as default.

The default value is 15. You can specify as many as you want. It is good practice that you leave this parameter as default.

The valid values are NO or YES.The default value is NO. With this exit, you can perform an action based on the result of a file transfer. This exit can be invoked on transfer completion (successful or unsuccessful), or on temporary errors, such as network errors, and also for each transfer retry.

The valid values are NO or YES.The default value is NO. For more information, see Appendix F. User Exits.

To invoke this exit properly, the EXIT_MIGRATE_VOLUME must be set to the volume used by the storage management system. The valid values are NO or YES. The default value is NO. For more information, see Appendix F. User Exits.

The valid values are NO or YES. The default value is NO. For more information, see Appendix F. User Exits.

With this exit, you can perform an action based on the result of a file transfer. This exit is invoked when a transfer request is completed successfully or unsuccessfully and the transfer is purged from the work queue. The exit is not invoked on temporary errors, such as network errors, until the batch interface RETRY parameter is reached and the transfer is purged.

With this exit, you can check the specified transfer parameters, override parameters specified, fail the transfer or return with no changes. This exit is invoked when a transfer request is queued.

This parameter is used when a storage manager other than HSM is used in an installation. This parameter has no default value.

When detects this VOLSER, the platform server calls EXIT03 to perform the data set recall. When this parameter is specified, EXIT03 must also be specified as YES, and program FUSEX03 must be assembled and link-edited to the platform server STEPLIB.

The valid values are from 20 to 9999. When the storage manager user exit EXIT03 is invoked, a return code is sent indicating that a recall has been submitted and the platform server must wait before accessing the data set.

It is good practice that you leave this parameter to the default value of 30 days.

This parameter contains two sub-parameters. The default value is NO,NO.

The first subparameter defines whether extended resource checking is performed to check if a user is authorized to use the platform server.

The second subparameter defines whether extended resource checking is performed to check if a user is authorized to use a node within the platform server.

• ENFORCE: performs extended resource checking. If the extended security checking fails, displays a message and terminates the request with errors.
• WARN: performs extended resource checking. If the extended security checking fails, displays a message, but the request can continue. This is useful in a migration phase where you do not want to terminate transfer requests.
• NO: does not perform extended resource checking.

For more information, see Define Platform Server to the z/OS Security System.

The value defined by this parameter is a prefix to the fixed component of the extended resource check.

For more information, see Define Platform Server to the z/OS Security System.

Many file transfer requests are terminated because of retry-able file errors. The valid values are from 1 to 9999. The default value is 5.

FILE_ERROR_TRY_COUNT cannot be overridden by the batch interface. Temporary file errors are only retried up to the lower number of the value defined by FILE_ERROR_TRY_COUNT and the try count defined by the transfer or by the GLOBAL DEFAULT_TRY_COUNT.

If the FILE_ERROR_TRY_COUNT exceeds the try count, file errors are terminated when the try count is reached. The default is to try a request 5 times before terminating the transfer with a permanent error.

Defines the amount of time in seconds that a request waits after a retry-able file error and before the request is retried.

The default value is 60. The valid values are from 10 to 9999.

• Yes: Uses both methods to match an incoming request to a node definition. Both the reverse DNS lookup and the DNS lookup are used.
• No: Uses only the reverse DNS look will be used to match an incoming request to a node definition. This is the default value.

This parameter contains two sub-parameters.

The second sub-parameter defines if the file can be released automatically.

The default value is MIGRAT. When the platform server detects a migrated data set, the data set is recalled before the transfer is started.

Defines whether EBCDIC line feed (0x25) and new line (0x15) characters are checked when the transfer DELIMITER is set to LF or CRLF. ASCII line feeds (0x0A) are always checked. The default value of NO indicates that both EBCDIC and ASCII line feeds are checked. When set to YES, only ASCII line feeds are checked.

• When CRLF is set to LF, the following delimiters are checked: 0x0a, 0x15, 0x25
• When CRLF is set to CRLF, the following delimiters are checked: 0x0d0a, 0x0d15, 0x0d25

You can specify as many descriptor codes as you want. Separate descriptor codes by commas. It is good practice that you leave this parameter as the default value 4.

You can specify as many route codes as you want. Separate route codes by commas. It is good practice that you leave this parameter as the default value 15.

Defines the PDS data set name used for the SUBMIT operand.

• Specify the entire data set name in the SUBMIT operand.
• Specify just a member in the SUBMIT operand.

Platform server transfers can be managed in three ways: cross memory, SNA communication and TCP communication. Cross memory requests are always accepted. Only TCP and SNA protocols can be restricted.

The default value is 100. The valid range is from 1 to 99,999.

The default value is 70. The valid range is from 1 to 99,999.

The default value is 50. The valid range is from 1 to 99,999. This parameter is used to limit the number of concurrent scripts that can be executed in the started task. This value must be less than or equal to the MAXINITS value.

The default value is 100. The valid range is from 1 to 99,999. The default value 100 is adequate for most users.

It is good practice that you leave it as the default value. If you do not use the default value, you must define a VTAM mode entry. The valid values must be from 1 to 8 characters and must correspond to a VTAM MODEENT. The default value is #BATCH.

You can refer to the platform server sample library for an example.

The valid values are $MQ:queue _manager _name:message_queue_name.

$MQ is a literal and must be the first three characters. The message queue name must be from 1 to 55 characters. This parameter has no default value, which means that no MQ notification takes place when a request fails.

The valid values are $MQ:queue _manager _name:message_queue_name.

$MQ is literal and must be the first three characters. The message queue name must be from 1 to 55 characters. This parameter has no default value, which means that no MQ notification takes place when a request is successful.

The default value is 5000. This means MQ waits for additional data for 5 seconds before returning EOF.

The valid values are from 0 to 99999999. A value of 0 tells MQ not to wait for additional data and return EOF after reading the last record.

Use a held SYSOUT class so the log can be browsed online. The valid values are from A to Z, or 0 to 9. The default value is blank, which implies that the SYSOUT log goes to the system wide default SYSOUT class.

The valid values are from 1 to 8 characters. The default value is LOCAL.

The valid values are 1 to 60. The default value is 7.

By defining a host on the command line or in a transfer template, you can override the RSHost value configured in the config.txt.

When this parameter is not defined, if you have RSAccelerator set to Yes, the value configured for RSHost in the config.txt is used.

By defining a port number on the command line or in a transfer template, you can override the RSPort value configured in the config.txt.

The default value is 9099.When this parameter is not defined, if you have RSAccelerator set to Yes, then the value configured for RSPort in the config.txt is used.

The SAPI interface extracts data off the JES spools and transmits it to a remote system either as a file or a report.

The valid values must be 4 byte. Using this parameter, you can override the name of the subsystem that is used for all SAPI requests.

This parameter is not required because the default value is the name of the primary subsystem, which is either JES2 or JES3. If you must use a secondary subsystem, you can use this parameter to override the subsystem name.

By specifying or using the default value of STC, all SAPI functions run under the ACEE of the started task.

By specifying a valid z/OS user ID, all SAPI functions, including scanning the JES queue for output, processing the request, and performing post processing actions on output, run under this user ID's authorization.

The type of units are determined by the SPACE= parameter. The default value is 0.

The valid values are NO or an SMF record number ranging from 192 to 255.

For more information on SMF data format, see TIBCO Managed File Transfer Platform Server for z/OS User's Guide.

The valid value is a 1 to 8 character storage class name. Do not specify this parameter unless you use SMS and your storage or DASD administrator specifically advises it for incoming files.

The valid value is an 8 character JES SYSOUT destination. If this parameter is not defined, the email is sent to the default JES destination. Using this parameter, the platform server can send the data to an SMTP server running on a different system.

This name is required for the platform server email feature and it must match the name of the SMTP started task.

This class must match the LOCALCLASS parameter of the SMTP configuration data set.

Defines the name of the TCP host.

When sending an email, the platform server uses this name when setting up the SMTP MAIL FROM command. This name shows up as the sender of the email when the email is read. The valid values can be up to 40 bytes of data.

This is the default unit type for space allocations when a new data set must be created on this system to satisfy a platform server activity.

This certificate is used for the client. If you want to use the default certificate, you must specify this parameter as NULL in upper case.

If this parameter is not specified, the SSL client uses the certificate label defined by the SSL_DNLABEL parameter.

If you are using the gskkyman utility, the label name is entered when issuing the certificate request. When using the RACDCERT command, the label name is specified on the ADD request by the WITHLABEL parameter.

This certificate is used for the server. If you want to use the default certificate, you must specify this parameter as NULL in upper case.

If the SSL_CLIENT_DNLABEL parameter is not specified, the SSL client also uses this certificate defined for the server.

If you are using the gskkyman utility, the label name is entered when issuing the certificate request. When using the RACDCERT command, the label name is specified on the ADD request by the WITHLABEL parameter.

If you are using the z/OS shell bases utility gskkyman, then you must define the name of the HFS key database file created by that utility.

If you are using the RACF RACDCERT command, then you must define the name of the key ring associated with the platform server started task.

If you are not using a stash file, you can omit this parameter, or specify this parameter as NULL.

If you are using a key ring, then you must omit this parameter, or specify this parameter as NULL.

If possible, do not use the stash file. If you are using the gskkyman utility, it is good practice that you use the $SSLDB user profile instead.

The default value is the IP address of the local system. This parameter is used to define whether a request must be an SSL request.

The platform server takes the IP address of the local system and the IP address of the target system. The platform server determines the subnet of these two addresses by using the SSL_NETWORK_SUBNET parameter. The platform server then compares the two values to determine if a request is within the subnet or outside the subnet. If inside the subnet, then the request does not have to be an SSL request. If outside the subnet, then the request must be an SSL request.

This parameter is used to decide whether a request must be an SSL request.

The platform server takes the IPV6 address of the local system and the IP address of the target system, and determines the subnet of these two addresses by using the SSL_NETWORK_SUBNET_IPV6 parameter, and then compares the two values to determine if a request is within the subnet or outside the subnet.

If inside the subnet, then the request does not have to be an SSL request. If outside the subnet, then the request must be an SSL request.

This is specified in dotted decimal format. Any target system that is outside of the defined subnet requires SSL. This parameter has no default value.

You must specify a number ranging from 0 to 128 and divisible by 8. Any target system that is outside of the defined subnet requires SSL. This parameter has no default value.

The valid values are OS390 or ZOS. This parameter has no default value.

Ensure that you only use this parameter under TIBCO technical support instructions.

The valid values are either 0 or a number from 1025 to 65535. The default value 0 indicates that the platform server does not listen for incoming IPV6 SSL requests.

If a non-SSL request is received on this port, then an error message is sent to the initiator and the request is terminated.

This field must be different than the IPPORT parameter, and unique on the z/OS system.

This indicates that the platform server accepts only requests that come in through the interface defined with this specified IP address. The default value ALL means to listen to all interfaces for incoming requests.

The address specified must be in dotted decimal format and match an IP address defined for a network interface in the TCP/IP configuration.

If a non-SSL request is received on this IP port, then an error message is sent to the initiator and the request is terminated.

This field must be different than the IPPORT parameter, and unique on the z/OS system. This parameter has no default value. If this parameter is not defined, then SSL processing is disabled.

If non-SSL requests are received on this port, then an error message is sent to the initiator and the request is terminated.

This field must be different than the IPPORT parameter, and must be unique on the z/OS system. The valid values are either 0 or a number from 1025 to 65535. The default value 0 indicates that the platform server does not listen for incoming IPV6 SSL requests.

The default is to wait until TCP times out the request. The valid values are from 10 to 180.

If you leave this parameter to the default value 30, the platform server terminates a request only when TCP detects that a connection is terminated. The maximum value is 1440, which is the number of minutes in one day.

You have to set this parameter high enough to ensure that network re-transmissions and tape mounts do not cause a request to fail.

The job name can contain up to 8 characters.

The valid values are either 0 or a number from 1025 to 65535. The default value is 46464. If 0 is specified, then the platform server does not listen for incoming requests.

This parameter is also used as the default IP port on a TCP connect request unless the IPPORT on the NODE or PROCESS statements is specified.

The valid values are either 0 or a number from 1025 to 65535. The default value 0 indicates that the platform server does not listen for incoming IPv6 requests.

The default value ALL means to listen to all TCP network interfaces. If you want to listen to only a single network interface, specify the dotted decimal address of the network interface, so the platform server only listen to that network interface for incoming requests.

If FIPS140 is specified, only FIPS approved ciphers are used.

Multiple TLSCIPHERS parameters can be defined. One TLS Cipher can be defined for each TLSCIPHERS parameter. The text after the 4 alphanumeric digits is used for documentation only and is ignored.

Example: TLSENABLEDPROTOCOLS=TLSV1_1,TLSV1_2

If this parameter is not entered, the default is ALL.

You can initiate transfers in three ways: cross memory, SNA communication and TCP communication. Cross memory requests are always accepted. Only TCP and SNA protocols can be restricted.

If the parameter is not defined, SNMP traps are not sent. If this parameter is defined, SNMP traps are sent to the address defined by this parameter.

On most SNMP computers, the default port number is 162.

• YES: Allow MFT to delete unexpired files when DISP=DNEW
• NO: Do not allow MFT to delete unexpired files when DISP=DNEW. NO is the default value.

• YES: Allows MFT to update unexpired files.
• NO: Does not allow MFT to update unexpired files. NO is the default value.

This is the unit type for incoming disk data sets. You can adjust this to your installation requirements.

Do not leave this as the default value. You can adjust it to meet your installation requirements. If this parameter is omitted, the volume is assigned from the pool of devices for the unit type defined by the UNIT parameter.