Adabas Review 00xxx Messages

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.

If the message number is for an Adabas Review message, contact your Software AG technical support representative.

This message welcomes users to Adabas Review and indicates the environment under which they are running.

This message is for information only.

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.

Enter a valid command.

The Adabas Review program REVTAB is not available to CICS or is not permanently resident.

Make sure REVTAB is available and permanently resident.

Adabas Review is waiting for terminal input.

Press a valid PF key or enter an Adabas Review command.

An invalid command was entered into the Adabas Review command line.

Press a valid PF key or enter a valid Adabas Review command.

During Adabas Review initialization a series of messages are displayed. Adabas Review will pause whenever a page is full or on the last page.

Press ENTER.

Adabas Review has determined that there are no online systems available to the user. There are two possible causes:

1. the installation of Adabas Review has not been fully completed.

2. Adabas Review is installed, but your profile prohibits you from accessing the available systems.

Contact your Adabas Review administrator.

During Adabas Review initialization, the interval statistics profile record was created.

This message is for information only.

The request to save a report definition to the Adabas Review repository has completed successfully.

This message is for information only.

You are now viewing current data as opposed to historical data.

This message is for information only.

Either you have not been defined to Adabas Review, or you are not authorized to use Adabas Review.

Contact your Adabas Review administrator.

An attempt was made to edit/copy a report without a name.

Enter a name in the report name field.

An attempt was made to add a report without selecting any items to be used as report criteria.

Select one or more fields to be used as criteria by entering a number in its ORDER field.

A number greater that 20 was entered into one of the ORDER fields.

Enter a number between 1 and 20.

Duplicate ORDER numbers have been detected.

Enter a unique number in each ACCT ORDER to be included in the report.

You are now viewing historical data as opposed to current data.

This message is for information only.

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.

This message is for information only.

A detailed response time report was requested but there are no detail records for the selected report.

This message is for information only.

This indicates that a request to restart a report was not successful.

This message is for information only.

An invalid reply was given to an Adabas Review prompt.

Enter a valid reply.

This confirms that the purge report request was successful.

This message is for information only.

An attempt to access a report has failed because the report is not active.

This message is for information only.

An unknown return code was returned from the purge reports program due to an internal error.

If the problem reoccurs, contact your Software AG technical support representative.

This is the oldest historical snapshot; the NEXT command cannot be entered.

This message is for information only.

A reply was entered into an Adabas Review prompt field and a direct command was entered simultaneously.

Either answer the Adabas Review prompt or enter a direct command, but not both.

An invalid response was detected and Adabas Review is prompting the user with the correct response.

Enter a valid response.

This confirms that a request to activate or deactivate a report was successful.

This message is for information only.

An invalid reply was given in response to an Adabas Review prompt that requires a reply of either yes ("Y") or no ("N").

Reply "Y" or "N".

The value entered was not within the range 0 and 100.

Enter a value between 0 and 100.

A selection was marked on a line that does not have a value or any data to select.

Mark a valid selection or enter an Adabas Review command.

A character was placed in the select field of a report that was just deleted.

Do not place a character in this field.

An invalid character was entered into an Adabas Review field.

Enter a valid character.

An unexpected return code has occurred while trying to free storage. The return code is also displayed.

If the problem recurs, contact your Software AG technical support representative.

When Adabas Review is invoked online for the first time, it adds sample Adabas reports to its system file.

This message is for information only.

Select a historical snapshot.

This message is for information only.

An attempt was made to perform an Adabas Review function that is not permitted for the user.

Contact your Adabas Review administrator.

A request to list report definitions was made but there are no definitions to list.

This message is for information only.

The operator command was issued to Com-plete.

This message is for information only.

A request to display a report cannot be satisfied because the report has not yet accumulated any data.

Determine if the report criteria is correct and if so, try again later or else add a new report.

An invalid function was entered.

Enter a valid function.

DBID= was entered on the Adabas Review command line of the Adabas Communication Statistics display, but no corresponding DBID number was given.

Enter DBID=nnn where nnn is a valid DBID number.

The cursor was placed at an invalid location on a screen that senses the cursor position to perform a function.

Place the cursor at a valid position or enter an Adabas Review command.

