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 XML Service CMPONENT SERVICE RECOMP fails in CMNADSP with 'Required parm missing'
This problem happens whether you run the service using XMLSERV or in Batch . The same XML service request run in v551 works fine and the component is recompiled.
CMS-XML Batch XML Service error when doing promotion
If the customer runs the Promote from within ChangeMan it works fine, in V6 and V7. They also run the batch XML Promote service , in V6 it ran fine but in V7 it fails with; PACKAG SERVICE PROMOTE
CMS-XML PACKAGE.PRM_HIST.LIST XML Service fails to return existing promotion history data (CMN6504I)
For example, a SERXMLBC batch call will end with a step return code 8 and the following response: <statusMessage CMN6504I - No information found for this request.</statusMessage
CMS-XML XML Service IMPACT/BUN/DELETE fails to delete BUN entry.
It would seem that this service never actually lets you delete any BUN entries. Even when executed against a ZMF instance which is not in use by any user nor by any batch process , it always returns "BUN entry for ..... is in use". If you detach the IA LDS, the XML issues the following message: "I/A dataspace environment has not been established".
CMS-XML 'Invalid XML service combination' message or strange results from XML
When attempting to run a function that uses XML services (ex: Batch Checkout) the job fails with a RC=16 and the message 'Invalid XML service combination'.
CMS-XML S0C4 abend running XML Service CMPONENT/PKG_COMP/LIST using SERXMLCC
The customer discovered that for those packages that the XML Service fail on, if he changes the Batch JCL to point the SER#PARM DD to a dsn that does not contain the #SERx member for the ChangeMan task, the job runs fine using Cross-Memory Services instead of TCPIP. Customer can also use XMLSERV and run it for the failed package and it works.
CMS-XML Stage in Batch fails 'Unable to connect' when TCP/IP is not up
Ron Palaniuk @SBC tried to validate that TCPIP is not a requirement in Buckingham for the ISPF functions that are now using XML . The results were that without TCPIP proc - up and running - User was unable to run Checkou/Stage in Batch. See steps to recreate and 2 filed attached
CMS-XML Several jobs fail for no apparent reason whilst running multiple, concurrent XML checkout requests
statusReturnCode:12 Subsequent attempts to rerun the job fail with a RC=8 and the following messages in the batch job: statusMessage:Local session disconnected from SerNet
CMS-XML XML area checkin request fails to remove some components from eligible list
The services in question are RLSMAREA.PACKAGE.CHECKIN and RLSMAREA.SERVICE.CHECKIN. Source components and the library types that they generate are unaffected by this problem which appears to be a duplicate of the problem we fixed for batch checkin requests under S129672.
CMS-XML XML area checkin request fails to remove some components from eligible list
When 2 administrators attempt to update Application Administration panel CMNGLP01, the "AUDIT PACKAGE LOCK" field is in update mode, rather than display mode for the 2nd administrator The services in question are RLSMAREA.PACKAGE.CHECKIN and RLSMAREA.SERVICE.CHECKIN. Source components and the library types that they generate are unaffected by this problem which appears to be a duplicate of the problem we fixed for batch checkin requests under S129672.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs