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 XML tag error in CMN100 REXX causes output to omit DB2 logical name on report
In the CMN100 REXX code when services DB 2ADMIN APL_ACTV LIST and DB 2ADMIN APL_LOGL LIST are run they reference incorrectly tag <logicalName>. Because of this the 'Logical Name' in the 'DB2 Active Library Information' section of the report is blank as is the 'DB2 Logical Name' in the 'DB2 Logical System Information' section of the report. Note: similar problem exists in the CMN990 REXX code.
CMS-XML CMNDB2DD, problem parsing SCHEMA name of "SYSPROC".
CMNDB2DD, problem parsing SCHEMA name of "SYSPROC".
CMS-XML CMNDB2DD is not templating the schema name on the DROP FUNCTION statement
CMNDB2DD is not templating the schema name on the DROP FUNCTION statement
CMS-XML 100 and 990 reports do not display DB2 logical name
100 and 990 reports do not display DB 2 logical name
CMS-XML CMNDB2PL generating incorrect data for single character DB2 PACKAGE name
CMNDB2PL generating incorrect data for single character DB 2 PACKAGE name
CMS-XML CMNRAHAR parm error processing 'short' DB2 subsystem names
The CMNRAHAR utility is provided to maintain the size of the ERO DB 2 history table. The DB2 subsystem is passed to the program as a JCL parameter. When processing 'short' DB2 subsystem names (i.e. any that are three characters or less) the CMNRAHAR job fails with a RC=12 in the EXTRACT step and the following error message:
CMS-XML V5.5.0 - DB2TM and Assist code is not extracting the PL1 component names correctly
In ZMF 5.5.0, the CMNDB2TM and CMNAS000 programs are not extracting the PL/I component names correctly, which may lead to either erroneous or missing !SYNCH audit errors.
CMS-XML Second run of DB2OPTN JCL getting RC=08 in ‘TABLES’ step because of ‘existing name’
CMNZMF.CMNDB2_ATTRIBS is a unique table in each physical DB 2 subsystem that is created by running CNTL member DB 2OPTN. If you have multiple ZMF tasks connecting locally to the same DB2 subsystem, you will get a ‘-601' SQLCODE error on the second attempt to run DB2OPTN (RC=08 in TABLES Step) when it attempts to create this table when it already exists, for example: SQL ERROR DURING EXECUTE IMMEDIATE
CMS-XML Panel CMNSTG18 ‘DB2 Site name’ not available to HLL exit BULD0118
Unable to reference the 'DB2 site name' from panel CMNSTG18 using HLL exit point BULD0118. Other HLLX variables ' db 2SubSystemId' and ' db 2PreCompileLinkLib' are available
CMS-XML Templating does not work on DB2 Stored Procedure names longer then 18 characters.
In V8 it is VARCHAR(128). As long as procedure names don't exceed 18 characters, ZMF works fine. However once it is longer then 18 characters the templating no longer works.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs