| 0025-001 | A read only SDR session has been obtained. Operations that create or change data are not allowed. |
Explanation: You tried to change or create an SDR object with a read lock.
User Response: Refer to the appendix on the System Data Repository in PSSP: Administration Guide for information on setting authorizations.
| 0025-002 | Lock could not be obtained. Another process has the class locked. |
Explanation: User tried to update a locked class.
User Response: Try again or issue SDRWhoHasLock class to find the process that has the lock. The lock can be cleared with SDRClearLock class if the process that owns the lock is gone.
| 0025-003 | Requestor already has lock on this class. |
Explanation: A lock was requested but you already have a lock on the class.
User Response: None.
| 0025-004 | Item specified for query, insertion or deletion was not found. |
Explanation: A class, attribute name, or attribute value specified in the command was not found.
User Response: Specify a valid class, attribute name, or attribute value.
| 0025-005 | Requested operation requires write authority. |
Explanation: The user must have write access to the SDR to do the requested operation.
User Response: On a DCE system, make sure that your principal is a member of the appropriate SDR write access group as defined in the spsec_defaults or spsec_overrides files. On a non-DCE system, make sure that you are running as root on the control workstation or an SP node.
| 0025-006 | Requested operation requires admin authority. |
Explanation: The user must have admin access to the SDR to do the requested operation.
User Response: On a DCE system, make sure that your principal is a member of the appropriate SDR admin access group as defined in the spsec_defaults or spsec_overrides files. On a non-DCE system, make sure that you are running as root on the control workstation or an SP node.
| 0025-007 | A write session has been obtained. SDR admin operations will not be allowed. |
Explanation: The user is authorized to do read and write operations.
User Response: If administrative operations are desired, the user's principal must be in the appropriate SDR admin access group as defined in the spsec_defaults or spsec_overrides file on a DCE system.
| 0025-008 | Incorrect parameter was passed. |
Explanation: The wrong number of parameters was passed or a parameter was unrecognized.
User Response: Examine the command as issued and correct the problem.
| 0025-009 | Mutual authentication with the SDR server did not succeed. |
Explanation: The SDR server (sdrd) could not be authenticated by DCE. There may be a program posing as the sdrd.
User Response: Check other messages returned to see if they offer a reason why mutual authentication with the SDR server was unsuccessful. The client may not have valid credentials. If that is the case, the client should issue a dce_login to obtain credentials. Otherwise, check the /etc/SDR_dest_info file on the client's machine to be sure that the client is trying to connect to the correct sdrd. If that is correct, make sure the sdrd daemons on the control workstation are running. There should be one daemon for each system partition.
| 0025-010 | An uninitialized object list was passed. |
Explanation: This should only be issued from the library routines -- a routine was passed an uninitialized object list.
User Response: Initialize the object list using the SDRInitObjList command.
| 0025-011 | Client does not have appropriate authority to change the SP_Restricted class. |
Explanation: The user must have appropriate access to the SP_Restricted class to make any change.
User Response: On a DCE system, make sure that your principal is a member of both the appropriate SDR access group and SDR-restricted group as defined in the spsec_defaults or spsec_overrides file. On a non-DCE system, make sure that you are running as root on the control workstation.
| 0025-012 | The contents of the object list passed were not appropriate for the command. |
Explanation: This is a library-only error. An object list did not contain the expected values.
User Response: Examine the contents of the list and the requirements.
| 0025-014 | Cursor is already past the end of the list. |
Explanation: The object cursor was advanced past the end of the object list.
User Response: Examine looping construct so this does not happen again.
| 0025-016 | Cursor is not in a valid position. |
Explanation: User tried to advance the cursor before it was initialized.
User Response: Use SDRInitLoop to initialize the cursor.
| 0025-020 | Class specified for creation already exists. |
Explanation: You tried to use SDRCreateClass to create a new class that already exists.
User Response: None.
| 0025-022 | The object specified for creation already exists. |
Explanation: You tried to create a new object that already exists for the class.
User Response: None.
| 0025-024 | The attribute specified for creation already exists. |
Explanation: User tried to create a new attribute that already exists for the class.
User Response: None
| 0025-026 | The class specified does not exist. |
Explanation: You attempted an action on a class that does not exist.
User Response: Perform the action on an existing class or create a new class.
| 0025-028 | The object specified does not exist. |
Explanation: You attempted an action on an object that does not exist in the specified class.
User Response: Change the values that describe the object so that they match an existing object.
| 0025-030 | An attribute specified does not exist. |
Explanation: You attempted an action on an attribute that does not exist for the specified class.
User Response: Change the attribute to one that does exist for the class.
| 0025-032 | Class is not locked by any process. |
Explanation: You attempted to unlock a class that was not locked, or issued SDRWhoHasLock on a class that was not locked.
User Response: None.
| 0025-034 | Cannot find or convert active system partition name. Possible error in SP_NAME |
Explanation: The system partition name cannot be found or cannot be resolved to the requested format.
User Response: Check the SP_NAME environment variable, the /etc/SDR_dest_info file, and name resolution.
| 0025-035 | Cannot convert system partition name to desired format. Possible error in SP_NAME. |
Explanation: The system partition name cannot be resolved to the requested format.
User Response: Check the SP_NAME environment variable, the /etc/SDR_dest_info file, and name resolution.
| 0025-036 | Source syspar and target syspar must not be the same. |
Explanation: User attempted to move objects in the same system partition.
User Response: Specify a target system partition that is different from the source.
| 0025-037 | The subsystem already exists. |
Explanation: An SDR subsystem that already exists was specified for creation.
User Response: Specify a subsystem name that does not already exist.
| 0025-038 | The subsystem did not start. |
Explanation: The SDR subsystem specified did not respond within the timeout period.
User Response: Perform problem determination procedures.
| 0025-045 | The string contains non-ASCII character data that cannot be written to the SDR. |
Explanation: The input character string is not valid for input according to the rules established for writing data to the SDR.
User Response: First, check the SP SDR_ASCII_ONLY attribute value. This value should be "false" in order to input non-ASCII data. Second, check the SP admin_locale attribute value. The client locale should be the same as this locale value.
| 0025-060 | AIX file name could not be read. |
Explanation: A specified file could not be found or could not be opened.
User Response: Check the existence of the file and the permissions.
| 0025-061 | SDR file already exists. |
Explanation: You specified that a file should be saved in SDR but gave the name of an existing SDR file.
User Response: Issue SDRReplaceFile or use a unique file name.
| 0025-062 | SDR file name not found. |
Explanation: You asked to retrieve an SDR that was not found.
User Response: Specify an existing file.
| 0025-064 | Cannot write or create AIX file name specified. |
Explanation: You specified an AIX file name that cannot be written or created.
User Response: Check the permissions on the AIX file and directory.
| 0025-066 | The /spdata filesystem on the control workstation is full. Make more space and process shadow files. |
Explanation: The file system that contains the SDR data on the control workstation is full. The changes made by this process are lost.
User Response: Free space in spdata on the control workstation and refer to information on processing shadow files in PSSP: Administration Guide.
| 0025-080 | The SDR routine could not connect to server. |
Explanation: Could not connect to SDR server.
User Response: Check the SDR_dest_info file. Refer to the appendix on the System Data Repository in PSSP: Administration Guide.
Check the server on the control workstation to ensure it is running and follow the procedure in the chapter on diagnosing SDR problems in PSSP: Diagnosis Guide that outlines what to do when an SDR command fails to connect to the server.
| 0025-082 | Authentication was denied. |
Explanation: You are not authenticated to the SDR server.
User Response: Check elements of authentication in the admin guide. Refer to information on configuring the user home environment in the chapter on the system monitor in PSSP: Administration Guide.
| 0025-083 | Could not open authentication file. |
Explanation: The file /etc/SDR_dest_info could not be opened.
User Response: Check file existence and user permissions.
| 0025-084 | There is no open SDR session. |
Explanation: User attempted a server operation but no session could be opened.
User Response: Open a session and check the return code from that call before issuing server requests.
| 0025-085 | Format error in SDR_dest_info file. |
Explanation: The file /etc/SDR_dest_info contained a format error.
User Response: Refer to the appendix on the System Data Repository in PSSP: Administration Guide for the correct file format.
| 0025-086 | Session has already been opened. |
Explanation: An SDROpenSession call was made but a session was already in progress.
User Response: If you wish, remove the redundant call.
| 0025-087 | Session open did not succeed - Cert Length from server was not valid. |
Explanation: An SDROpenSession call was made, but the returned Cert Length field could not be parsed properly. The session was not opened.
User Response: Record the above information and contact the IBM Support Center.
| 0025-088 | Session open failed - Locale Length from server was not valid. |
Explanation: An SDROpenSession call was made, but the returned Locale Length field could not be parsed properly. The session was not opened.
User Response: Record the above information and contact the IBM Support Center.
| 0025-100 | The system malloc routine did not succeed. |
Explanation: A call to allocate storage failed.
User Response: Record the above information and contact the IBM Support Center.
| 0025-102 | An internal data format inconsistency was detected. |
Explanation: Internal SDR checking revealed a corrupted class or other corrupted data.
User Response: Record the above information and contact the IBM Support Center.
| 0025-104 | A system routine returned an unsuccessful return code. |
Explanation: A system call unexpectedly failed.
User Response: Record the above information and contact the IBM Support Center.
| 0025-108 | Could not obtain local hostname. |
Explanation: The gethostname() routine failed.
User Response: Record the above information and contact the IBM Support Center.
| 0025-110 | Read or write operation on socket did not succeed. |
Explanation: Reading or writing the client or server tcp socket failed. The SDR server or client may have terminated unexpectedly.
User Response: Record the above information and contact the IBM Support Center.
| 0025-112 | Client attempted to move objects with class cached. |
Explanation: This is a programming error in the program that uses the SDR client library.
User Response: Record the above information and contact the IBM Support Center.
| 0025-113 | SDR command timed out. |
Explanation: While waiting for a response from sdrd (the SDR daemon), the command exceeded the 10 minute timeout limit.
User Response: Check the status of sdrd. Check network adapters for errors.
| 0025-301 | The sdr.syspar subsystem must be stopped before removing it. |
Explanation: The sdr command was issued to remove an sdrd SRC definition from the system. The SDR subsystem must be stopped before it can be removed.
User Response: Issue sdrd -spname syspar stop.
| 0025-303 | sdrd is not executable; SRC object sdr.syspar not made. |
Explanation: The sdrd binary in /usr/lpp/ssp/bin is not executable.
User Response: Use the chmod command to make the sdrd binary in /usr/lpp/ssp/bin executable.
| 0025-306 | Incorrect sdr parameter parameter. |
Explanation: An unrecognized parameter was passed to the sdr command.
User Response: Check the parameters and issue the command again.
| 0025-307 | sdr usage: sdr [ -spname syspar ] start | stop | reset | query | qall | mksrc | qsrc | rmsrc |
Explanation: An unrecognized parameter or no parameter was passed to the sdr command.
User Response: Check the parameters and issue the command again.
| 0025-308 | The code reached a path that was unexpected. |
Explanation: The sdr command reached a code path that is in error.
User Response: Record the above information and contact the IBM Support Center.
| 0025-309 | System partition name is missing. sdr usage: [-spname <syspar>] start | stop | reset | query | qall | mksrc | qsrc | rmsrc |
Explanation: The system partition name is required when issuing the command sdr -spname.
User Response: Reissue the command with the correct syntax.
| 0025-310 | Incorrect or missing IP address. |
Explanation: The input IP address is missing or the format is not valid.
User Response: Correct the IP address.
| 0025-311 | IP address IP address is not resolvable. |
Explanation: The input IP address cannot be resolved into a hostname.
User Response: Correct the IP address.
| 0025-312 | An error occured while creating the SDR IP address subsystem. |
Explanation: An error occurred while issuing the sdr mksrc command.
User Response: Follow local problem reporting procedures.
| 0025-313 | An error occured while starting the IP address subsystem. |
Explanation: An error occurred while issuing the sdr start command.
User Response: Follow local problem reporting procedures.
| 0025-320 | Usage: SDRArchive <file suffix>. |
Explanation: Syntax error with the wrong number of arguments.
User Response: Correct the syntax.
| 0025-321 | SDRArchive: tar command did not succeed, rc=return code. |
Explanation: An error occurred while issuing the tar command.
User Response: Follow local problem reporting procedures.
| 0025-322 | SDRArchive: SDR archive file name is /spdata/sys1/sdr/archives/filename. |
Explanation: The SDR has been archived in the specified file.
User Response: None.
| 0025-323 | The SDRArchive command can only be run on the control workstation. |
Explanation: The user tried to run the SDRArchive command on a node. This command can only be run on the control workstation.
User Response: Run the SDRArchive command on the control workstation.
| 0025-324 | The SDRRestore command can only be run on the control workstation. |
Explanation: The user tried to run the SDRRestore command on a node. This command can only be run on the control workstation.
User Response: Run the SDRRestore command on the control workstation.
| 0025-330 | SDRRemoveSyspar: Incorrect or missing IP address. |
Explanation: The input IP address is missing or the format is not valid.
User Response: Correct the IP address.
| 0025-331 | SDRRemoveSyspar: IP address IP address is not resolvable. |
Explanation: The input IP address cannot be resolved into a hostname.
User Response: Correct the IP address.
| 0025-332 | SDRRemoveSyspar: An error occured while stopping the SDR. IP address subsystem. |
Explanation: An error occurred while issuing the sdr stop command.
User Response: Follow local problem reporting procedures.
| 0025-333 | SDRRemoveSyspar: An error occured while removing the sdr. IP address subsystem. |
Explanation: An error occurred while issuing the sdr rmsrc command.
User Response: Follow local problem reporting procedures.
| 0025-340 | SDRRestore: Missing archive filename. Usage: SDRRestore archive_file. |
Explanation: Syntax error. The input filename is missing.
User Response: Correct the syntax.
| 0025-341 | SDRRestore: The file filepath/filenamedoes not exist or is empty. |
Explanation: The input file does not exist or is empty.
User Response: Check that the file exists and that it is not empty.
| 0025-342 | SDRRestore: The file filepath/filename is damaged or not in tar format. |
Explanation: The input file is not a valid tar file.
User Response: Check the file format.
| 0025-343 | SDRRestore: IP address IP address of SDR partitions is not resolvable. |
Explanation: The IP address cannot be resolved into a hostname.
User Response: Correct the IP address.
| 0025-344 | SDRRestore: removing /spdata/sys1/sdr/defs/* did not succeed, rc=return code. |
Explanation: An error occurred while removing SDR data files.
User Response: Follow local problem reporting procedures.
| 0025-345 | SDRRestore: removing /spdata/sys1/sdr/system/* did not succeed, rc=return code. |
Explanation: An error occurred while removing SDR data files.
User Response: Follow local problem reporting procedures.
| 0025-346 | SDRRestore: removing /spdata/sys1/sdr/partitions/* did not succeed, rc= return code. |
Explanation: An error occurred while removing SDR data files.
User Response: Follow local problem reporting procedures.
| 0025-347 | SDRRestore: the tar command did not succeed, rc=return code. |
Explanation: An error occurred while restoring SDR data from an archive file.
User Response: Follow local problem reporting procedures.
| 0025-350 | splst_syspars: SDR query did not succeed, rc=return code. |
Explanation: An error occurred while issuing SDRGetObjects command for an SDR query.
User Response: Follow local problem reporting procedures.
| 0025-360 | spchk_syspars: the SDR is not available. |
Explanation: An error occurred while issuing SDRGetObjects command to check if SDR is available.
User Response: Issue lssrc --g sdr to see which partitions sdrd is not available.
| 0025-361 | spchk_syspars: Partition address partition address is not resolvable. |
Explanation: An error occurred while checking address resolution of partition's ip_address found in the SDR Syspar class.
User Response: Correct name resolution.
| 0025-362 | spchk_syspars: Partition address partition address resolves to resolved partition address, which does not match the partition name partition name. |
Explanation: The syspar_name in the Syspar class of the SDR is not consistent with the hostname resolved from the ip_address in the Syspar class.
User Response: Correct hostname resolution, restore the archived SDR data, or contact the IBM Support Center.
| 0025-363 | spchk_syspars: Partition directory partition directory/partition address does not exist. |
Explanation: The partition directory for a partition defined in the SDR Syspar class does not exist.
User Response: Restore archived SDR data or contact the IBM Support Center.
| 0025-364 | spchk_syspars: Subsystem sdr.partition address is not active. |
Explanation: There is no active sdrd for this partition.
User Response: Issue startscr --s sdr.partition and lssrc --s sdr.partition to make sure that the SDR is up and running.
| 0025-365 | spchk_syspars: The following extraneous partition directory entries exist: |
Explanation: There are one or more partition subdirectories in the SDR database for which there is no Syspar object.
User Response: Restore the archived SDR data or contact the IBM Support Center.
| 0025-366 | spchk_syspars: The following incorrect partition names exist in Syspar_map: |
Explanation: One or more partitions defined in the Syspar_map class is not defined in the Syspar class.
User Response: Restore the archived SDR data or contact the IBM Support Center.
| 0025-367 | spchk_syspars: The following extraneous sdr subsystems exist: |
Explanation: There are src definitions for sdrd daemons for partitions that are not defined in the Syspar class of the SDR.
User Response: Contact the IBM Support Center.
| 0025-368 | spchk_syspars: Partition name partition name does not match partition address partition address in Syspar_map. |
Explanation: An error occurred while checking name and address consistency in Syspar_map.
User Response: Restore the archived SDR data or contact the IBM Support Center.
| 0025-500 | SDRWhoHasLock class_name |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-501 | SDRCreateClass class_name attr=datatype [attr=datatype...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-502 | SDRCreateObjects class_name attr=value [attr=value...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-503 | SDRCreateAttrs class_name attr=datatype [attr=datatype...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-504 | SDRChangeAttrValues class_name [attr==value... ]attr=value [attr=value...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-505 | SDRGetObjects [-q] [-G] [-x] [-d delimiter] class_name [attr==value...] [attr...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-506 | SDRDeleteObjects class_name [attr==value...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-507 | SDRClearLock class_name |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-508 | SDRCreateFile AIX_filename SDR_filename |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-509 | SDRRetrieveFile SDR_filename AIX_filename |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-510 | SDRReplaceFile AIX_filename SDR_filename |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-511 | SDRDeleteFile SDR_filename |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-512 | SDRArchive |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-513 | SDRRestore archive_file |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-514 | SDRListClasses |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-515 | SDRListFiles |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-516 | SDRCreateSystemClass class_name attr=datatype [attr=datatype...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-517 | SDRCreateSystemFile AIX_filename SDR_filename |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-518 | SDRMoveObjects source_syspar target_syspar class_name [attr==value...] |
Explanation: Syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-519 | spget_syspar [-n] [-d] |
Explanation: The n flag means to print the hostname (default is IP address).
The d flag means to print the address/hostname of the default system partition.
A syntax error causes the display of this usage message.
User Response: Correct the syntax and retry the command.
| 0025-520 | splst_syspars [-n] |
Explanation: A syntax error causes the display of this usage message.
User Response: Correct the syntax.
| 0025-521 | Usage: SDRValidateString [-q] string. |
Explanation: The syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-522 | Usage: SDRScan [-q] [-f] |
Explanation: The syntax error displays the usage message.
User Response: Correct the syntax.
| 0025-600 | Usage: splst_versions [-G] [-l] [-e] [-n node_num | -N node_group] [-t] [-h]. |
Explanation: A syntax error causes the display of this usage message.
User Response: Correct the syntax.
| 0025-601 | Flag flag_name not expected or used without required argument. |
Explanation: splst_versions detected either a flag it does not allow or a flag it allows that is missing a required argument.
User Response: Correct the syntax.
| 0025-602 | Node group specified nodegroup_name resolved to 0 nodes. |
Explanation: splst_versions was called with the -N flag to specify a nodegroup. The nodegroup specified has no nodes in it.
User Response: Specify a target that contains nodes.
| 0025-603 | An SDR routine internal to this program returned rc=return_code. |
Explanation: The splst_versions subroutine (not the command line) failed internally. The return code specified is an SDR return code.
User Response: Check the SDR return code to determine the cause of the problem.
| 0025-604 | The popen subroutine returned NULL trying to run the command command_name. |
Explanation: The splst_versions command tried to use popen to run the command to resolve a nodegroup. popen failed to run the command.
User Response: Try running the command from a shell command line.
| 0025-605 | A record returned from the command command_name was not a number. The record is record_name. |
Explanation: The splst_versions command used popen to run the command to resolve a nodegroup. A record returned was not a number, though a number was expected.
User Response: Try running the command from a shell command line.
| 0025-606 | The command command_name returned more nodes than the space allocated. The number allocated is max_number_nodes. |
Explanation: An internal buffer overflowed.
User Response: A programming change is required.
| 0025-607 | The command command_name ended abnormally from popen. The command_exit_status is the signal causing the abnormal end. |
Explanation: A command running with popen ended abnormally.
User Response: None.
| 0025-608 | The command command_name ended with rc=return_code. |
Explanation: A command running with popen ended with an error.
User Response: None.
| 0025-609 | The splst_version command could not complete because data was missing in the SDR. |
Explanation: The splst_version command expected certain data to be present, however that data was missing.
User Response: Check each node object's code_version attribute.
| 0025-610 | Information about a node(s) could not be found in the SDR. |
Explanation: The command expected certain data to be present, however that data was missing.
User Response: Check that the node exists in the node class of the SDR and that the code_version attribute is present.
| 0025-611 | Usage: splstnodes [-h] [-x] [-d delim] [--p str] [--s attr] [-G][-t standard | dependent] [-N nodegroup][attr==value...][attr] |
Explanation: The user either typed a flag or argument that was not valid or issued the --h flag.
User Response: Check the syntax of the command and enter it again.
| 0025-612 | Usage: splstadapters [-h] [-x] [-d delim] [--p str] [--s attr] [-G][-t standard | dependent] [attr==value...][attr] |
Explanation: The user either typed a flag or argument that was not valid or issued the --h flag.
User Response: Check the syntax of the command and enter it again.
| 0025-613 | An SDR routine internal to this program did not succeed. The message from that routine is: message. |
Explanation: The SDR is not configured yet or is not configured properly. The network or control workstation is not operating properly.
User Response: Find the source of the problem indicated by message.
| 0025-614 | An internal error prevented this command from completing. |
Explanation: An internal error was encountered. A more detailed message will follow this one, explaining the nature of the error.
User Response: Read the message that is output after this one for more detailed information about the problem.
| 0025-615 | Unable to resolve nodegroup <nodegroup_name>. |
Explanation: The program tried to resolve the nodegroup named above. A failure occurred.
User Response: Read the message that is output after this one for more detailed information about the problem.
| 0025-616 | The following attribute(s) were requested but do not exist: <comma-separated attr list>. |
Explanation: The user entered one or more arguments on the command line that the command found to be invalid as attribute names. It may be the case that the user used the wrong syntax- such as putting a "-" flag after a command argument.
User Response: Examine the list of attributes that were noted as being invalid and determine if the command was entered with the wrong syntax or if the attribute names are, in fact, invalid.
| 0025-617 | No objects were found with the attribute value(s) specified. |
Explanation: The user entered one or more arguments on the command line of the form <attr>==<value>. The command could not find any objects whose value of <attr> matched <value>.
User Response: No action necessary. Object does not exist.
| 0025-618 | The following attribute was specified multiple times. <[attribute]> |
Explanation: The user entered the same attribute name (to be returned in the output) more than once. For example: splstnodes node_number node_number
User Response: Remove duplicates in the command invocation and reinvoke command.
| 0025-619 | The following attribute was specified as a search argument multiple times. program name issuing message |
Explanation: The user entered the same attribute name as a search argument- <attr==value> more than once. For example:
splstnodes node_number==1 node_number==3
User Response: Remove duplicates in the command invocation and reinvoke the command.
| 0025-650 | Wrong number of operands. |
Explanation: The wrong number of operands were entered on the SDRSetTsAuth command. The command requires a partition IP address and an optional value to set ts_auth_methods. If ts_auth_methods value is not provided, it will be unset.
User Response: Correct the syntax and enter the command again.
| 0025-651 | The ts_auth_methods value is not valid. |
Explanation: The optional ts_auth_methods value entered on the SDRSetTsAuth command must be "dce", "compat", or "dce:compat".
User Response: Correct the syntax and enter the command again.
| 0025-652 | The specified Syspar does not exist. |
Explanation: The first operand of the SDRSetTsAuth command must be a valid Syspar IP address.
User Response: Correct the syntax and enter the command again.
| 0025-701 | NonAscii Data Found in FILE: LINENUMBER : LINE |
Explanation: The SDR filename, line number, and content of the line is displayed when there is non-ASCII data found in this line.
User Response: None.
| 0025-702 | SDR error: The following Class was found, but no corresponding SDR definition exists. |
Explanation: Class was found but a class definition file was not found.
User Response: Contact the IBM Support Center.
| 0025-703 | NonAscii Data Found in System Class : Attribute = Value |
Explanation: Where there is non-ASCII data found in a system class, the system class name, the attribute name that contains the non-ASCII data, and the data value are displayed.
User Response: None.
| 0025-704 | NonAscii Data Found in System Partitions : Class : Attribute = Value |
Explanation: When there is non-ASCII data found in a system partition class, the system partition name, class name, attribute name that contains the non-ASCII data, and the data value are displayed.
User Response: None.
| 0025-705 | The SDRObject Containing this data.: |
Explanation: When there is non-ASCII data found in an SDR class, the object that contains the non-ASCII data is displayed. This message is displayed after message 0025-703 or 0025-704 to provide more detailed information.
User Response: None.
| 0025-707 | Class contains that is not valid data. |
Explanation: The Class file contains data that is not valid, such as data without an attribute key.
User Response: Check the data to ensure that it is valid.
| 0025-708 | The SDRScan command can only run on the control workstation. |
Explanation: User tried to run SDRScan command on a node. This command can only run on the control workstation.
User Response: Run the SDRScan command on the control workstation.