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:
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).
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.
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.