An invalid logical operator was entered. Valid operators are: =,:,<,>,EQ,NE,LT,GT,LE,GE

Enter a valid logical operator.

More than one line was marked to perform a report function. This is not allowed.

Mark only one line at a time.

A line has been marked with a character that has no assigned function.

Mark lines using valid characters.

An invalid option was entered into the Transaction Summary Option field in the Edit Report screen.

Valid options are NONE, SUM, and DET.

Enter a valid option.

The request to purge a started report was not performed.

This message is for information only.

An inquiry was made for a message number that has an invalid prefix. Message numbers must start with REV.

Enter the MSG command using a valid message number.

A Com-plete performance monitor function was attempted. This is not valid under CICS.

This message is for information only.

A Com-plete performance monitor function was attempted on a version of Com-plete earlier than version 4.4.

Install the current version of Com-plete.

The Adabas Review buffer pool function is waiting for terminal input.

Select a buffer pool by name or enter an Adabas Review command.

A syntax error was detected while processing a scan command on the ET display.

This message is for information only.

The buffer pool selection entered cannot be identified.

Enter a valid buffer pool name or enter an Adabas Review command.

The command entered is not allowed in history mode.

Do not enter command.

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.

Try again later.

This confirms that the indicated report definitions have been changed from AUTOSTART to NON-AUTOSTART status.

This message is for information only.

An invalid code was entered for a command.

Enter a valid command code.

This confirms that the request to start a report was successful.

This message is for information only.

The request to start an online report has failed because of syntax errors in the report definition.

Correct the report definition and start the report again.

Adabas has responded with a non-zero response code.

Use the Adabas Messages and Codes documentation to determine the problem.

The request to start a report was not successful.

This message is for information only.

An attempt was made to access a user profile that is being updated by another user.

Edit the user profile again. Ensure that the changes made to profile do not affect the changes that you are making.

The purge user (PU) command was given without specifying a user profile.

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.

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.

This message is for information only.

An attempt was made to delete a user profile that was not found in the Adabas Review repository.

Check to make sure the user ID you specified is correct.

This confirms that a request to purge a user profile was successful.

This message is for information only.

The profile that you are editing is new.

You may now customize the new user profile. To save this new profile, press PF5or issue the SAVE command.

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.

This message is for information only.

An unexpected return code was received from one of Adabas Review's programs.

Record the error message and contact your Software AG technical support representative.

The changes made to the user profile have been saved.

This message is for information only.

(CICS Only) This message appears when REVTAB has not been defined as a resident program.

Contact your Software AG technical support representative.

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.

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.

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.

Purge one of the already existing reports or try again later.

The statistics profile was not saved.

This message is for information only.

This confirms that users have been attached to simulate a load on Com-plete.

This message is for information only.

An error has occurred while trying to attach users for load simulation.

If the problem reoccurs, contact your Software AG technical support representative.

The statistics profile has been saved.

This message is for information only.

A TID number was entered into the SA screen via the T= or TID= command but is was not numeric.

Enter a numeric TID number.

This confirms that the request to save a report definition was successful.

This message is for information only.

An attempt was made to retrieve a report definition but no report definition by that name was found.

Determine the correct name or create a new definition.

The interval may not be greater than 1440 minutes.

This message is for information only.

A request was made to start, view, or list a report, but Adabas Review is in the process of terminating.

This message is for information only.

An attempt to start an Adabas report has failed because a report with the same name is already active.

Purge the currently active report and retry or start a report with a different name.

An attempt was made to communicate with the Adabas Review exit but no Adabas Review command was provided.

Provide an Adabas Review command.

The Adabas Review exit routine is not accepting communications due to insufficient storage.

Purge at least one of the started reports.

An attempt to start an Adabas Review report has failed due to insufficient storage.

Purge an active report and retry.

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.

Make the fields Order fields only.

A format buffer error has occurred while trying to communicate with the Adabas Review exit routine.

Contact your Software AG technical support representative.

An attempt to view an active report has failed because the display program for this report cannot be found.

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.

A Natural error condition occurred. The Natural error message number is displayed.

Reference the Natural online message utility for an explanation of the error.

The request to save a report definition was cancelled by the user in response to an overlay warning.

This message is for information only.

The request to save a report definition was cancelled because the resulting generated display program would have exceeded the maximum allowable line size.

Reduce the number of fields and try again.

This confirms that the request to change the target DBID was successful.

This message is for information only.

A request to list started reports was made but there are no started reports to list.

This message is for information only.

Only summary reports can be viewed online. Detailed reports are printed at Adabas termination time.

This message is for information only.

An attempt was made to reactivate a report that was deactivated by Adabas Review due to insufficient storage. The report cannot be reactivated.

Use the refresh (RF) command to purge the existing data and start accumulating new information.

This confirms that a refresh (RF) command was successful.

This message is for information only.

A request to List History Reports was cancelled because there are no history reports to list.

This message is for information only.

An attempt was made to change the DBID number to less than 0 or greater than 255.

Enter a DBID number in the range of 0 to 255.

A value other than AND or OR was entered into the AND/OR field of the selection criteria on the Processing Rules screen.

Enter AND or OR.

No field name was specified for the entered criteria on the Edit Report screen.

Enter a field name.

AND or OR was entered into the AND/OR field of the Processing Rules screen but no condition followed.

Either remove the AND/OR or enter another condition.

More than one condition was coded on the Processing Rules screen, but no AND/OR was coded for the previous condition.

Enter AND/OR on the previous condition

The OPERATOR field has been left blank on a condition.

Fill in the OPERATOR field.

The VALUE field has been left blank on a condition.

Fill in the VALUE field.

An invalid operator was entered into the OPERATOR field of the Processing Rules screen.

Enter a valid operator.

An invalid FIELD NAME was entered on the Edit Report screen.

Press PF11 for a list of valid field names.

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.

Enter a number between 1 and 20.

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.

Place a number in the ORDER column, and remove any marks for SUM, AVG, PCT, or ROUND.

The request to save a report definition was cancelled by the user in response to an overlay warning.

This message is for information only.

An invalid value was entered as part of a logical condition on the Edit Report screen.

Enter a valid value.

An internal storage management error has occurred within the Adabas Review nucleus.

If the problem recurs, contact your Software AG technical support representative.

A rounding factor was specified for a field that does not also have an order number specified.

Enter a number in the ORDER field, or remove the rounding factor.

A field was entered on the Edit Report screen but no action was specified; i.e. ORDER, SUM, MIN, MAX, PCT, or AVG.

Enter a number in the ORDER field and/or an X in one or more of the SUM, MIN, MAX, PCT, or AVG fields

The data entered into the round column of the Edit Report screen was not numeric.

Enter a number with or without a decimal into the round field.

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.

Enter a number between 0 and 32,767.

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 cancelled.

Enter a number between 0 and 32,767.

ADAROLL specifies the amount of time Com-plete will wait for Adabas calls before rolling out the program making the call.

Enter ALWAYS, NEVER, or a number less than 30.99.

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.

This message is for information only.

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.

This message is for information only.

The letter "Y" (yes) and the letter "N" (no) are the only two valid values for this field.

Enter "Y" if you wish the APPLYMOD to be active; or enter "N" if you wish to deactivate the applymod.

This message confirms that the Adabas / Com-plete parameters have been successfully updated.

This message is for information only.

The cursor must be placed on a line that contains valid data.

Place cursor on a line with valid data.

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.

Reduce the number of fields by one until the message disappears.

A number was entered on the Adabas Review command line that was greater than the actual number of pages available.

Enter a valid page number.

The roll buffer is not allocated.

This message is for information only.

The roll data sets are not allocated.

This message is for information only.

The user is not logged on.

This message is for information only.

An invalid wrap option was specified in the report definition. The option must be NONE, STD, or HIGH.

This message is for information only.

The low water mark specified was higher than or equal to the high water mark.

Enter a number less than the high water mark.

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.

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.

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.

This message is for information only.

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.

Enter a valid program name.

This confirms that the request to change the display program name using the CP command of the List Report Definitions screen was successful.

This message is for information only.

The report definition selected is being purged by another user.

This message is for information only.

An invalid character such as a quotation mark or a period was used as part of the report name.

Remove the invalid character from the report name.

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.

Enter a valid date range in the form of yyyy-mm-dd or press ENTER to default to the maximum date range.

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.

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.

This prompts you to enter a date range before viewing a history report. The maximum date range (all dates) is the default.

Enter a date range in the form of yyyy-mm-dd, or press ENTER to default to the maximum date range.

The request to regenerate display programs has completed successfully.

This message is for information only.

Adabas Review attempted to read information from its system file but received an Adabas response code of 148.

Bring up the database that has the Adabas Review repository and make sure that the LFILE parameter has been specified correctly.

An invalid value was entered for default system. The valid system codes are:

Enter a valid system code.

A value was entered into a field that is intended to accept numeric data only.

Enter a valid numeric value.

The subtask to generate auto-report definitions was successfully started.

This message is for information only.

The subtask to generate auto-report definitions is still active from a previous execution.

Wait a few seconds and try the command again.

The subtask to regenerate auto-report definitions was not attached and did not run.

Check your Adabas STEPLIB and make certain that the module RAOSAUTO is present.

The Adabas UEX4 module RAOSEXIT is not the correct version.

Verify that Adabas Review has been correctly installed.

The Adabas Review message help subsystem is not available from this screen.

Perform the MSG function from another screen.

The target database ID must be in the range between 1 and 65535.

Enter a database ID in the specified range.

The SVC specified cannot be 0.

Enter a correct SVC number.

The target type must be one of the specified values.

Enter the correct target type.

If the target type is ADA, then the target database ID must be in the range of 1 to 255.

Enter a database ID in the specified range.

An invalid value was entered for the field.

Enter a valid field value: either yes ("Y") or no ("N").

The target definition did not exist for the requested target.

Define the target.

The target definition was successfully saved.

This message is for information only.

The default definition for target 00000 cannot be purged.

This message is for information only.

The target definitions marked for purge were successfully deleted.

This message is for information only.

The target definition for the database specified did not exist, and there was also no default definition.

Add the target definition for the specified target.

The subtask to generate report definitions was successfully started.

This message is for information only.

The subtask to generate report definitions is still active from a previous execution.

Wait a few seconds and try the command again.

The subtask to generate report definitions was not attached and did not run.

Check your Adabas STEPLIB and make certain that the module RAOSAUTO is present.

The requested function was terminated by user request and was not performed.

This message is for information only.

The Adabas Review data file's database ID and file number were set successfully.

This message is for information only.

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.

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.

The request to invoke Adabas Online System (AOS) from Adabas Review has failed because AOS is not installed in the current Natural system file.

This message is for information only.

The installation process did not complete successfully.

Make sure that all INPL and IUPD tapes are properly installed.

The PF key that was pressed is not defined to perform a function.

Press a valid PF key.

To exit without saving the changes made to a user profile, press PF3. To save the changes made to a user profile, press PF5.

See explanation.

A user ID must be specified.

Enter a user ID.

A Natural error has occurred in one of Adabas Review's programs.

Record the information given in the message and contact your Software AG technical support representative.

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.

Either use another data set, or purge the report that is using the command log data set.

LOGGING was specified on the Report Options screen for a summary report. Only Detail reports can perform the LOGGING function.

Either set LOGGING to "N" or set SUM/DETAIL to "D".

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.

Correct the report definition and press PF5to save the report definition.

A request to list report definitions cannot be satisfied because there are no definitions to list.

This message is for information only.

An attempt to save a summary report failed because there are no ORDER fields. At least one ORDER field is required for summary reports.

Make at least one field an ORDER field and save the report.

The process of converting Adabas Review report definitions has completed.

This message is for information only.

The process of converting Adabas Review history reports completed.

This message is for information only.

The process of converting Adabas Review user profiles has completed.

This message is for information only.

The process of converting Adabas Review report definitions was cancelled at the request of the user. Any reply other than "yes" or "change" on the LFILE confirmation screen will cause this message.

This message is for information only.

The process of converting Adabas Review history reports was cancelled at the request of the user. Any reply other than "yes" or "change" on the LFILE confirmation screen will cause this message.

This message is for information only.

The process of converting Adabas Review user profiles was cancelled at the request of the user. Any reply other than "yes" or "change" on the LFILE confirmation screen will cause this message.

This message is for information only.

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.

This message is for information only.

An attempt was made to convert Adabas Review history reports, but there are none to convert.

This message is for information only.

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.

This message is for information only.

Either an Adabas or a Natural error has occurred while trying to convert report definitions.

Follow the Adabas or Natural procedures for error correction.

Either an Adabas or a Natural error has occurred while trying to convert history reports.

Follow the Adabas or Natural procedures for error correction.

Either an Adabas or a Natural error occurred while trying to convert user profiles.

Follow the Adabas or Natural procedures for error correction.

An attempt was made to run an Adabas Review conversion program with identical TO and FROM files.

Correct the LFILE for the TO or FROM file.

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.

Specify a correct Adabas Review DBID/file number.

No active database targets were found on the SVC number specified in the message.

Verify that the target definitions are defined to the correct SVC number.

The target selected is a Entire System Server (formerly Natural Process) target type.

This message is for information only.

The database selected is not active.

This message is for information only.

The database selected is a non-Adabas type target.

This message is for information only.

An attempt was made to suspend a report that was is already suspended.

This message is for information only.

An invalid option was entered on the Edit Report screen for the OP summary parameter.

Enter a valid option.

A new report definition is being created.

Enter the parameters for the new report definition or exit.

An attempt was made to reactivate a report that was already active.

This message is for information only.

Historical data was purged.

This message is for information only.

Historical data was not purged.

This message is for information only.

Historical data was not found.

This message is for information only.

The available storage in the thread is insufficient.

Contact your Software AG technical support representative.

An invalid request or an invalid free queue element (FQE) was found.

Contact your Software AG technical support representative.

No response time report definition was specified.

Contact your Software AG technical support representative.

Report definition has been purged.

This message is for information only.

Report definition was not purged.

This message is for information only.

An attempt was made to download a report but the Natural session is not in PC mode.

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.

More than one field has the same order number on the Edit Report screen.

Make each order number unique.

An attempt was made to perform a function on a started report, but no started report with the specified report name was found.

This message is for information only.

An attempt was made to issue the LOG command while viewing a report.

Stop viewing the report and reissue the LOG command.

The Adabas Review dynamic logging options have been updated.

This message is for information only.

The LOG command was issued and an error occurred during processing. nnnn = the response code associated with the error.

Follow the Adabas or Natural procedures for error correction.

While attempting to view the buffer pool display, Adabas determined that Adabas Review was not installed on that database and issued a response code.

This message is for information only.

A Adabas Review function was restarted from the beginning because an Adabas response code 9 was received.

This message is for information only.

An attempt was made to enter Adabas Review NM, but the NM component was not on the installation tape.

Determine whether the NM component was actually purchased. If it was purchased, then you may have inadvertently received the wrong Adabas Review installation tape. Contact your Software AG representative.

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.

Specify the response time name.

The terminal ID (TID) must be between 1 and 65,535.

Enter a valid TID number.

An invalid terminal ID (TID) was specified.

Enter a valid TID number.

The current version of Adabas Review no longer supports the requested function.

Refer to the Adabas Review User documentation for a list of available features and functions.

The requested report definition could not be found in the Adabas Review data file.

This message is for information only.

No OP summary information was available for the report specified.

This message is for information only.

A DB report was defined with the first field as a buffer segment (FBSEG01, RBSEG01 ETC). The first field cannot be a buffer segment.

Make another field the first field.

A request was made to view a list of programs in the resident program library buffer, but none were defined to Com-plete.

This message is for information only.

A request was made to view a list of programs in the resident programs, but none where defined to Com-plete.

This message is for information only.

Adabas Review was unable to locate the Adabas IDT header.

Contact your Software AG technical support representative.

Adabas Review was unable to load the ADALDI text module from the Adabas textlib.

Verify that the Adabas textlib is accessible from your z/VM machine.

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.

If STATUS information for the database should be returned, edit and STOW the program N-IGNORE.

An attempt to reset the stopwatch was unsuccessful due to insufficient storage.

Try again later.

A value other than ON or OFF was entered.

Enter ON or OFF.

The command log data set was switched successfully.

This message is for information only.

Adabas Review command logging is not active for the specified report.

Choose a report that has command logging.

The subpool ID specified was invalid.

Select a valid subpool.

A Response Time Report was requested but no transaction summary records exist for the selected report.

This message is for information only.

A Response Time Report was requested but no OP summary records exist for the selected report.

This message is for information only.

The AND fields in the selection criteria have resulted in a data string that is too long for Adabas Review to process.

Reduce the number of AND statements and resave the report.

The OR fields in the selection criteria have resulted in a data string that is too long for Adabas Review to process.

Reduce the number of OR statements and resave the report.

A value larger than allowed was entered in the SVC field of the target definition. The maximum value for this field is 255.

Enter the correct SVC number.

The user specified in the cancel function has already been cancelled.

This message is for information only.

The specified terminal ID has been cancelled.

This message is for information only.

The specified terminal has been cancelled.

This message is for information only.

The terminal ID specified in the cancel, pick, or force function could not be found.

This message is for information only.

The user specified in the cancel, pick, or force function could not be found.

This message is for information only.

The terminal name specified in the cancel, pick, or force function could not be found.

This message is for information only.

The terminal ID number specified in the cancel, pick, or force function was not a valid numeric value.

This message is for information only.

The specified Adabas Review response time report was successfully autostarted.

This message is for information only.

No Adabas Review Response Time reports were found to autostart.

This message is for information only.

Adabas Review has started one autostarted response time report.

This message is for information only.

Adabas Review started the specified number of autostarted response time reports.

This message is for information only.

The Adabas Review history interval task successfully recovered from an Adabas timeout (response code 9).

This message is for information only.

The Adabas Review history interval task successfully invoked Natural and is initializing.

This message is for information only.

The Adabas Review history interval task terminated because it was unable to locate RNMTAB.

Check that RNMTAB has been defined to CICS as a resident PPT entry, and that RNMTAB is available to CICS.

The Adabas Review history interval task terminated because it was unable to locate the RNMCICS.

Check that RNMCICS has been defined to CICS as a PPT entry and that RNMCICS is available to CICS.

The Adabas Review history interval task terminated because it encountered a Natural error during initialization.

Investigate the Natural error indicated, correct the problem, and restart the history subsystem.

The Adabas Review history interval task terminated because it detected that the Adabas Review Natural Monitor data file was not initialized.

Verify that the INSTALL program has been executed to initialize the Adabas Review Natural Monitor data file.

The Adabas Review history interval task terminated because it encountered an error in Natural from which it could not recover.

Investigate the Natural error indicated, correct the problem, and restart the history subsystem.

The Adabas Review history interval task terminated normally.

This message is for information only.

The Adabas Review history interval task terminated because the counter for maximum reinitializations was exceeded.

Check messages sent to Adabas Review prior to this message to determine why the history task has reinitialized so many times.

The Adabas Review history interval task terminated.

Check other Adabas Review messages issued prior to this message to determine if an error condition was encountered.

The user with the specified terminal ID was cancelled by another user at another terminal.

This message is for information only.

The user with the specified user ID was cancelled by another user at another terminal.

This message is for information only.

The terminal with the specified name was cancelled by another user at another terminal.

This message is for information only.

The user with the specified terminal ID was forced.

This message is for information only.

The user with the specified user ID was forced.

This message is for information only.

The terminal with the specified name was forced.

This message is for information only.

The user with the specified terminal ID was forced by another user at another terminal.

This message is for information only.

The user with the specified user ID was forced by another user at another terminal.

This message is for information only.

The terminal with the specified name was forced by another user at another terminal.

This message is for information only.

A CANCEL command must be issued for a user before a FORCE command can be issued.

This message is for information only.

An invalid response time report autostart option was specified. The value must be "Y" or "N".

Specify valid value.

An invalid response time report history refresh option was specified. The value must be "Y" or "N".

Specify a valid value.

The value specified is invalid for the field. Valid values are denoted by <range-start> through <range-end> in the message.

Specify a valid value in the range specified.

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.

Verify that the Adabas Review NM code is correctly linked with the Natural nucleus.

The request to copy a report definition was successful.

This message is for information only.

An Adabas response code 148 was received while trying to store information in an Adabas Review repository.

Insure that the database ID and file number are correct and that the database is available.

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.

From the Database System menu, type TECH to determine why the current Adabas Review database is invalid and correct the error.

Using the DBID= command, the user attempted to change the Adabas Review database being accessed. The database selected did not have Adabas Review installed.

Verify that the database specified in the DBID= command is a valid Adabas Review database.

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).

Verify that the database specified in the DBID= command is a valid Adabas Review database and that it is active.

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.

Verify that the database specified in the DBID= command is a valid Adabas Review database.

Using the DBID= command, the user attempted to change the Adabas Review database being accessed. The user received the indicated response code.

Verify that the database specified in the DBID= command is a valid Adabas Review database.

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.

Execute the TECH command from the Database System menu.

A VIEW or VW command terminated because the display program invoked was generated for a different report.

Regenerate the display program for the report that failed using the RG function of the List Reports screen.

A list or range of values was entered without parentheses into a processing rule.

Include the values within parentheses.

The number of opening and closing parentheses are unequal.

Include a closing parentheses for each opening parentheses.

An invalid command was entered into the command line of a help screen.

Enter a valid command or press a valid PF key.

A GENAUTO (or GA) command was entered but is not implemented in z/VM.

This message is for information only.

DOWNLOAD (or DL) was entered from a screen where the DOWNLOAD command is invalid.

Enter DL into the SEL column of the List Started Reports screen.

The MAX K value specified in the report options must be at least 4k for z/OS, z/VM, and z/VSE, and 8k for BS2000.

Specify a value for MAX K that is at least the minimum.

The WRAPPING value can only be set to "Y" for a SUMMARY report with SEQUENCE as the first display field.

Only specify WRAPPING=Y for SUMMARY reports with SEQUENCE as the first field.

The page size entered on the Report Options screen is invalid. The value must be between 1 and 255.

Enter a valid page size.

The value must be greater than 0.

This message is for information only.

An attempt was made to change the FNR number to less than 1 or greater than 254.

Enter a FNR number in the range of 1 to 254.

The expanded list of history report occurrences could not be sorted because the resulting ISN list was too large. The list is displayed unsorted.

Increase the value in the LS ADARUN parameter.

The request to compress a history report completed successfully.

This message is for information only.

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.

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:

1. Enter RESET HISTORY FILE on the command line of the DB System menu.

2. Follow the instructions on the screen.

A reply of "N" was given in response to the confirmation prompt prior to compressing a history report.

This message is for information only.

A request to reset the history file was made but the file does not need resetting.

This message is for information only.

This confirms that the history file has been reset. This essentially unlocks the lock that that was placed on the file during a CH function.

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.

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.

Remove the duplicate field name from the expression.

The target DBID has been successfully changed for the report definition.

This message is for information only.

The graphical bufferpool reports cannot be downloaded or printed: they may only be viewed.

Use the VW command to view the report.

The AA function is not available in z/VM.

This message is for information only.

A non-zero response code was returned from the specified target.

This message is for information only.

The report defaults were saved successfully.

This message is for information only.

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.

This message is for information only.

The report options were updated successfully.

This message is for information only.

A request to update reports was unnecessary because no changes were made.

This message is for information only.

A request to start a report was unsuccessful because the DBID to monitor was set to the hub ID. Adabas Review reports can only monitor Adabas targets.

Correct the report and retry.

More than one buffer segment was defined in a report. Only one buffer segment per report is allowed.

Correct the report and retry.

An attempt was made to convert history records but there are no history records to convert.

None.

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.

Reduce the number of order fields to 1.

A user canceled a prompt to confirm the saving of report defaults.

None.

A user executed the NUCID or NUC LIST command for a non-cluster database.

None.

A user executed the NUCID or NUC LIST command in hub mode; these commands are available only in local mode.

None.

An attempt to edit the display program BUFFPOOL failed because it is not delivered as source.

None.

The maximum list size of 10 has been exceeded in a processing rule.

Limit the list size to 10.

No targets are active for the SVC listed in the message (nnn).

No action is required for this informational message.