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 | REV00043 | REV00044 | REV00045 | REV00046 | REV00047 | REV00050 | REV00054 | REV00055 | REV00057 | REV00058 | REV00059 | 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 | 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 | REV00390 | REV00391 | REV00392 | REV00393 | REV00394 | REV00395 | REV00396 | REV00397 | REV00398 | REV00399 | REV00400 | REV00401 | REV00402 | REV00403 | REV00404 | REV00405 | REV00406 | REV00407 | REV00408 | REV00410 | REV00413 | REV00414
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 a 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.
|
||||
Action: |
This message is for information only. |
REV00002 | REVIEW COMMAND MUST BEGIN WITH SUBSYSTEM CODE |
Explanation: |
An invalid command was entered from the 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 | REVTAB NOT FOUND |
Explanation: |
The Review program REVTAB is not available to CICS or is not permanently resident. |
Action: |
Make sure REVTAB is available and permanently resident. |
REV00004 | ENTER REVIEW COMMAND |
Explanation: |
Review is waiting for terminal input. |
Action: |
Press a valid PF key or enter a Review command. |
REV00005 | INVALID COMMAND |
Explanation: |
An invalid command was entered into the Review command line. |
Action: |
Press a valid PF key or enter a valid Review command. |
REV00006 | PRESS 'ENTER' TO CONTINUE INITIALIZATION PROCESS |
Explanation: |
During Review initialization a series of messages are displayed. 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: |
Review has determined that there are no online systems available to the user. There are two possible causes:
|
Action: |
Contact your Review administrator. |
REV00011 | INTERVAL STATISTICS PROFILE HAS BEEN CREATED |
Explanation: |
During 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 Review, or you are not authorized to use Review. |
Action: |
Contact your 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 a 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 a Review prompt field and a direct command was entered simultaneously. |
Action: |
Either answer the 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 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. |
REV00043 | YOU MUST REPLY 'Y' OR 'N' |
Explanation: |
An invalid reply was given in response to a 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 a 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 a 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 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 a Review function that is not permitted for the user. |
Action: |
Contact your 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. |
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: |
|
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 a 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 Review buffer pool function is waiting for terminal input. |
Action: |
Select a buffer pool by name or enter a 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 a 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 Review asked for a confirmation, the user decided not to purge the user profile. |
Action: |
This message is for information only. |
REV00099 | USER PROFILE NOT FOUND |
Explanation: |
An attempt was made to delete a user profile that was not found in the 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 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 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 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 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 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 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 Review exit but no Review command was provided. |
Action: |
Provide a Review command. |
REV00137 | INSUFFICIENT STORAGE TO ISSUE REVIEW COMMAND |
Explanation: |
The 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 a 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. |
REV00141 | FORMAT BUFFER ERROR |
Explanation: |
A format buffer error has occurred while trying to communicate with the 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 cancelled by the user in response to an overlay warning. |
Action: |
This message is for information only. |
REV00147 | TOO MANY FIELDS - EXCEEDS MAX LINESIZE - SAVE CANCELLED |
Explanation: |
The request to save a report definition was cancelled 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 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 cancelled 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 CANCELLED BY OPERATOR |
Explanation: |
The request to save a report definition was cancelled 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 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: |
|
Action: |
Enter a number between 0 and 32,767. |
REV00182 | ADALIMIT MUST BE AN INTEGER BETWEEN 0 AND 32,767 |
Explanation: |
|
Action: |
Enter a number between 0 and 32,767. |
REV00183 | ADAROLL MUST BE 'ALWAYS', 'NEVER', OR LESS THAN 30.99 |
Explanation: |
|
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 |
Action: |
This message is for information only. |
REV00185 | ADALIMIT FOR DBID dbid HAS BEEN CHANGED TO yyyyy BY user-id |
Explanation: |
The |
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 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 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 DATASETS NOT ALLOCATED |
Explanation: |
The roll datasets 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 Review installed as a user exit 4 or does not currently have LOGGING turned on. |
Action: |
Verify that Review is installed on the target DBID. If it is, ensure
that ADARUN |
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: |
Review attempted to read information from its system file but received an Adabas response code of 148. |
Action: |
Bring up the database that has the Adabas Review repository and make
sure that the |
REV00218 | DEFAULT SYSTEM MUST BE 'DB', 'DC', 'MM', OR 'NM' | ||||||||
Explanation: |
An invalid value was entered for default system. The valid system codes are:
|
||||||||
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 Review has been correctly installed. |
REV00224 | MSG FUNCTION NOT AVAILABLE FROM THIS SCREEN |
Explanation: |
The 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 CANNOT BE 0 |
Explanation: |
The SVC specified cannot be 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 CANCELLED |
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 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 |
REV00243 | ADABAS ONLINE SERVICES IS NOT INSTALLED |
Explanation: |
The request to invoke Adabas Online System (AOS) from 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 tapes 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 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 dataset is already in use by another report. The report is started without logging. |
Action: |
Either use another dataset, or purge the report that is using the command log dataset. |
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 Review report definitions has completed. |
Action: |
This message is for information only. |
REV00256 | HISTORY FILE CONVERSION COMPLETE |
Explanation: |
The process of converting Review history reports completed. |
Action: |
This message is for information only. |
REV00257 | USER PROFILE CONVERSION COMPLETE |
Explanation: |
The process of converting Review user profiles has completed. |
Action: |
This message is for information only. |
REV00258 | REPORT DEFINITION CONVERSION WAS CANCELLED |
Explanation: |
The process of converting 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. |
Action: |
This message is for information only. |
REV00259 | HISTORY FILE CONVERSION WAS CANCELLED |
Explanation: |
The process of converting 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. |
Action: |
This message is for information only. |
REV00260 | USER PROFILE CONVERSION WAS CANCELLED |
Explanation: |
The process of converting 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. |
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. 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 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 Review user profiles, but there are none to convert. 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 a 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 a Review file. |
Action: |
Specify a correct 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 a 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
|
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 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: |
A Review function was restarted from the beginning because an Adabas response code 9 was received. |
Action: |
This message is for information only. |
REV00294 | NM COMPONENT NOT INSTALLED |
Explanation: |
An attempt was made to enter Review NM, but the NM component was not on the installation tape. |
Action: |
Determine whether the NM component was actually purchased. If it was purchased, then you may have inadvertently received the wrong Review installation tape. 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 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 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: |
Review was unable to locate the Adabas IDT header. |
Action: |
Contact your Software AG technical support representative. |
REV00310 | UNABLE TO LOAD ADALDI |
Explanation: |
Review was unable to load the ADALDI text module from the Adabas textlib. |
Action: |
Verify that the Adabas textlib 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 DATASET SWITCHED |
Explanation: |
The command log dataset was switched successfully. |
Action: |
This message is for information only. |
REV00315 | COMMAND LOGGING IS NOT ACTIVE FOR REPORT |
Explanation: |
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 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 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 CANCELLED |
Explanation: |
The user specified in the cancel function has already been cancelled. |
Action: |
This message is for information only. |
REV00323 | TID terminal-id CANCELLED |
Explanation: |
The specified terminal ID has been cancelled. |
Action: |
This message is for information only. |
REV00325 | TERMINAL terminal-name CANCELLED |
Explanation: |
The specified terminal has been cancelled. |
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 Review response time report was successfully autostarted. |
Action: |
This message is for information only. |
REV00331 | NO AUTOSTARTED REPORTS FOUND TO START |
Explanation: |
No Review Response Time reports were found to autostart. |
Action: |
This message is for information only. |
REV00332 | ONE REPORT HAS BEEN AUTOSTARTED |
Explanation: |
Review has started one autostarted response time report. |
Action: |
This message is for information only. |
REV00333 | count REPORTS HAVE BEEN AUTOSTARTED |
Explanation: |
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 Review history interval task successfully recovered from an Adabas timeout (response code 9). |
Action: |
This message is for information only. |
REV00335 | RNMH HISTORY TASK INITIALIZING IN NATURAL |
Explanation: |
The 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 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 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 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 Review history interval task terminated because it detected that the Review Natural Monitor data file was not initialized. |
Action: |
Verify that the INSTALL program has been executed to initialize the Review Natural Monitor data file. |
REV00340 | HISTORY TASK TERMINATING. NON-RECOVERABLE NATURAL ERROR DETECTED |
Explanation: |
The 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 Review history interval task terminated normally. |
Action: |
This message is for information only. |
REV00342 | HISTORY TASK TERMINATING. MAXIMUM REINITIALIZATION COUNTER EXCEEDED |
Explanation: |
The Review history interval task terminated because the counter for maximum reinitializations was exceeded. |
Action: |
Check messages sent to Review prior to this message to determine why the history task has reinitialized so many times. |
REV00343 | HISTORY TASK TERMINATING |
Explanation: |
The Review history interval task terminated. |
Action: |
Check other Review messages issued prior to this message to determine if an error condition was encountered. |
REV00344 | TID terminal-id CANCELLED BY user-id AT TERMINAL terminal-name |
Explanation: |
The user with the specified terminal ID was cancelled by another user at another terminal. |
Action: |
This message is for information only. |
REV00345 | USER user-id CANCELLED BY user-id AT TERMINAL terminal-name |
Explanation: |
The user with the specified user ID was cancelled by another user at another terminal. |
Action: |
This message is for information only. |
REV00346 | TERMINAL terminal-name CANCELLED BY user-id AT TERMINAL terminal-name |
Explanation: |
The terminal with the specified name was cancelled 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 CANCELLED 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 Review history interval task terminated because it was unable to verify that the Review Natural Monitor code was correctly linked with the Natural nucleus. |
Action: |
Verify that the 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 was received while trying to store information in a 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 a Review function against a database that was inactive, did not have Review installed, or was not running a compatible version of Review. |
Action: |
From the Database System menu, type TECH to determine why the current 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 Review database being accessed. The database selected did not have Review installed. |
Action: |
Verify that the database specified in the DBID= command is a valid Review database. |
REV00363 | DATABASE dbid IS NOT ACTIVE |
Explanation: |
Using the DBID= command, the user attempted to change the Review database being accessed. The database selected was not active (Adabas response code 148). |
Action: |
Verify that the database specified in the DBID= command is a valid 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 Review database being accessed. The database selected has an invalid version of Review installed. |
Action: |
Verify that the database specified in the DBID= command is a valid Review database. |
REV00365 | RESPONSE CODE rsp RECEIVED ACCESSING DBID dbid |
Explanation: |
Using the DBID= command, the user attempted to change the Review database being accessed. The user received the indicated response code. |
Action: |
Verify that the database specified in the DBID= command is a valid Review database. |
REV00366 | TECH COMMAND ONLY AVAILABLE FROM THE DB SYSTEM MAIN MENU |
Explanation: |
The user attempted to executed the TECH command from a 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 OS/390, MVS/ESA, z/VM, and VSE/ESA, and 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. |
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 |
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:
|
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 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 VM/CMS. |
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: |
This message is for information only. |
REV00401 | REPORT DEFAULTS WERE SAVED |
Explanation: |
The report defaults were saved successfully. |
Action: |
This message is for information only. |
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: |
This message is for information only. |
REV00403 | UPDATE COMPLETED |
Explanation: |
The report options were updated successfully. |
Action: |
This message is for information only. |
REV00404 | NO CHANGES TO UPDATE |
Explanation: |
A request to update reports was unnecessary because no changes were made. |
Action: |
This message is for information only. |
REV00405 | CANNOT START A REPORT THAT MONITORS A HUB |
Explanation: |
A request to start a report was unsuccessful because the DBID to monitor was set to the hub ID. 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: |
None. |
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. |
REV00410 | REPORT DEFAULTS NOT SAVED |
Explanation: |
A user canceled a prompt to confirm the saving of report defaults. |
Action: |
None. |
REV00413 | NUCID ONLY VALID FOR CLUSTER DATABASES |
Explanation: |
A user executed the NUCID or NUC LIST command for a non-cluster database. |
Action: |
None. |
REV00414 | NUCID ONLY VALID IN LOCAL MODE |
Explanation: |
A user executed the NUCID or NUC LIST command in hub mode; these commands are available only in local mode. |
Action: |
None. |