Adabas Review 00xxx Messages

#### Search Results

Search

# Adabas Review 00xxx Messages

### Overview of Messages

`REV00MNF | REV00001 | REV00002 | REV00003 | REV00004 | REV00005 | REV00006 | REV00008 | REV00011 | REV00012 | REV00013 | REV00014 | REV00015 | REV0001 | REV00020 | REV00021 | REV00025 | REV00026 | REV0002 | REV00028 | REV00029 | REV00030 | REV00032 | REV00033 | REV00035 | REV00036 | REV00037 | REV00038 | REV00040 | REV00043 | REV00044 | REV00045 | REV00046 | REV00047 | REV00050 | REV00054 | REV00055 | REV00057 | REV00058 | REV00059 | REV00060 | REV00062 | REV00064 | REV00065 | REV00066 | REV00068 | REV00072 | REV00073 | REV00074 | REV00078 | REV00079 | REV00080 | REV00081 | REV00082 | REV00083 | REV00084 | REV00085 | REV00086 | REV00087 | REV00091 | REV00092 | REV00093 | REV00094 | REV00095 | REV00096 | REV00097 | REV00098 | REV00099 | REV00100 | REV00101 | REV00102 | REV00104 | REV00105 | REV00106 | REV00108 | REV00111 | REV00116 | REV00120 | REV00121 | REV00123 | REV00124 | REV00125 | REV00129 | REV00132 | REV00133 | REV00134 | REV00135 | REV00137 | REV00138 | REV00139 | REV00140 | REV00141 | REV00144 | REV00145 | REV00146 | REV00147 | REV00148 | REV00149 | REV00150 | REV00151 | REV00152 | REV00153 | REV00155 | REV00156 | REV00157 | REV00158 | REV00159 | REV00160 | REV00161 | REV00162 | REV00163 | REV00169 | REV00170 | REV00171 | REV00175 | REV00176 | REV0017 | REV00179 | REV00180 | REV00181 | REV00182 | REV00183 | REV00184 | REV00185 | REV00187 | REV00188 | REV00190 | REV00193 | REV00195 | REV00196 | REV00197 | REV00198 | REV00199 | REV00200 | REV00202 | REV00203 | REV00205 | REV00206 | REV00207 | REV00209 | REV00210 | REV00211 | REV00212 | REV00214 | REV00217 | REV00218 | REV00219 | REV00220 | REV00221 | REV00222 | REV00223 | REV00224 | REV00225 | REV00226 | REV00227 | REV00228 | REV00229 | REV00230 | REV00231 | REV00234 | REV00235 | REV00236 | REV00237 | REV00238 | REV00239 | REV00240 | REV00241 | REV00242 | REV00243 | REV00244 | REV00245 | REV00246 | REV00247 | REV00248 | REV00249 | REV00250 | REV00252 | REV00253 | REV00254 | REV00255 | REV00256 | REV00257 | REV00258 | REV00259 | REV00260 | REV00261 | REV00262 | REV00263 | REV00264 | REV00265 | REV00266 | REV00267 | REV00268 | REV00269 | REV00270 | REV00271 | REV00272 | REV00273 | REV00274 | REV00275 | REV00276 | REV00277 | REV00278 | REV00279 | REV00280 | REV00281 | REV00282 | REV00283 | REV00284 | REV00285 | REV00286 | REV00288 | REV00289 | REV00290 | REV00291 | REV00292 | REV00293 | REV00294 | REV00295 | REV00296 | REV00297 | REV00299 | REV00300 | REV00301 | REV00306 | REV00307 | REV00308 | REV00309 | REV00310 | REV00311 | REV00312 | REV00313 | REV00314 | REV00315 | REV00316 | REV00317 | REV00318 | REV00319 | REV00320 | REV00321 | REV00322 | REV00323 | REV00325 | REV00326 | REV00327 | REV00328 | REV00329 | REV00330 | REV00331 | REV00332 | REV00333 | REV00334 | REV00335 | REV00336 | REV00337 | REV00338 | REV00339 | REV00340 | REV00341 | REV00342 | REV00343 | REV00344 | REV00345 | REV00346 | REV00347 | REV00348 | REV00349 | REV00350 | REV00351 | REV00352 | REV00353 | REV00354 | REV00355 | REV00356 | REV00357 | REV00359 | REV00360 | REV00361 | REV00362 | REV00363 | REV00364 | REV00365 | REV00366 | REV00367 | REV00368 | REV00369 | REV00370 | REV00371 | REV00372 | REV00373 | REV00374 | REV00375 | REV00385 | REV00386 | REV00388 | REV00390 | REV00391 | REV00392 | REV00393 | REV00394 | REV00395 | REV00396 | REV00397 | REV00398 | REV00399 | REV00400 | REV00401 | REV00402 | REV00403 | REV00404 | REV00405 | REV00406 | REV00407 | REV00408 | REV00409 | REV00410 | REV00411 | REV00412 | REV00413 | REV00414 | REV00415 | REV00416 | REV00417 | REV00418 | REV00419 | REV00420 | REV00421 | REV00422 | REV00423 | REV00424 | REV00425 | REV00426 | REV00427 | REV00428 | REV00429 | REV00430 | REV00431 | REV00432 | REV00433 | REV00434 | REV00435 | REV00436 | REV00437 | REV00438 | REV00439 | REV00440 | REV00441 | REV00442 | REV00443 | REV00444 | REV00445 | REV00446 | REV00447 | REV00448 | REV00449 | REV00450 | REV00451 | REV00453 | REV0454 | REV00455 | REV00456 | REV00457 | REV00458 | REV00459 | REV00460 | REV00461 | REV00462 | REV00463 | REV00464 | REV00465 | REV00466 | REV00467 | REV00468 | REV00469 | REV00470 | REV00471 | REV00472 | REV00473 | REV00474 | REV00475 | REV00476 | REV00477 | REV00478 | REV00479 | REV00480 | REV00481 | REV00482 | REV00483 | REV00484 | REV00485 | REV00486 | REV00487 | REV00488 | REV00489 | REV00490 | REV00491 | REV00492 | REV00493 | REV00494 | REV00495 | REV00496 | REV00497 | REV00498 | REV00499 | REV00500 | REV00501 | REV00502 | REV00503 | REV00504 | REV00505 | REV00506 | REV00507 | REV00508 | REV00509 | REV00510 | REV00511 | REV00512 | REV00513 | REV00514 | REV00515 | REV00516 | REV00517 | REV00518 | REV00519 | REV00520 | REV00521 | REV00522 | REV00523 | REV00524 | REV00525 | REV00526 | REV00527 | REV00528`

REV00MNF | Message msg-id not found in logon-id
Explanation | A message inquiry was made for a message number that is not known to Adabas Review. This will happen if an invalid message number is entered.
Action | If the message number is for an Adabas Review message, contact your Software AG technical support representative.

REV00001 | Welcome to Adabas Review V v.r.s running under tp-monitor
Explanation | This message welcomes users to Adabas Review and indicates the environment under which they are running.
v.r.s | the version, revision, and SP level.
tp-monitor | the active TP monitor.
Action | This message is for information only.

REV00002 | Review command must begin with subsystem code
Explanation | An invalid command was entered from the Adabas Review main menu. All commands from the main menu must begin with a subsystem code as shown on the screen.
Action | Enter a valid command.

REV00003 | THIS FIELD IS NOT ALLOWED FOR DETAIL REPORTS
Explanation | The specified filed is not allowed for detailed reports.
Action | Remove the incorrect field.

REV00004 | Enter Review command
Explanation | Adabas Review is waiting for terminal input.
Action | Press a valid PF key or enter an Adabas Review command.

REV00005 | Invalid command
Explanation | An invalid command was entered into the Adabas Review command line.
Action | Press a valid PF key or enter a valid Adabas Review command.

REV00006 | Press 'Enter' to continue initialization process
Explanation | During Adabas Review initialization a series of messages are displayed. Adabas Review will pause whenever a page is full or on the last page.
Action | Press ENTER.

REV00008 | No online system of Review is available
Explanation | Adabas Review has determined that there are no online systems available to the user. There are two possible causes: the installation of Adabas Review has not been fully completed. Adabas Review is installed, but your profile prohibits you from accessing the available systems.
Action | Contact your Adabas Review administrator.

REV00011 | Interval statistics profile has been created
Explanation | During Adabas Review initialization, the interval statistics profile record was created.
Action | This message is for information only.

REV00012 | Report has been saved
Explanation | The request to save a report definition to the Adabas Review repository has completed successfully.
Action | This message is for information only.

REV00013 | Now viewing current data
Explanation | You are now viewing current data as opposed to historical data.
Action | This message is for information only.

REV00014 | user-id is not authorized to use Review
Explanation | Either you have not been defined to Adabas Review, or you are not authorized to use Adabas Review.
Action | Contact your Adabas Review administrator.

REV00015 | Report name is required
Explanation | An attempt was made to edit/copy a report without a name.
Action | Enter a name in the report name field.

REV0001 | At least one item must be selected
Explanation | An attempt was made to add a report without selecting any items to be used as report criteria.
Action | Select one or more fields to be used as criteria by entering a number in its ORDER field.

REV00020 | Order number must not exceed 20 (max number of items)
Explanation | A number greater that 20 was entered into one of the ORDER fields.
Action | Enter a number between 1 and 20.

REV00021 | Order number must be unique
Explanation | Duplicate ORDER numbers have been detected.
Action | Enter a unique number in each ACCT ORDER to be included in the report.

REV00025 | Now viewing historical data
Explanation | You are now viewing historical data as opposed to current data.
Action | This message is for information only.

REV00026 | Report was not saved
Explanation | The request to save a report was not successful. This is usually caused by responding NO when asked if you want to replace the report that was previously saved under the same name.
Action | This message is for information only.

REV0002 | There are no detailed records for this report
Explanation | A detailed response time report was requested but there are no detail records for the selected report.
Action | This message is for information only.

REV00028 | Report was not refreshed
Explanation | This indicates that a request to restart a report was not successful.
Action | This message is for information only.

REV00029 | Invalid reply
Explanation | An invalid reply was given to an Adabas Review prompt.
Action | Enter a valid reply.

REV00030 | Report has been purged
Explanation | This confirms that the purge report request was successful.
Action | This message is for information only.

REV00032 | Report not found
Explanation | An attempt to access a report has failed because the report is not active.
Action | This message is for information only.

REV00033 | Unknown return code from purge - RC= ret-code
Explanation | An unknown return code was returned from the purge reports program due to an internal error.
Action | If the problem reoccurs, contact your Software AG technical support representative.

REV00035 | This is the oldest historical snapshot
Explanation | This is the oldest historical snapshot; the NEXT command cannot be entered.
Action | This message is for information only.

REV00036 | Do not enter x and a direct command
Explanation | A reply was entered into an Adabas Review prompt field and a direct command was entered simultaneously.
Action | Either answer the Adabas Review prompt or enter a direct command, but not both.

REV00037 | Invalid response - only valid response is xxx
Explanation | An invalid response was detected and Adabas Review is prompting the user with the correct response.
Action | Enter a valid response.

REV00038 | Report status has been changed
Explanation | This confirms that a request to activate or deactivate a report was successful.
Action | This message is for information only.

REV00040 | Redisplay buffer full - Rediplay unavailable
Explanation | The redisplay is unavailable because more than 5000 lines were displayed.
Action | As a workaround, the report data can be printed via the HC command and other tools can be used to scroll through this output.

REV00043 | You must reply 'Y' or 'N'
Explanation | An invalid reply was given in response to an Adabas Review prompt that requires a reply of either yes ("Y") or no ("N").
Action | Reply "Y" or "N".

REV00044 | Value must be between 0 and 100
Explanation | The value entered was not within the range 0 and 100.
Action | Enter a value between 0 and 100.

REV00045 | Do not mark blank lines
Explanation | A selection was marked on a line that does not have a value or any data to select.
Action | Mark a valid selection or enter an Adabas Review command.

REV00046 | Do not mark deleted reports
Explanation | A character was placed in the select field of a report that was just deleted.
Action | Do not place a character in this field.

REV00047 | Invalid character
Explanation | An invalid character was entered into an Adabas Review field.
Action | Enter a valid character.

REV00050 | Non-zero return code from FREEMAIN
Explanation | An unexpected return code has occurred while trying to free storage. The return code is also displayed.
Action | If the problem recurs, contact your Software AG technical support representative.

REV00054 | Now creating sample report report-name
Explanation | When Adabas Review is invoked online for the first time, it adds sample Adabas reports to its system file.
Action | This message is for information only.

REV00055 | Select a historical snapshot
Explanation | Select a historical snapshot.
Action | This message is for information only.

REV00057 | Use of function is prohibited
Explanation | An attempt was made to perform an Adabas Review function that is not permitted for the user.
Action | Contact your Adabas Review administrator.

REV00058 | There are no saved reports to list
Explanation | A request to list report definitions was made but there are no definitions to list.
Action | This message is for information only.

REV00059 | Operator command issued
Explanation | The operator command was issued to Com-plete.
Action | This message is for information only.

REV00060 | No report selected to view
Explanation | An attempt was made to perform an Adabas Review View function, but no report was selected
Action | Access a report using a List or Edit function and the retry the View function.

REV00062 | No data has been accumulated for this report
Explanation | A request to display a report cannot be satisfied because the report has not yet accumulated any data.
Action | Determine if the report criteria is correct and if so, try again later or else add a new report.

REV00064 | Invalid function
Explanation | An invalid function was entered.
Action | Enter a valid function.

REV00065 | DBID missing
Explanation | DBID= was entered on the Adabas Review command line of the Adabas Communication Statistics display, but no corresponding DBID number was given.
Action | Enter DBID=nnn where nnn is a valid DBID number.

REV00066 | Invalid cursor position
Explanation | The cursor was placed at an invalid location on a screen that senses the cursor position to perform a function.
Action | Place the cursor at a valid position or enter an Adabas Review command.

REV00068 | Invalid logical operator
Explanation | An invalid logical operator was entered. Valid operators are: =,:,<,>,EQ,NE,LT,GT,LE,GE
Action | Enter a valid logical operator.

REV00072 | Mark one line only
Explanation | More than one line was marked to perform a report function. This is not allowed.
Action | Mark only one line at a time.

REV00073 | Invalid character in select column
Explanation | A line has been marked with a character that has no assigned function.
Action | Mark lines using valid characters.

REV00074 | Invalid Transaction Summary option
Explanation | An invalid option was entered into the Transaction Summary Option field in the Edit Report screen. Valid options are NONE, SUM, and DET.
Action | Enter a valid option.

REV00078 | Report was not purged
Explanation | The request to purge a started report was not performed.
Action | This message is for information only.

REV00079 | Invalid message prefix
Explanation | An inquiry was made for a message number that has an invalid prefix. Message numbers must start with REV.
Action | Enter the MSG command using a valid message number.

REV00080 | Com-plete functions are not valid under CICS
Explanation | A Com-plete performance monitor function was attempted. This is not valid under CICS.
Action | This message is for information only.

REV00081 | Review is not compatible with this version of Com-plete
Explanation | A Com-plete performance monitor function was attempted on a version of Com-plete earlier than version 4.4.
Action | Install the current version of Com-plete.

REV00082 | Select a buffer pool or enter a Review command
Explanation | The Adabas Review buffer pool function is waiting for terminal input.
Action | Select a buffer pool by name or enter an Adabas Review command.

REV00083 | Syntax error in scan command
Explanation | A syntax error was detected while processing a scan command on the ET display.
Action | This message is for information only.

REV00084 | Invalid buffer pool name
Explanation | The buffer pool selection entered cannot be identified.
Action | Enter a valid buffer pool name or enter an Adabas Review command.

REV00085 | Command not allowed in history mode
Explanation | The command entered is not allowed in history mode.
Action | Do not enter command.

REV00086 | No ADAB control block found
Explanation | The Adabas Communication Statistics function was invoked, but there has not been any database access since Com-plete was started. Therefore, there is no database information to display.
Action | Try again later.

REV00087 | nn Reports removed from AUTOSTART status
Explanation | This confirms that the indicated report definitions have been changed from AUTOSTART to NON-AUTOSTART status.
Action | This message is for information only.

REV00091 | Invalid command code
Explanation | An invalid code was entered for a command.
Action | Enter a valid command code.

REV00092 | Report has been started
Explanation | This confirms that the request to start a report was successful.
Action | This message is for information only.

REV00093 | Syntax error(s) in report definition
Explanation | The request to start an online report has failed because of syntax errors in the report definition.
Action | Correct the report definition and start the report again.

REV00094 | Adabas response code rsp
Explanation | Adabas has responded with a non-zero response code.
Action | Use the Adabas Messages and Codes documentation to determine the problem.

REV00095 | Report was not started
Explanation | The request to start a report was not successful.
Action | This message is for information only.

REV00096 | User profile is being held by another user
Explanation | An attempt was made to access a user profile that is being updated by another user.
Action | Edit the user profile again. Ensure that the changes made to profile do not affect the changes that you are making.

REV00097 | User profile not specified
Explanation | The purge user (PU) command was given without specifying a user profile.
Action | When using the purge user (PU) command, specify the user profile you wish to purge. The format for the command is PU uuuuuu where uuuuuu is the user profile.

REV00098 | User profile was not purged
Explanation | A request was made to purge a user profile. When Adabas Review asked for a confirmation, the user decided not to purge the user profile.
Action | This message is for information only.

REV00099 | User profile was not found
Explanation | An attempt was made to delete a user profile that was not found in the Adabas Review repository.
Action | Check to make sure the user ID you specified is correct.

REV00100 | User profile has been purged
Explanation | This confirms that a request to purge a user profile was successful.
Action | This message is for information only.

REV00101 | New user profile
Explanation | The profile that you are editing is new.
Action | You may now customize the new user profile. To save this new profile, press PF5or issue the SAVE command.

REV00102 | User profile was not saved
Explanation | A request was made to save the changes made to a user profile. When Adabas Review asked for a confirmation, the user decided not to save the changes.
Action | This message is for information only.

REV00104 | Return code ret-code received from program-name
Explanation | An unexpected return code was received from one of Adabas Review's programs.
Action | Record the error message and contact your Software AG technical support representative.

REV00105 | User profile has been saved
Explanation | The changes made to the user profile have been saved.
Action | This message is for information only.

REV00106 | No Review control block found
Explanation | (CICS Only) This message appears when REVTAB has not been defined as a resident program.
Action | Contact your Software AG technical support representative.

REV00108 | Default user profile has been added
Explanation | This message appears the first time Adabas Review is invoked after installation. A DEFAULT user profile is added to the Adabas Review repository, which allows all users to perform all functions of Adabas Review including the ability to maintain user profiles.
Action | A logical procedure at this point would be to invoke the user profile system and add yourself as able to maintain user profiles. Then update the DEFAULT profile so that general users cannot maintain user profiles.

REV00111 | No storage available to start report
Explanation | A request to start a report has failed due to insufficient storage. This is probably because of other reports that are using most or all of the storage allocated to Adabas Review.
Action | Purge one of the already existing reports or try again later.

REV00116 | Statistics profile was not saved
Explanation | The statistics profile was not saved.
Action | This message is for information only.

REV00120 | Users attached for test simulation
Explanation | This confirms that users have been attached to simulate a load on Com-plete.
Action | This message is for information only.

REV00121 | Error error-number attaching users
Explanation | An error has occurred while trying to attach users for load simulation.
Action | If the problem reoccurs, contact your Software AG technical support representative.

REV00123 | Statistics profile has been saved
Explanation | The statistics profile has been saved.
Action | This message is for information only.

REV00124 | TID number must be numeric
Explanation | A TID number was entered into the SA screen via the T= or TID= command but is was not numeric.
Action | Enter a numeric TID number.

REV00125 | Report definition has been saved successfully
Explanation | This confirms that the request to save a report definition was successful.
Action | This message is for information only.

REV00129 | Report definition not found
Explanation | An attempt was made to retrieve a report definition but no report definition by that name was found.
Action | Determine the correct name or create a new definition.

REV00132 | Interval may not be greater than 1440 minutes
Explanation | The interval may not be greater than 1440 minutes.
Action | This message is for information only.

REV00133 | Review is terminating
Explanation | A request was made to start, view, or list a report, but Adabas Review is in the process of terminating.
Action | This message is for information only.

REV00134 | Duplicate report name - report not started
Explanation | An attempt to start an Adabas report has failed because a report with the same name is already active.
Action | Purge the currently active report and retry or start a report with a different name.

REV00135 | Review command not provided
Explanation | An attempt was made to communicate with the Adabas Review exit but no Adabas Review command was provided.
Action | Provide an Adabas Review command.

REV00137 | Insufficient storage to issue Review command
Explanation | The Adabas Review exit routine is not accepting communications due to insufficient storage.
Action | Purge at least one of the started reports.

REV00138 | Insufficient storage to start report
Explanation | An attempt to start an Adabas Review report has failed due to insufficient storage.
Action | Purge an active report and retry.

REV00139 | Invalid SUMMARY, MAX or MIN field
Explanation | An attempt to start an Adabas Review report has failed because fields were marked as Sum, Min, Max, or Avg, but these fields are only allowed to be Order fields.
Action | Make the fields Order fields only.

REV00140 | An invalid value was specified in the RULE
Explanation | An attempt to start an Adabas Review report has failed because values specified in the Rule where either too long, or in case of numbers with a decimal point, the formatting is not correct.
Action | Specify a correct value in the RULE.

REV00141 | Format buffer error
Explanation | A format buffer error has occurred while trying to communicate with the Adabas Review exit routine.
Action | Contact your Software AG technical support representative.

REV00144 | Display program not found
Explanation | An attempt to view an active report has failed because the display program for this report cannot be found.
Action | Generate a display program by resaving the report definition, if it is available, or change the display program name on the LS screen to a program name that is known to be acceptable for this report.

REV00145 | Natural error: error-number
Explanation | A Natural error condition occurred. The Natural error message number is displayed.
Action | Reference the Natural online message utility for an explanation of the error.

REV00146 | Report definition was not saved
Explanation | The request to save a report definition was canceled by the user in response to an overlay warning.
Action | This message is for information only.

REV00147 | Too many fields - exceeds max linesize - save canceled
Explanation | The request to save a report definition was canceled because the resulting generated display program would have exceeded the maximum allowable line size.
Action | Reduce the number of fields and try again.

REV00148 | DBID has been changed
Explanation | This confirms that the request to change the target DBID was successful.
Action | This message is for information only.

REV00149 | There are no started reports
Explanation | A request to list started reports was made but there are no started reports to list.
Action | This message is for information only.

REV00150 | Detailed reports cannot be viewed online
Explanation | Only summary reports can be viewed online. Detailed reports are printed at Adabas termination time.
Action | This message is for information only.

REV00151 | Insufficient storage to reactivate report
Explanation | An attempt was made to reactivate a report that was deactivated by Adabas Review due to insufficient storage. The report cannot be reactivated.
Action | Use the refresh (RF) command to purge the existing data and start accumulating new information.

REV00152 | Report has been refreshed
Explanation | This confirms that a refresh (RF) command was successful.
Action | This message is for information only.

REV00153 | There are no history reports
Explanation | A request to List History Reports was canceled because there are no history reports to list.
Action | This message is for information only.

REV00155 | DBID must be between 0 and 255.
Explanation | An attempt was made to change the DBID number to less than 0 or greater than 255.
Action | Enter a DBID number in the range of 0 to 255.

REV00156 | Invalid AND/OR field
Explanation | A value other than AND or OR was entered into the AND/OR field of the selection criteria on the Processing Rules screen.
Action | Enter AND or OR.

REV00157 | No field specified
Explanation | No field name was specified for the entered criteria on the Edit Report screen.
Action | Enter a field name.

REV00158 | AND/OR field not followed by another condition
Explanation | AND or OR was entered into the AND/OR field of the Processing Rules screen but no condition followed.
Action | Either remove the AND/OR or enter another condition.

REV00159 | AND/OR field missing
Explanation | More than one condition was coded on the Processing Rules screen, but no AND/OR was coded for the previous condition.
Action | Enter AND/OR on the previous condition

REV00160 | OPERATOR field missing
Explanation | The OPERATOR field has been left blank on a condition.
Action | Fill in the OPERATOR field.

REV00161 | VALUE field missing
Explanation | The VALUE field has been left blank on a condition.
Action | Fill in the VALUE field.

REV00162 | Invalid OPERATOR field
Explanation | An invalid operator was entered into the OPERATOR field of the Processing Rules screen.
Action | Enter a valid operator.

REV00163 | Invalid field name
Explanation | An invalid field name was entered on the Edit Report screen.
Action | Press PF11 for a list of valid field names.

REV00169 | ORDER number too high
Explanation | A number greater than 20 was entered into the ORDER field of the Edit Report screen. 20 is the highest number that can be entered.
Action | Enter a number between 1 and 20.

REV00170 | field-name is not a valid field for SUM, AVG, PCT or ROUND
Explanation | A field was marked for SUM, AVG, PCT, or ROUND on the Edit Report screen, but the field marked is not a numeric field. Fields must have a numeric output to be eligible for SUM, AVG, PCT, or ROUND.
Action | Place a number in the ORDER column, and remove any marks for SUM, AVG, PCT, or ROUND.

REV00171 | SAVE/START canceled by operator
Explanation | The request to save a report definition was canceled by the user in response to an overlay warning.
Action | This message is for information only.

REV00175 | Invalid value
Explanation | An invalid value was entered as part of a logical condition on the Edit Report screen.
Action | Enter a valid value.

REV00176 | Internal storage error
Explanation | An internal storage management error has occurred within the Adabas Review nucleus.
Action | If the problem recurs, contact your Software AG technical support representative.

REV0017 | ROUND is only valid on fields with an ORDER number
Explanation | A rounding factor was specified for a field that does not also have an order number specified.
Action | Enter a number in the ORDER field, or remove the rounding factor.

REV00179 | You must enter ORDER, SUM, MIN, MAX, PCT or AVG
Explanation | A field was entered on the Edit Report screen but no action was specified; i.e. ORDER, SUM, MIN, MAX, PCT, or AVG.
Action | Enter a number in the ORDER field and/or an X in one or more of the SUM, MIN, MAX, PCT, or AVG fields

REV00180 | Invalid data in ROUND column
Explanation | The data entered into the round column of the Edit Report screen was not numeric.
Action | Enter a number with or without a decimal into the round field.

REV00181 | ADACALL must be an integer between 0 and 32,767
Explanation | ADACALL specifies the maximum number of Adabas calls an application can make before the Com-plete / Adabas interface forces the application to be rolled out. This parameter is ignored if ADAROLL=NO is specified.
Action | Enter a number between 0 and 32,767.

REV00182 | ADALIMIT must be an integer between 0 and 32,767
Explanation | ADALIMIT specifies the number of Adabas calls that many be made by an online transaction without any intervening terminal I/O. Programs that exceed this limit are canceled.
Action | Enter a number between 0 and 32,767.

REV00183 | ADAROLL must be 'ALWAYS', 'NEVER', or less than 30.99
Explanation | ADAROLL specifies the amount of time Com-plete will wait for Adabas calls before rolling out the program making the call.
Action | Enter ALWAYS, NEVER, or a number less than 30.99.

REV00184 | ADACALL for DBID dbid has been changed to yyyyy by user-id
Explanation | The ADACALL parameter for the specified database was changed to yyyyy through the facilities provided by the Adabas Communication Statistics function (Adabas Calls from Com-plete) in Adabas Review DC.
Action | This message is for information only.

REV00185 | ADALIMIT for DBID dbid has been changed to yyyyy by user-id
Explanation | The ADALIMIT parameter for the specified database was changed to yyyyy through the facilities provided by the Adabas Communication Statistics function (Adabas Calls from Com-plete) in Adabas Review DC.
Action | This message is for information only.

REV00187 | Only 'Y' and 'N' are valid values
Explanation | The letter "Y" (yes) and the letter "N" (no) are the only two valid values for this field.
Action | Enter "Y" if you wish the APPLYMOD to be active; or enter "N" if you wish to deactivate the applymod.

REV00188 | The ADABAS/COM-PLETE parameters have been updated
Explanation | This message confirms that the Adabas / Com-plete parameters have been successfully updated.
Action | This message is for information only.

REV00190 | Invalid cursor placement for requested function
Explanation | The cursor must be placed on a line that contains valid data.
Action | Place cursor on a line with valid data.

REV00193 | Too many xxx fields
Explanation | xxx is ORDER, SUM, MIN, MAX, AVG, or ROUND. There were too many of the indicated fields to process. When all field names are combined, they will not fit into an 80-byte statement. The 80-byte statements are used internally by Adabas Review for report definition storage.
Action | Reduce the number of fields by one until the message disappears.

REV00195 | Invalid page number entered
Explanation | A number was entered on the Adabas Review command line that was greater than the actual number of pages available.
Action | Enter a valid page number.

REV00196 | Roll buffer not allocated
Explanation | The roll buffer is not allocated.
Action | This message is for information only.

REV00197 | Roll data sets not allocated
Explanation | The roll data sets are not allocated.
Action | This message is for information only.

REV00198 | User not logged on
Explanation | The user is not logged on.
Action | This message is for information only.

REV00199 | Invalid wrap option
Explanation | An invalid wrap option was specified in the report definition. The option must be NONE, STD, or HIGH.
Action | This message is for information only.

REV00200 | Low water mark must be less than high water mark
Explanation | The low water mark specified was higher than or equal to the high water mark.
Action | Enter a number less than the high water mark.

REV00202 | Review is not installed in database dbid
Explanation | An attempt was made to either start a report or to list started reports against a database that either does not have Adabas Review installed as a user exit 4 or does not currently have LOGGING turned on.
Action | Verify that Adabas Review is installed on the target DBID. If it is, ensure that ADARUN LOGGING=YES has been specified and that LOGGING has not been subsequently disabled from the operator console.

REV00203 | Report hard copy has been queued
Explanation | This confirms that a request to send report output to a hardcopy device completed successfully, and that the report is either now printing or has been placed on the queue to be printed.
Action | This message is for information only.

REV00205 | Invalid display program name
Explanation | An attempt was made to change the display program name using the CP command of the List Reports screen, but the new name is blank or invalid.
Action | Enter a valid program name.

REV00206 | Display program name has been changed
Explanation | This confirms that the request to change the display program name using the CP command of the List Report Definitions screen was successful.
Action | This message is for information only.

REV00207 | Report definition was purged by another user
Explanation | The report definition selected is being purged by another user.
Action | This message is for information only.

REV00209 | Invalid character in report name
Explanation | An invalid character such as a quotation mark or a period was used as part of the report name.
Action | Remove the invalid character from the report name.

REV00210 | Invalid start/stop date
Explanation | A date range was entered for viewing a history report but the date(s) are not valid. This may mean that the starting date is greater than the ending date, or that invalid numeric data or an invalid date format has been entered.
Action | Enter a valid date range in the form of yyyy-mm-dd or press ENTER to default to the maximum date range.

REV00211 | History reports must be purged from the expanded list
Explanation | An attempt was made to purge a history report from the LH screen. This is not a valid LH function. The list must be expanded using the EX command before history reports can be purged.
Action | Enter EX in the SEL column next to the report to be purged. An expanded list will appear from which the Purge History Report (PH) function can be executed.

REV00212 | Enter date range
Explanation | This prompts you to enter a date range before viewing a history report. The maximum date range (all dates) is the default.
Action | Enter a date range in the form of yyyy-mm-dd, or press ENTER to default to the maximum date range.

REV00214 | Display program regeneration complete
Explanation | The request to regenerate display programs has completed successfully.
Action | This message is for information only.

REV00217 | Review system file not available
Explanation | Adabas Review attempted to read information from its system file but received an Adabas response code of 148 (ADARSP148).
Action | Bring up the database that has the Adabas Review repository and make sure that the LFILE parameter has been specified correctly.

REV00218 | Default system must be 'DB', 'DC', 'MM', or 'NM'
Explanation | An invalid value was entered for default system. The valid system codes are:
DB | Database (Adabas Review)
DC | Data Communication
MM | Main Menu
NM | Natural Monitor
Action | Enter a valid system code.

REV00219 | Input not numeric
Explanation | A value was entered into a field that is intended to accept numeric data only.
Action | Enter a valid numeric value.

REV00220 | Auto regenerate started
Explanation | The subtask to generate auto-report definitions was successfully started.
Action | This message is for information only.

REV00221 | Auto regenerate already active
Explanation | The subtask to generate auto-report definitions is still active from a previous execution.
Action | Wait a few seconds and try the command again.

REV00222 | Auto regenerate failed
Explanation | The subtask to regenerate auto-report definitions was not attached and did not run.
Action | Check your Adabas STEPLIB and make certain that the module RAOSAUTO is present.

REV00223 | UEX4 version error
Explanation | The Adabas UEX4 module RAOSEXIT is not the correct version.
Action | Verify that Adabas Review has been correctly installed.

REV00224 | MSG function not available from this screen
Explanation | The Adabas Review message help subsystem is not available from this screen.
Action | Perform the MSG function from another screen.

REV00225 | DBID must be between 1 and 65535
Explanation | The target database ID must be in the range between 1 and 65535.
Action | Enter a database ID in the specified range.

REV00226 | SVC is zero
Explanation | The SVC specified cannot be zero (0).
Action | Enter a correct SVC number.

REV00227 | Target type must be 'ADA', 'NET', 'NPR', or 'TPF'
Explanation | The target type must be one of the specified values.
Action | Enter the correct target type.

REV00228 | DBID for Adabas target type must be less than 255
Explanation | If the target type is ADA, then the target database ID must be in the range of 1 to 255.
Action | Enter a database ID in the specified range.

REV00229 | Field value must be 'Y' or 'N'
Explanation | An invalid value was entered for the field.
Action | Enter a valid field value: either yes ("Y") or no ("N").

REV00230 | No target definition found for target target-id
Explanation | The target definition did not exist for the requested target.
Action | Define the target.

REV00231 | Target definition for DBID dbid saved
Explanation | The target definition was successfully saved.
Action | This message is for information only.

REV00234 | Default definition cannot be purged
Explanation | The default definition for target 00000 cannot be purged.
Action | This message is for information only.

REV00235 | Target definition(s) purged successfully
Explanation | The target definitions marked for purge were successfully deleted.
Action | This message is for information only.

REV00236 | No target definition exists for DBID dbid and default is not present
Explanation | The target definition for the database specified did not exist, and there was also no default definition.
Action | Add the target definition for the specified target.

REV00237 | Generate started
Explanation | The subtask to generate report definitions was successfully started.
Action | This message is for information only.

REV00238 | Generate already active
Explanation | The subtask to generate report definitions is still active from a previous execution.
Action | Wait a few seconds and try the command again.

REV00239 | Generate failed
Explanation | The subtask to generate report definitions was not attached and did not run.
Action | Check your Adabas STEPLIB and make certain that the module RAOSAUTO is present.

REV00240 | Function canceled
Explanation | The requested function was terminated by user request and was not performed.
Action | This message is for information only.

REV00241 | Review file set successfully
Explanation | The Adabas Review data file's database ID and file number were set successfully.
Action | This message is for information only.

REV00242 | Unable to open command log file for output
Explanation | A report was started with the logging option set to "Y" (yes), but the file specified for output cannot be opened. The report is started without logging.
Action | If this is an online report, make sure the DSN field of the Report Options screen is set to a valid command log output file. If this is a batch report, make sure the DSN= parameter of the LOG statement is set to a valid command log output file.

REV00243 | Adabas Online Services is not installed
Explanation | The request to invoke Adabas Online System (AOS) from Adabas Review has failed because AOS is not installed in the current Natural system file.
Action | This message is for information only.

REV00244 | Components not installed properly
Explanation | The installation process did not complete successfully.
Action | Make sure that all INPL and IUPD media are properly installed.

REV00245 | PFnn not defined
Explanation | The PF key that was pressed is not defined to perform a function.
Action | Press a valid PF key.

REV00246 | Press 'PF3' to exit or 'PF5' to save the profile
Explanation | To exit without saving the changes made to a user profile, press PF3. To save the changes made to a user profile, press PF5.
Action | See explanation.

REV00247 | Userid must be specified
Explanation | A user ID must be specified.
Action | Enter a user ID.

REV00248 | Natural error error-number has occurred on line line-number of program program-name
Explanation | A Natural error has occurred in one of Adabas Review's programs.
Action | Record the information given in the message and contact your Software AG technical support representative.

REV00249 | Command log data set already in use
Explanation | A report was started with the logging option set to "Y" (yes), but the specified output data set is already in use by another report. The report is started without logging.
Action | Either use another data set, or purge the report that is using the command log data set.

REV00250 | Logging is not valid for summary reports
Explanation | LOGGING was specified on the Report Options screen for a summary report. Only detail reports can perform the LOGGING function.
Action | Either set LOGGING to "N" or set SUM/DETAIL to "D".

REV00252 | At least one field is required
Explanation | An attempt was made to save a report definition with no fields to be displayed. At least one field is required to save a report.
Action | Correct the report definition and press PF5to save the report definition.

REV00253 | There are no report definitions on file
Explanation | A request to list report definitions cannot be satisfied because there are no definitions to list.
Action | This message is for information only.

REV00254 | At least one order field is required
Explanation | An attempt to save a summary report failed because there are no ORDER fields. At least one ORDER field is required for summary reports.
Action | Make at least one field an ORDER field and save the report.

REV00255 | Report definition conversion complete
Explanation | The process of converting Adabas Review report definitions has completed.
Action | This message is for information only.

REV00256 | History file conversion complete
Explanation | The process of converting Adabas Review history reports completed.
Action | This message is for information only.

REV00257 | User profile conversion complete
Explanation | The process of converting Adabas Review user profiles has completed.
Action | This message is for information only.

REV00258 | Report definition conversion was canceled
Explanation | The process of converting Adabas Review report definitions was canceled at the request of the user. Any reply other than "yes" or "change" on the LFILE confirmation screen will cause this message.
Action | This message is for information only.

REV00259 | History file conversion was canceled
Explanation | The process of converting Adabas Review history reports was canceled at the request of the user. Any reply other than "yes" or "change" on the LFILE confirmation screen will cause this message.
Action | This message is for information only.

REV00260 | User profile conversion was canceled
Explanation | The process of converting Adabas Review user profiles was canceled at the request of the user. Any reply other than "yes" or "change" on the LFILE confirmation screen will cause this message.
Action | This message is for information only.

REV00261 | There are no report definitions to convert
Explanation | An attempt was made to convert report definitions, but there are none to convert. Adabas Review only converts report definitions that do not already exist in the target Adabas Review repository.
Action | This message is for information only.

REV00262 | There are no history reports to convert
Explanation | An attempt was made to convert Adabas Review history reports, but there are none to convert.
Action | This message is for information only.

REV00263 | There are no user profiles to convert
Explanation | An attempt was made to convert Adabas Review user profiles, but there are none to convert. Adabas Review only converts user profiles that do not already exist in the target Adabas Review repository.
Action | This message is for information only.

REV00264 | Error error-number while trying to convert report definitions
Explanation | Either an Adabas or a Natural error has occurred while trying to convert report definitions.
Action | Follow the Adabas or Natural procedures for error correction.

REV00265 | Error error-number while trying to convert history reports
Explanation | Either an Adabas or a Natural error has occurred while trying to convert history reports.
Action | Follow the Adabas or Natural procedures for error correction.

REV00266 | Error error-number while trying to convert user profiles
Explanation | Either an Adabas or a Natural error occurred while trying to convert user profiles.
Action | Follow the Adabas or Natural procedures for error correction.

REV00267 | Do not try to convert to and from the same file
Explanation | An attempt was made to run an Adabas Review conversion program with identical TO and FROM files.
Action | Correct the LFILE for the TO or FROM file.

REV00268 | Invalid file number
Explanation | The user attempted to change the database ID and file number of the Adabas Review repository. The file number specified was not an Adabas Review file.
Action | Specify a correct Adabas Review DBID/file number.

REV00269 | No active targets found on SVC svc
Explanation | No active database targets were found on the SVC number specified in the message.
Action | Verify that the target definitions are defined to the correct SVC number.

REV00270 | Database dbid is a Natural Process target
Explanation | The target selected is an Entire System Server (formerly Natural Process) target type.
Action | This message is for information only.

REV00271 | Database dbid is not active
Explanation | The database selected is not active.
Action | This message is for information only.

REV00272 | Database dbid is a non-Adabas target
Explanation | The database selected is a non-Adabas type target.
Action | This message is for information only.

REV00273 | Report is already suspended
Explanation | An attempt was made to suspend a report that was is already suspended.
Action | This message is for information only.

REV00274 | Invalid OP summary option
Explanation | An invalid option was entered on the Edit Report screen for the OP summary parameter.
Action | Enter a valid option.

REV00275 | New report definition
Explanation | A new report definition is being created.
Action | Enter the parameters for the new report definition or exit.

REV00276 | Report is already active
Explanation | An attempt was made to reactivate a report that was already active.
Action | This message is for information only.

REV00277 | History data has been purged
Explanation | Historical data was purged.
Action | This message is for information only.

REV00278 | History data was not purged
Explanation | Historical data was not purged.
Action | This message is for information only.

REV00279 | History data not found
Explanation | Historical data was not found.
Action | This message is for information only.

REV00280 | Available storage in thread insufficient
Explanation | The available storage in the thread is insufficient.
Action | Contact your Software AG technical support representative.

REV00281 | An invalid request or an invalid FQE was found
Explanation | An invalid request or an invalid free queue element (FQE) was found.
Action | Contact your Software AG technical support representative.

REV00282 | No response time report definition was specified
Explanation | No response time report definition was specified.
Action | Contact your Software AG technical support representative.

REV00283 | Report definition has been purged
Explanation | Report definition has been purged.
Action | This message is for information only.

REV00284 | Report definition was not purged
Explanation | Report definition was not purged.
Action | This message is for information only.

REV00285 | Invalid device type for download
Explanation | An attempt was made to download a report but the Natural session is not in PC mode.
Action | If the device is a PC using Entire Connection, set your Natural session to PC mode by entering %+ on the command line, and reenter the DL command.

REV00286 | Duplicate order numbers
Explanation | More than one field has the same order number on the Edit Report screen.
Action | Make each order number unique.

REV00288 | Report is not active
Explanation | An attempt was made to perform a function on a started report, but no started report with the specified report name was found.
Action | This message is for information only.

REV00289 | LOG command not allowed while viewing data
Explanation | An attempt was made to issue the LOG command while viewing a report.
Action | Stop viewing the report and reissue the LOG command.

REV00290 | Adabas Review logging status changed
Explanation | The Adabas Review dynamic logging options have been updated.
Action | This message is for information only.

REV00291 | Error returned during LOG request - nnnn
Explanation | The LOG command was issued and an error occurred during processing. nnnn = the response code associated with the error.
Action | Follow the Adabas or Natural procedures for error correction.

REV00292 | Review not installed on database
Explanation | While attempting to view the buffer pool display, Adabas determined that Adabas Review was not installed on that database and issued a response code.
Action | This message is for information only.

REV00293 | Function restarted due to Adabas rsp code 9
Explanation | An Adabas Review function was restarted from the beginning because an Adabas response code 9 (ADARSP009) was received.
Action | This message is for information only.

REV00294 | NM component not installed
Explanation | An attempt was made to enter Adabas Review NM, but the NM component was not on the installation media.
Action | Determine whether the NM component was actually purchased. If it was purchased, then you may have inadvertently received the wrong Adabas Review installation media. Contact your Software AG representative.

REV00295 | Select a history report
Explanation | An attempt was made to view a list of dates and times of history records for a response time report without specifying the name of the report.
Action | Specify the response time name.

REV00296 | TID must be between 1 and 65,535
Explanation | The terminal ID (TID) must be between 1 and 65,535.
Action | Enter a valid TID number.

REV00297 | Invalid TID specified
Explanation | An invalid terminal ID (TID) was specified.
Action | Enter a valid TID number.

REV00299 | Function has been discontinued
Explanation | The current version of Adabas Review no longer supports the requested function.
Action | Refer to the Adabas Review User documentation for a list of available features and functions.

REV00300 | Report not on file
Explanation | The requested report definition could not be found in the Adabas Review data file.
Action | This message is for information only.

REV00301 | No OP summary information available
Explanation | No OP summary information was available for the report specified.
Action | This message is for information only.

REV00306 | First field cannot be a buffer segment
Explanation | A DB report was defined with the first field as a buffer segment (FBSEG01, RBSEG01 ETC). The first field cannot be a buffer segment.
Action | Make another field the first field.

REV00307 | No resident PGMLIB defined
Explanation | A request was made to view a list of programs in the resident program library buffer, but none were defined to Com-plete.
Action | This message is for information only.

REV00308 | No resident programs defined
Explanation | A request was made to view a list of programs in the resident programs, but none where defined to Com-plete.
Action | This message is for information only.

REV00309 | Unable to locate Adabas IDTH
Explanation | Adabas Review was unable to locate the Adabas IDT header.
Action | Contact your Software AG technical support representative.

REV00310 | Unable to load ADALDI
Explanation | Adabas Review was unable to load the ADALDI text module from the Adabas TXTLIB.
Action | Verify that the Adabas TXTLIB is accessible from your z/VM machine.

REV00311 | Database dbid has been ignored
Explanation | The specified database has been ignored because an entry for the DBID was found in the IGNORE table in program N-IGNORE. No STATUS information is returned for this database.
Action | If STATUS information for the database should be returned, edit and STOW the program N-IGNORE.

REV00312 | Insufficient storage to reset stopwatch
Explanation | An attempt to reset the stopwatch was unsuccessful due to insufficient storage.
Action | Try again later.

REV00313 | Only 'ON' and 'OFF' are valid values
Explanation | A value other than ON or OFF was entered.
Action | Enter ON or OFF.

REV00314 | Command log data set switched
Explanation | The command log data set was switched successfully.
Action | This message is for information only.

REV00315 | Command logging is not active for report
Explanation | Adabas Review command logging is not active for the specified report.
Action | Choose a report that has command logging.

REV00316 | Invalid subpool ID
Explanation | The subpool ID specified was invalid.
Action | Select a valid subpool.

REV00317 | There are no transaction summary records
Explanation | A Response Time Report was requested but no transaction summary records exist for the selected report.
Action | This message is for information only.

REV00318 | There are no OP summary records
Explanation | A Response Time Report was requested but no OP summary records exist for the selected report.
Action | This message is for information only.

REV00319 | Too many "AND" fields in selection criteria
Explanation | The AND fields in the selection criteria have resulted in a data string that is too long for Adabas Review to process.
Action | Reduce the number of AND statements and resave the report.

REV00320 | Too many "OR" fields in selection criteria
Explanation | The OR fields in the selection criteria have resulted in a data string that is too long for Adabas Review to process.
Action | Reduce the number of OR statements and resave the report.

REV00321 | Target SVC cannot be greater than 255
Explanation | A value larger than allowed was entered in the SVC field of the target definition. The maximum value for this field is 255.
Action | Enter the correct SVC number.

REV00322 | User has already been canceled
Explanation | The user specified in the cancel function has already been canceled.
Action | This message is for information only.

REV00323 | TID terminal-id canceled
Explanation | The specified terminal ID has been canceled.
Action | This message is for information only.

REV00325 | TERMINAL terminal-name canceled
Explanation | The specified terminal has been canceled.
Action | This message is for information only.

REV00326 | TID terminal-id not found
Explanation | The terminal ID specified in the cancel, pick, or force function could not be found.
Action | This message is for information only.

REV00327 | User user-id not found
Explanation | The user specified in the cancel, pick, or force function could not be found.
Action | This message is for information only.

REV00328 | Terminal terminal-name not found
Explanation | The terminal name specified in the cancel, pick, or force function could not be found.
Action | This message is for information only.

REV00329 | Invalid TID specified
Explanation | The terminal ID number specified in the cancel, pick, or force function was not a valid numeric value.
Action | This message is for information only.

REV00330 | Response time report - report-name STARTED
Explanation | The specified Adabas Review response time report was successfully autostarted.
Action | This message is for information only.

REV00331 | No autostarted reports found to start
Explanation | No Adabas Review Response Time reports were found to autostart.
Action | This message is for information only.

REV00332 | One report has been autostarted
Explanation | Adabas Review has started one autostarted response time report.
Action | This message is for information only.

REV00333 | count reports have been autostarted
Explanation | Adabas Review started the specified number of autostarted response time reports.
Action | This message is for information only.

REV00334 | History task recovery from Adabas time-out
Explanation | The Adabas Review history interval task successfully recovered from an Adabas timeout (response code 9, ADARSP009).
Action | This message is for information only.

REV00335 | RNMH history task initializing in Natural
Explanation | The Adabas Review history interval task successfully invoked Natural and is initializing.
Action | This message is for information only.

REV00336 | History task terminating. Unable to locate RNMTAB
Explanation | The Adabas Review history interval task terminated because it was unable to locate RNMTAB.
Action | Check that RNMTAB has been defined to CICS as a resident PPT entry, and that RNMTAB is available to CICS.

REV00337 | History task terminating. Unable to load module-id
Explanation | The Adabas Review history interval task terminated because it was unable to locate the RNMCICS.
Action | Check that RNMCICS has been defined to CICS as a PPT entry and that RNMCICS is available to CICS.

REV00338 | History task terminating. Natural error error-number detected during initialization
Explanation | The Adabas Review history interval task terminated because it encountered a Natural error during initialization.
Action | Investigate the Natural error indicated, correct the problem, and restart the history subsystem.

REV00339 | History task terminating. NM data file has not been initialized
Explanation | The Adabas Review history interval task terminated because it detected that the Adabas Review Natural Monitor data file was not initialized.
Action | Verify that the INSTALL program has been executed to initialize the Adabas Review Natural Monitor data file.

REV00340 | History task terminating. Non-recoverable Natural error detected
Explanation | The Adabas Review history interval task terminated because it encountered an error in Natural from which it could not recover.
Action | Investigate the Natural error indicated, correct the problem, and restart the history subsystem.

REV00341 | History task terminating normally
Explanation | The Adabas Review history interval task terminated normally.
Action | This message is for information only.

REV00342 | History task terminating. Maximum reinitialization counter exceeded
Explanation | The Adabas Review history interval task terminated because the counter for maximum reinitializations was exceeded.
Action | Check messages sent to Adabas Review prior to this message to determine why the history task has reinitialized so many times.

REV00343 | History task terminating
Explanation | The Adabas Review history interval task terminated.
Action | Check other Adabas Review messages issued prior to this message to determine if an error condition was encountered.

REV00344 | TID terminal-id canceled by user-id at terminal terminal-name
Explanation | The user with the specified terminal ID was canceled by another user at another terminal.
Action | This message is for information only.

REV00345 | User user-id canceled by user-id at terminal terminal-name
Explanation | The user with the specified user ID was canceled by another user at another terminal.
Action | This message is for information only.

REV00346 | Terminal terminal-name canceled by user-id at terminal terminal-name
Explanation | The terminal with the specified name was canceled by another user at another terminal.
Action | This message is for information only.

REV00347 | TID terminal-id forced
Explanation | The user with the specified terminal ID was forced.
Action | This message is for information only.

REV00348 | User user-id forced
Explanation | The user with the specified user ID was forced.
Action | This message is for information only.

REV00349 | Terminal terminal-name forced
Explanation | The terminal with the specified name was forced.
Action | This message is for information only.

REV00350 | TID terminal-id forced by user-id at terminal terminal-name
Explanation | The user with the specified terminal ID was forced by another user at another terminal.
Action | This message is for information only.

REV00351 | User user-id forced by user-id at terminal terminal-name
Explanation | The user with the specified user ID was forced by another user at another terminal.
Action | This message is for information only.

REV00352 | Terminal terminal-name forced by user-id at terminal terminal-name
Explanation | The terminal with the specified name was forced by another user at another terminal.
Action | This message is for information only.

REV00353 | User must be canceled before force
Explanation | A CANCEL command must be issued for a user before a FORCE command can be issued.
Action | This message is for information only.

REV00354 | Invalid autostart option
Explanation | An invalid response time report autostart option was specified. The value must be "Y" or "N".
Action | Specify valid value.

REV00355 | Invalid history refresh option
Explanation | An invalid response time report history refresh option was specified. The value must be "Y" or "N".
Action | Specify a valid value.

REV00356 | Value must be in range range-start through range-end
Explanation | The value specified is invalid for the field. Valid values are denoted by <range-start> through <range-end> in the message.
Action | Specify a valid value in the range specified.

REV00357 | History task terminating. Review NM incorrectly installed
Explanation | The Adabas Review history interval task terminated because it was unable to verify that the Adabas Review Natural Monitor code was correctly linked with the Natural nucleus.
Action | Verify that the Adabas Review NM code is correctly linked with the Natural nucleus.

REV00359 | Report definition has been copied
Explanation | The request to copy a report definition was successful.
Action | This message is for information only.

REV00360 | Review repository not available
Explanation | An Adabas response code 148 (ADARSP148) was received while trying to store information in an Adabas Review repository.
Action | Insure that the database ID and file number are correct and that the database is available.

REV00361 | Database dbid inactive or invalid. Type 'TECH' for reason
Explanation | The user attempted to perform an Adabas Review function against a database that was inactive, did not have Adabas Review installed, or was not running a compatible version of Adabas Review.
Action | From the Database System menu, type TECH to determine why the current Adabas Review database is invalid and correct the error.

REV00362 | Review is not installed in database dbid
Explanation | Using the DBID= command, the user attempted to change the Adabas Review database being accessed. The database selected did not have Adabas Review installed.
Action | Verify that the database specified in the DBID= command is a valid Adabas Review database.

REV00363 | Database dbid is not active
Explanation | Using the DBID= command, the user attempted to change the Adabas Review database being accessed. The database selected was not active (Adabas response code 148, ADARSP148).
Action | Verify that the database specified in the DBID= command is a valid Adabas Review database and that it is active.

REV00364 | Database dbid is below Review V3.4
Explanation | Using the DBID= command, the user attempted to change the Adabas Review database being accessed. The database selected has an invalid version of Adabas Review installed.
Action | Verify that the database specified in the DBID= command is a valid Adabas Review database.

REV00365 | Response code rsp received accessing DBID dbid
Explanation | Using the DBID= command, the user attempted to change the Adabas Review database being accessed. The user received the indicated response code.
Action | Verify that the database specified in the DBID= command is a valid Adabas Review database.

REV00366 | TECH command only available from the DB system main menu
Explanation | The user attempted to executed the TECH command from an Adabas Review panel other than the Database System menu. The Adabas Review TECH command is only executable from the Database System menu.
Action | Execute the TECH command from the Database System menu.

REV00367 | Display program does not match report
Explanation | A VIEW or VW command terminated because the display program invoked was generated for a different report.
Action | Regenerate the display program for the report that failed using the RG function of the List Reports screen.

REV00368 | Parentheses are required for a list or range
Explanation | A list or range of values was entered without parentheses into a processing rule.
Action | Include the values within parentheses.

REV00369 | Unpaired parentheses
Explanation | The number of opening and closing parentheses are unequal.
Action | Include a closing parentheses for each opening parentheses.

REV00370 | Invalid HELP command
Explanation | An invalid command was entered into the command line of a help screen.
Action | Enter a valid command or press a valid PF key.

REV00371 | GENAUTO is not available in CMS
Explanation | A GENAUTO (or GA) command was entered but is not implemented in z/VM.
Action | This message is for information only.

REV00372 | Download is invalid from this screen
Explanation | DOWNLOAD (or DL) was entered from a screen where the DOWNLOAD command is invalid.
Action | Enter DL into the SEL column of the List Started Reports screen.

REV00373 | MAX K must be at least n K
Explanation | The MAX K value specified in the report options must be at least 4K for z/OS and z/VSE and at least 8K for BS2000.
Action | Specify a value for MAX K that is at least the minimum.

REV00374 | WRAPPING=Y only allowed on sequence reports
Explanation | The WRAPPING value can only be set to "Y" for a SUMMARY report with SEQUENCE as the first display field.
Action | Only specify WRAPPING=Y for SUMMARY reports with SEQUENCE as the first field.

REV00375 | Invalid page size - must be 1-255
Explanation | The page size entered on the Report Options screen is invalid. The value must be between 1 and 255.
Action | Enter a valid page size.

REV00385 | Value must be greater than 0.
Explanation | The value must be greater than 0.
Action | This message is for information only.

REV00386 | FNR must be between 1 and 254
Explanation | An attempt was made to change the FNR number to less than 1 or greater than 254.
Action | Enter a FNR number in the range of 1 to 254.

REV00388 | Invalid line size - must be 72-255
Explanation | The line size entered on the Report Options screen is invalid. The value must be between 72 and 255.
Action | Enter a valid line size.

REV00390 | List not sorted due to excessive report data
Explanation | The expanded list of history report occurrences could not be sorted because the resulting ISN list was too large. The list is displayed unsorted.
Action | Increase the value in the LS ADARUN parameter.

REV00391 | History report compression complete
Explanation | The request to compress a history report completed successfully.
Action | This message is for information only.

REV00392 | File is in use by another compression process
Explanation | An attempt was made to compress a history report but another report was being compressed at the time. This message can also occur if a CH function did not complete successfully.
Action | If another report is being compressed, wait until it completes and try again. If a CH function failed, you must run the RESET function. To run the RESET function: Enter RESET HISTORY FILE on the command line of the DB System menu. Follow the instructions on the screen.

REV00393 | Compression will not be performed
Explanation | A reply of "N" was given in response to the confirmation prompt prior to compressing a history report.
Action | This message is for information only.

REV00394 | History file does not need resetting
Explanation | A request to reset the history file was made but the file does not need resetting.
Action | This message is for information only.

REV00395 | History file has been reset
Explanation | This confirms that the history file has been reset. This essentially unlocks the lock that was placed on the file during a CH function.
Action | None if the message says HISTORY FILE HAS BEEN RESET. If the message also says DATA WAS LOST, restore the history file to a state prior to when the failing CH function was performed.

REV00396 | Duplicate field in "AND" expression
Explanation | A logical "AND" expression contains a duplicate field name in a processing rule. When using "AND" to connect fields, each field name can be used only once per expression.
Action | Remove the duplicate field name from the expression.

REV00397 | Target DBID has been changed
Explanation | The target DBID has been successfully changed for the report definition.
Action | This message is for information only.

REV00398 | Bufferpool reports cannot be printed or downloaded
Explanation | The graphical bufferpool reports cannot be downloaded or printed: they may only be viewed.
Action | Use the VW command to view the report.

REV00399 | AA is not available in VM/CMS
Explanation | The AA function is not available in z/VM.
Action | This message is for information only.

REV00400 | Non zero response from target = nnn
Explanation | A non-zero response code was returned from the specified target.
Action | Determine why the non-zero response code occurred.

REV00401 | Report defaults were saved
Explanation | The report defaults were saved successfully.
Action | No action is required for this informational message.

REV00402 | No matching reports to generate
Explanation | GENAUTO was started in local mode, but there are no autostarted reports with DBID-TO-MONITOR set to the local DBID. No autostarted reports will be generated.
Action | No action is required for this informational message.

REV00403 | Update completed
Explanation | The report options were updated successfully.
Action | No action is required for this informational message.

REV00404 | No changes to update
Explanation | A request to update reports was unnecessary because no changes were made.
Action | No action is required for this informational message.

REV00405 | Cannot start a rpt that monitors a hub
Explanation | A request to start a report was unsuccessful because the DBID-TO-MONITOR was set to the Adabas Review hub ID. Adabas Review reports can only monitor Adabas targets.
Action | Correct the report and retry.

REV00406 | Only one buffer segment allowed per report
Explanation | More than one buffer segment was defined in a report. Only one buffer segment per report is allowed.
Action | Correct the report and retry.

REV00407 | There are no history records to convert
Explanation | An attempt was made to convert history records, but there are no history records to convert.
Action | No action is required for this informational message.

REV00408 | Only 1 order field allowed with sum exit
Explanation | A summary exit was specified, but more than one order field was chosen for the report. Summary exit reports are limited to one (1) order field.
Action | Reduce the number of order fields to 1.

REV00409 | Pulse report cannot be purged
Explanation | A request was made to purge the Pulse report. The Pulse report cannot be purged.
Action | No action is required for this informational message.

REV00410 | Report defaults not saved
Explanation | A user canceled a prompt to confirm the saving of report defaults.
Action | No action is required for this informational message.

REV00411 | xxxxxxxx cannot be edited
Explanation | The EP command was used to edit a display program, but the display program is for a fixed format report. Since these programs are specific, not dynamic, no source code is available to the user.
Action | No action is required for this informational message.

REV00412 | NUCID nnnnn is not available
Explanation | An attempt was made to change the nucleus ID with which Adabas Review communicates, but the requested nucleus ID was not available.
Action | Enter the NUC LIST command to obtain a list of available nucleus IDs and try again.

REV00413 | NUCID only valid for cluster databases
Explanation | A user executed the NUCID or NUC LIST command for a non-cluster database.
Action | No action is required for this informational message.

REV00414 | Duplicate field names not allowed
Explanation | Two or more fields with the same name were entered on the ER screen. This is not allowed.
Action | Remove the duplicate fields.

REV00415 | Detail printer not available
Explanation | A request to start a detail report failed because there was no detail printer available.
Action | Delete another detail report first or provide more printers in the startup JCL. Then try again.

REV00416 | Invalid data in rules value
Explanation | An invalid character was entered into a processing rules value.
Action | Remove the invalid character from the rules value and try again.

REV00417 | Pulse interval must not be greater than 1440
Explanation | The pulse interval was incorrectly specified for a Pulse report.
Action | Specify a value between 1 and 1440 and try again.

REV00418 | Display program is not delivered in source form
Explanation | An attempt to edit the display program BUFFPOOL, PU-00001 or CS-00001 failed because it is not delivered as source.
Action | No action is required for this informational message.

REV00419 | List size exceeded
Explanation | The maximum list size of 10 has been exceeded in a processing rule.
Action | Limit the list size to 10 and try again.

REV00420 | Unable to obtain SVC list
Explanation | An AA command was issued, but the list of SVCs cannot be accessed.
Action | Make certain that ADATMZ exists and is accessible from the current Adabas Review hub or database. Then try again.

REV00421 | There are no targets for this SVC
Explanation | After an AA command, an SVC was selected, but there are not targets available for that SVC.
Action | No action is required for this informational message.

REV00422 | Only order fields are allowed for detailed reports
Explanation | SUM, MIN, MAX, AVG, or ROUND were selected on the Edit Reports screen, but the report is a detailed report. ORDER is the only valid entry for a detailed report.
Action | Remove the invalid entries and try again.

REV00423 | Report type changed -- defaults were reset
Explanation | While editing a report, the detail/summary report type was changed. Each report type requires its own set of default report options. The default report options for the new report type have now been loaded.
Action | No action is required for this informational message. Press PF2 to make any necessary changes to the report options.

REV00424 | Unable to retrieve data from target nnnnn
Explanation | For reasons unknown to Adabas Review, the requested target was unable to supply AA information.
Action | No action is required for this informational message.

REV00425 | Parameter input is missing or invalid
Explanation | The expected parameter input was either missing or has invalid data.
Action | Correct the input data and try again.

REV00426 | Value for keyword is missing or invalid.
Explanation | The parameter input for a keyword was either missing or has invalid data.
Action | Correct the keyword input and try again.

REV00427 | {TARGET|DBID|FILE} is not available
Explanation | The parameter input for a SET command keyword refers to an unavailable destination.
Action | Correct the keyword data or make sure the destination is available.

REV00428 | {TARGET ID|DBID|FILE} has been set to nnnnn
Explanation | A SET command changed the target ID, database ID, or file successfully.
Action | No action is required for this informational message.

REV00429 | SET program has terminated with errors
Explanation | The SET program encountered errors. The error will have been more clearly identified in a previous message.
Action | Correct the error and try again.

REV00430 | More than 256 target definitions on file
Explanation | The maximum number of target definitions has been exceeded.
Action | Limit the number of targets to 256.

REV00431 | Cannot save report due to error
Explanation | An attempt to save a report was unsuccessful because there was an error in the report definition.
Action | Correct the report definition and try again.

REV00432 | There are no REVIEW hubs running on SVC nnn
Explanation | The AH (Available Review Hubs) command was entered but there are no hubs running in the current SVC to display.
Action | No action is required for this informational message.

REV00433 | ADATMZ cannot be loaded
Explanation | Upon initialization, SYSREVDB calls a program named ADATMZ. This program was not available.
Action | Make certain ADATMZ is installed and available to SYSREVDB. If you are running Adabas Review in a CICS environment, verify that ACITMZ is installed. For more information, read the Adabas Review installation documentation. If the problem persists, contact your Software AG technical support representative.

REV00434 | ADATMZ: message-text
Explanation | Upon initialization, SYSREVDB calls a program named ADATMZ. One of the following messages (message-text) is included in the message and describes the error that has occurred with ADATMZ.
Message Text | Explanation | Action
--- | --- | ---
No Adabas SVCs found | An internal error has occurred. | Contact your Software AG technical support representative for assistance.
No active targets for an SVC
IDTHE appears to be invalid
Invalid or unknown function
Caller has answer area no answer count
GETMAIN for SVC table failed
GETMAIN for target table failed
Load of link routine failed | ADATMZ dynamically loads ADALNKR. If ADALNKR cannot be loaded, subsequent calls to ADATMZ can cause this problem. | Be sure that the ADATMZ and ADALNKR modules, which are available in the Adabas or WAL load libraries, are all available for the TP monitor.
Load of CCSTCK routine failed | ADATMZ dynamically loads CCSTCK. If CCSTCK cannot be loaded, subsequent calls to ADATMZ can cause this problem. | Be sure that the ADATMZ and CCSTCK modules, which are available in the Adabas or WAL load libraries, are all available for the TP monitor.
Initialization call to DEPRTR failed | An internal error has occurred. | Contact your Software AG technical support representative for assistance.
No SVC table address provided by caller
SVC table address inconsistent with PAL
No SVC count provided by caller
Invalid SVC number too low | The version of ADATMZ that was loaded is too low. | Install the current version of ADATMZ. Contact your Software AG technical support representative for assistance.
Invalid SVC number too high | The version of ADATMZ that was loaded is too high. | Install the current version of ADATMZ. Contact your Software AG technical support representative for assistance.
No SVC tbladdr on get target call | An internal error has occurred. | Contact your Software AG technical support representative for assistance.
No target tbladdr on get target call
No target table length

REV00435 | Buffer Pool reports cannot have DBID=ALL
Explanation | A value of "ALL" was specified as the DBID to monitor while attempting to start a report. Buffer Pool reports must only collect data from a single database, specifying "ALL" for them is not allowed. The report will not be started.
Action | Specify a numeric DBID for the Buffer Pool report.

