ERROR-121 | ERROR-122 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-128 | ERROR-129 | ERROR-130 | ERROR-131 | ERROR-132 | ERROR-133 | ERROR-134 | ERROR-135 | ERROR-136 | ERROR-137 | ERROR-138 | ERROR-139 | ERROR-140 | ERROR-141 | ERROR-142 | ERROR-143 | ERROR-145 | ERROR-146 | ERROR-147 | ERROR-148 | ERROR-149 | ERROR-150 | ERROR-151 | ERROR-152 | ERROR-153 | ERROR-154 | ERROR-155 | ERROR-156 | ERROR-157 | ERROR-158 | ERROR-159 | ERROR-160 | ERROR-161 | ERROR-162 | ERROR-163 | ERROR-164 | ERROR-165 | ERROR-166 | ERROR-167 | ERROR-168 | WARN-001 | WARN-002 | WARN-003 | WARN-004 | WARN-005 | WARN-006 | WARN-007 | WARN-008| ERROR-121 | Invalid value for parameter TIMEZONE. TIMEZONE must be set to MACHINE, LOCAL, or an integer value in the range -23 to +23. When entering + OR -, enclose the number in single quotes. e.g. TIMEZONE='+5' |
| Explanation |
An invalid value was specified for the TIMEZONE parameter. |
| Action |
Supply the correct parameter value and rerun the ADAWRK job. |
| ERROR-122 | Invalid value for parameter CHECKPOINT. Must be set to YES or NO. |
| Explanation |
An invalid value was specified for the CHECKPOINT parameter. |
| Action |
Supply the correct parameter value and rerun the ADAWRK job. |
| ERROR-124 | Invalid value for parameter FORCE. Must set to YES or NO. |
| Explanation |
An invalid value was specified for the FORCE parameter. |
| Action |
Supply the correct parameter value and rerun the ADAWRK job. |
| ERROR-125 | Invalid value for parameter REPLICATION. Must be set to YES, NO, DETAIL or FULL. |
| Explanation |
An invalid value was specified for the REPLICATION parameter. |
| Action |
Supply the correct parameter value (from those listed in the message) and rerun the ADAWRK job. |
| ERROR-126 | Invalid value for parameter REPORTFILE. Must be set to YES or NO. |
| Explanation |
An invalid value was specified for the REPORTFILE parameter. |
| Action |
Supply the correct parameter value and rerun the ADAWRK job. |
| ERROR-127 | Invalid value for parameter SUMMARY. Must be set to YES or NO. |
| Explanation |
An invalid value was specified for the SUMMARY parameter. |
| Action |
Supply the correct parameter value and rerun the ADAWRK job. |
| ERROR-128 | Invalid value for parameter TRANSACTIONS. Must be set to YES, NO or FULL. |
| Explanation |
An invalid value was specified for the TRANSACTIONS parameter. |
| Action |
Supply the correct parameter value and rerun the ADAWRK job. |
| ERROR-129 | Invalid value for parameter FILES. File number provided must be > 0 and < 65536. |
| Explanation |
An invalid value was specified for the FILES parameter. |
| Action |
Supply a file number in the correct range and rerun the ADAWRK job. |
| ERROR-130 | Invalid range for parameter FILES. When file range provided, VALUE1 < VALUE2. |
| Explanation |
An invalid value was specified for the FILES parameter. |
| Action |
Ensure that when providing a range of file numbers the first value (VALUE1) is less than the second value (VALUE2), then rerun the ADAWRK job. |
| ERROR-131 | IOR cccc call failed return code rc |
| Explanation |
An internal call failed. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-132 | Cannot identify Work data sets as no Work data sets were provided in the JCL and NOPPT was specified |
| Explanation |
ADAWRK was unable to find Work data sets. |
| Action |
Either include statements for the Work data sets in the JCL or remove the NOPPT parameter. |
| ERROR-133 | TIMESTAMP mismatch on Work data set |
| Explanation |
ADAWRK detected inconsistent timestamps in the Work data set provided. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-134 | Work data set dsn has wrapped |
| Explanation |
ADAWRK detected that the Work data set has wrapped and that old protection data has been overwritten. The Work data set name (dsn) is given in the message. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-135 | While processing a non cluster Work, a cluster nucleus Work block was found |
| Explanation |
While processing a Work data set from a non-cluster nucleus, ADAWRK detected a work block that originated from a cluster nucleus. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-136 | While processing a cluster Work data set, a non cluster nucleus Work block was found |
| Explanation |
While processing a Work data set from a cluster nucleus, ADAWRK detected a work block that originated from a non-cluster nucleus. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-137 | Work block size value longer than Work block size |
| Explanation |
While processing a Work data set, ADAWRK detected a work block with a size indicator greater than the block size of the work block. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-138 | Invalid version in Work block |
| Explanation |
While processing a Work data set, ADAWRK detected a work block with a version number that is not supported. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-139 | Invalid database ID in Work block |
| Explanation |
While processing a Work data set, ADAWRK detected a work block with a different database ID. |
| Action |
Ensure that you have not mixed the Work files you are passing to ADAWRK. |
| ERROR-140 | Invalid timestamp in Work block |
| Explanation |
While processing a Work data set, ADAWRK detected a work block with an invalid timestamp. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-141 | Invalid HSI record in Work block |
| Explanation |
While processing a Work data set, ADAWRK detected a work block with an invalid HSI record. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-142 | Cluster nucleus Work data set time stamps did not occur in chronological order |
| Explanation |
While processing a cluster Work data set, ADAWRK detected timestamps that are not in the correct order. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-143 | No recovery data found on provided Work data sets |
| Explanation |
While processing the specified Work data sets, ADAWRK was unable to detect any recovery data. |
| Action |
Ensure that you have not mixed the Work files you are passing to ADAWRK. |
| ERROR-145 | Work data set has wrapped |
| Explanation |
The Replication Restart Point was not found on the Work data set(s) provided. Replication information may have been lost. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-146 | Invalid nucleus ID in Work block |
| Explanation |
While processing the Work data set, an invalid nucleus ID was detected. |
| Action |
Ensure that you have not mixed the Work files you are passing to ADAWRK. |
| ERROR-147 | Userid cannot exceed 8 bytes |
| Explanation |
A user ID longer than eight bytes was specified when providing a user ID to be used for selecting transactions. |
| Action |
Correct the user ID and resubmit the job. |
| ERROR-148 | Missing Work data set entry in PPT block |
| Explanation |
When processing the PPT block in the specified Associator data set, a missing entry was detected. |
| Action |
Contact your Software AG technical support representative for assistance. |
| ERROR-149 | Invalid WORK part 1b header block for nucleus ID id |
| Explanation |
While processing a Work data set, ADAWRK detected an invalid work block part 1b header for WORK data set from nucleus with nucleus ID = id. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-150 | Insufficient workpool space for buffers |
| Explanation |
ADAWRK encountered a shortage of space in the Work pool during execution. |
| Action |
Check JCL, increase region size, and resubmit the job. If the problem persists, contact your Software AG technical support representative for assistance. |
| ERROR-151 | I/O error reading a Work data set |
| Explanation |
ADAWRK encountered an I/O error reading a Work data set. |
| Action |
Review the additional error message accompanying this message and rectify the problem. Then resubmit the job. |
| ERROR-152 | I/O error reading PPT |
| Explanation |
ADAWRK encountered an I/O error reading the PPT. |
| Action |
Review the additional error message accompanying this message and rectify the problem. Then resubmit the job. |
| ERROR-153 | Inconsistent Work data sets provided |
| Explanation |
ADAWRK detected inconsistencies in the Work data sets provided. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-154 | Parameter LWP must be specified in Kb, e.g. LWP=512K |
| Explanation |
The value provided for the LWP parameter must be specified in kilobytes. |
| Action |
Provide a value for LWP in kilobytes and try again. |
| ERROR-155 | Parameter LWP error : must be between 100K and 1048576K |
| Explanation |
The value provided for the LWP parameter is not in the correct range. |
| Action |
Provide a value for LWP in the correct range and try again. |
| ERROR-156 | Parameter error(s) detected |
| Explanation |
This message appears when errors have been detected in parameter processing. |
| Action |
Messages indicating which parameters are in error will have been issued earlier. Refer to these other error messages to resolve the issue. Then try again. |
| ERROR-157 | No space in Work pool to satisfy request Please review the settings of the LWP parameter |
| Explanation |
An internal ADAWRK storage request has failed. |
| Action |
Consider increasing the setting of the ADAWRK LWP (length of Work pool) parameter. If this does not resolve the issue, contact your Software AG technical support representative for assistance. |
| ERROR-158 | All Work data sets for nuclei referred to in Work-part-1 data not provided |
| Explanation |
Records have been detected in the Work part 1 data referring to clustered nuclei, but the work data sets for the other nuclei have not been provided as input to ADAWRK in JCL. Inconsistent ADAWRK output may result. |
| Action |
Ensure that all Work data sets for all component nuclei of the cluster are included as input to ADAWRK. Then try again. |
| ERROR-159 | Invalid value for parameter FILES. File number specified more than once. |
| Explanation |
The same file number has been specified more than once in the ADAWRK FILES parameter. This is invalid. |
| Action |
Correct the parameter and try again. |
| ERROR-160 | More than one Replication Data Begin Record received. |
| Explanation |
More than one internal replication begin record was encountered during ADAWRK processing. |
| Action |
Contact your Software AG technical support representative for assistance. |
| ERROR-161 | Missing WRKC for Replication ID record |
| Explanation |
An internal error has occurred when ADAWRK was processing a replication-related protection record. ADAWRK skips this protection record and continues processing, but its replication report may become inaccurate. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-162 | Missing WRKC for Replication RDI record |
| Explanation |
An internal error has occurred when ADAWRK was processing a replication-related protection record. ADAWRK skips this protection record and continues processing, but its replication report may become inaccurate. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-163 | Missing WRKC for Replication RDB record |
| Explanation |
An internal error has occurred when ADAWRK was processing a replication-related protection record. ADAWRK skips this protection record and continues processing, but its replication report may become inaccurate. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-164 | Missing WRKU for Replication RDB record |
| Explanation |
An internal error has occurred when ADAWRK was processing a replication-related protection record. ADAWRK skips this protection record and continues processing, but its replication report may become inaccurate. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-165 | Unexpected response code rc subcode sc |
| Explanation |
An unexpected Adabas response code has occurred when ADAWRK was opening, validating or traversing a Work data set. The response code and associated subcode are shown. ADAWRK stops processing. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-166 | Partially written block in WORK Part 1 extension NUCID=id, RABN=nnnnnn |
| Explanation |
While processing a Work data set, ADAWRK detected an invalid block in the Work part 1 extension (RABN=nnnnnn) on the Work data set of the nucleus with nucleus NUCID id. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-167 | PLOG record internal nucid > 32 |
| Explanation |
A protection record on a Work data set contains an invalid internal NUCID. ADAWRK stops processing. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| ERROR-168 | Inconsistency in WORK Part 1 extension NUCID=id |
| Explanation |
While processing a Work data set, ADAWRK detected an inconsistent block in the Work part 1 extension on the Work data set of the nucleus with NUCID id. |
| Action |
Contact your Software AG technical support representative with the details of this message. |
| WARN-001 | A timestamp was encountered reading the Work data sets indicating that ADAWRK is running against a running Adabas nucleus. ADAWRK will continue. |
| Explanation |
ADAWRK detected that the Work data sets it is reading are being used by an active database. |
| Action |
No action is required for this informational message. |
| WARN-002 | Flush point values not established |
| Explanation |
While processing the specified Work data sets, ADAWRK was unable to determine the flush point. |
| Action |
No action is required for this informational message. |
| WARN-003 | End of buffer flush values not established |
| Explanation |
While processing the specified Work data sets, ADAWRK was unable to determine the end of buffer flush point. |
| Action |
No action is required for this informational message. |
| WARN-004 | Start of buffer flush values not established |
| Explanation |
While processing the specified Work data sets, ADAWRK was unable to determine the start of buffer flush point. |
| Action |
No action is required for this informational message. |
| WARN-005 | Backward repair point values not established |
| Explanation |
While processing the specified Work data sets, ADAWRK was unable to determine the backward repair point. |
| Action |
No action is required for this informational message. |
| WARN-006 | Work data set dsn found in PPT but not provided to ADAWRK. |
| Explanation |
The PPT refers to a Work data set that has not been provided as input to ADAWRK in JCL. It may be that the data set has been omitted in error. Inconsistent ADAWRK output may result. |
| Action |
If the data set was not intentionally excluded from the run, include the relevant data set as input to ADAWRK. Then try again. |
| WARN-007 | Work data set dsn not found in PPT but provided to ADAWRK |
| Explanation |
The PPT does not refer to a Work data set that has been provided as input to ADAWRK in JCL. It may be that the data set has been included in error. Inconsistent ADAWRK output may result. |
| Action |
If the data set was not intentionally included from the run, remove the relevant data set as input to ADAWRK. Then try again. |
| WARN-008 | Work data set for nucleus that triggered the last buffer flush not provided |
| Explanation |
The Work data set for the nucleus that triggered the last buffer flush has not been provided as input to ADAWRK in JCL. Inconsistent ADAWRK output may result. |
| Action |
If the data set was not intentionally excluded from the run, include the relevant data set as input to ADAWRK. Then try again. |