ERROR
Under the Full Checking technique, use the ERROR option to control how PCP reports errors:
- Number of errors to print
- Type of errors to print
- Number of occurrences of slack bytes greater than seven reported
- Number of occurrences of logical parent segments without logical child segments reported
This option allows you to tailor the reporting of errors and warnings in your environment. For example, if logical parent segments without logical child segments in a database represent a problem for the database application, you could set the ERROR option to report these occurrences. For another database, however, logical parent segments without logical child segments are acceptable, so you could set the ERROR option to ignore these occurrences.
IMS never reuses slack bytes until the database is reorganized. If you have extreme DASD space constraints, you can use the ERROR option to obtain the location of slack bytes greater than seven and zap them. The criteria is seven bytes because IMS marks any space larger than seven bytes as a free space element when these bytes are released by a delete/replace call. Free space elements are reusable. Repetitive delete/replace calls to the same location can cause the slack bytes greater than seven condition.
Uses | You can set the ERROR option at the following levels:
|
---|---|
ISPF panel field | Error Options
|
PCPSYSIN keyword | ERROR(nnnn,type,slack,parent) |
Values | Specify one or more of the following positional values. If you omit a value, code a comma to indicate the omission.
|
Default | 100,P,0,0 |
Example | The following example tells PCP to print up to 500 errors, to report both errors and warnings, and omit detail about warnings. PCP uses the default limits on slack byte and logical parent messages. ERROR(500,A) The following example tells PCP to print details up to 32767 occurrences of slack bytes greater than seven: ERROR(,A,9999) |