f



AIX 1.3 900 series errors (actually 1.2.1, but...)

   � Copyright IBM Corp. 1985, 1991
  AIX Operating System Messages Reference
  Chapter 3.  Displayed Messages (Numeric)


900-041 Panic: brreada: negative block number
   Cause:  A remote read (with read ahead) was attempted with a block 
number that was less than zero (0).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

900-045 Panic: brelse: netwantsbuf
   Cause:  A synchronization error caused the system to lose track of 
which network wanted the buffer.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

900-200 symblnk: No "kmem"
   Cause:  The symblnk resolution failed because there was no memory 
available.
   Action:  Try the operation later, when more memory is available.

900-201 symblink: "nfs_readlink" fails #
    Cause:  A "Reading a symbolic link" incident was encountered on a 
Network File System (NFS) and has failed.
    Action:  Check operation between client and server and then record 
other failure conditions reported in Operators System Messages (OSM).

900-241 addgfs: Fails no free entries
    Cause:  No memory was available to allocate a mount entry.
    Action:  Try again later, verify system has enough memory, or 
increase the value of the v_mount or v_pmount system call.

900-242 deletegfs: gfs # not found
    Cause:  The operating system requested deletion of a mount entry 
that is not in the current mount table.
    Action:  Follow your local procedures for reporting software problems.

900-246 addgs: Invalid gfs #
    Cause:  The active site in topology, attempted to add this invalid 
global file system (gfs) entry to the gsmount table.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-247 addgs: Bad gfs
    Cause:  The active site in the topology tried to add this bad global 
file system (gfs) entry to the gsmount.
    Action:  Record all pertinent information and then follow your local 
procedures for reporting software problems.

900-248 gsentry: No mounts -- entry #
    Cause:  A request that was made for a given entry in the gsmount 
table cannot be satisfied because the table contains no entries.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-249 gsentry: No mounts
    Cause:  A request that was made for a given entry in the gsmount 
table cannot be satisfied because the table contains no entries.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-256 Panic: failed to allocate "gsmount" table
    Cause:  Insufficient kernel memory was available to allocate the 
incoming gsmount table (during a topology change).
    Action:  Reboot the machine.  If the problem continues, record all 
information and follow your local procedures for reporting software 
problems.

900-295 fss_close: gfs # already unmounted
    Cause:  This message is for your information only.  It indicates 
that a umount was attempted on a global file system (gfs) that was 
presently not mounted.
    Action:  No action is needed.

900-326 Panic: inodehremove: bad hash link
    Cause:  The inode hash links have been corrupted, possibly due to 
loss of lock synchronization of inode lock.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-366 niget: No response yet.  fsite=#, (g,i)=(#,#), pid=#
    Cause:  This message is for your information only.  It indicates 
that the niget subroutine has not yet received a response from the site 
indicated, reading the inode from the global file system (gfs) listed, 
for the process identifier (pid) displayed.
    Action:  No action is needed.

900-392 Panic: itst_grant: granting token, token not idle
    Cause:  An attempt was made to obtain a token (that was believed to 
be idle) but was found to already be in use.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-606 Panic: can't add any paging device
    Cause:  The device specified as a paging device could not be 
initialized as a paging device (or it did not exist).
    Action:  Check major and minor devices that are specified in the 
master file (or the values that were supplied when installing the kernel).

900-608 getgfs: Could not read pipe device's super block
    Cause:  The operating system could not read the super block of the 
file system used for the pipe device.  There may be an error in the 
operating system configuration.  The system continues to operate but 
without the pipe file system.
    Action:  Install the previous version of the operating system and 
try to run it again.  Verify the definition of the pipe file system.
    Ensure that the specified major and minor numbers are correct for 
the pipe file system that you have specified in the /etc/system file. 
Major numbers are specified in the master file, while minor numbers can 
be found by running the config command with the -t option.  This 
configures the  subdirectory of the system compilation directory.
    Before trying the new operating system, check the master and system 
files and correct any errors in them.  See the sections on operating 
system configuration in the Managing the AIX Operating System, the 
config entry in the AIX Operating System Command Reference, and the 
master entry in the AIX Operating System Technical Reference for 
information on the location and format of these files.
    If the problem persists, save the coredump, kernel load module, 
console logs, the /etc/master and /etc/system files, and any other 
pertinent information about what was happening before the error occurred 
and then follow your local procedures for reporting software problems.

900-610 Panic: Pipe does not contain a valid file system
   getgfs: magic #, dev #
    Cause:  The super block of the file system that is used for pipes 
has an invalid magic number.  The first message indicates the magic 
number that was found in the super block and, also, the major/minor 
device number of the disk on which the file system resides.  This 
message may indicate an error in the system configuration.  When this 
error occurs, the system stops running, terminates the subsystem and 
does not write a system coredump (since the partition map (which 
indicates both pipedev and dumpdev) may be corrupt).
    Action:  Install the previous version of the operating system and 
try to run it again. Verify the definition of the pipe file system.
    Ensure that the specified major and minor numbers are correct for 
the pipe file system that you have specified in the /etc/system file. 
Major numbers are specified in the master file; minor numbers can be 
found by running the config command with the -t flag (in the 
configuration subdirectory of the system compilation directory).  Using 
the ls -l /dev command, compare the major and minor numbers with those 
in the master and system files.
    Before trying the new system again, check the master and system 
files and correct any errors.  See the sections on system configuration 
in the Managing the AIX Operating System, config in the AIX Operating 
System Command Reference, and master in the AIX Operating System 
Technical Referencefor information on the location and format of these 
files.  If the problem persists, save the coredump, kernel load module, 
console logs, the /etc/master and /etc/system files, and any other 
pertinent information about what was happening before the error occurred 
and follow your local procedure for reporting software problems.

900-611 Panic: getgfs: pipe gfs out of range
    Cause:  The global file system (gfs) number which the system found 
in the super block of the file system (that is used for pipes) is out of 
range.  There may be an error in the system configuration. The system 
will stop running and will not write a system coredump, since the 
partition map (which indicates both pipedev and dumpdev) may be corrupt.
    Action:  Install the previous version of the operating system and 
try to run it again.  Verify the definition of the pipe file system.
    Ensure that the specified major and minor numbers are correct for 
the pipe file system (that you have specified in the system file). Major 
numbers are specified in the master file;  minor numbers can be found by 
running the config command with the -t flag (in the configuration 
subdirectory of the system compilation directory). Before trying the new 
system again, check the master and system files and correct any errors. 
  See the sections on the operating system configuration in the Managing 
the AIX Operating System, config in the AIX Operating System Command 
Reference, and master in the AIX Operating System Technical Reference 
for information on the location and format of these files. If the 
problem persists, save the coredump, kernel load module, console logs, 
the /etc/master and /etc/system files, and any other pertinent 
information about what was happening before the error occurred and 
follow your local procedures for reporting software problems.

900-615 Panic: mountit: could not read super block of root
    Cause:  The system received an I/O error while trying to read the 
super block of the replicated root file system.  There may be an error 
in the system configuration.  The system cannot continue running so it 
terminates and writes system core dump to the /dev/dump file (if dumping 
is enabled).
     Action:  Install the previous version of the operating system and 
try to run it again. Verify the definition of the replicated root file 
system.
    Ensure that the specified major and minor numbers are correct for 
the replicated root file system that you have specified in the system 
file.  Major numbers are specified in the master file, while minor 
numbers can be found by running the config command with the -t flag (in 
the configuration subdirectory of the system compilation directory).
    If the problem persists, save the coredump, kernel load module, 
console logs, the /etc/master and /etc/system files, and any other 
pertinent information about what was happening before the error occurred 
and follow your local procedures for reporting software problems.

900-616 Panic: mountit: root file system is not a valid file system
    Cause:  The super block of the replicated root file system has an 
invalid magic number.  There may be an error in the system 
configuration.  The system stops running, terminates, and does not dump 
core because there are no file systems available.
    Action:  Install the previous version of the operating system and 
try to run it again.  Verify the definition of the root file system.
    Ensure that the specified major and minor numbers are correct for 
the root file system that you have specified in the system file. Major 
numbers are specified in the master file; minor numbers can be found by 
running the config command with the -t flag (in the configuration 
subdirectory of the system compilation directory). If the problem 
persists, save the coredump, kernel load module, console logs, the 
/etc/master and /etc/system files, and any other pertinent information 
about what was happening before the error occurred and follow your local 
procedures for reporting software problems.

900-617 Panic: mountit: root gfs out of range
    Cause:  The global file system (gfs) number (that the system found 
in the super block of the replicated root file system) is out of range. 
  There may be an error in the system configuration.  The system cannot 
continue running so it terminates and writes system core dump to the 
dump device (if dumping is enabled).
    Action:  Install the previous version of the Operation System and 
try to run it again.  Verify the definition of the root file system.
    Ensure that the specified major and minor numbers are correct for 
the root file system that you have specified in the system file. Major 
numbers are specified in the master file; minor numbers can be found by 
running the config command with the -t flag (in the configuration 
subdirectory of the system compilation directory).
    If the problem persists, save the coredump, kernel load module, 
console logs, the /etc/master and /etc/system files, and any other 
pertinent information about what was happening before the error occurred 
and follow your local procedures for reporting software problems.

900-680 Panic: kmemalloc: "MA_SEG" not supported
    Cause:  The kmemalloc subroutine was used by a user-supplied device 
driver with the segment alignment option.  This option is currently not 
supported.
    Action:  Do not use the segment alignment option with the kmemalloc 
subroutine.

900-689 Panic: malloc botch
   MALLOC assertion failed: string on line # of file filename
    Cause:  The memory allocation support (malloc and free subroutines) 
have a corrupted allocation arena.  If a user-supplied device driver is 
part of the system, it is probably not correctly allocating, freeing, or 
manipulating dynamically allocated memory.
    Action:  Review the driver for programming errors.  Try the system 
without the driver installed.

900-720 hdinitpart: minis #, minie #
    Cause:  This message is for your information only.  It is one of a 
series of informational messages provided when overlapping minidisks are 
detected.
    Action:  No action is needed.

900-721 hdinitpart: partn #, mbrs #
    Cause:  This message is for your information only.  It is one of a 
series of informational messages provided when overlapping minidisks are 
detected.
    Action:  No action is needed.

900-723 hdinitpart: Missing bad block minidisk on drive #
    Cause:  This message indicates that the Virtual Table of Contents 
(VTOC) indicates there are one or more bad blocks, but no bad block 
minidisk can be found on the drive.
    Action:  Correct the VTOC problems with the minidisk command.

900-726 badblkinit: List allocation error for drive #
    Cause:  The attempt to allocate a bad block list for the indicated 
minidisk failed.
    Action:  Increase the available memory, or follow your local 
procedures for reporting software problems.

900-727 badblkinit: I/O buf allocation error for drive #
    Cause:  The attempt to allocate an I/O buffer for the bad block list 
(for the indicated minidisk) failed.
    Action:  Increase the available memory, or follow your local 
procedures for reporting software problems.

900-728 badblkinit: Read error, dev=#, error=#
    Cause:  The indicated error occurred trying to read the bad block 
information from the indicated device.
    Action:  Follow your local procedures for reporting software or 
hardware problems.

900-729 badblkinit: Bad magic
    Cause:  The Virtual Table of Contents (VTOC) information contained a 
bad magic number and was presumed to be invalid.
    Action:  Correct the VTOC information with the minidisks program.

900-844 svrfpr: tr_alrmleft #
    Cause:  A serious internal error occurred in the alarm device 
support that is associated with a remote process.
    Action:  Record all information and follow your local procedures for 
reporting software or hardware problems.

900-845 Panic: svrfpr: u.u_error=0 when aborting
    Cause:  The target site of a remote fork system call or a migrate 
operation aborted in the middle of receiving the process image, but did 
not have any indication as to what caused the operation to be aborted.
    Action:  Record all information, and follow your local procedures 
for reporting software problems.

900-847 getofile: Got all there is, but not enough!
    Cause:  An internal inconsistency occurred while trying to perform 
network processing (remote exec, fork, run, or migrate system calls) 
involving a process that has many open files.  This error is not, in and 
of itself, fatal but may be the cause of other observed problems.
    Action:  Note all available information.  If the problem is 
consistently reproduced, follow your local procedures for reporting 
software problems.

900-888 Panic: queue_netmsg: "fsite" negative
    Cause:  A routine is attempting to send a message to an invalid 
destination.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-891 Panic: queue_netmsg2: "fsite" negative
    Cause:  A routine is attempting to send a message to an invalid 
destination.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

900-923 Bad header checksum (site #?)
    Cause:  This message indicates that a Transparent Computing Facility 
(TCF) packet was dropped because the computed checksum of the TCF 
message header did not match the checksum included in the header.
    Action:  If this message occurs only infrequently, it is not of 
major significance and can be ignored.  If it occurs more often, then 
the checksumming configuration should be verified on all sites in the 
TCF cluster.  If the checksumming configuration is correct, the network 
most likely has a hardware problem which should be reported.

900-924 net_received: Wrong lsite #
    Cause:  The site received a Transparent Computing Facility (TCF) 
message destined for another TCF site, but which was not forwarded to 
the other site by the underlying Internet Protocol (IP) protocol layer. 
  This is most likely due to a mismatch on some node between its mapping 
of internet address and hardware address, or the wrong association of 
TCF site and internet address.
    Action:  Infrequent occurrences of this message are for your 
information only.  If this message appears frequently, then the network 
mappings should be investigated, and you should follow your local 
procedures for reporting hardware and software problems.

900-932
900-941 Bad checksum from site #
    Cause:  This message indicates that a Transparent Computing Facility 
(TCF) packet was dropped because the computed checksum of the TCF 
message did not match the checksum included in the header.
    Action:  If this message occurs infrequently, it is not of major 
importance and can be ignored.  If it occurs more often, then the 
checksumming configuration should be verified on all sites in the TCF 
cluster.  If the checksumming configuration is correct, the network most 
likely has a hardware problem which should be reported.

900-956 Panic: network.c: attempted to use an unconfigured network device
    Cause:  The system was unable to proceed because it attempted to 
send Transparent Computing Facility (TCF) traffic through a network 
interface device that did not exist.
    Action:  Verify that the network device is configured into the 
system kernel, and that the device is attached and available.  If these 
are both true, then follow your local procedures for reporting software 
or hardware problems.

900-957 procchar char received from local site
    Cause:  This message indicates that this site is having its 
Transparent Computing Facility (TCF) traffic disabled by another site in 
order to resolve an inconsistency caused by this site.
    Action:  Correct the inconsistencies and then use the clusterstart 
command.

900-958 procchar message message
    Cause:  This message is part of a multiple line message that 
indicates that the site received a special control message telling it to 
disable Transparent Computing Facility (TCF) activities, due to some 
problem or inconsistency.
    Action:  Correct the problem indicated in the procchar message.

901-020 page_fork: proc has too many data vsegs
    Cause:  A process has too many data virtual segments (vsegs) to 
complete this remote execution.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-124 Panic: nmrelse: "netwants" not found
    Cause:  A network interface set a flag that requested a network 
buffer which cannot be located.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-224 ptrksend: Too many PIDs and/or PGRPs with origin site siteno
    Cause:  The amount of network processing information on a single 
site exceeds the maximum capacity of the process tracking table that was 
sent in a single Transparent Computing Facility (TCF) message. 
Consequently, TCF traffic is disabled.
    Action:  Follow your local procedures for reporting software or 
hardware problems.

901-226 getpsp: "pid-site" table full
    Cause:  This message indicates that the capacity of the table of 
process IDs and associated cluster site numbers has been exceeded. 
Consequently, Transparent Computing Facility (TCF) traffic is disabled.
    Action:  Increase the size of the process identifier (pid)-site 
table, or follow your local procedures for reporting software problems.

901-300 qwarnflp: "warncount" out of bounds
    Cause:  A remote request for a quota warning contained a warn count 
which was out of bounds.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-400 SELECT: p_alrmp # !=NULL
    Cause:  In attempting to set an alarm, the kernel noticed that the 
alarm is in use or was not cleared by a previous use.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-403 svrselscan: Couldn't find server
    Cause:  This message is for your information only.  In attempting
   to cancel a remotely requested select, the current server could not 
be found.
    Action:  No action is needed.

901-463 Panic: bmap: can't find "indir" block for direct page
    Cause:  A request was made for an indirect block which is satisfied 
from a direct block.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-490 checksvrs: LEAVING NET!
    Cause:  A condition has occurred in which there are no server 
processes capable of responding to special messages in a reasonable 
period of time, so this site is leaving the cluster to prevent topology 
bottlenecks.
    Action:  Check that the number of server processes that is set by a 
minimum number of server processes (MINSVRPROC) is sufficient for system 
utilization and then unblock any stopped terminal.

901-540 newimage: xsite #: EBADST
    Cause:  The site which was specified for remote execution is not a 
valid site number (that is, not in range 1..32).
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-560 Panic: exit: "init" died
    Cause:  The init process has stopped.  The subsystem will terminate 
and write system core dump to the /dev/dump file, (if dumping is enabled).
    Action:  Reboot and try again.  If the problem reoccurs, run with 
the previous version of the AIX Operating System kernel.  Save the 
coredump, kernel load module, console logs, and any other pertinent 
information about what was happening before the error occurred and 
follow your local procedures for reporting software problems.

901-565 Panic: proc_checks: out of system PIDs
    Cause:  While trying to generate a new process, the system could not 
locate an unused Process Identification (PID) number.
    Action:  The cause may be a unique set of circumstances or an errant 
program.  One or more processes probably got into a state where they 
continuously "forked off" (due to the fork system call) new processes. 
If the problem persists, the system administrator should consider 
shifting some of the load from this machine to another one on the cluster.
    If the problem reoccurs, run with the previous version of the AIX 
Operating System kernel.  Save the coredump, kernel load module, console 
logs, and any other pertinent information about what was happening 
before the error occurred and follow your local procedures for reporting 
software problems.

901-606 Panic: fsumount: no "pmount"
    Cause:  A request was made to unmount a device which was not 
physically mounted.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-660 startnet: No cluster communication device detected
    Cause:  No network devices have been configured into this kernel and 
it is not capable of forming or joining a Transparent Computing Facility 
(TCF) cluster.
    Action:  Determine if a network device is available on this machine.

901-662 sysstart: init
    Cause:  The kernel failed to execute the /etc/init file and will 
attempt to access a copy from another cluster site.
    Action:  Check the permissions and residence of an executable 
version of the /etc/init file on this machine.

901-712 Panic: timeout table full
    Cause:  All of the timeout slots are in use.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-743 Panic: install_token: not open
    Cause:  An attempt is being made to grant a file token to a file 
descriptor which is no longer open.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-776 tcb_free: string conflict count #, calculated #
    Cause:  The list of free token control blocks does not contain the 
calculated amount (the free list has been severed).
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-803 Panic: no independent site available
    Cause:  A site was separated from the cluster when it did not have a 
local copy of the root file system mounted.
    Action:  Do not attempt to separate a site from the cluster when it 
does not have a copy of the root file system mounted.

901-804 newcss: Fails interrupted by "toperror"
    Cause:  An unexpected condition occurred, such as another site 
requesting to join the partition after this topology change stabilized.
    Action:  Wait for the topology to settle, and then continue.
    Technical Information:  The recovery phase of topology change has 
been interrupted due to a topology error; the process will be restarted.

901-811 Panic: sndnewtop: send nothing
    Cause:  The active site had no mounts to distribute during a 
topology change.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

901-860 nextop: Only # "svrprocs"
    Cause:  This message is for your information only.  The topology 
process reports the existence of only # server processes (the system 
will compensate).
    Action:  No action is needed.

901-871 recover: Lost local "fsys" gfs #
    Cause:  This message is for your information only.  A locally 
mounted file system was rejected by the active topology change site (its 
unmount was requested).
    Action:  No action is needed.

901-872 recover: Release token # #
    Cause:  This message is for your information only.  Tokens are 
released after a topology change when a change of synchronization site 
occurs on a Network File System (NFS).
    Action:  No action is needed.

901-980 errioctl: Enable physical media backup not working yet
    Cause:  This message indicates an ioctl system call option (that is 
not supported on the 370) was attempted.
    Action:  Correct the application so that it does not perform this 
ioctl operation.

906-001 arp: lan address is broadcast for IP address #!
    Cause:  An address resolution protocol (arp) packet with a source 
hardware address of all ones (1) has been received.  This is an illegal 
hardware address.
    Action:  The offending machine should be removed from the net and 
the hardware or software on that machine should be corrected. Follow 
your local procedures for reporting software or hardware problems.
    Technical Information:  This message is produced by the address 
resolution protocol (arp).

906-002 arp: All zeros lan address
    Cause:  An address resolution protocol (arp) packet with a source 
hardware address of all zeros (0) has been received.  This is an illegal 
hardware address.
    Action:  The offending machine should be removed from the net and 
the hardware or software on that machine should be corrected. Follow 
your local procedures for reporting software or hardware problems.
    Technical Information:  This message is produced by the address 
resolution protocol (arp).

906-005 Duplicate IP address!! sent from lan address
    Cause:  The machine on which this message was received is using the 
same Internet address as some other machine.
    Action:  One or more of the machines using the same address must be 
removed from the net and not brought back until new and unique Internet 
addresses have been assigned to each machine.
    Technical Information:  This message is produced by the Address 
Resolution Protocol (ARP).

906-081 lo #: Can't handle "af" #
    Cause:  This message implies that some protocol family other than 
Internet Protocol (IP) was introduced into the kernel without updating 
the loopback device driver to handle it.
    Action:  This message should not be generated.  If seen, it 
indicates a serious code error.  Record all relevant data and follow 
your local procedures for reporting software problems.
    Technical Information:  This message comes from the loopback 
pseudo-device driver and should not be generated.

906-201 Panic: icmp_error
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-202 Panic: icmp len
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-241 Panic: ip_init
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-283 Panic: no available network devices
    Cause:  No network devices were configured or available at boot time 
(for the generic system).
    Action:  Configure a network device and make sure that it is 
available to the machine (virtual or otherwise).

906-321 Panic: raw_usrreq
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-361 Panic: rtfree
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-401 SELECT: p_alrmp #!=NULL
    Cause:  In attempting to set an alarm, the kernel noticed that the 
alarm is in use or was not cleared by a previous use.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-481 Panic: tcp_pulloutofband
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-521 Panic: tcp_output
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-522 Panic: tcp_output REXMT
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-561 Panic: tcp_usrreq
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-601 Panic: udp_usrreq
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-641 Panic: accept
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-681 Panic: mbinit
    Cause:  This message may be generated when trying to establish the 
mbuf (memory buffer) pool.
    Action:  Possible occurrences for (and responses to) this prompt are:
     CLBYTES (the number of bytes in a paging size "click") has
been changed to something other than 1024 or 4096, so to correct this, 
change CLBYTES back to one of the two proper values, or
     The system is lacking enough memory so that it is unable to give 
the first few K bytes of memory to the mbuf pool.  Get more memory for 
your system.

906-683 Panic: m_copy
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-687 mclput: mbuf #
    Cause:  A mbuf (memory buffer) has an attached buffer which is 
external to the mbuf pool but which does not pass consistency header checks.
    Action:  Follow your local procedures for reporting software problems.

906-721 Panic: sofree dq
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-722 Panic: soclose: NOFDREF
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-723 Panic: soaccept: !NOFDREF
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-724 Panic: receive 1
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-725 Panic: receive 1a
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-726 Panic: receive 2
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-727 Panic: receive 3
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-761 Panic: soisconnected
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-762 Panic: sbappendrights
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-763 Panic: sbflush
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-764 Panic: sbflush 2
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-765 Panic: sbdrop
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-801 Panic: uipc 1
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-802 Panic: uipc 2
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-803 Panic: uipc 3
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-804 Panic: uipc 4
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-805 Panic: piusrreq
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
     Action:  Record all information and follow your local procedures 
for reporting software problems.

906-806 Panic: unp_connect2
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-807 Panic: unp_disconnect
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

906-808 Panic: unp_externalize
    Cause:  This is a firewall panic (a second or third level check for 
some condition that has already been checked at least once before and 
found to be in proper working order).  If seen, it indicates that 
something has gone wrong with the coding of the kernel itself.
    Action:  Record all information and follow your local procedures for 
reporting software problems.

909-121 flp autoassigned fail 1
    Cause:  The automatic assignment of the floppy disk drive to a 
DOS-Merge process failed because the system couldn't allocate space for 
the required internal tables.
    Action:  Make sure that the system is configured with enough memory. 
  If not, install more memory.  Otherwise, follow your local procedures 
for reporting software problems.

909-161 Connecting "devgic" to "dma" #, #
    Cause:  This message is for your information only.  A DOS process 
attached a device with a specific Direct Memory Access (DMA) channel.
    Action:  No action is needed.

909-321 irr_level=#
    Cause:  This message is for your information only.  A virtual 
interrupt was queued on a slave interrupt level where one was already set.
    Action:  No action is needed.

909-362 PRMFAIL
    Cause:  Reprogramming of the mouse's parameters failed (possibly due 
to two DOS processes trying to use the mouse simultaneously).
    Action:  Follow your local procedures for reporting software or 
hardware problems.

909-364 AUX BOGIED
    Cause:  This message indicates a minor internal consistency problem 
in the DOS-Merge subsystem.
    Action:  Follow your local procedures for reporting software 
problems and report any related behavior in DOS processes.

909-365 AUX: cmd buff full
    Cause:  A DOS-Merge process using the mouse did not run for a while 
and the mouse was moved.  Mouse "events" will be lost because the queue 
used to record these events is full.
    Action:  This is not a serious problem, but the user should not 
expect an arbitrary number of mouse button pushes to be "remembered" if 
his DOS process is stopped.

909-366 AUX: cmd stacking
    Cause:  Mouse commands (button pushes) are being saved in a buffer 
because the DOS process using the mouse is not being run.
    Action:  No action is needed.  The events will be delivered when the 
DOS process is allowed to continue executing.

909-441 setrealdma: Couldn't lock page
    Cause:  The system was unable to lock a page (which was to be the 
target of a device dma (direct memory access) for a DOS process). The 
dma will fail.
    Action:  This shouldn't happen unless the DOS application is
   attempting an illegal dma operation.  Follow your local procedures 
for reporting software or hardware problems.

909-521 Panic: merge copy protection violation: registration failed
    Cause:  A user attempted to install DOS-Merge without following the 
standard procedure.
    Action:  Consult the installation instructions provided with your 
copy of the DOS-Merge package.

909-561 Panic: vm86start returned
    Cause:  A serious internal consistency problem occurred in the 
DOS-Merge subsystem.
    Action:  Get a kernel coredump, if possible.  Follow your local 
procedures for reporting software or hardware problems.

910-298 ehd_err_log: Read: Write error on dev #/#, blkno=#
    Cause:  This message indicates a retryable write error (an error in 
which the system must repeat a write to the disk).  This error may be 
caused by a failing fixed-disk drive.  However, it may also occasionally 
appear even though there is nothing wrong with the fixed-disk.  This is 
due to an unusual and harmless condition that causes data transfer (via 
the microchannel bus) to be repeated.
    Action:  If this message appears occasionally, then repeating the 
write operation has successfully written data to the disk.  In this 
case, this message is for your information only.  However, if you see 
this message frequently (more than once a day), you should check the 
status of the fixed disk.

910-299 ehdr_err_log: Status #### #### #### #### #### #### ####
    Cause:  This message displays the status bytes generated by the 
hardware.
    Action:  Consult your hardware documentation to determine corrective 
action.

910-302 ehddump: Bad code
    Cause:  A kernel internal routine passed an unexpected code to the 
fixed disk dump routine.
    Action:  This message indicates a serious internal error.  Follow 
your local procedures for reporting software or hardware problems.

910-305 ehddumpio: DMA channel # is busy
    Cause:  This message indicates that a Direct Memory Access (DMA) 
channel could not be allocated when trying to do a kernel coredump.
    Action:  If this happens more than once, follow your local 
procedures for reporting software or hardware problems.

910-307 ehdintr: Bad status, intrstat=#, ointrstat=#
    Cause:  This message indicates a problem with the fixed-disk drive 
controller or a temporary (and harmless) error condition on the 
microchannel bus.  This message may appear often if the computer has 
down-level microcode in the disk controller.  If this is the case, the 
following additional message will be displayed when you boot up the 
system:  "The hard file controller contains down level microcode".
    This message may appear occasionally even if the disk controller 
microcode is up to date.
    Action:  If this message appears occasionally, it is for your 
information only.  If this message appears frequently, follow your local 
procedures for reporting software or hardware problems.  You may need a 
new set of disk controller microcode.

910-320 Panic: copy protection violation
    Cause:  The superuser attempted to illicitly run a copy protected PC 
Interface (PCI) or Merge product.
    Action:  Consult your place of purchase to get a legitimate copy of 
the package.

910-321 esntable overflow: Only # registrations possible
    Cause:  The system's limit on the maximum number of registrations of 
DOS-Merge installations has been exceeded.  The most likely cause is 
that someone is trying to break the copy-protection feature of the 
DOS-Merge package.
    Action:  This should not normally be possible.  If this legitimately 
happens, service may be able to provide a new module to build a kernel 
with a larger limit.

910-360 bodygetxfile: Unknown "ldtype" #
    Cause:All of the above relate to incorrectly constructed shared 
libraries or object modules.
    Action:Rebuild the object module or shared library so that it is in 
the correct format.

910-362 getcoff: .lib section too big!
    Cause:  A load module was encountered that had a .lib section that 
exceeded the maximum allowed size.
    Action:  Correct the load module problems, if you can.  Otherwise, 
follow your local procedures for reporting software problems.

910-401 fdpark: Motor(s) not killed, I/O still pending
    Cause:  The system tried to reboot while there was still an I/O 
pending on one of the diskette drives.  This should not happen in normal 
operations.  The system normally waits for an I/O to complete when doing 
a clean reboot.  However, certain other failures may cause the condition 
which produces this message.
    Action:  If a floppy diskette was being written, it may be 
corrupted.  Otherwise, this message is for your information only.

910-402 fdstate: Timed out on diskette drive #
    Cause:  The diskette (or diskette controller) failed to complete an 
expected state transition in a reasonable period of time.  This 
indicates a hardware problem.
    Action:  Note the error symptoms and run diskette diagnostics from 
the reference diskette (if possible).  Otherwise, follow your local 
procedures for reporting hardware problems.

910-403 Panic: fdcalc: verify botch
    Cause:  Due to an internal software error, the kernel was unable to 
find a sector on the floppy disk and verify its contents.
    Action:  Record all recent messages, get a coredump (if possible), 
and follow your local procedures for reporting software or
   hardware problems.

910-404 Panic: fdvercmp: zero "fdw_needsver"???
    Cause:  An Internal logic error was found in diskette driver.
    Action:  Record all recent messages, get a coredump (if possible), 
and follow your local procedures for reporting software or
   hardware problems.

910-406 fd_err_log: Write error on dev #/#, blkno=#
    Cause:  Either the diskette is bad, or the diskette is 
write-protected (in the latter case, the message will so indicate).
    Action:  Defeat the write protection on the diskette or use another 
diskette.  Also, reformatting the bad diskette may make it usable.

910-423
910-424 fdstate: NULL bp
    Cause:  This message is for your information only.  This message 
indicates a recoverable internal error in the kernel.
    Action:  No action is needed.

910-440 detach_devpg: No "pvsp" for #
    Cause:  A recoverable internal error occurred in the DOS-Merge 
subsystem.
    Action:  Note what DOS-Merge users were doing on the system.  If the 
message is reproducible, follow your local procedures for reporting 
software or hardware problems.

910-442 attach_devpg: No "pvsp" for #
    Cause:  A recoverable internal error occurred in the DOS-Merge 
subsystem.
    Action:  Note what DOS-Merge users were doing on the system.  If the 
message is reproducible, follow your local procedures for reporting 
software problems.

910-443 attach_devpg: No "ptep/dbdp" for #
    Cause:  A recoverable internal error occurred in the DOS-Merge 
subsystem.
    Action:  Note what DOS-Merge users were doing on the system.  If the 
message is reproducible, follow your local procedures for reporting 
software problems.

910-602 invalid window page
    Cause:  This message may appear on the console of a PS/2 running DOS 
Merge.  AIX emulates DOS EMS support through the use of window pages, 
which map low DOS addresses to high AIX addresses in virtual memory.  In 
response to the request of a DOS program, the AIX kernel has attempted 
to locate a window page in high virtual memory.  The DOS and AIX 
addresses were found to be improperly mapped.
    Action:  Reboot the AIX machine.  Report the error to IBM support 
with full details on what was being run.

910-603 getpages couldn't find real page
    Cause:  This message may appear on the console of a PS/2 running DOS 
Merge.  AIX emulates DOS EMS support through the use of window pages, 
which map low DOS addresses to high AIX addresses in virtual memory. 
The AIX kernel calls a routine named getpages to perform the address 
translation.  In response to the request of a DOS program, the AIX 
kernel has attempted to locate a window page in high virtual memory. 
The getpages routine found that the EMS window in high memory did not 
have an associated page in real memory.
    Action:  Reboot the AIX machine.  Report the error to IBM support 
with full details on what was being run.

910-720 Dump header #># bytes; can't dump, sorry
    Cause:  This message indicates a non-user fixable misconfiguration 
of the kernel.
    Action:  Record the numbers displayed and then follow your local 
procedures for reporting software or hardware problems.

910-724 dumpmem: Dump byte count # not aligned
    Cause:  This message indicates a non-user fixable misconfiguration 
of the kernel.
    Action:  Record the numbers displayed and then follow your local 
procedures for reporting software or hardware problems.

910-725 dumpmem: Improperly aligned dump address
    Cause:  This message indicates a non-user fixable misconfiguration 
of the kernel.
    Action:  Record the numbers displayed and then follow your local 
procedures for reporting software or hardware problems.

910-764 Panic: startup: inode table allocation error
    Cause:  A serious internal consistency failure has occurred (with 
respect to the inode table).
    Action:  Follow your local procedures for reporting software or 
hardware problems.

910-840 Panic: pmwinit
    Cause:  The kernel failed to allocate one of its internal data 
structures.
    Action:  If running with a supported amount of memory (>=3M bytes), 
then follow your local procedures for reporting software or hardware 
problems Otherwise, get more memory.

910-880 Bad PPI command "ms_ppi"
    Cause:  If this message appears, it would indicate a minor internal 
consistency problem in the mouse driver.
    Action:  Follow your local procedures for reporting software or 
hardware problems.

910-881 BD ACK #
    Cause:  The problem is most likely with the mouse hardware.
    Action:  Run diagnostics on the mouse.  Otherwise, Follow your local 
procedures for reporting hardware problems.

910-882 BD AA #
    Cause:  The problem is most likely with the mouse hardware.
    Action:  Run diagnostics on the mouse.  Otherwise, Follow your local 
procedures for reporting hardware problems.

910-883 BD 00 #
    Cause:  The problem is most likely with the mouse hardware.
    Action:  Run diagnostics on the mouse.  Otherwise, Follow your local 
procedures for reporting hardware problems.

910-972 LOW ON SWAP SPACE!  Can't find any process to kill!
    Cause:  The system is attempting to terminate processes to obtain 
space, but cannot find any processes that are appropriate to stop.
    Action:  Increase the amount of swap space available to the system.

910-973
910-974 Process # killed: no swap space
    Cause:  A Process whose Process Identifier (PID) is identified was 
terminated by the system because there was insufficient swap space for 
it to run.
    Action:  Increase the amount of swap space available to the system.

910-975 swkill: Still need # pages
    Cause:  The system is attempting to terminate processes to obtain 
space, and requires the indicated number of pages.
    Action:  Increase the amount of swap space available to the system.

910-979 Panic: vinifod: paging from small block file
    Cause:  An executable load module was run and was stored completely 
in the inode.  Running such a module is usually impossible because a 
well-formed load module is too large to be stored in such a file.
    Action:  Recreate the load module (it is malformed).

911-000 Pginit: Number of boards found > NPEGS
    Cause:  More Ethernet boards were found in the machine than were 
actually configured.
    Action:  Reconfigure if you want to use the additional cards.

911-001 Pginit: pgcsr POS is bogus # !
    Cause:  The hardware configuration for the Ethernet card is incorrect.
    Action:  Run the configuration program and correct the configuration 
information.

911-002 Panic: pginit: bad POS info
    Cause:  The Ethernet card was incorrectly configured.
    Action:  Return the hardware configuration support and correctly 
configure the Ethernet card.

911-009 Pgrint: Short packet #
    Cause:  A minor handshaking problem with the Ethernet card has 
caused a packet to be dropped.
    Action:  No action is needed, unless there is a problem with 
Ethernet communications.  Otherwise, this message is for your 
information only.

911-010 pg_isw: CBL is null with CU active!
    Cause:  A handshaking problem with the Ethernet card has occurred.
    Action:  If the system has Ethernet problems following this message, 
follow your local procedures for reporting software or hardware 
problems.  Otherwise, this message is for your information only.

911-011 pg_isw: PG appears "wedged"
    Cause:  This message is for your information only.  The Ethernet 
driver has decided that the card needs to be reset and reprogrammed. 
The system will recover.
    Action:  No action is needed.

911-041
911-042
911-049 Process # killed: no swap space
    Cause:  A Process whose Process Identifier (PID) is identified was 
terminated by the system because there was insufficient swap space for 
it to run.
    Action:  Increase the amount of swap space available to the system.

911-120 Panic: intrattach: couldn't alloc "intrstructs"
    Cause:  The system was unable to allocate memory for one of its 
internal data structures.
    Action:  Make sure that you are running in a configuration that is 
supported by the product.  This should only occur during start up on a 
system which has very little memory.

911-123 Panic: intrattach: ran out of "intrstructs"
    Cause:  The system was unable to allocate memory for one of its 
internal data structures.
    Action:  Make sure that you are running in a configuration that is 
supported by the product.  This should only occur during start up on a 
system which has very little memory.

911-280 sthdinita: Can't get "sthd" POS "config" data
    Cause:  The system doesn't acknowledge that there is a Small 
Computer Systems Interface (SCSI) disk controller present in your machine.
    Action:  Bootup the reference diskette and make sure that the 
configuration is correct.  If it is correct, follow yourr local 
procedures for reporting software or hardware problems.

911-282 sthdgettype: Incorrect argument
    Cause:  This message indicates a serious kernel internal logic problem.
    Action:  Follow your local procedures for reporting software or 
hardware problems.

911-283 sthdfsm: Spurious interrupt, stat=#
    Cause:  A minor hardware problem could cause this problem.  A 
misconfigured system might also cause this.
    Action:  If this happens often, you should run diagnostics on your 
system and follow yourr local procedures for reporting software or 
hardware problems.  If not, this message is for your information only.

911-286 Panic: sthdfsm: BUSY stuck on ssb req
    Cause:  The above error is caused by disk hardware failures.
    Action:  Run diagnostics on the disk controller and drive and then 
follow your local procedures for reporting hardware problems.

911-287 Panic: sthdfsm: no DATAREQ on ssb
    Cause:  The above errors are caused by disk hardware failures.
    Action:  Run diagnostics on the disk controller and drive and then 
follow your local procedures for reporting hardware problems.

911-290 sthdfsm: cyl=#, trk=#, sect=#
    Cause:  This message is for your information only.  Part of a 
message has indicated an error on a fixed disk drive.
    Action:  No action is needed.

911-291 Panic: sthdcmd: BUSY stuck on ccb req
   Cause:  A hardware problem has occurred with the Small Computer 
Systems Interface (SCSI) disk controller.
   Action:  Run the diagnostics from the reference diskette on the fixed 
disk (be careful not to select any destructive tests). Otherwise, follow 
your local procedures for reporting hardware problems.

911-292 Panic: sthdcmd: no DATAREQ for ccb
   Cause:  A hardware problem has occurred with the Small Computer 
Systems Interface (SCSI) disk controller.
   Action:  Run the diagnostics from the reference diskette on the fixed 
disk (be careful not to select any destructive tests). Otherwise, follow 
your local procedures for reporting hardware problems.

911-295 sthddump: Bad code
   Cause:  A kernel internal routine passed an unexpected code to the 
fixed disk dump routine.
   Action:  This error indicates a serious internal error.  Follow your 
local procedures for reporting software or hardware problems.

911-297 sthddumpio: DMA channel # is busy
   Cause:  This message indicates that a Direct Memory Access (DMA) 
channel could not be allocated when trying to perform a kernel coredump.
   Action:  If this happens more than once, follow your local procedures 
for reporting software or hardware problems.


911-299 sthdfsm: irs=#, S0=#, S1=#, S2=#.
   Cause:  A non-correctable, non-retryable error has occurred on the 
indicated hard drive.
   Action:  If this happens often, you should back up your fixed disk 
(to tape or to another fixed disk), then re-format the disk and rebuild 
the bad block table.  Before attempting any of this, follow your local 
procedures for reporting software or hardware problems.

911-360 tkinit: Tried to re-initialize board
   Cause:  This message is for your information only.  A minor internal 
consistency problem caused the kernel to attempt to initialize the token 
ring card twice.
   Action:  No action is needed.

911-364 tkinit: No token ring card. Option not enabled
   Cause:  The kernel was configured with the token ring driver, but 
there is no token ring present in the PS/2.
   Action:  If you want to run on the token ring, install a card. 
Otherwise, this message is for your information only.

911-365 tk_doinit: No memory for primary ring
   Cause:  The system was unable to allocate memory for one of its 
internal data structures.
   Action:  Make sure that you are running in a configuration that is 
supported by the product.  This should only occur during start up (on a 
  system which has very little memory).

911-366 tk_doinit: No memory for alternate ring
   Cause:  The system was unable to allocate memory for one of its 
internal data structures.
   Action:  Make sure that you are running in a configuration that is 
supported by the product.  This should only occur during start up (on a 
system which has very little memory).

911-367 tk_reset: Can't init unit #'s hardware
   Cause:  The indicated token ring could not be reset.
   Action:  Run diagnostics on the card.  Replace or have it serviced, 
if necessary.  Otherwise, follow your local procedures for reporting 
hardware problems.

911-368 tk_reset: Ring init unit # failed -- "init_code" #
   Cause:  The system could not reset the indicated token ring card.
    Action:  Run diagnostics on the card.  Replace or have it serviced, 
if necessary.  Otherwise, follow your local procedures for reporting 
hardware problems.

911-370 tkintr: tk_board=#, unit=#
   Cause:  This message indicates a serious problem either with the 
token ring hardware or with the present version of the driver.
    Action:  Run diagnostics on the token ring card.  If it passes, 
follow your local procedures for reporting software problems. Otherwise, 
replace the card.

911-371 isrp_low=#, interrupt vector=#
   Cause:  This message indicates a serious problem either with the 
token-ring hardware or with the version of the driver that is in use.
   Action:  Run diagnostics on the token ring card.  If it passes, 
follow your local procedures for reporting software or hardware 
problems.  Otherwise, replace the card.

911-372 Panic: tkintr: UNRECOGNIZED interrupt
   Cause:  This panic message indicates a serious problem either with 
the token-ring hardware or with the version of the driver in use.
    Action:  Run diagnostics on the token ring card.  If it passes, 
follow your local procedures for reporting software or hardware 
problems.  Otherwise, replace the card.

911-373 tk_open_complete: Ring open of unit # failed
   Cause:  This can happen for a variety of reasons.  The above message 
will be immediately followed by another message that indicates the 
specific cause of the failure.
   Action:  See the Cause and Action called for by the specific cause 
that was mentioned in the message that follows the above message.

911-375 Bad return from "TRANSMIT_DIR_COMMAND" in unit # : #
   Cause:  A handshaking problem occurred between the system and one of 
its token-ring cards.
   Action:  If network performance and behavior are not adversely 
affected, ignore this message. Otherwise, follow your local procedures 
for reporting software problems.

911-381 token_ring: <error> error in (PRIMARY) (ALTERNATE) adapter
   Cause:  The error described has been detected in either the PRIMARY 
or ALTERNATE token ring adapter board.
   Action:  Consult the documentation that accompanied the adapter 
board.  Perform the recommended actions to correct the error. Otherwise, 
follow your local procedures for reporting hardware problems.

911-405 Invalid command code
   Cause:  A handshaking problem occurred between the system and one of 
its token-ring cards.
   Action:  If network performance and behavior are not adversely 
affected, ignore this message.  Otherwise, follow your local procedures 
for reporting software or hardware problems.

911-407 Required parameter(s) not provided
   Cause:  A handshaking problem occurred between the system and one of 
its token-ring cards.
   Action:  If network performance and behavior are not adversely 
affected, ignore this message.  Otherwise, follow your local procedures 
for reporting software or hardware problems.

911-411 Inadequate receive buffers for open
   Cause:  This error is most likely due to a token ring card with 
insufficient memory.
   Action:  Run diagnostics on the token ring card.

911-412 Invalid NODE_ADDRESS
   Cause:  A handshaking problem occurred between the system and one of 
its token-ring cards.
   Action:  If network performance and behavior are not adversely 
affected, ignore this message.  Otherwise, follow your local procedures 
for reporting software or hardware problems.


911-413 Invalid adapter receive buffer len
   Cause:  A handshaking problem occurred between the system and one of 
its token-ring cards.
   Action:  If network performance and behavior are not adversely 
affected, ignore this message.  Otherwise, follow your local procedures 
for reporting software or hardware problems.

911-414 Invalid adapter transmit buffer len
   Cause:  A handshaking problem occurred between the system and one of 
its token-ring cards.
   Action:  If network performance and behavior are not adversely 
affected, ignore this message.  Otherwise, follow your local procedures 
for reporting software or hardware problems.

911-415 Unknown failure
   Cause:  Your communication task cannot complete.  One of the 
following occurred:
    The system tried to do the rename subcommand with the INftp command, 
but could not unlink the original file.
    In the ftplogger program, one of the following occurred:
-The /etc/utmp file could not be opened.
-The /etc/utmp file did not contain an expected entry for the terminal 
specified with the ftplogger program in the /etc/ports file.
-The ftplogger program could not determine which terminal it was logged 
into.
   Action:  Take the appropriate action:
    Check the permissions of the file that you tried to rename.
    Get superuser authority and edit the /etc/utmp file.  Make sure that 
all ports with a logger=pathname/ftplogger entry are specified correctly 
(the AIX Operating System Technical Reference shows the format of the 
/etc/utmp file).
   See the AIX PS/2 INmail/INnet/INftp Users Guide for details.

911-455 Panic: kernel trap
   Cause:  The kernel has detected an unrecoverable problem with its 
internal state.  The system will produce a coredump and then reboot.
   Action:  Record the internal registers, which are displayed preceding 
this "Panic".  If a coredump is successfully produced, save that as 
well.  Follow your local procedures for reporting software or hardware 
problems.

911-487 lsyscall: Getting "args": "copyin" failed
   Cause:  An application performed a system call, but the arguments to 
that call were not accessible on the user's stack.  The system call will 
fail, and the process is likely to stop soon.
   Action:  Any strange application behavior which seems to correspond 
with the occurrence of this message should be reported to the source of 
the application.

911-562 Panic: vswapout: no swap space
   Cause:  An attempt to swap out a virtual segment (vseg) failed 
because of insufficient swap space.
   Action:  Configure the AIX Operating System so that additional swap 
space is available.

911-600 x25com: Unexpected driver cmd returned
   Cause:  The on-board x.25 software posted a completion code that was 
not recognizable by the driver.
   Action:  Reload the x.25 software.

911-606 x25 software crashed or was reinitialized
   Cause:  The on-board x.25 software crashed or the driver recognizes 
that the x.25 software has been reloaded.
   Action:  Reload the x.25 software (if has not been already).

911-609 x25c_intr: Not expecting cmd #, lun #
   Cause:  A command completion status was posted by the onboard x.25, 
for which no driver request was made.
   Action:  No action is needed.  If it causes other failures, follow 
your local procedures for reporting software problems.

911-614 x25c_intr: lun mismatch # #
   Cause:  A command posted for a given logical unit number (lun) does 
not match the command block associated with the lun returned by the 
onboard x.25 software.
   Action:  No action is needed.  The machine will automatically reboot.

911-615 Panic: x25c_intr: driver "confused"
   Cause:  A command posted for a given logical unit number (lun) does 
not match the command block associated with the lun returned by the 
onboard x.25 software.
   Action:  No action is needed.  The machine will reboot automatically.

911-616 check_timeouts: x.25 software crash -- aborting
   Cause:  During a watchdog timer interrupt, the state of the driver 
noticed that the x.25 onboard software had crashed.
   Action:  Reload the x.25 software.

911-617 check_timeouts: lun mismatch # #
   Cause:  During a watchdog timer interrupt, the logical unit number 
(lun) table contained a command block for another lun table.
   Action:  Follow your local procedures for reporting software problems.

911-641 x25ip_rint: Receive failure -- receive halted
   Cause:  An error has occurred while trying to receive an x.25 packet. 
  That packet was discarded.
   Action:  If this message is seen once (or at rare intervals) it may 
be considered informational only.  Such failures are routine and usually 
indicate no problem.  If this message is seen regularly (at frequent 
intervals), investigate the x.25 hardware or in the x.25 connections.

911-642 Panic: x25_state: serverlun not open
   Cause:  The x.25com driver has not successfully opened the serverlun 
at this point.  The x.25 software must be initialized before attempting 
to use x.25ip.
   Action:  Verify that the x.25 software is properly initialized before 
using x.25ip.

911-643 Panic: x25ip_state: allocated the serverlun !!
   Cause:  The x.25 software allocated the serverlun as a user logical 
unit member (lun).
   Action:  Reboot the system.  If it reoccurs, follow your local 
procedures for reporting software or hardware problems.

911-680 x29init: Unable to allocate tables
   Cause:  A failure to allocate the required memory for the terminal 
tables occurred.
   Action:  Check the amount of memory and number of terminal sessions 
configured.

911-697 x29_signal: Couldn't locate associated terminal
   Cause:  This message is for your information only.  A signal 
generated by the onboard x.25 software for a specific logical unit 
number (lun) cannot locate a terminal associated with that lun.
   Action:  No action is needed.

911-700 x29_state: Unknown state #
   Cause:  An unknown state has been detected by the internal state
   machine of the x.29 driver.
   Action:  Follow your local procedures for reporting software problems.

915-083 klm_lockmgr: Blocking lock denied?!
   Cause:  Blocking locks should lock and eventually be granted (not 
denied).
   Action:  Check the operation of the remote lock daemon.

915-084 klm_lockmgr: Unlock denied?!
   Cause:  Unlock operations should not be denied (at least they should 
be ignored).
   Action:  Check the operation of the remote lock daemon.

915-085 klm_lockctl: ENOLCK on "KLM_CANCEL" request
    Cause:  Not expecting a shortage of locks on a cancel operation.
   Action:  Try again later.

915-120 kudp_send: Net unreachable
   Cause:  No route exists to reach the indicated recipient.
   Action:  Check validity of client request (is it properly addressed?).

915-121
915-122
915-123 kudp_send: Not enough bufs
   Cause:  This message is for your information only.  The kernel has 
run low on mbufs (memory buffers) and transmission cannot complete.
   Action:  No action is needed.  An automatic reattempt will occur.

915-124 kudp_send: if_output error #
   Cause:  An error was returned from the lower level network device.
   Action:  Check for proper operation of attached network devices.

915-161 Source IP address=#. #. #. #
   Cause:  This message is for your information only.  It is always 
generated as a companion to another notice which states what the problem 
is.  This companion message gives the specific address where that 
problem is to be found.
   Action:  No specific action is to be taken except to note the 
address.  The action to be taken at that address will be indicated by 
its companion notice.  For more information see the "NFS request from 
unprivileged port" message.

915-200 Panic: clget: null client
   Cause:  A serious error occurred while scanning the client hash 
table; system integrity believed to be compromised.
   Action:  Follow your local procedures for reporting software problems.

915-201 Panic: rfscall: null "cred"
   Cause:  The credentials structure was passed along with this remote 
request.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

915-202
915-203 NFS server name not responding still trying
   Cause:  This message is for your information only.  A communications 
failure is occurring while trying to reach the requested server (the 
server may be currently down).
   Action:  No action is needed.  The server may not have been brought 
up yet.

915-204
915-205 NFS type failed for server name: message
   Cause:  A local operation on a remote Network File System (NFS) has 
failed.
   Action:  Note the return code and follow your local procedures for 
reporting software problems.

915-280 Panic: nfs_umount: no "mntinfo"
   Cause:  The mntinfo structure associated with a mounted file system 
is invalid, yet a request to unmount the Network File System (NFS) has 
been made.
   Action:  Follow your local procedures for reporting software problems.

915-360 xdr_putrddirres: Error "xdring" dir part
   Cause:  An error occurred while trying to encode (serialize) a directory.
   Action:  Check the validity of the directory.

915-442 nfsopen: Zero inode
   Cause:  The file handle supplied in an Network File System (NFS) 
request is not a valid format.
   Action:  Try the operation again.

915-443 nfsopen: Stale ID
   Cause:  A new version of the file has been created; the old version 
is not accessible.
   Action:  Try the operation again.
   Technical Information:  The file handle supplied in an Network File 
System (NFS) request is no longer valid.

916-007 Panic: pfree: tried to "pfree" page 0
   Cause:  The system attempted to free page zero (0).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-008 Panic: pfree: freeing page 0!
   Cause:  The system attempted to free page zero (0).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-041 Panic: cetiinit: too many dev "startup" functions
   Cause:  The ceti adaptor driver attempted to add its special purpose 
startup function to the system list, but the list was already full.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-042 Panic: null ceti handler
   Cause:  The device appeared to generate an interrupt on one of the 
virtual devices that does not yet have a handler installed.
   Action:  Install the proper handler or choose another virtual machine.

916-043
916-044 Too many "ceti" input buffers -- reduced to #
   Cause:  This message is for your information only.  The number of 
configured input buffers exceeds the maximum that is allowed, so the 
maximum that is allowed will be used.
   Action:  No action is needed.

916-049 cetircv: Excessive Ethernet collisions
   Cause:  This message informs the user that the Ethernet adaptor is 
detecting an excessive number of Ethernet collisions.  This is usually 
due to a defective network or related component problem.
   Action:  Correct the network or device problem.

916-051 cetircv: Out of window Ethernet collisions
   Cause:  This message informs the user that the Ethernet adaptor has 
detected an out of window Ethernet collision.  This is usually due to a 
defective network or related component problem.
   Action:  Correct the network or device problem.

916-052 cetircv: Ethernet frame alignment error
   Cause:  This message is for your information only.  It informs the 
user that the Ethernet adaptor received a packet that had a frame 
alignment error.
   Action:  No action is needed.

916-053 cetircv: Shorted Ethernet
   Cause:  This message informs the user that the Ethernet adaptor is 
detecting an excessive number of Ethernet collisions.  This is usually 
due to a disconnection between the adaptor and the Ethernet transceiver, 
or a defective network or related component problem.
   Action:  Correct the connection or network problem.

916-054 Unknown "ceti" status=#
   Cause:  This message is for your information only.  An unexpected and 
unknown error status code was produced by the adapter.
   Action:  No action is needed.

916-055 cetircv: Unexpected error message -- msg
   Cause:  This message is for your information only.  An unexpected 
error message was generated by the adapter.
   Action:  No action is needed.

916-056 cetircv: Disabling adaptor
   Cause:  This message is for your information only.  It informs you 
that the Ethernet adaptor was disabled.
   Action:  Use the ceti command to re-enable the adaptor after the 
problem is resolved.

916-057 cetixmit: Unknown internal work type #
   Cause:  The adapter driver detected an internal inconsistency with a 
work item.
   Action:  Follow your local procedures for reporting hardware or 
software problems.

916-064 cetisnsanal: ioaddr #, sense data ####
   Cause:  This message is for your information only.  It indicates that 
sense data was read from the adaptor.
   Action:  No action is needed.

916-065 ceti_obr: Unknown type=#
   Cause:  This message is for your information only.  It indicates that 
the driver attempted to log an outboard recorder (obr) of an unknown type.
   Action:  No action is needed.

916-066 ceti_obr: Store subchannel information failed, result=#
   Cause:  This message is for your information only.  It informs the 
user that an error occurred while logging an outboard recorder (obr) record.
   Action:  No action is needed.

916-067 ceti_mdr: Store subchannel information failed, result=#
   Cause:  This message is for your information only.  It informs the 
user that an error has occurred while logging an miscellaneous data 
record (mdr).
   Action:  No action is needed.

916-068 Taking "ceti" # off-line
   Cause:  The indicated adaptor was taken off-line (due to the reason 
stated in a previous message).
   Action:  If the device is required, it must be brought back on-line.

916-069 ceti_ipc_output: Cannot handle address family #
   Cause:  Network traffic was generated for this device and found an 
address family that is not currently supported.
   Action:  Do not generate network traffic for unsupported address 
families.

916-082 ckddump: Read
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-083 ckddump: Write
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-084 ckddump: Physical memory exceeds dump space
   Cause:  The dump device minidisk is not large enough to store the 
entire system dump.
   Action:  Make the system dump minidisk larger or else reduce the size 
of the Virtual Machine (VM).

916-084 punopen: Could not get "sema"
   Cause:  This message is for your information only and regards the 
operation of the reader and punch.
   Action:  No action is needed.

916-085 blockno (number)=pageaddr+dumplo+partoff #+#+#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-085 punclose: File name name is illegal; replace by null
   Cause:  This message is for your information only and regards the 
operation of the card reader and card punch.
   Action:  No action is needed.

916-086 Bad final count in "cardio" read #, k=#
   Cause:  This message is for your information (only for the operation 
of the card reader and card punch).
   Action:  No action is needed.

916-087 rdrclose: "Close" command failed on rdr #
   Cause:  This message is for your information only and regards the 
operation of the card reader and card punch.
   Action:  No action is needed.

916-089 CP response: message
   Cause:  This message is for your information only.  It only regards 
the operation of the card reader and card punch.
   Action:  No action is needed.

916-161 "cpcmd" attached
   Cause:  This message is for your information only.  It indicates that 
the cpcmd driver is attached.
   Action:  No action is needed.

916-162 "cpinit nunits"=#, should be 1
   Cause:  This message is for your information only.  It indicates that 
more than one cpcmd units were configured (only the first can be used).
   Action:  No action is needed.

916-201 Panic: fbaintr
   Cause:  An unrecoverable error occurred in the I/O interrupt routine.
   Action:  Record all information and then follow your local procedures 
for reporting software or hardware problems.

916-202 FBAstrat: Invalid FBA disk number #
   Cause:  An I/O was attempted for a disk that is not a valid Fixed 
Block Architecture (FBA) disk.
   Action:  Follow your local procedures for reporting software or 
hardware problems.

916-203 FBAstrat: FBA disk number # is not "alive"
   Cause:  A buffer I/O was attempted and failed because the Fixed Block 
Architecture (FBA) disk was not active.
   Action:  Activate the device or correct the device configuration.

916-204 FBAstrategy: Bad partition on dev #, disk #
   Cause:  An I/O to a device failed because it did not refer to a valid 
minidisk.
   Action:  Correct the minidisk configuration (or the device 
specification).

916-205 FBAstrat: I cannot handle transfers larger than a frame yet
    Cause:  An I/O failed because the amount requested exceeded the
   maximum limit imposed by the system.
   Action:  Correct the I/O operation so that transfer does not exceed 
the limit.

916-206 FBAstrat: FBA devices can only transfer multiples of # (#req.)
   Cause:  This message indicates that an application attempted to read 
or write to a raw Fixed Block Architecture (FBA) disk but did not do so 
in the required block size.
   Action:  Correct the application to perform I/O in accordance with 
the device's count and alignment constraints (or reading from the block 
device).

916-208 FBAstart: b_active set!!
   Cause:  This message is for your information only.  It indicates that 
the sio (start channel I/O) routine was called for a device that was 
already active.
   Action:  No action is needed.

916-209 FBAstart: "sio" on dev # returned cc=#, csw=# #
   Cause:  This message is for your information only.  It indicates that 
the sio (start channel I/O) routine failed, and displays the returned 
condition code and Channel Status Word (CSW).
   Action:  No action is needed.

916-210 FBAsense: dev #, cc=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-212 FBAread: Invalid FBA disk number #
   Cause:  An I/O was attempted for a disk that is not a valid Fixed 
Block Architecture (FBA) disk.
   Action:  Follow your local procedures for reporting software or 
hardware problems.

916-213 FBAwrite: Invalid FBA disk number #
   Cause:  An I/O was attempted for a disk that is not a valid Fixed 
Block Architecture (FBA) disk.
   Action:  Follow your local procedures for reporting software or 
hardware problems.

916-214 FBAintr: "sio" on dev # returned deferred cc=#, csw=# #
   Cause:  This message is for your information only.  It indicates the 
deferred condition codes and Channel Status Word (CSW) of a failed I/O.
   Action:  No action is needed.

916-216 Whole device, errors ignored!
   Cause:  This message is for your information only.  It indicates that 
the errors reading the minidisk information from the disk are being 
ignored because the partition being opened is the minidisk
   maintenance partition.
    Action:  No action is needed.

916-217 FBAattach: No kmemalloc memory!
   Cause:  Cannot allocate memory to read the Virtual Table of Contents 
(VTOC) for a minidisk.
   Action:  Try the operation later when more memory is available.

916-220 FBAdump: Invalid FBA disk number #
   Cause:  The dump device is not a valid Fixed Block Architecture (FBA) 
disk.
   Action:  Correct the dump file configuration or the system dump
   minidisk.

916-221 FBAdump: FBA disk number # is not "alive"
   Cause:  The dump device is not an active minidisk.
   Action:  Correct the dump file configuration or the system dump minidisk.

916-222 FBAdump: Bad partition dev #, disk #
   Cause:  This message indicates that the dump partition is not a valid 
minidisk.
   Action:  Correct the dump file configuration or the system dump minidisk.

916-223 FBAdump: dev # is read-only
   Cause:  This message indicates the disk containing the dump partition 
currently linked (or attached) to the Virtual Machine (VM) is read only.
   Action:  Re-link (or attach) the disk to VM in a mode that permits 
writing.

916-224 FBAdump: Physical memory exceeds dump space
   Cause:  The dump device minidisk is not large enough to store the 
entire system dump.
   Action:  Make the system dump minidisk larger (or reduce the size of 
the Virtual Machine).

916-225 FBAdump: "sio" on dev # returned cc=#, csw[0]=#,
   csw[CSW_STATUS]=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-241 Panic: ckdstart: b_active set!!
   Cause:  The system attempted to start a ckd device that was already 
active.
   Action:  Follow your local procedures for reporting software
   problems.

916-242 Panic: ckdfree: invalid buf list
   Cause:  One (or both) of the buffer lists needed to free the used 
blocks (after the I/O completes) is invalid.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-243 Panic: ckdfree: invalid count
   Cause:  The buffer count did not match the actual I/O count.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-244 Panic: ckdinit: CCW work area too large, exceeds pagesize
   Cause:  The minimal amount of Channel Control Word (CCW) work area 
that is required to support this device is too large (in that it exceeds 
the size of a single page).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-245 Panic: ckdinit: "kmemalloc" failed
   Cause:  The system was unable to allocate the memory for the Channel 
Control Word (CCW) work area.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-247 ckddiaga4: dev # return code=#, blkct=#, devst=#
   Cause:  This message is for your information only.  It indicates the 
return information provided from the diaga4 Virtual Machine (VM) interface.
   Action:  No action is needed.

916-248 ckddiaga4: dev # sense data=#
   Cause:  This message is for your information only.  It indicates the 
sense data provided from the diaga4 Virtual Machine (VM) interface.
   Action:  No action is needed.

916-250 ckdkeysetup: # too many blocks (IDAWs)
   Cause:  This message indicates that the Count Key I/O failed
   because there were too many blocks used for Indirect Addressing Words 
(IDAWs).
   Action:  Try again with a Count Key I/O that is less complex.

916-251
916-252 ckdkeysetup: # too many blocks (CCWs)
   Cause:  This message indicates that the Count Key I/O failed because 
there were too many blocks used for Channel Control Words (CCW).
   Action:  Try again with a Count Key I/O that is less complex.

916-253 ckdsetup: CCW chain too long
   Cause:  This message is for your information only.  It indicates that 
the Channel Control Word (CCW) chain for an I/O exceeded the maximum length.
   Action:  No action is needed.  Report this as a potential programming 
error.

916-254 ckdsetup: Loop dev=#, cur=#, next=#, count=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-255 sio unit=#, blocks=#, cyl=# #, read flag=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-257 ckdstart: Nothing on queue
   Cause:  This message is for your information only.  It means that the 
start routine was called with nothing on the queue.
   Action:  No action is needed.

916-258 ckdintr: "sense" command failed
   Cause:  This message is for your information only.  It indicates the 
sense command to the device failed.
   Action:  No action is needed.

916-260 ckdintr: dev #, offline
   Cause:  The I/O to the indicated device failed because it is offline.
   Action:  Bring the hardware online and try again.

916-261 ckdintr: dev #, channel control check
   Cause:  The I/O to the indicated device caused a channel control
   check.
   Action:  Correct the hardware problems with the device.
   Otherwise, follow your local procedures for reporting hardware problems.

916-262 ckdintr: dev #, unrecoverable error
   Cause:  The I/O to the indicated device caused an unrecoverable error.
   Action:  Correct the hardware problems with the device.
   Otherwise, follow your local procedures for reporting hardware problems.

916-263 ckdintr: dev #, sense data=#
   Cause:  This message is for your information only.  It indicates that 
sense data was read from the device.
   Action:  No action is needed.

916-264 ckdretry: dev=# -- retry required blk=#, cnt=#
   Cause:  This message is for your information only.  It indicates that 
an I/O reattempt is required.
   Action:  No action is needed.  This could be an early sign of a 
hardware problem.

916-266 ckdretry: dev=# -- can't retry blk=#
   Cause:  This message is for your information only.  It indicates that 
the I/O reattempt for the block cannot be reattempted.
   Action:  No action is needed.

916-267 ckdretry: dev=# -- retry failed
   Cause:  This message is for your information only.  It indicates that 
the I/O reattempt failed.
   Action:  No action is needed.

916-268 ckdretry: dev=# -- retry okay
   Cause:  This message is for your information only.  It indicates that 
the I/O reattempt succeeded.
   Action:  No action is needed.

916-269 ckdfree: dev #, inv bp fi=#, dp=# # #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-270 ckdfree: dev=#, bp=buffer pointer, fi=file pointer, count=#, 
bcount=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-271 ckdfree: Device offline dev #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-272 ckdfree: Uncorrectable error dev #, blk #
   Cause:  An uncorrectable error on the device occurred while 
attempting to access the block indicated in the message.
   Action:  Correct the hardware problems with the device. Otherwise, 
follow your local procedures for reporting hardware problems.

916-273 ckdopen: Open disk #, R/c with # blocks
   Cause:  This message is for your information only.  It indicates that 
the opening of a new Virtual Machine (VM) minidisk occurred.
   Action:  No action is needed.

916-274 ckdvtread: No "kmemalloc" memory!
   Cause:  The attempt to read a Virtual Table of Contents (VTOC) from a 
disk failed because the allocation of the data area failed.
   Action:  Try this operation again when more memory is available.

916-275 ckd disk type disktype at disknumber is unknown
   Cause:  An unknown ckd device is attached, and is being treated as a 
3380.
   Action:  Verify the Virtual Machine (VM) configuration and 
acceptability of the ckd device, and if everything is valid, report the 
problem as a device support problem.

916-277 ckdinit: No space for CCW work areas
   Cause:  The space for Channel Control Word (CCW) work areas could not 
be allocated.
   Action:  Follow your local procedures for reporting software problems.

916-278 ckddump: Invalid "ckd" disk number #
   Cause:  The dump device is not a valid ckd disk.
   Action:  Correct the dump file configuration or the system dump minidisk.

916-279 ckddump: "ckd" disk number # is not "alive"
   Cause:  The dump device is not an active minidisk.
   Action:  Correct the dump file configuration or the system dump minidisk.

916-280 ckddump: Bad partition dev #, disk #
   Cause:  The dump partition refers to an invalid minidisk.
   Action:  Correct the dump file configuration or the system dump minidisk.

916-281 ckddump: dev # is read-only
   Cause:  The dump device is attached to the Virtual Machine (VM) read 
only.
   Action:  Correct the VM linkage of the disk that stores the dump 
device minidisk.

916-286 ckddump: # errors while writing dump
   Cause:  The number of errors indicated occurred while writing a 
system dump to a ckd disk device.
   Action:  Verify disk and system configurations, as they pertain to 
the dump device.

916-287 Begin sort
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-288 Begin follow 0 ... #, recs=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-362 Panic: getcoff: bad impure vsgrow #1
   Cause:  The virtual segment grow (vsgrow) for the mixed virtual 
segment (vseg), failed.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-363 Panic: getcoff: couldn't bind to 0
   Cause:  The bind to page zero (0) failed.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-366 getcoff: .lib section too big!
   Cause:  A load module was encountered that had a .lib section that 
exceeded the maximum allowed size.
   Action:  Correct the load module problems, if you can.  Otherwise, 
follow your local procedures for reporting software problems.

916-367 getcoff: Too many shared libraries
   Cause:  The system attempted to support too many shared libraries.
   Action:  Reduce the number of shared libraries used by the object 
module causing the error.

916-368 readcoff: Text not page aligned
   Cause:  An exec system call of a load module (whose text segment was 
not page aligned) was attempted.
   Action:  Correct the load module problems.

916-369 readcoff: Data not page aligned
   Cause:  An exec system call of a load module (whose data segment was 
not page aligned) was attempted.
   Action:  Correct the load module problems.

916-401
916-402 ILANS no devices configured
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-403 ILANS: Command Reject
   Cause:  This message is for your information only.  The ilans device 
rejected a command.
   Action:  No action is needed.

916-404 ILANS: Intervention required
   Cause:  The ilans device is shut down and requires a manual reset.
   Action:  Manually reset the ilans device.

916-405 ILANS: Bus Out Check
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-406 ILANS: Equipment check
   Cause:  This message is for your information only.  The ilans device 
issued an equipment check.
   Action:  No action is needed.

916-407 ILANS: Data check
   Cause:  This message is for your information only.  The ilans device 
issued a data check.
   Action:  No action is needed.

916-408 ILANS: Overrun
   Cause:  This message is for your information only.  It indicates that 
an I/O overrun error occurred.
   Action:  No action is needed.

916-409 ILANS: Control block check
   Cause:  This message is for your information only.  The ilans device 
issued a control block check.
   Action:  No action is needed.

916-410 ILANS: Reserved packet type received
   Cause:  This message is for your information only.  It indicates that 
the system received a packet from the ilans device that is a type not 
currently defined, but is reserved for future use.
   Action:  No action is needed.

916-412 ILANS: Unexpected "senseceti" unit #, port #
   Cause:  This message is for your information only.  It indicates that 
an unexpected senseceti interrupt was received on a port.
    Action:  No action is needed.

916-413 ILANS: Sense fatal error unit #, port #
   Cause:  This message is for your information only.  It indicates that 
the sense operation failed in an unrecoverable way.
   Action:  No action is needed.

916-414 ILANS: Bad status from SENSECETI csw=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-415 ILANS: Unexpected "senseceti" unit #, port #
   Cause:  This message is for your information only.  It indicates that 
an unexpected senseceti interrupt was received on a port.
   Action:  No action is needed.

916-416 ILANS: "senseid" fatal error unit #, port #
   Cause:  This message is for your information only.  It indicates that 
the senseid operation failed in an unrecoverable way.
   Action:  No action is needed.

916-417 ILANS: Bad status from SENSECETI csw=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-418 ILANS: Unexpected completion unit #, port #
   Cause:  This message is for your information only.  It indicates that 
an unexpected completion interrupt was received on a port.
   Action:  No action is needed.

916-419 ILANS: Error max exceeded : #
   Cause:  This message is for your information only.  The ilans driver 
exceeded its maximum limit of errors.
   Action:  No action is needed.

916-420 ILANS: sync interrupt fatal error unit #, port#
   Cause:  This message is for your information only.  It indicates that 
the sync interrupt failed in an unrecoverable way.
   Action:  No action is needed.

916-421 ILANS: Bad status csw=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-422 ILANS: Unexpected channel status unit #, port #
   Cause:  This message is for your information only.  It indicates that 
an unexpected channel status interrupt was received on a
   port.
   Action:  No action is needed.

916-423 ILANS: Error max exceeded : #
   Cause:  This message is for your information only.  The ilans driver 
exceeded its maximum limit of errors.
   Action:  No action is needed.

916-424 ILANS: Illegal unit status unit #, port #
   Cause:  This message is for your information only.  The ilans device 
returned an illegal unit status.
   Action:  No action is needed.

916-425 ILANS: Error max exceeded : #
   Cause:  This message is for your information only.  The ilans driver 
exceeded its maximum limit of errors.
   Action:  No action is needed.

916-426 ILANS: Unexpected attention received on port #
   Cause:  This message is for your information only.  It indicates that 
an unexpected attention interrupt was received on a port.
   Action:  No action is needed.

916-427 ILANS: Error max exceeded : #
   Cause:  This message is for your information only.  The ilans driver 
exceeded its maximum limit of errors.
   Action:  No action is needed.

916-428 ILANS: "async" interrupt UNIT EXCEPTION unit #, port #
   Cause:  The ilans device received a UNIT EXCEPTION interrupt.
   Action:  Correct problems with the device (if it persists). 
Otherwise, follow your local procedures for reporting software or 
hardware problems.

916-429 ILANS: "async" interrupt UNIT CHECK unit #, port #
   Cause:  The ilans device received a UNIT CHECK interrupt.
   Action:  Correct problems with the device (if it persists). 
Otherwise, follow your local procedures for reporting software or 
hardware problems.

916-430 ILANS bad status from "drar" unit #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-431 ILANS Unit# DLM Status Received
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-432 ILANS unknown MAC "prim_type" unit #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-433 ILANS bad status from "dasr" unit #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-434 ILANS Unit# is ready
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-435 ILANS got invalid "r_sap_id" #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-436 ILANS unknown LLC "prim_type" unit #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-437 ILANS bad status from "snpr" unit #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-438 ILANS Unit Chk detected at Level 2
   Cause:  The ilans device received a Unit Chk (check) due to a problem 
detected at the Level 2 layer.
   Action:  Correct the problem with the ilans device.

916-440 ILANS: "ceti" error message: message
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-441 ILANS: Disabling adaptor
   Cause:  This message is for your information only.  The ilans adaptor 
is being disabled.
   Action:  No action is needed.

916-442 ILANS unknown message type
   Cause:  This message is for your information only.  The ilans device 
received a message of an unknown type.
   Action:  No action is needed.

916-443 ILANS is already offline
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-444 ILANS going offline because of ioctl
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-448 ILANS: "ceti init" timed out after # tries
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-451 ILANS: Failed "sio" for "senseceti" dev #
   Cause:  The sio (start channel I/O) routine for the sense operation, 
failed.
   Action:  Correct problems with the ilans hardware.  Otherwise, follow 
your local procedures for reporting software or hardware problems.

916-452 ILANS: Failed "sio" for "senseid" dev #
   Cause:  The sio (start channel I/O) routine number for the senseid, 
failed.
   Action:  Correct problems with the ilans hardware.  Otherwise, follow 
your local procedures for reporting software or hardware problems.

916-453 ILANS: Failed interrupt "sio" dev #
   Cause:  An I/O from the ilans device could not succeed because the 
sio (start channel I/O) routine on the device was interrupted.
    Action:  Correct problems with the ilans hardware.  Otherwise, 
follow your local procedures for reporting software or hardware problems.

916-454 ILANS: Failed control "sio" dev #
   Cause:  This message is for your informational only.  The ilans 
device issued an equipment check.
   Action:  No action is needed.

916-455 ILANS: Failed input data "sio" dev #
   Cause:  Data from the ilans device could not be read because the sio 
(start channel I/O) routine on the device, failed.
   Action:  Correct problems with the ilans hardware.  Otherwise, follow 
your local procedures for reporting software or hardware problems.

916-456 ILANS: Failed output data "sio" dev #
   Cause:  Data to the ilans device could not be written because the sio 
(start channel I/O) routine on the device, failed.
   Action:  Correct problems with the ilans hardware.  Otherwise, follow 
your local procedures for reporting software or hardware problems.

916-458 ilansobr: Unknown type=#
   Cause:  This message is for your information only.  It indicates that 
an unexpected senseid interrupt was received on a port.
   Action:  No action is needed.

916-459 ilansobr: Store subchannel information failed, result=#
   Cause:  This message is for your information only.  It indicates that 
an attempt to write an outboard recorder (obr) into the Error Recording 
Editing Program (EREP) log, failed.
    Action:  No action is needed.

916-460 ilansmdr: Store subchannel information failed, result=#
   Cause:  This message is for your information only.  It indicates that 
an attempt to write an Miscellaneous Data Record (MDR) into the Error 
Recording Editing Program (EREP) log, failed.
   Action:  No action is needed.

916-481 Unexpected interrupt from device #(#)
   Cause:  An interrupt was detected from a device that did not have an 
installed interrupt handler.
   Action:  Correct the device and the AIX configurations (as necessary) 
so that they match.

916-521 IUCV query failed cc=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-522 IUCV query said it needs more than 40  bytes (#)
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-523 IUCV declare buffer failed cc=#, rc=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-524 IUCVinit OK, maxpath: #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-525 Attempt to reset "iucv" handler for conn #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-526 IUCV interrupt !OK
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-561 lcs: Can't allocate controller buffer
   Cause:  The lcs device cannot allocate a controller buffer because 
the memory allocation failed.
   Action:  Make additional memory available to the system.

916-601 ldsfwrite: Unexpected return code #
   Cause:  The return code from the indicated write was not expected.
   Action:  Correct the Virtual Machine (VM) configuration of the ldsf 
handler.

916-602 ldsfaccept: Unexpected return code #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-603 ldsfhandler: Interrupt for unknown device dev=#, flag=#, reason=#
   Cause:  This message is for your information only.  The ldsf handler 
received an interrupt from an unknown device.
   Action:  No action is needed.

916-641 lpintr: Interrupt devno=#, csw=# #, i=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-643 lpclose: Close command on "lp" # failed
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-644 lpclose: Command: message
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-645 CP response was: message
   Cause:  This message is for your information only.  It gives 
information about the operation of the printer.
   Action:  No action is needed.

916-646 lpclose: "cp" command on "lp" # failed
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-647 lpclose: Command: TAG DEV #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-648 CP response was: message
   Cause:  This message is for your information only.  It gives 
information about the operation of the printer.
   Action:  No action is needed.

916-649 lpclose: "cp" command on "lp" # failed
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-650 lpclose: Command: TAG DEV #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-651 CP response was: message
   Cause:  This message is for your information only.  It gives
   information about the operation of the printer.
   Action:  No action is needed.

916-681 Panic: startup: system tables
    Cause:  The system encountered an error when it tried to allocate 
space and also initialize the dynamic system tables.  Unreasonable 
values for table sizes in the /etc/master file were probably used when 
the system was last configured.  There may be an error in system 
configuration.
    Action:  Install the previous version of the AIX Operating System 
kernel and try to run it again.  Before trying the new system again, 
check the master and system files and correct any errors. See the 
sections on system configuration in the Managing the AIX Operating 
System, config in the AIX Operating System Command Reference, and master 
in the AIX Operating System Technical Reference for information on the 
location and format of these files.
    Verify the value of the fundamental parameters.  If you have changed 
the values of the secondary or tertiary parameters, verify those values. 
  You may have specified too large a value for one of these parameters. 
  If the problem persists, save the coredump, kernel load module, 
console logs, the /etc/master and /etc/system files, and any other 
pertinent information about what was happening before the error occurred 
and follow your local procedures for reporting software problems.

916-683 Panic: no memory
   Cause:  The system start up failed during the kernel
   initialization process, because there was insufficient Virtual 
Machine (VM) memory to run the kernel.
   Action:  Increase the size of the VM memory, and then re-IPL 
(initiate program load) the system.

916-686 Panic: setrq
   Cause:  The system tried to add a process to the run queue (when it 
was already on the run queue).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-687 Panic: remrq
   Cause:  The system tried to remove a process from the run queue (when 
it was not on the run queue).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-690 Panic: swtch: empty q
   Cause:  The system tried to run some process, but there were no 
processes able to run on the run queue.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-695 Panic: initnewproc: not pid 1
   Cause:  The system process (set up to run the init process) does not 
have a process identifier (pid) of 1.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-697 Panic: icodecopyout: vsalloc: no free vsegments
   Cause:  The icode (initialization code) could not be copied out 
because there were no virtual segment (vseg) tables that could be 
allocated (due to the lack of free vsegments).
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-698 Panic: icodecopyout: bad "sub-text" vsgrow
   Cause:  The virtual segment (vseg) grow for the icode (initialization 
code) XA sub-text, failed.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-699 Panic: icodecopyout: bad "text" vsgrow
   Cause:  The virtual segment (vseg) grow for the icode (initialization 
code) text, failed.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-715 dumpcore: Zero based segment? (type #)
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-716 Device # out of range -- ignored
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-770 Config ERROR -- Mag tape # at # -- INVALID DEV TYPE message
   Cause:  The device attached at the configured tape address is not a 
valid tape device type.
   Action:  Correct the AIX configuration or the Virtual Machine (VM) 
configuration.  Otherwise, follow your local procedures for reporting 
software or hardware problems.

916-772 mtopen: Tape dev=#, not configured
   Cause:  A program attempted to open a tape device that is not configured.
   Action:  Run the program again using a valid tape device.

916-773 mtopen: Tape addr=#, device not available
   Cause:  An operation using the tape drive failed because the device 
at the indicated address was not available.
   Action:  Make the device available and try the operation again.

916-774
916-777 mtopen: Tape addr=#, wrong device type
   Cause:  The device found at the address of the configured tape drive 
is not the correct device type.
   Action:  The Virtual Machine (VM) configuration should be altered to 
match the AIX configuration, or the AIX configuration should be changed 
to match the VM configuration.

916-782 mtopen: Tape addr=#, not ready
   Cause:  An operation using the tape drive failed because the device 
at the indicated address was not ready.
   Action:  Make the device ready and then try the operation again.

916-783 mtclose: I/O error dev=#
   Cause:  An I/O error occurred on the tape device indicated.
   Action:  Correct the problems with the drive and retry the operation.

916-784 mt.c: "ERP" recovered dev=#, r#=#, f#=#, b#=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-785 mt.c: message, dev=#, cmd=#, f#=#, b#=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-788 mtioctl: Request # not supported
   Cause:  This message is for your information only.  Some operation 
performed an ioctl system call on the magnetic tape device that is not 
supported.
   Action:  No action is needed.

916-790 MDR record for device: devtype=type, ioaddr=#
   Cause:  This message is for your information only
   Action:  No action is needed.

916-802 More vctc's defined (#) than configured (#)
   Cause:  This message is for your information only.  The number of 
virtual channel-to-channels (vctc) supported is limited to the number 
configured.
   Action:  No action is needed.

916-803 vctc_startio: cc=2
   Cause:  The indicated virtual channel-to-channel (vctc) device is not 
operational.
   Action:  The most action to be attempted, is to correct some problem 
with the device in the Virtual Machine (VM) system configuration.

916-804 vctc_startio for VCTC #: cc=3
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-805 vctc_ostart: Bad "sio" return code, rc=#
   Cause:  The indicated virtual channel-to-channel (vctc) device is not 
operational.
   Action:  The most action to be attempted, is to correct some problem 
with the device in the Virtual Machine (VM) system configuration.

916-806 vctc_read_start: Try again on a read
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-807 vctc_int: Unexpected state on non-zero deferred cc code
   Cause:  This message is for your information only.  It indicates that 
a non-zero deferred condition code was received on a virtual 
channel-to-channel (vctc) device.
   Action:  No action is needed.

916-809 vctc_int: Device # not operating (cc=3)
   Cause:  The indicated virtual channel-to-channel (vctc) device is not 
operational.
   Action:  The standard correction is to reconfigure some device in the 
Virtual Machine (VM) system.

916-810 vctc_int: Invalid cc -- csw flags=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-811 vctc_int: Non-attn interrupt: #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-812 vctc_int: ICC unit # while READING
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-813 vctc_int: ICC unit # while WRITING
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-881 Panic: trap
   Cause:  The kernel failed because it received an unexpected trap 
while executing in kernel mode.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-886 Kernel message fault at #
   Cause:  This message is for your information only (it always precedes 
a system panic message).
   Action:  No action is needed.

916-887 Kernel program check code is #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-889 Unexpected external interrupt #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-890 trap.c: Unknown machine check type, ic=# #
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-894 trap.c: Unknown channel report word, crw=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-921 Panic: alloc_vector_save: out of memory for status save area
   Cause:  The vector save area cannot be allocated because of 
insufficient memory.
   Action:  Increase the amount of available memory.

916-922 Panic: alloc_vector_save: for vector register save area
   Cause:  The vector save area cannot be allocated because of 
insufficient memory.
   Action:  Increase the amount of available memory.

916-933 Vector facility: Section size=# (dec) partial sum size=#
   Cause:  This message is for your information only.
   Action:  No action is needed.

916-964 Panic: getpages: page in hash
   Cause:  A page that was part of the copy on reference debugging 
feature was found in the hash table.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-967 getpages: Bad dbd
   Cause:  This message is for your information only.  It indicates that 
the getpages subroutine was called for a virtual segment (vseg) table 
whose dbd table type is not known.
   Action:  No action is needed.

916-968 Panic: swap: I can't do more than 1 page at a time
   Cause:  A limitation in swap code condition exists.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

916-970 getpages: Bad "dbd" type #
   Cause:  This message is for your information only.  It indicates that 
the getpages subroutine was called for a virtual segment (vseg) table 
whose dbd table type is not known.
   Action:  No action is needed.

917-024 Panic: vinifod: paging from small block file
   Cause:  An executable load module was run and was stored completely 
in the inode.  Running such a module is usually impossible because a 
well-formed load module is too large to be stored in such a file.
   Action:  Recreate the load module (it is malformed).

917-030 LOW ON SWAP SPACE!  Can't find any process to kill!
   Cause:  The system is attempting to terminate processes to obtain 
space, but cannot find any processes that are appropriate to stop.
   Action:  Increase the amount of swap space available to the system.

917-031
917-032 Process # killed: no swap space
   Cause:  A Process whose Process Identifier (PID) is identified was 
terminated by the system because there was insufficient swap space for 
it to run.
   Action:  Increase the amount of swap space available to the system.

917-033 swkill: Still need # pages
   Cause:  The system is attempting to terminate processes to obtain 
space, and requires the indicated number of pages.
   Action:  Increase the amount of swap space available to the system.

917-041 Panic: pagein: pvseg null after successful "stackgrow"
   Cause:  A pagein failed because the process virtual segment (pvseg) 
point was null after the stack had been successfully grown.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-057 Process # killed: no swap space
   Cause:  A Process whose Process Identifier (PID) is identified was 
terminated by the system because there was insufficient swap space for 
it to run.
   Action:  Increase the amount of swap space available to the system.

917-058 pagein: # validated for pid # while waiting for "mem"
   Cause:  This message is for your information only.
   Action:  No action is needed.

917-059 Process # killed: no swap space
   Cause:  A Process whose Process Identifier (PID) is identified was 
terminated by the system because there was insufficient swap space for 
it to run.
   Action:  Increase the amount of swap space available to the system.

917-062 Page read error, dev #, error #
   Cause:  The paging system detected a read error while trying to move 
a page from the paging specified device to main memory.
    Action:  Run hardware diagnostics on the specified device and follow 
your local procedures for reporting hardware problems.

917-063
917-064 Process # killed: no swap space
   Cause:  A Process whose Process Identifier (PID) is identified was 
terminated by the system because there was insufficient swap space for 
it to run.
   Action:  Increase the amount of swap space available to the system.

917-133 Panic: vsgrow: too many inodes
   Cause:  An attempt was made to grow a virtual segment (vseg) 
associated with an inode but the limit on the number of inodes was exceeded.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-134 Panic: vsgrow: page split between inodes
   Cause:  An attempt was made to grow a virtual segment (vseg) 
associated with an inode but the page was shared between two inodes.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-138 Panic: vscopy: "swpinc" overflow
   Cause:  A virtual segment (vseg) copy failed because the swpinc call 
failed.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-139 Panic: vsunlock
   Cause:  An attempt was made to unlock a virtual segment (vseg) that 
was not locked.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-140 Panic: pvsalloc: no free "procvsegs"
   Cause:  An attempt to allocate a procvseg structure failed because 
there were no free structures available.
   Action:  Increase the number of procvseg structures configured in the 
system.

917-141 Panic: vsegswapin: can't get vseg page table pointers
   Cause:  An attempt to swap in a virtual segment (vseg) failed because 
space for page table pointers could not be allocated (due to 
insufficient available memory).
   Action:  Increase the amount of available memory.

917-142 Panic: vsegswapout: can't get "dbd" space to swap vseg
   Cause:  An attempt to swap out a virtual segment (vseg) failed 
because the dbd table space could not be allocated (due to insufficient 
available memory).
   Action:  Increase the amount of available memory.

917-165 Panic: vswapout: no swap space
   Cause:  An attempt to swap out a virtual segment (vseg) failed 
because of insufficient swap space.
   Action:  Configure the AIX Operating System so that additional swap 
space is available.

917-241 Panic: real_buf_addr: bad "pvseg"
   Cause:  The real buffer address could not be determined because the 
process virtual segment (pvseg) is bad.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-242 Panic: real_buf_addr: bad "ptep"
   Cause:  The real buffer address could not be determined because the 
page table entry pointer (ptep) is bad.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-243 Panic: physiolock
   Cause:  The lock of the physio (physical I/O) channel failed.
   Action:  Record all information and follow your local procedures for 
reporting software problems.

917-285 sbreak: pid #: set new break to #
   Cause:  This message is for your information only.  It indicates that 
process identifier (pid) set is a new break value.
   Action:  No action is needed.

917-286 sbreak: pv_vaddr, v_rsvdsize, v_rosize, #, #, #
   Cause:  This message is for your information only.
   Action:  No action is needed.
0
Louis
2/13/2006 6:57:31 PM
comp.sys.ibm.ps2.hardware 10363 articles. 0 followers. Post Follow

4 Replies
905 Views

Similar Articles

[PageSpeed] 47

Hey Major Malfunction......

Just printed it all out. Thirty-five (count 'em) pages (legal size) of
great info.........

Thank you......

M/Sgt CT

0
Tim
2/13/2006 8:52:17 PM
Louis Ohland wrote:
>   AIX Operating System Messages Reference
>   Chapter 3.  Displayed Messages (Numeric)

Note that this manual extract is from the AIX/370 book, so many of
these messages will not apply to AIX 1.3 for the PS/2, like any
references to "ILANS" or "CP".  However, we work with what we have...

Rick Ekblaw

0
RickE
2/14/2006 4:41:16 AM
Rick, is the list of 900 series that you sendt me THE only 900 errors 
that apply to AIX 1.3? I wandted to use it and cut n paste to it, but it 
was ungainly (read too damn big to edit all at once).

What I can do is use the 900 list you sendt, and then delete the entries 
from the list I posted.

Rick, what are the other 000-800 errors? Are they AIX 1.3 specific, or 
do they apply to 370?

RickE wrote:
> Louis Ohland wrote:
>>   AIX Operating System Messages Reference
>>   Chapter 3.  Displayed Messages (Numeric)
> 
> Note that this manual extract is from the AIX/370 book, so many of
> these messages will not apply to AIX 1.3 for the PS/2, like any
> references to "ILANS" or "CP".  However, we work with what we have...
> 
> Rick Ekblaw
> 
0
Louis
2/14/2006 1:44:39 PM
Louis Ohland wrote:
> Rick, is the list of 900 series that you sendt me THE only 900 errors
> that apply to AIX 1.3? I wandted to use it and cut n paste to it, but it
> was ungainly (read too damn big to edit all at once).
>
> What I can do is use the 900 list you sendt, and then delete the entries
> from the list I posted.
>
> Rick, what are the other 000-800 errors? Are they AIX 1.3 specific, or
> do they apply to 370?

Louis, the 900 series text file I sent you is a formatted extract from
the AIX 1.3 SCSI boot diskettes, so every one of those messages is
"guaranteed" to be applicable to AIX 1.3.  Most of the 0xx and 1xx
messages in the book are from the shell or one of the standard
utilities, so they would be equally applicable to either AIX/370 or AIX
for the PS/2 (with perhaps a few exceptions, I didn't examine each
message in depth).

Rick Ekblaw

0
RickE
2/15/2006 1:46:39 AM
Reply:

Similar Artilces:

Correlated AIX 1.2.1 and 1.3 900 series error messages
� Copyright IBM Corp. 1985, 1991 AIX Operating System Messages Reference Chapter 3. Displayed Messages (Numeric) This is a list of the internal 1.3 error messages that Rick Ekblaw extracted. Where available, I have included the 1.2.1 description and actions. It gets no better than this... An error number NOT followed by Cause-Description is new for 1.3.0, an error message followed by Cause-Description is carried forward from 1.2.1 (except one)>. 900-000 free: NFS gfs %d 900-001 free called with NFS gfs 900-003 %s on %s 900-004 %s, %s on %s 900-008 Bad file system allocation detected 900-009 Bad file system free detected 900-037 - if_ena: autoconfigure could not allocate kernal memory 900-038 - if_ena: board configured but ROM does not check out 900-039 - no if_ena adaptors present 900-041 Panic: brreada: negative block number Cause: A remote read (with read ahead) was attempted with a block number that was less than zero (0). Action: Record all information and follow your local procedures for reporting software problems. 900-045 Panic: brelse: netwantsbuf Cause: A synchronization error caused the system to lose track of which network wanted the buffer. Action: Record all information and follow your local procedures for reporting software problems. 900-062 - if_ena: unit %d reset via 690 transmit watchdog. 900-142 commitdir: inconsistent 900-200 symblnk: No "kmem" Cause: The symblnk reso...

how can i write this statement labels=[1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;1;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;2;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;3;]; in compress fo
How to write it in compact form to avoid repetition "shah " <shahkhn3@gmail.com> wrote in message <lodugh$8hr$1@newscl01ah.mathworks.com>... > How to write it in compact form to avoid repetition You'll find in this thread different solutions for similar question http://www.mathworks.fr/matlabcentral/newsreader/view_thread/335814 Bruno ...

[1 1 1 1 1 ;2 2 2 2 2 ;3 3 3 3 3 3;....;n n n n n]
Hi, Anybody knows how to create this matrix but without using any loops? a=[1 1 1 1 1 ;2 2 2 2 2 ;3 3 3 3 3 ;.......;n n n n n ] Thank you. Hana. Hana wrote: > Hi, > Anybody knows how to create this matrix but without using any loops? > a=[1 1 1 1 1 ;2 2 2 2 2 ;3 3 3 3 3 ;.......;n n n n n ] HELP REPMAT - Randy Hana wrote: > > > Hi, > Anybody knows how to create this matrix but without using any > loops? > a=[1 1 1 1 1 ;2 2 2 2 2 ;3 3 3 3 3 ;.......;n n n n n ] > > Thank you. > Hana. Hope this isn't homework. >> repmat([1:n]'...

how to "(1-3*x^2)/(1-3*x+x^2+2*x^3) => 1/(1-2*x) + x/(1-x-x^2)"?
hi normal(1/(1-2*x) + x/ (1-x-x^2),expanded); 1/(1-2*x) + x/(1-x-x^2) => (1-3*x^2)/(1-3*x+x^2+2*x^3) how to do the reverse? dillogimp@gmail.com writes: > normal(1/(1-2*x) + x/ (1-x-x^2),expanded); > 1/(1-2*x) + x/(1-x-x^2) => (1-3*x^2)/(1-3*x+x^2+2*x^3) > how to do the reverse? convert(%,parfrac,x); -- Joe Riel ...

1 - 1, 1 -1, 1-1, 1
Hi, I have a question regarding lexical analysis. I recently came across a bug in our lexical analyser in phc (www.phpcompiler.org), that I am unsure how to solve. This is the problem: our current definition for integer constant looks something like INT ([1-9][0-9]*)|0 In particular, note that it does not allow for an (optional) "+" or "-" at the start of the integer. This means that the strings "1 - 1", "1 -1" and "1-1" all generate the same sequence of three tokens INT(1), OP(-), INT(1), for which the syntax analyser generates the subtree BIN_OP(-, 1, 1). For the string "1 - -1", the lexer (unsurprisingly) generates INT(1), OP(-), OP(-), INT(1). The syntax analyser recognises this as BIN_OP(1, UNARY_OP(-, 1)). In other words, the second "-" is treated as a unary operator, rather than as part of the number. This works fine, with the sole exception of the number "-2147483648". The problem is, of course, overflow: -2147483648 is a valid negative number (assuming 32-bit numbers), but the integer 2147483648 is _not_ a valid positive number. Thus, the above method of dealing with "-" as a unary operator breaks down. The solution is to interpret the "-" as part of the number, and generate INT(-2147483648), rather than OP(-), INT(...). However, changing the definition of INT to INT [+-]?([1-9][0-9]*)|0 causes "1-1" to be recognised as INT(1), INT(-1), which is...

1.1.1.1 ?
hi my firewall logs dropped packets from an internal IP address trying to contact 1.1.1.1 through port 9999. Any ideas whether 1.1.1.1 is valid IP? and what is port 9999?? thanks mike wrote: > hi > > my firewall logs dropped packets from an internal IP address trying to > contact 1.1.1.1 through port 9999. Any ideas whether 1.1.1.1 is valid > IP? and what is port 9999?? > thanks These trojans *BlitzNet*, *Backdoor.Oracle*, *Backdoor.Spadeace* uses port 9999 -- S.S. "StarScripter" <Star@privacy.net> wrote in message news:<bv8ejj$p54t3$1@ID-185702.new...

#1 #n+1 #2n+1 #2 #n+2 #2n+2 #3 #n+3 #2n+3 #n #2n #3n #1 #2 #3 #n #n+1 #n+2 #n+3 #2n #2n+1 100 Gbps aggregate stream of 64/66b words virtual lane markers virtual lane 1 virtual lane 2 virtual lan
#1 #n+1 #2n+1 #2 #n+2 #2n+2 #3 #n+3 #2n+3 #n #2n #3n #1 #2 #3 #n #n+1 #n+2 #n+3 #2n #2n+1 100 Gbps aggregate stream of 64/66b words virtual lane markers virtual lane 1 virtual lane 2 virtual lane 3 virtual lane n Simple 66-bit word level round robin distribution Transmit PM Transmit PM Receive PM Receive PM Transmit PC Receive PC 1 0.0 1.0 0.1 0.2 0.3 1.2 1.2 1.1 0.0 1.0 0.1 1.1 2.0 3.0 4.0 6.0 7.0 9.0 10.0 11.0 12.0 13.0 14.0 15.0 17.0 18.0 19.0 2.0 3.0 4.0 5.0 6.0 7.0 8.0 9.0 10.0 11.0 12.0 13.0 14.0 15.0 16.0 17.0 1...

1.1, 1.2, 1.3 are all goners now
It seems, well, it doesn't seem but it is, well, it seems that the subject version of Workbenches won't be any more these, versions of Workbench, but versions of Amix. The Amiga's go for the Network. :-)) Have you seen that CDTV on amiga.jorg? That kind od schalametry for games, like some high tech heavily classic games will be played... Heyyyaaa!!! p.s. some piece of equipment, eh.. CD, floppy, installable HD, all, joysticks, joypads for CDTV, playing CDs and playing games. It's like you'll need a high class massive wood shelf for this, the CDs and for the - :( r...

plot 1, -1, 1, -1, -1
Hi, How to plot those numbers in a rectangle style? thanks x = linspace(-4*pi,4*pi,1000); y = sin(x); plot(x,sign(y)), axis([-12 12 -2 2]) PZ <patrick.zou@gmail.com> wrote in message <d64c545f-f2ac-4f87-af89-051bda896707@x6g2000vbg.googlegroups.com>... > Hi, > > How to plot those numbers in a rectangle style? > > thanks help stairs stairs([-1 1 -1 1 -1 1]) hth Jos ...

ERROR IN EXPRESSION; -1 - (-1) not 1
The expression isn't a = 1 - (1-), but: a = -1 - (1) der <der@noemail.com> scribbled the following: > The expression isn't a = 1 - (1-), but: a = -1 - (1) Ah, that's different, then. Then the answer is: The result will be -2. You have *no* guarantees about which of -1 or (1) is evaluated first, but as they don't have side effects, you don't have to care. -- /-- Joona Palaste (palaste@cc.helsinki.fi) ---------------------------\ | Kingpriest of "The Flying Lemon Tree" G++ FR FW+ M- #108 D+ ADA N+++| | http://www.helsinki.fi/~palaste W++ B OP+ | \----------------------------------------- Finland rules! ------------/ "To doo bee doo bee doo." - Frank Sinatra ...

ActivePython 3.1.1.2 vs Python 3.1.1 for OSX?
I am just curious which I should use. I am going to start learning Python soon. Are they comparable and I just do a "eenie meenie minie moe"? Bob On 1 Oct, 00:51, Robert Hicks <sigz...@gmail.com> wrote: > I am just curious which I should use. I am going to start learning > Python soon. Are they comparable and I just do a "eenie meenie minie > moe"? > > Bob First off, a great choice of language to begin trying! Is it your first language (I'm guessing not), or do you come from another 'background'. Basically, Active is a possible 'supe...

Changing (1,2,3,4,5...) to (1,1,2,2,3,3,4,4,5,5...)
Hi All, I have a column vector of numbers that I would like to extrapolate by "doubling up": e.g. turn 2 4 6 8 into: 2 2 4 4 6 6 8 8 any ideas on an easy vectorised way to do this? TIA, Rob v=repmat([2; 4; 6; 8].',2,1); v=v(:) "Robert Barrie" <askme@ifuwant.com> wrote in message <hlt7kp$rut$1@fred.mathworks.com>... > Hi All, > > I have a column vector of numbers that I would like to extrapolate by "doubling up": > > e.g. turn > 2 > 4 > 6 > 8 > > into: > 2 > 2 > 4 > 4 > 6 > 6 > 8 >...

Will Apache JServ 1.1.2-2 support JRE 1.3.1 ?
Hi Has anybody tried Apache 2.0.47 - Apache JServ 1.1.2-2 - JRE 1.3.1 combination?Will it work? Would like to know if there is any compatability problem before i begin to istall the above combination.pl reply Thanks csb ...

Will Apache JServ 1.1.2-2 support JRE 1.3.1 ?
Hi Has anybody tried Apache 2.0.47 - Apache JServ 1.1.2-2 - JRE 1.3.1 combination?Will it work? Would like to know if there is any compatability problem before i begin to istall the above combination.pl reply Thanks csb ...

Newbie question; why (cons (list 1 2) (list 3 4)) is ((1 2) 3 4) and not ((1 2) (3 4))
Hi, I just started to learn LISP, and stumbled in SICP upon (cons (list 1 2) (list 3 4)) is evaluated to ((1 2) 3 4) I do not understand why this is not: ((1 2) (3 4)) because (cdr (cons (list 1 2) (list 3 4))) is (3 4) and (car (cons (list 1 2) (list 3 4))) is (1 2) Is there a logical explanation? Thank you for your patience. -- Greg Out of order, gregor <gregor@ediwo.com> writes: > Is there a logical explanation? Yes. > I just started to learn LISP, and stumbled in SICP...

Help construct a tree 1 -> 1.1 -> 1.2 -> 2 -> 2.1 -> 2.1.1 etc HELP !!!!!!!
Folks I need help. I have a view or(Text file) as follows: '1 2.1 1.1.1 1.1.1.1 2.2.1 1.3 2 Dim Parent() As String Dim Level1() As String Dim Level2() As String Dim Level3() As String etc .. How can I construct a tree. parent, children, grand children etc... and also figure out # of children # of grand children etc Thanks "Mos" <lndebug@gmail.com> wrote in message news:875cd1df-7605-45ab-9f7b-f1edec25d47b@r34g2000vbi.googlegroups.com... > Folks I need help. I have a view or(Text file) as follows: > > '1 > 2.1 > 1.1.1 > 1....

Help construct a tree 1 -> 1.1 -> 1.2 -> 2 -> 2.1 -> 2.1.1 etc HELP !!!!!!!
Folks I need help. I have a view or(Text file) as follows: '1 2.1 1.1.1 1.1.1.1 2.2.1 1.3 2 Dim Parent() As String Dim Level1() As String Dim Level2() As String Dim Level3() As String etc .. How can I construct a tree. parent, children, grand children etc... and also figure out # of children # of grand children etc Thanks "Mos" <lndebug@gmail.com> wrote in message news:875cd1df-7605-45ab-9f7b-f1edec25d47b@r34g2000vbi.googlegroups.com... > Folks I need help. I have a view or(Text file) as follows: > > '1 > 2.1 > 1.1.1 > 1....

Help construct a tree 1 -> 1.1 -> 1.2 -> 2 -> 2.1 -> 2.1.1 etc HELP !!!!!!!
Borland Guru's I need help I have a text file as follows: 1 2 1.1 1.1.1 3.3 2.3 etc I cannot use a control active x tree I need to read this file and 1 is a parent 1.1 is a child of parent 1 and 2 is a parent 2.3 is a child of parent 2 and construct in search a way using arrays or probably a recursive function No xml parsing just read a file. Does any body have a function "Mos" <lndebug@gmail.com> wrote in message news:c1aaeb20-3c1f-408d-9986-bb8d28a87509@s31g2000vbp.googlegroups.com... > I have a text file as follows: > 1 > 2 > 1.1 >...

Re: [tao-bugs] Increase in IFR Service footprint
Hello again, Something just occurred to me. Version 1.3.1 may have pre-dated some other changes to the IFR that would certainly explain the increase in runtime footprint you are referring to. Back in December, I changed the query dispatch mechanism in the IFR from servant locator to default servant, to optimize the performance. This new mechanism creates 30-odd servants and a POA for each at IFR startup time. This was done last December. Also, regarding the possible memory leaks - these servants and POAs have their lifetimes tied to the IFR, so any Purify checks must shut down the IFR grace...

[ANN] Pylint 1.3.1 / Astroid 1.2.1 released
Hello! I'm happy to announce that Pylint 1.3.1 and Astroid 1.2.1 were released. These releases include some bugfixes with the new string formatting checker and a couple of crash fixes. Please note that Pylint 1.3.X is the last version of Pylint which supports Python 2.5 and 2.6. Enjoy! ...

[ANN] Pylint 1.3.1 / Astroid 1.2.1 released
Hello! I'm happy to announce that Pylint 1.3.1 and Astroid 1.2.1 were released. These releases include some bugfixes with the new string formatting checker and a couple of crash fixes. Please note that Pylint 1.3.X is the last version of Pylint which supports Python 2.5 and 2.6. Enjoy! ...

MYSQL V4-1-1 and PHP 1.2 and CSWS 1.3
Does someone have documentation on how to properly configure MYSQL and PHP on OpenVMS 7.3-1. My test script fails on the line with mysql_connect(). Mysql is running and works using the parameters in the connect statement at the command line and I can connect and look at the db. I have not been able to locate the doc that explains how all of the configuration files must be configured for proper operations for the 4.1.1 version -- it is quite different from the previous version... Until the STREAM_LF issue is resolved in CSWS 2.0, I cannot install it. Any help is appreciated. Michael...

3.1.1 ok but 3.1.2-B3 error on same SiS965L board (pci: i/o base too low: 0)
The 3.1.2-B3 CD will not boot: Panic in pci: I/O base too low: 0 ... No CD found The 3.1.1 installed and then everything worked, but had 2 warnings at boot: pci_intel_init: unknown PCI-controller vendor 1039 (silicon Intergated Systems (SiS)), device 0760 unsupported ISA bridge 1039/0965 for bus 0 All, On 13 Apr 2006 22:17:59 -0700, Costel CV <cv.minix@gmail.com> wrote: > The 3.1.2-B3 CD will not boot: > Panic in pci: I/O base too low: 0 > ... > No CD found There is a new experimental version (a tentative 3.1.2) on the experimental page. Please try ...

OO 1.1 and java 1.3.1
Am attempting to install OO 1.1, but with just Java 1.3.1, and the install documentation says that without at least 1.4.1, I cannot make use of full capabilties. I infer from this that I should be able to OO crippled. However, However, OO does not like it when I point to my 131 JRE. Comments? -- Sir: David I. Smith wrote: > Am attempting to install OO 1.1, but with just Java 1.3.1, and the > install documentation says that without at least 1.4.1, I cannot make > use of full capabilties. I infer from this that I should be able to > OO crippled. However, However, OO...

Web resources about - AIX 1.3 900 series errors (actually 1.2.1, but...) - comp.sys.ibm.ps2.hardware

Ben Carson's bizarre presidential campaign's best moments
Ben Carson said he didn't see a "path forward" for his presidential campaign following Super Tuesday when he failed to win a single state. His ...

Today's Medical Mystery: Why Did All Those Abortion Clinics in Texas Close?
Today, the Supreme Court heard arguments about HB 2, a 2013 Texas law that requires (a) all abortion clinics to meet the standards of "ambulatory ...

Kanye West Conveniently Caught Using Torrents to Pirate Software
It looks like Kanye West has egg on his face, but with his recent Twitter strategy, it’s mostly likely us playing the fools. The latest Kanye ...

HBO to launch its streaming services in Brazil and Argentina by year end
Chris Ciaccia / TheStreet.com : HBO to launch its streaming services in Brazil and Argentina by year end — Move Over Netflix — HBO Is Coming ...

Adam Devine & Sarah Hyland Kiss On 'Modern Family' Set
Adam Devine and Sarah Hyland share a kiss while filming a scene for Modern Family on WEdnesday (March 2) in Los Angeles. The 32-year-old Pitch ...

UPDATE 1-North Korea fires projectiles after new UN sanctions
Hindustan Times UPDATE 1-North Korea fires projectiles after new UN sanctions Reuters (Adds details, South Korean president comments). By ...

Apple reportedly leases former Pepsi bottling plant. More room for Apple Car?
Apple seems to be in the midst of a land-grab — and I am not referring to its new campus . See also: Sorry, Tesla: The world’s fastest electric ...

U.S. military invites pre-approved experts to 'Hack the Pentagon'
By Andrea Shalal SAN FRANCISCO (Reuters) - The Pentagon on Wednesday invited outside hackers who have been vetted to test the cyber security ...

Full Episode: WN 03/02/16: Astronaut Scott Kelly Returns to Earth Taller, Lighter and Younger
Full Episode: WN 03/02/16: Astronaut Scott Kelly Returns to Earth Taller, Lighter and Younger

Google plans to kill the wallet for good with a hands-free mobile payment system
Thanks to services like Apple Pay and Samsung Pay, we're inching ever so closer to a world where won't necessarily need to always have our wallets ...

Resources last updated: 3/3/2016 6:54:22 AM