Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML No log record written when install fails in CMN21 rather than CMN20
We changed install job CMN21 bind failure to work like CMN20I install failure. On an "ALL" site, failure executes CMNBATCH transaction 99 with FUN=21 at the "ALL" site. This transaction notifies the package creator of the bind failure.
CMS-XML Long name transactions not being logged for forward recovery
The use of long name components (greater than 8 characters) is not writing recovery records to CMNELLOG. In the event of a restore of the component master using forward recovery, the long name component activity is not restored.
CMS-XML S0C7 abend occurs in SERDATES at OFFSET 222, when CMNDELAY processes "CMNDELAY - ****000000 95 AGEI" transaction.
If the housekeeping job is run while the ZMF task is down, so that the transaction are written to the delay file and processed by CMNDELAY when the task is brought up, the following S0C7 abend occurs, if all applications (****920=Y for SYSIN) are processed. If only 1 application is processed the abend does not occur.
CMS-XML Unexplained message/CMNBATCH type 95 transaction produced during housekeeping
This is related to but not identical to the problems documented under DEF92801/DEF170355. They are dealing with the potential impact of these transactions being written to the delay file.
CMS-XML CMNBATCH and CMNDELAY fail to update calendar and incorrect message is issued.
When CMN930 transactions are processed by CMNBATCH the following CMNVRLIO messages are written to the SERPRINT dd in the task and the calendar is not updated: If task is down when CMNBATCH runs, the following are issued when CMNDELAY processes the records. CMNE464I CMNVRLIO VCA=0B6A9000,USER=SERVDLAY,Active Lock..: ....0000000000000000,TTOK=00000000
CMS-XML CMN37 job not submitted if RIPPLIA ends with RC=6
If the started task is down when the CMN30 job is running, the RIPPLIA step will receive a RC=6, log the CMN37 job to the delay file, and both the SUCCESS and FAILURE steps will flush. When the task is started the 37 job will not be submitted since the sysin submit transactions were written as x'06' not x'05'.
In ISPF there is an edit profile characteristic called RECOVERY which acts to save edit transactions that occur during the ISPF session when RECOVERY is turned on. The edit transactions can be automatically reapplied to the last saved version of the edit data to reconstruct the edit session up to the point where it was disrupted. However, the edit session can only be reconstructed up to the last time the ENTER or any PF key was used.
CMS-XML Component history not aging if multiple reports run in CMNBAT10 step
The distributed REPORTS2 member in the CNTL library implies that multiple reports can be executed in the same step. However, if a CMN920 report is followed by a CMN930 in the same CMNBAT10 SYSIN dataset no component history aging or deletion records are written to the AGETRANS/&&AGETX dataset when the job is executed. Package master data aging transactions are written to the file along with the calendar synchronisation transactions .
CMS-XML New Features in ChangeMan ZMF 8.2 Patch 3
This transaction notifies the package creator of the bind failure. This transaction has also been changed to write a log record with type=02 (install), package= package name
CMS-XML CMNDELAY File Serialization; enhancement delivered in ZMF and 7.1.1
CMNBATCH attempts to connect to the ZMF started task to process status updates. If the attempt to connect fails, then CMNBATCH writes transactions to the delay file, which is processed the next time ZMF is started.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs