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.

Valid values are YES and 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 managed by Command Center. Management requests are typically ISPF or REXX transfer inquiries.

Valid values are:

• YES: TCP and SNA transfer requests are accepted. This is the default value.
• NO: TCP and SNA transfer requests are not accepted. Only requests initiated on the same server and scheduled through cross memory are accepted.
• NODE: The node ALLOW_MANAGE_REQUESTS parameter defines whether TCP or SNA requests are accepted. If a node definition is not defined for an incoming transfer management request, the request is denied.

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

Valid values are:

• YES: TCP and SNA transfer requests are accepted. This is the default value.
• NO: TCP and SNA transfer requests are not accepted. Only requests initiated on the same server and scheduled through cross memory are accepted.
• NODE: The node ALLOW_TRANSFER_REQUESTS parameter defines whether TCP or SNA requests are accepted. If a node definition is not defined for an incoming transfer schedule request, the request is denied.

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.

Valid values are applid andFUSNAPPL.

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.

Valid values are:

• NO: Temporary errors are not written to the audit log or to SMF.
• YES: Temporary records are written to the audit log and to SMF.
• BOTH: Temporary records are written to the audit log and to SMF.
• AUDIT: Temporary records are written to the audit log but not to SMF.
• SMF: Temporary records are written to SMF but not to the audit log.

Valid values are:

• NO: Only members defined in the CONFIG member or overridden by the GLOBAL CONFIG member are enabled. This is the default value.
• YES: All members of the CONFIG DD statement are enabled unless the member is defined with the AUTOENABLE=NO parameter. If you want to use the Command Center function that creates node definitions, you must specify AUTOENABLE=YES.

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

Valid values are ANY and a facility name. This parameter supports the following functions:

• Restricts the people that are able to administer the Platform Server work queue.

  By specifying a facility class name in this field, the Platform Server gives rights to administer the Platform Server work queue only to those users that have READ access to this facility class.

  By specifying ANY or by leaving this field bank, the Platform Server gives anybody rights to access the work queue: all valid users have the same rights and privileges. Any valid user can browse the work queue and display or put on hold or purge activities waiting to execute. You might have to consult your mainframe security specialist for a facility that can be used to limit access to the Platform Server work queue.

• Restricts a user to view but not to update access to the Platform Server work queue.

  By creating a facility class with a prefix of the BOSSID and a suffix of .READ, you can assign users that can view all Platform Server transfers but can only update transfers where the local user ID matches their TSO user ID.

• Determines if a user is a Platform Server administrator with ADD/DELETE/LIST capability of Platform Server profiles for all users.

  By specifying a facility class name in this field, the Platform Server assigns Platform Server administrator rights only to those users that have CONTROL access to this facility class.

  By specifying ANY or by leaving this field bank, the Platform Server gives anybody rights to perform the Platform Server administrator functions for all users. This means that any user is able to ADD/DELETE/LIST user profiles for all users.

Three values are defined:

• YES: U7SVC is called for tasks only when a file is created.
• ALL: U7SVC is called for tasks when a file is created or replaced.
• NO: U7SVC cannot be called.

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.

Valid values are a 32-byte facility name and$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 Command Center administrative capabilities include:

• List or update node definitions.
• List or update profile definitions.
• Execute Platform Server transfers.
• Browse Platform Server completed transfers.
• Alter Platform Server transfers waiting to run.

Valid values are a 32-byte facility name and$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.

Valid values are a 32-byte facility name and$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.

Valid values are a 32-byte facility name and$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.

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

Valid values are:

• YES: Performs CRC checking by default.
• NO: Does not perform CRC checking by default. NO is the default value.

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

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.

When a non-zero value is defined, the Platform Server sets the volume count when the following prerequisites are met:

• An MVS file is being created.
• The DATACLASS parameter is defined.
• The GLOBAL DATACLASS_DEFAULT_VOLCT parameter is set between 1 and 255.

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.

Valid values:

• CREATE_REPLACE: This is the default value. If the file exists on the system, replaces the file. If the file does not exist, creates the file.
• CREATE: If the file does not exist, creates the file. If the file exists on the system, displays an error message and terminates the transfer request with errors.
• REPLACE: If the file exists on the system, replaces the file. If the file does not exist, displays an error message and terminates the transfer request with errors.
• APPEND: If the file exists on the system, appends to the end of the file. If the file does not exist, displays an error message and terminates the transfer request with errors.
• CREATE_APPEND: If the file exists on the system, appends to the end of the file. If the file does not exist, creates the file.

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.

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 datasets. 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 postprocessing 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.

Valid values are:

• NONE: No email notification is sent. This is the default value.
• INITIATOR: Email notifications are sent on initiator transfers.
• RESPONDER: Email notifications are sent on responder transfers.
• BOTH: Email notifications are sent on initiator and responder transfers.

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.

See the following list of the tokens in the long and short forms that are supported:

• #(STATUS) or #(ST): Failure or success
• #(NODE) or #(ND): 1-byte to 64-byte node name, IP address, or IP name
• #(SERVER) or #(STC): 1-character to 8-character started task name
• #(PROCESS) or #(PR): 1-character to 8-character transfer process name
• #(TRANSID) or #(TID): 10-character transfer transaction ID
• #(EASTERTIDE) or #(UD): 1-character to 25-character transfer description
• #(LFILE) or #(LF): 1-character to 255-character transfer local file name

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

The default value is Transfer Request #(ST) Activity Number #(TR).

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.

See the following list of the tokens that are supported in the long and short forms:

• #(STATUS) or #(ST): Failure or success
• #(NODE) or #(ND): 1-byte to 64-byte node name, IP address, or IP name
• #(SERVER) or #(STC): 1-character to 8-character started task name
• #(PROCESS) or #(PR): 1-character to 8-character transfer process name
• #(TRANSID) or #(TID): 10-character transfer transaction ID
• #(EASTERTIDE) or #(UD): 1-character to 25-character transfer description
• #(LFILE) or #(LF): 1-character to 255-character transfer local file name

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

The default value is Transfer Request #(ST) Activity Number #(TR).

Valid values are:

• NONE: No encryption. This is the default value.
• AES: AES 256-bit encryption
• AES128: AES 128-bit encryption
• DES: DES encryption
• 3DES: Triple DES encryption
• BF: Blowfish 56-bit encryption
• BLOWFISH: Blowfish 56-bit encryption
• BFL: Blowfish 448-bit encryption
• BLOWFISH_LONG: Blowfish 448-bit encryption

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.

Valid values are:

• FIPS140: Uses FIPS 140 security policy.
• TLSFIPS: Uses FIPS 140 protocols and ciphers to execute all SSL/TLS connections, but does not require the entire STC to execute in FIPS 140 mode.
• HIPAA: Uses HIPAA security policy. This requires that all files are transferred using encryption, and that encryption must be 128 bits or greater. This checking takes place for both initiator and responder requests.
• NO: Uses no security policy. This is the default value.

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 Postprocessing Actions.

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

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

Defines whether directory transfer postprocessing actions are executed on the parent transfer or the child transfers.

Valid values are:

PARENT: Executes postprocessing on parent transfer.

CHILD: Executes postprocessing on child transfers.

Default: CHILD

Defines whether directory transfer preprocessing actions are executed on the parent transfer or the child transfers.

Valid values are:

PARENT: Executes preprocessing on parent transfer.

CHILD: Executes preprocessing on child transfers.

Default: CHILD

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 dataset 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.

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 dataset.

Valid values are NO andYES. 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.

For more information on how to code a user exit, see Appendix F. User Exits.

Valid values are NO andYES. 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. Valid values are NO andYES. The default value is NO. For more information, see Appendix F. User Exits.

Valid values are NO andYES. 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.

For more information, see Appendix F. User Exits.

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.

Valid values are NO andYES. The default value is NO. For more information, see the Appendix F. User Exits.

It is a 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. 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. 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.

Valid values are:

• NO: Purges the transfer from the active queue. This is the default value.
• YES: Puts the transfer on the hold queue. The operator can then release the transfer when the condition that caused the error is resolved.

This parameter contains two sub-parameters.

The first sub-parameter defines what happens when a locally initiated file transfer is completed with a temporary file or network error, and the Platform Server retries until the batch try count or GLOBAL DEFAULT_TRY_COUNT is exceeded.

For the first sub-parameter, valid values are:

• NO: Purges the transfer from the active queue. This is the default value.
• YES: Puts the transfer on the hold queue. The operator can then release the transfer when the condition that caused the error is resolved.

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

For the second sub-parameter, valid values are:

• NORELEASE: The transfer cannot be released automatically. The transfer must be released by a Platform Server operator.
• RELEASE: The Platform Server can automatically release the file transfer request.

The transfer request can be released in the following two ways:

• The operator can release the transfer.
• The transfer can also be released if another transfer request is successfully performed with the same node. The request that causes the transfer to be released can be initiated locally or remotely.

The default value is MIGRAT. When the Platform Server detects a migrated dataset, the dataset 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 a 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 a good practice that you leave this parameter as the default value 15.

Valid values are:

• NO: Initiator tasks run normally when the Platform Server is started. This is the default value.
• YES: The Platform Server can be started, but cannot initiate any file transfer requests. You can use the INITIATORSTOP operator command to stop initiator requests while the Platform Server is running, and use the INITIATORSTART operator command to start initiator tasks again.

Defines the PDS dataset name used for the SUBMIT operand.

When you use TYPE=COMMAND, SUBMIT=membername operand of the Platform Server batch interface to submit a job, if the JCL is located on the remote system, you can define the JCL to be submitted through one of the following two ways:

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

When just a member name is specified in the SUBMIT operand, the Platform Server uses the dataset name defined in the GLOBAL JOB_SUBMIT_DSN parameter.

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.

Valid values are:

• ALL: TCP, SNA and cross memory requests are all accepted. This is the default value.
• NONE: Only cross memory requests are accepted.
• TCP: TCP and cross memory requests are accepted.
• SNA: SNA and cross memory requests are accepted.

When that number is exceeded or the file runs out of space, the Platform Server begins rewriting over the oldest records in the audit files. The default value is 25,000 and the valid range is from 100 to 99,999,999.

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.

Valid values are:

• Yes: Passwords are not translated to upper case.
• No: Passwords are translated to upper case. This is the default value.

It is a 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. 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.

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.

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.

Valid values are:

• NONE: No MQ notification is sent. This is the default value.
• INITIATOR: MQ notification is sent for initiator tasks.
• RESPONDER: MQ notification is sent for responder tasks.
• BOTH: MQ notification is sent for both initiator and responder tasks.

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

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. 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.

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

Valid values are:

• YES: Releases unused disk space when a PDS file is created. This is the default value.
• NO: Does not release unused disk space when a PDS file is created.

Valid values are:

• OLD: The Platform Server requires exclusive access (DISP=OLD) to the dataset. This is the default value.
• SHR: The Platform Server requires shared access (DISP=SHR) to the dataset.

When you first install the product, you can leave this parameter to the default value 3.

Valid values are:

• YES: The Platform Server automatically removes the trailing CR delimiter.
• NO: The Platform Server does not remove the trailing CR delimiter. This is the default value.

This parameter has two subparameters. The first subparameter is for initiator requests and the second subparameter is for responder requests. The default values are NO,NO.

• If YES is specified for an initiator request, the IPADDR and IPNAME parameters cannot be used. Requests can be scheduled only through the use of the NODE parameter, and the node specified in the NODE parameter must be enabled. If IPADDR or IPNAME parameters are used or if the node specified on the NODE parameter is not enabled, the request is terminated with an error.
• If YES is specified for a responder request, the Platform Server checks the node definitions when a request is received. If the LUNAME or IP address from which the request is received is defined on an enabled node definition, the request is accepted. Otherwise, the request is rejected with an error.

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

Valid values are:

• YES: Requires responder profiles. This can only be overridden by a node definition that specifies the RESPONDER_PROFILE parameter.
• NO: does not require responder profiles. This is the default value.
• DUAL: The responder profiles are checked. If no matches are found in the responder profile, the request can continue to be processed, and the user ID and password are checked against the RACF or ACF2 or Top Secret security system.

For more information, see User Profiles.

Valid values are:

• YES: Local password is required to create a responder profile when the user initiating the request is different than the user defined by the LUSER parameter.
• NO: Local password is not required to create a responder profile when the user initiating the request is different than the user defined by the LUSER parameter. This is the default value.

Valid values are:

• YES: The Platform Server can be started, but cannot accept any responder file transfer requests. You can use the RESPONDERSTART operator command to start responder tasks again.
• NO: Responder tasks run normally when the Platform Server is started. This is the default value.

Valid values are 4 - 10. The default value is 6.

Valid values are 3 - 8. The default value is 3.

Valid values are 0 - 8. The default value is 1.

Defines the minimum number of special characters. The valid special characters are !@#$%();:&<>

Valid values are 0 - 8. The default value is 1.    

Valid values are 3 - 8. The default value is 4.

Valid values are:

• YES: Validates the responder profile password strength.
• NO: Does not validate the responder profile passwords. Default: NO

Valid values are:

• YES: Requires upper and lower case characters. The default value is YES.
• NO: Upper and lower case characters are not required.

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.

Valid values are:

• YES: Activates the SAPI interface.
• NO: Does not activate the SAPI interface. This is the default value.

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

Valid values must be 4 bytes. 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 postprocessing actions on output, run under this user ID's authorization.

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

Defines whether a failure notification email will be sent when an inactive or held transfer is canceled:

Valid values are:

YES: Sends an email when an inactive or held transfer is canceled.

NO:  Does not send an email when an inactive or held transfer is canceled.

Default: YES

Defines the sender email address that will be used when a Failure Notification email is sent.  When defined, this overrides the GLOBAL SMTP_SENDER_HOSTNAME and the hard-coded TRANSFER_FAIL value.

There is no default for this parameter.  

Defines the sender email address that will be used when a Success Notification email is sent.  When defined, this overrides the GLOBAL SMTP_SENDER_HOSTNAME and the hard-coded TRANSFER_GOOD value.

There is no default for this parameter.  

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-character 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 dataset.

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. Valid values can be up to 40 bytes of data.

This is the default unit type for space allocations when a new dataset 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.

Valid values are:

• NONE: No encryption
• AES: AES 256-bit encryption
• AES128: AES 128-bit encryption
• DES: DES encryption
• 3DES: Triple DES encryption
• BLOWFISH| BF: Blowfish 56-bit encryption. This is the default value.
• BLOWFISH_LONG | BFL: Blowfish 448-bit encryption

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 must omit this parameter or specify this parameter as NULL.

If you are using a key ring, 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 a 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.

Valid values are:

• NO: SSL is not required but can be used. This is the default value.
• YES: SSL must be used for both initiator and responder requests.
• OUTSIDE_NETWORK: SSL usage depends on the IP address of the target system and how it compares with the address of the local system.

  If the target system address is outside the subnet defined by the SSL_NETWORK_IPADDRESS and SSL_NETWORK_SUBNET parameters, the request must use SSL.

Valid values are:

• NO: SSL is not required but can be used. This is the default value.
• YES: SSL must be used for both initiator and responder requests.
• OUTSIDE_NETWORK: SSL usage depends on the IPV6 address of the target system and how it compares with the address of the local system.

  If the target system address is outside the subnet defined by the SSL_NETWORK_IPADDR_IPV6 and SSL_NETWORK_SUBNET_IPV6 parameters, then the request must use SSL.

Valid values are OS390 andZOS. This parameter has no default value.

Ensure that you only use this parameter under TIBCO Support instructions.

Valid values are:

• ERROR: Rejects the tape mount. Terminates the transfer with retry-able abend 913-34.
• IGNORE: Performs the default SMS action. This is the default value.

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

Valid values are either 0 or a number from 30 to 7200. The default value is 0 and it means no keepalive.

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 default value ALL means to bind to all TCP network interfaces. If you want to bind to only a single network interface, specify the dotted decimal address of the network interface, so the Platform Server only binds to that network interface for outgoing requests.

The default value ALL means to bind to all TCP network interfaces. If you want to bind to only a single network interface, specify the IPv6 address of the network interface, so the Platform Server only binds to that network interface for outgoing requests.

The job name can contain up to 8 characters.

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.

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.

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 IPV6 address of the network interface, so the Platform Server then only listen to that network interface for incoming requests.

This parameter is used only for incoming IPV6 requests, and it is ignored for outgoing requests.

Valid values are:

• NO: Does not append LF or CRLF to the last record. This is the default value.
• YES: Appends LF or CRLF to the last record.

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

Ciphers that meet the following criteria are specified in the sample GLOBAL member:

• FIPS approved
• AES256
• SHA or higher message digest

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.

Valid values are:

• TLSV1: TLSV1 is supported.
• TLSV1_1: TLSV1_1 is supported.
• TLSV1_2: TLSV1_2 is supported.
• ALL

Example: TLSENABLEDPROTOCOLS=TLSV1_1,TLSV1_2

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

If a non-TLS 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 TLS processing is disabled.

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 TLS requests.

If a non-TLS 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.

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 IPv6 address of the network interface, and the Platform Server only listens to that network interface for incoming requests.

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.

Valid values are:

• ALL: TCP, SNA and cross memory requests are all accepted. This is the default value.
• NONE: Only cross memory requests are accepted.
• TCP: TCP and cross memory requests are accepted.
• SNA: SNA and cross memory requests are accepted.

This parameter describes how transfers can be scheduled, but does not regulate how transfers are actually executed. Only the following programs that initiate transfers are referred to:

• Batch: OSIUB000 and OSIUC000
• ISPF: REXX and ISPF panels

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.

Valid values are:

• YES: Trap requests are sent for all transfer requests that are completed either successfully or unsuccessfully.
• NO: Trap requests are not sent. This is the default value.
• ERRORS: Trap requests are sent when a request is unsuccessful and no more retries can be made.

• YES: Allows MFT to delete unexpired files when DISP=DNEW
• NO: Does 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 datasets. 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.