Find Answers

Filter Search Results
All Products:

Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML "CMN2650I - Unable to allocate" is issued when a component is staged (without edit) for the second time, and "ELIMINATE SAVE TO PERSONAL LIB" is set to "NO" and "ALLOW CHECKOUT TO PERSONAL LIB." is set to "YES".
"CMN2650I - Unable to allocate" is issued when a component is staged (without edit) for the second time, and "ELIMINATE SAVE TO PERSONAL LIB " is set to "NO" and "ALLOW CHECKOUT TO PERSONAL LIB." is set to "YES".
CMS-XML Save previous version when staging programs using function "S"
This is being raised as it is a change in behaviour in ZMF 7.1 as it does not accur in ZMF 6.1. First of all you need to make sure that for the library type you are testing with is in the Application Admin\Library Types you have the following set for this particular lib type. SAVE STAGING VERSIONS ===> PROMPT ALWAYS/NONE/PROMPT
CMS-XML 0C4-11 HPSVINIT+A36 using SSV after coversion from PDS to PDSE staging libs
The user gets the following messages: CMN8711I - Save staging version error; Function = 7, Reason code = Abend. CMN8711I - Save staging version error; Function = CREATE , Reason code = DOWN
CMS-XML Application Admin - Incorrect Info displayed in General Parameters
Overlay prior staged module: ECP shows Disabled, ZMF specifies YES Link Package: ECP shows Disabled, ZMF specifies Yes Save to personal and staging libraries : ECP shows Enabled, ZMF specifies No
CMS-XML Attempt to edit HFS component presents empty edit session
ELIMINATE SAVE TO PERSONAL LIB ===> NO The component can be browsed without problems and components staged when 'ELIMINATE SAVE TO PERSONAL LIB ===> YES' can be successfully edited in the package.
CMS-XML CMN8711I - Save staging version error; Function = 8, Reason code = 0018.
CMN8711I - Save staging version error; Function = 8, Reason code = 0018. STAGING LIBRARY DELETED DUE TO AGING. CMAN.Q.STG.DEMO.#000001.LDG STAGING LIBRARY DELETED DUE TO AGING. CMAN.Q.STG.DEMO.#000001.LSA
CMS-XML Bad records being written to the package master or recovery file
I'm seeing a pattern in the package master in that occassionaly for whatever reason a user will create a package get hungup and never get a package # assigned. that is the staging libraries get allocated on the mainframe but thats it. if you query this package # in CHANGEMAN its not there.
CMS-XML Recompile SYSLIB incorrect for participating packages with read-only TSOID
When you recompile into a participating package, the staging libraries from the other packages in the complex are included in the SYSLIB DD in the WRITE step. However, if the TSOID of the user doesn't have read access to an application, that application's libraries will not be included in the SYSLIB.
CMS-XML 'Edit' Command from 'View' Mode Causes Source-to-Load Integrity if Audit not run
When editing a source component from the ‘VIEW’ mode of another source component in the same package it is possible to save the edited source member in the staging library without forcing a re- stage of the component. This results in a source member in a package being different than the load module (source-to-load integrity issue). Audit will catch this issue with a SYNCH11, but not for customer sites that do not require an audit to be run.
CMS-XML ZMF4ECL: Smart editor fails after timeout/automatic reconnection
A customer is reporting that if a ZMF4ECL Smart Editor session is started and times out (e.g. SDNOTIFY/TIMEOUT=M45) subsequent efforts to save the content to the staging library fail. The transient edit dataset is updated but the contents are never copied back to the staging dataset. A 'Data Set ENQ unavailable' message is issued.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs