ZMF REST Services Getting Started Guide, all secure communication functionality (i.e. SSL) associated with this processing on z/OS must be implemented using IBM's Application Transparent Transport Layer Security (AT-TLS). Some customers may have found and implemented other solutions that address their specific needs (e.g. the implementation of native Apache Tomcat SSL connectors). However, if problems are encountered
ZMF Rest Services API. Customers must be running 8.2 Patch 2 on their test subsystem before applying these fixes. The changes in this hotfix package are incompatible with all other versions of ChangeMan
Customer is on ZMF 8.2 Patch 3 and has the REST Services Tomcat server up. They noticed in the Tomcat log the SEVERE error message listed below. The customer confirmed the file does exist using ISPF option 3.17.
The same setup was used in the previous release ZMF 8.2 Patch 4 installation and the message was not displayed, so it seems to be specific to the ZMF 8.2 Patch 5 setup. As the ZMFRESTCONTEXT keyword still exists in the shipped ZMFPARMS member
service, identical to that displayed in TSO. When the ZMF Server task is running with LCLCCSID/CCSID=1141 the returned data is misformatted as follows:
ZMF Customization Guide for more detailed information about the skeletons and processing that supports the development of CICS web services. ZMF Now Supports CICS JSON REST Bundles
A Time-out Mechanism for Communication Between ZMF and the REST server - Event Emission Has Been Implemented If the REST server becomes unresponsive for some reason, ZMF functions do not simply hang,
This enhancement supports the generation of a z/OS Connect service archive to communicate either with CICS using the IP Interconnectivity (IPIC) facility or with Db2 using native Db2 Representation State Transfer ( REST )-ful services.
