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 Attempt to memo delete a package throws user out of ZMF session
Attempt to memo delete a package throws user out of ZMF session
CMS-XML Can not Memo Delete Promoted Packages on P Site.
Can not Memo Delete Promoted Packages on P Site.
CMS-XML Memo deleted participating packages are not removed from the COMPLEX package.
Memo deleted participating packages are not removed from the COMPLEX package.
CMS-XML CMNBATCH ends with RC=12 during housekeeping when memo delete last pkg in PMAST
CMNBATCH ends with RC=12 during housekeeping when memo delete last pkg in PMAST
CMS-XML v712 pf3 out of MEMO DELETE hung
v712 pf3 out of MEMO DELETE hung
CMS-XML Memo Delete and Demote inconsistency between ZMF4ECL and ZMF.
Memo Delete and Demote inconsistency between ZMF4ECL and ZMF.
CMS-XML Insufficient warning when large packages are incompletely deleted by CMNBATCH.
If a package has more than 2048 records in the package master file, a memo delete may not delete all the records. A record lock table used by CMNBATCH has 2048 slots and all records must be locked at once. If the started task is running when the CMNBATCH program executes to delete this package the following errors may show in the SERPRINT and the task may hang:
CMS-XML Deleted HFS packages or components leaving related information in component master file
When packages containing HFS components are memo deleted and then subsequently removed by housekeeping it appears that a significant amount of information related to the HFS components is retained in the component master dataspace. This would appear to be redundant data that needs cleaning up. The same data does not appear to be retained for non-HFS components (although it may simply be that it is better hidden or formatted differently).
CMS-XML Houskeeping run on P Site, incorreclty deletes DP Site staging datasets.
Housekeeping run on P Site, incorrectly deletes DP Site staging datasets, when a package has been installed, backed out and then memo deleted on the P site.
CMS-XML Failed attempt to delete TT4ZMF package ejects user from ISPF interface
When a user attempts to memo delete a package using the CMN ZMF ISPF interface and they receive the following error message the package is not deleted and the user is ejected from the ISPF interface: CMN5000I SER0063W - HTTP server did not respond Their system is using a TT4ZMF Control Level of 1 (No Control) and if the SBM server is completely unavailable in this scenario then the request is processed in the correct manner.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs