Find Answers

Filter Search Results
All Operating Systems:
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML MCLG: 5.1.2.1 Hot fix: Error "ASA Error -193: Primary key for table '#readassets' is not unique" or Properties screen gives error
MCLG: 5.1.2.1 Hot fix: Error "ASA Error -193: Primary key for table '#readassets' is not unique" or Properties screen gives error
CMS-XML MCLG: Collage Patch to upgrade 5.1.3.x to 5.1.3.7 - Purge gives "Primary key for row in table 'Asset' is referenced by foreign key
MCLG: Collage Patch to upgrade 5.1.3.x to 5.1.3.7 - Purge gives "Primary key for row in table 'Asset' is referenced by foreign key
CMS-XML IOO311: Receiving bad data on sequential reads
Users are receiving bad data on sequential reads. Appears that the switch to MSR if it happens with a key toward the end of an extended VSAM file, after the re-open appears that the wrong key is there. Programmer did traces and is getting data with a high value and then is getting data with a low record and this is with sequential files.
CMS-XML IOO312: After upgrade, IOO seems to be handling file differently, switching to NSR.
Customer implemented V3.1.2 in their production environment and had a programmer report that his program is getting NOTFOUNDs intermittently against the same key . They found some indicators in the extended stats for the job, that might be related to his problem. Prior to the new release going in, IOO was handling one of his files one way, and now that has switched, for no apparent reason.
CMS-XML Patch or Update for PVCS, Version Manager, version 6.8.0
This patch contains 3 defect fixes for development interfaces and one new feature. The defect fixes are for the following problems: 1 Erroneous Prompt for a New Product Key [1034633] 2 Check Out Status Is Incorrectly Displayed in PowerBuilder 8 [1034635] 3 Memory Errors with COM IDEs [1034106] The new feature is the ability to stop the PVCSCLIServ Service.
CMS-XML SSM823: MAINT after INTEG required subsequent INTEG (more work to do)
If you do not have the fix in place and you run the $INTEG job (SIMULATE not specified) and then the $MAINT job (some LEVEL= specified) repeatedly - both with TRACE specified - you are likely to see that one Delta Master record (a compression/expansion record), whose key looks like x'00xxxx000000000000000000' (xxxx is some value between
CMS-XML Mariner 6.2.1 Patch Release
What is New or Updated in this Patch? 5712 ALM Integration: Backspace key doesn't work in the Encrypt Password field. 5717 ALM Integration: Team Track configuration xml shows specific server instead of locahost. 5734 Rollup Investment Hierarchy job missing from list of available Job types.
CMS-XML Version Manager 8.2.0.1 patch for 8.2.0.0
1.1.2 Desktop Client: Java exception thrown when using Delete key to delete label from file [DEF151216]
CMS-XML Changeman ZMF 5.6.1.03 Patch Release
This COPY structure by itself is not enough to trigger the loop. The location of the COPY statement within the collection area (internal program storage) is key to the occurrence or non-occurrence of the loop. As this is not predictable, Serena recommends that you use a backlevel version of CMNWRITE to avoid this problem.
CMS-XML IOO311: Stats not being generated for a file.
records are added by key at the end of the file during the processing. 5) This is a file belonging to a third-party vendor, the product is called AMMO. I need the extended stats, in particular (e.g. the number of "points" issued), to revisit the buffering for this file because it is generating over 3M EXCPs daily.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs