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 DMCM: Replicator does not transfer related request details
DMCM: Replicator does not transfer related request details
CMS-XML Copy User doesn't transfer the content of the Memo field
Copy User doesn't transfer the content of the Memo field
CMS-XML KM-Dim2009: Three way replication involving a mix of air-gap and online sites may not keep all sites synchronized
In a three-way replication requests can be owned by any of the three sites. However once a request is transferred updates are only accepted from the owning site, meaning that requests that exist on all three sites will be out of synch on one site.
CMS-XML Dim CM 12.2.2: Adding large request attachments is very slow
Similar tests in Support took about 20 minutes but this is still a long time. SDP trace of the operation showed the file being transfered from client to server very quickly, within a minute. Then nothing occurred in the log for 15 minutes until it started to update the database.
CMS-XML DMCM: Replicator fails to report certain errors when dumping projects
Replicator fails to report certain errors when dumping projects, for example Replicator should report errors for the revisions with missing library files. However, it reports the same number of objects as being dumped but also omits the "missing" revisions and the user has no way of knowing this. This could lead to an apparent data loss scenario if these files are them transferred to the subordinate site.
CMS-XML Notification Server Email Header Information
This problem can be solved by adding following 2 lines to the MAIL HEADER area Content- Transfer -Encoding: 8bit MIME-Version: 1.0
CMS-XML Dim CM 12.2: Mainframe Build - Fetching from web client to tertiary MVS node gives bogus messages
2) Choose a project (e. g. ACCTS:ACCTS) and use the web client to fetch all files; 3) The files are transferred successfully, but the messages generated are not informative. The server command run is: -
CMS-XML 12.2.1 z/os agent : got abend 002 rc=30 when trying to unzip the xmit file
slide 4 : I transfer it on mainframe following installation guide commands slide 5 : allocation of xmit once uploaded on mainframe slide 6 : issue tso receive command
CMS-XML Dim CM 12.2 - z/OS deployment somewhat slow
Additional testing shows that: - 1) The files being transferred to the different areas are the same - a lot of small files and some bigger files, but it is pretty much the same.
CMS-XML Dim2009R2: Potential data loss in Check-in when deploy areas attached
- Check-in the file - The check-in finish and the new revision is transferred to the Deploy Area - Check-out the file
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs