Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Invalid characters being passed in ZMF REST Service HTTP headers
Invalid characters being passed in ZMF REST Service HTTP headers
CMS-XML ZMF REST-API missing service delete component from package.
ZMF REST -API missing service delete component from package.
CMS-XML ZMF REST Services polling function issuing erroneous error messages (CMNs544I & CMNs540I)
ZMF REST Services polling function issuing erroneous error messages (CMNs544I & CMNs540I)
CMS-XML SBM: Rest Grid connecting to ZMF Connector returns error 500
Unknown error received from https://SERVER/sbmproxy/xhp [url: 'http://SERVER:8080/almsernet/services/SernetProxyHttpServer?system= ZMF &hostName=999.999.999.999&hostPortId=8888&responseType=JSON&request=PACKAGE%2FGENERAL%2FSEARCH%2Fpackage%3Dxxxx%2CsearchForDevelopmentStatus%3DY% 2CsearchForFrozenStatus%3DY']
CMS-XML Installing a Secure Version of the ChangeMan ZMF REST API-Jenkins Integration
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
CMS-XML ChangeMan ZMF REST Services 8.2 Patch 2 Hotfix 1
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
CMS-XML Attempts to create package using REST Services prototyping tool fail
A customer is attempting to prototype a ZMF package create (POST /zmfrest
CMS-XML REST Services – Tomcat Log shows SEVERE error (tomcat-users.xml could not be found)
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.
CMS-XML REST API Tomcat Server : Message: Property Name ZMFRESTCONTEXT Not recognized.
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
CMS-XML Localisation (l10n/i18n) problem using REST API
":"500" The ZMF Server started task output, running with CCSID=284 (Spanish code page), shows the following: ...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs