- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- memory allocation error - Tru64 Unix V5.1B
Operating System - Tru64 Unix
1748131
Members
3509
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2003 08:11 PM
тАО11-06-2003 08:11 PM
memory allocation error - Tru64 Unix V5.1B
Hi,
Received "memory allocation error" when starting up cobol in Tru64 Unix V5.1B.
The physical memory is 2GB.
sysconfig -q proc output are :-
proc:
max_proc_per_user = 1024
max_threads_per_user = 1024
per_proc_stack_size = 8388608
max_per_proc_stack_size = 33554432
per_proc_data_size = 134217728
max_per_proc_data_size = 1073741824
max_per_proc_address_space = 4294967296
per_proc_address_space = 4294967296
ulimits parms are :-
# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 131072
stack(kbytes) 8192
memory(kbytes) 2024856
coredump(blocks) unlimited
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
Which parms requires a change in the sysconfigtab to accomadate an increase in system resources to address this issue ?
Thanks.
Received "memory allocation error" when starting up cobol in Tru64 Unix V5.1B.
The physical memory is 2GB.
sysconfig -q proc output are :-
proc:
max_proc_per_user = 1024
max_threads_per_user = 1024
per_proc_stack_size = 8388608
max_per_proc_stack_size = 33554432
per_proc_data_size = 134217728
max_per_proc_data_size = 1073741824
max_per_proc_address_space = 4294967296
per_proc_address_space = 4294967296
ulimits parms are :-
# ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 131072
stack(kbytes) 8192
memory(kbytes) 2024856
coredump(blocks) unlimited
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
Which parms requires a change in the sysconfigtab to accomadate an increase in system resources to address this issue ?
Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2003 08:56 PM
тАО11-06-2003 08:56 PM
Re: memory allocation error - Tru64 Unix V5.1B
Hello,
Resource problem,
Try it:
The H and S options specify whether the hard limit or the soft limit for the given resource is set. A hard limit cannot be increased once it is set. A soft limit can be increased up to the value of the hard limit.
To list hard limit values
#ulimit -aH
Then
#ulimit -d maxvalue
#ulimit -s maxvalue
Example:
vador@root[[/]]>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 131072
stack(kbytes) 8192
memory(kbytes) 502160
coredump(blocks) 0
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>ulimit -aH
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194304
stack(kbytes) 4194304
memory(kbytes) 502160
coredump(blocks) unlimited
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>ulimit -d 4194304
vador@root[[/]]>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194304
stack(kbytes) 8192
memory(kbytes) 502160
coredump(blocks) 0
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>ulimit -s 4194304
vador@root[[/]]>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194304
stack(kbytes) 4194304
memory(kbytes) 502160
coredump(blocks) 0
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>
If is not enough, perhaps it will be necessary to increase the hard limits.
Hope it helps,
Albertino Cortes
Resource problem,
Try it:
The H and S options specify whether the hard limit or the soft limit for the given resource is set. A hard limit cannot be increased once it is set. A soft limit can be increased up to the value of the hard limit.
To list hard limit values
#ulimit -aH
Then
#ulimit -d maxvalue
#ulimit -s maxvalue
Example:
vador@root[[/]]>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 131072
stack(kbytes) 8192
memory(kbytes) 502160
coredump(blocks) 0
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>ulimit -aH
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194304
stack(kbytes) 4194304
memory(kbytes) 502160
coredump(blocks) unlimited
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>ulimit -d 4194304
vador@root[[/]]>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194304
stack(kbytes) 8192
memory(kbytes) 502160
coredump(blocks) 0
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>ulimit -s 4194304
vador@root[[/]]>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4194304
stack(kbytes) 4194304
memory(kbytes) 502160
coredump(blocks) 0
nofiles(descriptors) 4096
vmemory(kbytes) 4194304
vador@root[[/]]>
If is not enough, perhaps it will be necessary to increase the hard limits.
Hope it helps,
Albertino Cortes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2003 09:16 PM
тАО11-06-2003 09:16 PM
Re: memory allocation error - Tru64 Unix V5.1B
this question was made several times here in the forum.
The error message "memory allocation error" indicates mostly a stack/data segment limitation depending on the application used.
The error message "memory allocation error" indicates mostly a stack/data segment limitation depending on the application used.
Help() { FirstReadManual(urgently); Go_to_it;; }
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP