[Administravia] The list has moved to a new home

[Johnson, Harold A EDUC:EX]

This is an error that occurs when compiling a screen, not during run time.
Anyone can duplicate the error by creating a simple screen with 16 temps of
2000 chars each.  (~32,000 chars)  I'm not complaining about it, just
wondering if there was a "startup" parameter with PH that will allow me to
bump up this limit.  I'm been working with VMS and PH for 15 years.
Reworking the screen is not an option, but we do have a work around
(compiling under version 830d); our VMS limits are already quite high.

Yes, it is indeed great to have the listserve back! 

thnx all



-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of Chris Sharman
Sent: 2004 February 20 4:04 AM
To: powerh-l@sowder.com
Subject: Re: [Administravia] The list has moved to a new home


Johnson, Harold A EDUC:EX wrote:

> Here's one to start us off!

Great to have the list back - thanks very much David.

> We have a very large PH screen that is being ported from Unix to OpenVMS.
> Our OpenVMS version of PH (710g1) chokes on the screen and complains that
> the "*E* The internal buffer size limit has been exceeded."  The screen
uses
> a very large number/size of temporaries but works fine on Unix PH and also
> compiles fine under 830d and later versions.  Upgrading our entire system
to
> 830d is not an option at this point.
> My question is:  is this limit (~32,000 temporary chars) a hard coded
limit
> in PH or can it be adjusted via some system parameter?

Look into the QKGO maintenance, and runtime parameters etc.
We've seen obscure errors go away with an uplift in quotas, too.
In authorize, we've got wsdef, wsquo, and wsextent set to 2k, 4k, 16k 
respectively, and pgflquo set to 50k for our PH users - YMMV.
System parameters WSMAX and VIRTUALPAGECNT impose systemwide limits on 
the same quotas, so they need to be at least that high.

Authorize changes are effective from next login, changing system 
parameters typically requires running sys$update:autogen & rebooting.

It is possible to run several versions of Powerhouse on VMS 
simultaneously, so long as the screens don't call each other: you'd just 
need an @setpowerhouse either side of the errant screen.

Sorry if I'm telling you things you already know - you don't say how 
familiar you are with VMS.

Chris


-----------------------------------------------------------------------

Any views expressed in this message are those of the sender and not
necessarily those of CCA Group.  The unauthorized use, disclosure,
copying or alteration of this message is forbidden.  The contents of
this message may be confidential and/or privileged, copyright CCA Group
and are intended solely for the use of the individual or entity to whom
they are addressed.  Whilst this message has been scanned, CCA Group
cannot guarantee that it is virus free or compatible with your systems
and accepts no responsibility for any loss or damage arising from its
use. The recipient is advised to run their own anti-virus software. If
you receive this message in error please contact
postmaster@ccagroup.co.uk immediately, destroy any copies and delete it
from your computer systems.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.