We have just released V3.0.45 of z/OS Connect EE.
In this release we have enhanced our SMF 123 records with a set of new V2 records for API requester, plus enhanced our SMF samples, including the ability to generate a comma-separated file (CSV) that can be imported into spreadsheets. We have also added two new attributes for API requesters to enable security at different levels.
SMF 123 Subtype 2 Version 2 and enhanced samples
We have made the following enhancements:
- You can now configure z/OS Connect EE to record SMF 123 subtype 2 version 2 records, which provide more detailed information about API requester requests. Do not enable recording of subtype 2 version 2 records until all the products you use to process your SMF records support this new subtype.
- You can now format all SMF 123 records as a comma-separated file (CSV) for importing into a desktop spreadsheet application. This new utility is delivered as a load module called BAQSMFX and supersedes BAQS123A.
- The pre-existing SMF sample BAQSMFP, used to format all SMF 123 records to STDOUT, is now delivered as a load module called BAQSMFP. This means you no longer require a C compiler to compile this sample.
- The SMF123S1_TRACKING_TOKEN is now padded with spaces (0x40) in the SMF 123 subtype 1 version 2 record instead of nulls (0x00). This change allows much simpler comparison with the OADATA1 fields of the DFHCICS group in the PERFORMANCE class of SMF 110 subtype 1 records.
Find out more.
API requester configuration updates
The z/OS Connect EE API requester has been enhanced to allow you to specify the following attributes:
- The requireSecure attribute on the zosconnect_apiRequesters element for all API requesters. Prior to this release this attribute could only be specified globally on the zosconnect_zosConnectManager level and therefore applied to all APIs, services and API requesters, or could be specified on individual API requesters.
- The idAssertion attribute on the zosconnect_apiRequesters > apiRequester subelement for individual API requesters. Prior to this release this attribute could only be specified for all API requesters.
Find out more.
Build toolkit version
The version of the build toolkit has changed from 1.3 to 1.4 due to fixes shipped in this release. See the list of APARs in the Change History in the IBM Documentation for details.
WebSphere Liberty Profile V21.0.0.3
The version of WebSphere Liberty Profile that is embedded in z/OS Connect EE V3.0.45 is V21.0.0.3.
This version of Liberty includes a fix that prevents HTTP return code 404 during server start up. Therefore you no longer need to pause your endpoint ports during the start up of your server to prevent HTTP return code 404.
Find out more.
Angel V16
The version of the angel shipped with WebSphere Liberty Profile V21.0.0.3 is version 16.
If you choose to update to the version of the Liberty Angel shipped with this PTF, the following error message will appear in the system output for the Angel:
CWWKB0086E THE NAME SPECIFIED FOR ELEMENT WAS NOT VALID WHEN TRYING TO REGISTER WITH ARM. THE PROGRAM ROUTINE EXITED WITH RETURN CODE: 8 AND REASON CODE: 2c. |
This error message can be safely ignored. The angel process starts and functions as normal.
If you choose not to update to this level of the Liberty Angel, then the following warning message will appear in your messages.log file:
CWWKB0127W: The current angel version is earlier than the version that the server expects. Update the angel version to the latest available version. |
Find out more.
API toolkit versions
The latest version of the z/OS Connect EE API toolkit plug-in to design and create your services and APIs is V3.0.9.1 for Aqua 3.1 users, and V3.2.9.1 for Aqua 3.2 users. You should obtain the latest version of the API toolkit from the Aqua download site for your version of Aqua as it includes all the latest features and fixes.
If unzipping the API toolkit zip file on Windows, due to the long filenames of some of the file members, you should use a tool such as 7-Zip or the “jar -x” command. Do not use winzip, winrar, or the Windows own zip extraction tool, as warnings/errors will occur during the unzip and the API toolkit will be unusable.
Find out more.
Get started today
Use the links below to find out more, and to get started with V3.0.45 now!