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.
To all of our great TPF clients, please join us in the 2015 Mainframe Mobile App Throwdown . Show us your industry app prototype and be eligible to win a week with our IBM experts to help you turn the prototype into a reality. Early entrants even qualify for a 1:1 with an IBM zMobile expert, so head on over to the sign-up page , read the getting started guide , and then start building.
z/TPFDF data collection infrastructure updates provide changes to the way that z/TPFDF data collection statistics are collected.
These updates include the following changes:
Statistics are collected on a per-SW00SR basis. All data collection statistics are collected for the length of time that the subfile is open.
A DFUEX user exit is available during close processing. Applications or utilities can use this user exit to query the individual subfile statistics, such as the number of I/Os that were performed for a... [More]
The file named "zTPFDF_PUT11_APAR_Descriptions.txt" in the "zTPFDF.V1.1.112014.source.tar.Z" file that is available for download from the TPF Family of Products download site for the "PID 5748-F15 z/TPF Database Facility Version 1.1" product has been updated to include missing APEDITs. For additional information, please see Service Bulletin 183 .
You can use prefetch prime block processing to open multiple z/TPFDF subfiles and initiate find processing for the prime addresses of all the opened subfiles with as little as one WAITC macro or waitc function required.
When a z/TPFDF subfile is opened, the only processing that is done is the SW00SR slot in the database interface block (DBIFB) is set up. Each time a subfile is accessed for the first time, z/TPFDF issues a find API to retrieve the prime block from DASD, and then z/TPFDF issues a WAITC macro or waitc function to wait for... [More]
With APAR PJ42623, the z/TPF TCP/IP stack has been updated to change the client port range of each local IP address from 1024-5000 to 49152-65535. This change was made to comply with RFC 6335 regarding port number assignments, allow for a larger number of z/TPF client sockets, further reduce client conflicts with server port numbers, and significantly reduce the likelihood of port number reuse issues on z/TPF when connecting to some remote server platforms.
The replacement and expansion of the client port range will accommodate a... [More]
In the past I received a request to give a free Webinar on TO2 (TPF Collection Support). One idea I had was to walk you through a real-life example of a problem, and show how to follow the instructions I gave in my previous blog post https://www.ibm.com/developerworks/community/blogs/zTPF/entry/some_basice_to2_collection_support_diagnostics?lang=en to gather information on the problem, as well as resolve it. Do you think that would be of interest? Do you have any other topics or questions about collection support that you... [More]
Multiple LREC buffer direct access support provides APIs for applications to directly access and manipulate LRECs in a multiple LREC buffer. In addition, multiple ECBs are allowed to have concurrent, read-only access to a multiple LREC buffer.
With z/TPFDF multiple LREC buffer enhancement (PUT 9 APAR PM55273), support was added to allow applications to copy multiple LRECs from a z/TPFDF database into a memory-based buffer with a single API call, and to write multiple LRECs from the buffer to a z/TPFDF database with a single API call.... [More]
When business events were first introduced for z/TPF on PUT 9, business event support allowed you to easily define signal events using event specifications (XML files). You also created dispatch adapters (more XML files) to define how to format signal events and transmit them to other platforms. After the specifications were defined and deployed on z/TPF, signal events were generated by inserting a call to the tpf_bev_signal() function in your application. By doing this, you could easily signal other systems that some event... [More]
Please take 5 minutes to select and write-in topics for webinars in 2015. We will create a schedule based on your input. Feel free to email the survey link to others that might not be subscribed to our blog.
TPF File View
While debugging your application, you can now display file records via the TPF File View, newly available through the TPF Debugger. From the TPF File view, you can select to add a monitor, type in a file address, and it will show you the entire contents of the file. If you are interested in a file address that your application is already working with, you can select that file address from one of the other views, such as the Variables view, and choose to monitor the TPF File. This will open the TPF File view and... [More]
With optimistic locking support for z/TPFDF, applications can open subfiles without a hold (lock) and then subsequently decide to hold the subfile. Prior to this support, you could lock a subfile only when the subfile was first opened. This gave the applications two main choices for locking:
Lock a subfile if there was a possibility it would be updated. This pessimistic approach to locking meant that locks might be unnecessarily obtained even if no updates were ultimately needed.
Open a subfile without a... [More]
On z/TPF PUT 11, enhancements and fixes have been made to the HTTP client daemon to improve its scalability, performance, and reliability, including:
Using a more efficient serialization mechanism to reduce the amount of CPU used and to increase the scalability of the HTTP client daemon.
Increasing by 10 times the maximum queue length of the HTTP client daemon.
Increasing by 10 times the maximum number of HTTP client requests that can be queued for a single server destination.
Issues with the ZHTTP RECYCLE... [More]
Setting maximum large logical record (LLR) size restrictions on a subfile basis is another enhancement that was made to the z/TPFDF product earlier in 2014. This support allows you to use different maximum LLR sizes across your system.
z/TPFDF LLR support provided the ability to set the maximum size for an LLR for a given installation. While this system-wide value (defined by the #LLRMLR equate located in macro acpdbe.mac) met certain objectives, you did not have the capability to define a maximum LLR... [More]
z/TPF HTTP Server support has been updated, providing the following enhancements:
HTTP server applications can now receive HTTP requests that contain the HEAD, PUT, DELETE and OPTIONS methods. Along with the already supported GET and POST methods, these HTTP methods can be used to create Representational State Transfer (REST) web services.
HTTP/1.0 version requests are now accepted. Prior to PJ42624, only HTTP/1.1 requests were supported.
HTTP Server support will automatically add Connection:... [More]