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 Wrong Staging DSN used by Monitor / Limbo
Limbo is using the PRD MODEL DSNAME from the DP A.G.1 5th panel. Since the PRD MODEL DSNAME from A.G.1 5th panel can be different from the A.G.6 PRD STAGING MODEL DSNAME, we get a 'IKJ56228I DATA SET CMN.C53C.XMTO.#000246.X.SLTESTP NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED' error message in the Limbo panel.
CMS-XML Warning message when printing compile listing.
Customer has "DISPLAY PACKAGE USER OPTION PANEL(S) ===> NO" specified. When customer set "DISPLAY PACKAGE USER OPTION PANEL(S) ===> YES", they get "XXXXXX.CMN0757.BACKUP" was not found in catalog . Error alos occurs using =1.L (L Listing - Browse compressed listings)
CMS-XML CMN8711I error possible causes
RC=17: Check the SYSPRINT for a message like this: HPS0516W HPSIDV Cataloged dsn CHGMAN.V5R2.CUST.#000000.SRC is currently pointing to pseudo volume MIGRAT
CMS-XML CMNDYNAL Dynamic allocation error: 1708 when using edit xxxxx.src
JESYSMSG IKJ56228I UTILITY DATA SET NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED The workaround is to use XMS.
CMS-XML Create New Component - CMNDYNAL Dynamic allocation error: 1708
14.18.30 JOB02584 $HASP165 ACHERNA ENDED AT MP3JES2 MAXCC=4 CN(INTERNAL) IKJ56228I DATA SET CMNSUP.CMNT.S530ALL.CHER.#000326.SRC.SR1 NOT IN CATALOG OR C ATALOG CAN NOT BE ACCESSED
CMS-XML SER9661E Dynalloc of new log dataset failed; S99ERROR=00000004 S99INFO=170C0000 DSN=? during creation of notification
249 NOT DEFINED BECAUSE DUPLICATE NAME EXISTS IN CATALOG 249 RETURN CODE IS 8 REASON CODE IS 38 IGG0CLEH 09:49:04.11 SER9661E Dynalloc of new log dataset failed; S99ERROR=00000004 S99INFO=170C0000 DSN=?
CMS-XML Promoting package with only DBB and/or PKG components receives JCL ERROR.
The reason for this is that it is possible for a developer to check-out BIND control to make changes to it (e.g. make a change so that PLANs/PACKAGEs are used instead of just PLANs). If the BIND control is changed, then a promotion is required to make this change available within the DB2 system catalog . However, since the CMN$$PRB skel assumes that a DBRM staging library exists in the DBRMLIB concatenation during a promote with DB2, a JCL error results.
CMS-XML IKJ56228I issued in error for package JCL tailoring.
IKJ56228I DATA SET CMNSUP.CMND.S710ALL.DTHI.#000009.LRO NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
CMS-XML VARY WLM,APPLENV=xxxxxxxx,REFRESH command is not being issued or is issued incorrectly by CMNDB2SL.
If it is suffixed by an *, the command is issued. If the Environment Name in Admin is shorter than other names found in the DB2 catalog , the field is not cleared and when a match is found, only the 'matching' part of the name is replaced and the VARY command is issued with the 'combined' name. For example:
CMS-XML XMLSERV uses wrong library name ( from XMLINI) for help function
IKJ56228I DATA SET CMNSUP.CMN53.PANELS NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Updating a work area from a stream (demonstration)
This Dimensions CM demonstration shows you how to update a work area from a stream, restrict the update to specific folders in the stream, and exclude files from the update.
Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes
Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision

Additional Assistance

  • Submit a Case Online
  • FAQs