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 Link Information gets deleted when Scheduler (in a linked package) is updated
Link Information gets deleted when Scheduler (in a linked package ) is updated
CMS-XML Various versions of an "Invalid character (Unicode 0x0)" error message when trying to approve a linked package from TT.
Various versions of an "Invalid character (Unicode 0x0)" error message when trying to approve a linked package from TT.
CMS-XML How to save compile, link and user options without baselineing a package.
Compile , link and user options are recorded as history each time a component is baselined. The next time the component is compiled or recompiled, the options in effect when it was previously baselined are used.
CMS-XML Linked Approver not removed from package after Freeze, Revert, then Unlink
The Revert service will reset the Linked Package indicator and delete the Link Package Approvers. A user must Relink a package after a revert. This is the direction ECP is heading.
CMS-XML ERO: XML checkin fails for recompiled/relinked package components for a release.
When doing an XML checkin from a package linked to an ERO release (RLSMAREA PACKAGE CHECKIN), when you do the CHECKIN from one area to another the XML service fails for recompiled/ relinked components. Checkin for components physically present in the staging or area datasets works fine.
CMS-XML ZMF complex/super packages losing participating package relationships
ZMF complex/super packages losing participating package relationships
CMS-XML Invalid SYNCH18! auditing package 'staging libraries only'
A customer has encountered invalid SYNCH18!s (a called load module in a staging library was deleted after it was statically linked into a composite load module in the package ) being reported when auditing a participating package with the ' staging libraries only' option enabled. Auditing the package with this option disabled does not report the SYNCH18! The subroutine in question has been pulled in from the baseline library which is shared between multiple applications including that of the participating package.
CMS-XML Scratch request picking up relationship information from non-baselined packages
Scratch request picking up relationship information from non-baselined packages when no relationships exist in baseline. Also auto-generated scratch records not verified up against baseline contents to verify the validity of the scratch request records.
CMS-XML Able to relink a component when source exists in the package
When a source component is staged into a package, and the stage fails, you are able to relink the same component in the package. The source component remains in the package, but cannot be edited. Attempts to relink if the stage is successfull will receive a process error.
CMS-XML RECOMP and RELINK components not handled correctly by package integrity service
When the PACKAGE CMPONENT INTEGRTY service is run against a package that contains relinked or recompiled components, modules are incorrectly identified as missing. For components recompiled from baseline, the like-SRC is identified as missing. For components relinked from baseline, if the INPUT LIBRARY and TARGET LIBRARY types are different, the INPUT LIBRARY component is identified as missing.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs