Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Library types missing from global and application administration after upgrade to 8.2 Patch 4
After upgrading a ZMF 8.2 Patch 3 system to 8.2 Patch 4 using the documented conversion job (CMVCONVF) a large number of administration library type records are missing. For example, global admin shows 263 library types pre-upgrade but only 211 post-upgrade (option a.g.2). Similarly, my DEMO application shows 184 library types on 8.2 Patch 3 but only 138 on 8.2 Patch 4 (option a.a.2).
CMS-XML Global libtype admin sets directory blocks to zero if a LIBRARY(PDSE) is defined
Global libtype admin sets directory blocks to zero if a LIBRARY(PDSE) is defined
CMS-XML VLD library type
I'm seeing some strange behavior related to library type VLD. I noticed that it is not defined in either my Global or Application Library Types . What is the behavior of this libtype and why am I now having problems?
CMS-XML Library Type Sort order ignored in Checkout and Recompile panels.
The Lib Type order entered in Global Admin and Local Admin is ignored during Checkout and Recompile. It seems that the order of Lib Types as entered in panels CMNGRST1 or CMNCLRST does not have any impact except in these panels themselves. I would have expected that the list of Lib Types displayed to users in panels such as CMNCLTSL and CMNSTG08 would reflect the order entered in CMNGRST1 or CMNCLRST.
CMS-XML Default CMNSTG08 to sort on LIB for the Library Type Selection List.
If you define a new library type in both Global and Application Admin and then define the baseline library, when you come to stage a component from development for the new library type the library type is not in the same location on the Library Type Selection List panel CMNSTG08 as when you defined it in Appl and Global Admin (CMNCLLT0). This is confusing, so we need to default the sort to Lib on panel CMNSTG08.
CMS-XML NCL library type is no longer sacred in ZMF 6.1.0 and later releases
Customers using the NCL library type to house subroutine-type components in CMN ZMF 6.1.0 must now ensure that these are defined as like-N libraries in the appropriate global , application and release administration panels or code CMNEX034 to define the NCL library type as like-NCL.
CMS-XML CMNZMF 6.1.1 - Audit Autoresolve CMN1077A - Undefined staging library type
The customer is testing CMNZMF 6 NS2 is not a defined library type in Global or Application configuration.
CMS-XML CMN30 scratch request fails with RC=08 when component with library type defined as SD previously scratched from baseline
A package then scratches just the MPC component from baseline. With the Global Admin parm ‘Auto scratch load member with source’ selected, when a second package creates a scratch request for the source MPS component it also generates the scratch records for LST, MPS, and MPC. Because the MPC component was already scratched the CMN30 job fails with a RC=08.
CMS-XML CMN5052A - message ID does not exist. when adding a like other libtype to an appl with SSV
Add a new like other libtype to the global libtypes with the following: CMNCGLT1 Global Library Types Part 2 of 2 Command ===>
CMS-XML No dataset validation running the LIBTYPE\GBL\CREATE service.
When creating a Global /Application Lib Type through XMLSERV using the yellow XML service LIBTYPE |GBL|CREATE, you can enter a sequential dataset with 0 directory blocks which the XML Service creates. Now, if a component is staged for this lib type the STC abends with a S013-14.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs