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 Unable to see generated LOD and LST when a BUILD is submitted.
Using ZDD 6.1.1 GA client version, if you connect to a ZMF 5.6.2 subsystem and select a package with a checked out source member in it, when you issue a BUILD for the source member although the BUILD completes and activates the source, the associated LST and LOD members are not seen in there corresponding folders when viewed through ZDD. ZMF 5.6.x side.
CMS-XML SYNCH12 is incorrectly reported for LST component that is tied to a like-OTH component
SYNCH12 is incorrectly reported for LST component that is tied to a like-OTH component. 1) Create a package and checkout or stage a like-OTH component and be sure LST is also generated. 2) Run audit against the package and a SYNCH12 will be generated for the LST.
CMS-XML Unable to see generated LOD and LST when a BUILD is submitted.
Using the ZDD 6.1.1 GA client version, the LST and LOD components are not viewable following the build of a source member. If you connect to a ZMF 5.6.2 subsystem and select a package with a checked out source member in it, the BUILD operation completes successfully and activates the source. However, the associated LST and LOD members are not seen in their corresponding folders when viewed through ZDD.
CMS-XML CMNBILOD ending RC=8 when two stage jobs for same named component overlap or use the same like-LST library type.
When a SRC component build is requested via the ISPF or any other interface, all existing 'ILOD' (i.e. SRC-LOD relationship) records associated with that SRC are deleted from the package master metadata. When program CMNBILOD executes within the staging job it checks that there are still no ILOD records. If none are found, the build job is allowed to proceed and the component can be activated in the expected manner.
CMS-XML Why does my SerenaLicenseServer.log file show more named license checkouts than get_concurrent_usage reports?
When a named license user logs in from multiple computers (permitted because the users. lst file has multiple entries for this user), the SerenaLicenseServer.log file will show every attempt to check out the named license
CMS-XML Invalid component promotion history displayed after checkout overlay in package
- The promotion history query panel, CMNQRY28, shows the SRC as being re-staged when it is still in checkout status. - No indication is given on promotion-related panels (e.g. CMNQRY28, CMNRPM06, etc.) that the associated/ILOD components (e.g. LOD, LST , DBR, etc.) have been affected in any way.
CMS-XML CMN1077A issued for checkout, if CMNEX026 is active and X26$BULB code is active.
Customer has the following code and does not have LST defined for one application. DC CL4'*' all applications DC CL3'*' staged library type (JCL)
CMS-XML Invalid CMN2592I ‘Out of sync’ message attempting to checkout component
But the COMPLST step continued on to successfully link the LST library to the now non-existent SRC component. And a CMPONENT.PKG_LOD.LIST confirms this fact:
CMS-XML KM-Dim10: Reported Defect DEF75604: check-out - produces a branch revision on a Workset that has no branch
this will generate in the current directory a file sql-final-check. lst . In the file sql-final-check.lst, check in particular for any record where last_branch_extracted='Y' and undo check out for these items / revision.
MS-WORD Could you please have the customer verify that ALL of the following concatenations of libraries match
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs