- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: ACMS - DIBOL Program throws 33 in Development
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
тАО11-04-2009 07:52 AM
тАО11-04-2009 07:52 AM
A DIBOL Program executable run successfully at production and not in development. This DIBOL program gets invoked thru ACMS. In development it throws 33 too many channels open run time error. But the program contains only 90 channels which is < max 255 limit.
I have verified the "UAF> Show Username" against an existing production account.
My current account settings are.....
Maxjobs: 0 Fillm: 400 Bytlm: 1000000
Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0
Maxdetach: 0 BIOlm: 120 JTquota: 15000
Prclm: 8 DIOlm: 120 WSdef: 15000
Prio: 4 ASTlm: 150 WSquo: 16384
Queprio: 4 TQElm: 10 WSextent: 524288
CPU: (none) Enqlm: 2000 Pgflquo: 1000000
Whenever changes in UAF for the user, ACMS Stop and Start activities done. but still the same problem 33 - too many channels open...
Any sugeestion please......
Thanks
-VV
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 08:09 AM
тАО11-04-2009 08:09 AM
Re: ACMS - DIBOL Program throws 33 in Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 11:30 AM
тАО11-04-2009 11:30 AM
Re: ACMS - DIBOL Program throws 33 in Development
The program, if I remember correctly, was doing something like sending email using a distribution list. The problem was that the distribution list contained itself as an entry.
This caused a loop of some kind and caused the program to exceed the maximum number of channels open.
I'm not saying this is your problem, however it might get you thinking in the right direction.
HTH
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 12:42 PM
тАО11-04-2009 12:42 PM
Re: ACMS - DIBOL Program throws 33 in Development
$ analyze/system
SDA> show proc/id=xxxxxxxx ! replace x's with PID
SDA> show proc/chan
SDA> exit
I too have observed and fixed programs that misbehave and bleed channels - one instance that comes to mind occurred when a program repeatedly trapped some unexpected condition and looped back around opening a channel to the same object while neglecting to close the original channel - repeat until channel exhaustion. fwiw...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2009 01:05 AM
тАО11-05-2009 01:05 AM
Re: ACMS - DIBOL Program throws 33 in Development
Thanks for the different possible suggestion.
I have ensured that
A. CHANNELCNT - 16384 (SYS$SYSTEM:MODPARAMS.DAT)
B. the program is not falling under "Infinite Loop". and No Mail activities. The DIBOL Program does I/O Operation with 90 files.
C. Analyse/System - 16 channels open at the time of running the DIBOL Program thru ACMS.
I have added the following lines to list the number of channel open
Open (CHVVTEST, 'O', 'olw:CHtest.seq')
FOR TESTCHN FROM 1 THRU 250
IF (%CHOPEN(TESTCHN))
BEGIN
TESTCHN_A = TESTCHN
WRITES(CHVVTEST,TESTCHN_A)
END
It results the same 90 channels opened.
I am analysing the problem. Please share if you have any suggestion. Once i get a solution, I post it in the forum. Thanks you very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2009 06:26 AM
тАО11-05-2009 06:26 AM
Re: ACMS - DIBOL Program throws 33 in Development
A. CHANNELCNT - 16384 (SYS$SYSTEM:MODPARAMS.DAT)"
$ MCR SYSMAN PARAMETERS SHOW CHANNELCNT
?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2009 06:40 AM
тАО11-05-2009 06:40 AM
Re: ACMS - DIBOL Program throws 33 in Development
$ MCR SYSMAN PARAMETERS SHOW CHANNELCNT
gives the below result...
Parameter Name Current Default Minimum Maximum Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
CHANNELCNT 16384 256 31 65535 Channels
Thanks.
-VV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2009 04:59 AM
тАО11-06-2009 04:59 AM
Re: ACMS - DIBOL Program throws 33 in Development
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2009 03:37 PM
тАО11-07-2009 03:37 PM
Re: ACMS - DIBOL Program throws 33 in Development
Do the server usernames have the same access to the directories/files on dev/test as they do in production? (UIC group SOGW ACLs etc)
Cheers Richard Maher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2009 09:06 AM
тАО11-09-2009 09:06 AM
SolutionIt probably does not matter, but what versions are you using for Dibol, VMS, ACMS?
What is a typical full file name as provided? Logical name involved? Search list involved?
You mention 'username'. But with ACMS there are several usernames in play. The one that matters is probably the username used for the procedure server process. Is that the one you checked?
Is it possible for you to run your test in production? It is probably relevant to know whether the production box would fail with just a few more files open, or with many more open files (whatever the documented Dibol max is). If production fails with just a few more files, then the difference could be a extra library or message file being activated or not.
>> Analyse/System - 16 channels open at the time of running the DIBOL
That doesn't make much sense.. unless this is strictly a Dibol runtime event, and not a system resource issues.
Can you change the test program to go to sleep when there are 89 channels open and repeat the ANALYZE/SYS... SHOW PROC/CHANNEL?
Maybe you see non-file disk channels for each time the file is opened? That could be a mismanaged file context in LIB$FIND_FILE before getting to the open.
Hope this helps some,
Hein.