ADARPE Utility Messages

#### Search Results

Search

# ADARPE Utility Messages

### Overview of Messages

`ERROR-121 | ERROR-122 | ERROR-123 | 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-121 | EXTRACT=name: Value must be set to YES or NO for parameter parmname
Explanation | The setting of parameter parmname in extract name is not valid. Valid settings are YES or NO.
Action | Correct the parameter and try again.

ERROR-122 | EXTRACT=name: Parameter IMAGE must be set to BI, AI or BOTH.
Explanation | The value of the IMAGE parameter has been incorrectly specified in extract name.
Action | Correct the parameter and try again.

ERROR-123 | EXTRACT=name: Parameter TRANSACTIONLEVEL must be set to NONE, RECORD, or TRANSACTION.
Explanation | The value of the TRANSACTIONLEVEL parameter has been incorrectly specified in extract name.
Action | Correct the parameter and try again.

ERROR-124 | EXTRACT=name: Parameter MODIFICATIONTYPE must be a selection of INSERT/UPDATE/DELETE/ISTATE/ALL.
Explanation | The value of the MODIFICATIONTYPE parameter has been incorrectly specified in extract name.
Action | Correct the parameter and try again.

ERROR-125 | OUTPUTFILE=file has been specified in EXTRACT=name1, and EXTRACT=name2.
Explanation | The OUTPUTFILE parameter for two different extracts refers to the same output file. They must be unique.
Action | Correct the OUTPUTFILE parameter and try again.

ERROR-126 | type failure on {outputfile|outputexit}={filename|exitname} for EXTRACT=name, RC=rc
Explanation | A close, open, write, delete, or load (type) failure occurred for the output or exit file listed in the message. The name of the extract and the return code from processing are also given in the message.
Action | Correct the JCL or parameters and try again.

ERROR-127 | type failure by User Exit=exitname for EXTRACT=name, RC=rc User Exit error code=errorcode
Explanation | An initialize, terminate, or processing (type) error occurred for the user exit named in the message. The name of the extract and the return and error codes from processing are also given in the message.
Action | Correct the JCL or parameters and try again.

ERROR-128 | When TRANSACTIONLEVEL=TRAN or RECORD is specified, both MERGIN1 and MERGIN2 must be present, and must be the same type of file with the same or a larger record size as the CLOG input file
Explanation | When TRANSACTIONLEVEL parameter is set to "TRAN" or "RECORD", the MERGIN1 and MERGIN2 data sets are required. They must be the same file type and their record sizes must be at least as large (or larger) as the CLOG input file.
Action | Correct the JCL or parameters and try again.

ERROR-129 | The combination of PAYLOADDATA=YES, PAYLOADPREFIX=NO, and RECORDPREFIX=YES is invalid.
Explanation | An invalid combination of parameters was specified.
Action | Correct the parameters and try again.

ERROR-130 | Failure on writing to PRINT file. Consult Software Support.
Explanation | A failure occurred writing to the PRINT file. Additional messages should be present.
Action | Examine the additional messages and see if you can resolve the problem. If the problem persists, contact your Software AG technical support representative.

ERROR-131 | Open failed for file DDCLOG with returned code of rc
Explanation | An attempt to open the DDCLOG file failed. The return code of the attempt is given in the message.
Action | Correct the JCL or parameters and try again.

ERROR-132 | Invalid parameters supplied
Explanation | The specified parameters are not valid.
Action | Examine the additional message to fully identify the problem. Then correct the JCL or parameters and try again.

ERROR-133 | A record that was not a V52 or V8 CLOG record was encountered
Explanation | The input file for the CLOG appears corrupted or incorrect.
Action | Correct the JCL or parameters and try again. If the problem persists, contact your Software AG technical support representative.

ERROR-134 | NAME parameter is required for EXTRACT
Explanation | No value was supplied for the NAME parameter (the extract name). A value for this parameter is required in an ADARPE run.
Action | Supply a NAME parameter setting and try again.

ERROR-135 | NAME=name is not unique across EXTRACTs.
Explanation | The name specified for an extract is not unique; the same name was specified for different extracts. Extract names must be unique.
Action | Specify a unique name for the extract and try again.

ERROR-136 | Specified destinations are not unique.
Explanation | The same destination was specified more than once. Destinations listed in an individual DESTINATIONS parameter must be unique.
Action | Correct the destination list and try again.

ERROR-137 | Specified subscriptions are not unique.
Explanation | The same subscription was specified more than once. Subscriptions listed in an individual SUBSCRIPTIONS parameter must be unique.
Action | Correct the subscription list and try again.

ERROR-138 | OUTPUTFILE parameter is required for EXTRACT.
Explanation | No value was supplied for the OUTPUTFILE parameter. A value for this parameter is required in an ADARPE run.
Action | Supply an OUTPUTFILE parameter setting and try again.

ERROR-139 | At least one EXTRACT must be specified.
Explanation | No EXTRACT parameter was specified. At least one EXTRACT parameter is required in an ADARPE run.
Action | Supply an EXTRACT parameter and try again.

ERROR-140 | Parameters specified require parameter TRANSACTIONLEVEL=RECORD
Explanation | When the EXTRACT parameter is specified `TRANSACTIONLEVEL=RECORD` must also be specified.
Action | Specify the `TRANSACTIONLEVEL=RECORD` parameter and try again.

ERROR-141 | Parameters specified require parameter TRANSACTIONLEVEL=TRAN
Explanation | When the EXTRACT parameter is specified `TRANSACTIONLEVEL=TRAN` must also be specified.
Action | Specify the `TRANSACTIONLEVEL=TRAN` parameter and try again.