- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Help with new Integrity
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
тАО06-04-2008 03:08 AM
тАО06-04-2008 03:08 AM
Help with new Integrity
Both should be identical. One one system I am getting this error:
%DCL-E-OPENIN, error opening SYS$SYSDEVICE:[MYDIRECTORY]QUELIST.DAT; as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-EXBYTLM, exceeded byte count quota
*** Exiting due to error encountered
FM21$ dir/date/size quelist.dat
QUELIST.DAT;3 exceeded byte count quota
QUELIST.DAT;2 exceeded byte count quota
QUELIST.DAT;1 exceeded byte count quota
Total of 3 files, 0 blocks.
My account has both: UIC 1,4 & bypass, I only get this on one system, the other one is fine.
And all setting for my account on both systems are identical
If I log out and back in, itтАЩs works fine. It is reproducable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 03:35 AM
тАО06-04-2008 03:35 AM
Re: Help with new Integrity
The help/message says
help/message EXBYTLM
Facility: SYSTEM, System Services
Explanation: The requested operation failed because the byte count quota of
the process is not large enough. This can occur if excessive
concurrent buffered I/O is outstanding, if a large number of
mailboxes is created, or if a large number of windows needs to
be created to completely map a file.
Failure on window creation can occur on a $CRMPSC, $CREATE_
GFILE, $CRMPSC_FILE_64, or $CRMPSC_GFILE_64 system service
call, the DCL command RUN, or an Access or Create of a file.
In this case, this message indicates that the specified file
is very fragmented or the byte limit quota of the process
should be increased.
What is the bytlm of the 2 processes ?
Check the bytlm and bytcnt (in fact JIB$L_OR
G_BYTLM) using the procedure I posted at
http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1212579054833+28353475&threadId=712900
What is the value of the system parameter MAXBUF on both systems ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 04:42 AM
тАО06-04-2008 04:42 AM
Re: Help with new Integrity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 04:44 AM
тАО06-04-2008 04:44 AM
Re: Help with new Integrity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 04:46 AM
тАО06-04-2008 04:46 AM
Re: Help with new Integrity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 04:58 AM
тАО06-04-2008 04:58 AM
Re: Help with new Integrity
May be the login or sylogin does different things on the 2 nodes, and you have just a little bytlm lef t on a node ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 05:27 AM
тАО06-04-2008 05:27 AM
Re: Help with new Integrity
As you have a recent OpenVMS version (8.3) you can also look into the process from a different window using : $SHOW PROC/CONT/ID
Now hit "q" for the dynamic quoate display.
See how it changes through the life of the process.
It must be building up open files, outstanding IO and so on.
Is the problem specific to one (set of) file(s) as suggested or does the DIR/DATE fail on all files once it fails?
If it is one (set) of files, then try other things: Can you do DIR/FILE. Probably yes, as that does not open the file. Can you do DUMP/HEAD/BLO=COUNT=0?...
And uh.. what does DIR/FULL or DUMP/HEAD/BLOCK=COUNT=0 look like when it succeeds?
Good luck!
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-04-2008 08:05 AM
тАО06-04-2008 08:05 AM
Re: Help with new Integrity
Have you verified this under a correctly-provisioned SYSTEM username?
Here are a few quota-related discussions:
http://64.223.189.234/node/141
http://64.223.189.234/node/226
http://64.223.189.234/node/49
Various memory-related process quotas can potentially need to be doubled or better from (good) Alpha values, and even the older OpenVMS Alpha quotas have seen increases into the V8 range. And existing quota values can quite easily be somewhere between marginal and entirely insufficient. And there are specific recommendations around increasing quotas on existing SYSTEM users even on OpenVMS Alpha releases.
OpenVMS I64 physical memory tends to best be double or triple that of a reasonable and equivalent OpenVMS Alpha memory configuration, too, at least in terms of executable code size. (And being faster and usually more capable than most any Alpha systems, more is better.)
The "so I don't think fragmentation would be the issue" is an odd approach toward debugging. Years spent in debug has taught me that certain sorts of assumptions can lead me badly astray. Here, even with these files, I'd still check disk fragmentation. Sure, it might be a waste of time, but -- if the fragmentation had been checked -- it's quite and easy and a minimal waste of time, and it's also work that allows fragmentation to be ruled out as a potential trigger.
And FWIW, your account should not be [1,4], unless you are SYSTEM. That's bad practice from the perspective of accountability; it's the sort of thing that (good) auditors will catch, too.
In general, do load current ECOs for OpenVMS I64 V8.3-1H1, too. DIRECTORY blowing up is either a system-level error, or the process quotas are way out of whack.
The BYPASS privilege is only centrally relevant to overriding object access and object protections, and not to quotas.
Stephen Hoffman
HoffmanLabs LLC