START. HP HP System Dictionary/XL SDMAIN
Реклама
Реклама
>
START
Marks the start of a report definition.
Syntax
ST[ART] [.]
Description
The report definition must immediately follow this command and it, in turn, must be immediately followed by a SAVE command. A report definition consists of an optional CONFIGURE and/or FORMAT command followed by a required REPORT command.
No commands, other than the CONFIGURE, FORMAT, and REPORT commands are logged after the
START command until you issue the SAVE command. Once you issue the SAVE command, all commands are executed and logged. A [[Control]] Y entered while a START is active terminates the START command, thereby eliminating the need for a SAVE command. When this occurs, you are returned to command processing mode. In addition, as is normal in the processing of [[Control]] Y, all levels of redirected input are exited and input is reset to $STDINX.
Open Mode:
Shared-update or exclusive-update
Scope:
DA scope or any scope with create capability
Example
The following example saves the report element-report that produces a report on entities of type element.
In addition, the report on each element begins on a new page.
>START
>CONFIGURE PAGE.
>REPORT ENTITY;
>> ENTITY-TYPE = element.
>SAVE element-report;
>> DESCRIPTION = "Detailed report to list occurrences of
>> entity-type ELEMENT in sorted order.".
>
4- 147
4-148
A Appendix A SDMAIN Error Messages
The following is a complete list of System Dictionary SDMAIN errors listed in order by error number. The list includes at least one possible cause of the error and a recommended action for each cause.
The list is divided into the following groups:
Message Number ErrorType
1001-1099
1100-1149
1150-1174
1175-1199
File System
Initialization
Driver
Validator
1200-1299
1300-1324
1325-1349
1350-1374
1375-1399
1400-1424
1425-1449
1450-1474
Scanner/Parser/Prompt
Configure
Define
Edit
Format
Help
Redo
Renumber/Resequence
1475-1499
1500-1599
1600-1699
1700-1724
1725-1749
1750-1799
1800-1899
Macro Processor
Create/Copy/Modify
Display/Report
Start/Save
Stored Report
Execute
Miscellaneous
NOTE
A number of the error messages list an action of "Refer to the associated error". If this is the suggested action, the system has encountered an error in an MPE subsystem or with an System Dictionary intrinsic call. The subsystem or intrinsic returns a message that is printed for you and helps to explain the error encountered.
Another set of error messages list an action of "Contact the DA". If this is the suggested action, the system has encountered an error with the file system or an MPE subsystem that is unexpected. You should report this problem to the Dictionary
Administrator, who should try to determine its cause and fix it, if possible. If assistance is needed, the System Manager should contact an HP Response Center.
Some of the messages, as shown in this list, include an exclamation point ( ! ). This character stands for a parameter (such as a file name), which is displayed as part of the actual message in place of the !.
A-149
File System Messages (1001-1099)
1001 MESSAGE Unable to open the dictionary (SDERR 1001)
CAUSE The dictionary cannot be opened with the specified DEFINE command.
ACTION Refer to the associated error and correct the indicated problem.
1002 MESSAGE Cannot reopen dictionary after restructuring (SDERR 1002)
CAUSE The dictionary cannot be reopened after the completion of the RESTRUCTURE operation.
ACTION Refer to the associated error and correct the indicated problem.
1003 MESSAGE Dictionary close failed (SDERR 1003)
CAUSE The dictionary cannot be closed.
ACTION Refer to the associated error and correct the indicated problem.
1005 MESSAGE Unable to open $STDLIST file (SDERR 1005)
CAUSE Cannot open the $STDLIST file due to a file error.
ACTION Refer to the associated file error and correct the indicated problem.
1006 MESSAGE Unable to retrieve information about $STDLIST file (SDERR 1006)
CAUSE Unable to retrieve information about the $STDLIST file through the FGetInfo intrinsic.
ACTION Contact the DA. (Remember to get the associated error, too.)
1007 MESSAGE Error while writing the banner message (SDERR 1007)
CAUSE Error while writing the banner message to $STDLIST.
ACTION Refer to the associated file error and correct the indicated problem.
1008 MESSAGE Error while writing the command prompt (SDERR 1008)
CAUSE Error while writing the command prompt to $STDLIST.
ACTION Refer to the associated file error and correct the indicated problem.
1009 MESSAGE Error while writing a prompt message (SDERR 1009)
CAUSE Error while writing a prompt message to $STDLIST.
ACTION Refer to the associated file error and correct the indicated problem.
1010 MESSAGE Error while writing output line (SDERR 1010)
CAUSE Error while writing an output line to $STDLIST.
ACTION Refer to the associated file error and correct the indicated problem.
1015 MESSAGE Unable to open $STDINX file (SDERR 1015)
CAUSE Unable to open the $STDINX file.
ACTION Refer to the associated file error and correct the indicated problem.
1016 MESSAGE Unable to read from $STDINX file (SDERR 1016)
CAUSE Unable to read from the $STDINX file.
A-150
ACTION Refer to the associated file error and correct the indicated problem.
1017 MESSAGE Unable to retrieve information about the $STDINX file (SDERR 1017)
CAUSE Unable to retrieve information about the $STDINX file through the FGetInfo intrinsic.
ACTION Contact the DA. (Remember to get the associated error, too.)
1018 MESSAGE Unable to close $STDINX file (SDERR 1018)
CAUSE The $STDINX file cannot be closed.
ACTION Contact the DA. (Remember to get the associated error, too.)
1020 MESSAGE Unable to open the input file (SDERR 1020)
CAUSE Cannot open the specified input file.
ACTION Refer to the associated file error and correct the indicated problem.
1021 MESSAGE Unable to close the input file (SDERR 1021)
CAUSE Cannot close the input file while exiting the system.
ACTION Refer to the associated file error and correct the indicated problem.
1022 MESSAGE Error while reading an input line (SDERR 1022)
CAUSE Bad read when reading the next line from the input file.
ACTION Refer to the associated file error and correct the indicated problem.
1023 MESSAGE Unable to retrieve information about the input file (SDERR 1023)
CAUSE Unable to retrieve information about the input file through the FGetInfo intrinsic.
ACTION Contact the DA. (Remember to get the associated error, too.)
1024 MESSAGE Input file recsize too long. All lines truncated to 80 chars (SDWARN 1024)
CAUSE The user-specified input file has a record size greater than 80 characters. All input lines are a maximum of 80 characters so all lines are truncated to 80 characters.
ACTION If the commands in the file do not take up more than 80 characters per line, no action is needed. If the commands do take more than 80 characters per line, all characters after 80 are ignored so the expected action will not occur. In this case, the commands must be placed on multiple lines so that no one line contains more than 80 characters
(including embedded blanks).
1025 MESSAGE Input has been reset to your terminal (SDWARN 1025)
CAUSE A Control-Y was entered while input was initially redirected by using SDIN. All nested input levels are exited and input is reset to $STDINX.
ACTION No action is needed.
1030 MESSAGE The log file is full (SDWARN 1030)
CAUSE The log file for the system is full. The system will attempt to open an alternate log file if one is available. If no alternate is available, logging is disabled. In either case, processing can continue.
ACTION No action is needed.
1031 MESSAGE Unable to close the log file (SDERR 1031)
A-151
CAUSE Cannot close the log file while exiting the system.
ACTION Refer to the associated file error and correct the indicated problem.
1032 MESSAGE Command logging has been disabled for this session (SDERR 1032)
CAUSE SDLOG is equated to $NULL or the user responded that the system cannot overwrite the existing log file on entrance to the system.
ACTION To start command logging, use the OPTIONS command to specify a log file.
CAUSE The SDLOG file is filled up or there is a write error to the SDLOG file so it is no longer available for use.
ACTION To continue command logging, use the OPTIONS command to specify a new log file.
1033 MESSAGE Close failed on old log file (SDWARN 1033)
CAUSE Cannot close the old log file when specifying a new log file. The new file will be the log file.
ACTION Refer to the associated error and correct the indicated problem.
1035 MESSAGE Unable to open macro file SDMACRO (SDERR 1035)
CAUSE The SDMACRO file cannot be opened.
ACTION No action is needed if you do not wish to use the macro facility. If you wish to use the facility, specify a valid macro file name using the OPTIONS command.
1036 MESSAGE Error while reading from SDMACRO file (SDERR 1036)
CAUSE An error was encountered while reading from the SDMACRO file.
ACTION Refer to the associated file error and correct the indicated problem.
1037 MESSAGE Close failed on old Macro file (SDWARN 1037)
CAUSE Could not close the old macro file when specifying a new macro file. The new file will be the macro file.
ACTION Refer to the associated file error and correct the indicated problem.
1038 MESSAGE Macro file recsize too long. All lines truncated to 80 chars (SDWARN 1038)
CAUSE The user specified macro file has a record size of larger than 80 characters. All macro lines are a maximum of 80 characters so all lines are truncated to 80 characters.
ACTION If the commands in the file do not take up more than 80 characters per line, no action is needed. If the commands do take more than 80 characters per line, all characters after
80 are ignored so the expected action will not occur. In this case, the commands must be placed on multiple lines so that no one line contains more than 80 characters
(including embedded blanks).
1040 MESSAGE Default the output file to $STDLIST (SDWARN 1040)
CAUSE Cannot open the specified output file. The system defaulted to opening $STDLIST as the output file so processing can continue.
ACTION Refer to the associated file error, correct the indicated problem, and use the
CONFIGURE command to redirect to the output file. Or, do nothing and continue processing with the output directed to $STDLIST.
1041 MESSAGE Output file is full. Must reassign before additional output (SDERR 1041)
A-152
CAUSE The output file is full so no more output can be directed into it. If more reporting output is desired, the file must be redirected before continuing.
ACTION Use the CONFIGURE command to redirect the output file to another file or to
$STDLIST as desired.
1042 MESSAGE Unable to close the output file (SDERR 1042)
CAUSE Cannot close the output file while exiting the system.
ACTION Refer to the associated file error and correct the indicated problem.
1043 MESSAGE Old Output file close failed. Opening new Output file (SDERR 1043)
CAUSE Cannot close the old output file when redirecting output to a new file. The new file will be the output file.
ACTION Refer to the associated file error and correct the indicated problem.
1044 MESSAGE Unable to open printer file. Default Output to $STDLIST (SDERR 1044)
CAUSE Cannot open the printer as requested. Output is directed to $STDLIST.
ACTION Refer to the associated file error, correct the indicated problem, and use the
CONFIGURE command again to direct output to the printer. Or, do nothing and leave the output directed to $STDLIST.
1050 MESSAGE Cannot reset EDTXT file equate. Reset manually if necessary (SDERR 1050)
CAUSE Cannot reset the EDTXT file equate while exiting the system.
ACTION Issue the following MPE command: RESET EDTXT.
1051 MESSAGE EDTXT file is full (SDERR 1051)
CAUSE The text of the specified variable attribute does not fit in the edit file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1052 MESSAGE Error while writing to file ! (SDERR 1052)
CAUSE Error encountered while writing to the edit file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1053 MESSAGE Unable to reopen EDTXT file (SDERR 1053)
CAUSE The edit file cannot be opened by the system after the return from the editor. All the edited text is lost but the original text is preserved.
ACTION Contact the DA. (Remember to get the associated error, too.)
1054 MESSAGE Cannot write eof to ! file (SDERR 1054)
CAUSE Error encountered while trying to write an end-of-file mark to the edit file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1055 MESSAGE ! close failed so no edit was made (SDERR 1055)
CAUSE Error encountered while closing the edit file in preparation for passing it to the editor.
ACTION Contact the DA. (Remember to get the associated error, too.)
1056 MESSAGE ! close failed (SDERR 1056)
A-153
CAUSE Cannot close the edit file while exiting the system.
ACTION Contact the DA. (Remember to get the associated error, too.)
1057 MESSAGE Edited text is too long. Truncated to maximum allowed (SDWARN 1057)
CAUSE The edited text is greater than the maximum length allowed by SDMAIN for variable attributes. The maximum length is allowed and any extra is truncated.
ACTION No action is needed. However, the text should be modified to compact the text so that the portion truncated can again be added onto the end.
1060 MESSAGE Unable to open the include file (SDERR 1060)
CAUSE Cannot open the specified include file.
ACTION Refer to the associated file error and correct the indicated problem.
1061 MESSAGE Unable to retrieve information about the include file (SDERR 1061)
CAUSE Unable to retrieve information about the include file through the FGetInfo intrinsic.
ACTION Contact the DA. (Remember to get the associated error, too.)
1062 MESSAGE Include file recsize too long. All lines truncated to 80 chars (SDWARN 1062)
CAUSE The user specified input file has a record size of larger than 80 characters. All input lines are a maximum of 80 characters so all lines are truncated to 80 characters.
ACTION If the commands in the file do not take up more than 80 characters per line, no action is needed. If the commands do take more than 80 characters per line, all characters after
80 are ignored so the expected action will not occur. In this case, the commands must be placed on multiple lines so than no one line contains more than 80 characters
(including embedded blanks).
1090 MESSAGE Unable to open temporary file ! (SDERR 1090)
CAUSE Cannot open a temporary file for the system to use.
ACTION Contact the DA. (Remember to get the associated error, too.)
1091 MESSAGE Error while rewinding temporary file ! (SDERR 1091)
CAUSE Error while resetting the file pointer of a temporary file to the beginning of the file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1092 MESSAGE Error while reading from temporary file ! (SDERR 1092)
CAUSE Error while reading from the temporary file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1093 MESSAGE Error while retrieving information on temporary file ! (SDERR 1093)
CAUSE Unable to retrieve information about the temporary file through the FGetInfo intrinsic.
ACTION Contact the DA. (Remember to get the associated error, too.)
1094 MESSAGE Temporary file is full ! (SDERR 1094)
CAUSE A temporary file used by the system is full.
ACTION The number of items requested by the command is too large (> 32767). Use Selection
Criteria to reduce the number of items retrieved or to split the retrieval so that half are
A-154
retrieved in one command and the other half in another command.
1095 MESSAGE Error while writing to temporary file ! (SDERR 1095)
CAUSE Error while writing to a temporary file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1096 MESSAGE Error while writing End-Of-File to temporary file ! (SDERR 1096)
CAUSE Error while writing an end-of-file marker to a temporary file.
ACTION Contact the DA. (Remember to get the associated error, too.)
1097 MESSAGE Purge failed on temporary file ! (SDERR 1097)
CAUSE Error while trying to delete a temporary file that is no longer needed.
ACTION Contact the DA. (Remember to get the associated error, too.)
Initialization Messages (1100-1149)
1100 MESSAGE Unable to find the Banner message in the catalog (SDERR 1100)
CAUSE Cannot retrieve the banner message from the message catalog.
ACTION Contact the DA to get a new copy of the catalog with the banner message in it.
1101 MESSAGE Word overflow, too many characters in message number ! (SDERR 1101)
CAUSE The number at the specified location in the message catalog is too large.
ACTION Contact the DA to get a new copy of the catalog with a legal number in the specified location.
1102 MESSAGE An illegal character was encountered in message number ! (SDERR 1102)
CAUSE The number at the specified location in the message catalog has an illegal character in it.
ACTION Contact the DA to get a new copy of the catalog with a legal number in the specified location.
1103 MESSAGE Illegal negative number found in message number ! (SDERR 1103)
CAUSE The number at the specified location in the message catalog is negative.
ACTION Contact the DA to get a new copy of the catalog with a legal number in the specified location.
1104 MESSAGE Invalid language number specified in the catalog (SDERR 1104)
CAUSE The language number specified in the catalog is invalid.
ACTION Contact the DA to get a new copy of the catalog with a valid language number.
1105 MESSAGE Error while converting a number in message set ! (SDERR 1105)
CAUSE Error encountered while converting a number in the specified set in the message catalog.
ACTION Refer to the associated error message for the message number of the bad number and the type of error encountered. Then, contact the DA to get a new copy of the catalog
A-155
with the error corrected.
1106 MESSAGE Abbreviation for command word ! is missing (SDERR 1106)
CAUSE The abbreviation for the specified command word in the command word set of the message catalog is missing.
ACTION Contact the DA to get a new copy of the catalog with the missing abbreviation present.
1107 MESSAGE Command word with abbreviation ! is missing (SDERR 1107)
CAUSE The command word with the specified abbreviation in the command word set of the message catalog is missing.
ACTION Contact the DA to get a new copy of the catalog with the missing command word present.
1108 MESSAGE Wild card character is missing (SDERR 1108)
CAUSE Wild card character is missing from the message catalog.
ACTION Contact the DA to get a new copy of the catalog with the missing wild card character present.
1109 MESSAGE SDMAIN and Dictionary Intrinsics versions are not compatible (SDERR
1109)
CAUSE The version of the SDMAIN program and the System Dictionary Intrinsics is not compatible.
ACTION Contact the DA and get a version of the SDMAIN program that is compatible with the version of the intrinsics that are on the system.
Driver Messages (1150-1174)
1150 MESSAGE Exceeded maximum number of allowed errors (SDWARN 1150)
CAUSE The system encountered the number of errors specified as the maximum in the PARM option.
ACTION Correct the errors found and rerun/finish running the job.
1151 MESSAGE Logging has been disabled (SDWARN 1151)
CAUSE Logging has been disabled because the user does not want the system to overwrite an existing log file.
ACTION Do nothing and no logging will take place or use the OPTIONS command to specify a new log file.
CAUSE Logging has been disabled because the current log file has filled up and an alternate log file was not available.
ACTION Do nothing and no logging will take place or use the OPTIONS command to specify a new log file.
1152 MESSAGE Logging proceeding on temporary file SDLOG (SDWARN 1152)
CAUSE Logging is being redirected to an alternate temporary file (SDLOG) after the permanent file (SDLOG) filled up.
A-156
ACTION Do nothing as logging will continue in a temporary file with the same name as the permanent file being logged to previously.
1153 MESSAGE SDLOG is a temporary file. Save if needed (SDWARN 1153)
CAUSE The log file was saved as a temporary file.
ACTION If the log file is not needed, do nothing and it will remain as a temporary file. If the log file is needed, save it (and rename it if its name is SDLOG).
1154 MESSAGE Expected End-Of-File NOT found in input file (SDERR 1154)
CAUSE Unexpected input lines found in the input file after an EXIT command.
ACTION Edit the input file to remove the extra lines.
1155 MESSAGE Hit End-Of-File of input file before executed an EXIT (SDERR 1155)
CAUSE The end of the input file was found without finding an EXIT command.
ACTION Edit the input file to place an EXIT command as the last command in the command stream.
1156 MESSAGE Logging will continue to the previous log file (SDWARN 1156)
CAUSE There was an error while trying to open the new log file. Logging will continue to the same file as before this command was issued.
ACTION Refer to the associated file error and correct the indicated problem.
Validator Messages (1175-1199)
1175 MESSAGE Invalid command (SDERR 1175)
CAUSE The command entered is not recognized by the system.
ACTION Issue a command that is recognized by the system (use HELP for help).
1176 MESSAGE Invalid command within a START/SAVE pair (SDERR 1176)
CAUSE The command entered is not allowed while within a START/SAVE pair.
ACTION Issue a command that is allowed within the pair (use HELP for help) or wait until the pair is completed before entering the command.
1177 MESSAGE Invalid subcommand (SDERR 1177)
CAUSE The subcommand entered is not recognized by the system.
ACTION Issue a subcommand that is recognized by the system (use HELP command for help).
1178 MESSAGE Invalid command/subcommand pair (SDERR 1178)
CAUSE The command and subcommand entered are not legal together.
ACTION Issue a command/subcommand pair that is allowed by the system (use HELP command for help).
1179 MESSAGE Command/subcommand pair is NOT valid in this open mode (SDERR 1179)
CAUSE The command/subcommand pair entered is not allowed in the current open mode.
ACTION Issue a command/subcommand pair that is allowed in the current open mode or switch
A-157
to the appropriate open mode for the specified command/subcommand pair.
1180 MESSAGE Command is NOT valid in this open mode (SDERR 1180)
CAUSE The command entered is not allowed in the current open mode.
ACTION Issue a command that is allowed in the current open mode or switch to the appropriate open mode for the specified command.
1181 MESSAGE Command is NOT allowed when processing a compiled dictionary (SDERR
1181)
CAUSE The command entered is not allowed when the currently opened dictionary is a compiled dictionary. The command is requesting a modification and a compiled dictionary cannot be modified.
ACTION Issue a command that is allowed in a compiled dictionary (any READ command is allowed) or switch to an appropriate master dictionary to make the desired modification.
Scanner/Parser/Prompt Messages (1200-1299)
1200 MESSAGE Missing closing quote on a character string (SDERR 1200)
CAUSE There is no closing quote on the character string specified.
ACTION Insert a closing quote in the appropriate location.
1201 MESSAGE Exceeded maximum number of temporary files (SDERR 1201)
CAUSE The command involves too many temporary files (probably in the form of too many variable length attributes specified in a single command).
ACTION Simplify the command so that it does less work (divide the operation into a two-step operation).
1202 MESSAGE Invalid character found (SDERR 1202)
CAUSE A character not allowed in the local language was found.
ACTION Remove the indicated character from the command string.
1203 MESSAGE Name is too long (SDERR 1203)
CAUSE The indicated name is greater than 32 characters.
ACTION Change the name so that it contains no more than 32 characters.
CAUSE The indicated character value is more than 32 characters long.
ACTION Enclose the character string in quotes.
1204 MESSAGE Invalid character for an MPE file name (SDERR 1204)
CAUSE The indicated character is not allowed in an MPE filename.
ACTION Remove the invalid character from the filename.
1210 MESSAGE Text skipped from last error to here (SDWARN 1210)
CAUSE Note indicating that some of the input string was not processed in order to recover from the preceding error.
A-158
ACTION No action is needed.
1211 MESSAGE Unexpected token for a Value (SDERR 1211)
CAUSE An attribute or keyword value was expected in the indicated location.
ACTION Insert the missing value or change the existing unexpected token into a valid value.
1212 MESSAGE Operators are NOT allowed here (SDERR 1212)
CAUSE A relational operator is not allowed for this value (it cannot be qualified).
ACTION Remove the operator from the command.
1213 MESSAGE Wild card characters are NOT allowed here (SDERR 1213)
CAUSE Wild card characters are not allowed for this value (it cannot be qualified).
ACTION Remove the wild card character from the value.
1214 MESSAGE Unexpected token: probably missing semicolon, comma, or quotes (SDERR
1214)
CAUSE The token indicated is not allowed in this position.
ACTION Review the command syntax and correct the entered command accordingly.
CAUSE A semicolon is expected before the indicated token to separate the object and a keyword clause or to separate two keyword clauses.
ACTION Insert a semicolon before the indicated token.
CAUSE A comma is expected before the indicated token to separate the attribute value clause from the next attribute value clause.
ACTION Insert a comma before the indicated token.
CAUSE The indicated character string contains characters not allowed in a System Dictionary name and so must be placed within a pair of quotes.
ACTION Place a pair of quotes around the indicated character string.
CAUSE There is a token missing at the indicated position.
ACTION Review the command syntax and insert the part of the command expected.
1215 MESSAGE Expected an Identifier (SDERR 1215)
CAUSE An identifier was expected at this location.
ACTION Insert an identifier or change the value in this position to an identifier.
1216 MESSAGE Too few values in the list (SDERR 1216)
CAUSE A relationship or relationship type must consist of at least 2 entities or entity types, respectively.
ACTION Include a list of at least 2 in the indicated position.
1217 MESSAGE Too many values in the list (SDERR 1217)
CAUSE A relationship or relationship type consists of a maximum of 6 entities or entity types, respectively.
ACTION Reduce the number of items in the list to no more than 6.
A-159
1218 MESSAGE Object clause expected (SDERR 1218)
CAUSE An object clause indicating the item on which to operate was expected here.
ACTION Include an object on which to operate.
1219 MESSAGE Characters found after the end of the command (SDERR 1219)
CAUSE Characters were found after the period ending the command.
ACTION Remove the extra characters that follow the period from the command.
1220 MESSAGE A period was expected here (SDERR 1220)
CAUSE No period was found to end the command.
ACTION Place a period at the end of the command.
1221 MESSAGE Invalid nested command (SDERR 1221)
CAUSE The nested command is not a valid command.
ACTION Enter a valid command as the nested command (EXECUTE).
CAUSE The nested command is not allowed as a nested command.
ACTION Enter a valid command as the nested command (EXECUTE).
1222 MESSAGE Invalid attribute name (SDERR 1222)
CAUSE The indicated string is not a valid attribute name.
ACTION Specify a valid attribute name.
1223 MESSAGE Equal expected (SDERR 1223)
CAUSE An equal sign is expected at the indicated location.
ACTION Place an equal sign in the command string as indicated.
1224 MESSAGE Missing close parenthesis (SDERR 1224)
CAUSE The closing parenthesis on the complex value is not present.
ACTION Place a closing parenthesis where specified.
CAUSE The closing parenthesis in the qualifying value is missing.
ACTION Place a closing parenthesis where specified.
1225 MESSAGE Bad character(s) after close parenthesis (SDERR 1225)
CAUSE The characters following the closing parenthesis are not any of the expected characters.
ACTION Check the command syntax and remove the unexpected characters or insert the missing expected characters.
1226 MESSAGE Expected a quoted character string (SDERR 1226)
CAUSE A quoted character string was expected in this position.
ACTION Supply a string within quotes.
CAUSE The value specified here is not quoted.
ACTION Place the string in quotes.
1227 MESSAGE Expected a filename (SDERR 1227)
A-160
CAUSE An MPE filename was expected here.
ACTION Modify the value in the indicated location to produce a valid filename.
1228 MESSAGE Invalid domain access (SDERR 1228)
CAUSE The specified domain access is not one of the valid domain accesses.
ACTION Check the valid domain accesses in the documentation and enter a valid one.
1229 MESSAGE Invalid list item (SDERR 1229)
CAUSE The item in the LIST list is not legal.
ACTION Remove the illegal item or change it to a legal list item.
1230 MESSAGE Invalid option flag (SDERR 1230)
CAUSE The specified option flag is not one of the valid option flags.
ACTION Check the valid option flags in the documentation and enter a valid one.
1231 MESSAGE Invalid name mode (SDERR 1231)
CAUSE The specified name mode is not one of the valid name modes.
ACTION Check the valid name modes in the documentation and enter a valid one.
1232 MESSAGE Invalid open mode (SDERR 1232)
CAUSE The specified open mode is not one of the valid open modes.
ACTION Check the valid open modes in the documentation and enter a valid one.
1233 MESSAGE Invalid output destination (SDERR 1233)
CAUSE The specified output destination is not one of the valid destinations.
ACTION Check the valid output destinations in the documentation and enter a valid one.
1234 MESSAGE Invalid scope rights (SDERR 1234)
CAUSE The specified scope right is not one of the valid scope rights.
ACTION Check the valid scope rights in the documentation and enter a valid one.
1235 MESSAGE Invalid scope access (SDERR 1235)
CAUSE The specified scope access is not one of the valid scope accesses.
ACTION Check the valid scope accesses in the documentation and enter a valid one.
1236 MESSAGE Invalid version status (SDERR 1236)
CAUSE The specified version status is not one of the valid version statuses.
ACTION Check the valid version statuses in the documentation and enter a valid one.
1237 MESSAGE Invalid attribute data type (SDERR 1237)
CAUSE The specified attribute data type is not one of the valid data types.
ACTION Check the valid data types in the documentation and enter a valid one.
1238 MESSAGE The number is out of range (SDERR 1238)
CAUSE The specified number is not in the legal range for the field.
A-161
ACTION Check the legal range for the field and specify a number in that range.
1239 MESSAGE The number is too large (maximum is 32767) (SDERR 1239)
CAUSE The specified number is too large to be represented internally. The largest number allowed in this position is 32767.
ACTION Enter a number that can be represented by the system.
1240 MESSAGE A number is required (SDERR 1240)
CAUSE A number value is required in the indicated location.
ACTION Change whatever value is in this position to an appropriate number.
1241 MESSAGE Quoted string not allowed here (SDERR 1241)
CAUSE A quoted character string is not allowed in this location.
ACTION Specify a value for the indicating position that is not a quoted string.
1242 MESSAGE Invalid keyword (SDERR 1242)
CAUSE The specified keyword is not one of the recognized keywords in the system.
ACTION Change the keyword to one recognized by the system (use HELP command subcommand for help).
1243 MESSAGE This keyword is NOT valid for this command/subcommand pair (SDERR
1243)
CAUSE The specified keyword is not allowed with the current command(/subcommand).
ACTION Change the keyword to one that is valid with the current command/subcommand (use
HELP command subcommand for help).
1244 MESSAGE This keyword had already been specified in the command (SDERR 1244)
CAUSE The indicated keyword has already been specified in the command.
ACTION Combine the two clauses into one clause for the command or eliminate the extra clause.
1245 MESSAGE There are illegal characters after a keyword flag (SDERR 1245)
CAUSE The specified keyword is a flag and has unexpected characters following it.
ACTION Remove the unexpected characters after the flag.
1246 MESSAGE A value is expected (SDERR 1246)
CAUSE A value is expected in the indicated location.
ACTION Enter an appropriate value where indicated.
1247 MESSAGE Unexpected left parenthesis (SDERR 1247)
CAUSE Found an unexpected left parenthesis where Selection Criteria is not allowed.
ACTION Remove the parenthesis and any Selection Criteria as they are not allowed in this location.
CAUSE The indicated keyword clause does not have a complex value and so cannot be within parenthesis.
ACTION Remove the parenthesis and issue an appropriate value clause for the keyword.
A-162
1248 MESSAGE Expected a left parenthesis (SDERR 1248)
CAUSE Expected an opening left parenthesis for the complex value to be entered.
ACTION Insert parenthesis around the value for this keyword clause.
1249 MESSAGE Required keyword ! not specified (SDERR 1249)
CAUSE The supplied keyword is required for this command but was not included.
ACTION Insert the required keyword clause.
1250 MESSAGE The number specified here must be positive (SDERR 1250)
CAUSE The number in the specified location must be positive.
ACTION Change the indicated number from a negative to an appropriate positive number.
1252 MESSAGE No keywords are allowed for this command/subcommand pair (SDERR 1252)
CAUSE The specified command/subcommand does not have any keywords.
ACTION Remove the keyword clause from the command and execute it.
1253 MESSAGE = and <> are the only operators allowed (SDERR 1253)
CAUSE Only = and <> operators are allowed when dealing with scope rights (other relational operators are not meaningful as the rights are not hierarchical).
ACTION Change the Selection Criteria so that only = and <> operations are used.
1254 MESSAGE There is a duplicate scope right entry (SDERR 1254)
CAUSE The indicated scope right is specified more than one time.
ACTION Remove the duplicate specification of the scope right.
1255 MESSAGE Expected a Nested Execute command (SDERR 1255)
CAUSE A nested EXECUTE command was expected in the SUB-REPORT clause.
ACTION Either specify a nested EXECUTE or remove the SUB-REPORT clause.
1256 MESSAGE Expected an 'attribute = value' pair (SDERR 1256)
CAUSE Expected an attribute to be assigned a value (value can be blank) here.
ACTION Check the syntax of the ATTRIBUTE-LIST clause. Probably need to remove an extra comma before the closing parenthesis of the clause.
1257 MESSAGE Expected an attribute edit value (SDERR 1257)
CAUSE Expected an edit value for the attribute.
ACTION If there is an extra comma with no value, remove it. Otherwise, make sure that the attribute edit values specified are legal for the attribute type (remember, quotes are required if a character string will not be accepted as a legal System Dictionary name).
1258 MESSAGE Ranges are legal only for numeric edit values (SDERR 1258)
CAUSE Ranges of values in the EDIT-VALUE list are allowed only for numeric data types
(integer and floating).
ACTION If the attribute is of a numeric type, specify only numeric values and the range can remain. Otherwise, a range is not allowed for this type so the possibilities must be listed explicitly.
A-163
1259 MESSAGE A number range can consist of only two values (SDERR 1259)
CAUSE A range consists of just two numeric values (val1 : val2). There is a range specified with more than two values (i.e. val1 : val2 : val3).
ACTION Collapse the values into a range of two values or use several values and/or ranges separated by commas to build the edit value list for the attribute.
1260 MESSAGE Invalid macro parameter name (SDERR 1260)
CAUSE One or more wild card characters are specified in the parameter name. They are not allowed as they confuse the substitution process.
ACTION Change the name of the indicated parameter to remove all wild card characters.
CAUSE The indicated parameter name in the macro header is not a valid name for a parameter.
ACTION The indicated parameter name should be corrected to make it into a name acceptable to System Dictionary.
1261 MESSAGE Expected a macro parameter (SDERR 1261)
CAUSE Expected a parameter to be specified in the macro header at this point.
ACTION There is probably an extra comma in the macro header with no parameter specified.
1275 MESSAGE Illegal menu option found at position ! (SDERR 1275)
CAUSE There is an unexpected character at the indicated position.
ACTION Enter a valid option (a number).
1276 MESSAGE ! is not in the valid range for menu options (SDERR 1276)
CAUSE The indicated number is not one of the possible numbers on the menu.
ACTION Look at the menu and choose a valid option from it.
1277 MESSAGE Invalid range specified at position ! (SDERR 1277)
CAUSE The end of the range is the same as the start of the range.
ACTION No range is needed as it is a single number. So, just enter the single number and do not specify a range.
CAUSE The end of the range is less than the start of the range.
ACTION Specify a higher ending point than starting point for the range.
1278 MESSAGE Invalid use of colon or comma at position ! (SDERR 1278)
CAUSE The indicated comma or colon is used incorrectly.
ACTION Do nothing as it is ignored. The next time the option string is entered, remove the extra comma/colon.
1279 MESSAGE Prompting can be used only when input is from $STDINX (SDERR 1279)
CAUSE Prompting for attributes makes sense only when input is interactive (from $STDINX).
ACTION Do nothing as no action is taken and prompting is not allowed.
1280 MESSAGE Invalid alignment option (SDERR 1280)
CAUSE The specified alignment option is not one of the valid alignment options.
A-164
ACTION Check the valid alignment options in the documentation and enter a valid one.
Configure Messages (1300-1324)
1300 MESSAGE Too few columns are specified for the terminal (SDERR 1300)
CAUSE The number specified for the SCREEN-WIDTH keyword is too small.
ACTION Specify a number for the SCREEN-WIDTH that is 53 or larger. This size is required because the width must be able to handle a 32-character name, a 15-character header and some spacing.
1301 MESSAGE Too many columns are specified for the terminal (SDERR 1301)
CAUSE The number specified for the SCREEN-WIDTH keyword is too large.
ACTION Specify a number for the SCREEN-WIDTH that is not larger than the maximum output size (132).
1302 MESSAGE Too few lines are specified for the terminal (SDERR 1302)
CAUSE The number specified for the SCREEN-LENGTH keyword is too small.
ACTION Specify a number for the SCREEN-LENGTH that is 1 or larger.
1303 MESSAGE Too few columns are specified for a page of paper (SDERR 1303)
CAUSE The number specified for the PAGE-WIDTH keyword is too small.
ACTION Specify a number for the PAGE-WIDTH that is 53 or larger. This size is required because the width must be able to handle a 32 character name, a 15-character header and some spacing.
1304 MESSAGE Too many columns are specified for a page of paper (SDERR 1304)
CAUSE The number specified for the PAGE-WIDTH keyword is too large.
ACTION Specify a number for the PAGE-WIDTH that is not larger than the maximum output size (132).
1305 MESSAGE Too few lines specified for a page of paper (SDERR 1305)
CAUSE The number specified for the PAGE-LENGTH keyword is too small.
ACTION Specify a number for the PAGE-LENGTH that is 1 or larger.
1306 MESSAGE Configure not executed due to error (SDWARN 1306)
CAUSE There was an error in one or more of the CONFIGURE values so none of the values were changed.
ACTION Refer to the associated error and correct the indicated problem.
1307 MESSAGE SINGLE-SPACE used instead of PAGE (SDWARN 1307)
CAUSE The SINGLE-SPACE keyword is recognized and the PAGE keyword ignored.
ACTION No action is needed. The next time the command is issued, specify only one spacing option.
1308 MESSAGE SINGLE-SPACE used instead of DOUBLE-SPACE (SDWARN 1308)
A-165
CAUSE The SINGLE-SPACE keyword is used and the DOUBLE-SPACE keyword ignored.
ACTION No action is needed. The next time the command is issued, specify only one spacing option.
1309 MESSAGE DOUBLE-SPACE used instead of PAGE (SDWARN 1309)
CAUSE The DOUBLE-SPACE keyword is used and the PAGE keyword ignored.
ACTION No action is needed. The next time the command is issued, specify only one spacing option.
1310 MESSAGE Default margins and report page-length are incompatible (SDWARN 1310)
CAUSE The output file and page-length fields cannot be reassigned while in a nested report
(you do not want output sent to different files or have the page length changing within a file while in the same report). When the values for these fields are reset to their default values, they are not compatible with the page defined by the top level report.
ACTION No action is required as the margins and page-length of the top level report are used.
The incompatibility should be checked to make sure the various levels of the report are all set up to write to the same size paper.
Define Messages (1325-1349)
1325 MESSAGE The ! keyword is ignored in customization mode (SDWARN 1325)
CAUSE The indicated keyword is not allowed if the open mode of the dictionary is going to be
CUSTOMIZATION.
ACTION Do nothing as the clause is ignored. The next time the dictionary is open in
CUSTOMIZATION mode, do not specify this keyword.
1326 MESSAGE Both VERSION and STATUS were specified. STATUS is ignored (SDWARN
1326)
CAUSE Both the VERSION and STATUS keyword cannot be specified in the same command.
Either VERSION for a specific version or STATUS for the last version of the given status should be used.
ACTION Do nothing as the version will be used and the status ignored. The next time the dictionary is opened, specify either a specific version (VERSION) or a specific status
(STATUS) but not both.
1327 MESSAGE Quoted passwords cannot extend to multiple lines (SDERR 1327)
CAUSE If the password is entered within quotes it must be entered on a single line.
ACTION Specify the password so that the opening and closing quotes are on the same line.
1328 MESSAGE Invalid scope password. Remember case counts (SDWARN 1328)
CAUSE An invalid password has been entered in response to the scope password prompt.
Remember, System Dictionary distinguishes between uppercase and lowercase characters in a scope password.
ACTION Specify the correct password for the scope.
1329 MESSAGE Exceeded maximum tries for a valid scope password (SDERR 1329)
A-166
CAUSE Unable to open the dictionary because a valid scope password was not specified within three tries.
ACTION Reenter the DEFINE command and specify the correct password for the scope.
1330 MESSAGE Unexpected End-Of-File on $STDINX (SDERR 1330)
CAUSE Reached the end of the file on $STDINX when trying to read the scope password.
ACTION Refer to the associated file error and correct the indicated problem.
1331 MESSAGE Unable to turn the echo facility off (SDERR 1331)
CAUSE Unable to turn the echo facility off through the FControl Intrinsic when prompting for the scope password.
ACTION Contact the DA. (Remember to get the associated file error, too.)
1332 MESSAGE Unable to turn the echo facility on (SDERR 1332)
CAUSE Unable to turn the echo facility on through the FControl Intrinsic when prompting for the scope password.
ACTION Contact the DA. (Remember to get the associated file error, too.)
Edit Messages (1350-1374)
1350 MESSAGE EDIT only allowed when input is from $STDINX (SDERR 1350)
CAUSE The EDIT command is only allowed when input is interactive (or when running interactively and input is from a redirected STDIN).
ACTION Use the MODIFY command in the command file or batch job to 'edit' an existing variable attribute or report.
1351 MESSAGE No EDTXT file is available so the edit fails (SDERR 1351)
CAUSE No edit file could be opened so the EDIT command has been disabled.
ACTION The system tried to open files EDTXT0 through EDTXT999 and failed. Either there is insufficient disc space for this file or files exist with all of these names. Rerun the system with the above problem corrected. For now, the same results can be obtained by using the appropriate MODIFY command and entering the complete text.
1352 MESSAGE Cannot delete the variable length attribute (SDERR 1352)
CAUSE The old variable attribute could not be deleted.
ACTION Contact the DA. Internal Error.
1353 MESSAGE Cannot create the variable length attribute (SDERR 1353)
CAUSE The variable length attribute could not be created with the new text.
ACTION Refer to the associated error.
1354 MESSAGE Cannot invoke EDIT/V (SDERR 1354)
CAUSE The EDIT/V program could not be invoked from the program.
ACTION Make sure that the EDIT/V program is on the system. If it is, contact the DA. Internal
Error.
A-167
1355 MESSAGE The report definition does not exist (SDERR 1355)
CAUSE There is no definition stored for the indicated report.
ACTION Contact the DA. Internal Error. The definition was deleted manually without using the
SDMAIN commands that manipulate reports or the dictionary has been corrupted.
1356 MESSAGE The report description does not exist (SDERR 1356)
CAUSE There is no description stored for the specified report.
ACTION Use the MODIFY REPORT command to add the new text as the description for the report.
1357 MESSAGE The entity was deleted while being edited (SDERR 1357)
CAUSE The entity was deleted by another user while its attribute was being edited.
ACTION Do nothing if the entity is not needed. If it is needed, find out who deleted it and why.
To avoid this problem, open the dictionary in EXCLUSIVE-UPDATE mode.
1358 MESSAGE The relationship was deleted while being edited (SDERR 1358)
CAUSE The relationship was deleted by another user while its attribute was being edited.
ACTION Do nothing if the relationship is not needed. If it is needed, find out who deleted it and why. To avoid this problem, open the dictionary in EXCLUSIVE-UPDATE mode.
1359 MESSAGE The report was deleted while being edited (SDERR 1359)
CAUSE The report was deleted by another user while its definition or description was being edited.
ACTION Do nothing if the report is not needed. If it is needed, find out who deleted it and why.
To avoid this problem, open the dictionary in EXCLUSIVE-UPDATE mode.
1360 MESSAGE Cannot delete report ! (SDERR 1360)
CAUSE All lines of the report definition were deleted during editing but the report cannot be deleted from the system.
ACTION Contact the DA. Internal Error.
Format Messages (1375-1399)
1375 MESSAGE Value for ! is too long (SDWARN 1375)
CAUSE The value specified for the PAGE-HEADER or TITLE keyword is longer than the maximum output width (132 characters) of the system.
ACTION Reduce the length of the value to no more than the maximum output width. Probably want to reduce the length to less than or equal to the current output width or the line will be truncated when printed.
Help Messages (1400-1424)
1400 MESSAGE Expected a period (SDERR 1400)
A-168
CAUSE A period was expected in the indicated position if any character is present.
ACTION Remove the unexpected character and replace them by a period or blanks.
1401 MESSAGE Expected a command or a period (SDERR 1401)
CAUSE The characters after the HELP command must be either a command or a period.
ACTION Remove the unexpected characters and replace them by a command, a period, or blanks.
1402 MESSAGE Command does not have a subcommand (SDERR 1402)
CAUSE The specified command does not have a subcommand.
ACTION Remove the subcommand from the command line. May want to check to see if the desired command is specified correctly.
1403 MESSAGE Expected a subcommand or a period (SDERR 1403)
CAUSE The characters after the HELP command must be either a subcommand or a period.
ACTION Remove the unexpected characters and replace them by a subcommand, a period, or blanks.
1404 MESSAGE Macros do not have subcommands (SDERR 1404)
CAUSE Macros are identified by the name and cannot be qualified in the HELP command.
ACTION Reenter the command specifying only HELP and the macro name.
1405 MESSAGE Help not available for this macro definition (SDWARN 1405)
CAUSE The NOHELP option is specified in the definition for the requested macro so the HELP command cannot be used to display its definition.
ACTION No action is needed. If the command definition should be accessible, edit the macro file to remove the NOHELP option from the macro header.
Redo Messages (1425-1449)
1425
CAUSE
MESSAGECannot REDO a REDO command (SDERR 1425)
REDO cannot be used to change a command into a REDO command.
ACTION Do not change a command being edited to a REDO command.
1426 MESSAGE REDO and SHOWREDO only allowed when input is from $STDINX (SDERR
1426)
CAUSE The REDO command and SHOWREDO command are only allowed when input is interactive (or when running interactively and input is from a redirected STDIN).
ACTION Enter the entire command in the command file or batch job instead of trying to use
REDO or SHOWREDO.
1427 MESSAGE No command has been entered to REDO (SDERR 1427)
CAUSE No command has been entered into the SDMAIN from the current input file yet.
ACTION Enter a command other than REDO. Then use REDO to reissue or correct the command entered.
A-169
1428 MESSAGE The number is too large (SDERR 1428)
CAUSE The number entered causes an integer overflow.
ACTION Reissue the +/- command with a smaller number.
1429 MESSAGE There are illegal characters in the number (SDERR 1429)
CAUSE There are unexpected characters in the number.
ACTION Reissue the +/- command with all non-digit characters removed.
1430 MESSAGE Must break the line before insert/append to prevent line overflow (SDERR
1430)
CAUSE Together, the existing line and the string to be inserted or appended will not fit on a single input line.
ACTION Break the existing line so that the new line and the string to be inserted or appended will fit on a single input line.
1431 MESSAGE Bad command after delete (ignored) (SDERR 1431)
CAUSE Unexpected characters were on the line after the DELETE command.
ACTION Delete can consist of a continuous string of one or more D' s or two single D' s, with blanks between. The only other command allowed on the same line as a Delete is an
Insert (I). It (I) is allowed after either of the two D strings.
1432 MESSAGE The entire command has been deleted (SDWARN 1432)
CAUSE The entire command in the REDO buffer has been deleted.
ACTION Since the entire command was deleted, the REDO system returns to the command mode. Edit the original command or issue a new command.
1433 MESSAGE Unexpected characters after REDO command (SDERR 1433)
CAUSE There are characters on the line after the REDO system command. Except for the D/I combination, only a single edit command can be entered on a line.
ACTION Reissue the edit command with only a single command on the line.
1434 MESSAGE + and - NOT allowed in a number (SDERR 1434)
CAUSE The numbers used to move within REDO buffer cannot involve a + or -.
ACTION Remove the + or - from the number specifying how far to move and simply use the appropriate command to specify direction (+ to move forward and - to move backward).
1435 MESSAGE The quoted string after REDO must contain at least one char (SDERR 1435)
CAUSE The string specified after the REDO command contains no characters (or only blanks).
A qualifying value must contain at least one non-blank character.
ACTION Reenter the REDO command specifying a qualifying string to be used to determine the appropriate command to select from the redo history stack.
1436 MESSAGE No match found for the requested string in the redo stack (SDERR 1436)
CAUSE No match was found for the specified string in the redo history stack.
ACTION Use the SHOWREDO command to obtain a list of the commands currently in the redo history stack. If the desired command is present, select it by number (either absolute
A-170
or relative) or provide a qualifying string that matches the start of the command.
1437 MESSAGE No command is currently stored in the referenced location (SDERR 1437)
CAUSE No command is stored in the redo stack at the location referred to by the absolute or relative number offset specified.
ACTION Use the SHOWREDO command to obtain a list of the commands currently in the redo history stack. Specify an absolute or relative command number that will refer to one of the commands listed by the command or issue a command that performs the desired action.
Redo Messages (1425-1449)
1425 MESSAGE Cannot REDO a REDO command (SDERR 1425)
CAUSE REDO cannot be used to change a command into a REDO command.
ACTION Do not change a command being edited to a REDO command.
1426 MESSAGE REDO and SHOWREDO only allowed when input is from $STDINX (SDERR
1426)
CAUSE The REDO command and SHOWREDO command are only allowed when input is interactive (or when running interactively and input is from a redirected STDIN).
ACTION Enter the entire command in the command file or batch job instead of trying to use
REDO or SHOWREDO.
1427 MESSAGE No command has been entered to REDO (SDERR 1427)
CAUSE No command has been entered into the SDMAIN from the current input file yet.
ACTION Enter a command other than REDO. Then use REDO to reissue or correct the command entered.
1428 MESSAGE The number is too large (SDERR 1428)
CAUSE The number entered causes an integer overflow.
ACTION Reissue the +/- command with a smaller number.
1429 MESSAGE There are illegal characters in the number (SDERR 1429)
CAUSE There are unexpected characters in the number.
ACTION Reissue the +/- command with all non-digit characters removed.
1430 MESSAGE Must break the line before insert/append to prevent line overflow (SDERR
1430)
CAUSE Together, the existing line and the string to be inserted or appended will not fit on a single input line.
ACTION Break the existing line so that the new line and the string to be inserted or appended will fit on a single input line.
1431 MESSAGE Bad command after delete (ignored) (SDERR 1431)
CAUSE Unexpected characters were on the line after the DELETE command.
A-171
ACTION Delete can consist of a continuous string of one or more D' s or two single D' s, with blanks between. The only other command allowed on the same line as a Delete is an
Insert (I). It (I) is allowed after either of the two D strings.
1432 MESSAGE The entire command has been deleted (SDWARN 1432)
CAUSE The entire command in the REDO buffer has been deleted.
ACTION Since the entire command was deleted, the REDO system returns to the command mode. Edit the original command or issue a new command.
1433 MESSAGE Unexpected characters after REDO command (SDERR 1433)
CAUSE There are characters on the line after the REDO system command. Except for the D/I combination, only a single edit command can be entered on a line.
ACTION Reissue the edit command with only a single command on the line.
1434 MESSAGE + and - NOT allowed in a number (SDERR 1434)
CAUSE The numbers used to move within REDO buffer cannot involve a + or -.
ACTION Remove the + or - from the number specifying how far to move and simply use the appropriate command to specify direction (+ to move forward and - to move backward).
1435 MESSAGE The quoted string after REDO must contain at least one char (SDERR 1435)
CAUSE The string specified after the REDO command contains no characters (or only blanks).
A qualifying value must contain at least one non-blank character.
ACTION Reenter the REDO command specifying a qualifying string to be used to determine the appropriate command to select from the redo history stack.
1436 MESSAGE No match found for the requested string in the redo stack (SDERR 1436)
CAUSE No match was found for the specified string in the redo history stack.
ACTION Use the SHOWREDO command to obtain a list of the commands currently in the redo history stack. If the desired command is present, select it by number (either absolute or relative) or provide a qualifying string that matches the start of the command.
1437 MESSAGE No command is currently stored in the referenced location (SDERR 1437)
CAUSE No command is stored in the redo stack at the location referred to by the absolute or relative number offset specified.
ACTION Use the SHOWREDO command to obtain a list of the commands currently in the redo history stack. Specify an absolute or relative command number that will refer to one of the commands listed by the command or issue a command that performs the desired action.
Renumber/Resequence Messages (1450-1474)
1450 MESSAGE Cannot resequence the relationship due to a collision (SDERR 1450)
CAUSE The relationship cannot be resequenced as there is no relationship-position number available at the destination location (either the relationship must go before a relationship with relationship-position of 1, after a relationship with relationshipposition of the maximum value, or between two relationships numbered consecutively).
A-172
ACTION Use the RENUMBER command to renumber the relationships of the type with an
INCREMENT of at least 2. Then issue the command again.
1451 MESSAGE Error while modifying the relationship-position (SDERR 1451)
CAUSE An error was encountered while the relationship-position was being changed.
ACTION Contact the DA. Internal error.
1452 MESSAGE Error in retrieving the relationship (SDERR 1452)
CAUSE Cannot retrieve the indicated relationship to resequence.
ACTION Refer to the associated error and correct the problem.
1453 MESSAGE Error in retrieving the before relationship (SDERR 1453)
CAUSE Cannot retrieve the indicated relationship to resequence before.
ACTION Refer to the associated error and correct the problem.
1454 MESSAGE Error in retrieving the relationship-position (SDERR 1454)
CAUSE An error was encountered while retrieving the relationship-position.
ACTION Contact the DA. Internal Error.
1455 MESSAGE BEFORE-ENTITY and relationship to be moved must be different (SDERR
1455)
CAUSE The relationship to be resequenced was requested to be moved before itself.
ACTION The command does nothing so can be skipped.
1456 MESSAGE Cannot resequence as only one relationship of the type exists (SDWARN 1456)
CAUSE A resequence was requested when there is only one relationship of the type.
ACTION The command does nothing so can be skipped.
1457 MESSAGE Unexpected error. RENUMBER is only partially completed (SDERR 1457)
CAUSE An error was encountered while updating the relationship-positions. The sequence of the relationships remains the same but their relationship-position may be changed.
ACTION Contact the DA. Internal Error.
1458 MESSAGE Combination of START-POSITION and INCREMENT leads to overflow
(SDERR 1458)
CAUSE With the given START-POSITION and INCREMENT and the number of relationships of the type, the relationship-position field will overflow by the end of the list.
ACTION Modify the START-POSITION and/or INCREMENT so that they will not lead to overflow during the processing of the list.
1459 MESSAGE There are no relationships to renumber (SDERR 1459)
CAUSE There are no relationships of the type to renumber.
ACTION The command does nothing so can be skipped.
1460 MESSAGE Current scope needs modify access to all relationships of the type (SDERR
1460)
CAUSE The current scope does not have modify access to all of the required subset of
A-173
relationships of the specified relationship type. The required subset consists of all relationships having the given entity in the first position. In order to RENUMBER or
RESEQUENCE a relationship, the user must have modify access to all the relationships in this subset.
ACTION Open the dictionary as either the DA scope or as a scope with modify access to all the relationships of the specified relationship type.
1461 MESSAGE BEFORE-ENTITY has incorrect number of entities for the rel-type (SDERR
1461)
CAUSE Too few entities were specified in the BEFORE-ENTITY entity list when the command was entered. The entity in the clause must consist of a list of the entities having one less entity than the relationship type has, as there is no entity corresponding to the parent entity.
ACTION Reenter the command, specifying a valid child entity (entity list) for the relationship type of the relationship being resequenced.
Macro Processor Messages (1475-1499)
1475 MESSAGE Restoring macros from previous SDMACRO file (SDWARN 1475)
CAUSE Due to the noted error encountered during loading of the newly specified macro file, the macros from the previous macro file will be restored.
ACTION No action is needed. The indicated error must be corrected to allow the specified file to be used as a macro file in the future.
1476 MESSAGE Invalid name for a macro at line ! in SDMACRO file (SDERR 1476)
CAUSE The name specified for the macro definition beginning at the indicated line is not a valid name.
ACTION The indicated macro is invalid at this time. The macro file should be edited to correct the invalid name so the macro can be used in future runs of the program.
1477 MESSAGE No name specified for macro at line ! in SDMACRO file (SDERR 1477)
CAUSE There was no name specified for the macro definition beginning at the indicated line.
ACTION The indicated macro is invalid at this time. The macro file should be edited to correct the invalid name so the macro can be used in future runs of the program. (There is probably just an extra blank line in the file that should be removed.)
1478 MESSAGE Errors in header for macro at line ! in SDMACRO file (SDERR 1478)
CAUSE One or more errors were detected in the header for the macro beginning on the indicated line.
ACTION See the associated error messages for an explanation of the errors found. The indicated macro is invalid at this time. The macro file should be edited to correct the invalid header so the macro can be used in future runs of the program.
1479 MESSAGE The macro call has more parameters than the definition (SDERR 1479)
CAUSE The macro call specifies more parameters than are specified in the definition in the macro file.
A-174
ACTION Use the HELP macro-name command to find the definition of the macro and correct the call to correspond to the number of parameters defined in the macro. If HELP shows that the macro definition is not what you wanted, the next time you exit the system, edit the macro file to adjust the definition as needed and the macro will be ready for all future runs.
1480 MESSAGE The value ! could not be substituted into the definition (SDERR 1480)
CAUSE The indicated value could not be substituted into the macro definition as the line it is being substituted on cannot be split.
ACTION Edit the macro definition to have some kind of punctuation (blank, period, comma, etc.) on the affected line. This allows the system to break the line at a consistent point and perform the substitution.
1481 MESSAGE No macro file has been specified (SDERR 1481)
CAUSE A SHOWMACRO command was issued but no macro file has been initialized. So, there are no macro names to report.
ACTION Use the OPTIONS command to load a macro file and then issue the SHOWMACRO to see what macro names were loaded. No action is required if you do not wish to use any macros.
1482 MESSAGE Macro name ! conflicts with a command name (SDERR 1482)
CAUSE The indicated macro name conflicts with an SDMAIN command name.
ACTION Change the name of the macro to one that does not conflict with an SDMAIN command name. The indicated macro will not be available for the current execution.
1483 MESSAGE No value specified for required parameter ! (SDERR 1483)
CAUSE The specified parameter is a required parameter but no value is provided on the call.
ACTION Provide a value for the specified parameter. If the parameter really should be optional, you can make it optional by editing the macro header to provide a default value of a null value (that is, parm=). This allows you to omit a value for the parameter if desired and the system will substitute nothing in its place.
1484 MESSAGE Invalid macro option (SDERR 1484)
CAUSE The specified macro option is not one of the valid macro options.
ACTION Check the valid macro options in the documentation and enter a valid one. The indicated macro will not be available for the current execution.
1485 MESSAGE Conflicting macro option. Default value ! used (SDWARN 1485)
CAUSE The indicated macro option conflicts with a previous macro option.
ACTION No action is required at this time. The macro will be defined for the current execution using the specified default value for the conflicting options. You should edit the macro file to remove the conflicting options for future uses of the macro file.
1486 MESSAGE Must supply a value for the required parameter (SDWARN 1486)
CAUSE The parameter being prompted for is a required parameter. A value is required for all required parameters.
ACTION The system reprompts for the parameter. To execute the macro, enter an appropriate value for this parameter. To cancel the macro, press [[Control]] Y. If the parameter is
A-175
required, no further action is needed; however, if the parameter is optional or has a default value that can be used if no new value is entered, you should edit the macro header to provide the desired default value before the program is run the next time.
1487 MESSAGE Expected a simple value or a quoted string for parameter value (SDERR 1487)
CAUSE The value entered for the last prompt contains a character not allowed in a valid name or contains more than 32 characters. The value you enter for a macro parameter must be a name, number, or quoted text string.
ACTION If the value is supposed to be a simple value, correct the error and reenter the value at the prompt. If the value contains an illegal character, such as a blank, then reenter the value at the prompt specifying the value within a pair of quotes.
Create/Copy/Modify Messages (1500-1599)
1500 MESSAGE The text for Variable attribute ! was too long (truncated) (SDWARN 1500)
CAUSE The text for the indicated variable length attribute is greater than the maximum allowed by the system. The maximum length allowed is accepted and the remainder truncated.
ACTION No action is needed as the maximum length is stored with any excess truncated.
1501 MESSAGE The text for fixed attribute ! was too long (truncated) (SDWARN 1501)
CAUSE The text for the fixed length character string is longer than the attribute length. The maximum length is stored and the remainder truncated.
ACTION No action is needed as the attribute length number of characters are stored with any excess truncated.
1502 MESSAGE Exceeded max attr per type. Attributes after ! ignored (SDERR 1502)
CAUSE More attributes are specified than are allowed to be associated to a type.
ACTION Check to make sure that all the attributes specified are linked to the type or are alias or variable attributes. If the check is OK, split the command into two pieces and assign values to all of the fixed attributes in one half and the alias and variable attributes in the other.
1503 MESSAGE Exceeded buffer maximum. Attributes after ! ignored (SDERR 1503)
CAUSE The buffer holding the attribute values overflowed.
ACTION Break the attributes into two pieces and use two commands to perform the operation desired.
1504 MESSAGE Attribute ! does not exist (SDERR 1504)
CAUSE The indicated attribute does not exist.
ACTION Create the attribute before proceeding or specify an attribute that does exist.
1505 MESSAGE Couldn't restore variable attributes (SDERR 1505)
CAUSE The variable attributes cannot be restored.
ACTION Contact the DA. Internal Error.
A-176
1506 MESSAGE Unable to lock System Dictionary (SDERR 1506)
CAUSE The dictionary lock failed.
ACTION Contact the DA. Internal Error.
1507 MESSAGE System Dictionary Integrity may be lost (SDERR 1507)
CAUSE Dictionary operations performing a portion of the operations indicated by the command completed. The remainder did not completed due to an error and the operations that completed cannot be reversed.
ACTION Contact the DA. Internal Error.
1508 MESSAGE Cannot retrieve source version ! (SDERR 1508)
CAUSE The source version does not exist in the current domain.
ACTION Refer to the associated error and correct the indicated problem.
1509 MESSAGE Cannot create the target version (SDERR 1509)
CAUSE The target version could not be created.
ACTION Refer to the associated error and correct the indicated problem.
1510 MESSAGE Cannot get Relationship-Type attribute list (SDERR 1510)
CAUSE Error encountered while retrieving the attribute list for a relationship type.
ACTION Contact the DA. Internal Error.
1511 MESSAGE Cannot retrieve relationships of the source entity (SDERR 1511)
CAUSE Error encountered while retrieving a relationship involving the source entity.
ACTION Contact the DA. Internal Error.
1512 MESSAGE Cannot create a relationship (SDERR 1512)
CAUSE Cannot create one of the target relationships.
ACTION Refer to the associated error and correct the indicated problem.
1513 MESSAGE Cannot get Entity-Type attribute list (SDERR 1513)
CAUSE Error encountered while retrieving the attribute list for the entity type.
ACTION Contact the DA. Internal Error.
1514 MESSAGE Cannot retrieve the source entity (SDERR 1514)
CAUSE Error encountered while retrieving the source entity.
ACTION Refer to the associated error and correct the indicated problem.
1515 MESSAGE Cannot create the target entity (SDERR 1515)
CAUSE Error encountered while creating the target entity.
ACTION Refer to the associated error and correct the indicated problem.
1516 MESSAGE Cannot retrieve needed attribute(s) (SDERR 1516)
CAUSE Error encountered while retrieving an attribute needed for command execution.
ACTION Contact the DA. Internal Error.
A-177
1517 MESSAGE Cannot retrieve a variable length attribute value (SDERR 1517)
CAUSE Error encountered while retrieving a variable length attribute value.
ACTION Contact the DA. Internal Error.
1518 MESSAGE Cannot create a variable length attribute value (SDERR 1518)
CAUSE Error encountered while creating a new variable attribute.
ACTION Refer to the associated error and correct the indicated problem.
1519 MESSAGE Position specified is too high for the relationship (SDERR 1519)
CAUSE POSITION specified by the user is larger than the number of entities involved in the relationship.
ACTION Change the POSITION value to one that is between 1 and the number of entities involved in the relationship (inclusive).
1520 MESSAGE Cannot retrieve the source report (SDERR 1520)
CAUSE Error encountered while retrieving the source report.
ACTION Refer to the associated error and correct the indicated problem.
1521 MESSAGE Cannot create the target report (SDERR 1521)
CAUSE Error encountered while creating the target report.
ACTION Refer to the associated error and correct the indicated problem.
1522 MESSAGE No attributes were added (SDERR 1522)
CAUSE No attributes are added to the entity type/relationship type.
ACTION Refer to the associated error and correct the indicated problem.
1523 MESSAGE Attribute ! was not added (SDERR 1523)
CAUSE The indicated attribute is not added to the entity type/relationship type.
ACTION Refer to the associated error and correct the indicated problem.
1524 MESSAGE No attribute pairs were modified (SDERR 1524)
CAUSE No modifications are made to any of the entity type/relationship type pairs.
ACTION Refer to the associated error and correct the indicated problem.
1525 MESSAGE The pair with attribute ! was not modified (SDERR 1525)
CAUSE The indicated attribute of the entity type/relationship type pair is not modified.
ACTION Refer to the associated error and correct the indicated problem.
1526 MESSAGE No attributes were removed (SDERR 1526)
CAUSE No attributes are removed from the entity type/relationship type.
ACTION Refer to the associated error and correct the indicated problem.
1527 MESSAGE Attribute ! was not removed (SDERR 1527)
CAUSE The indicated attribute is not removed from the entity type/relationship type.
ACTION Refer to the associated error and correct the indicated problem.
A-178
1528 MESSAGE Illegal character in value for attribute ! (SDERR 1528)
CAUSE An illegal character is found in the value for the indicated attribute.
ACTION Remove the illegal character and reissue the command.
1529 MESSAGE No integer or fraction found in attribute ! (SDERR 1529)
CAUSE No integer (base) or fraction (exponent) is found in the indicated number.
ACTION Correct the number so that a valid number is specified.
1530 MESSAGE Number > largest representable value for attribute ! (SDERR 1530)
CAUSE The value for the indicated attribute is too large to be represented in the system.
ACTION Reduce the size of the number and reissue the command.
1531 MESSAGE Number < smallest representable value for attribute ! (SDERR 1531)
CAUSE The value for the indicated attribute is too small to be represented in the system.
ACTION Increase the size of the number and reissue the command.
1532 MESSAGE Number too large and illegal character for attribute ! (SDERR 1532)
CAUSE The value for the indicated attribute is too large to be represented in the system and contains an invalid character.
ACTION Remove the invalid character and reduce the size of the number.
1533 MESSAGE Number too small and illegal character for attribute ! (SDERR 1533)
CAUSE The value for the indicated attribute is too small to be represented in the system and contains an invalid character.
ACTION Remove the invalid character and increase the size of the number.
1534 MESSAGE Invalid alias specified for attribute ! (SDERR 1534)
CAUSE An invalid alias value is specified for the indicated attribute.
ACTION Correct the value and reissue the command.
1535 MESSAGE Invalid boolean specified for attribute ! (SDERR 1535)
CAUSE An invalid boolean value is specified for the indicated attribute.
ACTION Correct the value (to TRUE or FALSE) and reissue the command.
1536 MESSAGE Invalid character string specified for attribute ! (SDERR 1536)
CAUSE An invalid character string value is specified for the indicated attribute.
ACTION Correct the value and reissue the command. Remember, quotes are required if the value wouldn't be accepted as a valid name.
1537 MESSAGE Invalid date specified for attribute ! (SDERR 1537)
CAUSE An invalid date value is specified for the indicated attribute.
ACTION Correct the value and reissue the command. Remember that all dates should be specified within quotes in the customized format of the Native Language Intrinsics.
1538 MESSAGE Invalid time specified for attribute ! (SDERR 1538)
CAUSE An invalid time value is specified for the indicated attribute.
A-179
ACTION Correct the value and reissue the command. Remember that all dates and time should be specified within quotes in the customized format of the Native Language Intrinsics.
1539 MESSAGE Invalid integer specified for attribute ! (SDERR 1539)
CAUSE An invalid integer value is specified for the indicated attribute.
ACTION Correct the value and reissue the command.
1540 MESSAGE Invalid floating point value for attribute ! (SDERR 1540)
CAUSE An invalid floating point value is specified for the indicated attribute.
ACTION Correct the value and reissue the command.
1541 MESSAGE Invalid value for attribute ! (SDERR 1541)
CAUSE An invalid value is specified for the indicated attribute.
ACTION Correct the value and reissue the command. Remember that valid values for
SENSITIVITY are PRIVATE, READ, and MODIFY.
1542 MESSAGE Text for ! must be specified within quotes (SDERR 1542)
CAUSE Text for the indicated variable attribute must be specified within quotes.
ACTION Add the quotes and reissue the command.
1543 MESSAGE Entity type ! does not exist (SDERR 1543)
CAUSE The indicated entity type specified as a part of the relationship type does not exist in the dictionary.
ACTION Create the entity type before proceeding or specify an entity type that does exist.
1544 MESSAGE Entity ! does not exist (SDERR 1544)
CAUSE The indicated entity specified as part of the relationship does not exist in the dictionary.
ACTION Create the entity before proceeding or specify an entity that does exist.
1545 MESSAGE EDIT-VALUE is not allowed for attributes of this type (SDWARN 1545)
CAUSE Attributes of type ALIAS and VARIABLE cannot have attribute edit-values.
ACTION No action is needed. The attribute is created/modified as if no EDIT-VALUE clause was specified.
1546 MESSAGE There is a problem with edit-value number ! (SDWARN 1546)
CAUSE The indicated edit value in the EDIT-VALUE clause has a problem.
ACTION Refer to the associated error to see what the problem with the value is. Then, either ignore the problem if it is merely a warning and is OK or correct it and reenter the command with the corrected value. Note that if the associated problem is merely a warning, the attribute will be created or modified while if the problem is an error, no action will be taken.
1547 MESSAGE There are too many edit-values specified for the attribute (SDERR 1547)
CAUSE With the padding of the edit-values to the length of the attribute, the number of editvalues specified overflowed the maximum allowance of 255 characters for the edit buffer.
A-180
ACTION The EDIT-VALUE list should be inspected and reduced to a number that can fit in the buffer and the attribute modified to supply the new edit list. Remember, each value is padded to the length of the attribute and there is a maximum buffer length of 255 characters.
1548 MESSAGE LENGTH required for types CHARACTER, FLOATING, and INTEGER
(SDERR 1548)
CAUSE An attribute of type CHARACTER, FLOATING, or INTEGER is being created, but no
LENGTH keyword is used. When creating a new attribute, the length of the attribute must be specified if there is a choice between two or more lengths for the attribute.
ACTION Reenter the same command but include a LENGTH keyword clause that specify a length for the attribute being created.
1549 MESSAGE Cannot specify variable attribute if have/establish common link (SDERR
1549)
CAUSE An entity or relationship is being created with a common link and a variable length attribute assigned a value.
ACTION Create the entity or relationship with the common link and do not assign any value to the variable length attribute. Create the entity or relationship as a local entity or relationship without a common link. Or create the entity or relationship with the common link and then modify the common occurrence linked to add the variable length attribute text.
CAUSE An entity or relationship is being modified with a common link existing or being added and a variable length attribute assigned a value.
ACTION Modify the entity or relationship to add the common link and then modify the common entity or relationship to change the variable length attribute or modify the local entity or relationship to remove the common link (or not establish it) and assign the variable length text to the local occurrence.
Display/Report Messages (1600-1699)
1600 MESSAGE No SECURE capability. Cannot qualify other SCOPE-OWNERs (SDWARN
1600)
CAUSE The current open scope does not have SECURE capability. Accordingly, it can only retrieve the name of the object's owner scope if the current scope is the owner
(otherwise, the owner name is blank). Because of this, if the qualifying SCOPE-
OWNER qualifies retrieval to the current scope, everything will be fine. If the qualification contains anything else, the match against a blank name will fail and so the objects are NOT retrieved.
ACTION If the SCOPE-OWNER clause qualifies to the current scope, no action is needed. Also, if the SCOPE-OWNER contains selection criteria and if the current scope matches the criteria and it is OK that the list of objects retrieved will be limited to the ones owned by the current scope, no action is needed. However, if it is NOT OK to limit to the objects owned by the current scope, either switch to a scope that does have SECURE capability or don't use the SCOPE-OWNER field to qualify the owner in the current scope.
1601 MESSAGE Attribute list is incomplete for entity type ! (SDERR 1601)
A-181
CAUSE The attribute list being retrieved for the indicated entity type is not complete.
ACTION Correct the associated error and reissue the command.
1602 MESSAGE Lock failed so partial results may be returned (SDWARN 1602)
CAUSE The dictionary lock failed. Accordingly, the list of items retrieved may not include all items in the dictionary at the current time.
ACTION No action is required. The system returns results but there is no guarantee that they are complete. The DA should be notified of the problem. Internal Error.
1603 MESSAGE Unlock failed so must terminate to prevent system hang (SDERR 1603)
CAUSE The unlock failed. Accordingly, the system is terminated to exit the dictionary to insure that this run does not hold a lock on the dictionary.
ACTION Contact the DA. Internal Error.
1604 MESSAGE Error encountered during a list retrieval (SDERR 1604)
CAUSE An error was encountered during a list retrieval.
ACTION Refer to the associated error and correct the problem found.
1605 MESSAGE Error while switching to or from the report domain (SDERR 1605)
CAUSE An error was encountered while switching to or from the domain holding all of the
SDMAIN stored reports.
ACTION Contact the DA. Internal Error.
1606 MESSAGE NAME-ONLY used instead of ALL (SDWARN 1606)
CAUSE The NAME-ONLY keyword is used and the ALL keyword ignored.
ACTION No action is needed. The next time the command is issued, specify only one information granularity option.
1607 MESSAGE NAME-ONLY used instead of LIST (SDWARN 1607)
CAUSE The NAME-ONLY keyword is used and the LIST keyword ignored.
ACTION No action is needed. The next time the command is issued, specify only one information granularity option.
1608 MESSAGE LIST used instead of ALL (SDWARN 1608)
CAUSE The LIST keyword is used and the ALL keyword ignored.
ACTION No action is needed. The next time the command is issued, specify only one information granularity option.
1609 MESSAGE ! is not allowed as a LIST parameter for RELATIONSHIPS (SDWARN 1609)
CAUSE The indicated LIST option is not allowed as a LIST parameter when reporting on relationships.
ACTION No action is needed as the option is ignored. Remove the indicated option from the
LIST options.
1610 MESSAGE ATTRIBUTES entry overrides specific parameters (SDWARN 1610)
CAUSE The ATTRIBUTES option for the LIST keyword overrides any specific attributes listed.
A-182
ACTION No action is needed. The next time the command is issued, if all the attributes are desired, omit specific attributes from the LIST list.
1611 MESSAGE Cannot qualify a variable attribute (SDERR 1611)
CAUSE Cannot qualify a variable length attribute.
ACTION Remove the variable length attribute qualifier from the ATTRIBUTE-LIST clause.
1612 MESSAGE Attribute ! not related to the entity (SDERR 1612)
CAUSE The indicated attribute is not related to the entity.
ACTION Remove the unrelated attribute or change the mistyped attribute to the correct attribute.
1613 MESSAGE Attribute ! not related to the relationship (SDERR 1613)
CAUSE The indicated attribute is not related to the relationship.
ACTION Remove the unrelated attribute or change the mistyped attribute to the correct attribute.
1614 MESSAGE Invalid operation on a boolean for attribute ! (SDERR 1614)
CAUSE The operation specified for the indicated Boolean attribute is invalid. Boolean attribute can only be qualified using relational operators = and <>.
ACTION Change the type of comparison to one including only = and/or <>.
1615 MESSAGE Duplicate Item List entry ! (SDWARN 1615)
CAUSE The indicated list option is listed twice in the LIST keyword clause.
ACTION No action is needed as the duplicate is ignored.
1616 MESSAGE Duplicate Attribute List entry ! (SDERR 1616)
CAUSE The indicated attribute is listed twice in the ATTRIBUTE-LIST keyword clause.
ACTION Remove the duplicate attribute (or combine the two into one) and reissue the command.
1617 MESSAGE Must own Domain to report on scopes having access (SDWARN 1617)
CAUSE The current scope must be the owner of the domain to allow retrieval of scope information.
ACTION Open the dictionary with the owner scope as the open scope.
1618 MESSAGE Must own Entity to report on scopes having access (SDWARN 1618)
CAUSE The current open scope must be the owner of the entity to allow retrieval of scope information.
ACTION Open the dictionary with the owner scope as the open scope.
1619 MESSAGE Must own Relationship to report on scopes having access (SDWARN 1619)
CAUSE The current open scope must be the owner of the relationship to allow retrieval of scope information.
ACTION Open the dictionary with the owner scope as the open scope.
1620 MESSAGE Domain deleted or changed during processing (SDWARN 1620)
A-183
CAUSE The domain being processed has been deleted or changed since the start of the operation.
ACTION Do nothing if this is not a problem. If a problem, open the dictionary in EXCLUSIVE-
UPDATE mode and repeat the command.
1621 MESSAGE Entity deleted or changed during processing (SDWARN 1621)
CAUSE The entity being processed has been deleted or changed since the start of the operation.
ACTION Do nothing if this is not a problem. If a problem, open the dictionary in EXCLUSIVE-
UPDATE mode and repeat the command.
1622 MESSAGE Relationship deleted or changed during processing (SDWARN 1622)
CAUSE The relationship being processed has been deleted or changed since the start of the operation.
ACTION Do nothing if this is not a problem. If a problem, open the dictionary in EXCLUSIVE-
UPDATE mode and repeat the command.
1623 MESSAGE Too many entities in ! for the relationship-type (SDERR 1623)
CAUSE The number of entities specified as composing the relationship is greater than the number of entity types making up the relationship type.
ACTION Reduce the number of entities to no more than the number of entity types in the relationship type.
1624 MESSAGE List entry ! is not allowed for compiled dictionaries (SDWARN 1624)
CAUSE The list entry specified is not allowed for compiled dictionaries. That functionality is not available there.
ACTION No action is needed. The option will be ignored. This information is not implemented in compiled dictionaries so you must move to a master dictionary to retrieve this information.
Start/Save Messages (1700-1724)
1700 MESSAGE START command has been cancelled (SDWARN 1700)
CAUSE The START/SAVE pair is cancelled so you are returned to the normal command processing mode.
ACTION No action is needed.
1701 MESSAGE Create capability is required to SAVE a report (SDERR 1701)
CAUSE The current open scope does not have CREATE capability (scope right) and so cannot
SAVE a report. Accordingly, you are not allowed to initiate a START/SAVE pair.
ACTION Switch to a scope having create capability.
1702 MESSAGE A ! command has already been defined (SDERR 1702)
CAUSE Only one of the indicated command (CONFIGURE, FORMAT, or REPORT) can be issued in each stored report.
ACTION No action is needed. The first instance of the command is stored with the report.
A-184
1703 MESSAGE Cannot specify ! after a REPORT command (SDERR 1703)
CAUSE The specified command (CONFIGURE or FORMAT) cannot be issued after the
REPORT command has been issued for a stored report.
ACTION Cancel the current report (using [[Control]] Y) if interactive. Then START the report again issuing the indicated command before the REPORT command. Or, SAVE the current report and then use the EDIT REPORT command to insert the indicated command into the report.
1704 MESSAGE A START command is already active (SDERR 1704)
CAUSE A START/SAVE pair is already active so another cannot be initiated.
ACTION Complete the current START/SAVE pair and then another START can be issued.
Remember, [[Control]] Y can be used to cancel the current START/SAVE pair.
1705 MESSAGE No START command has been issued (SDERR 1705)
CAUSE A SAVE cannot be issued here because no START has been issued to initiate the storage of commands.
ACTION Issue a START command and enter the command to be stored. Then, the SAVE command will be accepted.
1706 MESSAGE No REPORT command so START is active. <Control-Y> to stop. (SDERR 1706)
CAUSE A REPORT command is required within a START/SAVE pair. As one has not been issued, the START remains active so one can be entered.
ACTION Enter a REPORT command and then issue the SAVE. Or, use the [[Control]] Y (if interactive) to cancel the START.
1707 MESSAGE No REPORT command was specified. START is cancelled (SDERR 1707)
CAUSE A REPORT command is required within a START/SAVE pair. As input is NOT interactive, the START is cancelled so further processing can take place.
ACTION Update the command file to include a REPORT within the START/SAVE.
1708 MESSAGE Cannot create REPORT so START is active. <Control-Y> to stop (SDERR
1708)
CAUSE The indicated report cannot be created. Accordingly, the START remains active so the problem with the report can be corrected without losing the commands to be saved.
ACTION Refer to the associated error and correct the problem indicated. Then, issue the SAVE command. Or, issue a [[Control]] Y (if interactive) to cancel the START.
1709 MESSAGE Cannot create REPORT. START is cancelled (SDERR 1709)
CAUSE The indicated report cannot be created. As input is NOT interactive, the START is cancelled so further processing can take place.
ACTION Refer to the associated error and correct the problem indicated.
1710 MESSAGE Definition too long so REPORT not stored and START cancelled (SDERR
1710)
CAUSE The commands to be stored are too long to store in the dictionary. Because there is no way to shrink the commands, the START is cancelled.
ACTION Reissue the START and enter the commands again. However, this time use simpler
A-185
commands with fewer lines or simply put more data on each line so there are less lines to the command.
1711 MESSAGE Definition SAVE failed so REPORT not stored and START cancelled (SDERR
1711)
CAUSE The report cannot be stored. Because the data could not be placed in the dictionary, the
START is cancelled.
ACTION Refer to the associated error and correct the problem indicated. The problem is probably a database capacity error.
1712 MESSAGE Description was too long. It was truncated and stored (SDWARN 1712)
CAUSE The description supplied with the report is too long so it is truncated.
ACTION No action is needed. As much of the description as can be handled is stored and the remainder discarded.
1713 MESSAGE Description SAVE failed. Report saved without Description (SDERR 1713)
CAUSE The report's description cannot be saved. Because it cannot be placed in the dictionary, it is discarded and the report saved without a description.
ACTION Refer to the associated error and correct the indicated problem. The problem is probably a database capacity error. The description can be added later, if desired, using the MODIFY REPORT command.
Stored Report Messages (1725-1749)
1725 MESSAGE Report does not exist (SDERR 1725)
CAUSE The report specified by the user does not exist in the dictionary.
ACTION Work with a report that exists or create this report before operating on it.
1726 MESSAGE Report already exists (SDERR 1726)
CAUSE The report specified by the user already exists in the dictionary.
ACTION Either no action is needed as the report already exists or a modify operation on the report should be used.
1727 MESSAGE Internal report name exists (SDERR 1727)
CAUSE The internal name specified for the report already exists in the dictionary.
ACTION Specify a unique internal name for the report.
1728 MESSAGE External report name exists (SDERR 1728)
CAUSE The external name specified for the report already exists in the dictionary.
ACTION Specify a unique external name for the report.
1729 MESSAGE Current scope is not the report owner (SDERR 1729)
CAUSE The current scope is not the owner of the specified report and ownership is required for the desired operation.
ACTION Open the dictionary with the owner scope to perform the operation.
A-186
1730 MESSAGE Scope lacks sufficient access to the report (SDERR 1730)
CAUSE The current scope does not have modify access to the specified report.
ACTION Only the owner can modify a report so open the dictionary as the owner to modify.
Execute Messages (1750-1799)
1750 MESSAGE Both ENTITY and RELATIONSHIP keywords cannot be specified (SDERR
1750)
CAUSE As the underlying report is either a REPORT ENTITY or a REPORT RELATIONSHIP, only one of the ENTITY/RELATIONSHIP keywords can be specified.
ACTION Reissue the command deleting the unneeded keyword clause.
1751 MESSAGE Could NOT retrieve the report named ! (SDERR 1751)
CAUSE Cannot retrieve the specified report.
ACTION Refer to the associated error and correct the indicated problem.
1752 MESSAGE A ! command cannot be issued after a REPORT command (SDERR 1752)
CAUSE The specified command (CONFIGURE or FORMAT) cannot be placed after the
REPORT command in a stored report.
ACTION Use the EDIT REPORT command to move the indicated command to before the
REPORT command (or to delete it completely if there is already one before the
REPORT command).
1753 MESSAGE Cannot issue two ! commands (SDERR 1753)
CAUSE Two of the specified commands (CONFIGURE, FORMAT, or REPORT) are not allowed in the same stored report.
ACTION Use the EDIT REPORT command to delete one of the indicated commands.
1754 MESSAGE ! is an invalid command in a stored report (SDERR 1754)
CAUSE The specified command is invalid in a stored report.
ACTION Use the EDIT REPORT command to remove the invalid command.
1755 MESSAGE The keyword is incompatible with the report type (SDERR 1755)
CAUSE Either the ENTITY keyword is specified and the stored command is a REPORT
RELATIONSHIP or the RELATIONSHIP keyword is specified and the stored command is a REPORT ENTITY.
ACTION Reissue the command with the keyword corresponding to the stored command.
1756 MESSAGE Source and indicated entity-types do not match for report ! (SDERR 1756)
CAUSE The entity type of the REPORT command and the entity type specified by the
SOURCE-POSITION keyword are not the same.
ACTION Revise the REPORT command so that the specified source entity type matches the entity type of the REPORT command.
1757 MESSAGE SOURCE-POSITION required as is > 1 match for report ! (SDERR 1757)
A-187
CAUSE There are two or more possible position matches for the source entity so the SOURCE-
POSITION keyword must be specified.
ACTION Reissue the command with the SOURCE-POSITION keyword specified.
1758 MESSAGE Source entity-type is NOT in the relationship-type for report ! (SDERR 1758)
CAUSE The RELATIONSHIP-TYPE to be followed does not involve the source ENTITY-TYPE.
ACTION Revise the relationship type to be followed so that it involves the source entity type.
1759 MESSAGE REPORT-POSITION required as > 2 entity-types for report ! (SDERR 1759)
CAUSE A 3-way (or more) relationship is being followed to the nested report. Accordingly, the
REPORT-POSITION keyword is required.
ACTION Reissue the command with the REPORT-POSITION keyword added.
1760 MESSAGE Error while retrieving entities for report ! (SDERR 1760)
CAUSE Encountered an error while retrieving the entities to be used for the nested report.
ACTION Refer to the associated error and correct the problem indicated.
1761 MESSAGE Illegal REPORT-POSITION value given for report ! (SDERR 1761)
CAUSE The REPORT-POSITION specified in the indicated report is not legal (there is no such position in the relationship type to follow).
ACTION Change the REPORT-POSITION to a value that is present in the relationship to be followed.
1762 MESSAGE Stored and indicated entity-types don't match for report ! (SDERR 1762)
CAUSE The entity types in the REPORT command and the stored report do not match.
ACTION Revise the REPORT command so the entity types match or specify a different stored report with the correct entity type (create one if needed).
1763 MESSAGE Error found in stored report ! (SDERR 1763)
CAUSE An error was encountered while processing the indicated report.
ACTION Refer to the associated error and correct the indicated problem.
1764 MESSAGE Report and Source position cannot be the same for report ! (SDERR 1764)
CAUSE The same position was specified for both SOURCE-POSITION and REPORT-
POSITION.
ACTION Reissue the report with the position values updated so they are not both the same.
1765 MESSAGE The stored report must be a REPORT ENTITY (SDERR 1765)
CAUSE For nested EXECUTEs, the stored report must be a REPORT ENTITY while in this case it is a REPORT RELATIONSHIP.
ACTION Change the report chained to so that the chained report is a REPORT ENTITY.
Miscellaneous Messages (1800-1899)
1800 MESSAGE Catalog error ! encountered during catalog read (SDERR 1800)
A-188
CAUSE An error was encountered while retrieving information from the message catalog.
ACTION Contact the DA.
1801 MESSAGE Could not find message set ! in the catalog (SDERR 1801)
CAUSE The indicated message set could not be found in the catalog.
ACTION Contact the DA to get a new catalog with the indicated set present.
1802 MESSAGE Could not find message (set:number) ! in the catalog (SDERR 1802)
CAUSE Cannot find the desired message in the specified set in the catalog.
ACTION Contact the DA to get a new catalog with the indicated message present.
1810 MESSAGE Bad error message from FErrMsg Intrinsic (SDERR 1810)
CAUSE A file system error occurred, but the associated message cannot be retrieved from the
FErrMsg intrinsic.
ACTION Contact the DA.
1811 MESSAGE Error message ! not found in the catalog. Catalog error ! (SDERR 1811)
CAUSE The indicated error message cannot be found in the message catalog.
ACTION Contact the DA to get a new catalog with the indicated error message present.
1812 MESSAGE Native language error (SDERR 1812)
CAUSE An error was detected during a call to the Native Language Intrinsics.
ACTION Contact the DA. Internal Error.
1813 MESSAGE Date returned from the dictionary was invalid (SDERR 1813)
CAUSE The data for the DATE-CREATED or DATE-CHANGED attribute field is not in the valid format for a System Dictionary date field.
ACTION Contact the DA. Internal error.
1814 MESSAGE Sort Intrinsic error number ! (SDWARN 1814)
CAUSE An error was detected during a call to the Sort intrinsics.
ACTION Use the NOSORT option in all cases so the error is avoided. In addition, contact the
DA. Internal Error.
1820 MESSAGE Heap overflow. Command is too complex (SDERR 1820)
CAUSE All of the available heap space in the system has been allocated. The command is too long and/or complex.
ACTION Simplify the command by breaking it into two or more pieces and reissue the pieces.
CAUSE All of the available heap space in the system has been allocated. There are too many nested levels in the REPORT command.
ACTION Limit the number of nested levels in the report and/or limit the amount of information and qualification at each level of the report.
1821 MESSAGE Library error ! encountered. Terminate program (SDERR 1821)
CAUSE A Pascal error was encountered.
A-189
ACTION Contact the DA (remember to supply the library error number). Internal Error.
1830 MESSAGE MPE command is too long (SDERR 1830)
CAUSE The entered MPE command is too long.
ACTION Limit the MPE command to 256 characters and reenter it.
1831 MESSAGE Invalid MPE command (SDERR 1831)
CAUSE The specified MPE command is not a legal MPE command.
ACTION Enter a legal MPE command.
CAUSE The specified MPE command is not allowed to be issued from within SDMAIN.
ACTION Enter an MPE command that can be issued through the command intrinsic.
1832 MESSAGE MPE Executor error number ! (SDERR 1832)
CAUSE An error was encountered while executing the MPE command.
ACTION Use the error number to look up the error for the specified command in the MPE
Intrinsics Manual.
1840 MESSAGE Intrinsic logging is already ! (SDWARN 1840)
CAUSE Intrinsic logging is already set in the indicated position.
ACTION None is needed as logging is already set as desired.
1841 MESSAGE Version is already set to ! status (SDWARN 1841)
CAUSE The status of the version is already set to the status specified.
ACTION None is needed as the status of the version is already what is desired. However, a check should be made to make sure that the version name is correct and you are not trying to set the status of a different version than expected.
A-190
Изтегляне
Публичната връзка е актуализирана
Публичната връзка към вашия чат е актуализирана. You may view and manage your chat links after registration here.
Публична връзка към документа
Реклама
