Just to clarify:
> maxdsiz = 2063835136
> maxdsiz_64bit = 1073741824
is quite wrong! If maxdsiz_64 is less than maxdsiz, then both parameters are silently enforced to the maxdsiz_64 value. ALWAYS set maxdsiz_64 larger than maxdsiz.
As far as OutOfMemory, there are many, many causes but generally it has nothing to do with physical memory. HP-UX is a virtual memory system so available memory is a combination of RAM plus swap space. But there are several limits that are much less than virtual memory. Kernel parameter maxdsiz sets the maximum local data (heap) for a 32 bit process. Parameter maxdsiz_64 refers only to 64 bit processes. shmmax refers to the largest shared memory segment allowed. If a set of programs need a larger segment, this kernel parameter must be adjusted.
To see all the ulimit values, use ulimit -a. If this fails, your shell is badly out of date (ksh needs a patch). Note also that shared memory (32 bit programs) must be mapped in a single space and can be heavily fragmented with InterProcess Comunication (IPC) objects like semaphores and other shared memory segments.
You may have a massively oversized kernel (normal is 8 to 15 megs) due to an oversized parameter, or your buffer cache is far too large (should be 600to 1200 megs).
Bill Hassell, sysadmin