REV00436 | Invalid field for client report
Explanation | A reporting field was referenced in a client report that was not valid for client reports. Client reports have a restricted set of available fields. A complete list of these fields is provided in ????
Action | Specify a valid field name.

REV00437 | The maximum number of fields has been selected
Explanation | While selecting fields for a report using the online field selection screens, the maximum allowable number of fields you can select has been reached. All fields selected beyond the maximum are ignored.
Action | Specify fewer fields, ensuring that only the most important fields are selected.

REV00438 | Invalid field for a database report
Explanation | A client reporting field was referenced in a database report. This field is only permitted in a client report.
Action | Specify a valid field name.

REV00439 | Warning: A client report has been started. If client monitoring is not turned on, no client monitoring will be collected. Press ENTER to exit
Explanation | This message appears in a pop-up box whenever a client report is started. It warns you that if client reporting has not been started, no client reporting data will be collected.
Action | No action is required for this informational message. Press the ENTER key to remove the pop-up box containing the message.

REV00440 | Redisplay buffer full - Redisplay unavailable
Explanation | The Redisplay function is unavailable because more than 5000 lines were displayed.
Action | As a workaround, the report data can be printed using the HC command and other tools might be used to scroll through that output.

REV00441 | Report name cannot be 'ALL'
Explanation | The name "ALL" was used as a report name in the report definition editor. The word "ALL" is reserved in Adabas Review and cannot be used as a report name.
Action | Specify a different name.

REV00442 | The display program has not been generated yet
Explanation | An attempt was made to edit the display program for a report but the display program has not yet been generated. This is most likely due to having copied a report where the display program name shows as "NEED RG" or "NEED RU".
Action | Enter RG or RU on the command line to generate the display program.

REV00443 | Userid is required
Explanation | User profiles require a unique user or group ID in the User ID / Group ID field. You cannot create a user profile without one.
Action | Specify a valid user or group ID for the user profile. Valid user or group IDs are eight alphanumeric characters long and begin with either a letter or a national ($, @, or #) character.

REV00444 | Group must be "Y" or "N"
Explanation | The setting for the Group access rule in the user profile definition is not "Y" (yes) or "N" (no). These are the only valid values for the field.
Action | Specify either "Y" or "N" for the Group access rule.

REV00445 | Description is required
Explanation | User profiles require a description in the Description field.
Action | Specify up to 20 alphanumeric characters for the description.

REV00446 | At least one report type must be "Y" for "EDIT REPORTS=Y"
Explanation | When the Edit Reports? access rule in a profile is set to "Y", at least one of the other edit report access rules must also be set to "Y". The other edit report access rules are Edit Bufferpool Reports?, Edit Client Reports?, Edit Cluster Reports?, Edit Database Reports?, and Edit Pulse Reports?.
Action | Either set the Edit Reports? access rule to "N" or specify "Y" for one of the other edit report access rules.

REV00447 | All report types must be "N" for "EDIT REPORTS=N"'
Explanation | When the Edit Reports? access rule in a profile is set to "N", none of the other edit report access rules may be set to "Y". The other edit report access rules are Edit Bufferpool Reports?, Edit Client Reports?, Edit Cluster Reports?, Edit Database Reports?, and Edit Pulse Reports?.
Action | Either set the Edit Reports? access rule to "Y" or specify "N" for all of the other edit report access rules.

REV00448 | Cannot save - This is the only Administrator profile
Explanation | An attempt has been made to alter and save the only administrator profile so that it is no longer an administrator profile. Adabas Review will not allow you to turn the default profile or any administrator profile into a non-administrator profile if another administrator profile is not available.
Action | If you intend to change the only administrator profile to a non-administrator profile, first create another administrator profile. You can then alter and save the original administrator profile as you wish.

REV00449 | Cannot purge - This is the only administrator profile
Explanation | An attempt has been made to delete the only administrator profile so that there is no longer an administrator profile. Adabas Review will not allow you to delete an administrator profile if another administrator profile is not available.
Action | If you intend to delete this administrator profile, first create another administrator profile. You can then delete the original administrator profile.

REV00450 | Monitor DBID dbid prohibited by profile
Explanation | An attempt has been made to create, start or alter a report for a DBID that is not included in the DBID list of your user profile.
Action | Contact your system administrator to change your user profile or change the DBID you are trying to monitor in the report.

REV00451 | User profiling is already installed
Explanation | An attempt was made to install the user profiling system when it is already installed.
Action | No action is necessary for this informational message.

REV00453 | You must enter at least one DBID
Explanation | When editing an Adabas Review user profile, the option Monitor All Targets? was set to "N", however, a DBID was not specified. At least one DBID must be specified if this option is set to "N".
Action | Specify at least one DBID or set Monitor All Targets? to "Y".

REV0454 | Profile reset to default values
Explanation | All values for the user profile you are viewing have been reset to the factory values.
Action | No action is required for this informational message.

REV00455 | Group must be 'Y' or 'N'
Explanation | An invalid or blank value was entered in the Group Profile? option of the user profile. This option must be set to either "Y" or "N".
Action | Specify a valid value for the Group Profile? option.

REV00456 | Info: Both "ALL TARGETS" and specific DBIDs are defined
Explanation | The user profile option Monitor All Targets? was set to Y but there are DBIDs listed. This is perfectly valid; in this case, the listed DBIDs have no effect on processing. However, if you later set the option to "N", the listed DBIDs will become the only valid DBIDs for the user.
Action | No action is necessary for this informational message.

REV00457 | Invalid user ID
Explanation | The user ID entered on the user profile screen is invalid. User IDs must begin with a letter followed by any combination of alphanumeric or national (@#$) characters.
Action | Specify a valid user ID.

REV00458 | Review Client engine status has been turned {ON |OFF}
Explanation | The Review Client status was toggled either on or off, as shown in the message.
Action | No action is required for this informational message.

REV00459 | Review exit 2 is not installed
Explanation | While using the CM function, a call to communicate with client monitoring has determined that REVEXIT2 is not properly installed.
Action | Verify that the installation of REVEXIT2 has been performed correctly. For more information, refer to your Adabas Review (Phase 2) installation documentation.

REV00460 | Review exit 2 is not active
Explanation | While using the CM function, a call to communicate with client monitoring has determined that REVEXIT2 is not active. It is possible to have REVEXIT2 linked into the link routine but not have it set to active in the LNKGBLS tables.
Action | Verify that the installation of REVEXIT2 has been performed correctly. For more information, refer to your Adabas Review (Phase 2) installation documentation.

REV00461 | Response nnn received from REVEXIT2
Explanation | While using the CM function, a non-zero response code was returned from REVEXIT2. This is rare.
Action | Verify that the installation of REVEXIT2 has been performed correctly. For more information, refer to your Adabas Review (Phase 2) installation documentation. If you need additional assistance, contact your Software AG support representative.

REV00462 | Ending apostrophe missing
Explanation | While editing the report processing rules for a report, an argument was specified with unpaired apostrophes.
Action | Correct the argument syntax and try again.

REV00463 | Ending apostrophe incorrectly placed
Explanation | While editing the report processing rules for a report, an apostrophe was incorrectly used.
Action | Correct the syntax and try again.

REV00464 | The maximum number of fields has been selected
Explanation | The maximum field limit has been reached. You cannot select any more fields.
Action | Evaluate the fields you have selected, removing ones you don't really need and adding ones you do, but be sure to stay within the maximum field limit.

REV00465 | Unable to obtain SVC list
Explanation | While trying to use the AA function, the Adabas Review nucleus was unable to obtain the list of available SVCs on the current LPAR.
Action | Verify your Adabas Review installation is correct. If the problem persists, contact your Software AG support representative for assistance.

REV00466 | Report option defaults converted successfully
Explanation | While editing a preexisting report after upgrading Adabas Review from version 4.4, the report defaults were converted to the current standard.
Action | No action is required for this informational message.

REV00467 | Invalid character in field name
Explanation | While editing a report, an invalid character was used in one of the field names.
Action | Correct the field name syntax and try again.

REV00468 | Cannot EC a non-client report
Explanation | An attempt was made to edit a non-client report using the EC command. The EC command only edits client reports.
Action | Use the ER command to edit a non-client report.

REV00469 | Command line entries are not valid here
Explanation | When entering Adabas Review for the first time after upgrading from a previous version, a user profile conversion takes place. The only actions allowed are on the screen. Command line entries are not allowed for this special one-time event.
Action | Do not enter data on the command line while this conversion is taking place.

REV00470 | NUCID only valid in local mode
Explanation | The NUCID command was used but SYSREVDB is currently communicating with an Adabas Review hub. The NUCID command is only valid when SYSREVDB is communicating with a local mode target.
Action | Do no use the NUCID command in hub mode.

REV00471 | No NUCID was selected
Explanation | PF5 was pressed on a NUCID list screen but no NUCID was selected.
Action | Select a NUCID or use PF3 to exit the NUCID screen.

REV00472 | NUCID has been changed
Explanation | Upon request, the NUCID was successfully changed.
Action | No action is required for this informational message.

REV00473 | CM function only available in hub mode
Explanation | An attempt to turn on the client report engine using the CM command was made in local mode. The CM command is available only in hub mode.
Action | Operate Adabas Review in hub mode before attempting to start the client reporting engine.

REV00474 | Parameter missing or invalid
Explanation | The required NAME parameter was omitted or invalid when using the batch Natural Review program COPYREP.
Action | Add or correct the parameter and rerun the job.

REV00475 | Parameter is missing or invalid
Explanation | The required NEWNAME parameter was omitted or invalid when using the batch Natural Review program COPYREP.
Action | Add or correct the parameter and rerun the job.

REV00476 | Invalid parameter specified
Explanation | When using a batch Natural Review program, an unknown or invalid parameter keyword was specified.
Action | Correct the error and rerun the job.

REV00477 | STACKPARM= is incorrectly specified
Explanation | The optional STACKPARM parameter was incorrectly specified when using the batch Natural Review program COPYREP.
Action | Correct the error and rerun the job.

REV00478 | NAME= and NEWNAME= parameters are required
Explanation | While using the batch Natural Review program COPYREP, both of the required parameters NAME= AND NEWNAME= were missing.
Action | Supply the correct parameters and rerun the job.

REV00479 | Undefined keyword in input
Explanation | When using the batch Natural Review program COPYREP, an unknown parameter keyword was specified. Valid keywords are NAME, NEWNAME, STACKPARM and GO=YES.
Action | Supply only valid parameters and rerun the job.

REV00480 | Words in report names must be separated by periods
Explanation | While using a batch Natural Review program that requires a report name as input, the report name did not have periods between each word. This is required to allow Natural to pass the parameters to the Adabas Review program correctly.
Action | Always place periods between words in report names. Correct the specification and rerun the job.

REV00481 | Report already exists
Explanation | The new report name specified in the batch Natural Review program COPYREP already exists. COPYREP will not overwrite an existing report; instead it terminates with response code 12.
Action | Specify a unique name for the new report name or delete the report definition that already exists.

REV00482 | Report definition has been purged
Explanation | This message confirms that the request to purge a report definition was successful.
Action | No action is necessary for this informational message.

REV00483 | GO= parameter is incorrectly specified
Explanation | The GO= parameter specified in the batch Natural Review program COPYREP is specified incorrectly. The only valid syntax for this parameter is GO=YES.
Action | Correct the error and rerun the job.

REV00484 | INVALID COST OPERATOR
Explanation | An invalid cost operator was entered on the Edit Report screen. Valid cost operators are: "+": Plus -- add the cost factor to the field value. "-": Minus -- subtract the cost factor from the field value. "*": Multiply -- multiply the field value by the cost factor. "@": Fixed -- apply a fixed cost to each command select by the report.
Action | Enter a valid cost operator if you want to use the cost feature.

REV00485 | COST FACTOR REQUIRED IF OPERATOR IS PROVIDED
Explanation | A cost operator was entered on the Edit Report screen but no cost factor was provided. Both an operator and a cost factor must be specified to use the cost feature.
Action | Specify a cost factor for the field in addition to the operator or remove the cost operator from the field specification on the Edit Report screen.

REV00486 | COST OPERATOR REQUIRED IF FACTOR IS PROVIDED
Explanation | A cost factor was entered on the Edit Report screen but no cost operator was provided. Both an operator and a cost factor must be specified to use the cost feature.
Action | Specify a cost operator for the field in addition to the cost factor or remove the cost factor from the field specification on the Edit Report screen.

REV00487 | COST FACTOR MUST BE A POSITIVE VALUE
Explanation | A cost factor was provided on the Edit Report screen but the value is zero or negative. The values must be a positive or negative integer. Negative values can only be specified if the cost operator is "*" or "@".
Action | Specify a valid cost factor and try again.

REV00488 | COST FACTOR IS NOT NUMERIC
Explanation | A cost factor was entered on the Edit Report screen that was not numeric. Only numeric values are valid.
Action | Specify a numeric value for the cost factor.

REV00489 | ERROR WHILE TRYING TO RECATALOG USER EXIT
Explanation | During the first invocation of Adabas Review after a new installation or upgrade, an error occurred compiling and cataloging a user exit. The reason for the error cannot be determined.
Action | If the problem persists, examine and correct any user written exits. If no user exit has been written or modified, contact your Software AG technical support representative.

REV00490 | COST FACTOR can only have 7 numeric digits
Explanation | A COST factor was entered on the Edit Report screen with eight numeric numbers and no decimal points. The maximum number of numeric digits is seven.
Action | Enter a value with no more than seven numeric digits. You may place a decimal point anywhere in the field if desired.

REV00491 | COST OPERATOR '@' CAN ONLY BE USED FOR THE 'COMMANDS' FIELD
Explanation | A COST factor was entered on the Edit Report screen for the field COMMANDS but the operator was not the " @ " operator. The only operator allowed for the field COMMANDS is " @ ", indicating a FIXED cost. No other reporting field may use the " @ " operator.
Action | Either change the field name to something other than COMMANDS or change the Cost operator to " @ " and try again.

REV00492 | COST IS ONLY VALID FOR SUM FIELDS
Explanation | A COST factor was entered into the ER screen for a field that is not a summary field. If the field does not have the SUM slot checked then COST is not possible.
Action | Correct the ER screen and try again.

REV00493 | THIS FIELD IS NOT ALLOWED FOR DETAIL REPORTS
Explanation | A field was entered on the ER screen for a detail report that can only be used in a summary report.
Action | Remove the offending field.

REV00494 | TARGET NAME MUST NOT BE BLANK
Explanation | The Target Name field must contain an alpha-numeric value. The field must not be all blanks.
Action | Enter a valid Target Name.

REV00495 | REVIEW COMMANDS MUST BE 'Y' OR 'N'
Explanation | The Review Commands fields must contain a "Y" or an "N". All other values, including blank are invalid.
Action | Enter "Y" or "N".

REV00496 | INVALID SYNTAX IN START PARAMETERS
Explanation | The Review command `START` or `ST` was entered into the command line to start an online report. The parameter data following the `START` command contained invalid syntax.
Action | Correct the error and re-submit.

REV00497 | DBID VALUE IS NOT VALID
Explanation | The Review command `START` or `ST` was entered along with a `DBID` parameter. The `DBID` parameter data contains invalid syntax.
Action | Correct the error and re-submit.

REV00498 | DBID KEYWORD MUST BE FOLLOWED BY "="
Explanation | The Review command `START` or `ST` was entered along with a `DBID` keyword. The `DBID` keyword must be followed by an equal sign (=). The equal sign was either missing or was an incorrect character.
Action | Correct the error and re-submit.

REV00499 | DBID KEYWORD MUST BE PRECEEDED BY ","
Explanation | The Review command `START` or `ST` was entered along with a `DBID` keyword. The `DBID` keyword must be preceded by a comma. The comma was either missing or was an incorrect character.
Action | Correct the error and re-submit.

REV00500 | INVALID NUCID
Explanation | In LOCAL mode within a cluster environment, an attempt was made to alter the current nucleus ID, but the value entered was not valid. Valid values are 1 through 65535. Only numeric characters are allowed.
Action | Re-enter the nucleus ID using a valid value.

REV00501 | CHANGE DBID PARAMETER ERROR(S)
Explanation | During a `CHANGE DBID FROM` operation, one or more parameter values were incorrect.
Action | Re-enter the `CHANGE DBID` command using valid values.

REV00502 | INVALID INPUT PARAMETER(S)
Explanation | During a `CHANGE DBID FROM` operation, one or more parameter values were incorrect.
Action | Re-enter the `CHANGE DBID` command using valid values.

REV00503 | FROM DBID IS INVALID
Explanation | During a `CHANGE DBID FROM` operation, the `FROM DBID` value was not valid. Valid values are 1-65535, ALL or NONE.
Action | Re-enter the `CHANGE DBID` command using valid values.

REV00504 | INVALID DBID VALUE
Explanation | During a `CHANGE DBID FROM` operation, one or more of the DBID values were not valid. Valid values are 1-65535, ALL or NONE.
Action | Re-enter the `CHANGE DBID` command using valid values.

REV00505 | FROM AND TO DBID CANNOT BE THE SAME
Explanation | During a `CHANGE DBID FROM` operation, both DBID values were identical. The values must be different.
Action | Re-enter the `CHANGE DBID` command using valid values.

REV00506 | NO DBID(S) WERE CHANGED
Explanation | During a `CHANGE DBID FROM` operation, no DBIDs were found that match the `FROM` value.
Action | No action is required for this informational message.

REV00507 | 1 DBID HAS BEEN UPDATED
Explanation | During a `CHANGE DBID FROM` operation, one DBID was found that matched the `FROM` value and was updated with the `TO` value.
Action | No action is required for this informational message.

REV00508 | nnn DBIDS HAVE BEEN UPDATED
Explanation | During a `CHANGE DBID FROM` operation, multiple DBIDs were found that matched the `FROM` value and were updated with the `TO` value. nnn will show the number of reports updated.
Action | No action is required for this informational message.

REV00509 | Invalid parameter for "ZIIP" command
Explanation | During a `CHANGE DBID FROM` operation, multiple DBIDs were found that matched the `FROM` value and were updated with the `TO` value.
Action | No action is required for this informational message.

REV00510 | Review started with ZIIP=NO, zIIP disabled
Explanation | zIIP is installed, but Adabas Review was started with ZIIP=NO. The zIIP interface is disabled and cannot be turned on online, while Adabas Review is running.
Action | Start Adabas Review with ZIIP=YES.

REV00511 | zIIP not installed
Explanation | An attempt to read the zIIP status returned a blank return character, indicating that zIIP is not installed.
Action | Install Adabas Review zIIP.

REV00512 | Unkown data getting zIIP state: X
Explanation | An attempt to read the zIIP status returned an unkown return character for the zIIP state.
Action | Contact Software AG support.

REV00513 | zIIP already switched on
Explanation | The command ZIIP=YES was issued, but zIIP is already active. zIIP state did not change.
Action | No action is required for this informational message.

REV00514 | zIIP switched on
Explanation | The command ZIIP=YES was issued and zIIP was switched from inactive to active.
Action | No action is required for this informational message.

REV00515 | Rsp=402, zIIP not supported
Explanation | An attempt was made to switch the zIIP state, but zIIP is not supported.
Action | Install Adabas Review zIIP.

REV00516 | Unkown response code setting zIIP state: nnn
Explanation | An attempt was made to switch the zIIP state. But zIIP returned an uknown response code.
Action | Contact Software AG support.

REV00517 | zIIP already switched off
Explanation | The command ZIIP=NO was issued, but zIIP is already inactive. zIIP state did not change.
Action | No action is required for this informational message.

REV00518 | zIIP switched off
Explanation | The command ZIIP=NO was issued and zIIP was switched from active to inactive.
Action | No action is required for this informational message.

REV00519 | Display of "ZIIP" statistics not allowed
Explanation | The display of zIIP statistics is disabled in the SYSREVDB user profile settings.
Action | Enable zIIP statistics in the user profile.

REV00520 | Use of "ZIIP YES/NO" command not allowed
Explanation | The use of the ZIIP YES/NO command is disabled in the SYSREVDB user profile settings. ZIIP YES/NO changes the zIIP state (active/inactive).
Action | Enable ZIIP YES/NO command in the user profile.

REV00521 | "ZIIP" command not allowed in User Profile System.
Explanation | An attempt was made to switch the zIIP state, but zIIP is not supported
Action | Issue the command outside the User Profile System.

REV00522 | zIIP on Target must be Y(es) or N(o).
Explanation | The input value for the field "zIIP on Target" must be Y(es) or N(o). No means no zIIP clause will be generated in the parameters for autostarting. This equals to ZIIP=NO. Yes means ZIIP=YES will be generated.
Action | Enter correct value.

REV00523 | Function "RG" not available for this report type.
Explanation | Display programs for Buffer Pool reports (BUFFPOOL) or for Pulse Reports (PU-00001) cannot be generated. They are delivered.
Action | If missing, move a backup copy to SYSREVDB.

REV00524 | No targets are available for this SVC.
Explanation | On the Active Adabas SVCs screen, an SVC was selected but the SVC has no target associated with it.
Action | No action is required for this informational message.

REV00525 | Report and saved definition do not match; REFRESH/REGEN necessary.
Explanation | Before a VW/VX command is executed, the running report and the saved definition will be checked. This is done by comparing the Account Record Length. For a running report this value is returned from the IN command. For the saved definition this value is calculated. If the calculation is not possible, e.g. because a user-defined variable is missing, the check will be ignored and the VW/VX will be executed without check.
Action | Refresh the running report and/or regenerate the report and the display program with its original definition.

REV00526 | In local mode the DBID to monitor may be the local DBID only.
Explanation | Adabas Review running in local mode can collect data on its local DBID only. Thus the DBID-to-be-monitored and the local DBID must be the same. Use the HUB mode to monitor several different DBIDs.
Action | Enter the local DBID or ALL as DBID-to-be-monitored and/or update the report definition.

REV00527 | No NUCID found for TARGET dbid.
Explanation | An attempt to read NUCID(s) from a local DBID did not return any NUCID. Most probably the DBID is not a cluster. Or the Adabas call to read the NUCIDs failed.
Action | Enter the correct local TARGET DBID or check the Adabas cluster environment.

REV00528 | TARGET not initialized, set to default value dbid.
Explanation | The Adabas Review local or HUB TARGET dbid was not yet initialized, i.e. the value was 0. The TARGET has been set to the default value, derived from the REVIEW-DB dbid or the user profile.
Action | No action required if the TARGET is the desired one. Otherwise set the TARGET in advance with the batch Natural SET command.