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 The important connection between CMNWRITE and Audit
The ISIC record, which contains source to copy information for a component, is built by CMNWRITE. This record is used during audit to determine SYNCH 5/ SYNCH 15 / SYNCH 16 errors. If the stage process for a source component does not include CMNWRITE, or CMNWRITE returns a non-zero return code, then no ISIC record is built.
CMS-XML Complex package audit reporting copybook picked up from incorrect package and potentially missing error situation
If copybook components are moved around between different participating packages within the same complex/super package, inconsistent information can be returned by the audit report. Incorrect package names and ISPF stats can show up in the report. Importantly potential SYNCH 4! or SYNCH 15 ! errors can also be missed.
CMS-XML Audit and LCT components
Currently Audit does not review the LCT cards if they exist in the package by themselves. If the package also contains the corresponding SRC, then it will see the change to the LCT card (the deleted INCLUDE) and flag a synch 15 . There might be plans to change this in the future, but for now customers need to remember to checkout the SRC or relink the LOD.
CMS-XML How can you improve audit performance?
2. Activate CMNEX031 to exclude selected component library types from audit. 3. Activate CMNEX021 to exclude promotion libraries from audit for SYNCH 15 . 4. Activate CMNEX022 to exclude selected components from audit.
CMS-XML What problems can occur when you run audit against an out-of-date Impact Analysis file?
It is important that this relationship information be current, since the audit process uses the data during out-of-synch processing. Any synch errors that are based on component relationships are suspect if your Impact Analysis data is out-of-date. Some specific synch errors that can be impacted are SYNCH 5, SYNCH 8, SYNCH 15 , and SYNCH 16.
CMS-XML Parsing baselines in audit
Audit still reads the baseline library directories for SPF stats for non-load components, and link-edit attributes (including SSI) for load components. This process has been buffered to make it faster. And we still read the like-copy staging libraries for hashing to determine SYNCH 15 s.
CMS-XML Duplicate components in participating packages within the same complex or super package
When auditing a package, customers may see different package numbers generated in the audit report for various errors based on the sequence that the participating packages are defined within the complex. For example, a SYNCH 15 ! error for a copybook that is resident in more than one participating package within the complex could be displayed as coming from any of the packages in which it resides.
MS-WORD ChangeMan ZMF Hilo Documentation Content and Notes
If CMNWRITE run a second (or third, etc.) time within a given compile, then the “OPT=CONTINUE” control card will automatically be added to CMNWRITE’s SYSIN DD to ensure that any new ISIC (source-to-copybook) records that are found during the second, third, etc. run of CMNWRITE will be saved into the master files for the source component being staged. This will ensure that SYNCH 4, SYNCH 5, SYNCH 15 , etc. will be generated as needed during Audit.
CMS-XML Dim10: Information on 'Request under work' field in the Windows Explorer Shell Extension Synchronization Wizard
You can see what the default request is in the "Working On" field of your desktop client views or in the project preferences. You can enter a different request id in the synchronization wizard if you wish, using the same syntax as anywhere else in Dimensions. (e.g. PAYROLL_CR_ 15 ).
CMS-XML SYNCH3 errors in Audit
SYNCH 3 errors in Audit
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Using multiple teams and multiple streams to perform parallel development (demonstration)
This demonstration shows you how to use multiple teams and multiple streams to perform parallel development in Dimensions CM.
Dimensions CM: A typical parallel development flow (animation)
This animation demonstrates a typical parallel development flow in Dimensions CM using multiple teams and multiple streams.

Additional Assistance

  • Submit a Case Online
  • FAQs