MFT Platform Server for z/os Release Notes

Transcription

1 MFT Platform Server for z/os Release Notes Version 7.1 Error! Unknown document property name. TIBCO provides the two-second advantage November 4, 2011

2 Table of Contents I. Introduction... 3 II. New Enhancements for MFT Platform Server for z/os... 3 III. Fixes in MFT Platform Server for z/os IV. Parameter Changes... 5 V. Batch Interface... 6 VI. Script Interface... 6 VII. PTFs since MFT Platform Server for z/os VIII. Known Issues... 9 IX. Pre-requisites X. New Messages XI. Support Copyright TIBCO Software Inc. All Rights Reserved. Page 2 of 11

3 I. Introduction MFT Platform Server for z/os is now generally available. MFT Platform Server enables secure, controlled file-transfer activity on all platforms. With the power of MFT Platform Server, businesses can transfer critical business files between applications, integrate data from a network of stores or branch locations, or send large files to an offshore data center. Release includes valuable enhancements and also resolves outstanding issues from the previous version of Platform Server for z/os. TIBCO continues to stay ahead of the competition by adding the most advanced technology to MFT Platform Server. II. New Enhancements for MFT Platform Server for z/os 1. Mixed case passwords support Platform Server for z/os now supports the use of both upper and lower case characters simultaneously in a z/os password to provide enhanced password security. 2. Added a new parameter for TCP connection timeout - An additional parameter has been added to specify the amount of time to wait for a response to a TCP/IP connection request. This parameter will provide better control for checkpoint/restart processing in the event of a network or other failure during a file transfer. 3. Customization of notification subject - Created new global parameters for the notification Subject for failed and successful transfers and tokens for parameter substitution to provide increased flexibility, usability, and effectiveness for notifications. 4. Retry the TCP connection upon startup - Retry the TCP connection if the Platform Server started before TCP/IP. 5. Improved audit records Send requests for local files that do not exist are now queued to allow audit record to be written. 6. Updated multi volume support During a file transfer, the input volume count is now passed to the dynamic allocation of the receiver. 7. Improved notification formatting- Resolved formatting errors when using Microsoft Outlook New capability to remove trailing spaces - Removed trailing spaces when z/os is receiving data so users no longer have to make changes to the input file. This capability is only supported when receiving variable length records from UNIX or Windows servers. Copyright TIBCO Software Inc. All Rights Reserved. Page 3 of 11

4 9. Updated Multi Casting - Updated the maximum entries in a distribution list from 1024 to Customers can now specify up to 2048 NODE, IPADDR or IPNAME definitions. Customers can also override the IPPORT by specifying the IPPORT statement. 10. Added new Date/Time script variables (see section VI) 11. Changed and MQ notification A change was made to display the entire 32 byte node name instead of 8 byte Node names. III. Fixes in MFT Platform Server for z/os Resolved an issue with DNI when an MQ Message Queue is defined. The following error was received: PGTF2670E DNI MQ Error Member=xxxxx: Invalid MQ QMGR defined: 1 to 4 characters must follow $MQ: and is terminated with: Added support for INCLUDE to be in the middle of PROCESS statements in the scripting interface Moved TCP startup before the Initiator Dispatcher start. This change resolves a problem binding to a Virtual IP Address. Resolved an issue where the compression ratio is invalid when files are larger than 200 MB. Resolved issue where node member display incorrectly after first display on ISPF Panel Option 2: "Node info" Resolved a hang condition in the VTAM LOGON exit. This condition occurred when the LOGON exit was entered multiple times for a single session. Symptoms of this problem include: o SNA session establishment hanging o The started task will not respond to any operator commands Fixed 0C4 that occurred on zos Platform Server Responder when TRANS_TYPE=JOB and DATASET_TYPE=VSAM was defined. This sometimes happened when an ISPF panel had set the VSAM parameters and a subsequent a job submission was initiated to a remote zos Platform Server. Copyright TIBCO Software Inc. All Rights Reserved. Page 4 of 11

5 IV. Parameter Changes New Parameters: SUBGOOD=1 to 58 characters This parameter defines the subject that will be used for successful notifications and supports 1 to 58 characters. In addition to the fixed information, the following tokens can be defined to add dynamic information to the subject: #(STATUS) #(ST) Failure or Success #(NODE) #(ND) 1 to 64 byte NodeName, IP Address or IP Name #(SERVER) #(STC) 1 to 8 character started task name #(PROCESS) #(PR) 1 to 8 character Process Name #(TRANSID) #(TID) 10 character Transaction ID #(USERDATA) #(UD) 1 to 25 character User Data #(LFILE) #(LF) 1 to 255 character Local File Name The maximum length of the Subject field after token substitution is 230 bytes. Default Value: Transfer Request #(ST) Activity Number #(TR) Note: Columns 1 to 71 will be read. Do not put any comments at the end of this parameter. SUBFAIL=1 to 58 characters Defines the subject that will be used for unsuccessful notifications and supports 1 to 58 characters. In addition to the fixed information, the following tokens can be defined to add dynamic information to the subject: #(STATUS) #(ST) Failure or Success #(NODE) #(ND) 1 to 64 byte NodeName, IP Address or IP Name #(SERVER) #(STC) 1 to 8 character started task name #(PROCESS) #(PR) 1 to 8 character Process Name #(TRANSID) #(TID) 10 character Transaction ID #(USERDATA) #(UD) 1 to 25 character User Data #(LFILE) #(LF) 1 to 255 character Local File Name The maximum length of the Subject field after token substitution is 230 bytes. Default Value: Transfer Request #(ST) Activity Number #(TR) Note: Columns 1 to 71 will be read. Do not put any comments at the end of this parameter. MIXED_CASE_PASSWORDS={YES NO} This parameter defines whether password validation will use mixed case passwords or will translate all passwords to upper case. Valid values are YES or NO. Yes: Passwords will not be translated to upper case No: Passwords will be translated to upper case If this field is not entered, the default value of NO will be used. Copyright TIBCO Software Inc. All Rights Reserved. Page 5 of 11

6 TCP_CONNECT_TIMEOUT=nnn This parameter defines the amount of time that TCP will wait for a TCP CONNECT request to complete before terminating the request with an error. The default is to wait until TCP times out the request. Valid values are between 10 to 180 seconds. V. Batch Interface Updated REMOVETRAIL: This parameter is used only when sending or receiving text files to a UNIX or Windows machine and works differently depending on whether you are sending or receiving a file. When Sending text files to remote systems with CRLF=YES, this parameter allows the z/os system to remove all trailing spaces and nulls before the file is transmitted. This will cause the transfer to run faster, and take up less disk space on the remote system. This parameter is ignored when communicating with MFT Platform Server z/os or for binary transfers. When receiving text files, this parameter will remove trailing spaces under the following circumstances : When Receiving Text files from UNIX or Windows : When the RECFM is Variable or Variable Blocked VI. Script Interface Symbolic Parameters Token Decode %TDAY The current English day of week is saved in this field. The field will be 9 bytes and space filled. Values will be Sunday through Saturday %TDAYOFWEEK The numeric Day of Week is saved in this field. The values will be from 1 to 7 where Sunday is 1 and Saturday is 7 %TMONTH The current English month is saved in this field. The field will be 9 bytes long and space filled. Values will be January through December. %TYYYY The numeric 4 digit Year is saved in this field. %TDDD The numeric Julian Day is saved in this field. Values returned will be 1 to 366. %TMM The numeric Month is saved in this field. Values returned will be 1 for January to 12 for December. %TDD The numeric Day of Month is saved in this field. Values returned will be from 1 to 31. VII. PTFs since MFT Platform Server for z/os CZ01822 Platform Server will now set the SSL flag when Responder processes an SSL Request. Copyright TIBCO Software Inc. All Rights Reserved. Page 6 of 11

7 Fixed a storage leak that could lead to an abend 878 after a period of time when notification is used. Resolved 0C2 abend in FUS when invalid SMTP Parameter is defined. Implemented storage improvements when GLOBAL SMF processing is enabled. Resolved condition where messages PGTS0023I and PGTS0804E are displayed when many messages are displayed in a short period of time. The condition that caused this error displayed 6000 messages in 15 seconds and could eventually cause the started task to require a restart. Fixed continuation when + is combined with - in column 72. Resolved 0C4 at OSIUC000+A5F6 when JCL PARM script variable has no value. Resolves problem with CKPT Restart and multi-volume dataset when communicating with IBM i/as400. Added support for Wildcard search on ISPF Manage Transfer: Transaction Selection Criteria: File name Resolved an issue causing Remote File name on third party transfers to become corrupted. Resolved hang condition when attempting to write to a tape that has not expired. Resolved 0C1 abend when executing the CFPING operator command. Removed Message PGTN9777D when CFPING operator command is executed. Resolved problem where the IP Address is displayed as in the Initiator messages. Added support for 64 byte IP names in following interfaces: o SPF/REXX o Batch Interface o Script Interface Resolved miscellaneous issues when MFT Internet Server requests a file list from z/os. CZ01834 Resolved issue where token substitution didn t work for directory transfers Copyright TIBCO Software Inc. All Rights Reserved. Page 7 of 11

8 Resolved issue where token substitution didn t work for Send transfers Resolved receiving 0C4 at FUSTOKEN+594 during Token substitution when file name is 1 byte CZ01837 Resolved an issue where FUSSCRPT transfers executed under the STC using SNA to communicate with the STC receive error 002C on ALLOCD command. The first request will succeed; subsequent requests will fail with this error. Resolved an issue where FUSSCRPT transfers incorrectly UPPER CASE the Script name and parameters Resolved an issue when a REXX exec runs under the started task and the FUSCFG entry specifies the STCNAME parameter the following error is displayed and the request fails. PGTE2234E Unable to allocate AUDPATH dsn xxxxxx.xxxxxx.xxxxxx: dd AUDPATH1 already allocated Resolved an issue on Initiator Requests, the remote password was intermittently getting corrupted CZ01838 Resolved an issue when DNI is configured for HFS files, the transfers that are queued are single threaded Resolved an issue when Command Center collects audit records from z/os, records can get corrupted on the Command Center Audit database when the Transfer _SUCCESS or _FAILURE parameters are used CZ01842 Resolved an issue where a user was receiving Message PGTF0042I indicating that the maximum CONTENTION LOSERS has been exceeded. Responder transfers were incorrectly being counted in the LOSERS count during transfer termination processing. When multiple PROCESS statements in the same batch job step use the VOLUME or OVOLUME parameter, the value is lost in the second and subsequent PROCESS statements. CZ01852 Responder Profile requests initiated by Command Center do not support Trusted Users (*VER) Copyright TIBCO Software Inc. All Rights Reserved. Page 8 of 11

9 VIII. Known Issues ISPF Changes Due to some internal control blocks being changed, V7.0 will have issues communicating with V6.5.1 and below and vice versa. Below are the restrictions regarding communicating between different versions of client and started task. ISPF V6.5.1 or less communicating with STC 7.0 or higher SERVER o History will display correct information o Active Tasks will display incorrect data TCP SNA o Both History and Active tasks will display correct information o Both History and Active tasks will display correct information ISPF V7.0 or less communicating with STC or lower SERVER o History will display correct information o Active Tasks will display incorrect data TCP SNA o Both History and Active tasks will display correct information o Both History and Active tasks will display correct information Due to the 32 byte node name change, the communication between the ISPF interface and the started task has changed. CFI has three types of communication between ISPF and the started task as defined by the FUSCFG configuration member: o Cross memory through the SERVER parameter o TCPIP through the IPADDR or IPNAME parameters o SNA through the LUNAME parameters When the STEPLIB for the ISPF interface points to a different version of CyberFusion that is running in the started task, the results from the ISPF Option 1: Manage File Transfers can be corrupted. Since a 32 byte node name is now being returned instead of an 8 byte node name, the data being displayed could be invalid if the ISPF STEPLIB does not match the started task version. The release notes document when the data could be corrupted on the ISPF panel and when it should work. Copyright TIBCO Software Inc. All Rights Reserved. Page 9 of 11

10 IX. Pre-requisites The MFT Platform Server for z/os is supported on the following systems: z/os version 1.9 or higher *Note: Support is provided by TIBCO only for the vendor s generally supported release versions. Once the operating system goes into extended support mode, or the vendor no longer supports a version, it will cease to be supported by TIBCO Technical Support. Space Requirements: MFT Platform Server for z/os: 50 Cylinders of 3390 DASD space X. New Messages PGTCB001I Activity Queued to Server: xxxxxxxxx with the following Transaction ID: tttttttttt Explanation: This message is displayed in the Batch Interface when a transfer has been queued to the started task. xxxxxxxx defines the STC Name, LU Name or IP Address/IPName of the started task. tttttttttt defined the transaction ID associated with the transfer. This message is for information purposes only and does not require any actions. PGTS0120E TCP Initialization failed: Repl E(nd) C(ontinue), R(etry) Explanation: During the started task TCP initialization, an error was detected. This error message allows the operator the ability to define the action that should be taken: E Terminate the started task C Continue processing; TCP will be disabled. TCP can be enabled through the STARTTCP operator command R Retry the TCP request. While waiting for an operator to respond to this message, the started task will attempt to perform TCP initialization every 30 seconds. If initialization is successful, this message will be deleted and started task initialization will continue normally. PGTS0121E INITAPI Failed: Started Task xxxxxxx Terminating Explanation: During the started task TCP initialization, an error was detected. Error message PGTS0120E was displayed. The operator replied E to that message. This message indicates that the started task is terminating. PGTS1503E MIXED_CASE_PASSWORDS must be YES or NO Explanation: The GLOBAL config defined the MIXED_CASE_PASSWORDS parameter incorrectly. Valid values are YES or NO. The default value of NO will be used and startup will continue. PGTS1504E SUBGOOD must be 58 characters or less Explanation: The GLOBAL config defined the SUBGOOD parameter incorrectly. Data entered into this parameter must be from 1 to 58 characters. The default value will be used and startup will continue. Copyright TIBCO Software Inc. All Rights Reserved. Page 10 of 11

11 PGTS1505E SUBFAIL must be 58 characters or less Explanation: The GLOBAL config defined the SUBFAIL parameter incorrectly. Data entered into this parameter must be from 1 to 58 characters. The default value will be used and startup will continue. PGTS1506E TCP_CONNECT_TIMEOUT must be a number between 10 and 180 Explanation: The GLOBAL config defined the TCP_CONNECT_TIMEOUT parameter incorrectly. Valid input is a number between 10 and 180 seconds. No TCP Timeout will be used. The started task will wait for TCP to timeout CONNECT requests. XI. Support For technical questions regarding installation or configuration of MFT Platform Server for z/os 7.1.0, please contact support@tibco.com. Copyright TIBCO Software Inc. All Rights Reserved. Page 11 of 11