Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Problems working with ZMF in Java perspective
2 . Whilst researching this we hit several intermittent problems where component checkins failed with 'Error uploading to Data Set '. We have been unable to consistently recreate this error here but it also warrants investigation.
CMS-XML Rdz Plug-in 7.1.3 with ZMF 6.1.2 : Query component fails with an exception
Running Query Component ends with an exception
CMS-XML Multi-threaded ZMF web service requests failing with SAXParseException errors
Basing testing around sample code provided by the customer we can recreate the behaviour here. For example, running 10 identical, concurrent, multithreaded queries consisting of a logon, query , logoff frequently results in the error detailed above.
CMS-XML ZMF4ECL 8.1.2 fails to handle empty ZDDOPTS PROMOTE profile
Further research showed that the customer had effectively an empty ZDDOPTS PROMOTE profile in place which worked fine under the old client software: <?xml version="1.0"?> <options name="PROMOTE">
CMS-XML ZMF4ECL always ‘OR’ing search requests
When scanning a baseline library for records containing two strings the search results are always being generated with an ‘OR’ condition, even when the ‘AND’ condition has been explicitly requested.
CMS-XML New Features in ChangeMan ZMF for Eclipse 8.1.3
name Profile name, enclosed in question marks No
CMS-XML Calling external programs in the ChangeMan ZMF HLLX address space
4. Re-entrancy and memory utilization When calling any external program from a HLLX, two questions must be answered before deciding if it is suitable: a) has the program been coded and linkedited/bound to be re-entrant (RENT)?
CMS-XML Corrupt-looking message returned to ZMF4ECL user in response to SER9008E message
The libraries could not be expanded and there were no clues to the cause. After research we found that they had NULLFILE defined in both the shadow and promotion library 1 fields for many library types in ZMF application admin. A trace showed that this was resulting in a SER9008E (not authorized) message in the started task attempting to expand the member list and, in turn, the invalid error message being issued by ZMF4ECL.
CMS-XML Impact query shows incorrect information.
Impact query shows incorrect information.
CMS-XML Query Component not displaying component status field values
Query Component not displaying component status field values
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs