AIX 5L Version 5.

3 򔻐򗗠򙳰

Message Center Reference

SC23-4901-00
AIX 5L Version 5.3 򔻐򗗠򙳰

Message Center Reference

SC23-4901-00
 Note
Before using this information and the product it supports, read the information in “Notices,” on page 223.

First Edition (August 2004)

This edition applies to AIX 5L Version 5.3 and to all subsequent releases of this product until otherwise indicated in
new editions.
A reader’s comment form is provided at the back of this publication. If the form has been removed, address
comments to Information Development, Department 04XA-905-6C006, 11501 Burnet Road, Austin, Texas
78758-3493. To send comments electronically, use this commercial Internet address: [email protected]. Any
information that you supply may be used without incurring any obligation to you.
© Copyright International Business Machines Corporation 2003, 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Case-Sensitivity in AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
ISO 9000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Message Component 0042 . . . . . . . . . . . . . . . . . . . . . . . . 1

Detailed Information for Message Component 0042 . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Message Component 0301 . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 3. Message Component 0315 . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4. Message Component 0402 . . . . . . . . . . . . . . . . . . . . . . . . 43

Detailed Information for Message Component 0402 . . . . . . . . . . . . . . . . . . . . 43

Chapter 5. Message Component 0403 . . . . . . . . . . . . . . . . . . . . . . . . 47

Detailed Information for Message Component 0403 . . . . . . . . . . . . . . . . . . . . 47

Chapter 6. Message Component 0453 . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 7. Message Component 0454 . . . . . . . . . . . . . . . . . . . . . . . . 51

Chapter 8. Message Component 0460 . . . . . . . . . . . . . . . . . . . . . . . . 53

Detailed Information for Message Component 0460 . . . . . . . . . . . . . . . . . . . . 53

Chapter 9. Message Component 0503 . . . . . . . . . . . . . . . . . . . . . . . . 55

Detailed Information for Message Component 0503 . . . . . . . . . . . . . . . . . . . . 55

Chapter 10. Message Component 0504. . . . . . . . . . . . . . . . . . . . . . . . 57

Chapter 11. Message Component 0509 . . . . . . . . . . . . . . . . . . . . . . . . 59

Detailed Information for Message Component 0509 . . . . . . . . . . . . . . . . . . . . 59

Chapter 12. Message Component 0511 . . . . . . . . . . . . . . . . . . . . . . . . 63

Detailed Information for Message Component 0511 . . . . . . . . . . . . . . . . . . . . 63

Chapter 13. Message Component 0512. . . . . . . . . . . . . . . . . . . . . . . . 71

Detailed Information for Message Component 0512 . . . . . . . . . . . . . . . . . . . . 71

Chapter 14. Message Component 0514. . . . . . . . . . . . . . . . . . . . . . . . 73

Detailed Information for Message Component 0514 . . . . . . . . . . . . . . . . . . . . 74

Chapter 15. Message Component 0516. . . . . . . . . . . . . . . . . . . . . . . . 79

Detailed Information for Message Component 0516 . . . . . . . . . . . . . . . . . . . . 80

Chapter 16. Message Component 0517. . . . . . . . . . . . . . . . . . . . . . . . 87

Chapter 17. Message Component 0518. . . . . . . . . . . . . . . . . . . . . . . . 89

Chapter 18. Message Component 0519. . . . . . . . . . . . . . . . . . . . . . . . 91

Detailed Information for Message Component 0519 . . . . . . . . . . . . . . . . . . . . 91

© Copyright IBM Corp. 2003, 2004 iii

Chapter 19. Message Component 0551. . . . . . . . . . . . . . . . . . . . . . . . 93
Detailed Information for Message Component 0551 . . . . . . . . . . . . . . . . . . . . 94

Chapter 20. Message Component 0602. . . . . . . . . . . . . . . . . . . . . . . . 97

Detailed Information for Message Component 0602 . . . . . . . . . . . . . . . . . . . . 97

Chapter 21. Message Component 0652. . . . . . . . . . . . . . . . . . . . . . . . 99

Detailed Information for Message Component 0652 . . . . . . . . . . . . . . . . . . . . 99

Chapter 22. Message Component 0653 . . . . . . . . . . . . . . . . . . . . . . . 101

Detailed Information for Message Component 0653 . . . . . . . . . . . . . . . . . . . 102

Chapter 23. Message Component 0654 . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 24. Message Component 0702 . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 25. Message Component 0703 . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 26. Message Component 0705 . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 27. Message Component 0706 . . . . . . . . . . . . . . . . . . . . . . . 113

Detailed Information for Message Component 0706 . . . . . . . . . . . . . . . . . . . 113

Chapter 28. Message Component 0710 . . . . . . . . . . . . . . . . . . . . . . . 115

Chapter 29. Message Component 0781 . . . . . . . . . . . . . . . . . . . . . . . 117

Detailed Information for Message Component 0781 . . . . . . . . . . . . . . . . . . . 118

Chapter 30. Message Component 0803 . . . . . . . . . . . . . . . . . . . . . . . 129

Detailed Information for Message Component 0803 . . . . . . . . . . . . . . . . . . . 129

Chapter 31. Message Component 0821 . . . . . . . . . . . . . . . . . . . . . . . 133

Detailed Information for Message Component 0821 . . . . . . . . . . . . . . . . . . . 134

Chapter 32. Message Component 0822 . . . . . . . . . . . . . . . . . . . . . . . 137

Detailed Information for Message Component 0822 . . . . . . . . . . . . . . . . . . . 137

Chapter 33. Message Component 0826 . . . . . . . . . . . . . . . . . . . . . . . 139

Detailed Information for Message Component 0826 . . . . . . . . . . . . . . . . . . . 139

Chapter 34. Message Component 0827 . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 35. Message Component 0832 . . . . . . . . . . . . . . . . . . . . . . . 143

Detailed Information for Message Component 0832 . . . . . . . . . . . . . . . . . . . 143

Chapter 36. Message Component 0950 . . . . . . . . . . . . . . . . . . . . . . . 147

Detailed Information for Message Component 0950 . . . . . . . . . . . . . . . . . . . 147

Chapter 37. Message Component 1001 . . . . . . . . . . . . . . . . . . . . . . . 153

Chapter 38. Message Component 1002 . . . . . . . . . . . . . . . . . . . . . . . 155

Chapter 39. Message Component 1003 . . . . . . . . . . . . . . . . . . . . . . . 157

Chapter 40. Message Component 1004 . . . . . . . . . . . . . . . . . . . . . . . 159

iv Message Center Reference

Chapter 41. Message Component 1005 . . . . . . . . . . . . . . . . . . . . . . . 161

Chapter 42. Message Component 1006 . . . . . . . . . . . . . . . . . . . . . . . 163

Chapter 43. Message Component 1007 . . . . . . . . . . . . . . . . . . . . . . . 165

Chapter 44. Message Component 1201 . . . . . . . . . . . . . . . . . . . . . . . 167

Chapter 45. Message Component 1232 . . . . . . . . . . . . . . . . . . . . . . . 169

Chapter 46. Message Component 1254 . . . . . . . . . . . . . . . . . . . . . . . 171

Detailed Information for Message Component 1254 . . . . . . . . . . . . . . . . . . . 171

Chapter 47. Message Component 1281 . . . . . . . . . . . . . . . . . . . . . . . 173

Chapter 48. Message Component 1283 . . . . . . . . . . . . . . . . . . . . . . . 175

Chapter 49. Message Component 1285 . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 50. Message Component 1286 . . . . . . . . . . . . . . . . . . . . . . . 179

Chapter 51. Message Component 1311 . . . . . . . . . . . . . . . . . . . . . . . 181

Chapter 52. Message Component 1312 . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 53. Message Component 1345 . . . . . . . . . . . . . . . . . . . . . . . 185

Chapter 54. Message Component 1356 . . . . . . . . . . . . . . . . . . . . . . . 187

Detailed Information for Message Component 1356 . . . . . . . . . . . . . . . . . . . 187

Chapter 55. Message Component 1363 . . . . . . . . . . . . . . . . . . . . . . . 189

Chapter 56. Message Component 1365 . . . . . . . . . . . . . . . . . . . . . . . 191

Chapter 57. Message Component 1371 . . . . . . . . . . . . . . . . . . . . . . . 193

Chapter 58. Message Component 1386 . . . . . . . . . . . . . . . . . . . . . . . 195

Chapter 59. Message Component 1800 . . . . . . . . . . . . . . . . . . . . . . . 197

Detailed Information for Message Component 1800 . . . . . . . . . . . . . . . . . . . 197

Chapter 60. Message Component 1820 . . . . . . . . . . . . . . . . . . . . . . . 201

Detailed Information for Message Component 1820 . . . . . . . . . . . . . . . . . . . 202

Chapter 61. Message Component 1831 . . . . . . . . . . . . . . . . . . . . . . . 205

Detailed Information for Message Component 1831 . . . . . . . . . . . . . . . . . . . 206

Chapter 62. Message Component 2053 . . . . . . . . . . . . . . . . . . . . . . . 207

Chapter 63. Message Component 2054 . . . . . . . . . . . . . . . . . . . . . . . 209

Chapter 64. Message Component 2055 . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 65. Message Component 2056 . . . . . . . . . . . . . . . . . . . . . . . 215

Chapter 66. Message Component 3001 . . . . . . . . . . . . . . . . . . . . . . . 217

Contents v
Detailed Information for Message Component 3001 . . . . . . . . . . . . . . . . . . . 217

Chapter 67. Message Component 3015 . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 68. Message Component 4050 . . . . . . . . . . . . . . . . . . . . . . . 221

Appendix. Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

vi Message Center Reference

About This Book
This book provides information about messages and troubleshooting.

Who Should Use This Book

This book is intended for users of the AIX operating system who are attempting to troubleshoot errors.
Users of this book should be familiar with AIX usage (entering commands, creating and deleting files,
editing files, and navigating the file system).

Highlighting
The following highlighting conventions are used in this book:

Bold Identifies commands, subroutines, keywords, files, structures, directories, and other items whose
names are predefined by the system. Also identifies graphical objects such as buttons, labels, and
icons that the user selects.
Italics Identifies parameters whose actual names or values are to be supplied by the user.
Monospace Identifies examples of specific data values, examples of text similar to what you might see
displayed, examples of portions of program code similar to what you might write as a programmer,
messages from the system, or information you should actually type.

Case-Sensitivity in AIX
Everything in the AIX operating system is case-sensitive, which means that it distinguishes between
uppercase and lowercase letters. For example, you can use the ls command to list files. If you type LS, the
system responds that the command is ″not found.″ Likewise, FILEA, FiLea, and filea are three distinct file
names, even if they reside in the same directory. To avoid causing undesirable actions to be performed,
always ensure that you use the correct case.

ISO 9000
ISO 9000 registered quality systems were used in the development and manufacturing of this product.

Related Publications
The following books contain information about troubleshooting:
v AIX 5L Version 5.3 General Programming Concepts: Writing and Debugging Programs
v AIX 5L Version 5.3 Kernel Extensions and Device Support Programming Concepts

© Copyright IBM Corp. 2003, 2004 vii

viii Message Center Reference
Chapter 1. Message Component 0042
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

0042–001 Error Recovery Information

0042–002 Error Recovery Information
0042–003 Error Recovery Information
0042–004 Error Recovery Information
0042–005 Error Recovery Information
0042–006 Error Recovery Information
0042–007 Error Recovery Information
0042–008 Error Recovery Information
0042–011 Error Recovery Information
0042–012 Error Recovery Information
0042–013 Error Recovery Information
0042–014 Error Recovery Information
0042–015 Error Recovery Information
0042–016 Error Recovery Information
0042–017 Error Recovery Information
0042–018 Error Recovery Information
0042–019 Error Recovery Information
0042–020 Error Recovery Information
0042–021 Error Recovery Information
0042–022 Error Recovery Information
0042–023 Error Recovery Information
0042–024 Error Recovery Information
0042–025 Error Recovery Information
0042–027 Error Recovery Information
0042–028 Error Recovery Information
0042–029 Error Recovery Information
0042–030 Error Recovery Information
0042–031 Error Recovery Information
0042–032 Error Recovery Information
0042–033 Error Recovery Information
0042–034 Error Recovery Information
0042–035 Error Recovery Information
0042–036 Error Recovery Information
0042–037 Error Recovery Information
0042–038 Error Recovery Information
0042–039 Error Recovery Information
0042–040 Error Recovery Information
0042–041 Error Recovery Information
0042–042 Error Recovery Information
0042–043 Error Recovery Information
0042–043 Error Recovery Information
0042–044 Error Recovery Information
0042–045 Error Recovery Information
0042–046 Error Recovery Information

© Copyright IBM Corp. 2003, 2004 1

0042–047 Error Recovery Information
0042–048 Error Recovery Information
0042–049 Error Recovery Information
0042–051 Error Recovery Information
0042–052 Error Recovery Information
0042–053 Error Recovery Information
0042–055 Error Recovery Information
0042–056 Error Recovery Information
0042–058 Error Recovery Information
0042–059 Error Recovery Information
0042–060 Error Recovery Information
0042–061 Error Recovery Information
0042–062 Error Recovery Information
0042–063 Error Recovery Information
0042–064 Error Recovery Information
0042–065 Error Recovery Information
0042–066 Error Recovery Information
0042–067 Error Recovery Information
0042–069 Error Recovery Information
0042–073 Error Recovery Information
0042–074 Error Recovery Information
0042–075 Error Recovery Information
0042–076 Error Recovery Information
0042–077 Error Recovery Information
0042–078 Error Recovery Information
0042–079 Error Recovery Information
0042–081 Error Recovery Information
0042–083 Error Recovery Information
0042–084 Error Recovery Information
0042–086 Error Recovery Information
0042–093 Error Recovery Information
0042–109 Error Recovery Information
0042–111 Error Recovery Information
0042–113 Error Recovery Information
0042–118 Error Recovery Information
0042–121 Error Recovery Information
0042–124 Error Recovery Information
0042–129 Error Recovery Information
0042–130 Error Recovery Information
0042–131 Error Recovery Information
0042–132 Error Recovery Information
0042–133 Error Recovery Information
0042–134 Error Recovery Information
0042–135 Error Recovery Information
0042–136 Error Recovery Information
0042–137 Error Recovery Information
0042–138 Error Recovery Information
0042–139 Error Recovery Information
0042–140 Error Recovery Information
0042–141 Error Recovery Information
0042–142 Error Recovery Information
0042–143 Error Recovery Information
0042–144 Error Recovery Information
0042–145 Error Recovery Information
0042–146 Error Recovery Information

2 Message Center Reference

0042–147 Error Recovery Information
0042–148 Error Recovery Information
0042–150 Error Recovery Information
0042–151 Error Recovery Information
0042–152 Error Recovery Information
0042–153 Error Recovery Information
0042–154 Error Recovery Information
0042–155 Error Recovery Information
0042–156 Error Recovery Information
0042–157 Error Recovery Information
0042–158 Error Recovery Information
0042–159 Error Recovery Information
0042–160 Error Recovery Information
0042–161 Error Recovery Information
0042–162 Error Recovery Information
0042–163 Error Recovery Information
0042–164 Error Recovery Information
0042–165 Error Recovery Information
0042–166 Error Recovery Information
0042–167 Error Recovery Information
0042–168 Error Recovery Information
0042–169 Error Recovery Information
0042–170 Error Recovery Information
0042–171 Error Recovery Information
0042–172 Error Recovery Information
0042–173 Error Recovery Information
0042–174 Error Recovery Information
0042–175 Error Recovery Information
0042–176 Error Recovery Information
0042–177 Error Recovery Information
0042–178 Error Recovery Information
0042–179 Error Recovery Information
0042–180 Error Recovery Information
0042–181 Error Recovery Information
0042–182 Error Recovery Information
0042–183 Error Recovery Information
0042–184 Error Recovery Information
0042–185 Error Recovery Information
0042–186 Error Recovery Information
0042–187 Error Recovery Information
0042–188 Error Recovery Information
0042–189 Error Recovery Information
0042–190 Error Recovery Information
0042–191 Error Recovery Information
0042–192 Error Recovery Information
0042–193 Error Recovery Information
0042–194 Error Recovery Information
0042–195 Error Recovery Information
0042–196 Error Recovery Information
0042–197 Error Recovery Information
0042–198 Error Recovery Information
0042–199 Error Recovery Information
0042–204 Error Recovery Information
0042–205 Error Recovery Information
0042–206 Error Recovery Information

Chapter 1. Message Component 0042 3

0042–207 Error Recovery Information
0042–208 Error Recovery Information
0042–209 Error Recovery Information
0042–210 Error Recovery Information
0042–211 Error Recovery Information
0042–212 Error Recovery Information
0042–213 Error Recovery Information
0042–214 Error Recovery Information
0042–215 Error Recovery Information
0042–216 Error Recovery Information
0042–217 Error Recovery Information
0042–218 Error Recovery Information
0042–219 Error Recovery Information
0042–220 Error Recovery Information
0042–221 Error Recovery Information
0042–222 Error Recovery Information
0042–223 Error Recovery Information
0042–224 Error Recovery Information
0042–225 Error Recovery Information
0042–226 Error Recovery Information
0042–227 Error Recovery Information
0042–228 Error Recovery Information
0042–229 Error Recovery Information
0042–230 Error Recovery Information
0042–231 Error Recovery Information
0042–232 Error Recovery Information
0042–233 Error Recovery Information
0042–234 Error Recovery Information
0042–235 Error Recovery Information
0042–236 Error Recovery Information
0042–237 Error Recovery Information
0042–238 Error Recovery Information
0042–239 Error Recovery Information
0042–240 Error Recovery Information
0042–241 Error Recovery Information
0042–242 Error Recovery Information
0042–243 Error Recovery Information
0042–244 Error Recovery Information
0042–245 Error Recovery Information
0042–246 Error Recovery Information
0042–247 Error Recovery Information
0042–248 Error Recovery Information
0042–249 Error Recovery Information
0042–250 Error Recovery Information
0042–251 Error Recovery Information
0042–252 Error Recovery Information
0042–253 Error Recovery Information
0042–254 Error Recovery Information
0042–255 Error Recovery Information
0042–256 Error Recovery Information
0042–257 Error Recovery Information
0042–258 Error Recovery Information
0042–259 Error Recovery Information
0042–260 Error Recovery Information
0042–261 Error Recovery Information

4 Message Center Reference

0042–262 Error Recovery Information
0042–263 Error Recovery Information
0042–264 Error Recovery Information
0042–265 Error Recovery Information
0042–266 Error Recovery Information
0042–267 Error Recovery Information
0042–268 Error Recovery Information
0042–269 Error Recovery Information
0042–270 Error Recovery Information
0042–271 Error Recovery Information
0042–272 Error Recovery Information
0042–273 Error Recovery Information
0042–274 Error Recovery Information
0042–275 Error Recovery Information
0042–276 Error Recovery Information
0042–277 Error Recovery Information
0042–278 Error Recovery Information
0042–279 Error Recovery Information
0042–280 Error Recovery Information
0042–281 Error Recovery Information
0042–282 Error Recovery Information
0042–283 Error Recovery Information
0042–323 Error Recovery Information
0042–324 Error Recovery Information
0042–325 Error Recovery Information
0042–326 Error Recovery Information
0042–327 Error Recovery Information
0042–330 Error Recovery Information

Detailed Information for Message Component 0042

0042–001 String : processing error encountered on String String

Explanation: An error was detected by an underlying NIM method (a subcommand). This message describes where
the error occurred with respect to the NIM client or master and may be useful in troubleshooting the problem. The
messages that are displayed subsequent to this error are normally the true source of the problem.
User response: Read the additional information and error messages, and refer to their explanation and recovery
hints as appropriate.

0042–002 String : error signal number String received - processing aborted

Explanation: An interrupt signal has been received, perhaps because the user entered Ctrl-C or used the kill
command on a NIM process.
User response: The NIM operation that was active has been interrupted. Perform the operation again.

Note: This error is expected if it occurs after the nimclient -o bos_inst operation is performed on a client.

0042–003 String : error on system call; info follows: String

Explanation: An error has been returned from a system call.
User response: Fix the condition that caused the system call to fail and perform the operation again.

Chapter 1. Message Component 0042 5

0042–004 String : error on system call String
Explanation: An error has been returned from a system call.
User response: Fix the condition that caused the system call to fail and perform the operation again.

0042–005 String : ODM error encountered; odmerrno = Number

Explanation: The Object Data Manager (ODM) has returned an error.
User response: Refer to the Message Database located on the Information Center Web page for specific details of
the error. Fix the ODM problem and perform the NIM operation again.

0042–006 String : ( String ) String String

Explanation: Generic error message used for rarely occurring NIM errors.
User response: Phrases contained in this error message are constructed from debug information and from
messages returned by commands called by NIM. If the content of the message does not give insight into the true
cause of failure, contact your point of sale.

0042–007 String : internal error (buffer overflow) in function String

Explanation: An internal NIM error has occurred.
User response: Try the operation again.

0042–008 String : Request denied - String

Explanation: NIM has attempted to establish socket communications with a remote machine, and it has refused the
connection.
User response: If the failing operation occurred on the master, verify that the master has rsh permissions on the
client and that inetd is active on the client; otherwise, verify that the nimesis daemon is active on the master. If the
failing operation was the niminit command on the client, a possible cause of failure is that the master does not have a
network object that corresponds to the client’s network. A network object that represents the client’s network needs to
be added to the database on the master; then a route needs to be added from the master’s network to the client’s
network.
If the failure occurs during operations initiated from a client, using the nimclient command, or during a NIM installation
of the base operating system, the cpuid attribute on the client’s machine definition may be obsolete (for example, if
the machine’s system planar was recently replaced). To guarantee that this is not the case, erase the cpuid from the
machine definition by issuing the following from the master:
nim -Fo change -a cpuid= ClientName

0042–011 String : unable to access the /etc/niminfo file

Explanation: The /etc/niminfo file is not accessible.
User response: The niminfo file is required by all NIM commands and methods. This file is created when the
bos.sysmgt.nim.master and bos.sysmgt.nim.client packages are configured. If this file is not available, this
indicates that the NIM package has not been initialized or that this file has been deleted. To create the niminfo file,
execute the nimconfig command on the master or the niminit command on the client. To recreate a deleted or
corrupted niminfo file, enter from the master:
nimconfig -r

OR enter from the client:

niminit -aname=ClientName -amaster=MasterHostName -amaster_port=MasterPortValue

6 Message Center Reference

0042–012 String : this command may only be executed on a NIM master
Explanation: The specified command may only be executed on the master.
User response: Execute the desired operation on the NIM master.

0042–013 String : unable to obtain the global NIM lock

Explanation: The global lock used for synchronized access to the NIM database could not be obtained.
User response: Try the operation again. If the same error is returned, verify that there are no active NIM commands.
If this is true, remove the /var/adm/nim/glock file and try the operation again. If the file does not exist and the error
persists, contact your point of sale.

0042–014 String : an internal error has occurred resulting in an invalid String object named String
Explanation: An internal NIM error has occurred.
User response: Perform the remove operation on the NIM object followed by the appropriate define operation.

0042–015 String : syntax error String

Explanation: A syntax error has been detected.
User response: Refer to the appropriate man page for the NIM command and try again using valid syntax.

0042–016 String : - char is not a valid option for this operation String
Explanation: An invalid option has been specified.
User response: Refer to the appropriate man page for the NIM command and try again using valid syntax.

0042–017 String : invalid option-argument for - char String

Explanation: An invalid value was specified for an option argument.
User response: Refer to the appropriate man page for the NIM command and try again using valid syntax.

0042–018 String : -char is a required option for this operation String

Explanation: A required option was not supplied.
User response: Refer to the appropriate man page for the NIM command and try again using valid syntax.

0042–019 String : option -char requires an argument String

Explanation: An option that requires an argument was specified without its argument.
User response: Refer to the appropriate man page for the NIM command and try again, specifying the missing
argument.

0042–020 String : String must be supplied for this operation String

Explanation: An operand was required but not supplied. Usually, the operand is the NIM object to which a given
operation is being applied (that is, a NIM name for a network, machine or resource object that is the target of the NIM
operation).
User response: Refer to the appropriate man page for the NIM command and try again using valid syntax. If you do
not know the name of an operand, and if the failing operation was targeted toward an existing NIM object, enter:
lsnim -l -t ObjectType

OR
lsnim -l

Chapter 1. Message Component 0042 7

to determine the operand name.

0042–021 String : the String attribute is required for this operation

Explanation: A NIM attribute was required for the operation.
User response: Specify the missing attribute. If the failing command is the nim or nimclient command, to obtain a
list of attributes, enter from the master:
lsnim -q ObjectName

OR
lsnim -q -t ObjectType

OR enter from the clients:

nimclient -l lsnimOptions

For the other NIM commands, see the appropriate NIM man page.

0042–022 String : String exceeds the maximum limit of Number

Explanation: A value was specified that exceeds the bounds of acceptable values.
User response: Supply a value within the acceptable bounds.

0042–023 String : String is not a valid String

Explanation: The specified value is not valid.
User response: Try the command again with a valid value. To determine the valid values for classes of objects and
operations as they pertain to those objects, enter:
lsnim -Pc ObjectClass

AND
lsnim -POc ObjectClass

where ObjectClass is one of machines, networks, or resources.

0042–024 String : String is not a valid type for String

Explanation: An invalid NIM object type was specified.
User response: Specify a valid NIM object type. See user actions for error 023 for lsnim options to determine a
valid object type.

0042–025 String : the String operation cannot be applied to String types

Explanation: The specified operation cannot be supplied to the specified NIM object.
User response: Specify an operation that can be applied to the object. Enter lsnim -O ObjectName for a list of valid
operations that can be applied to the object.

0042–027 String : String is required to complete the definition of the String object. This attribute is either
currently missing or the current operation would cause it to become missing.
Explanation: The specified object is missing an attribute that is required to complete the specified operation.
User response: Redefine the object that is missing an attribute by performing the remove operation followed by the
define operation.

8 Message Center Reference

0042–028 String : String cannot be used for this operation
Explanation: The specified information cannot be supplied in the current context.
User response: Try the operation again without supplying the offending attribute.

0042–029 String : the String attribute cannot be supplied for this operation
Explanation: The specified information cannot be supplied in the current context.
User response: Try the operation again without supplying the offending attribute.

0042–030 String : a sequence number may not be specified with the String attribute
Explanation: A sequence number was opened to an attribute that doesn’t allow sequence numbers.
User response: Try the operation again without a sequence number on the offending attribute.

0042–031 String : unable to generate a unique id

Explanation: An internal NIM error has occurred. NIM is unable to generate a unique object ID.
User response: Try the operation again.

0042–032 String : String must be unique and String already exists

Explanation: The specified value for the attribute is not unique and it must be.
User response: Supply a unique value for the attribute.

0042–033 String : String attr already exists with seqno of Number

Explanation: The specified value is not unique and it must be. An attribute with a sequence number requires a
unique value.
User response: Supply a unique value.

0042–034 String : unable to generate a new seqno for String

Explanation: The specified value is not unique and it must be.
User response: Supply a unique value.

0042–035 String : unable to find attr which matches this query: String
Explanation: NIM was attempting to access an attribute that had the specified characteristics, but the attribute
doesn’t exist.
User response: Make sure the attribute exists and retry the operation.

0042–036 String : String cannot serve a resource because of its type ( String )
Explanation: The define operation failed for a resource because the specified server does not have a standalone
configuration.
User response: Try the operation again using a NIM client that is a standalone machine.

0042–037 String : the state of String prevents this operation from succeeding
Explanation: The NIM state of the specified object prevents the operation from succeeding.
User response: NIM states are used to synchronize activity among NIM objects. To perform the desired operation,
the state of the specified object must be changed. If the specified object is in an unexpected state, check the system
to make sure another user or process is not manipulating the object. Use the reset operation to set the object to a
known state and try the operation again.

Chapter 1. Message Component 0042 9

0042–038 String : unable to continue because String is locked
Explanation: An object that NIM would operate on is already locked and thus cannot be operated on.
User response: NIM object locks are used to synchronize activity among NIM objects. These locks are temporary,
so try the operation again after some delay. The value of the lock is the process ID of a NIM process that is using the
lock. If the lock persists and no NIM commands are active, reset all NIM locks by stopping the nimesis daemon, then
restarting it.

0042–039 String : unacceptable release level of String . String for String

Explanation: The operating system version or release level of the specified object is unacceptable.
User response: Perform the desired operation on objects that have the appropriate operating system version and
release levels.

0042–040 String : unable to remove the String definition because it is currently referenced by other objects
Explanation: A NIM object could not be removed because it is being used by some other NIM object.
User response: Remove all references to the object to be removed before the remove operation is specified. If NIM
states are such that you cannot remove references to the object and you want to remove the object anyway, provide
the -F flag to the remove operation.

0042–041 String : String already exists

Explanation: A specified value has already been defined to NIM.
User response: Specify a value that isn’t already known to NIM.

Note: If /etc/niminfo is the value and the NIM command producing this error is niminit, this means that niminit has
already been performed. If you want to reinitialize your NIM master or client, deinstall the appropriate fileset,
and then reinstall and reconfigure the NIM master or client fileset.

0042–042 String : unable to communicate with String

Explanation: The specified machine could not be reached with the ping command from the master.
User response: If the operation you were attempting to perform requires that the target machine be running and that
it can be reached, then verify that the machine is currently running. If not, turn it on; otherwise, perform network
diagnostic procedures to determine why the master could not reach the target machine.

0042–043 String : unable to remove String because one or more NIM resources are still defined as being
served by that machine
Explanation: The remove operation cannot be performed, because the target machine currently serves a NIM
resource that has been allocated for use. Performing the operation at this time could lead to processing failures on
clients that are attempting to use the served resources.
User response: You need to deallocate all resources that the target serves before you can remove the machine.

0042–044 String : missing in attribute assignment for String

Explanation: You have specified a NIM attribute without an accompanying value. Most NIM attributes can only be
specified with a value assigned to them in the form of attr=value.
User response: Retry the operation with a value assigned to the specified attribute.

0042–045 String : a sequence number must be specified with all String attributes for this operation
Explanation: Some NIM attributes can be added to an object’s definition more than once. In these cases, a
sequence number is used to uniquely identify each attribute of that type. In this case, you have specified an attribute
of this type without its required sequence number and, therefore, NIM is unable to determine which attribute you are
attempting to specify.

10 Message Center Reference

User response: Verify the sequence number and try the operation again.

0042–046 String : unable to String the file String

Explanation: NIM was unable to perform an operation on the specified file. This may be due to the permissions on
the file. The file usually needs read, write, and, in some cases, execute permissions for root.
User response: Change the permissions of the specified file and try the operation again.

0042–047 String : unable to allocate the String resource because its type cannot be used by String objects
Explanation: Some types of NIM resources may only be used by specific machine types. In this case, you attempted
to allocate a NIM resource to a type of machine that is not allowed to use that type of resource.
User response: Specify a resource type that the machine is allowed to use when performing allocation for the target
machine.
To determine the valid resource types, enter:
lsnim -p -s ResourceSubclassForMachineType

To view the subclasses that are available, enter: lsnim -p -S

0042–048 String : String is unable to access the String resource due to network routing
Explanation: When resource allocation is requested, NIM verifies that the designated client has the potential to
communicate with the server of the resource. NIM does this by checking the NIM routing between the network that the
client’s primary interface connects to and all the networks that the server connects to. In this case, a NIM route is
missing between the client and the server.
User response: Either establish a NIM route between the client and the server or choose a different resource to
allocate.

0042–049 String : either String or another resource of this type has already been allocated to String
Explanation: Only one resource of this type may be allocated to the client and one has already been allocated.
User response: Choose the resource that you want to use and deallocate the currently allocated resource of this
type if you want to use the new one.

0042–051 String : unable to resolve String to an String

Explanation: NIM was unable to resolve a host name to an IP address or the other way around.
User response: All host names that are used in the NIM environment must be resolvable. Perform the appropriate
network administration tasks to ensure that the specified host name is resolvable and try the operation again.

0042–052 String : unable to String String because resources have been allocated to it
Explanation: One or more NIM resources are still allocated to the machine that you have requested to be removed
from the NIM environment. To remove a machine, it cannot have any resources allocated to it.
User response: Deallocate all resources that have been allocated to the target machine and try the operation again.

0042–053 String : there is no NIM object named String

Explanation: You have specified the name of a NIM object that does not currently exist in the NIM environment. NIM
can only operate on objects that have been defined to NIM.
User response: Verify that you have spelled the name of the object correctly and that it has already been defined.
The name of a target machine for a NIM operation must be the NIM name, not the host name. Enter:
lsnim -l -t ObjectType

OR

Chapter 1. Message Component 0042 11

lsnim -l

to obtain listings of currently defined objects in the NIM environment. If you need to define the object, use the define
operation.

0042–055 String : String is not a valid source for this operation

Explanation: Many NIM operations require a source for installable images. You have specified a source that cannot
be used for this operation. Examples of valid sources for NIM operations are:
v /dev/rmt0, /dev/cd1 for lpp_source definition
v rte, spot, mksysb for bos_inst operation
User response: Try the operation again using a source that the operation can use.

0042–056 String : duplicate attribute assignment for String

Explanation: You have specified the same attribute assignment more than once.
User response: Try the operation again using only one instance of the attribute assignment.

0042–058 String : unable to allocate String to String because it does not support the network interface type
or platform of that client
Explanation: You have attempted to allocate a SPOT to a client whose primary network interface type or platform is
not supported by the SPOT. For a client to use a SPOT, the SPOT must support the network interface type and
platform of the client’s primary interface.
User response: Install the appropriate device support into the SPOT, which will allow the SPOT to support the
client’s primary interface type and platform, or choose a different SPOT that supports the client’s primary interface type
and platform.

0042–059 String : conflict between the supplied type ( String ) and the real type ( String ) for String
Explanation: In an attribute assignment (in the form of attr=value), the value you have specified represents a NIM
object whose type conflicts with the object type of the specified attr.
User response: Try the operation again using the attr that corresponds to the type of object that value represents.

0042–060 String : multiple String attributes were specified and only one is allowed
Explanation: You have specified multiple attribute assignments for an attribute that may only be specified once.
User response: Try the operation again, using only one instance of the attribute.

0042–061 String : the String resource is currently allocated for client use
Explanation: You have requested an operation to be performed on a NIM resource object that is currently allocated
for client use. NIM is not allowing this operation to be performed because it may interrupt the client’s use of the
resource.
User response: Try the operation again when the resource is not allocated for client use. If necessary, try the force
option (-F flag) to disregard the preventive check by NIM. In some cases, NIM will allow the operation to be
performed.

0042–062 String : String is missing something which is required

Explanation: The NIM object that was operated on is missing something that is required for its definition to be
complete.
User response: List information about the object using the lsnim command. Each item that is missing from the
object’s definition will be represented by a missing attribute. Perform the appropriate NIM operation that will add the
missing item to the object’s definition. For a SPOT, if network boot images are missing, apply the check operation to

12 Message Center Reference

the SPOT. If software filesets are missing from a SPOT, allocate an lpp_source that contains the required filesets and
apply the cust operation to the SPOT.

0042–063 String : the following resource types are required for this operation but have not yet been
allocated to String \
Explanation: Some NIM operations require access to one or more NIM resources to complete successfully. This
access is granted through the allocate operation. In this case, you have not allocated all the resources that are
required for this operation.
User response: Allocate all the required resources and try the operation again. For a list of required and optional
resources for a given operation, enter:
lsnim -q Operation ObjectName

OR
lsnim -q Operation -t ObjectType

0042–064 String : String is currently serving a resource ( String ) that is allocated for use
Explanation: The machine that is the target of the requested operation currently serves a NIM resource that is
allocated for client use. The requested operation cannot be performed until all resources that the target serves have
been deallocated for use.
User response: Deallocate all resources that the target serves and try the operation again.

0042–065 String : String is a reserved word and cannot be used to name objects
Explanation: You have specified a name that is reserved for NIM internal use only.
User response: Try the operation again using a different name. To determine what names are reserved, enter:
lsnim -a reserved

0042–066 String : the string String contains one or more characters which are not allowed to be used in
strings in the NIM environment
Explanation: You have specified one or more characters that are not allowed in NIM object names. NIM uses
regular expressions to perform many of its operations, so any character that has special meaning for regular
expressions cannot be used (for example, ^). Also, any character that has special meaning to the shell cannot be used
(for example, /).
User response: Try the operation again using valid characters.

0042–067 String : this operation cannot be applied to String because it is a reserved NIM object
Explanation: You have requested an operation to be performed on a NIM object that has been reserved for NIM
internal use only.
User response: Try the operation again, using a NIM object that is not reserved. To determine what objects are
reserved, enter:
lsnim -a reserved

0042–069 String : the String operation cannot be performed when the target has a String of String
Explanation: The requested operation cannot be performed at this time because it conflicts with the current NIM
state of the target. NIM uses states to synchronize NIM activity so that operations don’t interfere with each other.
User response: Try the operation again when the state changes or, if necessary, try using the force option (-F flag).
In some cases, NIM will allow you to override this state checking.
If you encounter this error as a result of trying to remove, using the reset operation, the boot resource from a client
that incorrectly has a state of ″ready for a NIM operation″, you can remove the boot resource from the NIM master by
entering:

Chapter 1. Message Component 0042 13

/usr/lpp/bos.sysmgt/nim/methods/m_dealloc_boot client_name

where client_name is the name of the NIM object for the client.

0042–073 String : unable to create a customization script for String because it does not have any
customization resources allocated to it
Explanation: To perform customization on a machine, NIM constructs a shell script that is executed on the target. To
construct this script, some type of resource that can be used for customization must be used. In this case, NIM could
not create the customization script because no resources have been allocated to the target that could be used for
customization purposes.
User response: Allocate one or more resources that can be used for customization and try the operation again. To
display the subclass of resources that can be used for customization, enter:
lsnim -p -s cust_res

0042–074 String : String is not a valid pathname because it has been specified with a relative path and
pathnames must be absolute
Explanation: You have specified an attribute assignment in which the value represents a relative path name. NIM
only allows absolute path names (that is, path names that begin with /) to be used.
User response: Try the operation again, using an absolute path name.

0042–075 String : error encountered when exporting String on String String

Explanation: The requested operation requires that a NIM resource be exported for a machine’s use. In this case,
NIM attempted to export the resource but an error was returned by an NFS utility.
User response: Fix the error condition that the NFS utility reported and try the operation again.

0042–076 String : port Num is already used by the String service

Explanation: You have specified a port number that is already in use.
User response: Try the operation again, using a port number that is currently not being used. Check the
/etc/services file.

Note: NIM uses both the specified port number and its successor. Therefore, ensure that the port number after the
specified port number is also free.

0042–077 String : unable to add routes from the NIM Master

Explanation: The niminit command is used to join the NIM environment. When executed, this command attempts to
add routing information that the NIM master has determined the client needs to participate in the NIM environment. In
this case, one or more of the required routes could not be added.
User response: Perform the appropriate network diagnostic task to determine why the route could not be added.

0042–078 String : unable to change the String NIM route because the destination network specified in the
new value does not match the destination network specified in the current value
Explanation: You have specified a change to a NIM routing attribute in which the destination network is different
from its current value. This is not allowed because only the gateway field of the routing attribute may be changed.
User response: If you are trying to change the connectivity between NIM networks, then you must remove the
current NIM route by supplying a NULL value for the appropriate routing attribute. Otherwise, specify the same
destination network when attempting to change the gateway field of the routing attribute.

14 Message Center Reference

0042–079 String : unable to deallocate String because String must be deallocated first
Explanation: In the NIM environment, one resource may depend on another for information. In this case, an
allocated resource has a dependency on the resource you have specified for deallocation.
User response: Deallocate the resource that is dependent on the resource causing the error.

0042–081 String : a resource already exists on String at location String ; due to NFS export restrictions, the
new location String may not be used
Explanation: NIM uses NFS to make remote resources available for client use. To avoid NFS export errors, NIM
enforces some restrictions on where a resource can be defined. In general, a NIM resource cannot be defined within a
directory that is already a NIM resource. Conversely, a NIM resource cannot be defined for a directory that already
contains an existing NIM resource.
User response: Move the resource to a location that adheres to NIM export rules and try the operation again.

0042–083 String : network hardware addresses must be unique and String is already being used by the
machine String
Explanation: Each network communications adapter has an associated network hardware address that is unique. In
this case, you attempted to define a NIM network interface using a network hardware address already being used by a
NIM machine object.
User response: Only one NIM interface attribute may be defined for each network communications adapter a client
might have. If you are attempting to add another interface definition, then verify that the hardware address is correct. If
so, then you must first change the interface attribute that is currently using that address. If not, try the operation again
with the correct hardware address.

0042–084 String : This machine is already configured to be a NIM Master

Explanation: The machine has already been configured to be a NIM master.
User response: If you want to reconfigure the machine as a NIM master, enter nim -o unconfig master, then
deinstall and reinstall the master fileset. You may then run the nimconfig command.

0042–086 String : a NIM route already exists between String and String (only 1 is allowed)
Explanation: You have attempted to add a NIM route between two NIM networks that already have a NIM route
between them. Only one NIM route can be specified between any two NIM networks.
User response: If you are attempting to change NIM routing, delete the existing NIM route and try the operation
again.

0042–093 String : unable to create directory String

Explanation: NIM attempted to create a directory, and the mkdir command returned an error.
User response: Fix the error reported by the mkdir command and try the operation again.

0042–109 String : unable to get filesystem information about String

Explanation: To complete the requested operation, NIM requires information about one or more file systems about
which it was unable to obtain information.
User response: Verify that the file systems exist. If not, either specify the correct path name when performing the
NIM operation or redefine the NIM environment so that all the participating file systems exist.

0042–111 String : invalid sequence number in String ; it must be between 1 and Number
Explanation: When a sequence number is specified for a NIM attribute, it must be within a specific range. You have
specified a sequence number that falls outside of the acceptable bounds.
User response: Try the operation again using a sequence number that is within the acceptable bounds.

Chapter 1. Message Component 0042 15

0042–113 String : unable get size requirements for String
Explanation: To complete the requested operation, NIM requires information about the size of one or more objects,
which NIM was unable to determine.
User response: If the object is a file or directory that does not exist, then create the file or directory and try the
operation again.

0042–118 String : a NIM operation is currently being performed on the String machine or it has resources
allocated to it
Explanation: You have requested to change characteristics of a NIM network on which there is currently one or
more active NIM operations. NIM is not allowing the change because changing the network characteristics at this time
could result in failures in the active operations.
User response: Wait until the NIM resources allocated to machines that use the network being changed have been
deallocated and try the operation again.

0042–121 String : Specify String OR String

Explanation: An invalid value has been specified.
User response: Try the operation again, using a valid value.

0042–124 String : NFS option String is NOT supported

Explanation: An NFS option was specified that is not supported.
User response: Try the operation again using valid NFS options. Refer to ″NFS Problem Determination″ in Networks
and communication management.

0042–129 String : String is an invalid resource type for this operation

Explanation: An invalid resource type was specified for this operation.
User response: Use the lsnim -q Operation -t TargetType command to view a list of required and optional resources
for Operation when applied to TargetType.

0042–130 String : String cannot be specified as an attribute for this operation

Explanation: You have specified an attribute that cannot be used for this requested operation.
User response: Try the operation again, without using the attribute you specified.

0042–131 String : the String attribute conflicts with String one or the other may be specified, but not both
Explanation: You have specified two or more attributes that conflict with each other.
User response: Try the operation again, using only one of the attributes.

0042–132 String : String cannot be specified as a value for String for this operation
Explanation: You have specified a value for an attribute assignment that is invalid in the context in which the
operation is being performed.
User response: Try the operation again, using a different value for the attribute assignment.

0042–133 String : unable to remove the String at location String

Explanation: The physical entity that is represented by the NIM resource object you have requested to be deleted
could not be deleted.
User response: Delete the file or directory, using the rm command.

16 Message Center Reference

0042–134 String : unable to initiate network boot on String
Explanation: The operation you requested requires the designated target to reboot using a network boot image. NIM
has automatically initialized the environment to enable the target to do this; however, NIM was unable to force the
target to load the network boot image.
User response: Intervention at the target is required. Follow the procedures for initiating a BOOTP request.

0042–135 String : unable to perform the requested operation because String is currently controlled by the
machine String . It may be necessary to deallocate resources from the target before performing
the intended operation.
Explanation: To synchronize NIM operations that can be initiated from a client or on the master, NIM keeps track of
which machine (the client or the master) is used to allocate the first resource to the client; this machine is said to be in
control. For example, if the first resource allocation occurs from the client, then the client is in control. Once a machine
has control, it remains in control until all resources for that client have been deallocated. You have requested an
operation to be performed from a machine that is currently not in control of the specified target.
User response: Perform the desired operation from the machine that is in control of the target, or from the
controlling machine deallocate the resources (to remove the control), or override this behavior by using the force (-F
flag) option when performing the operation from the master.

0042–136 String : there is no NIM route from the String network to the machine String
Explanation: The requested operation cannot be performed because a NIM route does not exist between two
machines that participate in this operation.
User response: Establish a NIM route between the networks.

0042–137 String : the /etc/niminfo file is missing some required environment varibles
Explanation: The /etc/niminfo file contains information about the NIM environment that all NIM commands require.
In this case, the /etc/niminfo file is missing some information that is required to continue, which indicates that the file
has been corrupted.
User response: Reinitialize the NIM environment.

0042–138 String : unable to update the rhost file with String hostname
Explanation: Unable to update the rhost file.
User response: Edit the $HOME/.rhosts file for root on the client machine to add an entry for the host name of the
NIM master.

0042–139 String : the resource String is served by String and cannot be used to install String
Explanation: The process of installing a machine prevents any attached disks from being used as the source for
installable images. You have allocated a resource to the target of the install operation that is served by the target itself.
User response: Deallocate the resource, allocate another resource of this type that is served by another machine,
and try the operation again.

0042–140 String : unable to remove the /etc/niminfo file on String

Explanation: You have requested that a machine object be removed from the NIM environment and this has been
done; however, NIM was unable to remove the /etc/niminfo file on the machine that has been removed from the NIM
environment.
User response: Remove the /etc/niminfo file from the machine that was removed from the NIM environment.

Note: Verify that the .rhost permissions for the master have been removed from the client.

Chapter 1. Message Component 0042 17

0042–141 String : unable to remove the String attribute because String does not have one
Explanation: By specifying an attribute assignment with a NULL value, you have requested NIM to remove the
specified attr. However, in this case, the specified attr is not currently part of the specified object’s definition.
User response: Try the operation again, using an attribute that is part of the object’s definition.

0042–142 String : unable to add the String attribute because attribute values must be unique and String
already exists with the same value
Explanation: All attribute values must be unique. You have specified a value in an attribute assignment that already
exists.
User response: Try the operation again, using a unique value for the attribute.

0042–143 String : only one String attribute can be specified for an object and one already exists for String
Explanation: Some NIM attributes can only be added to an object’s definition once. In this case, you have specified
an attribute of this type when one already exists for the specified object.
User response: Only one attribute of this type can be used in the object’s definition. Perform the change operation
on the object if you want to replace the current value with a new one.

0042–144 String : sequence numbers must be unique and is already being used with the String attribute
Explanation: Some NIM attributes require a unique sequence number so that NIM can distinguish between multiple
attributes of that type. In this case, you have specified a sequence number that is already being used.
User response: Try the operation again, using a sequence number that is not currently being used. To display the
sequence number that are being used, enter:
lsnim -a AttributeName ObjectName

0042–145 String : String is not a valid attribute name

Explanation: You have specified an attribute that does not exist in the NIM environment.
User response: Try the operation again, using a valid NIM attribute. To display a list of valid attribute names, enter:
lsnim -p -s info_subclass

0042–146 String : String is not a valid type

Explanation: You have specified an object type that does not exist in the NIM environment.
User response: Try the operation again, using a valid NIM object type. On the NIM master, the lsnim command can
be used to display the valid NIM object types.

0042–147 String : this command may not be executed on a NIM master

Explanation: You have attempted to execute a NIM command on the NIM master that can only be executed on NIM
clients.
User response: Execute the command on a NIM client.

0042–148 String : invalid information in String for the String object

Explanation: The information contained in the specified attribute is no longer valid.
User response: Change the information in the attribute to reflect valid information and try the operation again.

18 Message Center Reference

0042–150 String : the file String has a vfstype of String . This conflicts with the expected vfstype, which is
one of the following: t String
Explanation: Any directory used to store NIM resources must be local to the machine that serves those resources.
This is required because NIM can only NFS export local directories. In this case, you have specified a directory that is
not local to the designated server of the directory. NIM has obtained this information from the file system of the
designated server and the vfstype listed corresponds to values in the /usr/include/sys/vmount.h file.
User response: Either copy the desired resources onto the designated server and perform the operation again, or
specify the correct server when performing the operation.

0042–151 String : the file String has a file type of String . This conflicts with the expected type of String .
Explanation: For NIM to use a file, it must be of a specific type. In this case, you have specified a file whose type
cannot be used by NIM. NIM has obtained this information from the file system of the designated server of the file and
the file type corresponds to values in the /usr/include/sys/mode.h file.
User response: Change the file type of the file and try the operation again.

0042–152 String : an error occurred while performing root sync operations on the following clients:
Explanation: When an installp operation is performed on a SPOT, the root directories of all diskless and dataless
clients that use that SPOT must be synchronized with the changes made within the SPOT. In this case, one or more
errors occurred when performing the root sync operation on a root directory.
User response: Investigate why some of the root syncs failed and perform the operation again. The nim.installp log
for the client root is located in RootResrcParentDir/ClientName/var/adm/ras.

0042–153 String : the file String has file permissions of String . This conflicts with the expected permissions
of String .
Explanation: For NIM to use a file, it must have specific file permissions. In this case, you have specified a file
whose permissions conflict with those required by NIM. NIM has obtained this information from the file system of the
designated server of the file, and the value of the file permissions comes from the /usr/include/sys/mode.h file.
User response: Change the file permissions of the file and try the operation again.

0042–154 String : the file or directory String does not exist

Explanation: For NIM to use a file, it must exist. You have specified a file that does not exist.
User response: Create the file and try the operation again.

0042–155 String : unable to perform requested operation because the server of the root resource must be
the same as the server of the spot resource and your request violates this requirement.
Explanation: For NIM to keep diskless and dataless root directories in sync with their corresponding SPOTs, NIM
requires that the client’s root directory be served from the same machine as its SPOT. In this case, you have
requested a resource to be allocated that violates that requirement.
User response: Try the operation again using resources that do not violate the NIM requirement.

0042–156 String : there is no String at location String

Explanation: You have requested an operation to be performed that involves a directory that does not exist.
User response: Create the missing directory and try the operation again.

0042–157 String : unable to access the String file

Explanation: The operation you have requested could not be performed because a required file could not be
accessed.
User response: Create the missing file and try the operation again. For example:

Chapter 1. Message Component 0042 19

v If the missing file is a boot image with a name whose format is SpotName.NetworkInterface.Platform (for example,
myspot.tok.up), recreate the boot image by performing the check operation on the SPOT.
v If the missing files are directories with which root or paging resources are associated, delete the resource definition
with the remove operation, create the directories, and then redefine the resource.
v If a SPOT’s image.template file is missing, this indicates that the SPOT has been corrupted or was not constructed
successfully. To recover, you may need to remove and rebuild the SPOT with the remove and define operations.

0042–158 String : unable to modify the String file

Explanation: The operation you have requested requires NIM to modify a file that it was unable to modify
successfully.
User response: Check the file permissions on the file and try the operation again.

0042–159 String : String is missing one or more of the following options: String
Explanation: Required software is missing which prevents the target machine from acting as a SPOT server.
User response: Install the missing software and retry the operation.

0042–160 String : unable to create any type of network boot image

Explanation: The operation you requested requires the construction of network boot images and NIM was unable to
do that.
User response: Fix the problem that prevented the network boot images from being constructed and try the
operation again.

0042–161 String : there is insufficient free disk space in String to complete the requested operation; data
follows: required = String tavailable = String
Explanation: There is insufficient free disk space to complete the requested operation.
User response: Increase the amount of available space, as detailed in the error message.

0042–162 String : an lpp_source which has the simages attribute is required for this operation
Explanation: To perform the requested operation, NIM requires an lpp_source type resource object that has the
simages attribute as part of its definition. This attribute is used to designate that an lpp_source contains the total set
of optional packages that are required to support NIM install operations. In this case, you have not supplied an
lpp_source that fulfills this requirement.
User response: Try the operation again using an lpp_source that has the simages attribute in its definition.

0042–163 String : machine String serves a resource which is being allocated, however, NIM is unable to
determine which interface on this machine should be used by the client because this machine is
also functioning as the gateway between the String and String networks.
Explanation: NIM coordinates access between a client and the server of the resource. To do this, NIM must identify
a network interface that can be used by the client. This becomes a complex problem when the server has more than
one network interface. NIM uses a connectivity algorithm to establish which network interface to use. This error
message occurred because the connectivity algorithm detected a problem with the client’s routing and the interface the
algorithm has selected to use. NIM does not allow the interface on the server that the client uses as a gateway to be
used to serve resources because the operation requiring the resource could fail.
User response: If the server has other network interfaces that are not known to NIM, change the server machine
object to add the interfaces.
Define a NIM route between the client’s primary network and one of the other networks to which the server connects.

20 Message Center Reference

0042–164 String : String cannot be used as a source for installable images in this context because it is a
CDROM.
Explanation: Some NIM operations do not allow the source of installable images to be a CD-ROM. NIM is not
always able to construct an environment that supports the use of a CD-ROM for the operation being performed. This
is true for the operation you tried to perform.
User response: Try the operation again using a different source for installable images.

0042–165 String : String cannot be associated with the type of network referenced by the String attribute
Explanation: Some attributes can only be specified together; others are mutually exclusive. In this case, you
specified one or more attributes that conflict.
User response: Try the operation again, omitting the attribute that was in conflict. For example, the ring_speed and
cable_type attributes cannot be used with the same if attribute; the one you should use depends on the type of
network interface referenced by the corresponding if attribute.

0042–166 String : String requires a corresponding String attribute

Explanation: The if attribute specifies network interface information, which includes a reference to the network object
that the interface connects to. In this case, you have omitted a required attribute which is associated with the if
attribute.
User response: Try the operation again, including the required attribute. For example, the ring_speed attribute
corresponds with the Token-Ring network interface, and the cable_type attribute corresponds with the Ethernet
network interface.

0042–167 String : String does not contain a valid IPL ROM emulation image
Explanation: The device which you have specified as the source for the IPL ROM emulation, does not contain a
valid, bootable image of the IPL ROM emulation.
User response: If the specified device has media in it, this media either does not contain the IPL ROM emulation, or
the media has been corrupted. Remake the IPL ROM emulation, and try the operation again. If the specified device
has no media in it, make the IPL ROM emulation, put it in the device, and try the operation again.

0042–168 String : the destination network ( String ) specified in String is the same as the originating network
Explanation: You have specified that the originating and destination network are the same. Machines that are on the
same network do not need routing to communicate; therefore, adding a route from a network to itself is not allowed.
User response: Specify a different originating and destination network when adding a NIM route.

0042–169 String : you have allocated an lpp_source, but have not specified which filesets are to be
installed using that lpp_source
Explanation: You have allocated an lpp_source, but you have not specified which filesets are to be installed using
that lpp_source.
User response: Specify the filesets to install using the filesets attribute in the command, or by allocating an
installp_bundle that contains a list of the filesets to install.

0042–170 String : String is not a valid platform type

Explanation: You entered a platform type that is not known to NIM.
User response: The valid platform types are rs6k, rs6ksmp, and rspc. Correct the platform type attribute and try
the operation again.

Chapter 1. Message Component 0042 21

0042–171 String : the String configuration type is not supported for the String platform type
Explanation: Not all platform types are supported on all configuration types. For example, the diskless configuration
type is not supported on the platform type rs6ksmp.
User response: Use the correct platform type and try the operation again.

0042–172 String : This machine’s CPU ID does not match the CPU ID stored in the NIM database.
Explanation: You have specified the incorrect name of the machine object for the NIM client machine. When the
niminit command is used to rebuild the niminfo file, the master registration process checks the CPU ID of the
machine with the value stored in the NIM database for the named machine. If the stored value does not match the
value passed by niminit, this message is issued.
User response: Use the correct name and try the command again.

0042–173 String : X cannot be specified as a value for installp_flags when the auto_expand attribute has a
value of no .
Explanation: You specified that the installp command should expand file systems (using the -X flag) while
specifying that NIM should not auto expand (using the auto_expand attribute). This is not an allowable combination
for the command invoked.
User response: Use either the -X flag or the auto_expand attribute, but not both.

0042–174 String : The String attribute may only be assigned a value of yes or no .
Explanation: You specified an invalid value for an attribute whose only valid values are yes and no.
User response: Retry the operation with a value of yes or no for the attribute indicated.

0042–175 String : An unexpected result was returned by the String command: String
Explanation: An unexpected result has been returned from a command that NIM tried to execute.
User response: Fix the problem that caused the executed command to fail and try the operation again.
If the command failed due to a shortage of space, its error messages indicating this should be displayed. Expand the
indicated file system, (for most NIM operations use the auto_expand attribute) and retry the operation. If a space
failure occurred during SPOT creation, and if the bosboot command failed to make boot images as a result, increase
the free space and run the check operation.
If the command listed by NIM in this message is the installp command, check the nim.installp log for failure and
recovery information. (For standalone client operations, this is located in the /var/adm/ras directory of the client. For
SPOT cust and maintoperations, this is located in SPOTParentDir/SPOTName/usr/lpp/bos/inst_root/var/adm/ras on
the SPOT. For diskless and dataless clients, this is located in RootResrcParentDir/ClientName/var/adm/ras.

0042–176 String : The resource located in String cannot serve as a support images (or simages ) lpp_source
because one or more of the following filesets are missing: String
Explanation: The resource cannot serve as a support image (simages)lpp_source. When an lpp_source serves as
a support image resource, it contains a minimal set of software packages for facilitating installation and the use of the
base operating system.
User response: No action is necessary if this resource does not need to serve as a support images lpp_source. If
the resource needs to be a support images lpp_source, add the missing software to the lpp_source. If the
lpp_source is a directory, you can do this by copying the missing packages to the location of the lpp_source and
running the check operation.

22 Message Center Reference

0042–177 String : There is insufficient free disk space in String to complete the requested operation; data
follows: (All sizes displayed are in 512-byte blocks.) required = String tavailable = String
Explanation: The operation you requested could not be completed due to insufficient free space in one or more file
systems.
User response: Make more space available if possible, by extending the file system displayed. For most NIM
operations, the auto_expand attribute is available to automatically expand file systems.

0042–178 String : the logical device name of the network adapter must be supplied when connecting to the
String network because that network is composed of more than one network interface type.
Explanation: The if attribute is made up of four fields. The fourth field is optional in most cases. In this case. the
network object that you specified (in field one) has more than one type of network. In this case, NIM requires that the
fourth field has a value that specifies the logical device name of the network adapter.
User response: Add the appropriate value to the if attribute, and try the operation again.

0042–179 String : the network type specified by the String attribute cannot be removed because it is
currently being used by one or more clients which are attached to the String network.
Explanation: You are attempting to remove an if or other_net_type attribute on which one or more NIM clients have
a dependency.
User response: If this is not a mistake, remove the NIM clients that are dependent on the network, or remove the if
attribute from the NIM client object definition.

0042–180 String : The ip address String does not belong to the network String which is represented by the
nim object String .
Explanation: The address of the machine that is being defined is not connected to the network that is represented
by the specified network object.
User response: Define a network object that represents the physical network to which the machine is connected.
Use this network object when defining the machine.

0042–181 String : The fix_query_flags attribute has an illegal value. Use lsnim -Pa fix_query_flags for a list
of legal values.
Explanation: The fix_query_flags attribute has an illegal value. Use lsnim -Pa fix_query_flags for a list of legal
values.
User response: Determine the correct flags and retry the operation.

0042–182 String : A resource of type String cannot be allocated for the current operation at the same time
as a resource of type String . Allocate one or the other but not both.
Explanation: A resource of one type cannot be allocated for the current operation at the same time as a resource of
another type. Allocate one or the other, but not both.
User response: The resources specified are mutually exclusive. Determine which one is needed for the operation,
and omit the other.

0042–183 String : The String attribute cannot be specified for the current operation when a resource of type
String is allocated. Use one or the other but not both.
Explanation: An attribute cannot be specified for the current operation when a type of resource is allocated. Use one
or the other, but not both.
User response: The attribute and the resource specified are mutually exclusive. Determine which one is needed for
the operation, and omit the other.

Chapter 1. Message Component 0042 23

0042–184 String : The network address (net_addr) or subnet mask (snm) cannot be changed for network
String because NIM clients are currently defined as being connected to that network. Remove the
client definitions before changing the network.
Explanation: The network address (net_addr) or subnet mask (snm) cannot be changed for the network, because
NIM clients are currently defined as being connected to that network. Remove the client definitions before changing
the network.
User response: The nimdef command can be used to quickly redefine NIM clients after they have been removed to
update the network definition.

0042–185 String : Failed to link or copy String to String Check permissions and filesystem space
Explanation: Failed to link or copy files. Check permissions and file system space.
User response: Verify that space and inodes are available for the files and links specified in the error message.

0042–186 String : Failed to copy setup programs to String Either start NFS on String or free 1000 512-byte
blocks in the String filesystem.
Explanation: Failed to copy setup programs. Either start NFS on the client or free 1000 512-byte blocks in the file
system.
User response: Programs required to set up the operation could not be copied to the client system. Either start NFS
on the client, or increase space in the file system specified in the error message.

0042–187 String : Failed to expand filesystem String on String

Explanation: Failed to expand file system.
User response: Attempt to manually expand the file system specified in the error message, then retry the operation.

0042–188 String : Failed to NFS mount String on String

Explanation: Failed to NFS mount.
User response: Verify that NFS is running on both the resource server and the client specified in the error message.
Retry the operation when the NFS problems have been resolved.

0042–189 String : Failed saving existing boot image. Check space in the String filesystem.
Explanation: Failed saving existing boot image. Check space in the file system.
User response: Increase space in the file system specified by the error message, and retry the operation.

0042–190 String : The key is NOT in the NORMAL position. Unattended installtion cannot complete unless
the key is in the NORMAL position.
Explanation: The key is not in the NORMAL position. Unattended installation cannot complete unless the key is in
the NORMAL position.
User response: Turn the key on the client machine to the NORMAL position and retry the operation.

0042–191 String : Unable to write the IPLROM emulation to String

Explanation: Unable to write the IPLROM emulation.
User response: The mkboot command failed to write the IPLROM emulation on the client. Boot the client manually
over the network to begin the BOS installation.

24 Message Center Reference

0042–192 String : Unable to find boot logical volume String
Explanation: Unable to find boot logical volume.
User response: Verify that a boot logical volume is defined for the machine. NIM attempts to use the lslv -l hd5
command to determine the boot logical volume.

0042–193 String : String has no entry for String in .rhosts or cannot resolve host id
Explanation: The client does not have an .rhosts entry for the master, or the client host ID is not resolvable.
User response: Verify that the client host name is resolvable by the master. Then verify that an entry exists for the
master in the $HOME/.rhosts file for root on the client machine.

0042–194 String : String does not allow NIM push operations. Remove /etc/nimstop on String if push
operation is necessary.
Explanation: The client does not allow NIM push operations. Remove /etc/nimstop on %s if push operation is
necessary.
User response: On the client machine, run the nimclient -p command to re-enable master push permissions.

0042–195 String : Unable to order boot device list on String

Explanation: Unable to order boot device list.
User response: An error was returned by the bootlist command on the client. If a network boot must be performed
for a bos_inst, diag, or maint_boot operation, manually set the boot list and reboot the client, or follow the normal
procedure to boot the client over the network.

0042–196 String : The set_bootlist attribute is only valid when used in combination with the no_client_boot
or boot_client attributes.
Explanation: The set_bootlist attribute is only valid when used in combination with the no_client_boot or
boot_client attributes.
User response: Only specify the set_bootlist attribute to the nim command when changing the default behavior
with the no_client_boot or boot_client attributes.

0042–197 String : The network adapter’s logical device name must be specified in the if1 attribute of the
target machine’s NIM definition when using the force_push attribute if the target machine has
more than one interface for a given network type. Add one of the following to the if1 attribute of
the target’s NIM definition: String
Explanation: If the target machine has more than one interface for a given network type, the network adapter’s
logical device name must be specified in the if1 attribute of the target machine’s NIM definition when using the
force_push attribute.
User response: Modify the client’s if1 attribute using the NIM change operation. Change the if1 attribute to include
one of the client’s network adapter logical device names listed in the error message.

0042–198 String : When converting a machine’s /usr filesystem to a SPOT the bos image on the media
(lpp_source) being used to create the SPOT must match the bos image that was used to install
the machine. The machine was installed with bos.rte String . The package on the installation
media contains bos.rte String .
Explanation: When converting a machine’s /usr file system to a SPOT, the bos image on the media (lpp_source)
being used to create the SPOT must match the bos image that was used to install the machine.
User response: When defining the /usr SPOT, use the same installation media that was used to install the machine
originally. For example, if a machine was originally installed with AIX 4.3.2 and then updates were applied to bring the
machine to AIX 4.3.3, the installation media that should be used when defining the /usr SPOT on the machine would
still need to be the AIX 4.3.2 product media.

Chapter 1. Message Component 0042 25

0042–199 String : The no_client_boot and boot_client attributes may not be specified together.
Explanation: The no_client_boot and boot_client attributes may not be specified together.
User response: To avoid the possibility of giving conflicting instructions to the NIM command, do not supply both the
no_client_boot and boot_client attributes in the same NIM operation.

0042–204 String : The mk_image and source attributes are only valid when specified together.
Explanation: The mk_image and source attributes are only valid when specified together.
User response: When creating a mksysb resource from a running client machine, use the mk_image=yes attribute
to indicate that a mksysb should be created, and use the source=ClientName attribute to specify the name of the
client that is to be backed up.

0042–205 String : The bos.sysmgt.sysbr fileset must be installed on String to perform the system backup.
You may install this fileset with the NIM cust operation.
Explanation: The bos.sysmgt.sysbr fileset must be installed on the client to perform the system backup. You may
install this fileset with the NIM cust operation.
User response: Install the bos.sysmgt.sysbr fileset on the client machine before retrying the operation.

0042–206 String : There is already a String resource allocated to String .

Explanation: There is already a resource allocated.
User response: Only one resource of the type specified can be allocated to the client. Deallocate the first resource
before attempting to allocate the other.

0042–207 String : Unable to allocate the String resource to String .

Explanation: Unable to allocate a resource to a client.
User response: Look for other NIM error messages that may accompany this error and which may provide more
information about the problem. Verify that the resource specified is NFS-exportable to the client.

0042–208 String : Unable to lock String . This could mean that the client is already locked, or that the name
given does not refer to a valid NIM client.
Explanation: Unable to lock a client. This could mean that the client is already locked, or the name given does not
refer to a valid NIM client.
User response: If another NIM operation is being performed on the same client, wait for the process to complete
before retrying the operation. If no other NIM operations are being performed, stop and restart the nimesis daemon to
remove locks.

0042–209 String : The mksysb_flags attribute contains an illegal value. Use lsnim -Pa mksysb_flags for a
list of legal values.
Explanation: The mksysb_flags attribute contains an illegal value. Use the lsnim -Pa mksysb_flags command to
get a list of legal values.
User response: Specify the correct values for the mksysb_flags attribute, and retry the operation.

0042–210 String : The maximum space required for the backup is greater than the amount of free space in
the target filesystem. To ignore space requirements use the -F flag when defining the mksysb
resource.
Explanation: The maximum space required for the backup is greater than the amount of free space in the target file
system. To ignore space requirements, use the -F flag when defining the mksysb resource.
User response: Either increase the space of the target file system where the mksysb is to be created, or use the -F
flag as specified in the error message.

26 Message Center Reference

0042–211 String : The member String already exists in group String .
Explanation: The member already exists in the group.
User response: No additional action is required, because the member is already added to the group.

0042–212 String : The member named String was not added to the String group, because it is not a valid NIM
name.
Explanation: The member was not added to the group, because it is not a valid NIM name.
User response: The name of a member to add to a group was invalid. Verify that the member was specified
correctly.

0042–213 String : The group String was not created because it did not contain any valid members.
Explanation: The group was not created, because it did not contain any valid members.
User response: A group must contain at least one member. Redefine the group with valid members to add it to the
NIM environment.

0042–214 String : Unable to add String as a member of group String

Explanation: Unable to add a member to a group.
User response: Look for other NIM error messages that may accompany this error and which may provide more
information about the problem.

0042–215 String : String is an invalid log type for the showlog operation. Valid types are: String
Explanation: An invalid log type for the showlog operation was specified.
User response: Specify one of the valid log types listed in the error message.

0042–216 String : String is an invalid log type for SPOTs. Valid types are: String
Explanation: An invalid log type for the showlog operation was specified for a SPOT.
User response: Specify one of the valid log types listed in the error message.

0042–217 String : String is an invalid log type for diskless and dataless machines. Valid types are: String
Explanation: An invalid log type for the showlog operation was specified for a diskless or dataless machine.
User response: Specify one of the valid log types listed in the error message.

0042–218 String : The log file is either empty or does not exist at String
Explanation: The log file is either empty or does not exist.
User response: No information is available in the log file for the machine or SPOT specified.

0042–219 String : The object String is incompatible with the group String .
Explanation: The object is incompatible with the group.
User response: The object cannot be added to the group, because its type is not allowed in the group. Machine
groups can only contain one type of NIM client, and that type is determined by the first member added. Resource
groups can only contain members whose types are resources.

Chapter 1. Message Component 0042 27

0042–220 String : You cannot have more than one resource of type String in a resource group.
Explanation: You cannot have more than one resource of the specified type in a resource group.
User response: You must remove the current member with the specified type from the resource group before the
new member with the same type can be added.

0042–221 String : The group String is being removed because its single remaining member was removed
during this operation.
Explanation: The group GroupName is being removed, because its single remaining member was removed during this
operation.
User response: A group cannot be empty. Redefine the group with at least one member if it should remain in the
NIM environment.

0042–222 String : An unknown error occurred allocating resources to the machine String in the method:
String .
Explanation: An unknown error occurred allocating resources to the machine.
User response: Look for other NIM error messages that may accompany this error and which may provide more
information about the problem. Verify that the resource specified is NFS-exportable to the client.

0042–223 String : Invalid input file: String The file either cannot be read, is empty, or contains no valid
entries.
Explanation: Invalid input file. The file either cannot be read, is empty, or contains no valid entries.
User response: Verify that the file specified in the error message is the correct file for the operation.

0042–224 String : The limit on the length of a line (Number bytes) in a NFS exports file was exceeded in the
file String The export operation cannot be performed.
Explanation: The limit on the length of a line in an NFS exports file was exceeded. The export operation cannot be
performed.
User response: Manually edit the /etc/exports and /etc/xtab files to remove any obsolete entries. The number of
hosts to which NIM can NFS-export a resource can also be increased by setting the restrict_nfs_exports attribute to
no on the master by running the nim -o change -a restrict_nfs_exports=no master command.

0042–225 String : An error occurred while updating the exports file String . Check for corruption in the file.
Explanation: An error occurred while updating the exports file. Check for corruption in the file.
User response: Manually edit the /etc/exports and /etc/xtab files to fix any file corruption problems. Attempt to
determine why NIM was unable to successfully update the files. Check file and directory permissions, and verify that
file systems are not full.

0042–226 String : A time-out occurred while attempting to initiate the String operation on the client. The
operation may not have started successfully.
Explanation: A timeout occurred while attempting to initiate the operation on the client. The operation may not have
started successfully.
User response: If the operation that was performed was bos_inst, the client only needs to be rebooted manually
over the network to begin the installation. For all other operations, the problem is most likely due to network
communication problems between the master and the client. Verify that the client is reachable by the master and that
rsh permission is still granted by the client to the master.

28 Message Center Reference

0042–227 String : The state of String indicates that the machine may not be ready for certain NIM
operations: String
Explanation: The state of the machine indicates that it may not be ready for certain NIM operations.
User response: Check to see if any NIM operations are still being performed on the machine. If not, reset the state
of the machine with the nim -Fo resetMachineName command. This returns the machine to the ready state so NIM
operations can be performed on it. The reset operation does not deallocate resources, so deallocate resources if
necessary using the nim deallocate operation.

0042–228 String : invalid release level of String . String . String for String
Explanation: Invalid release level.
User response: The release level of the resource is incomplete, or incorrectly specified. The level of the resource
can be obtained by running the lsnim -l ResourceName command and viewing the version, release, and mod
attributes. To correct the problem, either recreate the resource, or modify the NIM database to contain the correct level
using the command on the NIM master:/usr/lpp/bos.sysmgt/nim/methods/m_chattr -aAttribute=Value
ResourceName, where Attribute is version, release, or mod; Value is the correct value; and ResourceName is the
name of the resource with the incorrect level specification.

0042–229 String : When installing a system using a mksysb as the source for the installation, the level of
the SPOT used for the installation must match the level of the mksysb image that is being
installed. The release levels of the SPOT, String , and the mksysb, String , do not match.
Explanation: When installing a system using a mksysb as the source for the installation, the level of the SPOT used
for the installation must match the level of the mksysb image being installed. The release levels of the SPOT and the
mksysb do not match.
User response: Create a SPOT that matches the level of the mksysb being installed, and use that SPOT when
performing a mksysb BOS installation. The level of mksysb and SPOT resources can be obtained by running the
lsnim -l ResourceName command and viewing the version, release, and mod attributes.

0042–230 String : When installing a system using a mksysb as the source for the installation, the level of
the SPOT used for the installation should match the level of the mksysb image that is being
installed. If this convention is not followed, the installation may not complete successfully.
Explanation: When installing a system using a mksysb as the source for the installation, the level of the SPOT used
for the installation should match the level of the mksysb image being installed. If this convention is not followed, the
installation may not complete successfully.
User response: Create a SPOT that matches the level of the mksysb being installed, and use that SPOT when
performing a mksysb BOS installation. The level of mksysb and SPOT resources can be obtained by running the
lsnim -l ResourceName command and viewing the version, release, and mod attributes.

0042–231 String : Unable to generate the formatted list of software to install.

Explanation: A temporary list of software that should be installed is created and used for this operation. The list
could not be created.
User response: Check previous error messages to understand why the error occurred. Correct the problem and try
the operation again.

0042–232 String : Unable to create the temporary INSTALLP_BUNDLE resource needed to perform this
operation.
Explanation: A temporary installp_bundle resource is created and used for this operation. The temporary resource
could not be created.
User response: Check previous error messages to understand why the creation of the resource failed. Correct the
problem and try the operation again.

Chapter 1. Message Component 0042 29

0042–233 String : The NIM Master is already initialized. You must unconfigure the NIM Master before you
can perform this operation.
Explanation: The operation cannot be performed because the NIM Master is already initialized.
User response: Unconfigure the NIM Master and try the operation again.

0042–234 String : You can not restore a NIM database backup onto a machine that has an earlier level of
the NIM master fileset installed.
Explanation: You cannot restore a NIM database backup onto a machine that has an earlier level of the NIM master
fileset installed. For example, a NIM database backup of a system with level 4.2.0.0 of the NIM master cannot be
restored to a system that has a level of the NIM master lower than 4.2.0.0.
User response: Install a level of the NIM master fileset that is at the same level or a later level than that from which
the backup was created. Then attempt to restore the NIM database backup.

0042–235 String : You must specify an image source for SPOT creation.
Explanation: An image source was not specified for creating the SPOT.
User response: Specify a device containing installation images or specify an lpp_source with the simages attribute
for creating the SPOT.

0042–236 String : A name and/or directory specification is missing for the LPP_SOURCE.
Explanation: A name for the lpp_source or a directory to contain the lpp_source was not specified for the
lpp_source that will be created.
User response: Specify a name and a directory for the lpp_source and try the operation again.

0042–237 String : A name and/or directory specification is missing for the SPOT.
Explanation: A name for the SPOT and/or a directory to contain the SPOT was not specified for the SPOT that will
be created.
User response: Specify a name and a directory for the SPOT and try the operation again.

0042–238 String : A directory specification is missing for the Diskless/ Dataless machine resources.
Explanation: A parent directory was not specified for the diskless and dataless machine resources that will be
created.
User response: Specify a directory for the diskless/dataless machine resources and try the operation again.

0042–239 String : You must specify both a name and a directory for the String resource to create it.
Explanation: A name for the resource and/or directory to contain the resource was not specified for the resource that
will be created.
User response: Specify a name and a directory for the resource and try the operation again.

0042–240 String : You must specify a directory for the diskless and dataless machine resources to create
them.
Explanation: A parent directory was not specified for the diskless and dataless machine resources that will be
created.
User response: Specify a directory for the diskless/dataless machine resources and try the operation again.

30 Message Center Reference

0042–241 String : You must specify both a size and a volume group if you want to create a new filesystem
for the String resource.
Explanation: The size and/or volume group was not specified for the creation of a new file system to contain a NIM
resource.
User response: Specify both the size and volume group for the file system and try the operation again.

0042–242 String : You must specify both a size and a volume group if you want to create a new filesystem
for the diskless and dataless machine resources.
Explanation: The size and/or volume group was not specified for the creation of a new file system to contain
diskless and dataless machine resources.
User response: Specify both the size and volume group for the file system and try the operation again.

0042–243 String : **** You can not create the same filesystem for the LPP_SOURCE and the SPOT. Please
specify different directory names for these resources.
Explanation: An attempt was made to create the same file system twice: once for an lpp_source and once for a
SPOT.
User response: Specify a different directory for either the lpp_source or the SPOT. This will cause different file
systems to be created for the resources. If a new file system really should be created to contain both resources, then
only specify that the file system should be created for one of the resources, but specify the same directory for both
resources.

0042–244 String : **** You can not create the same filesystem for the LPP_SOURCE and the
Diskless/Dataless resources. Please specify different directory names for these resources.
Explanation: An attempt was made to create the same file system twice: once for an lpp_source and once for
diskless/dataless machine resources.
User response: Specify a different directory for either the lpp_source or the diskless/dataless resources. This will
cause different file systems to be created for the resources. If a new file system really should be created to contain
both sets of resources, then only specify that the file system should be created for one of the resources, but specify
the same directory for both resources.

0042–245 String : **** You can not create the same filesystem for the SPOT and the Diskless/Dataless
resources. Please specify different directory names for these resources.
Explanation: An attempt was made to create the same file system twice: once for a SPOT and once for
diskless/dataless machine resources.
User response: Specify a different directory for either the SPOT or the diskless/dataless resources. This will cause
different file systems to be created for the resources. If a new file system really should be created to contain both sets
of resources, then only specify that the file system should be created for one of the resources, but specify the same
directory for both resources.

0042–246 String : Not enough space on String . Try specifying different volume groups for the filesystems
that you are creating.
Explanation: Not enough space on the volume group to create the specified file system.
User response: Specify a different volume group for the file system to be created and try the operation again.

0042–247 String : Creation of the String filesystem failed.

Explanation: Creation of the file system failed.
User response: Check the previous output for error messages to understand what caused the file system creation to
fail. Correct the error and try the operation again.

Chapter 1. Message Component 0042 31

0042–248 String : An error occurred during filesystem creation. Please correct the problem and try again.
Explanation: An error occurred during file system creation.
User response: Check the previous output for error messages to understand what caused the file system creation to
fail. Correct the error and try the operation again.

0042–249 String : NIM Master initialization failed.

Explanation: NIM master initialization failed.
User response: Check the previous output for error messages to understand what caused the configuration of the
NIM master to fail. Correct the error and attempt to reinitialize the master. The most frequent cause of this failure is
that the master is already initialized. The master can be unconfigured with the nim -o unconfig master command and
reinitialized. However, this should be done with extreme caution, since unconfiguring the master will remove all
definitions from the NIM database.

0042–250 String : Unable to continue with the configuration.

Explanation: Unable to continue with configuration.
User response: Check the previous output for error messages to understand what caused the configuration to fail.
Correct the error and attempt to configure the system again from the point of failure.

0042–251 String : A route cannot be added to String because a required default route for String is missing.
Add a default route to String and try this operation again.
Explanation: A route cannot be added to the network, because a required default route is missing. Add a default
route to the network, and try this operation again.
User response: Add a default route to the network specified in the error message, and retry the operation.

0042–252 String : Unable to locate a matching network for String

Explanation: Unable to locate a matching network.
User response: The find_net keyword was used in the if attribute of the machine. However, no matching network
was found. Either define the network prior to defining the machine interface, or use the net_definition attribute in
conjunction with the find_net keyword to define the network while the interface is being defined.

0042–253 String : You cannot use the net_definition attribute when the find_net keyword is not specified as
the first field of the if attribute. You specified String instead of find_net
Explanation: You cannot use the net_definition attribute when the find_net keyword is not specified as the first
field of the if attribute.
User response: The net_definition attribute is invalid when using a known network in the if attribute. Specify the
find_net keyword in the if attribute, or omit the net_definition attribute, and retry the operation.

0042–254 String : Invalid format for the specified value of net_definition String The value of the attribute
should be as follows: [ ] [ ] [ ] where: = network type (one of tok, ent, fddi, etc.) = dotted decimal
subnet mask for the network = optional default gateway ip address or hostname used by the
machine being defined to communicate with the master = optional default gateway ip address or
hostname used by the master to communicate with clients on other subnets = optional name to
be given to the NIM definition created for the network. (A unique default name is used otherwise.)
If you wish to specify and if or are not applicable, specify 0 in their place. If is 0, cannot be
non-zero.
Explanation: Invalid format for the specified value of net_definition. The value of the attribute should be as follows:
NetType
Network type (for example, tok, ent, fddi, etc.).

32 Message Center Reference

snmName
Dotted decimal subnet mask for the network.
Client_gwName
Optional default gateway IP address or host name used by the machine being defined to communicate with
the master.
Master_gwName
Optional default gateway IP address or host name used by the master to communicate with clients on other
subnets.
NetName
Optional name given to the NIM definition created for the network. (Otherwise, a unique default name is
used.)

If you want to specify NetName and if Client_gwName or Master_gwName are not applicable, specify 0 in their place.
If Client_gwName is 0, Master_gwName cannot be nonzero.
User response: Correct the syntax error, and retry the operation.

0042–255 String : The master already has a default route and the gateway which you specified as being the
default for the master is different from that which is already defined: String Use the change
operation if you wish to modify the master’s default gateway.
Explanation: The master already has a default route, and the gateway you specified as being the default for the
master is different from that which is already defined. Use the change operation if you want to modify the master’s
default gateway.
User response: To change the default gateway for a network, use the following command:
nim -o change -a routingX="default GtName" NetName

where X is the sequence number for the routing attribute; GtName is the default gateway to use; and NetName is the
name of the master’s network.

0042–256 String : A default route already exists for the network String You may modify the default gateway
but you cannot define more than one default route.
Explanation: A default route already exists for the network. You can modify the default gateway, but you cannot
define more than one default route.
User response: To change the default gateway for a network, use the following command:
nim -o change -a routingX="default GtName" NetName

where X is the sequence number for the routing attribute; GtName is the default gateway to use; and NetName is the
name of the network to modify.

0042–257 String : You cannot specify the net_definition attribute without specifying the if attribute when
changing a machine definition.
Explanation: You cannot specify the net_definition attribute without specifying the if attribute when changing a
machine definition.
User response: The net_definition must reference a machine interface, so specify an if attribute when using the
net_definition attribute.

0042–258 String : You cannot specify the net_definition attribute when creating or modifying more than one
if attribute in the same change operation. Use two separate operations.
Explanation: You cannot specify the net_definition attribute when creating or modifying more than one if attribute in
the same change operation. Use two separate operations.
User response: To avoid ambiguity, manipulate only one machine interface (if attribute) at a time when using the
net_definition attribute.

Chapter 1. Message Component 0042 33

0042–259 String : The value of default_res , specified as String on the master’s database definition, is not a
valid NIM resource group.
Explanation: The value of default_res specified on the master’s database definition is not a valid NIM resource
group.
User response: Specify a valid NIM resource group as the default resource. Obtain a list of resource groups by
running the lsnim -t res_group command.

0042–260 String : The default attribute is only applicable when manipulating a resource group.
Explanation: The default attribute is only applicable when manipulating a resource group.
User response: Setting the default=yes/no attribute on a resource group makes it the default set of resources to
use in NIM operations. The default attribute is invalid when used as an attribute in other NIM operations.

0042–261 String : Illegal use of the async attribute. This attribute may only be specified for the lppchk
operation when the target is a standalone machine or a group of standalone machines.
Explanation: Illegal use of the async attribute. This attribute can only be specified for the lppchk operation when
the target is a standalone machine or a group of standalone machines.
User response: Omit the async attribute when performing the lppchk operation, unless the target is a standalone
machine or a group of standalone machines.

0042–262 String : The filename of the client definition file is missing for this operation.
Explanation: The file name of the client definition file is missing for this operation.
User response: Specify the client definition file that should be used to add machines to the NIM environment.

0042–263 String : The netboot_kernel attribute may only be assigned a value of up or mp .

Explanation: The netboot_kernel attribute can only be assigned a value of up or mp.
User response: Correct the value specified for the netboot_kernel attribute.

0042–264 String : The image source String that was used to define the lpp_source is missing one or more
of the following requested packages: String
Explanation: The image source that was used to define the lpp_source is missing one or more requested
packages.
User response: Installation images were not copied into the lpp_source directory. The source for installation images
may not contain all of the filesets specified to populate the lpp_source. Copy the missing installation images to the
lpp_source directory, and then perform the NIM check operation on the lpp_source.

0042–265 String : The image source String that was used to define the lpp_source is missing one or more
of the following from the list of default packages: String
Explanation: The image source that was used to define the lpp_source is missing one or more items from the list of
default packages.
User response: Installation images were not copied into the lpp_source directory. The source for installation images
may not contain all of the default filesets used to populate the lpp_source. Copy the missing installation images to the
lpp_source directory, and then perform the NIM check operation on the lpp_source.

0042–266 String : The following requested packages are missing from the defined lpp_source: String
Explanation: Requested packages are missing from the defined lpp_source.
User response: Installation images were not copied into the lpp_source directory. The fileset names may have
been specified incorrectly, or the source for installation images may not contain all of the specified filesets. Copy the

34 Message Center Reference

missing installation images to the lpp_source directory, and then perform the NIM check operation on the
lpp_source.

0042–267 String : The defined lpp_source does not have the simages attribute because one or more of the
following packages are missing: String
Explanation: The defined lpp_source does not have the simages attribute, because one or more packages are
missing.
User response: Copy the missing installation images to the lpp_source directory, and perform the NIM check
operation on the lpp_source to add the simages attribute.

0042–268 String : The operation cannot be performed because all members of the target group specified
are currently excluded from operations on the group. You must unmark (or include) excluded
group members before proceeding.
Explanation: The operation cannot be performed, because all members of the target group specified are currently
excluded from operations on the group. You must unmark (or include) excluded group members before proceeding.
User response: Perform the NIM select operation on the group to include members in further operations.

0042–269 String : Only one verification mode may be specified for this operation.
Explanation: Only one type of verification can be performed at a time when verifying installed filesets on a NIM
client.
User response: Disable or deselect all but one verification option and try the operation again.

0042–270 String : The String operation is only supported on SPOTs and NIM clients installed with a version
and release level of 4.2 or greater.
Explanation: The operation is only supported on SPOTs and NIM clients installed with a version and release level of
AIX 4.2 or greater.
User response: The NIM client fileset on the target is at an earlier level and does not support the attempted
operation. The client software on the target must be upgraded before the operation can be performed.

0042–271 String : A resource matching the type of String is already allocated to String . You cannot allocate
more than one resource of this type to a machine.
Explanation: A resource matching the type is already allocated. You cannot allocate more than one resource of this
type to a machine.
User response: Deallocate the first resource before attempting to allocate the second. It may be necessary to reset
the machine before the resource can be deallocated.

0042–272 String : String cannot be specified as a value for default_res because it is not a valid NIM
resource group.
Explanation: A value specified is not a valid value for default_re because it is not a valid NIM resource group.
User response: Specify a different resource group for the default_res attribute, or correct the resource group in
question.

0042–273 String : ’ String ’ cannot be specified as the location for the mksysb image because it is a
directory. You must specify the filename where the mksysb image currently resides or will reside
after creation.
Explanation: A value specified cannot be used as the location for the mksysb image because it is a directory. You
must specify the filename where the mksysb image currently resides or will reside after creation.
User response: Specify a file name instead of a directory for the location of the mksysb resource.

Chapter 1. Message Component 0042 35

0042–274 String : The ’-e’ flag in the mksysb_flags attribute and the exclude_files attribute cannot be
specified together. Specify the ’-e’ flag with the mksysb_flags attribute to exclude the files in
/etc/exclude.rootvg on String from the backup, or specify an exclude_files attribute.
Explanation: The -e flag in the mksysb_flags attribute and the exclude_files attribute cannot be specified together.
Specify the -e flag with the mksysb_flags attribute to exclude the files in /etc/exclude.rootvg from the backup, or
specify an exclude_files attribute.
User response: Do not specify both the -e mksysb flag and an exclude_files resource when performing this
operation.

0042–275 String : Unable to obtain possession of the lock file String . If no NIM operations are currently in
progress remove the file and repeat the operation.
Explanation: Unable to obtain possession of a lock file. If no NIM operations are currently in progress, remove the
file and repeat the operation.
User response: Use the ps -ef | grep nim command to list the running NIM processes on the system. If any NIM
processes other than the nimesis daemon are running, wait for them to finish and then remove the file specified by
the error message.

0042–276 String : The String fileset must be installed before this operation can be performed.
Explanation: A file set must be installed before this operation can be performed.
User response: Install the file set listed in the error message before retrying the operation. Generally, the fileset
needs to be installed on the client system. However, depending on the operation being performed, the NIM master
may also need to have the fileset installed before the operation will succeed.

0042–277 String : diskless and dataless machines cannot be defined with a primary network install
interface residing on a generic NIM network. It is presumed that a network adapter defined on a
generic NIM network does not support network boot.
Explanation: Diskless and dataless machines cannot be defined with a primary network install interface residing on
a generic NIM network. It is presumed that a network adapter defined on a generic NIM network does not support
network boot.
User response: To define the systems as diskless or dataless clients, they must first be connected to a NIM network
that is known to support network boot, such as ethernet, token-ring, or FDDI.

0042–278 String : The interface specified does not correspond to a network adapter that is known to
support network boot. As a result, the NIM master has been defined on a generic NIM network.
Network boot dependent operations, such as base operating system installation, will not be
possible on any NIM client whose primary network install interface is defined on the same
network as the NIM master.
Explanation: The interface specified does not correspond to a network adapter that is known to support network
boot. As a result, the NIM master has been defined on a generic NIM network. Network boot-dependent operations,
such as base operating system installation, will not be possible on any NIM client whose primary network install
interface is defined on the same network as the NIM master.
User response: Operations that rely on network boot capability cannot be performed on clients on generic NIM
networks. Such operations must be performed using local media on the system.

0042–279 String : The interface specified maps to a subnet which has been defined as a generic NIM
network. It will not be possible to perform network boot dependent operations, such as base
operating system installation, on the machine definition created by this operation.
Explanation: The interface specified maps to a subnet which has been defined as a generic NIM network. It will not
be possible to perform network boot-dependent operations, such as base operating system installation, on the
machine definition created by this operation.
User response: Operations that rely on network boot capability cannot be performed on clients on generic NIM

36 Message Center Reference

networks. Such operations must be performed using local media on the system.

0042–280 String : Specify a complete date and time for the scheduled operation in the form:
YYMMDDhhmm.
Explanation: Specify a complete date and time for the scheduled operation in the form: YYMMDDhhmm.
User response: Use the format described in the error message to correctly schedule a date and time for the
operation.

0042–281 String : The /usr filesystem on the specified server cannot be converted to a NIM SPOT. Either the
RM_INST_ROOTS variable was set to yes in a bosinst.data file during initial installation of the
machine or inurid -r was invoked at some time subsequent. The only way to create a SPOT on
this machine is to specify the location to be something other than /usr or re-install the machine
and then create a SPOT in /usr.
Explanation: The /usr file system on the specified server cannot be converted to a NIM SPOT. Either the
RM_INST_ROOTS variable was set to yes in a bosinst.data file during initial installation of the machine or inurid -r
was subsequently invoked. The only way to create a SPOT on this machine is to specify the location to be something
other than /usr or reinstall the machine and then create a SPOT in /usr.
User response: The system is unable to support the creation of a /usr SPOT. A non-/usr SPOT may be created on
the system by specifying a different value for the location attribute.

0042–282 String : The BOS installation has been enabled but could not be initiated because the following
file was not found on the target: String To start the installation do ONE of the following: 1. initiate
a network boot operation from the target 2. correct the state of the target with NIM’s reset
operation and invoke the bos_inst operation again either: a) using the Force Push option (-a
force_push=yes), or b) after installing and configuring the bos.sysmgt.nim.client fileset on the
target.
Explanation: The BOS installation has been enabled but could not be initiated, because the following file was not
found on the target. To start the installation, do one of the following:
1. Initiate a network boot operation from the target.
2. Correct the state of the target with NIM’s reset operation and invoke the bos_inst operation again using one of
the following:
a. The Force Push option (-a force_push=yes)
b. After installing and configuring the bos.sysmgt.nim.client fileset on the target.
User response: The NIM client fileset is not properly installed and configured on the target system. Follow the
directions specified in the error message to correct the problem.

0042–283 String : The existence of the file String on the server String indicates that a NIM SPOT may still be
mounted in a subdirectory of String which will be removed by this operation. Before attempting
this operation again, unmount the SPOT’s directory along with any other directories that may be
mounted beneath the directory being removed. FAILURE TO DO SO WILL RESULT IN LOSS OF
DATA ON THE SPOT SERVER!
Explanation: The existence of a file on the server indicates that a NIM SPOT may still be mounted in a subdirectory
which will be removed by this operation. Before attempting the operation again, unmount the SPOT’s directory along
with any other directories that may be mounted beneath the directory being removed.
Failure to do so will result in loss of data on the SPOT server.
User response: A SPOT operation failed, and NIM was unable to unmount all the directories mounted into the
SPOT. Manually unmount the directories specified in the error message before retrying the operation. The mount
command can be used to list the directories mounted on the system, and the unmount command can be used to
unmount directories. Use the -f option with the unmount command if necessary to force the unmount.

Chapter 1. Message Component 0042 37

0042–323 String : This operation requires all resource to be the same architecture as the object it is being
used on. Object String and resource String are incompatible for this operation.
Explanation: To perform an operation on a NIM object, the NIM resource allocated to the object must be of the
same architecture as the NIM object.
User response: Deallocate the conflicting resource and allocate a resource with the same architecture as the object.

0042–324 String : Unable to complete this operation. Defined resource and server must have the same
architecture when the OS level of the server specified is less than String .
Explanation: Cross-platform resources and operations are not allowed on servers with an operating system level
prior to AIX 5.1.
User response: Try performing operation on a server with an operating system level of AIX 5.1 or later.

0042–325 String : This operation requires that the resource and server be of the same architecture.
Explanation: To perform the operation, the resource and server must be of the same architecture.
User response: Perform the operation with a server and resource of the same architecture.

0042–326 String : This operation requires that the architecture supplied by the user match the architecture
value of the source resource.
Explanation: If an architecture value is specified during the creation of a cross-platform resource, then it should
correctly identify the architecture of the source being used.
User response: Give the correct architecture of the resource or do not specify an architecture when defining the
resource.

0042–327 String : An existing SPOT is necessary when creating a SPOT resource with an architecture
different from its server.
Explanation: Cross-platform SPOT resources may only be created from an existing SPOT resource.
User response: Use an existing cross-platform SPOT as the source to create the new SPOT resource.

0042–330 String : Unable to determine the architecture of String .

Explanation: NIM cannot determine the architecture of the source being used for the current operation.
User response: In an lpp_source resource is being created, then supply a value for the arch attribute.

38 Message Center Reference

Chapter 2. Message Component 0301
Messages 0301-150 through 0301-176 are associated with the bosboot command.

© Copyright IBM Corp. 2003, 2004 39

40 Message Center Reference
Chapter 3. Message Component 0315
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-004 errdead
errdemon
errstop
021-023 errclear
errpt
024-040 For more information, see Error-Logging Overview in AIX 5L Version 5.3 General Programming
Concepts: Writing and Debugging Programs.
041-073 errupdate
080-097 errclear
errinstall
errmsg
errpt
098 errclear
errpt
099-100 errdemon
101 errdemon
errpt
102 errdemon
errlog
errlogger
103-106 errpt
107 errlogger
108-119 errpt
120-130 errdemon
132 errclear
errpt
133 errclear
134-136 errpt

© Copyright IBM Corp. 2003, 2004 41

42 Message Center Reference
Chapter 4. Message Component 0402
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–040 bsh
0402–001 Error Recovery Information
0402–002 Error Recovery Information
0402–004 Error Recovery Information
0402–011 Error Recovery Information
0402–021 Error Recovery Information
0402–026 Error Recovery Information
041–043 apply
044 env
045–050 expr
051–062 xargs
070 expr
083 xargs
100–102 bsh
110–111 getopt
140–145 syscall
150–155 test

Detailed Information for Message Component 0402

0402–001 Cannot trap SIGSEGV

Explanation: You specified an illegal trap command to the SIGSEGV signal (signal number 11) in a shell script.
User response: Remove the illegal trap command from your shell script, and restart your system by doing the
following:
1. Using an editor, locate the illegal trap command and delete it from the shell script. The illegal trap command looks
similar to the following:
trap ’echo SIGSEGV received’ 11

Note: To save the shell script, you need write permission to the file. You may need to use the su command to
change to the root user or to a user who has write permission.
2. Restart your system to remove the trap.

0402–002 Cannot find FileName

Problem determination: You attempted to use a file in a directory that is not listed in your PATH environment
variable.
User response: Add the directory where the file is located to your PATH variable by doing the following:
1. Run the echo $PATH command to determine which directories are in your PATH variable.
2. If the directory where the file resides is not listed, type the following command:
PATH=DirectoryName: $PATH; export PATH

where DirectoryName specifies the directory that you wish to add.

© Copyright IBM Corp. 2003, 2004 43

3. If you want the DirectoryName directory included in your PATH variable every time you create a new session, edit
your .profile file and change the line where the PATH variable is set to include the DirectoryName directory.
Otherwise, this modification is active only for your current session.
Problem determination: You entered the type command with a file for which you do not have execute permission.
User response: Add execute permissions to the file by doing the following:
1. Run the ls -ld command to determine the permissions on the file.
2. Run the su command to change to a user that has execute permission on the file, or run the chmod +x command
to give yourself execute permission on the file.
Problem determination: You attempted to use a file that does not exist.
User response: Create the file by doing the following:
1. Using an editor, create and save the file.
2. Run the ls -ld command to ensure that you have permissions on the file. If needed, run the chmod +x command
to give yourself execute permission on the file.

0402–004 There is not enough memory available now

Problem determination: A process running under the Bourne shell (bsh) requires more memory than is available on
the system. The following can cause this condition:
v A process is being forked and the fork fails with errno ENOMEM.
v A process is being run and the run fails with errno ENOMEM.
v A setbrk is being performed to increase the shell stack space and fails.
User response:
v Increase the amount of memory allocated per process.
v Increase the amount of physical memory in your system.

0402–011 Cannot create the specified file

Problem determination:
v The path for the specified file name does not exist.
v The path exists, but you do not have permission to create a file within the specified path.
User response: Ensure that the path for the specified file exists by doing the following:
1. Run the ls command to list each directory in your path. If the path is valid, a list of the contents of the directory is
displayed. If the path does not exist, the following message is displayed:
The file /Directory1/Directory2 does not exist
2. If the path does not exist, further isolate the problem by using the ls command for each directory in the path. Use
the mkdir command to create any directories that are missing from the path. If the specified path is valid, the error
message indicates that you do not have permission to create a file within that path.
3. Obtain permission to create a file within the specified path.
4. Run the ls -ld command to display the permissions for the specified path. If you do not have access permission to
a file or directory, enter the su command to switch to the root user or owner of the file or directory. Then use the
chmod command to change permissions. For more information, see File and Directory Access Modes in CHECK
THIS LINK--was AIX 5L Version 5.3 System User’s Guide: Operating System and Devices.

0402–021 Cannot run the command as specified

Explanation: Using the Bourne shell, you issued from the command line:
/Path/Command

where Path is the path name of the command you tried to run, but you do not have execute permission for the
command.
User response:

44 Message Center Reference

v You need to be the root user to run this command. Enter the su command to switch to the root user or owner of the
file or directory.
OR
v The command has group execute permission. Ask your system administrator to include you as a member of this
group.

0402–026 The specified data is not a valid identifier

Problem determination: Using the Bourne shell, you issued the following command:
export Variable=Value
User response: When using the Bourne shell, the correct syntax for the export command is:
Variable=Value export Variable
Problem determination: Using the Bourne shell, you attempted to use a variable that does not begin with an
alphanumeric character, or has unsupported characters.
User response: Change the variable name to begin with a letter or underscore ( _ ), and remove any invalid
characters.
Problem determination: Using the Bourne shell, you attempted to assign a variable as read-only, without first setting
the value of the variable. For example:
readonly Variable=Value
User response: When using the Bourne shell, the correct syntax for the readonly command is:
Variable=Value readonly Variable

Chapter 4. Message Component 0402 45

46 Message Center Reference
Chapter 5. Message Component 0403
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-004 ksh
005 ksh
open, openx, or creat subroutine
link subroutine
0403-005 Error Recovery Information
006-019 ksh
0403-011 Error Recovery Information
021-022 ksh
027 ksh
029-022 ksh
035-037 ksh
039-059 ksh
065 ksh
067-068 ksh

Detailed Information for Message Component 0403

0403–005 Cannot create the specified file

Explanation: From the command line, you issued the following command:
cat Filename > Printdevice
Problem determination: The printer device was either not attached, was busy, was down, or was not on the
network.
User response: Ensure that the printer device is attached to the system by doing the following:
1. Run the lpstat command to check if the printer is busy, or if the print queue is down.
2. If the printer is busy, wait until the currently queued job is complete, then rerun the command.
3. If the print queue is down, run the su command to become the root user, and then run the qadm command to
restart the queue by typing:
qadm -U Queuename
Problem determination: You attempted to create a file in a directory for which you do not have write or execute
permissions.
User response: Run the su command and become the root user, then add read-write permission to the directory
and to the parent directories.
Problem determination: You attempted to write to a file system that is mounted as read-only.
User response: Unmount the file system using the unmount command. Then remount the file system with
read-write access by entering the following on the command line:
mount -o rw Filesystem Directory

© Copyright IBM Corp. 2003, 2004 47

0403–011 The specified substitution is not valid for this command
Explanation: You attempted to change directories using a pattern-matching character that incorrectly specified the
directory name.
User response: Verify the directory name and run the command again. For example, if you have a chap1dir
directory and a chap10dir directory, you cannot change directories by typing cd chap*. You must type cd chap1d*.

48 Message Center Reference

Chapter 6. Message Component 0453
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–025 sysdumpdev
sysdumpstart
026–042 sysdumpdev

© Copyright IBM Corp. 2003, 2004 49

50 Message Center Reference
Chapter 7. Message Component 0454
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–011 trace
trcdead
trcoff
trcon
trcstop
012–036 trcrpt
trcupdate
040–041 trace
trcdead
trcoff
trcon
trcstop
061–069 trcrpt
trcupdate
070–072 trace
trcdead
trcoff
trcon
trcstop
073–075 trcrpt
076 trcdead

© Copyright IBM Corp. 2003, 2004 51

52 Message Center Reference
Chapter 8. Message Component 0460
Messages 0460-001 through 0460-091 are associated with the adfutil command.

Detailed Information for Message Component 0460

0460–018 -C option requires an argument - CardID

Explanation: The adfutil command was invoked without an argument for the -c option.
User response: If the -c flag is supplied, a card identifier must be specified. If you started the adfutil command with
the -c flag and have the card identifier as follows:
adfutil -c

change it to the following:

adfutil -c cardidxxxx

© Copyright IBM Corp. 2003, 2004 53

54 Message Center Reference
Chapter 9. Message Component 0503
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-099 installp
0503–006 Error Recovery Information
0503–020 Error Recovery Information
100-129 geninstall
130-151 gencopy
200-308 ckprereq
installp
400-500 installp
600-619 bffcreate
620-629 inucp
630-639 inutoc
700-709 inurest
710-719 inusave
750-799 installp
810-825 get_license_info
826-840 instfix
841-886 mkinstallp
makebff
960-970 vpdadd

Detailed Information for Message Component 0503

0503–006 Cannot create the directory DirectoryName. Check path name and permissions.
Explanation: When installing or rejecting your software, your command specified a directory to which you do not
have write access.
User response: If you are not logged in as the root user, log in as root user and reissue your command.
OR
Edit the /etc/filesystems file to check if the file system where the directory is located is mounted as read-only. If the
file system is mounted as read-only, change the access to read-write by doing the following:
1. Unmount the file system by using the unmount command.
2. Mount the file system by using the mount command.
3. Reissue your command.

0503–020 There is not enough disk space for installation of the software on file system FileSystem
Explanation: You were unable to install the software on the specific file system indicated in the error message
because you ran out of space.
User response: If you are installing software using the command line, add the -X flag to your command in order to
extend the size of the file system.
OR

© Copyright IBM Corp. 2003, 2004 55

If you are using System Management Interface Tool (SMIT), set the EXTEND file systems if space needed? attribute
to yes.

56 Message Center Reference

Chapter 10. Message Component 0504
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–051 installp
100–199 lslpp
200–299 lppchk
300–333 lslpp
999 installp

© Copyright IBM Corp. 2003, 2004 57

58 Message Center Reference
Chapter 11. Message Component 0509
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000–011 ps
0509-004 Error Recovery Information
0509-005 Error Recovery Information
0509-010 Error Recovery Information
0509-011 Error Recovery Information
012–015 kill
0509-013 Error Recovery Information
0509-015 Error Recovery Information
016–017 killall
018 nice
0509-018 Error Recovery Information
019 nohup
0509-019 Error Recovery Information
020 sleep
021–037 loadquery subroutine
0509-029 Error Recovery Information
038–041 renice
0509-039 Error Recovery Information
0509-040 Error Recovery Information
0509-041 Error Recovery Information
042–049 ps
0509-048 Error Recovery Information
050–051 kill
060–061 ps

Detailed Information for Message Component 0509

0509–004 Cannot open the directory /dev

Explanation: You entered the ps command, which relies on information contained in the /dev directory, but access
to the /dev directory was not granted by the system.
User response: Ensure that you have the correct file permissions on the /dev directory by doing the following:
1. Enter the ls -ld /dev command to view the permissions. The output should look similar to the following:
drwxrwxr-x 3 root system 2048 Feb 20 10:58 /dev
2. If the ownership and the permissions do not match the preceding output, enter the su command to change to the
root user.
3. Use the chown, chgrp, and chmod commands to assign the correct ownership and permissions.
4. Reenter the ps command.

© Copyright IBM Corp. 2003, 2004 59

0509–005 Cannot change the current directory to /dev
Explanation: You used the ps command, but you do not have execute permission on the /dev directory.
User response: Ensure that you have the correct file permissions on the /dev directory by doing the following:
1. Enter the ls -ld /dev command to view the permissions. The output should look similar to the following:
drwxrwxr-x 3 root system 2048 Feb 20 10:58 /dev
2. If the ownership and the permissions do not match the preceding output, enter the su command to change to the
root user.
3. Use the chown, chgrp, and chmod commands to assign the correct ownership and permissions.
4. Reenter the ps command.

0509–010 An error occurred on the read process

Problem determination: You ran the ps command, and one of the following occurred:
v There was a physical problem on the disk.
v The ps_data file is set to Null.
User response:
v Run disk diagnostics using the fsck or dfsk command, and correct the physical problem on the disk.
OR
v Reset the ps_data file by doing the following:
1. Enter the rm ps_data command to remove the ps_data file.
2. Enter the ps command.

0509–011 An error occurred on the write process. Check path name and permissions.
Explanation: The ps command failed in writing to the internal database file even though it succeeded in opening the
file.
User response: Ensure that the correct /etc file is mounted in the file system and has enough space by doing the
following:
1. Enter the df /etc command to check if the /etc file is mounted and how much of the file system is being used.
2. If the file system is full, remove unnecessary files or increase the size of the file system by using System
Management Interface Tool (SMIT).
3. Reenter the ps command.

0509–013 Permission denied

Problem determination: You are not the root user and you tried to use the kill command to stop a process that you
did not start.
User response: Change to the root user and reissue the kill command by doing the following:
1. Enter the su command to change to the root user.
2. Reissue the kill command.
Problem determination: You tried to stop a process and entered an incorrect process ID (PID) number.
User response: Obtain a valid process ID number and reissue the kill command by doing the following:
1. Enter the ps -eaf command to list the currently running processes.
2. Locate the process you want to stop.
3. Reissue the kill command with the correct PID number.

60 Message Center Reference

0509–015 The specified process does not exist
Explanation: You used the kill command to stop a process with a nonexistent or invalid process ID (PID).
User response: Locate a valid PID, then specify it with the kill command to stop the process by doing the following:
1. Enter the ps -eaf command to list the existing processes with their PIDs.
2. Locate the process that you want to stop.
3. Enter the kill command, specifying the correct PID.

Note: You can use the kill command only on processes that you own. You may need to enter the su command to
change to the root user (who owns all processes) or to the user who owns the process you want to stop.

0509–018 Flag must be numeric

Explanation: You entered the nice command with a flag that is not numeric.
User response: Enter a numeric flag after the nice command, as in the following example:
nice -10 CommandArgument

0509–019 Cannot open or create the nohup.out file

Explanation: You issued the nohup command, with one of the following results:
Problem determination: Your HOME variable is not set, and you do not have write permission to your home
directory.
User response: Ensure that your HOME environment variable reflects your home directory by doing the following:
1. Enter the echo $HOME command to obtain the value of your HOME environment variable.
2. If the two do not match, enter export HOME=PathName, where PathName is the full path of your home directory.
3. Reissue the nohup command.
Problem determination: Your HOME variable is set, but you do not have write permission to your home directory.
User response: Obtain write permission to the current directory by doing the following:
1. Enter the ls -ld command to display the permissions on the current directory and ensure that you have write
permissions.
2. Reissue the nohup command.
Problem determination: Your HOME variable is set and a nohup.out file already exists in your home directory, but
you do not have write permission to the $HOME/nohup.out file.
User response: Verify that the nohup.out file exists and obtain write permission by doing the following:
1. Enter the ls -l nohup.out command to verify that the nohup.out file exists in the current directory and that you
have write permission on the file.
2. If the nohup.out file exists but you do not have write permission, use the chmod command to modify the file
permissions.
3. Reissue the nohup command.

Note: The nohup command creates a nohup.out file in the current directory. If the nohup.out file already exists, the
output from the nohup command is appended to the existing file.

0509–029 Alignment of text does not match required alignment

Explanation: The format of the code for an executable program is not correct.
User response: Recompile the code using the ld command.

Chapter 11. Message Component 0509 61

0509–039 The process or process group String is not an integer
Explanation: You entered the renice command to reset the scheduling priority of one or more running processes,
but specified an invalid process ID (PID) or process group ID with the -p flag.
User response: Reenter the renice command, specifying a valid PID by doing the following:
1. Enter the ps -eaf command to list the system processes and obtain a valid PID.
2. Reenter the renice command, specifying a valid PID.

0509–040 Number: getpriority: The process does not exist

Explanation: You attempted to change the renice value of an invalid or nonexistent process.
User response: Reenter the renice command, specifying a valid process ID (PID) and options by doing the
following:
1. Use the ps -eaf command to list the system processes and obtain a valid PID.
2. Reenter the renice command using a valid PID and valid command options.

0509–041 ProgramName: 0509-041: Number

Explanation: You used the renice command and do not have root user authority.
User response:
1. Enter the su command to change to root user.
2. Reenter the renice command.

0509–048 Flag -F was used with invalid list

Explanation: You specified invalid or unknown names of field specifiers.
User response: Use the correct recognized name with the -F flag when using the ps command. For a list of valid
descriptors, see the ps command in AIX 5L Version 5.3 Commands Reference, Volume 4.

62 Message Center Reference

Chapter 12. Message Component 0511
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–038 cpio
0511-023 Error Recovery Information
0511-037 Error Recovery Information
0511-038 Error Recovery Information
039–065 dd
0511-051 Error Recovery Information
0511-053 Error Recovery Information
066–069 flcopy
070–078 tctl
079–099 backup
0511-079 Error Recovery Information
0511-080 Error Recovery Information
100–161 restore
0511-123 Error Recovery Information
0511-133 Error Recovery Information
0511-160 Error Recovery Information
162–199 tar
0511-169 Error Recovery Information
0511-193 Error Recovery Information
0511-195 Error Recovery Information
202–259 rdump
274–365 restore
367–425 rdist
430–444 backup
0511-432 Error Recovery Information
461–462 cpio
470–471 backup
472–502 restore
550–555 tcopy
600–667 pax
900–902 cpio
903–905 dd
0511-903 Error Recovery Information

Detailed Information for Message Component 0511

0511–023 Cannot write to the DirectoryName directory

Problem determination:
v The directory you specified using the cpio -p command does not exist.
OR
v You do not have write access permission to copy files in the directory you specified.
User response: Enter the ls -ld/DirectoryName command to verify that the directory exists. Then do one of the
following:

© Copyright IBM Corp. 2003, 2004 63

v If the directory does not exist, create the directory using the mkdir DirectoryName command.
v If the directory does exist, verify that you own the directory and that you have write access permissions to it.
v If you are the owner, but you do not have write access permission, enter the chmod 700 DirectoryName command,
where DirectoryName is the directory on which you want to change the access permissions.
v If you are not the owner and do not have write access, log in as root user and enter the chmod 777 DirectoryName
command, where DirectoryName is the directory on which you want to change the access permissions.

0511–037 Cannot read from the specified input

Problem determination: From the command line, you issued the cpio command, with the -c flag to extract an
archived file that was not initially created with the -c flag.
User response: Rerun the cpio command without the -c flag.
Problem determination: You attempted to use the cpio command to extract archived files that were not created
using the cpio format.
User response: Run one of the following formats from the command line to check the correct format of the file or
device:
v For tar format, use the following:
tar -tvf FileOrDeviceName
v For backup format, use the following:
restore -Tv

0511–038 Cannot write to the specified output

Problem determination: You issued the cpio command to create an archive but specified an incorrect blocking
factor with the -C or -B flag.
User response:
v Use the tctl command to verify the block size of the tape device. For example:
tctl -f /dev/rmt# status
v Use the -C# flag to specify a multiple block factor of the physical device. For example, if the tape block size is set
to 1024, use the -C2 flag.

Note: Do not use the -B flag if the tape device block size is 4096.
Problem determination: The tape is damaged.
User response: Check the error log for tape errors by using the errpt -a command.

0511–051 The read failed

Problem determination: The tape is backed up on a tape device with a block size that differs from the one on which
it is currently set.
User response: Use the chdev command to change the block size on the tape device by typing the following on the
command line:
chdev -1 rmt# -a block size=0
Problem determination: The value specified with either the bs, ibs, or obs flag is not a multiple of the block size of
the tape device.
User response: Use the tctl command to verify the block size of the tape device by typing the following on the
command line:
tctl -f /dev/rmt# status

Then, specify the value of the bs, ibs, or obs flag as a multiple of the block size.
Problem determination: The value specified for the fskip flag is greater than the number of end-of-file marks on the
tape.
User response: Use the tcopy command to check the number of files or records that can be accessed on tape.

64 Message Center Reference

Problem determination: The tape is damaged.
User response: Check the error log for tape errors by typing the following on the command line:
errpt -a

Take action as indicated.

0511–053 The write failed

Problem determination: From the command line, you issued the following command:
dd if=Filename of=Device conv=block

but did not specify the cbs parameter.

User response: Use the cbs=value parameter with the conv=block parameter.
Problem determination: You issued the dd command, but the length of the data was not a multiple of 512 bytes,
and you did not use the conv=sync parameter.
User response: Use the conv=sync parameter if the data length is not a multiple of 512 bytes.
Problem determination: You issued the dd command with the obs or bs parameter, which did not have a
corresponding value as a multiple of the tape device block size.
User response: Use the lsattr command to verify the block size of the tape drive by typing the following on the
command line:
lsattr -1 rmt# -E

Specify the obs or bs parameter with a value that is a multiple of the tape block size.
Problem determination: You attempted to write data to a diskette with the dd command, but the length of the data
was greater than the capacity of the diskette.
User response: If the data is greater than the capacity of the diskette, use a different medium.

0511–079 The backup media may be damaged

Problem determination: From the command line, you issued the backup command, naming a tape device with the
block size set to 0, but specified a value with the -b flag that is larger than the maximum allowable write size for the
tape device.
User response: Specify a value with the -b flag that does not exceed the maximum allowable write size for the tape
device, or do not use the -b flag.
Problem determination: From the command line, you issued the backup command, naming a tape device, but
specified a value with the -b flag that does not yield a whole number multiple of the tape device’s physical block size.
User response: Specify a value with the -b flag that yields a whole number multiple of the tape device’s physical
block size. For example:
backup -b Number

where Number is the number of 512-byte blocks.

Note: You can use the lsattr command to verify the physical block size of the device as follows:
lsattr -l rmt# -E
Problem determination: From the command line, you issued the following command:
find File -print| backup -ivf FileSystem/FileName

but the specified FileSystem was full.

User response: Remove unnecessary files from the file system, or use the chfs command to increase the file
system and rerun the backup command.
Problem determination: The backup media is damaged.

Chapter 12. Message Component 0511 65

User response:
v Check the error log for media errors by using the following command:
errpt -a

OR
v Use a different tape or disk to run the backup.

0511–080 Pathname is too long

Explanation: During the backup process, the find command could not locate data because the path name specified
was too long.
User response: Do one of the following:
v Limit the path name to one that is fewer than 255 characters.
v Start the backup process from a lower-level directory.

0511–103 The volume not correct restore expects volume X

Problem determination: The number X tape was inserted in the incorrect order.
User response:
v Check to see if the disks were inserted into the tape drive in the correct order.
v If it is a multivolume archive, it is likely that tapes are misnumbered.
Problem determination: If it is a single-volume archive, the archive might be corrupt and the tape device
erroneously thinks that it has reached end-of-file.
User response: Check the tape and see if it is damaged or corrupted.

0511–123 The volume on String is not in backup format

Problem determination: You attempted to access data beyond the end of the tape marker, using the restore
command.
User response: Use the tctl command to rewind the tape, then rerun the restore command. For example:
tctl -f /dev/rmt# rewind restore -xvf /dev/rmt#.1
Problem determination: From the command line, you issued the restore command, with the -s flag, but did not
specify the no-rewind tape device.
User response: Specify the no-rewind tape device, /dev/rmt#.1 with the -s flag.
Problem determination: From the command line, you issued the installp command and specified the device as:
/dev/rmt#.1.
User response: Specify the tape device as follows:
/dev/rmt#.
Problem determination: You tried to access a file or device with the restore command, but the file or device was
not in the backup format.
User response: Run one of the following formats from the command line to verify the correct format of the file or
device:
v For tar format:
tar -tvf DeviceOrFileName
v For cpio format:
cpio -itv DeviceOrFileName
Problem determination: The /var or /tmp directory is too small.
User response: Increase the size of the /var or /tmp directory.
Problem determination: The tape or drive is damaged.

66 Message Center Reference

User response: Check the error log to determine if the tape or drive is damaged. If it is, replace the tape or drive.

0511–133 There is a data read error

Explanation: From the command line, you issued the following command:
restore -s Number -f Device
User response: Use the tcopy command to check the number of records on the tape, and specify a correct value
with the skip flag. For example:
tcopy Device

0511–160 Cannot read the backup media

Problem determination: The tape is backed up on a tape device with a block size that differs from the one on which
it is currently set.
User response: Log in as the root user, and use the chdev command to change the block size on the tape device
as follows:
chcev -1 rmt# -a block size=0

You can also change the block size by selecting the SMIT Devices -> Tape Drive -> Change/Show Characteristics
of a Tape Drive menu options. Select the appropriate drive and change the block size.
Problem determination: The backup medium is damaged.
User response: Check the error log for tape errors as follows:
errpt -a

Take action as indicated.

0511–169 A directory checksum error on media: MediaName not equal to Number

Problem determination: From the command line, you issued the tar command to extract files from an archive that
was not created with the tar command.
User response: Ensure that the file is in the correct format by running the cpio command or the restore command.
Problem determination: You issued the tar command for a file that became damaged while being copied over the
network.
User response: Run the sum command on the copied file and also on the original file. Recopy the file if the sizes
are different.
Problem determination: You issued the tar command for a file that was copied over the network, using the ftp
command, but did not specify the binary flag.
User response: Rerun the ftp command using the binary flag to copy the file, then rerun the tar command.

0511–193 An error occurred while reading from the media

Problem determination: You issued the tar command to read an archive from a tape device that has a different
block size than it had when the archive was created.
User response:
v From the command line, run the tctl command to verify the tape block size as follows:
tctl -f /dev/rmt# status

OR
v Use the chdev command to change the block size, for example:
chdev -1 rmt0 -a block size=0
Problem determination: The tape is damaged.
User response: Check the error log for tape errors as follows:

Chapter 12. Message Component 0511 67

errpt -a

Take action as indicated.

0511–195 An error occurred while writing to the storage media

Problem determination: You issued the tar command without the -b flag, but the tape drive had an incorrect block
size (4096).
User response: From the command line, run the tctl command to verify the tape block size as follows:
tctl -f /dev/rmt# status

If a block size of 4096 is desired, specify the -b flag with a value of 8 or multiple of 8, or run the chdev command to
change the tape block size, as follows:
chdev -1 rmt0 -a block size=1024

A block size of 512 or 2048 can also be used.

Problem determination: You attempted to create a new archive beyond the end of the tape marker using the tar
command.
User response: Rewind the tape and reissue the command as follows:
tctl -f /dev/rmt# rewind
Problem determination: The tape density is incorrect.
User response: Change the tape density using the chdev command as follows:
chdev -1 rmt# -a density_set_1=value

Rerun the original command.

Problem determination: The tape medium is defective.
User response: Check the error log for tape errors as follows:
errpt -a

Take action as indicated.

0511–432 A write error occurred

Problem determination: From the command line, you issued the backup command, naming a tape device with the
block size set to 0, but specified a value with the -b flag that is larger than the maximum allowable write size for the
tape device.
User response: Specify a value with the -b flag that does not exceed the maximum allowable write size for the tape
device, or do not use the -b flag.
Problem determination: From the command line, you issued the backup command, naming a tape device, but
specified a value with the -b flag that does not yield a whole number multiple of the tape device’s physical block size.
User response: Specify a value with the -b flag that yields a whole number multiple of the tape device’s physical
block size. For example:
backup -b Number

where Number is the number of 512-byte blocks.

Note: You can use the lsattr command to verify the physical block size of the device as follows:
lsattr -l rmt# -E
Problem determination: From the command line, you issued the following command:
find File -print| backup -ivf FileSystem/FileName

but the specified FileSystem was full.

68 Message Center Reference

User response: Remove unnecessary files from the file system, or use the chfs command to increase the file
system and rerun the backup command.
Problem determination: The backup media is damaged.
User response:
v Check the error log for media errors by using the following command:
errpt -a

OR
v Use a different tape or disk to run the backup.

0511–903 Out of phase! cpio attempting to continue

Problem determination: From the command line, you issued the cpio command, with the -c flag to extract an
archived file that was not initially created with the -c flag.
User response: Rerun the cpio command without the -c flag.
Problem determination: You attempted to use the cpio command to extract archived files that were not created
using the cpio format.
User response: Run one of the following formats from the command line to check the correct format of the file or
device:
v For tar format, use the following:
tar -tvf FileOrDeviceName
v For backup format, use the following:
restore -Tv

Chapter 12. Message Component 0511 69

70 Message Center Reference
Chapter 13. Message Component 0512
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

004-015 mksysb
0512-004 Error Recovery Information
0512-005 Error Recovery Information
0512-009 Error Recovery Information
016 bosboot
0512-016 Error Recovery Information
017 mksysb
018, 020 mkszfile

Detailed Information for Message Component 0512

0512–004 The /FileName file does not exist. System backup canceled
Problem determination: The / or /tmp file system is not large enough.
User response: Extend the file system. For information on extending file systems, see File System Management
Tasks in Operating system and device management.
Problem determination: You ran the mksysb command outside of SMIT without running the mkszfile command
first.
User response: Run the mkszfile command and then run the mksysb command again.

0512–005 Backup Completed

Explanation: The backup command completed with errors. The messages displayed on Standard Error contain
additional information.

Note: If SMIT was used to do the system or volume group backup, then check the smit.log file for errors.
Problem determination: A file was removed during the system or volume group backup.
User response:
v Quiesce the system and rerun the backup.
OR
v Verify the backup tape. For more information, see Backup Files and Storage Media in CHECK THIS LINK--was AIX
5L Version 5.3 System User’s Guide: Operating System and Devices.

0512–009 Invalid or Missing Volume Group Name

Explanation:
v The volume group name might be misspelled.
v The volume group name was not specified on the command line.
User response: Choose the volume group name from a list of volume groups.

© Copyright IBM Corp. 2003, 2004 71

0512–016 Attempt to create a bootable tape failed
Explanation: This message is displayed with one of the following:
bosboot -d /dev/device -a failed with return code Number

OR
mkinsttape /dev/device failed with return code Number
Problem determination: The media is write-protected (return code 2).
User response: Ensure that the media is not write-protected.
Problem determination: There is not enough space in the file systems (return code 5 or 1).
User response: Extend the file system. The / directory must have at least 500 1 KB blocks. The /tmp directory must
have at least 7400 1 KB blocks, and the /usr directory must have at least 4000 1 KB blocks. For information on
extending file systems, see File System Management Tasks in Operating system and device management.
Problem determination: The tape is defective (return code 11).
User response: Replace the tape.
Problem determination: The /usr/lib/boot/unix directory is damaged (0 length), or the link to the /unix directory is
missing (return code 52 or 45).
User response: Restore the directories from the original tape or create the missing link to the /unix directory.
Problem determination: The tape drive cannot be written to or the /dev/blv/ directory cannot be read. This can be
caused by an incorrect density setting for the tape-drive/tape-type/device-name combination, dirty tape drive heads, or
a tape drive hardware problem.
User response: Ensure the status of the tape drive. If cleaning the tape drive heads does not correct the problem,
contact your system administrator.

72 Message Center Reference

Chapter 14. Message Component 0514
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-017 chdev
lsattr
lsconn
lsdev
lsparent
mkdev
restbase
rmdev
savebase
018 chdev
lsattr
lsconn
lsdev
lsparent
mkdev
restbase
rmdev
savebase
0514-018 Error Recovery Information
019-021 chdev
lsattr
lsconn
lsdev
lsparent
mkdev
restbase
rmdev
savebase
022 0514-022 Error Recovery Information
031 0514-031 Error Recovery Information
040 0514-040 Error Recovery Information
047 0514-047 Error Recovery Information
050 0514-050 Error Recovery Information
060-061 cfgmgr
062 cfgmgr
0514-062 Error Recovery Information
063 cfgmgr
0514-063 Error Recovery Information
064-076 cfgmgr

© Copyright IBM Corp. 2003, 2004 73

081-090 chdev
lsattr
lsconn
lsdev
lsparent
mkdev
restbase
rmdev
savebase
200-219 bootlist
400-405 iostat
410-419 chcons
430-431 lscons
516 0514-516 Error Recovery Information
521 0514-521 Error Recovery Information
534 mkdev
rmdev
chdev
535 mkdev
600-613 cfgmgr

Detailed Information for Message Component 0514

0514–018 The values specified for the following attributes are not valid
Problem determination: From the command line, you specified an attribute that is out of the range of legal values.
User response: Verify the attributes in your command to be sure they are in legal range by running the lsattr -R
command to display the range of legal attribute values for that specific device, run your command with the correct
attributes.
Problem determination: The Object Data Management (ODM) database is damaged.
User response: Verify that your ODM database is not damaged. If it is, do the following:
1. Try replacing the PdAt file by copying the PdAt file from another system that has the same release level as your
system, either through the network by running the ftp command or through a diskette by using the backup and
restore commands.
2. Restore the file, making sure that it preserves the permission code, ownership, and the location of your previous
file.
3. Reenter your command.

0514–022 The specified connection is not valid

Problem determination: Using System Management Interface Tool (SMIT), you supplied an invalid connection
location to define a device or make a device available.
User response: Using SMIT, supply a valid connection location by doing the following:
1. Return to the SMIT screen where the error occurred.
2. Locate the screen containing the PORT number field. You might need to select Cancel to page back through the
screens.
3. Position the cursor in the PORT number field of this screen and select List to display a list of valid connection
locations.
4. Select the desired connection location from the list.
5. Select Do to insert the correct value into the PORT number field.
Problem determination: From the command line, you specified an invalid connection location with the mkdev
command to define a device or make a device available.

74 Message Center Reference

User response: Locate a valid connection location, then use it with the mkdev command as follows:
1. Enter the lsconn -p command to list the valid connection locations.
2. Select a connection location from the list.
3. Reenter the mkdev command using the new connection location.

0514–031 A device is already configured at the specified location

Explanation: You attempted to add a device at a location that is already occupied by a different device.
User response: Determine which device occupies the location, and either remove it or find a new location for the
new device by doing the following:
1. Select the System Management Interface Tool (SMIT) Devices -> List Devices -> List All Defined Devices menu
option. SMIT displays the name, status, location, and description of all defined devices. The device status is one of
the following:
v Available: The device is defined and configured.
v Defined: The device is currently defined but not configured. The location is still reserved for the device and no
other device can be added at that location.
v Undefined: The system does not recognize the device.
2. Choose the location where you want to add the device, or choose a location where you want to add the device.
3. Use the lsdev command to determine which device currently occupies the specified location, as follows:
lsdev -C | grep aa-bb-cc-dd

where aa-bb-cc-dd is the location code (found in step 1). The location code can range from 2 to 12 characters in
length. The name of the device is displayed, along with its present status.
4. With the information from steps 1 and 2, either delete the existing device from the specified location and add the
new device, or add the new device at a different location.

0514–040 Error initializing a device into the kernel

Problem determination: You were unable to configure a specific device. While trying to initialize your device driver,
you were unable to load it as part of the kernel extension. The specific device driver file in the /etc/drivers file is
damaged or contains software errors.
User response:
v If you are modifying your configuration method or device driver, check for possible software errors.
OR
v If you suspect that the device driver is damaged, try replacing the device driver file by doing the following:
1. Copy the device driver file from another system that has the same release level as your system, either through
the network by running the ftp command, or through a diskette by using the backup and restore commands.
When you restore the file, make sure that it preserves the permission code, ownership, and location of your
previous file.
2. Enter your command again.
Problem determination: Your Object Data Management (ODM) database file is damaged, and you are unable to
configure your device.
User response: If you suspect that the ODM database is damaged, try replacing the PdAt file by doing the
following:
1. Copy the PdAt file from another system that has the same release level as your current system, either through the
network by running the ftp command, or through a diskette by using the backup and restore commands. When
you restore the file, make sure that it preserves the permission code, ownership, and location of your previous file.
2. Enter your command.

Chapter 14. Message Component 0514 75

0514–047 Cannot access a device
Problem determination: You specified the wrong connection address to make a device available.
User response:
v Verify that your device has the correct connection address. If your device is connected to a SCSI card, the number
is on the back of the device. This number is a single-digit number. To convert it to a connection number, add a 0
(zero) digit to this number; that is, if the number is 1 (one), the connection number is 10, and if the number is 2, the
connection number is 20.
OR
v Verify that no other device attached to the SCSI card has the same connection number as your device. Use the
lsdev command to check the connection numbers of the devices attached to the SCSI card. If there is one number
that matches your connection number, change the number on the back of your device to a unique number. If you
are using SMIT, return to the SMIT screen where the error occurred and enter the appropriate connection number.
Otherwise, reenter the mkdev command with the appropriate connection address.
Problem determination: The device that you are trying to add is not attached to your system or has hardware
problems.
User response: If your device is connected to a serial port, check to see if it is plugged in to the correct serial port,
then rerun your command. If you suspect there is a hardware problem, do the following:
1. Verify that your cables are attached correctly.
2. Verify that your device is turned on.
3. Run diagnostics by using the diag command.

0514–050 Cannot perform the requested function because the specified device was not detected
Explanation: The device you are trying to add is not attached to your system or has hardware problems.
User response: If your device is connected to a serial port, check to see if it is plugged in to the correct serial port,
then rerun your command. If you suspect there is a hardware problem, do the following:
1. Verify that your cables are attached correctly.
2. Verify that your device is turned on.
3. Run diagnostics by using the diag command.

0514–062 Cannot perform the requested function because the specified device is busy
Explanation: You specified a device that is being used by one or more processes.
User response: Verify that you selected the correct device. If that is not the problem, remove the process that is
allocating your device by doing the following:
1. Run the ps -ef command to determine which process is using the device you specified.
2. Remove the process by using the kill command.

If your device is still busy, run your command in single-user mode by doing the following:
1. Run the shutdown -m command. Wait for the login prompt.
2. After you log in, rerun your command.

If that does not resolve the problem, reboot your system by doing the following:
1. Use the sync command to update your i-node table.
2. Run the shutdown -Fr command. Wait for the login prompt.
3. After you log in, rerun your command.

0514–063 The specified device driver name is too long

Problem determination: The name of the device driver you want to configure is too long. The device name must be
fewer than 20 characters in length in order to be added to the CuDvDr Object Data Management (ODM) database file.
User response: Change the name of your device driver to a name with fewer than 20 characters.

76 Message Center Reference

Problem determination: Your libcfg.a library file is damaged.
User response:
1. Replace the libcfg.a library file by copying the libcfg.a file located on your /lib directory from another system that
has the same release level as your current system, either through the network by running the ftp command, or
through a diskette by using the backup and restore commands. If you use the ftp command, use the bin
subcommand. When you restore the file, make sure that it preserves the permission code, the ownership, and the
location of your previous file.
2. Reenter your command.

0514–516 Device configuration database lock service timed out

Explanation: You ran a command that tried to access a Configuration Object Data Management (CODM) file that is
presently in use or was closed incorrectly.
User response:
v Run the df command to determine if there is a process currently using any CODM file. If there is, wait until the
process is completed and reissue your command.
v If you suspect that the CODM file was incorrectly closed, do the following:
1. Run the cd command to go to the /etc/objrepos directory.
2. Rename the config_lock file to config_lock.old using the mv command.
3. Reissue your command.

0514–521 Cannot find information in the predefined device configuration database for the customized
device: DeviceName
Explanation: Your predefined device configuration database PdDv file, located in the /usr/lib/objrepos file, is
damaged.
User response:
1. Replace the PdDv file by copying the PdDv file from another system that has the same release level as your
current system, either through the network by running the ftp command, or through a diskette, by using the
backup and restore commands. When you restore the file, make sure that it preserves the permission code,
ownership, and the location of your previous file.
2. Reenter your command.

Chapter 14. Message Component 0514 77

78 Message Center Reference
Chapter 15. Message Component 0516
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-699 chlv
chpv
cplv
exportvg
extendlv
extendvg
importvg
lslv
lspv
lsvg
migratepv
mklv
mklvcopy
mkvg
reducevg
reorgvg
rmlv
rmlvcopy
syncvg
varyoffvg
varyonvg
0516-005 Error Recovery Information
0516-010 Error Recovery Information
0516-013 Error Recovery Information
0516-022 Error Recovery Information
0516-304 Error Recovery Information
0516-306 Error Recovery Information
0516-320 Error Recovery Information
0516-366 Error Recovery Information
0516-404 Error Recovery Information
700-719 chlv
720-725 chpv
730-732 chvg
740-759 cplv
760-773 exportvg
774-784 importvg
785-789 extendlv
0516-787 Error Recovery Information
790-799 extendvg
0516-794 Error Recovery Information
800-819 migratepv
820-839 mklv
0516-822 Error Recovery Information
840-859 mklvcopy
860-879 mkvg
880-899 reducevg
910-919 rmlv

© Copyright IBM Corp. 2003, 2004 79

920-925 rmlvcopy
930-939 syncvg
940-945 varyoffvg
950-959 varyonvg
0516-952 Error Recovery Information
960-990 reorgvg
992-1034 lslv
lspv
lsvg
0516-1034 Error Recovery Information

Detailed Information for Message Component 0516

0516–005 String: The physical volume is already a member of the requested volume group
Problem determination: You attempted to add a physical volume to a volume group, but you specified a physical
volume that is already a member of the volume group.
User response: Ensure that the physical volume you specified is not already a member of the volume group by
doing the following:
1. Enter the lsvg -p VolumeGroupName command to list the members of the volume group.
2. Reenter the extendvg command to add a physical volume to a volume group, and specify a valid physical volume
that is not a member of the volume group.
3. Update the ODM database with information from the VGDA.
Problem determination: You attempted to add a physical volume to a volume group, and a discrepancy exists
between the volume group descriptor area (VGDA) and the Object Data Manager (ODM). If the VGDA does not match
the ODM, the 0516-320 error message displays, even though the physical volume is actually a member of a volume
group.
User response: If the physical volume is a member of the volume group but error message 0516-320 is displayed
anyway, enter the following command to update the ODM database with information from the VGDA. The VGDA
contains current information.
redefinevg -d PhysicalVolumeName VolumeGroupName

0516–010 Volume group must be varied on: use varyonvg command

Explanation: You specified a volume group that is currently unavailable on your system.
User response:
v Check for misspelling in the volume group name you specified.
v Make your volume group available by doing the following:
1. Use the lsvg command to verify whether your volume group is available.
2. If the volume group is not available, use the varyonvg command to make it available.
v Check to see if one of the disks in the volume group is available by doing the following:
1. Run the lspv command.
2. If the disk is not available, issue the mkdev command to make the disk available, and run the varyonvg
command to make the volume group available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command. It might
be necessary to use the Object Data Manager (ODM).

0516–013 The volume group cannot be varied on because there are no good copies of the descriptor area
Explanation: Most of the volume group descriptor area (VGDA) cannot be accessed or is damaged.
User response:
v Verify that one of the disks where the volume group is located is available by doing the following:

80 Message Center Reference

 1. Issue the lspv command to see if the disk is available.
2. If the disk is not available, issue the mkdev command to make it available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.
4. If the disk is available, run the odmdelete command to delete the damaged volume group from the
configuration database by typing the following on the command line:
odmdelete -q name=VolumeGroupName -o CuAt
5. Use the System Management Interface Tool (SMIT) to add a new volume group.

OR
v Shut down your system and check for any loose or faulty cables around the fixed-disk area by doing the following:
1. Check your adapters and power sources.
2. Reboot your system and enter your command again.

OR
v For volume groups with multiple physical volumes, do the following:

Note: This procedure should be used as a last resort because data integrity cannot be guaranteed.
1. If the varyon operation reports a missing physical volume, use the chpv -vr command to temporarily remove
the volume from the volume group.
2. Reissue your command to make the volume group partially available.
3. After the problem is corrected and the physical volume is brought back online, issue the chpv -va command to
return the physical volume and make it available again to the volume group.

0516–022 Illegal parameter or structure value

Problem determination: The Object Data Management (ODM) database was damaged, and the physical volume ID
(pvid) of a disk was listed as None.
User response: Verify that the disk is recognized by the system by typing the following on the command line:
lqueryvg -p hdisk# -At
Problem determination:
v One of your Customize Device Configuration database files was damaged, and while you ran your command, the
file collected illegal parameters or structure values.
OR
v You attempted to create a logical volume with System Management Interface Tool (SMIT), or from the command
line with the mklv command. The physical volume name specified was not configured.
User response: Deactivate the volume group by doing the following:
1. Use the lsvg -o command to determine if your volume group is active.
2. If it is active, run the varyoffvg command.
3. Remove the definition of the volume group from the system by using the exportvg command.
4. Add the definition of the volume group to the system by using the importvg command.

0516–304 Unable to find device ID in the Device Configuration Database

Explanation: One of your Customize Device Configuration database files was damaged, and while you ran your
command, this file collected illegal parameters for the device ID.
User response:
1. Deactivate the volume group. Use the lsvg -o command to find out if your volume group is active. If it is active,
run the varyoffvg command.
2. Remove the definition of the volume group from the system by using the exportvg command.
3. Add the definition of the volume group to the system by using the importvg command.
4. Activate the volume group by using the varyonvg command.

Chapter 15. Message Component 0516 81

0516–306 Unable to find VolumeGroupName VolumeGroupDescription in the Device Configuration Database
Explanation: You issued one of the following commands:
v extendvg
v getlvodm
v lsvg
and the specified device does not exist in the Object Data Manager (ODM) database.

Note: The getlvodm command is an internal command only.

User response: Ensure that the device is defined in the database by doing the following:
1. Enter the lsdev -C command to display a list of devices defined in the database.
2. If the device is not listed, use one the following methods to define it, depending on the type of device:
v Define a physical volume using the mkdev command or the SMIT Devices --> Fixed Disk --> Add a Disk
menu option.
v Define a logical volume using the mklv command or the SMIT Physical and Logical Storage --> Logical
Volume Manager --> Volume Groups --> Add a Volume Group menu option.

0516–320 ProgramName: Physical volume String is not assigned to a volume group

Explanation: You issued one of the following commands:
v getlvodm
v lspv
v lsvg
and the specified physical volume is not assigned to a volume group in the Object Data Manager (ODM) database.

Note: The getlvodm command is an internal command only.

User response: Ensure that the physical volume is defined in your system and its name is spelled correctly in the
ODM database by doing the following:
1. Enter the lsvg command to list all the volume groups defined in your system.
2. Enter the lsvg -p VolumeGroupName command to list all the physical volumes in the specified volume group.
3. Ensure that the physical volume name is spelled correctly. For information on editing the ODM database, see
Object Data Manager (ODM) in AIX 5L Version 5.3 General Programming Concepts: Writing and Debugging
Programs.
4. If the physical volume is undefined or its name misspelled, add the correct physical volume in one of the following
ways:
v With the System Management Interface Tool (SMIT), use the Physical and Logical Storage--> Define a Fixed
Disk to the Operating System menu option to add the physical volume to the volume group. Then select one
of the following menu options to add the definition of the physical volume to a volume group:
– Add a Fixed Disk to an Existing Group
– Add a Fixed Disk without Data to a New Group
– Add a Fixed Disk with Data
v From the command line, use one of the following commands:
– mkvg: Creates a new volume group containing the physical volume.
– extendvg: Defines a physical volume to an existing volume group.
– importvg: Imports a new volume group definition from a set of physical volumes.

Note: Use the importvg command only if the volume group definition was previously exported using the
exportvg command.

82 Message Center Reference

0516–366 Volume group VolumeGroupName is locked. Try again
Problem determination: You ran a command that tried to access a Configuration Object Data Management file that
was in use or was closed incorrectly.
User response: Log in as the root user and run the odmdelete command to remove the lock from the configuration
database by typing the following on the command line:
odmdelete -q name=VGname and attribute=lock -o CuAt
Problem determination: The installation of a software product was interrupted, causing the system to lock the root
volume group.
User response: Reissue your command.

0516–404 Not enough resources available to fulfill allocation

Problem determination: You used the mklv or extendlv command, specifying a physical volume without enough
partitions (free space) to fulfill the requested logical volume size.
User response: Allocate enough disk space by specifying different characteristics by doing one of the following:
v Enter the mklv or extendlv command and specify a different physical volume, ensuring that the physical volume
specified includes enough free partitions to fulfill the requested logical volume size.
v Enter the mklv or extendlv command specifying fewer partitions to be allocated for the logical volume.
v Do not specify a physical volume. If you do not specify a physical volume, the command uses all the physical
volumes available in the volume group.
Problem determination: You used the mklv or extendlv command without specifying a physical volume, and the
volume group specified does not have enough free partitions (free space) to fulfill the requested logical volume size.
User response: Add or create more disk space by doing one of the following:
v Add another physical volume (fixed disk) to the volume group.
v Delete an unused logical volume.

0516–787 extendlv: Maximum allocation for logical volume Name is Value

Problem determination: Using System Management Interface Tool (SMIT), you specified a value in the Number of
ADDITIONAL logical partitions field to try to increase the logical volume size beyond the maximum number of logical
partitions.
User response: Use SMIT to change the number of logical volume partitions by using the SMIT Physical and
Logical Storage--> Logical Volume Manager--> Logical Volumes--> Set Characteristic of a Logical Volume-->
Change a Logical Volume menu option to specify a new number of logical partitions in the MAXIMUM NUMBER of
LOGICAL PARTITIONS field.

Note: You must change the number of logical volume partitions before you can extend or increase the logical volume.
Problem determination: From the command line, you used the extendlv command (or the chfs command, which
calls the extendlv command) to try to increase the logical volume size beyond the maximum number of logical
partitions.
User response: Use the chlv command to change the number of logical volume partitions by doing the following:
1. Increase the maximum number of logical volume partitions for the named logical volume with the chlv command,
as follows:
chlv -x MaximumLogicalPartitions LogicalVolumeName
2. Rerun the chfs command or the extendlv command.

Note: You must change the number of logical volume partitions before you can extend or increase the logical volume.

Chapter 15. Message Component 0516 83

0516–794 String not configured. Please configure the disk before trying this command again
Problem determination:
v You used the System Management Interface Tool (SMIT) to add an undefined physical volume to the volume group,
but the physical volume specified is not defined or installed on the system, or does not exist.
OR
v From the command line, you used the mkvg or the extendvg command to add an undefined physical volume to the
volume group.
User response:
1. Use one of the following procedures to define the disk:
v Use the following SMIT menu option to define the disk: Devices--> Fixed Disk--> Add a Disk.
v Use the mkdev command to define a disk.
2. After the disk is defined, you can add it to an existing volume group or use it to create a new volume group.

Note: The mkvg and extendvg commands are for disks without data. If the disk contains data, use the importvg
command rather than the mkvg command or the extendvg command.

0516–822 Unable to create logical volume

Problem determination: You specified a logical volume name that already exists.
User response: Give your logical volume a name not already in use by doing the following:
1. List all of the current logical volumes by issuing the following command:
lsvg -o| lsvg -i -1
2. Rerun your command with the correct logical volume name.
Problem determination: You specified a volume group that currently does not have enough disk space for your
logical volume.
User response: Check the disk space in your volume group by doing the following:
1. Run the lsvg command to check how many free partitions you have available in your volume group.
2. Rerun your command with the correct number of partitions or correct volume name.
Problem determination: You specified a volume group that is currently unavailable on your system.
User response:
v Verify that your volume group is available.
v Verify that one of the disks in the volume group is available by doing the following:
1. Check to see if the disk is available by using the lspv command.
2. If the disk is not available, issue the mkdev command to make the disk available, then run the varyonvq
command to make the volume group available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.

0516–952 Unable to vary on volume group uvgl

Explanation: You specified a volume group that is currently unavailable on your system.
User response:
v Check for misspelling in the volume group name you specified.
v Verify that one of the disks in the volume group is available by doing the following:
1. Check to see if the disk is available by using the lspv command.
2. If the disk is not available, issue the mkdev command to make it available, then run the varyonvq command to
make the volume group available.
3. If you are unable to make the disk available, run hardware diagnostics by issuing the diag command.

84 Message Center Reference

0516–1034 Not enough physical partitions in physical volume String.
Explanation: This message is reported during an extendlv operation on a striped logical volume if all the physical
partitions on the smallest hdisk have been consumed. Even if there are free partitions on some of the larger disks
containing the logical volume, those free partitions will not be used because the stripe width (that is, the number of
disks being striped across) must remain consistent throughout the entire logical volume.

Chapter 15. Message Component 0516 85

86 Message Center Reference
Chapter 16. Message Component 0517
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-022 chps
lsps
mkps
rmps
swapon
030-031 chps
040-044 lsps
050-051 mkps
060-062 rmps
070-072 swapon

© Copyright IBM Corp. 2003, 2004 87

88 Message Center Reference
Chapter 17. Message Component 0518
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-025 odmcreate
100-105 odmdrop
200-217 odmchange
300-307 odmdelete
401-417 odmadd
501-509 odmget
601-603 odmshow

© Copyright IBM Corp. 2003, 2004 89

90 Message Center Reference
Chapter 18. Message Component 0519
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-004 odmadd
odmchange
odmcreate
odmdelete
odmdrop
odmget
odmshow
0519-002 Error Recovery Information

Detailed Information for Message Component 0519

0519–002 The CLASS_SYMBOL does not identify a valid object class

Problem determination:
v You specified an invalid parameter, path name, or permission in the profiles load file used to convert the Systems
Network Architecture (SNA) profile.
OR
v The profiles load file does not exist.
User response: If you are having a problem with the profiles load file, import a new profiles load file that contains
valid information by doing the following:
1. Use the print command in the SNA configuration file to send the profiles to a file.
2. Move the created file to the desired system.
3. Enter the following on the command line:
awk -f /usr/lpp/sna/bin/sna_update.awk profiles.rt > profiles.r s
4. Enter the following on the command line:
importsna -l profiles.rs -e profiles.err
Problem determination: The Object Data Manager (ODM) files for SNA Services have been damaged.
User response: Remove all SNA Services profiles from the ODM database and import them again by doing the
following:
1. Enter the following commands to remove all SNA Services from the ODM database:
cd /usr/lpp/sna/objrepos
rm */usr/lpp/sna/bin/peu
2. Enter the following command to import the profiles again:
importsna -l profiles.rs -e profiles.err

© Copyright IBM Corp. 2003, 2004 91

92 Message Center Reference
Chapter 19. Message Component 0551
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001, 105-106 date

0551-001 Error Recovery Information
0551-006 Error Recovery Information
007-008 lastcomm
009-010 time
011 tty
012-014 who
026-033 uname
034-070 gprof
071-085 prof
092-100 sa
0551-099 Error Recovery Information
101 date
102-103 sa
104-113 sadc
117 vmstat
118 vmstat
0551-118 Error Recovery Information
119 vmstat
0551-119 Error Recovery Information
120-130 vmstat
0551-128 Error Recovery Information
131 w
150-154 iostat
0551-154 Error Recovery Information
200-204 sar
0551-203 Error Recovery Information
0551-201 Error Recovery Information
205 timex
206-207 sar
208 timex
209-211 sar
212 timex
213 sar
0551-213 Error Recovery Information
250-257 sysline
0551-250 Error Recovery Information
0551-256 Error Recovery Information
0551-257 Error Recovery Information
300 whoami
400-404 date
0551-404 Error Recovery Information

© Copyright IBM Corp. 2003, 2004 93

Detailed Information for Message Component 0551

0551–001 Character is not a recognized field descriptor

Explanation: You specified a field descriptor that is not supported by the date command.
User response: Reenter the date command with valid field descriptors. For more information on valid field
descriptors, see the date command.

0551–006 Cannot reach the time server; time set locally

Explanation: You attempted to set the date or time using the date command on a machine controlled by timed
daemons, but the attempt failed because of a network problem.
User response: Verify network connectivity by entering the ping MachineName command to determine the
availability of a particular machine on the network. Press the Ctrl-C key combination to stop the ping command. If the
ping command indicates that the machines are not communicating or that data is being lost, a network problem exists.

Note: The timed daemon should be controlled using the System Resource Controller (SRC) or the System
Management Interface Tool (SMIT). Entering the timed daemon on the command line is not recommended.

0551–099 The Character flag is not valid

Explanation: You specified an invalid flag or combination of flags with the sa command.
User response: As root user, reenter the sa command with a valid flag by doing the following:
1. Use the su command to change to the root user if necessary.
2. See the sa command for a list of valid flags.
3. Reenter the sa command with a valid flag or flag combination.

0551–118 The interval value is not valid

Explanation: You specified an invalid interval value using the vmstat command.
User response: Reenter the command, specifying a valid interval value. The vmstat command requires a positive,
nonzero interval value.

0551–119 The count value is not valid

Explanation: You specified an invalid count value using the vmstat command.
User response:
v Reenter the vmstat command, specifying valid interval and count values. The vmstat command requires a positive,
nonzero integer for a count value.
v Reenter the vmstat command, specifying a valid interval value and no count value. When no count value is
specified, the vmstat command generates output at the specified interval until you stop the command by entering
the Ctrl-C key combination.

0551–128 Drive Name is not found

Explanation: You used the vmstat command to specify a physical volume that does not exist.
User response: Specify a valid physical volume by doing the following:
1. Enter the getlvodm -C command to display a list of all valid physical volumes.

Note: The getlvodm command is an internal command. There is no man page available.
2. Reenter the vmstat command, specifying a valid physical volume or volumes.

94 Message Center Reference

0551–154 Disk Name is not found
Explanation: You entered the iostat command to report statistics on I/O activity on terminals or disks, but specified
a name that does not match any of the names on the internal list of disks.
User response: Supply valid physical volume names by doing the following:
1. Enter the getlvodm -C command to list all disk names.
2. Reenter the iostat command, specifying valid device names.

0551–201 Cannot open FileName

Explanation: You cannot open /usr/adm/sa/FileName using the sar command for one of the following reasons:
v The file does not exist.
v You do not have valid permissions on the file or the directory.
User response:
v If the file does not exist, create the file by doing the following:
1. Enter the su command to change to the root user.
2. Enter the /usr/lib/sa/sa1 command.
3. Reissue the sar command.
v Ensure that you have correct file and directory permissions by doing the following:
1. Enter the su command to change to the root user.
2. Enter the chmod 754 /usr/adm/sa command to obtain valid permissions on the directory.
3. Enter the chmod 644 /usr/adm/sa/FileName command to obtain valid permissions on the file.
4. Reissue the sar command.

0551–203 ending time (etime) <= starting time (stime)

Explanation: You used the sar command with the -e and -s flags to specify the starting and ending time for
reporting, but the specified ending time was less than or equal to the starting time.
User response: Ensure that the -e flag is greater than the -s flag when using the sar command.

0551–213 Try running /usr/lib/sa/sa1 IncrementNumber

Explanation: You entered the sar command to extract the contents of the /usr/adm/sa/saDD/FileName file that was
not previously created.
User response: Create the /usr/adm/sa/saDD/FileName file using the sa1 command by doing the following:
1. Use the su command to change to the root user.
2. Enter the /usr/lib/sa/sa1 IncrementNumber command with the correct increment and number settings.
3. Reenter the sar command.

0551–250 The argument String is not valid

Explanation: You specified an invalid command line argument for the sysline command.
User response: Enter a valid command line argument. For a list of valid arguments, see the sysline command in
AIX 5L Version 5.3 Commands Reference, Volume 5.

0551–256 There is no status capability for String

Explanation: You entered the sysline command, but the terminal type defined does not have status line capabilities.
User response: Define a terminal type that has status line capabilities by doing the following:
1. Use the env command to determine if the TERM environment variable is set correctly. If the variable is not set to a
terminal type that has status line capability, enter export TERM=TerminalType on the command line to reset the
variable.

Chapter 19. Message Component 0551 95

2. If the error message is still displayed, the terminal does not have screens to display the status line. For more
information on terminal types, see the terminfo file in AIX 5L Version 5.3 Files Reference.

0551–257 The Character option is not valid

Explanation: You specified an invalid option value for the sysline command.
User response: Enter a valid command line argument. For a list of valid arguments, see the sysline command in
AIX 5L Version 5.3 Commands Reference, Volume 5.

0551–404 Specified value of date/time is out of range

Explanation: You specified an invalid range value when using the date command.
User response: Use valid range of values with the date command. The following is a list of valid ranges for the date
command:

mm (01-12) Specifies the month

dd (01-31) Specifies the day
HH (00-23) Specifies the hour
MM (00-59) Specifies the minute
SS (00-59) Specifies the second
YY (00-37) Specifies the year from 2000 to 2037
YY (70-99) Specifies the year from 1970 to 1999

96 Message Center Reference

Chapter 20. Message Component 0602
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-144 ex
145 vi
0602-145 Error Recovery Information
146-173 ex
174 ctags
300-366 ed
400-429 sed
500-595 awk

Detailed Information for Message Component 0602

0602–145 There are no preserved files

Explanation: You attempted to recover a file with the vi -r command, and there are no saved files.
User response: Verify that you entered the correct file name.

© Copyright IBM Corp. 2003, 2004 97

98 Message Center Reference
Chapter 21. Message Component 0652
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-002 fgrep
003-006 egrep
007-031 find
0652-019 Error Recovery Information
032-035 grep
0652-033 Error Recovery Information
036 head
037-039 look
040-041 od
042-043 tail
044 tee
045-048 touch 0652-048 Error Recovery Information
049-054 cat
0652-050 Error Recovery Information
055-080 bfs
081-084 find
088 head
100-108 more
110-139 pg
140-141 which
142 strings

Detailed Information for Message Component 0652

0652–019 The status on FileName is not valid

Problem determination: The system looked for a file that either does not exist or was specified incorrectly.
User response: Ensure that the file exists and verify the file name.
Problem determination: The system looked for a file for which you do not have write permission.
User response: Add write permission to the file or parent directory. You might need to run the su command to
change to the root user in order to add the appropriate permission.

0652–033 Cannot open FileName

Problem determination: You used the grep command to search a file for which you do not have read permission.
User response: Obtain read permission for the file by doing the following:
1. Use the li -l command to determine access and ownership permissions on the file.
2. Change to the root user, then use the chmod command to add read permission to the file.
Problem determination: You used the grep command to search a file, and you do not have execute permission for
one or more of the parent directories containing the file.
User response: Establish execute permission for the directories containing the file by doing the following:

© Copyright IBM Corp. 2003, 2004 99

1. Determine which directory is causing permission problems by running the cd ParentDirectory command, where
ParentDirectory is the parent directory of the file in question. If the cd command displays an access error, rerun
the command using the parent directory of the directory specified in the previous usage of the cd command.
2. Repeat this process until the cd command changes to the specified directory without returning an error. The child
of this directory is the directory that is causing access problems.
3. Use the ls -l command to determine the access permissions and ownership of the directory.
4. If you do not have access permission to a file or directory, run the su command to switch to the root user or owner
of the file or directory.
5. Use the chmod command to give yourself the correct permissions, or ask the owner or system administrator to
give you the correct permissions.

Note: You might need to repeat one or both of the recovery procedures presented here because permission problems
might exist in multiple directories under which the file resides.

0652–048 Cannot change the modification time on FileName or DirectoryName

Explanation: You used the touch command to change the time stamp information on a file or a directory for which
you do not have write permission.
User response: Establish write permissions on the file by doing the following:
1. Determine the current ownership of the file or directory by running the ls -dl Name command, where Name
specifies the file or directory.
2. If you do not have access permission to a file or directory, run the su command to switch to the root user or owner
of the file or directory.
3. Use the chmod command to give yourself the correct permissions, or ask the owner or system administrator to
give you the correct permissions.

0652–050 Cannot open FileName

Explanation: You attempted to use the cat command on a file that is in the process of being downloaded.
User response: Wait until the file has finished downloading, then rerun your command.

100 Message Center Reference

Chapter 22. Message Component 0653
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-010 bdiff
015-016 chroot
023 cmp
030-031 colrm
038 comm
050-079 compress
100-116 csplit
130-137 cut
145-146 devnm
155-156 dircmp
175-178 du
190-192 expand
197 fold
200-210 format
230-249 install
270-276 install command (BSD)
285-290 join
293-294 link
300-310 li
0653-309 Error Recovery Information
340-345 ls
0653-341 Error Recovery Information
355-358 mkdir
360-361 mknod
400-403 mv
0653-401 Error Recovery Information
417-424 ln
433-440 cp
451-457 newform
465-471 nl
480-483 paste
500-513 pack
535-540 pcat
550-556 pr
565-572 proto
582 rev
600-603 rm
0653-603 Error Recovery Information
606-607 del
609 rm
0653-609 Error Recovery Information
610-611 rmdir
del
rm
0653-611 Error Recovery Information

© Copyright IBM Corp. 2003, 2004 101

612 del
625-635 sdiff
645-658 sort
0653-650 Error Recovery Information
0653-657 Error Recovery Information
680-685 split
690-691 sum
700-702 tab
710-717 tr
720-723 uniq
730-741 unpack
755 wc
775-776 tr
800-827 diff
860-866 diff3
900-906 file

Detailed Information for Message Component 0653

0653–309 Cannot open the directory Name

Explanation: When using the ls command, access to a directory was denied because of incorrect user permission.
User response: Determine the current directory ownership and obtain the correct user permissions by doing the
following:
1. Run the ls -ld DirectoryName command to determine ownership and permissions for the directory.
2. If you do not have access permission to a file or directory, run the su command to switch to the root user or owner
of the file or directory.
3. Use the chmod command to give yourself the correct permissions, or ask the owner or system administrator to
give you the correct permissions.

0653–341 The file FileName does not exist

Explanation: You attempted to access a file or a directory that is not in your current directory or in the directory that
you specified.
User response:
v Verify that you entered the correct file name, directory, or path name.
v Issue the mount command to ensure that all file systems are mounted, then use the mount command to mount the
file system you need.

0653–401 Cannot rename String1 to String2

Problem determination: The source file or source directory that you attempted to move or copy does not exist.
User response: Verify the location and the name of the source file or directory, as follows:
1. Use the ls command to verify that the file or directory to be moved or copied exists.
2. Run the cp or mv command, using a valid file or directory name to copy or move the file.
Problem determination: You do not have read and write permissions to move or copy the source file or directory
that you specified.
User response: Obtain the correct read or write permissions, as follows:
1. Use the ls -al command to determine access permissions of each directory or file involved. For more information,
see File and Directory Access Modes in CHECK THIS LINK--was AIX 5L Version 5.3 System User’s Guide:
Operating System and Devices.

102 Message Center Reference

2. If you do not have access permission to a file or directory, run the su command to switch to the root user or owner
of the file or directory. Then use the chmod command to give yourself the correct permissions, or ask the owner
or system administrator to give you the correct permissions.
3. Enter the cp or mv command to copy or move the file.

0653–603 Cannot remove directory DirectoryName

Explanation: You attempted to remove a directory that contains files.
User response: Do one of the following:
v Remove the files in the directory and try again.
v Force the deletion of the directory and its files by running the rm -r command as follows:
rm -r DirectoryName

0653–609 Cannot remove FileName

Explanation: You attempted to remove a file for which you do not have write permission by overriding the write
protection.
User response: Establish write permissions on the file by running the ls -dl Name command, where Name specifies
the file or directory, then running the chmod command.

0653–611 Directory DirectoryName is not empty

Explanation: You attempted to remove a directory with the rmdir command, but the directory contains files.
User response:
v Remove the files in the directory and run the rmdir command again.
v Force the deletion of the directory and its files by running the rm -r command as follows:
rm -r DirectoryName

0653–650 Cannot locate the temporary directory or /tmp

Problem determination: The sort command could not create its temporary files because the /usr/tmp and /tmp
directories do not exist.
User response: Use the mkdir command to create the /usr/tmp and /tmp directories.
Problem determination: The sort command could not create its temporary files because you do not have write
permission to the /usr/tmp and /tmp directories.
User response: Establish write permission to the /usr/tmp or /tmp directories, as follows:
1. Use the su command to change to the root user. If you already own the /usr/tmp or /tmp directories, omit this
step.
2. Run the chmod 777 /tmp or the chmod 777 /usr/tmp command to gain write permission to the specified
directory.

Note: The chmod 777 command gives read, write, and execute permissions to all users. To avoid this situation,
see File and Directory Access Modes in CHECK THIS LINK--was AIX 5L Version 5.3 System User’s Guide:
Operating System and Devices for more information about files and directories.
Problem determination: You used the sort -T command to specify a directory that does not exist.
User response: Use the -T flag to specify an existing directory.
Problem determination: You used the sort -T command to specify a directory for which you do not have write
permission.
User response: As the root user or as a user with correct permissions, run the chmod 777 /DirectoryName
command to give yourself write permission to the directory specified by the -T flag.

Chapter 22. Message Component 0653 103

0653–657 A write error occurred while sorting
Problem determination: You used the sort command, and the file system became full, while the file was being
processed.
User response: Ensure that there is enough disk space for the sort to be completed, as follows:
1. Enter the df FileSystem command while the sort command is processing the file. The df command displays
information about space available on a file system.
The sort command creates temporary files in either the /usr/tmp directory or the /tmp directory. Writing is
unsuccessful if the file system containing the temporary directory becomes full. If you are not sure which directory
is used for temporary file storage, run the sort -T /usr/tmp FileName command to create the temporary files in the
desired directory.
2. If the sort fails because the file system containing the temporary directory is full, do one of the following:
v Use a directory in a file system that has more space.
v Increase the file system size by using the chfs command.
Problem determination: Write permission to the directory containing the temporary files was removed, while the sort
was in progress.
User response: Verify that you have write permission on the directory containing the temporary files by running the
ls -la DirectoryName command to list permissions. Use the chmod 777 command to change write permissions, if
necessary.

104 Message Center Reference

Chapter 23. Message Component 0654
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

100-110 dump
200-212 nm
301-306 size
400-425 strip
501-505 tsort
654-603 ranlib

© Copyright IBM Corp. 2003, 2004 105

106 Message Center Reference
Chapter 24. Message Component 0702
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001 cal
002-004 factor
005-008 units
009 cal

© Copyright IBM Corp. 2003, 2004 107

108 Message Center Reference
Chapter 25. Message Component 0703
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-037 learn
101-109 catman
201 man
203 man
301, 303-311 man

© Copyright IBM Corp. 2003, 2004 109

110 Message Center Reference
Chapter 26. Message Component 0705
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-005 bc
006-011 dc

© Copyright IBM Corp. 2003, 2004 111

112 Message Center Reference
Chapter 27. Message Component 0706
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-972 ld
0706-010 Error Recovery Information

Detailed Information for Message Component 0706

0706–010 Binder killed by signal Signal

Explanation: You ran out of memory while linking your object files.
User response: Do one of the following:
v Run the lsps command to verify that you have enough paging space. You can increase the paging space using the
smit command.
v Increase the default limits set by the /etc/security/limits file by doing the following:
1. Edit the /etc/security/limits file.
2. Increase the settings of the fsize, cpu, data, stack, core, and rss process resource limits for your user ID,
starting with the fsize parameter.
3. Run your command again.

© Copyright IBM Corp. 2003, 2004 113

114 Message Center Reference
Chapter 28. Message Component 0710
Messages 0710-010 through 0710-028 are associated with the virscan command.

© Copyright IBM Corp. 2003, 2004 115

116 Message Center Reference
Chapter 29. Message Component 0781
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

0781-001 qconfig
0781-002 through digest
0781-020 0781-012 Error Recovery Information
0781-017 Error Recovery Information
021-056 enq
0781-035 Error Recovery Information
0781-039 Error Recovery Information
0781-046 Error Recovery Information
0781-047 Error Recovery Information
0781-048 Error Recovery Information
0781-050 Error Recovery Information
057-058 pac
059-100 qdaemon
0781-063 Error Recovery Information
0781-088 Error Recovery Information
0781-100 Error Recovery Information
101-108 enq
0781-102 Error Recovery Information
0781-104 Error Recovery Information
109-175 cancel
digest
disable
enable
enq
lp
lpd
lpq
lpr
lprm
lpstat
lptest
pac
qadm
qcan
qchk
qdaemon
qpri
qprt
qstatus
rembak
0781-113 Error Recovery Information
0781-117 Error Recovery Information
0781-132 Error Recovery Information
0781-156 Error Recovery Information
0781-161 Error Recovery Information
0781-162 Error Recovery Information

© Copyright IBM Corp. 2003, 2004 117

176-194 chque
chquedev
lsallq
lsallqdev
lsque
lsquedev
mkque
mkquedev
rmque
lpd
rmquedev
0781-182 Error Recovery Information
0781-183 Error Recovery Information
0781-189 Error Recovery Information
0781-194 Error Recovery Information
195-219 lpd
0781-209 Error Recovery Information
220 enq
221-224 lpd
225-254 rembak
0781-254 Error Recovery Information
277 0781-277 Error Recovery Information
282 0781-282 Error Recovery Information
304 0781-304 Error Recovery Information
305 0781-305 Error Recovery Information
310 0781-310 Error Recovery Information
318-328 pac
0781-320 Error Recovery Information
0781-321 Error Recovery Information
329 enq
340-342 qdaemon
343 qdhld

Detailed Information for Message Component 0781

0781-012 No device line in queue stanza

Explanation: This error message displays when the digester attempts to digest the qconfig file and encounters a
problem in a device line. Error message 0781-017 always displays prior to this message.
These problems occur only when you edit the qconfig file directly. Changing the qconfig file with system commands
or the System Management Interface Tool (SMIT) does not cause these errors. The following problems can occur with
the device line:
Problem determination: The device line is missing from the qconfig file.
User response: If the device line is missing from the stanza, do the following:
1. Determine which file caused the error message by looking at the preceding error message.
2. Edit the ConfigFileName file with a text editor.
3. Add the device line immediately after the QueueName: line so that the two lines display as follows:
QueueName:
device = DeviceName1[, DeviceName2 . . . ]

Include a tab before the device keyword and one space on each side of the equal sign (=).

OR

118 Message Center Reference

 If the stanza containing DeviceName: is missing as well as the device line, delete the entire stanza containing the
QueueName: line.
4. Save the file.
Problem determination: The device line is incomplete (an element such as a keyword is missing).
User response: If the device line in the stanza is incomplete, do the following:
1. Determine which file caused the error message by looking at the preceding error message.
2. Edit the ConfigFileName file with a text editor.
3. Making sure that the spacing is correct, change the device line so that it matches the following format:
device = DeviceName1[, DeviceName2 . . . ]
4. Save the file.
Problem determination: The syntax of the device line is incorrect (the line breaks, tabs, or spaces are incorrect).
User response: If the syntax is incorrect in the device line in the stanza, do the following:
1. Determine which file caused the error message by looking at the preceding error message.
2. Edit the ConfigFileName file with a text editor.
3. Make sure that the order and spacing are correct in the device line and that the line matches the following format:
device = DeviceName1[,DeviceName2 . . . ]

Note: Make sure the device and backend lines include a tab before the device and backend keywords, and a
space before and after the equal sign (=).
4. Save the file
Problem determination: The device name is incorrect.
User response: If the device name is incorrect, do the following:
1. Determine which file caused the error message by looking at the preceding error message.
2. Edit the ConfigFileName file with a text editor, ensuring the device name is correct.
3. Save the file.

0781-017 Error in config file Name, line Number

Explanation: The digester encountered a problem in the qconfig file. Any command that calls the digest command
to create the qconfig.bin file can generate this message. A supplementary error message sometimes follows,
specifying the problem.
User response:
v Determine the nature of the error from the supplementary error message, if one exists, and follow the recovery
instructions for that message.
OR
Change the qconfig file and rerun the command that caused the error to display.
1. Change the qconfig file by using one of the following methods:
– Restore the backup of the qconfig file, if one exists. If no backup exists, edit the existing qconfig file.
– Use one of the following file-manipulating commands at the command line to change the qconfig file:
- chque
- mkquedev
- chquedev
- rmque
- mkque
- rmquedev
– Use options from the SMIT menus to edit the qconfig file.
– Edit the qconfig file directly, using a text editor, and then save the file.

Chapter 29. Message Component 0781 119

 Note: File-manipulating commands and System Management Interface Tool (SMIT) options do not make
changes directly to the qconfig file. Instead, they make changes to a temporary file. If the temporary file
is successfully digested by the digest command, the temporary file is copied to the qconfig file.
2. Rerun the original command that caused the error message to display.

0781–035 No such request in queue Name - perhaps it’s done?

Problem determination: Using the System Management Interface Tool (SMIT), you specified an invalid job number
to cancel a print job.
User response: Using SMIT, locate a valid job number and cancel the print job by doing the following:
1. Use the Spooler (Print Jobs)--> Cancel a Print Job menu option.
2. Type a valid queue name in the PRINT QUEUE field, or select List to list valid queue names.
3. Next to the JOB NUMBER field, select List to list valid job numbers.
4. Select a job number. If a job is not listed, it has already been processed or does not exist.
5. To delete the selected job, select Do.
Problem determination: From the command line, you specified an invalid job number with the qcan-x command or
the enq -x command.
User response: Using the qchk command, locate a valid job number, as follows:
1. Run the qchk -P(QueueName) command. The resulting display lists the job numbers and status for the specified
queue.
2. Specify a valid job number with the qcan -x or the enq -x command to cancel a print job.
Problem determination: You are not the owner of the job specified by the job number. If you are logged in as root
user, then this is not the cause of this error.
User response: Change to the owner of the file, or to the root user.
Problem determination: The job specified by the job number is already processed; therefore, it is not in the
specified queue. Run the su command to change to the root user or to the owner of the file. Then use SMIT or
commands to cancel the print job.
User response: The print job has been processed and cannot be canceled or queried.

0781–035 qdaemon appears to be dead

Explanation: The qdaemon subsystem is not running, and a command is issued to update or digest the
/etc/qconfig file.
User response: Shut down the qdaemon subsystem, then restart it, as follows:
1. Use the lssrc -a command to show the status of the defined subsystems. The qdaemon subsystem is active if it
is listed in the resulting table with a status of active.
2. If the qdaemon is listed as active, stop the qdaemon subsystem with the stopsrc -s qdaemon command.
3. Restart the qdaemon subsystem with the startsrc -s qdaemon command.
4. Verify that the qdaemon is running using one of the following methods:
v Use the ps - ef | grep qdaemon command to show the process status. The qdaemon is running if the
/etc/qdaemon file displays in the resulting list.
v Use the lssrc -a command to show the status of the defined subsystems.

0781–046 Illegal burst page option

Explanation: You specified an invalid burst page option using the enq -B command.
User response: Specify a valid burst page option, as follows:
1. Obtain a valid character pair for the page burst option from the -B flag section of the enq command.
2. Rerun the enq command, specifying a valid page burst option.

120 Message Center Reference

0781–047 Bad job number: String
Explanation: You used the enq -x command to cancel a print job, and entered a job number that does not
correspond to a job on the print queue.
User response: Rerun the enq -x command using a valid job number, as follows:
1. Run the lpstat command to obtain a list of valid job numbers.
2. Rerun the enq -x command, specifying a valid job number, to cancel the print job.

0781–048 Bad queue or device name: String

Explanation: You issued a print request to a nonexistent queue or device. This error message can occur when you
are using any of the following commands, each of which has an option to specify a print queue and printer device:
v cancel
v lprm
v disable
v qadm
v enable
v qcan
v enq
v qprt
v lpr
User response: Do one of the following:
v Determine the name of existing queues or printers, and rerun the command with valid specifications. At the
command line, type one or more of the following commands to get the information you need:
– lpstat to list all the queues and corresponding devices defined for the system.
– lsallq to list all configured queues.
– lsquedev to list all devices (printers) configured for a specified queue.
v Rerun the command without specifying a printer or printer-queue combination. This causes the print request to go to
the default queue, which is the first queue defined in the /usr/lib/lpd/qconfig file.

0781–050 Bad PRINTER or LPDEST env. variable String

Explanation: You used one of the following commands without specifying a print queue or printer device, and the
PRINTER and LPDEST environment variables specify nonexistent queues or devices:
v cancel
v lprm
v disable
v qadm
v enable
v qcan
v enq
v qprt
v lpr
User response: Ensure that the PRINTER or LPDEST environment variables specify valid queue or printer names.

Note: The system checks the LPDEST environment variable first; if it is set, it is used. If the LPDEST environment
variable is not set, the PRINTER environment variable is checked.
1. Determine the name of existing queues or printers by running one of the following commands at the command
line:
v lpstat to list all the queues and corresponding devices defined for the system.
v lsallq to list all configured queues.

Chapter 29. Message Component 0781 121

 v lsquedev to list all devices (printers) configured for a specified queue.
2. Change the value of the PRINTER or LPDEST environment variable in one of the following ways:
v If you are in sh (Bourne) shell, run one of the following commands:
PRINTER=NewValue; export PRINTER

OR
LPDEST=NewValue; export LPDEST
v If you are in csh (C) shell, run one of the following commands:
setenv PRINTER=NewValue

OR
setenv LPDEST=NewValue
v If you are in ksh (Korn) shell, run one of the following commands:
export PRINTER=NewValue

OR
export LPDEST=NewValue
3. Verify the current value of the PRINTER or LPDEST environment variables by running one of the following
commands:
echo $PRINTER

OR
echo $LPDEST

0781–063 Error reading FileName. Errno = Number

Problem determination:
v You ran the qadm command with the -K, -U, -D, or -X flag, which created a job description file with a length of 0
bytes, in the /var/spool/lpd/qdir directory.
v The error was generated when the qdaemon was started.
User response: Use the df /var command to check if the /var file system is out of space by doing the following:
1. Manually clear the /var/spool/lpd subdirectories of unnecessary files.
2. Run the qadm command again.

0781–088 Queue PrinterName went down, job is still queued:

Problem determination: You tried printing to a printer on a remote host, but your host name was not in either the
/etc/hosts.lpd file or the /etc/hosts.equiv file on the remote host.
User response: Ensure that your host name is in either the remote /etc/hosts.lpd file or /etc/hosts.equiv file. Use
the refresh command to implement the changes as follows:
refresh -h HostName -s lpd
Problem determination: You attempted to print to a remote printer, but the lpd daemon on the remote host was not
active.
User response: Use the startsrc command to start the lpd daemon on the remote printer as follows:
startsrc -h HostName -s lpd
Problem determination: The file name in the /etc/qconfig file has an incorrect queue device name. This caused a
write error, which caused the print queue to be lost.
User response: Ensure that the file name in the etc/qconfig file has the name of a valid print device. Run the qadm
command to restart the print queue.
qadm -U QueueName

122 Message Center Reference

0781–100 Failure to create QueueName
Explanation: This error message displays on the system console only.
Problem determination: Using the System Management Interface Tool (SMIT), you specified an invalid device name
when adding a queue device.
User response: Using SMIT, remove the invalid device name, enter a valid device name, and restart the qdaemon
subsystem by doing the following:
1. Go to the Devices--> Printer/Plotter--> Manage Local Printer Subsystem--> Local Printer Queue Devices-->
Remove a Queue Device menu option.
2. Select the queue from which to remove the device, and press Enter.
3. At the Remove a Queue Device screen, select List to list the devices in the queue.
4. Select the invalid device name and press Enter.
5. Go to the Devices--> Printer/Plotter--> Manage Local Printer Subsystem--> Local Printer Queue Devices-->
Add Another Local Queue Device to an Existing Queue menu option, and type a valid device name in the
NAME of device to add field.
6. Press the F6 key to verify that the device name following the -d flag is valid.
7. If the device name is invalid, select Cancel, type a valid device name, and press Enter.
8. Exit SMIT and return to the command line.
9. At the command line, use the startsrc -s qdaemon command to restart the qdaemon subsystem.
Problem determination: From the command line, you specified an invalid device name with the mkquedev
command when adding a queue device.
User response: From the command line, remove the invalid device name, enter a valid device name, and restart the
qdaemon subsystem.
1. Use the rmquedev command to remove the invalid device name, as follows:
rmquedev -q QueueName -d DeviceName . . .
2. Use the mkquedev command to enter a valid queue device name, as follows:
mkquedev -q QueueName -d DeviceName . . .
3. Use the startsrc -s qdaemon command to restart the qdaemon subsystem.

0781–102 Invalid printer name: String

Explanation: You issued a printer status request to a nonexistent queue or device using one of the following
commands:
v enq
v lpstat
v lpq
v qchk
User response:
v Reenter one of the commands without specifying a queue or queue-printer combination. The status of all valid
queues and associated printers is displayed.
OR
v Determine the names of existing queues or printers, and rerun the command with valid specifications. Use the
following commands to get the information you need.
– lsallq to list all configured queues.
– lsallqdev to list all devices (printers) configured for a specified queue.

0781–104 No queue devices detected

Explanation: A job was submitted to the queue with no queue device attached to it.
User response: Resubmit the job, specifying a valid queue device, as follows:
1. Use the enq -A command to list the available queue devices.

Chapter 29. Message Component 0781 123

2. Resubmit your job, specifying a valid queue device.

0781–113 Insufficient memory

Explanation: The system has run out of both virtual and real memory.
User response: Do one of the following:
v Remove any unnecessary processes from the system by doing the following:
1. Run the su command to change to the root user.
2. Run the ps -eaf command to list all processes currently on the system.
3. To remove any unnecessary processes, run the kill command.
v Add more page space with the System Management Interface Tool (SMIT) utility (Use the Physical and Logical
Storage option in the Main Menu).
v Add more physical memory.

0781–117 Cannot execute digester FileName

Problem determination: The /usr/lib/lpd/digest file does not exist.
User response: Verify that the /usr/lib/lpd/digest file exists, as follows:
1. Run the su command to change to the root user.
2. Run the cd /usr/lib/lpd command to change to the correct directory.
3. Run the ls -l digest command to verify that the file exists.
4. If the digest file does not exist, reload it from the original system software. See your system administrator for
assistance.
Problem determination: You do not have execute permission on the /usr/lib/lpd/digest file.
User response: Ensure that you have execute permission on the /usr/lib/lpd/digest file.

0781–132 Cannot open message file FileName

Problem determination: You used an invalid or incorrect message file path or specification with the qprt command.
User response: Specify a valid message file name when using the -M option, as follows:
1. Use the li -l FileName command to verify the existence of the specified message file.
2. If the message file does not exist, use an editor to create the desired file.
3. Reissue the qprt command, specifying a valid message file.
Problem determination: You do not have read access on the specified message file.
User response: Ensure that you have read access to the message file specified.

0781–156 Cannot find config file Name

Explanation: You issued the enq command, and the /etc/qconfig file does not exist.
User response: Ensure that the /etc directory contains a qconfig file, as follows:
1. Run the cd /etc/qconfig command to verify that the qconfig file exists in the /etc directory.
2. If the qconfig file does not exist, use the su command to change to the root user, and use an editor to create a
qconfig file.
3. Rerun the enq command.

0781–161 fatal: Argument PrinterID is not an accessible file

Problem determination: You attempted to print a file, but you do not have access permission for the file.
User response: Obtain access permission for the file you want to print.
Problem determination: You attempted to print a file, but you misspelled the file name.

124 Message Center Reference

User response: Verify the file name and try again.

0781–162 Cannot awaken qdaemon (request accepted anyway)

Explanation: The qdaemon is not running or has been stopped.
User response: Restart the qdaemon subsystem, as follows:
1. Run the startsrc -s qdaemon command.
2. Verify that the qdaemon is running by doing one of the following:
v Run the ps -ef | grep qdaemon command to display the process status.
OR
v Run the lssrc -a command to display the status of the defined subsystems.

0781–182 Problem with line Number in FileName

Explanation: The /etc/qconfig file has been damaged. The qconfig file contains printer queue information, and the
error is caused by the lsque or lsallq command.
User response: Correct errors in the /etc/qconfig file, as follows:
1. Run the cd /etc command to change to the /etc directory, where the qconfig file is located.
2. Using an editor, view the qconfig file and correct any errors you find.

0781–183 Cannot delete QueueName. Queue contains devices

Problem determination: Using the System Management Interface Tool (SMIT), you attempted to remove a queue,
but the queue contained associated devices.
User response: Using SMIT, remove the associated devices before removing the queue, as follows:
1. Select Devices--> Printer/Plotter-->Manage Local Printer Subsystem--> Local Printer Queue
Devices-->Remove a Queue Device.
2. Select the name of the queue you want to delete.
3. Select List to display a list of devices.
4. Select the queue device you want to remove.
5. Select Do to remove the queue device.
6. Repeat until all queue devices are removed.
7. After the devices have all been removed, use the following SMIT menu option to remove the queue:
Devices-->Printer/Plotter--> Manage Local Printer Subsystem-->Local Printer Queues--> Remove a Queue.
8. Select List to display a list of queues.
9. Select the name of the queue you want to delete.
10. Select Do to remove the queue.
Problem determination: From the command line, you typed the rmque command to remove a queue, but the queue
contained associated devices.
User response: Remove the associated devices before using the rmque command to remove the queue, as follows:
1. Run the lsallq command to list the queues configured for your system.
2. Run the lsallqdev -q QueueName command to list all the devices associated with the queue you want to delete.
3. For each device in that queue, run rmquedev -q QueueName -d DeviceName command to remove the device.
4. After deleting all the devices, run the rmque -q QueueName command to delete the queue.

0781–189 Queue:device, String:/String not found in qconfig file. Not deleted

Problem determination: Using the System Management Interface Tool (SMIT), you attempted to remove a queue
device not contained in the /etc/qconfig configuration file.
User response: Using SMIT, verify the queue device name and then remove it, as follows:

Chapter 29. Message Component 0781 125

1. From SMIT, select the menu option Devices--> Printer/Plotter--> Manage Remote Printer Subsystem--> Server
Services--> Manage Local Printers Subsystem--> Local Printer Queue Devices--> Remove a Queue
Device--> (queue name).
2. Select List to display all valid device names.
3. Select the desired device from the device name list.
4. Select Do to remove the selected device.
Problem determination: From the command line, you used the rmquedev command with an invalid queue device.
User response: Verify the queue device name and then remove it using the rmquedev command, as follows:
1. Run the lsallq command to list the queues configured for your system.
2. Run the lsallqdev -q QueueName command to list all the queue devices for that queue.
3. Run the rmquedev -q QueueName -d DeviceName command, ensuring that you enter a valid device name.

0781–194 Syntax error in qconfig file

Explanation: An invalid queue stanza entry was entered into the /etc/qconfig file when the lsque or lsallq
command was issued.
User response: Ensure that all queue stanza entries are correct, as follows:
1. Examine the list of valid queue stanza (configuration) entries for the qconfig file.
2. Use an editor to correct any invalid entries contained in the qconfig file.
3. After correcting the qconfig file, rerun the lsque or the lsallq command.

0781–209 Option not supported

Explanation: A print request with an invalid option was placed in the /usr/spool/lpd directory.
User response: Check the remote print jobs to ensure that the print request was made correctly by using the
following System Resource Controller (SRC) commands. These commands control the lpd daemon subsystem.
v startsrc: Starts a subsystem, group of subsystems, or a subserver.
v stopsrc: Stops a subsystem, group of subsystems, or a subserver.
v refresh: Causes the subsystem or group of subsystems to reread the appropriate configuration file.
v traceson: Enables tracing of a subsystem, group of subsystems, or a subserver.
v tracesoff: Disables tracing of a subsystem, group of subsystems, or a subserver.
v lssrc: Gets the status of a subsystem, group of subsystems, or a subserver.
See the lpd command for a list of valid options and their functions, as well as more information.

0781–254 No print server specified

Explanation: At the command line, you entered the rembak command without specifying a print server. The rembak
command should be called only by the qdaemon command.
User response:
v Specify a valid printer server. The rembak command is not intended to be entered on the command line by a user.
See the rembak command for a list of valid options and flags and their functions.
OR
v Use the enq command or the System Management Interface Tool (SMIT) to request a print job. Always use a flag
with the enq command.

0781–277 Error from digester String, status = Number, rv = Number

Explanation: The digest command was called by an executable and an error occurred when the digester attempted
to convert the qconfig file. One or more additional error messages precede this message.
User response: Follow the recovery procedure for each error message that accompanies this message.

126 Message Center Reference

0781–282 Not enough args to digest
Explanation: The bin and config files were not specified for the digest command.
User response: Ensure that the digest command is being issued correctly. The digest command should only be
called by the qdaemon command, not entered from the command line. For more information, see the qdaemon
command. Check the qconfig file for invalid entries. A list of examples of correct queue stanza configuration entries
can be found at the top of the qconfig file.

0781–304 Unable to open PrinterID as standard out

Problem determination: There is a printer-cabling problem.
User response: Verify that the cable to the printer is not damaged or disconnected from the system or printer.
Problem determination: The printer is not configured to the system correctly.
User response: Verify printer configuration.

0781–305 Retrying qdaemon

Problem determination: The printer is not responding.
User response: Ensure that the printer is powered on.
Problem determination: There is a printer-cabling problem.
User response: Reset the printer, then disable and enable it again. See error message 0781-304 for more
information.

0781–310 No such request in any local queue - perhaps it’s done?

Problem determination: You tried to change the priority of a print job or delete a print job, but the job number does
not exist.
User response: Ensure that the job number exists.

Note: The job number might not exist because the job has already printed or because you entered an invalid job
number. If the job number is valid, ensure that you either own the job or are logged in as root. If you are not
logged in as root, you cannot delete or modify jobs issued by other users.
v Using SMIT, list jobs in the queues by selecting the Spooler (Print Jobs)--> Show the Status of Print Jobs
option. In the Show the status of ALL printjobs? field, select Yes and then press Enter. A table of print job
numbers and user IDs displays.
Problem determination: You tried to change the priority of a print job or delete a print job that does not belong to
you.
User response: Ensure that the print job belongs to you. Check your user log on identity. At the command line, type
the whoami command (with no spaces) to display the current user name. Type the who am i command (with spaces
separating the words) to display the user identity initially used to begin the current logon session. To delete or change
the priority of a print job, you must either own the print job or be logged in as the root user. Use the su command to
change users, if needed.

0781–320 No accounting file specified for queue: QueueName

Explanation: The pac command was used to generate a summary file without defining an accounting file in the
/etc/qconfig file.
User response: Add a line to the qconfig file to define the accounting file, as follows:
1. Use an editor to place an acctfile = clause in the appropriate location within the /etc/qconfig file. For more
specific information, see the qconfig article.
2. Rerun the pac command.

Chapter 29. Message Component 0781 127

0781–321 Problem opening account file. Errno = Number
Explanation: You ran the pac command, but the accounting file specified in the acctfile = clause in the
/etc/qconfig file does not exist.
User response: Locate and create the correct path name for the accounting file by doing the following:
1. Run the view /etc/qconfig command.
2. Scroll down to the acctfile = PathName line.
3. Run the touch command to create the path name assigned by the acctfile line.
4. Rerun the pac command.

128 Message Center Reference

Chapter 30. Message Component 0803
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-003 mesg
004-009 news
0803-005 Error Recovery Information
0806-006 Error Recovery Information
0803-007 Error Recovery Information
0803-008 Error Recovery Information
0803-009 Error Recovery Information
010-011 wall
0803-011 Error Recovery Information
012-019 writesrv
020-023 msgs
024-050 write
051 writesrv
052-076 confer
0803-058 Error Recovery Information
0803-059 Error Recovery Information
0803-062 Error Recovery Information
0803-073 Error Recovery Information
0803-074 Error Recovery Information
0803-076 Error Recovery Information

Detailed Information for Message Component 0803

0803-005 Cannot open the String directory

Explanation: You used the news command, but access was denied because you do not have read-execute
permission to the /usr or the /usr/news subdirectories.
User response: Establish read-execute permissions by doing one of the following:
v Determine ownership of the /usr/news directory by running the ls -ld /usr/news command. If you are the owner of
the directory, run the chmod +rx /usr/news command to establish the necessary permissions.
If you are not the owner of the directory, obtain the necessary permissions by running the su command to change
to the root user. Change access permission on the directory by running the chmod +rx /usr/news command.
OR
v Ask the system administrator or the owner of the directory to make the necessary permissions changes.

Note: A symbolic link exists between the /usr/news and the /var/news directories. If the link between these
directories is broken, error message 0803-007 displays. If the permissions are correct on /usr and /usr/news,
see Error Message 0803-007.

0803-006 There is not enough memory available now

Problem determination: This error occurs when using the news command. The system attempts to allocate
memory using the malloc subroutine while space is unavailable in the /usr/news subdirectory. This occurs for one of
the following reasons:

© Copyright IBM Corp. 2003, 2004 129

v Too many processes are running.
v A file is too large or there are too many files.
User response: Do one of the following:
v Remove unnecessary processes or wait for them to stop running by entering the ps -eaf command to check the
number of processes that are running. If there are too many processes running, do one of the following:
– Wait until some of the processes are completed.
OR
– Use the kill command to stop a process that you started. If you did not start the process, use the su command
to change to the root user and stop the process with the kill command. Otherwise, ask the owner of the process
to stop the process.
v Remove unnecessary files or release sufficient memory for the files.
Use the li -ld command to check the size and the number of files that exist in the /usr/news subdirectory. If there is
not enough memory because of the size or the number of files, more memory can be freed using the rm or delete
command.
v Increase the paging space.

0803-007 Cannot move to the String directory

Explanation: You used the news command, but access was denied for one of the following reasons:
Problem determination: You do not have read-execute permission to the /var or /var/news directories, or they do
not exist.
User response: Verify that the /var and /var/news directories exist with the correct ownership and permissions by
doing the following:
1. Run the ls -ld /var/news command to verify the directory’s existence.
2. If the directories do not exist, do the following:
a. Create the directory by running the mkdir /var/news command.
b. Ensure that the ownership for the /var/news directory is bin for group and bin for owner by running the ls -ld
/var/news command.
c. Establish full permissions for the directory by running the chmod 777 /var command and the chmod 777
/var/news command.
3. If the directories do exist, check the ownership and permissions using the procedures outlined in steps b and c.
Problem determination: The symbolic link between the /usr/news directory and the /var/news directory does not
exist.
User response: Ensure that the symbolic link exists by doing the following:
1. Run the su command to change to the root user. Determine if the link exists by running the ls -ld /usr/news
command. A symbolically linked directory is indicated by an arrow and the contents of the symbolic link are listed
after the directory name, as follows:
/usr/news -> /var/news
2. If the /usr/news directory is not followed by an arrow pointing to the /var/news directory, run the ls -ld /var/news
command to verify that the /var/news directory exists. If it does not exist, do the following:
a. Create the directory by running the mkdir /var/news command.
b. Ensure that the ownership for the /var/news directory is bin for group and bin for owner by running the ls -ld
/var/news command. Also, check that all users have the following read-write-execute permissions:
drwxrwxrwx 3bin bin 512 Mar 04 11:48 /var/news
c. Run the chgrp bin /var/news command to change the group. Run the chown bin /var/news command to
change the owner. Run the chmod 777 /var/news command to obtain full read-write-execute permissions.
d. If the /usr/news file exists as an unlinked file, remove it by running the rmdir /usr/news command.
e. To create the link between the /usr/news and the /var/news files, run the ln -s /var/news /usr/news
command.

130 Message Center Reference

0803-008 Cannot open DirectoryName/FileName
Explanation: You used the news command, and you do not have read-execute permission to the
/usr/news/FileName file.
User response: Obtain read-execute permissions for the /usr/news/FileName file.

0803-009 The HOME environment variable does not exist

Explanation: You used the news command, which calls the HOME environment variable. Access was denied while
trying to open a file under the /news directory because the HOME environment variable does not exist.
User response: Define the HOME environment variable by running the export HOME=/u/UserID command and then
rerunning the news command. Use the env command to verify that the HOME environment variable is defined
correctly.
You can also set the HOME variable in your .profile file so that it is set correctly on each login.

0803-011 Cannot create another process at this time

Explanation: You tried to use the fork subroutine using the wall command, but not enough memory was available
for the fork to create a new process.
User response: Find all invalid or unnecessary processes and remove them by doing the following:
1. Run the ps -ef command to show all invalid or unnecessary processes.
2. Run the kill -9 command to remove any invalid or unnecessary processes.
3. Rerun the wall command.

Note: The wall command continues to run and to broadcast the intended message to all other valid logged-in users.
Thus, it might not be necessary to reenter the command.

For more information on how to stop processes, see Processes Overview in CHECK THIS LINK--was AIX 5L Version
5.3 System User’s Guide: Operating System and Devices.

0803-058 Can’t make String

Explanation: This error occurs while using the confer command. After closing a conference by pressing the Ctrl-D
key combination, you are asked Do you want a transcript mailed to you? If you answer yes, this message displays
for one of the following reasons:

Note: You cannot recover the transcript of this conference. These procedures allow you to receive a transcript of your
next conference.
Problem determination: The /tmp directory is full.
User response: Remove unnecessary files from your /tmp directory by running the df command and examining the
%used column to see if the /tmp directory is full. If the directory is full, use the rm command to remove unnecessary
files in the /tmp directory.
Problem determination: You do not have write-execute permissions to the /tmp directory.
User response: Obtain write-execute permissions to the /tmp directory.

0803-059 Cannot read FileName

Explanation: You entered the confer command and it could not open the /etc/utmp/FileName file for reading
because it does not exist or is damaged. The /etc/utmp/FileName file contains information about users who are
logged in.
User response: Create the /etc/utmp/FileName file by doing the following:
1. All users must log off and then log in again to create the file /etc/utmp/FileName file.
2. Rerun the confer command.

Chapter 30. Message Component 0803 131

0803-062 Can’t create conference String
Problem determination: You used the confer command, which creates a transcript file in the /tmp directory, and
you do not have write-execute permission on the /tmp directory.
User response: Ensure that you have write-execute permissions on the /tmp directory.
Problem determination: Using the confer command, you attempted to open more than the maximum number of
eight conferences having the same name.
User response: Cancel some of the conferences that have the same name. Press the Ctrl-D key combination to
cancel a conference.

0803-073 Cannot run mesg -y

Explanation: You used the confer command to set up a conference among some users on the local node, but the
system was unable to make the tty writable by running the mesg -y command from within the confer command.
User response: Ensure that the /bin/mesg file in the mesg -y command exists and has the correct execute
permissions, and rerun the confer command, as follows:
1. Run the su command to change to the root user.
2. Enter the ls -al /bin/mesg command to confirm that the mesg command exists.
3. If the /bin/mesg does not exist, it must be reinstalled from the original system installation source or copied from
another machine that has the same version number of the operating system.
4. Ensure that the /bin/mesg file has execute permissions set.
5. Rerun the confer command.

Note: This error is usually generated by the confer command. However, it can also be generated by the joinconf
command if the joinconf command calls the confer command.

0803-074 Illegal redirection of stdin or stdout

Explanation: You entered the confer or joinconf command and redirected the stdin or stdout file to a device other
than a tty device.
User response: Rerun the confer or joinconf command and direct the stdin or stdout file to a valid tty device, as
follows:
1. Run the lsdev -C -c tty command to list the valid tty names.
2. Rerun the confer or joinconf command, and redirect the stdin or stdout file to the correct tty device.

0803-076 Too many participants

Explanation: You used the confer command, but the system could not find enough memory to allocate for each
person called to participate in the conference.
User response: Allocate sufficient memory for each conference participant.

132 Message Center Reference

Chapter 31. Message Component 0821
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-007 cfgif
014-035 defif
038-047 definet
055-059 no
0821-058 Error Recovery Information
062-077 ping
0821-069 Error Recovery Information
0821-073 Error Recovery Information
078-082 stpinet
089-095 sttinet
102-111 cfgif
cfginet
chgif
chginet
defif
definet
stpinet
sttinet
ucfgif
ucfginet
udefif
udefinet
118-126 udefif
133-142 udefinet
149-151 ucfgif
189-200 cfginet
206-218 chginet
0821-216 Error Recovery Information
222 chgif
223-230 chgif
0821-223 Error Recovery Information
231 arp
0821-231 Error Recovery Information
232-249 arp
0821-233 Error Recovery Information
256-260 ucfginet
266-268 hostname
0821-267 Error Recovery Information
274-289 route
291-299 slattach
500-518 ifconfig
519-535 Required SCSI Adapter Device Driver ioctl Commands in Kernel Extensions and Device Support
Programming Concepts.
536-553 ifconfig
600 syslogd

© Copyright IBM Corp. 2003, 2004 133

Detailed Information for Message Component 0821

0821–058 Only the root user can set network options

Explanation: You entered the no command without having root user authority.
User response: Reissue the no command as the root user by doing the following:
1. Run the su command to change to the root user.
2. Reissue the no command.

Note: The no command does not perform range-checking; therefore, it accepts all values for variables. If used
incorrectly, the no command might cause your system to become inoperable.

0821–069 ping: sendto:

Problem determination: You ran the following command from the command line:
ping -s Packetsize Hostname

where Packetsize was specified greater than 8184 bytes.

User response: Specify a packet size less than 8185 bytes.
Problem determination:
v You installed a network adapter card but did not configure TCP/IP.
OR
v You reinstalled the system, but did not configure TCP/IP.
User response: Using the System Management Interface Tool (SMIT), do the following:
1. From the menu, select the Communication and Application Services option.
2. Select TCP/IP, and complete the Minimum Configuration and Startup menu.

0821–073 You must be root to use the -f option

Explanation: You used the ping command without having root user authority.
User response: Run the ping command as the root user by doing the following:
1. Run the su command to change to the root user.
2. Rerun the ping command.

Note: Be careful when using the -f flag with the ping command; it can place large loads on the network. The -f flag is
incompatible with the -i Wait flag.

0821–216 Cannot delete route from CuAt

Problem determination:
v You might have entered invalid information in the request.
OR
v If the route was added manually, outside of SMIT, there is no database entry.
User response: Remove the route and then add it again by doing the following:
1. Remove the route manually.
2. Add the route using SMIT.
Problem determination: You must be logged in as root or be a member of the system group to add or delete route.

Note: Error messages 0821-223, 0821-229 and 0821-510 always occur simultaneously.
User response: Log in as root user or have your system administrator add you to the system group.

134 Message Center Reference

0821–223 Cannot get records from CuAt
Problem determination: You must be logged in as root user or be a member of the system group to run the
mktcpip command.
User response: Log in as root user or have your system administrator add you to the system group.
Problem determination: Using the System Management Interface Tool (SMIT), you tried to configure a network
adapter that was not available for TCP/IP.
User response: Ensure that the specified adapter is listed as available. From the command line, run:
lsdev -C -c Adapter
Problem determination: You specified a network adapter that was defined, but not available to the system, using
the mktcpip command from the command line.
User response: If you added the adapter after the system initial program load (IPL), run the cfgmgr command to
make it available to the system.
Problem determination: An adapter listed as available has hardware problems.
User response: Verify that there are no problems with the hardware. Using SMIT, run Hardware Diagnostics from
the Problem Determination menu.
Problem determination: The root file system is full.
User response: Ensure that the root file system is not full by doing the following:
1. Run the df / command from the command line.
2. If the file system is full, remove unnecessary files from the root file system or use the SMIT Physical and Logical
Storage menu to increase the size of the root file system.
Problem determination: The object data management (ODM) database is damaged.
User response: Verify that the state, netaddr, and netmask attributes have valid values in the object database by
running the following from the command line:
odmget -q name=Adaptername CuAt

0821–231 Cannot open FileName

Problem determination: You must be logged in as root user or be a member of the system group to run the arp -f
command.
User response: Log in as root user or have your system administrator add you to the system group.
Problem determination: You used the arp -f FileName command, but you cannot open the file because you do not
have read permission on the file, or the file does not exist.
User response:
v Obtain read permission on the file.
OR
v Using an editor, create the FileName file. Ensure you have the correct permissions on the new file.

0821–233 Permission is denied

Explanation: You used the arp command to change the Address Resolution Protocol (ARP) table entry, but you are
not logged in as the root user.
User response: Change to the root user and rerun the arp command by doing the following:
1. Run the whoami command to check your user ID.
2. If you are not logged in as the root user, run the su command to change to the root user.
3. Rerun the arp command.

Chapter 31. Message Component 0821 135

0821–267 The sethostname system call failed
Explanation: This error message is displays when you use the hostname command to set or change the current
host name of the system and you are not logged in as the root user.
User response: Change to the root user and reissue the hostname command by doing the following:
1. Run the whoami command to check your user ID.
2. If you are not logged in as the root user, run the su command to change to the root user.
3. Rerun the hostname command.

136 Message Center Reference

Chapter 32. Message Component 0822
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-006 chnamsv
012-022 chprtsv
029 0822-029 Error Recovery Information
041-049 hostent
121-126 lsnamsv
132-136 lsprtsv
142-147 mknamsv
153-161 mkprtsv
167-179 namerslv
187-190 rmnamsv
196-201 rmprtsv
207-210 ruser
211 ruser
0822-211 Error Recovery Information

Detailed Information for Message Component 0822

0822–029 Cannot open /etc/hosts.lpd

Problem determination: You used the System Management Interface Tool (SMIT) to remove a remote host name,
but the /etc/hosts.lpd file could not be opened.
User response: Ensure that the /etc/hosts.lpd file exists and that you have write permission in both the file and in
the /etc directory by doing the following:
1. Run the cd command to ensure that the /etc directory exists.
2. Run the ls -l command to ensure that you have write permission to the /etc directory.
3. Run the ls -l command to ensure that the /etc/hosts.lpd file exists, that it is a file and not a directory, and that you
have write permission on this file.
4. Ensure that you are logged in as the root user or have the appropriate write permissions. Use the su command to
change users, if necessary.
Problem determination: From the command line, you used the ruser command to remove a remote host name, but
the /etc/hosts.lpd file could not be opened.
User response: Use SMIT or the ruser command to remove a remote host name.

0822–211 Cannot delete from /etc/hosts.lpd

Problem determination: You specified an invalid remote host name while using the System Management Interface
Tool (SMIT) to remove a remote host.
User response: Using SMIT, specify a valid remote host and remove it by doing the following:
1. From the SMIT menu, select Devices--> Printer/Plotter--> Manage Remote Printer Subsystem--> Server
Services--> Host Access for Printing--> Remove a Remote Host.
2. Select the List option to display a list of valid remote hosts.
3. Select the remote host you want to remove.

© Copyright IBM Corp. 2003, 2004 137

4. Select Do to remove the selected remote host.
Problem determination: From the command line, you ran the ruser -dp command with an invalid remote host
name.
User response: Specify a valid remote host name and remove it with the ruser command by doing the following:
1. Run the ruser -sP command to list remote hosts in the /etc/hosts.lpd file.
2. Run the ruser -dp RemoteHostName command, where RemoteHostName specifies the remote host listed in the
/etc/hosts.lpd file that you want to remove.

138 Message Center Reference

Chapter 33. Message Component 0826
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

301-310 rexec
402 ruptime
501-532 inetd
601-615 rexecd
801-831 rshd
0826-813 Error Recovery Information

Detailed Information for Message Component 0826

0826-813 Permission is denied.

Problem determination: The host or user is not listed in the /etc/hosts.equiv file.
User response: Add the host or the user to the /etc/hosts.equiv or $HOME/.rhosts file.
Problem determination: The host or user is denied access in the /etc/hosts.equiv or $HOME/.rhosts file on the
server.
User response: Add access for host or user in the /etc/hosts.equiv or $HOME/.rhosts file.
Problem determination: The $HOME/.rhosts file on the server is not owned by the local user.
User response:

Note: This action is only applicable if the $HOME directory is NFS-mounted.

Set the appropriate permission in the server so that the local user (nfs client) can access it by doing one of the
following:
v Set the owner of the $HOME/.rhosts to the local user (UID).
v Set the permissions on the $HOME/.rhosts file to 600.
Problem determination: The $HOME/.rhosts file has write permission set for ″group″ and ″others″.
User response: Set the permissions on the $HOME/.rhosts file to 600.

© Copyright IBM Corp. 2003, 2004 139

140 Message Center Reference
Chapter 34. Message Component 0827
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

801-803 host
821 hostid
841-844 ipreport
861-883 iptrace

© Copyright IBM Corp. 2003, 2004 141

142 Message Center Reference
Chapter 35. Message Component 0832
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-002 Object Data Manager (ODM) database or odm command failure

010 Object Data Manager (ODM) database or odm command failure
003-008 chhwkbd
0832-003 Error Recovery Information
0832-004 Error Recovery Information
0832-005 Error Recovery Information
0832-006 Error Recovery Information
0832-007 Error Recovery Information
0832-008 Error Recovery Information
011-013 chhwkbd
0832-011 Error Recovery Information
0832-012 Error Recovery Information
0832-013 Error Recovery Information
0832-014 Error Recovery Information
015 savebase
016-017 chhwkbd
0832-016 Error Recovery Information
0832-017 Error Recovery Information

Detailed Information for Message Component 0832

0832-003 <string>: A keyboard must be configured to run this command.

Explanation: You tried to run the chhwkbd command, but there was no keyboard configured.
User response: Configure a keyboard and run the command again.

0832-004 <string>: Missing or invalid value specified. After the -d flag, specify 250, 500, 750 or 1000.
Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-005 <string>: Missing or invalid value specified. After the -r flag, specify an integer between 2 and 30.
Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

© Copyright IBM Corp. 2003, 2004 143

0832-006 <string>: Missing or invalid value specified. After the -c flag, specify an integer between 0 and 3.
Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-007 <string>: Missing or invalid value specified. After the -a flag, specify an integer between 0 and 3.
Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-008 <string>: Value following -m flag is not valid.

Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-011 <string>: Invalid flag specified. -<char> is not valid.

Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-012 <string>: Command line options are invalid.

Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-013 <string>: -m flag is not valid for the configured keyboard.

Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

0832-014 <string>: Keyboard operation failed with error code of <string>. Your changes have been saved
and will not completely take effect until the next system boot.
Explanation: Your keyboard has a hardware error.
User response: Run diagnostics on the keyboard to determine the problem, or replace the keyboard with a working
keyboard.

0832-016 <string>: Value following -t flag is not valid.

Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command.

144 Message Center Reference

0832-017 -t flag is not valid for the configured keyboard.
Explanation: An invalid parameter was specified for the chhwkbd command.
User response: Obtain the correct parameter and run the chhwkbd command again. For more information, see the
chhwkbd command. If man pages are installed on your system, you can run the man chhwkbd command on the
command line to view the command information.

Chapter 35. Message Component 0832 145

146 Message Center Reference
Chapter 36. Message Component 0950
Messages 0950-001 through 0950-031 are associated with the ethchan_config command.

0950–001 Error Recovery Information

0950–002 Error Recovery Information
0950–003 Error Recovery Information
0950–004 Error Recovery Information
0950–005 Error Recovery Information
0950–007 Error Recovery Information
0950–008 Error Recovery Information
0950–010 Error Recovery Information
0950–011 Error Recovery Information
0950–012 Error Recovery Information
0950–013 Error Recovery Information
0950–014 Error Recovery Information
0950–015 Error Recovery Information
0950–016 Error Recovery Information
0950–017 Error Recovery Information
0950–018 Error Recovery Information
0950–020 Error Recovery Information
0950–021 Error Recovery Information
0950–022 Error Recovery Information
0950–024 Error Recovery Information
0950–025 Error Recovery Information
0950–026 Error Recovery Information
0950–027 Error Recovery Information
0950–028 Error Recovery Information
0950–029 Error Recovery Information
0950–031 Error Recovery Information

Detailed Information for Message Component 0950

0950–001 You must be the superuser to use this command.

Explanation: You tried to execute this command without root permission.
User response: Reissue the command as the root user by doing the following:
1. Run the su command to log in as the root user.
2. Reissue the command that failed.

0950–002 Specify only one command flag.

Explanation: You specified more than one command flag (e.g. ″-a -c″) at the same time. Each command must only
specify one command flag.
User response: Reissue the command specifying only one command flag.

0950–003 Specify an EtherChannel and an adapter contained in said EtherChannel.

Explanation: You specified a command flag that requires the name of an EtherChannel and an adapter name, but
one of these was missing.
User response: Reissue the command specifying first the name of the EtherChannel adapter and then the name of
the adapter being modified by the command.

© Copyright IBM Corp. 2003, 2004 147

0950–004 Specify an EtherChannel, the attribute to modify and the attribute’s new value
Explanation: You specified the ″change″ command, which requires the name of the EtherChannel adapter, the name
of the attribute to modify, and the new value of the attribute, but one or more of these arguments was not specified.
User response: Reissue the command specifying the name of the EtherChannel adapter, the name of the attribute
to modify, and the new value of the attribute. The names of the EtherChannel’s attributes can be obtained by running
the command lsattr -E -l EtherChannel_Adapter. The possible values of a specific attribute can be obtained by
running the command lsattr -D -R -l EtherChannel_Adapter -a Attribute.

Note: The name of the attribute to modify and its new value are specified as different arguments, that is, they are
separated by white space, not an equal sign (=), as in the chdev command format.

0950–005 Specify at least one command flag.

Explanation: You did not specify any command flag as a command argument.
User response: Reissue the command specifying one (and only one) command flag.

0950–007 Unable to open device EtherChannel_Adapter, errno = Num.

Explanation: You specified an EtherChannel device that can not be opened.
User response: Reissue the command after having made sure that the EtherChannel adapter specified on the
command exists on the system. Check this by issuing the following command:
lsdev -C -c adapter -s pseudo -t ibm_ech

0950–008 Unable to connect to device EtherChannel_Adapter, errno = Num.

Explanation: You specified an EtherChannel device that does not exist or is not available for use on the system.
User response: Reissue the command after having made sure that the EtherChannel adapter specified on the
command exists and is in the Available state by issuing the following command:
lsdev -C -c adapter -s pseudo -t ibm_ech

If it exists but it is in the Defined state, bring it to the Available state by issuing the following command:
mkdev -l EtherChannel_Adapter

0950–010 Unable to add adapter Adapter to EtherChannel EtherChannel_Adapter, errno = Num.

Explanation: You specified an adapter to be added that either does not exist, is not in the Available state, or is
currently configured with an IP address. In order to be included in an EtherChannel, an adapter must be properly
loaded (that is, be in the Available state) and it must not be currently configured with an IP address.
User response: Reissue the command after having made sure that the EtherChannel adapter specified on the
command exists, is in the Available state, and is not configured with an IP address by doing the following:
1. Issue the following command:
lsdev -C -c adapter -s pseudo -t ibm_ech

If the adapter exists but it is in the Defined state, bring it to the Available state by issuing the following command:
mkdev -l Adapter
2. Issue the following command:
ifconfig Interface detach

For example, if Adapter is ent0, Interface is en0.

148 Message Center Reference

0950–011 Unable to delete adapter Adapter from EtherChannel EtherChannel_Adapter, errno = Num.
Explanation: There was an internal program error in the EtherChannel driver or the ethchan_config command.
User response: None.

0950–012 Unable to modify attribute ″Attribute″ in EtherChannel EtherChannel_Adapter, errno = Num.

Explanation: You attempted to modify an attribute that does not exist.
User response: Reissue the command after having made sure that the attribute specified is a valid EtherChannel
attribute by issuing the following command:
lsattr -D -R -l EtherChannel_Adapter -a Attribute

0950–013 Unable to access ODM database, errno = Num.

Explanation: There was an error trying to set the path for the ODM database, initializing the ODM database,
obtaining the lock for the ODM database, or opening the CuDv or CuAT ODM object classes.
User response: Reissue the command after having made sure that the ODM database is correctly configured.

0950–014 Unable to open CuDv object for device Adapter, errno = Num.
Explanation: There was an error trying to get the current values of an attribute of the specified adapter.
User response: Reissue the command after having made sure that the ODM database is correctly configured.

0950–015 Unable to access CuDv object for device Adapter, errno = Num.
Explanation: There was an error trying to get the current values of an attribute of the specified adapter.
User response: Reissue the command after having made sure that the ODM database is correctly configured.

0950–016 Unable to access attributes for device Adapter, errno = Num.

Explanation: There was an error trying to get the current values of an attribute of the specified adapter.
User response: Reissue the command after having made sure that the ODM database is correctly configured.

0950–017 Unable to access attribute Attribute for device Adapter, errno = Num
Explanation: There was an error trying to get the current value of the attribute Attribute of the specified adapter.
User response: Reissue the command after having made sure that the ODM database is correctly configured.

0950–018 The value ″Value″ is invalid for attribute ″Attribute″, errno = Num.
Explanation: You attempted to modify the value of Attribute to an invalid value.
User response: Reissue the command specifying a valid value for Attribute. The possible values for Attribute can be
obtained by running the following command:
lsattr -D -R -l EtherChannel_Adapter -a Attribute

0950–020 Unable to delete adapter Adapter from EtherChannel EtherChannel_Adapter: it is not the backup
adapter.
Explanation: There was an internal program error in the EtherChannel driver or the ethchan_config command.
User response: None.

Chapter 36. Message Component 0950 149

0950–021 Unable to delete adapter Adapter from the EtherChannel because it could not be found, errno =
Num.
Explanation: You attempted to delete an adapter that does not exist in the EtherChannel.
User response: Reissue the command specifying a valid adapter to delete. To view the adapters and backup
adapter that do exist in the EtherChannel, run the following command:
lsattr -E -l EtherChannel_Adapter

0950–022 Unable to add adapter Adapter to the EtherChannel because it does not support the same
capabilities as the EtherChannel, errno = Num.
Explanation: You attempted to add an adapter that does not support the same capabilities as the other ones in the
EtherChannel. Capabilities are features that a specific type of adapter can perform. For example, there is checksum
offload, large send, and private segments. After an EtherChannel is configured with an IP address, its interface
automatically starts using the minimum common denominator of the capabilities supported by the adapters contained
in the EtherChannel at that point . For example, if one supports large send but another adapter does not, large send
cannot be supported. However, if all of them support checksum offload, the interface will automatically use checksum
offload.
After the capabilities for the whole EtherChannel have been decided, adapters that are added to the EtherChannel
must support all the same capabilities the EtherChannel said it supports (otherwise erroneous behavior could occur).
Adapters being added, however, can support capabilities that the EtherChannel does not support (they will simply be
unused).
User response: Reissue the command specifying an adapter that supports the same capabilities as the
EtherChannel. To view the capabilities supported by an adapter or the EtherChannel, run the following command:
entstat Adapter

The capability flags are listed at the end, under the ″General Statistics″ header, in the ″Driver Flags″ section.

0950–023 You may not specify the backup flag with the delete command: an adapter will be deleted
whether it is in the main channel or if it is the backup adapter.
Explanation: You specified the delete and the backup flag simultaneously (that is, -d -b). It is not necessary to
specify the backup flag to delete the backup adapter.
User response: Reissue the command without the -b flag to delete the backup adapter.

0950–024 You may not modify the attribute ″Attribute″, errno = Num.
Explanation: You attempted to modify an attribute that cannot be modified at runtime. The use_jumbo_frame
attribute cannot be modified at runtime.
User response: Detach the EtherChannel’s interface and use the chdev command to modify the attribute if it cannot
be modified at runtime by using the following commands:
1. ifconfig Interface detach

For example, if EtherChannel_Adapter is ent3, Interface is en3.

2. chdev -l EtherChannel_Adapter -a Attribute=Value

0950–025 You may not change the attribute ″Attribute″ to (or from) the value ″Value″, errno = Num.
Explanation: You attempted to modify an attribute that cannot be modified to a specific value at runtime.
User response: Detach the EtherChannel’s interface and use the chdev command to modify the attribute if it cannot
be modified at runtime by using the following commands:
1. ifconfig Interface detach

For example, if EtherChannel_Adapter is ent3, Interface is en3.

2. chdev -l EtherChannel_Adapter -a Attribute=Value

150 Message Center Reference

0950–026 Unable to start the process ″Process″, errno = Num.
Explanation: There were not enough memory resources to fork the process Process.
User response: Reissue the command when enough memory resources have been freed.

0950–027 The command ″Process″ failed, errno = Num.

Explanation: There was a problem executing the spawned command Process.
User response: Reissue the command when the reason of the spawned process’s failure has been ascertained and
corrected.

0950–028 Unable to add adapter Adapter to the EtherChannel because it would exceed the maximum
number of adapters in an EtherChannel, errno = Num.
Explanation: You attempted to add an adapter when the main channel already has a maximum number of adapters.
There can only be 8 adapters in the main channel of an EtherChannel.
User response: To add this adapter, first delete one of the existing main adapters and then reissue to command to
add the new adapter.

0950–029 Unable to add adapter Adapter to the EtherChannel as a backup adapter because it already has
one, errno = Num.
Explanation: You attempted to add a second backup adapter to an EtherChannel. An EtherChannel can only have 1
backup adapter at any time.
User response: To change the backup adapter at runtime, first delete the existing backup adapter and then reissue
the command to add the new adapter.

0950–031 Unable to resolve the address for hostname Hostname, errno = Num.
Explanation: You attempted to set the netaddr attribute to a value that was determined to be a host name (That is,
it was not a valid IPv4 address), and this host name could not be resolved into an IPv4 address.
User response: Reissue the command after making sure that the host name specified could be resolved. Make sure
the /etc/resolv.conf file contains a valid resolver, or that the host name is contained in the /etc/hosts file.

Chapter 36. Message Component 0950 151

152 Message Center Reference
Chapter 37. Message Component 1001
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-202 spell
spellin
spellout
301-306 diction
500 style

© Copyright IBM Corp. 2003, 2004 153

154 Message Center Reference
Chapter 38. Message Component 1002
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

022-023, 025 addbib

102 indxbib
202-205 lookbib
301 roffbib
402-407 sortbib
503-655 refer

© Copyright IBM Corp. 2003, 2004 155

156 Message Center Reference
Chapter 39. Message Component 1003
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-043 tbl
103-142 eqn
201-230 neqn
303-355 pic
403-451 grap
501-507 vgrind
601-650 checkmm
703-706 col
803 diffmk

© Copyright IBM Corp. 2003, 2004 157

158 Message Center Reference
Chapter 40. Message Component 1004
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-117 nroff
troff
202 mm
mmt
403 ndx
450 subj
501-503, 537 style
602-603 hyphen
703-708 macref
901-916 ptx

© Copyright IBM Corp. 2003, 2004 159

160 Message Center Reference
Chapter 41. Message Component 1005
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

102-105, 107, 111-112 checknr

201, 203-204 cw
306 checkcw
502, 504 deroff
602 greek
801, 807-809 tc
901-908 ibm3816

© Copyright IBM Corp. 2003, 2004 161

162 Message Center Reference
Chapter 42. Message Component 1006
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

101-117 makedev
201-202 ibm5587G
301-306 hplj

© Copyright IBM Corp. 2003, 2004 163

164 Message Center Reference
Chapter 43. Message Component 1007
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

002-025 xpreview
150-161 ps4014
200-202 ps630
250-251 psplot
500-511 psrev
600-617 enscript
650-675 psdit

© Copyright IBM Corp. 2003, 2004 165

166 Message Center Reference
Chapter 44. Message Component 1201
Messages 1201-001 through 1202-198 are associated with the libc library.

© Copyright IBM Corp. 2003, 2004 167

168 Message Center Reference
Chapter 45. Message Component 1232
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001 regcmp or regex subroutine

002 xcreat subroutine
003 xlink subroutine
004-010 xmsg subroutine

© Copyright IBM Corp. 2003, 2004 169

170 Message Center Reference
Chapter 46. Message Component 1254
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-049 make
1254-004 Error Recovery Information

Detailed Information for Message Component 1254

1254–004 The error code from the last command is Number

Problem determination: You issued the make command from a directory for which you do not have write
permission.
User response: Use the ls -l command to check the permissions of the directory, then use the chmod +w command
to add write permission.
Problem determination: A syntax error exists in the source code that the make command is trying to compile.
User response: Check the file indicated by the make command in which the error is occurring, make the necessary
corrections, and rerun the make command.

© Copyright IBM Corp. 2003, 2004 171

172 Message Center Reference
Chapter 47. Message Component 1281
Messages 1281-013 through 1281-107 are associated with the adb command

© Copyright IBM Corp. 2003, 2004 173

174 Message Center Reference
Chapter 48. Message Component 1283
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-017 dbx
201-249 dbx

© Copyright IBM Corp. 2003, 2004 175

176 Message Center Reference
Chapter 49. Message Component 1285
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

100-131 bs
300-354 lex
For more information, see Generating a Lexical Analyzer with the lex Command in AIX 5L Version
5.2 General Programming Concepts: Operating Systems and Devices.
355-360 lex
500 sno
700-776 yacc
For more information, see Generating a Lexical Analyzer with the lex Command in AIX 5L Version
5.2 General Programming Concepts: Operating Systems and Devices.

© Copyright IBM Corp. 2003, 2004 177

178 Message Center Reference
Chapter 50. Message Component 1286
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000-007 cb
050-053 asa
fpr
075-079 fsplit
100-110 cflow
150-169 cxref
200-202, 205-210 unifdef
225-247 indent
300-309, 330-336 lint
400-430 struct
600-604 regcmp

© Copyright IBM Corp. 2003, 2004 179

180 Message Center Reference
Chapter 51. Message Component 1311
Messages 1311-101 and 1311-104 through 1311-108 are associated with the chlang command.

© Copyright IBM Corp. 2003, 2004 181

182 Message Center Reference
Chapter 52. Message Component 1312
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-004 dspcat
005-017, 019-022 gencat
025-038 mkcatdefs
040-044 dspmsg

© Copyright IBM Corp. 2003, 2004 183

184 Message Center Reference
Chapter 53. Message Component 1345
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-073 AIX Graphics Library Overview in ″GL3.2 Version 4.1 for AIX: Programming Concepts″. This
information applies to AIX Version 5.1 and earlier.

© Copyright IBM Corp. 2003, 2004 185

186 Message Center Reference
Chapter 54. Message Component 1356
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

200-208 xhost
300-301 xclock
400-402 mkfontdir
501-550 xpr
551-603 xwd
770 xsetroot
780–781 xsetroot
790-792 xrdb
800-825 xinit
1356-800 Error Recovery Information

Detailed Information for Message Component 1356

1356–800 Unable to start the X server

Problem determination: You ran the xinit command, but specified an incorrect parameter.
User response: Ensure that you specified the correct parameters. For more information, see the xinit command.

Note: If you are using the X11R5 server, use the -- (double-dash) flag to specify an alternate server or display. For
example:
xinit -- /usr/lpp/X11/bin/X :1

OR
xinit -- :2
Problem determination: The X server command file is missing or does not have execute permission.
User response: Ensure that the /usr/bin/X11/X file exists and that it has execute permission. If it does not exist, run
the installp command to reinstall the X11rte.obj lpp.
Problem determination: The path to the X server is not set.
User response: Check the PATH environment variable in your .profile file to ensure that it points to the /usr/bin/X11
file so that the X command file is accessible.

© Copyright IBM Corp. 2003, 2004 187

188 Message Center Reference
Chapter 55. Message Component 1363
Messages 1363-000 through 1363-014 are associated with the aixterm command.

© Copyright IBM Corp. 2003, 2004 189

190 Message Center Reference
Chapter 56. Message Component 1365
Messages 1365-060 through 1365-065 are associated with the mkfontdir command.

© Copyright IBM Corp. 2003, 2004 191

192 Message Center Reference
Chapter 57. Message Component 1371
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-003 setupterm subroutine

010 _showstring subroutine

© Copyright IBM Corp. 2003, 2004 193

194 Message Center Reference
Chapter 58. Message Component 1386
Messages 1386-101 through 1386-129 are associated with the xlock command.

© Copyright IBM Corp. 2003, 2004 195

196 Message Center Reference
Chapter 59. Message Component 1800
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001-039 smit
1800-034 Error Recovery Information
041-088 smit
090-109 smit
1800-093 Error Recovery Information
1800-102 Error Recovery Information
1800-106 Error Recovery Information
201-208 dsmit

Detailed Information for Message Component 1800

1800-034 Exit Status 1

Problem determination: You attempted to remove a device that is busy.
User response: Check the device by doing the following:
1. Run the rmdev -l DeviceName -d command to delete the device. If an error code of 0514-063 (device busy)
results, run the disable command for that device.
2. Run the rmdev command again.
Problem determination: You are adding or removing a virtual printer without using SMIT.
User response: Use SMIT to add a virtual printer.

1800-093 Could not open SMIT log file

Problem determination: You specified an invalid log file name with the System Management Interface Tool (SMIT) -l
flag. This log file name is invalid for one of the following reasons:
v The specified name is the name of a directory.
v You do not have write permission for the file specified.
v The path name to the specified log file does not exist.
User response: Specify a valid log file name by doing the following:
1. Check that the path name of the specified smit.log file is correct.
2. Use the cd command to verify that the directory and all parent directories in which the smit.log file resides.
3. Ensure that you have write permission for the directory in which the smit.log file is created by using the ls -ld
command.
4. If the specified smit.log file already exists, check that you have write permission to this file by using the ls -l
command. To change the permission, use the chmod command.
Problem determination: You do not have write permission to the smit.log file in the default (home) directory. This
problem occurs for one of the following reasons:
v Your home directory was inadvertently deleted, and you do not have write permission for the alternate directory
assigned by the operating system.
v The permissions on your default (home) directory have been changed.

© Copyright IBM Corp. 2003, 2004 197

User response: Obtain write permission to the smit.log file by doing the following:
1. Ensure that your default (home) directory is the expected default directory by entering the echo $HOME
command.
2. Verify that you have write permission to the default (home) directory by running the ls -l command from the parent
of the home directory. Use the chmod command to change permission, if necessary.
3. If a file named smit.log exists in your default (home) directory, ensure that you have write permission to this file by
running the ls -l command. Use the chmod command to change permission, if necessary.
To specify an alternate smit.log file rather than correct directory or permission problems, use the -l flag. You must
have write permission for the alternate log file specified.
The following produces a smit.log file in the specified location (logging takes place in this file during the session):
smit -l/tmp/smit.log

You should research the possibility that your default (home) directory has been deleted (using the cd and ls
commands) or that your file system has been damaged (using the fsck command).

1800-102 Could not open SMITscript file

Problem determination: You specified an invalid script file name with the System Management Interface Tool (SMIT)
-s flag. This script file name is invalid for one of the following reasons:
v The specified name is the name of a directory.
v You do not have write permission for the file specified.
v The path name to the specified script file does not exist.
User response: Specify a valid script file name by doing the following:
1. Check that the path name of the specified smit.script file is correct.
2. Use the cd command to verify that the directories contain the smit.script file and that all parent directories exist.
3. Use the ls -ld command to ensure that you have write permission for the directory where the smit.script file is
created.
4. If the specified smit.script file already exists, use the ls -l command to check that you have write permission to
this file. Use the chmod command to change the permission, if necessary.
Problem determination: You do not have write permission to the smit.script file in the default directory (usually the
home directory). This problem occurs for one of the following reasons:
v Your home directory was inadvertently deleted, and you do not have write permission for the alternate directory
assigned by the operating system.
v The permissions on your default (home) directory have been changed.
User response: Obtain write permission to the smit.script file by doing the following:
1. Ensure that your default (home) directory is the expected default directory by entering the echo $HOME command
to examine the $HOME environment variable.
2. Verify that you have write permission to the default (home) directory by running the ls -l command from the parent
of the home directory. Use the chmod command to change permission, if necessary.
3. Verify that you have write permission to the smit.script in your default (home) directory by running the ls -l
command. Run the chmod command to change permission, if necessary.

1800-106 An error occurred

Problem determination: This error occurs for one of the following reasons:
v While using the System Management Interface Tool (SMIT), you chose an option in which SMIT tried to run a
command that is not currently available in your system.
v You chose an option in which SMIT started a command that returned an error message.
User response: Determine the problem that SMIT is having with the command by doing the following:
1. View the end of the smit.log file to check which command SMIT tried to run. The smit.log file is located in your
home directory.
2. Try running the command yourself. If the command does not exist, install it on your system.

198 Message Center Reference

3. If an error message returns after the command has been reentered, check that error message for more
information.

Chapter 59. Message Component 1800 199

200 Message Center Reference
Chapter 60. Message Component 1820
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001 asl_screen subroutine

002 asl_screen subroutine
asl_function_key subroutine
003-004 asl_screen subroutine
asl_print_screen subroutine
005-006 asl_screen subroutine
asl_init_screen subroutine
007 asl_read subroutine
asl_init_screen subroutine
008 asl_init_screen subroutine
asl_ring subroutine
009 asl_init_screen subroutine
010 asl_init_screen subroutine
asl_print_screen subroutine
011-013 asl_init_screen subroutine
014 asl_init_screen subroutine
asl_msg subroutine
015 asl_init_screen subroutine
016 asl_vnote subroutine
asl_msg subroutine
017 asl_vnote subroutine
018 asl_msg subroutine
019 asl_shell subroutine
asl_init_screen subroutine
asl_msg subroutine
020 asl_msg subroutine
asl_shell subroutine
021 asl_msg subroutine
asl_clear_buffer_screen subroutine
022 asl_msg subroutine
asl_wprintw subroutine
asl_wchar_wprintw subroutine
023 asl_check_file_entriessubroutine
asl_msg subroutine
024 asl_msg subroutine
asl_help subroutine
025 asl_msg subroutine
026 asl_msg subroutine
asl_reallotc subroutine
027 asl_malloct subroutine
028 asl_msg subroutine
asl_reduce_sbrks subroutine
029 asl_msg subroutine
asl_strcpy_max subroutine
030 asl_strcat_max subroutine
asl_msg subroutine

© Copyright IBM Corp. 2003, 2004 201

031 asl_execute subroutine
032 asl_check_file_entries subroutine
asl_execute subroutine
033 asl_check_file_entries subroutine
asl_msg subroutine
034 asl_init subroutine
asl_msg subroutine
035 asl_shell subroutine
036 asl_list_waddstr subroutine
037 asl_vnote subroutine
asl_shell subroutine
1820-037 Error Recovery Information
038 asl_help subroutine
asl_curses_rc subroutine
1820-038 Error Recovery Information

Detailed Information for Message Component 1820

1820-037 An internal error or system error has occurred. See the log file for further information
Problem determination: While using the System Management Interface Tool (SMIT), the system ran out of paging
space.
User response: Do one of the following:
v Stop unnecessary processes by doing the following:
1. Run the ps -ef command to list the processes that are currently running.
2. Run the kill -q command to stop some of the processes that are not necessary at this time.
3. Run the lsps -a command to check if there is now sufficient paging space.
v Increase the paging space, using SMIT, by doing one of the following:
1. From the command line, type:
smit storage
2. From the menu, select the Paging Space option, then select the Change/Show Characteristics of a Paging
Space option.
3. Add the number of partitions.

OR

From the command line, type:

chps -s# PagingSpace

where # represents the number of additional partitions and PagingSpace is the name of the paging space to be
increased.
Problem determination: While running an application from SMIT, the DATA segment was exceeded because the
size of a user’s DATA segment was set too low when the new user was created.
User response: Increase the size of the user’s DATA segment by doing the following:
1. Edit the /etc/security/limits file to change the user’s DATA segment to the default size (specified in the file).
2. Run the application again.
Problem determination: You attempted to load too many optional software products or updates at once.
User response: Reload the software products or updates, selecting fewer items in SMIT to load.

202 Message Center Reference

1820-038 Internal error: error in call to libcur/libcurses at line Number
Explanation: The size of the user’s DATA segment was set too low when the user was created. The error occurred
while selecting the Using SMIT (information only) option from the System Management Interface Tool (SMIT) Main
Menu.
User response: Increase the size of the user’s DATA segment by doing the following:
1. Edit the /etc/security/limits file to change the user’s DATA segment to the default size (specified in the file).
2. Run the application again.

Chapter 60. Message Component 1820 203

204 Message Center Reference
Chapter 61. Message Component 1831
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

For more information on all 1831 error messages, see Network File System Overview for System
Management in Networks and communication management.

003–004 nfsd daemon

005–019 mount
1831-008 Error Recovery Information
1831-011 Error Recovery Information
020–026 portmap daemon
027–043 ypbind daemon
129–136 chkey
137–140 keylogin
141–150 ypcat
147–150 ypmatch
151–164 yppasswd
165–180 ypwhich
181–195 exportfs
196–208 nfsstat
209–213 rusers
rusersd daemon
214–228 yppasswdd daemon
229–234 ypupdated daemon
237–240 rwall
rwalld daemon
241–244 spray
sprayd daemon
245–256 rpcinfo
256–262 rusers
rusersd daemon
263–264 rwall
rwalld daemon
265 spray
sprayd daemon
266–269 automount daemon
270–280 keyserv daemon
281–325 rexd daemon
326–334 on
335–349 bootparamd daemon
365–376 makedbm
377–392 ypserv daemon
393–400 ypset
401–425 ypxfr
429–434 newkey
437–453 yppoll
454–484 yppush
485–499 ypinit

© Copyright IBM Corp. 2003, 2004 205

507–513 automount
mount
514–521 rpc.pcnfsd daemon
522–523 rpcgen
528–542 nfso

Detailed Information for Message Component 1831

1831-008 Giving up on: DeviceName

Explanation: You attempted to unmount a file to a drive that is locked into active mode, but the system has stopped
trying to access the drive.
User response: Reboot the system.

1831-011 Access denied for DeviceName

Explanation: You attempted to unmount a file to a drive that is locked into active mode.
User response: Reboot the system.

206 Message Center Reference

Chapter 62. Message Component 2053
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–056 mwm
101–119 mwm

© Copyright IBM Corp. 2003, 2004 207

208 Message Center Reference
Chapter 63. Message Component 2054
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

201 XmNarrowDirection resource in XmArrowButton widget class

XmNarrowDirection resource in XmArrowButtonGadget widget class
202 XmNresizePolicy resource in XmBulletinBoard widget class
203 XmNdialogStyle resource in XmBulletinBoard widget class
204 XmNshadowType resource in XmBulletinBoard widget class
XmNshadowType resource in XmDrawnButton widget class
XmNshadowType resource in XmFrame widget class
205 XmNbuttonFontList resource
XmNlabelFontList resource
XmNtextFontList resource in XmBulletinBoard widget class
211–212 XmCascadeButton widget class
XmCascadeButtonGadget widget class
213 XmNmappingDelay resource in XmCascadeButton widget class
XmNmappingDelay resource in XmCascadeButtonGadget widget class
214 XmCascadeButton widget class
XmCascadeButtonGadget widget class
215 XGrabPointer function
XtGrabPointer function
216 XGrabKeyboard function
XtGrabKeyboard function
221 XmCommand widget class
XmNdialogType resource in XmSelectionBox widget class
222 XmCommandGetChild function
223 XmCommandAppendValue function
XmCommandSetValue function
224 XmCommandAppendValue function
225 XmCommand widget class
XmNmustMatch resource in XmSelectionBox widget class
226 XmCommand widget class
XmSelectionBox widget class
231 XmClipboardCopy function
232 XmClipboardEndCopy function
233 XmClipboardCopy function
241–242 XmDialogShell widget class
252 XmNresizePolicy resource in XmDrawingArea widget class
261–268 XmForm widget class
272 XmFrame widget class
282 XmNunitType resource in XmGadget widget class
XmNunitType resource in XmManager widget class
XmNunitType resource in XmPrimitive widget class
284 XmNtopShadowPixmap resource
XmNbottomShadowPixmap resource
XmNhighlightPixmap resource in XmPrimitive widget class
291 XmNlabelType resource in XmLabel widget class
XmNlabelType resource in XmLabelGadget widget class

© Copyright IBM Corp. 2003, 2004 209

292 XmNalignment resource in XmLabel widget class
XmNalignment resource in XmLabelGadget widget class
XmNstringDirection resource in XmManager widget class
293 XmNstringDirection resource in XmLabel widget class
XmNstringDirection resource in XmLabelGadget widget class
294 XmNlabelString resource in XmLabel widget class
XmNlabelString resource in XmLabelGadget widget class
295 XmNacceleratorText resource in XmLabel widget class
XmNacceleratorText resource in XmLabelGadget widget class
300 XmNvisibleItemCount resource in XmList widget class
301 XmNselectionPolicy resource in XmList widget class
302 XmNlistSizePolicy resource in XmList widget class
303 XmNscrollbarDisplayPolicy resource in XmList widget class
304 XmNstringDirection resource in XmList widget class
305 XmNlistSizePolicy resource in XmList widget class
306 XmNitemCount resource in XmList widget class
308 XmNitemCount resource in XmList widget class
XmListDeleteItem function
XmListDeleteItems function
XmListDeletePos function
XmListDeleteItemsPos function
309 XmListSetHorizPos function
311 XmNlistSpacing resource in XmList widget class
312 XmNitemCount resource
XmNitems resource in XmList widget class
313 XmNselectedItemCount resource in XmList widget class
314 XmNselectedItemCount resource
XmNselectedItems resource in XmList widget class
315 XmNtopItemPosition resource in XmList widget class
316 XmNitemCount resource
XmNitems resource in XmList widget class
321 XmNmenuBar resource in XmMainWindow widget class
322 XmNcommandWindow resource in XmMainWindow widget class
331 XmMenuShell widget class
332 XmMenuShell widget class
XmCreatePopupMenu function
341 XmNdialogType resource in XmMessageBox widget class
342 XmNdefaultButtonType resource in XmMessageBox widget class
343 XmNmessageAlignment resource in XmMessageBox widget class
344 XmMessageBoxGetChild function
345 XmMessageBox widget class
354 XmNpaneMinimum resource in XmPanedWindow widget class
355 XmNpaneMaximum resource in XmPanedWindow widget class
356 XmNpaneMinimum resource
XmNpaneMaximum resource in XmPanedWindow widget class
357–359 XmPanedWindow widget class
371–373 XmAddProtocols function
402–404 XmRowColumn widget class
405–408 XmNmenuHelpWidget resource in XmRowColumn widget class
409 XmNrowColumnType resource in XmRowColumn widget class
410 XmCreatePulldownMenu function
411 XmNrowColumnType resource in XmRowColumn widget class
412–413 XmNorientation resource in XmRowColumn widget class
414–415 XmNpacking resource in XmRowColumn widget class
416–417 XmNentryAlignment resource in XmRowColumn widget class
418 XmNisHomogeneous resource in XmRowColumn widget class
419 XmNentryClass resource in XmRowColumn widget class

210 Message Center Reference

420 XmNwhichButton resource in XmRowColumn widget class
421–422 XmNmenuPost resource in XmRowColumn widget class
423–425 XmRowColumn widget class
426–427 XmNisHomogeneous resource in XmRowColumn widget class
428 XmRowColumn widget class
429 XmNmnemonic resource in XmRowColumn widget class
431 XmNminimum resource
XmNmaximum resource in XmScale widget class
432–433 XmNvalue resource in XmScale widget class
434 XmNorientation resource in XmScale widget class
435 XmNprocessingDirection resource in XmScale widget class
436 XmNhighlightThickness resource in XmScale widget class
437–438 XmNscaleMultiple resource in XmScale widget class
439 XmNmaximum resource in XmScale widget class
441 XmNminimum resource in XmScrollBar widget class
442 XmNincrement resource in XmScrollBar widget class
443–444 XmNvalue resource in XmScrollBar widget class
445 XmNorientation resource in XmScrollBar widget class
446 XmNprocessingDirection resource in XmScrollBar widget class
447 XmNincrement resource in XmScrollBar widget class
448 XmNpageIncrement resource in XmScrollBar widget class
449 XmNinitialDelay resource in XmScrollBar widget class
450 XmNrepeatDelay resource in XmScrollBar widget class
453 XmNsliderSize resource in XmScrollBar widget class
461 XmNscrollBarDisplayPolicy resource in XmScrolledWindow widget class
462 XmNscrollingPolicy resource in XmScrolledWindow widget class
463 XmNvisualPolicy resource in XmScrolledWindow widget class
464 XmNscrollBarPlacement resource in XmScrolledWindow widget class
466 XmNscrollingPolicy resource in XmScrolledWindow widget class
467–468 XmNvisualPolicy resource in XmScrolledWindow widget class
469 XmNscrollingPolicy resource in XmScrolledWindow widget class
470 XmNclipWindow resource in XmScrolledWindow widget class
471 XmScrollVisible function
481–482 XmNdialogType resource in XmSelectionBox widget class
483 XmSelectionBox widget class
484 XmSelectionBoxGetChild function
491 XmNseparatorType resource in XmSeparator widget class
XmNseparatorType resource in XmSeparatorGadget widget class
492 XmNorientation resource in XmSeparator widget class
XmNorientation resource in XmSeparatorGadget widget class
501 XmNsource resource in XmText widget class
502 XmNeditMode resource in XmText widget class
503 XmNeditable resource in XmText widget class
504 XmText widget class
505 XmNrows resource in XmText widget class
506–510 XmNfontList resource in XmText widget class
511 XmNcursorPosition resource in XmTextField widget class
513 XmTextField widget class
514 XmNcolumns resource in XmTextField widget class
521 XmNindicatorType resource in XmToggleButton widget class
XmNindicatorType resource in XmToggleButtonGadget widget class
531 XmNnavigationType resource in XmManager widget class
541 XmNdeleteResponse resource in VendorShell widget class
542 XmNpreeditType resource in VendorShell widget class
545 VendorShell widget class
561 XmGetColors function

Chapter 63. Message Component 2054 211

562–563 XmNbackground resource in Core widget class
571–573 XmNinputMethod resource in VendorShell widget class
574 XmImGetXIM function
591 XmDisplay widget class
603 XmInternAtom function
614 XGrabPointer function
616 XmDragStart function
631 XmDragIcon widget class
632 XmNpixmap resource in XmDragIcon widget class
641 XmNblendModel resource in XmDragContext widget class
642 XmNattachment resource in XmDragIcon widget class
644 XmNblendModel resource in XmDragContext widget class
652 XmNanimationPixmapDepth resource in XmDropSite registry
661 XmNdropSiteType resource in XmDropSite registry
662–663 XmDragContext widget class
664 XmDropSiteRegister function
665 XmNdropRectangles resource in XmDropSite registry
666–667 XmDropSiteRegister function
668 XmNdropSiteType resource in XmDropSite registry
669 XmNdropRectangles resource in XmDropSite registry
670–672 XmDropSiteRegister function
701–702 XmRepTypeValidValue function
721 XmScreen widget class
722 XmGetXmScreen function

212 Message Center Reference

Chapter 64. Message Component 2055
Messages 2055-000 through 2055-416 are associated with AIXwindows. For more information, see AIX 5L
Version 5.3 AIXwindows Programming Guide.

© Copyright IBM Corp. 2003, 2004 213

214 Message Center Reference
Chapter 65. Message Component 2056
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

For more information, see AIX 5L Version 5.3 AIXwindows Programming Guide.

000 d_dupl_opt
001 d_unknown_opt
002 d_add_source
003 src_open
004 src_read
005 bug_check
006 src_trucate
007 out_of_range
008 unterm_seq
009 control_char
010 unknown_seq
011 backslash_ignored
012 name_too_long
013 out_of_memory
014 syntax
015 undefined
016 ctx_req
017 not_impl
018 wrong_type
019 unsupported
020 supersede
021 previous_def
022 non_pvt
023 arg_count
024 arg_type
025 obj_type
026 never_def
027 dup_list
028 list_item
029 prev_error
030 submit_spr
032 d_miss_opt_arg
033 listing_open
034 listing_write
035 inv_module
036 src_limit
037 src_null_char
038 summary
039 uid_open
040 no_uid
041 create_proc
042 create_proc_inv

© Copyright IBM Corp. 2003, 2004 215

043 create_proc_req
044 null circular_def
045 circular_def
046 d_no_source
047 single_occur
048 d_single_control
049 unknown_charset
050 names
051 single_letter
052 dup_letter
053 icon_width
054 icon_letter
055 too_many
057 gadget_not_sup
058 operand_type
060 d_unsupp_const
061 d_too_many_dirs
062 d_src_close
063 d_circular_ref
064 d_override_builtin
065 d_no_enumset
066 d_invalid_enumval
067 d_bad_lang_value
068 d_widget_cycle
069 d_value_too_large
070 d_illegal_forward_ref
071 d_cannot_convert
072 d_bad_argument
073 d_unterm_seq_1
074 d_unterm_seq_2
075 d_unterm_seq_3
076 d_unterm_seq_4
077 d_undefined_1
078 d_undefined_2
079 d_undefined_3
080 d_undefined_4
081 d_uid_write

216 Message Center Reference

Chapter 66. Message Component 3001
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

001–200 sysck
3001-023 Error Recovery Information
201–400 grpck
401–600 pwdck
601–800 usrck

Detailed Information for Message Component 3001

3001-023 The file FileName has the wrong file mode

Problem determination:
v During the installation of system products, the sysck command was run on a file that did not have the correct
mode, as specified in the /etc/security/sysck.cfg file.
v From the command line, you ran the following command:
tcbck -n [Filename | ALL]

and a specified file did not have the correct mode, as shown in the /etc/security/sysck.cfg file.
User response: Check the /etc/security/sysck.cfg file for the correct mode, and use the chmod command to make
the necessary changes to the file.

© Copyright IBM Corp. 2003, 2004 217

218 Message Center Reference
Chapter 67. Message Component 3015
Messages associated with component 3015 refer to the chlicense command.

© Copyright IBM Corp. 2003, 2004 219

220 Message Center Reference
Chapter 68. Message Component 4050
Many messages associated with this component ID refer to the same command. The message IDs are
grouped below in numerical order according to the command to which they refer.

Certain messages refer to more than one command. In these cases, each command is listed as a choice.

Find the appropriate range of message IDs below. To see the reference article for an associated
command, select the appropriate command name.

000 quotaon
001 quotaon
repqota
002–003 quotaon
004 edquota
quotacheck
quotaon
005 quotaon
100–101 quotacheck
102 edquota
104 quotacheck
105 edquota
quotacheck
106–109 quotacheck
110 edquota
quotacheck
repqota
201–205 quota
206 edquota
quota
207–208 quota
209 edquota
quota
210 quota
212 edquota
quota
quotacheck
quotaon
213 edquota
quota
300 quota
301–303 edquota
304 edquota
quota
quotacheck
quotaon
305 edquota
quotacheck
307–308 edquota
quota
309–313 edquota
401–402 quot
quotacheck
500 repqota

© Copyright IBM Corp. 2003, 2004 221

501 edquota
quota
repqota
502 repqota

222 Message Center Reference

Appendix. Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that only
that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the
exchange of information between independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation
Dept. LRAS/Bldg. 003
11400 Burnet Road
Austin, TX 78758-3498
U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases,
payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by
IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any
equivalent agreement between us.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:

© Copyright IBM Corp. 2003, 2004 223

IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of
the materials for this IBM product and use of those Web sites is at your own risk.

This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.

Each copy or any portion of these sample programs or any derivative work, must include a copyright
notice as follows:
(c) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (c)
Copyright IBM Corp. _enter the year or years_. All rights reserved.

Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States,
other countries, or both:
v AIX
v AIX 5L
v IBM

Other company, product, or service names may be trademarks or service marks of others.

224 Message Center Reference

Readers’ Comments — We’d Like to Hear from You
AIX 5L Version 5.3
Message Center Reference

Publication No. SC23-4901-00

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied Very Dissatisfied

Accurate h h h h h
Complete h h h h h
Easy to find h h h h h
Easy to understand h h h h h
Well organized h h h h h
Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you. IBM or any other organizations will only use the
personal information that you supply to contact you about the issues that you state on this form.

Name Address

Company or Organization

Phone No.
 ___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
SC23-4901-00 򔻐򗗠򙳰 Along Line

_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM Corporation
Information Development
Department 04XA-905-6C006
11501 Burnet Road
Austin, TX 78758-3493

_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape

Cut or Fold
SC23-4901-00 Along Line
򔻐򗗠򙳰

Printed in U.S.A.

SC23-4901-00