Technical experts from the IBM Transaction Processing Facility (TPF) Development Lab share knowledge and information about the TPF product set - including z/TPF, TPF Operations Server (TOS), z/TPF Database Facility (z/TPFDF), and the TPF Toolkit.
IBM® Doc Buddy, a no charge mobile application that enables retrieving support documentation for IBM z Systems ™ products, can help you resolve problems faster and improves the total information experience. After you install the application on your smart phone or tablet, you can search for the error messages issued from IBM z Systems products within seconds! IBM Doc Buddy provides the following features: The application enables looking up message documentation without Internet connections after the initial setup. To download z/TPF... [More]
IBM Knowledge Center is now in the Request for Enhancement (RFE) Community , where IBM product users can make suggestions for improving the IBM Knowledge Center application. Besides opening and tracking new requests, you also can search existing requests, and comment on them. The RFE Community provides a great opportunity for you to interact more directly with the IBM Knowledge Center development team.Visit the RFE Community and check it out!
The TPF Lab will be closed on Monday, May 29, 2017 for the U.S. Memorial Day Holiday. The Lab will resume normal operations on Tuesday, May 30, 2017. If you have a critical problem that requires immediate assistance, please open a Severity 1 PMR/ETR and offshift support will be notified. (See Opening Problems with the Service Request Tool for more information.)
Greater than 64 KB TCP read support increases the maximum amount of data that can be received on a single TCP socket read-type function from 64 KB (65535 bytes) to 1 MB (1048576 bytes). With this enhancement, the cost of reading large TCP messages in customer applications is significantly reduced in terms of application complexity and CPU consumption in the z/TPF system. Non-SSL z/TPF WebSphere MQ sender/receiver channels, SRVCONN channels, and MQ Client are updated to use this support when reading large MQ messages. For more... [More]
User exits for MongoDB requests provides two user exits for you to control pre-request and post-request processing by using z/TPF support for MongoDB. You can use the pre-request user exit (UMON_pre_request) in the following ways: Check resources or status for each received MongoDB request. Reject requests and return the reason why the requests are rejected. Optionally disconnect the MongoDB session from the z/TPF server for MongoDB. With the post-request user exit (UMON_post_request), you can apply accounting logic based on the... [More]
IBM delivered z/TPFDF default key support for z/TPF support for MongoDB (APAR PJ44378) in April of 2017. This support provides a way for you to access z/TPFDF files that do not have default keys defined in the z/TPFDF database definition (DBDEF). Previously, the default keys could be defined only in the DBDEFs and doing so was optional. Many DBDEFs do not have default keys defined; instead, the z/TPFDF application uses a DBKEY macro or dfkey() function to specify the file organization when the application inserts or updates LRECs. With... [More]
At the TPF User's Group meeting in Scottsdale, AZ, a hot topic was held on PUT Delivery Model Changes Not all customer representatives were able to attend the session, so we are posting this call for sponsor users to participate in phone calls and/or web meetings to provide feedback on the APAR reference data, prerequisite data, tar packages and tools that we currently provide. The responses collected will be used to enhance our deliverables, possibly by reformatting information, removing information that is redundant or no... [More]
IBM TPF Toolkit 4.2 Interim Fix 10 is now available on the update site. This interim fix contains maintenance and security updates only. For more information, see the security bulletin . IBM TPF Toolkit 4.0 Interim Fix 12 is now available on the update site. This interim fix contains security updates only. For more information, see the security bulletin . Regards, The TPF Toolkit Team
As Java and REST services on z/TPF comes to users and their production equipment there needs to be a way to monitor performance. Enter the Services Report in data reduction on Linux on Z Systems. This new report is one way to monitor the culmination of relevant statistical information gathered by data collection and interpreted by the tpfdataredux tool on Linux. This report consists of two core tables. These tables are the Service Summary table and the JAM (z/TPF application manager for Java) Summary table. The Service table depicts individual... [More]
The "SSL Death Alert" vulnerability for OpenSSL affects z/TPF. With APAR PJ44539, the z/TPF system was updated with OpenSSL version 1.0.2j to address this security vulnerability. For more information about the security vulnerability, see security bulletin . For more information about APAR PJ44539, see the APEDIT .
With the availability of z/TPF support for Java™ , you can now run Java applications on your z/TPF system. These applications can be structured as stand-alone applications or as service applications in Java. On the z/TPF system, stand-alone Java applications can represent drivers, utilities, server daemons or other processes and are started using the ZFILE java command. The ZFILE java command is the standard java command that is supported by the IBM runtime environment on other platforms and accepts the same set of... [More]
z/TPF WebSphere MQ includes a trace facility enhancement to diagnose problems with applications and channels, including problems with new or existing applications that use a queue or channel problems. You can choose to display the trace on the console or to write the data to tape and process offline. Using tracing to tape instead of tracing to the console can avoid flooding the console with numerous messages. Using the trace facility adds overhead to the z/TPF system; therefore, you can enable trace only on a subset of queues or... [More]
z/TPF support for MongoDB (PJ42292) introduced z/TPF to MongoDB and allowed you to access your z/TPFDF databases through a standard MongoDB interface. With z/TPF support for Java™ (PJ43892), z/TPF became Java compatible and you could run Java applications on your z/TPF system. Both of these APARs are about using commonly used interfaces, standard languages, and widely known skills, bringing those to z/TPF, and helping you unlock the data and capabilities of your z/TPF system. This article... [More]
The aparDownload and aparMerge commands in the zTPF APA R Do wnlo ad t ool s package were updated to work with download packages for the IBM® 64-bit Runtime Environment for z/TPF, Java™ Technology Edition, Version 8 . If you use these tools, download the latest copy to ensure that you can download the Java runtime tar files. In addition, the APAR data spreadsheet and CSV files that are available for download from the TPF Family Products: Maintenance... [More]
Be advised that the aparDownload command in the zTPF APAR Download tools package was updated to work with new security software that was added to the Secure FTP APAR download servers last Sunday, February 12, 2017. If you use these tools, download the latest copy to ensure that you can continue to download the APAR tar files. For additional details, see Service Bulletin 195 .
The IBM Tivoli Monitoring Agent for z/TPF V1.1.3 is available for download from the TPF Family Products: Tools web page. This version adds support for services statistics. APARs PJ44455 and PJ43892 add support for continuous data collection to collect services statistics. The data collected by the CDC_SERVICE and CDC_JAM metrics is displayed in the Services workspace in the Tivoli Enterprise Portal by the IBM Tivoli Monitoring Agent for z/TPF. For more information about APARs PJ44455 and PJ43892 , see the APEDITs.... [More]
With z/TPF APAR PJ43892 (z/TPF support for Java™) applied, a Java conflict occurs that causes some TPF Toolkit operations to function incorrectly. When the server.linux script is run to start the Remote System Explorer (RSE) DataStore server on Linux on z Systems, the PATH environment variable is updated to a version of Java that is not supported in the MakeTPF environment that was updated with APAR PJ43892. The MakeTPF environment that was updated with APAR PJ43892 requires IBM SDK, Java Technology Edition Version 8 or later. For... [More]
With z/TPF support for Java™, you can run Java Platform, Standard Edition (Java SE) 8 applications on your z/TPF system. Programmers with little or no knowledge about the z/TPF system can develop Java applications using familiar integrated development environments (IDEs) and development tools for Java and then deploy those Java applications on your z/TPF system. On the z/TPF system, the runtime environment for Java is the IBM® 64-bit Runtime Environment for z/TPF, Java Technology Edition, Version 8 and is compatible with Java SE... [More]
IBM delivered logging for z/TPF support for MongoDB (APAR PJ44239) in November of 2016. Logging for z/TPF support for MongoDB is different from the MongoDB log messages function. Logging support on the z/TPF system logs the MongoDB requests and replies for specified collections and actions; the MongoDB log messages function logs requests and replies by severity and MongoDB components. Logging for z/TPF support for MongoDB can help you in the following ways: 1. Diagnosing database problems that can occur when you update the z/TPFDF... [More]
IBM TPF Toolkit Interim Fix v4.2.9 is now available on the update site. For additional information, please see the announcement. There are a number of migration consideration in this interim fix, so please pay extra attention to the migration information in the service.html file provided with the interim fix. In addition, a YouTube channel has been started for IBM TPF Toolkit and two videos have been uploaded related to the content of this interim fix. Installing IBM ZOS Connect EE API Editor provides... [More]
Socket lock contention enhancements improves the efficiency of TCP/IP and socket API processing on the z/TPF system. In the z/TPF system , the socket block lock is extensively used in processing TCP/IP and socket APIs. TCP/IP and socket API processing on different I-streams tries to hold the socket block lock, which can cause contention. Socket lock contention enhancements reduces the amount of TCP/IP and socket API processing that is holding the socket block lock when the send , sendto , write , and writev functions are called.... [More]
The TPF Lab will be closed on the following dates: Monday, December 26, 2016 Monday, January 2, 2017 We will have limited staff working from now through the end of the year so you might experience longer than usual response times. The Lab will resume normal operations on Tuesday, January 3, 2017. We wish all of our customers a very happy holiday season, with best wishes for the New Year!
PJ44068: critical JSON fixes The JSON being produced in the original DFDL support was not always valid JSON so PJ44068 was needed to fix the following issues: 1) JSON array notation  was not being generated and was repeating the elements like what is done for XML. 2) JSON boolean values were being created as strings of either "true" or "false" instead of using the proper non-string notation. 3) The JSON null value was not being set for DFDL elements defined as nillable. The value being set was the empty string which... [More]
The Required z/TPFDF source code and Licensed Program Specifications for PU T 13 download package was updated on the TPF Family of Products download website today (12/13/16). See Service Bulletin 193 for details.
Currently, the certificate requests or self-signed certificates generated through the ZPUBK REQCERT command can only be signed with either MD5 or 160-bit SHA (SHA1). Both of these digest algorithms are not recommended for use in industry, as they have been considered not secure against well-funded opponents. APAR PJ44481 provides the SHA256 option for the DIGEST parameter with ZPUBK REQCERT, allowing the generation of certificate requests or self-signed certificates with the SHA256 digest algorithm. For more information, see... [More]
The final set of product documentation updates for z/TPF PUT 13 became available in IBM Knowledge Center in November 2016, coinciding with the November 18 general availability of PUT 13. The PUT 13 collection now includes documentation for all product enhancements and maintenance for z/TPF and z/TPFDF PUT 13. Enhancements that are available since the September 27 content refresh include the following new function: High speed connector Logging for z/TPF support for MongoDB... [More]
The z/TPF and z/TPFDF PUT 13 eDelivery packages are now available. The downloads can be accessed through the z/T P F 1 . 1 & z/T P FDF 1 . 1 tab on the TPF Fam i ly P rod u cts : Pr o duc t So f twa r e web page. Please note that there are PUT 13 downloads for the z/TPF and z/TPF product code as well as the opensource C and C++ runtime libraries, the z/TPF Software profiler, the Apache HTTP Server 2.2 package, and the Curl package. See Ser v ice Bul l eti n 19 2... [More]
Before z/TPF PUT 13, finding a specific system heap, whether it was looking for the start or size of it, required a bit of background knowledge of that specific system heap and even then it wasn’t the easiest of tasks. Once that information was found, there were features that allowed you to look at that area in memory and even update it, but there was no guarantee that the data you were seeing or updating was completely in the specific system heap you were looking for. You might accidently go beyond the bounds of that system heap, you... [More]
In the past, the only method of viewing data collection information for a z/TPF system was to employ the offline data reduction tool on z/OS. The offline data reduction tool on z/OS was one of the few remaining tools that required customers to utilize a z/OS system to understand their critical z/TPF system. The offline data reduction tool on z/OS also required the purchase of a PL/I compiler license. In addition, z/TPFDF statistical information was not available in the offline data reduction reports. Finally, the reports generated... [More]