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 CMNEX021 to bypass SYNCHs
CMNEX021 to bypass SYNCHs
CMS-XML CMNEX021 is not working properly when the package status is OPN.
CMNEX021 is not working properly when the package status is OPN.
CMS-XML CMNEX021 X21£STAT field not being set correctly when autoresolve enabled
CMNEX021 X21£STAT field not being set correctly when autoresolve enabled
CMS-XML SYNCH19 is not being bypassed by CMNEX021
SYNCH19 is not being bypassed by CMNEX021
CMS-XML CMNEX021 and participating packages
CMNEX021 and participating packages
CMS-XML CMNEX021 not bypassing Like-P HFS lib types.
CMNEX021 not bypassing Like-P HFS lib types.
CMS-XML CMNEX021 to bypass SYNCH1 on Audit report produces ‘garbage’ in copybook baseline ISPF statistics
CMNEX021 to bypass SYNCH1 on Audit report produces ‘garbage’ in copybook baseline ISPF statistics
CMS-XML Inconsistent field contents passed to CMNEX021 when called from CMNAD000 and CMNAD500
Inconsistent field contents passed to CMNEX021 when called from CMNAD000 and CMNAD500
CMS-XML V5.5.0 - CMNEX021 SYNCH5 bypass logic is NOT working
V5.5.0 - CMNEX021 SYNCH5 bypass logic is NOT working
CMS-XML When CMNEX021 is used to bypass SYNCH9, a SYNCH12 is incorrectly reported.
When CMNEX021 is used to bypass SYNCH9, a SYNCH12 is incorrectly reported.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs