TOLERATE_CONFIG_ERRORS Statement

Read syntax diagramSkip visual syntax diagram TOLERATE_CONFIG_ERRors YesNo

Purpose

Use the TOLERATE_CONFIG_ERRORS statement to mark sections of the system configuration file that must be without errors when CP processes them.

How to Specify

Include as many statements as needed; they are optional. You can place TOLERATE_CONFIG_ERRORS statements anywhere in the system configuration file.

If you do not specify any TOLERATE_CONFIG_ERRORs statements, CP will tolerate errors in your system configuration file.

The first statement you specify must be TOLERATE_CONFIG_ERRORS NO. All subsequent statements must alternate between YES and NO. You cannot have two TOLERATE_CONFIG_ERRORS statements in a row with the same operand. That is, you cannot tell CP to tolerate errors, process a few more statements, and then tolerate errors again.

Operands

Yes
tells CP to begin tolerating errors in the system configuration file.
No
tells CP not to tolerating any errors in the system configuration file until encountering a TOLERATE_CONFIG_ERRORS YES statement.

Usage Notes

  1. When CP finds an error in a system configuration file statement that follows a TOLERATE_CONFIG_ERRORS NO statement, it remembers the error occurrence and, after displaying all the errors encountered, prompts the operator with a question. The operator can respond to the question in one of the following ways:
    • Stopping the IPL process
    • Continuing with the normal IPL process
    • Continuing with the normal IPL process but not automatically logging on any virtual machines.
  2. If CP does not find any errors while processing the system configuration file or if all errors found are in sections of the system configuration file where TOLERATE_CONFIG_ERRORS YES is in effect, the normal IPL process continues.
  3. If you are using the IMBED and the TOLERATE_CONFIG_ERRORS statements, remember that CP processes the statements in an imbed file as if those statements were included in the master system configuration file. If you are not tolerating errors in the master file and then repeat the statement in the imbedded file, CP will flag the duplicate statement in the imbedded file as an error.
  4. If you change a system configuration file, you should run the CPSYNTAX exec to make sure there are no syntax errors in the system configuration file.

Examples

  1. To tell CP not to ignore any syntax problems found in the processing of the CP_OWNED statements, use the following TOLERATE_CONFIG_ERRORS statements: 
      Tolerate_Config_Errors  no             /* Don't Ignore errors here */
   CP_Owned  Slot 1 ESARES
   CP_Owned  Slot 2 ESAP01
   CP_Owned  Slot 3 ESAP02
   CP_Owned  Slot 4 ESAP03
   CP_Owned  Slot 5 ESAP04
   CP_Owned  Slot 6 ESAP05
   Tolerate_Config_Errors  yes     /* Back to normal mode      */
  2. To make sure CP does not ignore any errors when defining your checkpoint and warm start areas, use the following TOLERATE_CONFIG_ERRORS statements: 
      Tolerate_Config_Errors  no             /* Don't Ignore Any Errors in */
                                         /* the System Residence Stmt  */
  System_Residence,
     CheckPoint  VolID  esares  From  Cylinder  784  For  9,
     WarmStart   VolID  esares  From  Cylinder  568  For  9
  Tolerate_Config_Errors  yes           /* From here on, errors are OK */