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 Logical record lock table is full
Logical record lock table is full
CMS-XML Release installation filling logical record lock table
Release installation filling logical record lock table
CMS-XML Incorrect LOG records are being created for Lock/Unlock
Incorrect LOG records are being created for Lock /Unlock
CMS-XML Package backout STC CMN6435I CMNVRLIO .. ,Attempt to lock same record twice.
Package backout STC CMN6435I CMNVRLIO .. ,Attempt to lock same record twice.
CMS-XML CMN_303I CMNVRLIO VCA=2A636000,LOGICAL RECORD LOCK TABLE IS FULL
CMN_303I CMNVRLIO VCA=2A636000,LOGICAL RECORD LOCK TABLE IS FULL
CMS-XML Global parms locked - How to reset.
On occasion if your TSO gets logged off without shutting down cleanly whilst you are updating the ZMF Global Parms this can leave a lock on the Global Parm records so that others\you cannot edit them. Now if you try and go in again to option A.G.8 you will get a ‘GLOBAL PARMS IN USE’ message in the upper right of the screen and when you I hit PF1 it says:
CMS-XML CMNENTFY process does not update checkpoint date when global parms are locked
The CMNENTFY process runs in the ZMF Server started task and works by scanning the ZMF log file for all ZMF log records that have been generated since the last successful execution and sending them as events or transactions to the location specified in the NTFYURL parm When the process completes successfully a field is updated in the global admin general record (<eventNotifyCheckpoint
CMS-XML Attempts to lock or unlock any application in ISPF are failing
Attempts to lock or unlock any application (ISPF global admin option A.G.7/panel CMNGBULP) in a ZMF 8.1.4 environment here always results in the DEMO application being selected for processing. For example, I have not yet selected DEMO for any lock or unlock request and these are the log records that have been generated:
CMS-XML 7.1.2 XML service PACKAGE PRM_HIST LIST returns record with 19600101 date
In v7.1.2 when you run the XML service PACKAGE PRM_HIST LIST the first result record contains promotionLevel ‘00’, and promotionDate ‘19600101’ and promotionTime ‘000000’. The bogus entries were identified as promotion lock records . These have no date/time stamp, and no promotion level/name information.
CMS-XML User's ZMF session locks up, when using the UTILITY SCRATCH from Option 4.
While adding and/or removing scratch requests from a package from Build Option 4, using Options (1 Baseline) and (2 Package) from main Option (4 Utility), the user's session locks up and the following can be noticed in SERPRINT for the task. CMNB220I CMNVRLIO VCA=17C00000,USER=DHADDEN ,Attempt to lock same record twice CMNB220I CMNVRLIO VCA=17C00000,USER=DHADDEN ,Locked Read..: C8C1C4C40000074F0000
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs