Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML ZMF REST API – misaligned component/browse output
ZMF REST API – misaligned component/browse output
CMS-XML REST API: Local admin access required to subscribe to events
REST API : Local admin access required to subscribe to events
CMS-XML ZMF REST API – package/promote test functions not working
ZMF REST API – package/promote test functions not working
CMS-XML REST API - Unable to CHECKIN for a sourceLib greater the 44 characters.
REST API - Unable to CHECKIN for a sourceLib greater the 44 characters.
CMS-XML ZMF Jenkins EAP - REST API is getting (SER8401E - Invalid XMLService Combination) attempting to submit COBOL compile.
ZMF Jenkins EAP - REST API is getting (SER8401E - Invalid XMLService Combination) attempting to submit COBOL compile.
CMS-XML Event Response Code: 500 following the implementation of ChangeMan ZMF 8.2 Patch 3 - REST API (Revision-1)
Event Response Code: 500 following the implementation of ChangeMan ZMF 8.2 Patch 3 - REST API (Revision-1)
CMS-XML What are the z/OS security requirements for the Tomcat server, to support the REST API web services?
What are the z/OS security requirements for the Tomcat server, to support the REST API web services?
CMS-XML V8.2.03 REST API: Secured Port prevents ZMF variable & EVTNOxx from being set to “Y”.
V8.2.03 REST API : Secured Port prevents ZMF variable & EVTNOxx from being set to “Y”.
CMS-XML REST Services: German characters causing data translation errors in Tomcat server output
A customer is running with a ZMF Server task CCSID=1047 (Latin 1 (Open Systems)) and their package master data contains many German characters. When using the package/search Rest API we appear to return the expected data to the user. However, it always causes the following failure to be reported in the Tomcat server ZMFREST output file when the packages containing German data in the package title are returned:
CMS-XML JSON API response incorrect for Multi-Relational fields internal values - internal ID of the value does not match with TS_ID in aux table.
If you call the JSON API for using with Rest Services or Grid and get Multi-Relational fields in the response then the internal values TS_ID are incorrect. The values are provided numerically and alphabetically but mixed up.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs