═══ 1. C Messages ═══

Expand this Table of Contents entry to access the general help for messages 
used in C/C++. The information provided in these help entries will not be 
relevant unless accessed from messages provided by C/C++ tokenizer. 


═══ 1.1. Help for CLE0011I ═══

Explanation: The help index support module specified could not be accessed. 

Response: If the problem persists, copy the module from another workstation to 
a directory specified by the LIBPATH environment variable in your CONFIG.SYS 
file, or reinstall the product on your workstation. 


═══ 1.2. Help for CLE0014I ═══

Explanation: The C/C++ tokenizer was called with an unknown option. 

Response: Ensure that changes made to the language profile (the ".LXL" file) 
are valid. If the problem persists, copy the profile from another workstation, 
or reinstall the product on your workstation. 


═══ 1.3. Help for CLE0015I ═══

Response: Close all unnecessary windows and applications and try again. 


═══ 1.4. Help for CLE0016I ═══

Response: Close all unnecessary windows and applications and try again. 


═══ 1.5. Help for CLE0017I ═══

Explanation: The language profile (the ".LXL" file) could not be loaded. 

Response: Ensure that changes made to the language profile are valid. If the 
problem persists, copy the profile from another workstation, or reinstall the 
product on your workstation. 


═══ 1.6. Help for CLE0018I ═══

Response: Ensure that the specified LSX file is installed on your workstation. 


═══ 1.7. Help for CLE0019I ═══

Explanation: The specified LSX file may have been damaged. 

Response: Retry the operation. If the problem persists, copy the LSX file from 
another workstation, or reinstall the product on your workstation. 


═══ 1.8. Help for CLE0020I ═══

Explanation: The specified LSX file could not be successfully updated. The LSX 
file will not be updated. 

Response: Ensure that: 

 The specified LSX file is installed on your workstation. 
 The language definition file is not marked as read-only (see your OS/2 
  manual). 
 There is sufficient free space in the directory to allow the write operation. 
If the problem persists, copy the LSX file from another workstation, or 
reinstall the product on your workstation.