- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- CHANNELCNT / FILLM
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО07-01-2004 06:53 PM
тАО07-01-2004 06:53 PM
CHANNELCNT / FILLM
As I understand it, it is some kind of maximum for FILLM (or am I wrong ?).
I added a check for the usage of this parameter and found 3 nodes out of 140 that suffered from it (all processes that connect to many other nodes and I guess it is caused by network problems we had some day).
How to check this quota ?
$ write sys$output f$getsyi("CHANNELCNT")
to get the maximum allowed.
To get the highwatermark :
$ ana/sys
>set proc/id=xxxxx
>eval @CTL$GL_CHINDX
>exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 07:09 PM
тАО07-01-2004 07:09 PM
Re: CHANNELCNT / FILLM
Fillm is just the maximum number of files a process can open
sda>eval @CTL$GL_CHINDX
gives you the number at the end of
sda> sh proc/chann
total number of open channels:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 07:15 PM
тАО07-01-2004 07:15 PM
Re: CHANNELCNT / FILLM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 07:26 PM
тАО07-01-2004 07:26 PM
Re: CHANNELCNT / FILLM
CHANNELCNT dictates the size of a process table
in P1 space. This is the maximum number of channels
that your process can have assigned at any one
time.
The channel number returned from $ASSIGN is just
an index into this table. Because channels are
used for things other than just OPENs in high
level languages it doesn't always directly
relate to number of "files". Channels are used
behind-the-scenes in various system services so
it is possible to have things hang or break for
no apparent reason until you look at things like
FILLM and CHANNELCNT and what was happening at
the time.
Exactly what problem are you seeing?
Regards
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 07:37 PM
тАО07-01-2004 07:37 PM
Re: CHANNELCNT / FILLM
If I'm not mistaken (working from fading memory here), the CHANNELCNT defines the size of the table in P1 space that holds the addresses of the CCBs (channel control blocks) used by the process.
You can find that table at CTL$GL_CCBBASE (at least on VAX). The channel number is an index in this table.
Hope this helps.
Kris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 07:52 PM
тАО07-01-2004 07:52 PM
Re: CHANNELCNT / FILLM
FILLM : open files + all busy NET devices
CHANNELCNT : fillm + the exe + files behind the exe + status blank devices (???) + BG devices + DCL.EXE + mbx
Why wasn't this implemented more clearly ? E.g. mbxlm etc in authorize ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 08:04 PM
тАО07-01-2004 08:04 PM
Re: CHANNELCNT / FILLM
You wouldn't want a different limit for each file
type. What is associated with the channel is
largely irrelevant. It is the channel control
block that identifies what is channel is pointing
to. All you need is for CHANNELCNT to be "large
enough" so that the process on the system that
has many channels assigned, Pathworks is a big
user of channels as is backup, can do its job
and that FILLM is set to a "bit less" than
CHANNELCNT to allow for those behind-the-scenes
assignments.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 08:07 PM
тАО07-01-2004 08:07 PM
Re: CHANNELCNT / FILLM
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=625161
If you are not memory contrained then set it up to 4096 (adds 10 alpha (8k) memory pages to each process) and thats usually ok for most things. Can now be up to 64k channels if you want (old limit was 2047).
The explainations so far say what it is. Why is it there ? I guess its part of the VMS idea of having limits on the use of system resources by a process.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 08:12 PM
тАО07-01-2004 08:12 PM
Re: CHANNELCNT / FILLM
I do not agree. Quotas are not invented to put on the maximum value. They are used to limit things.
If I put channelcnt on 10.000 then all users can open 10.000 channels (e.g. mailboxes).
I would like to see that I can :
1) limit the number of network connections a process can open
2) limit the number of mailboxes
3) limit the number of files the process opens (not exe, not .com, not dcl)
BTW : what are NET devices that have a blank status ?
and of course, per user, not on system level.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2004 08:21 PM
тАО07-01-2004 08:21 PM
Re: CHANNELCNT / FILLM
On my desktop Alpha I have CHANNELCNT=8192 and
my UAF entry has FILLM=8000. If you set your
CHANNELCNT to 10000 and your FILLM to 1000, how
many files will you be able to open?
CHANNELCNT puts an absolute limit on the number
of channels a process can use. This structure
is NOT dynamic therefore it needs to be known
when the process is created so the space can be
allocated. The FILLM entry in the UAF can be
different for each user. Since FILLM can be
easily changed, setting a large CHANNELCNT and
changing FILLM should not present any problems.
Dave