2Gig limitation - is this limited to Unix or does it also affect VMS?

Wed, 2 Feb 2005 14:29:07 -0500

This is a multi-part message in MIME format.

------_=_NextPart_001_01C5095D.768B1AC5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

PowerHouse itself is limited to 2 Gig records in its counters such as
REPORT LIMIT. My understanding is that C-ISAM is also limited to 2 Gig
records. There used to be a limitation of a 2 Gigabyte file size. Large
file support overcomes this size limitation but not the record count
limit.
=20
And I apologize for the misuse of gigabyte in the Large File Support
discussion. I remember trying to be very careful about using records
where I meant a count and gigabyte where I meant the size in bytes. The
last use of gigabyte was incorrect.
=20
I do not know about RMS ISAM specifically. I have never heard of any
complaints (which doesn't mean there weren't any) regarding number of
bytes.
Bob Deskin             =20
Senior Product Manager, Application Development Tools, Cognos Inc.=20
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178=20
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA=20

	-----Original Message-----
	From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Joe Boyle
	Sent: February 2, 2005 1:18 PM
	To: 'Philip Jackson'; powerh-l@lists.sowder.com
	Subject: RE: 2Gig limitation - is this limited to Unix or does
it also affect VMS?
=09
=09

	the details below would suggest that you are correct when you
say 'the limitation was more in the C-ISAM libraries than the PowerHouse
libraries/products.', but if that is the case why limit the number of
records to 2^31, unless there is a PH internal issue after all; and if
there is a PH internal problem, does it affect VMS also ? Which is where
I started :-)

	=20

	Regards, Joe.=20

=09
________________________________

	From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Philip Jackson
	Sent: 02 February 2005 17:47
	To: powerh-l@lists.sowder.com
	Subject: RE: 2Gig limitation - is this limited to Unix or does
it also affect VMS?

	=20

	From the manual for 8.4

	=20

	Large File Support (UNIX)

	Direct and sequential files, non-indexed subfiles and portable
subfiles can now exceed the two

	gigabyte limit in total number of bytes.

	The file must be recreated to be able to grow beyond two
gigabytes. An existing file cannot grow

	beyond the two gigabyte limit.

	The file system must be able handle large files and must be
configured to allow them.

	PowerHouse 4GL can still only process up to 2,147,483,647
records.

	Note: PowerHouse 8.43 supports large files for C-ISAM within the
limit set by C-ISAM version

	7.25 which is greater than 2 gigabytes. The maximum number of
records supported by C-ISAM

	is the same as for flat files, 2 gigabytes.

	=20

	which I take to mean that non-indexed files can exceed
2,147,483,647 records now with some system changes/file recreations, but
that indexed ones can't.

	=20

	Bit confusing the way they seem to use gigabytes to mean the
number of records, as opposed to the number of bytes.

	=20

	I actually understood the limitation was more in the C-ISAM
libraries than the PowerHouse libraries/products.

	=20

	Cheers,

	Philip

	=20

=09
________________________________

	From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Joe Boyle
	Sent: 02 February 2005 17:15
	To: 'Johnson, Harold A EDUC:EX'; powerh-l@lists.sowder.com
	Subject: RE: 2Gig limitation - is this limited to Unix or does
it also affect VMS?

	I think a test case was logged on Unix using a QTP which
attempted to write records out to a subfile, and once the number of
bytes written out exceeded 2^31 a fatal error occurred.  I then recall
that this behaviour was fixed to the extent that now the failure ( not
error as this is a new limitation ) will occur when 2^31 'records' have
been written.

	=20

	I assume that quick would have the same problem when reading or
writing similar numbers of records, but I am not clear if this affects
Unix only, or if VMS would suffer similarly.

	=20

	I seem to recall that BD once said that this would affect RDB's
also, as the call originally related to CISAM, I do not know if RMS on
VMS is affected.

	=20

	I'm not thinking of the quick screen call issue, but the
underlying causes might be related as far as I know.

	=20

	I seem to recall that the limitation was a result of PH being a
32 bit application - and presumably able to map to 'only' 2^31 addresses
on the stack.

	Regards, Joe.=20

=09
________________________________

	From: Johnson, Harold A EDUC:EX
[mailto:Harold.A.Johnson@gems1.gov.bc.ca]=20
	Sent: 02 February 2005 16:37
	To: 'Joe Boyle'; powerh-l@lists.sowder.com
	Subject: RE: 2Gig limitation

	=20

	Do you mean in QTP (ie: total size of records accessed?) or
QDESIGN/QUICK?    There is a problem on OpenVMS/Powerhouse when calling
screens (run screen) in batch processing using QUICK - there is a limit
as to how many times screens can be called (~32k times).  Otherwise,
I've never experienced a problem with the number or size of data
processed.    (our main application is current hovering around the 160gb
size)

	=20

	=20

		-----Original Message-----
		From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com]On Behalf Of Joe Boyle
		Sent: 2005 February 2 5:08 AM
		To: powerh-l@lists.sowder.com
		Subject: 2Gig limitation

		Hi all,

		Does anyone know if the 2 Gig processing limitation
applies on VMS platforms as well as Unix ?=20

		If the problem is due to the fact that PH is a 32 bit
application, and I am assuming that PH is a 32 bit application on both
VMS and Unix, then the problem is likely to exist on both - any ideas ?

		For those that may not be aware of it, the limitation on
Unix was that processing would stop after processing 2 Gig bytes had
been processed. This was then partially fixed so that processing would
stop when 2 Gig records ( of any acceptable byte length ) had been
processed.

		Regards, Joe.

		This e-mail and all information contained in it is
confidential and may be legally privileged. If you are not the intended
recipient, your access to this e-mail is unauthorized. Any use,
dissemination, distribution, publication or copying by you of this
e-mail or any of the information contained within it is prohibited and
may be unlawful. Do not open any attachments, delete it immediately from
your system and notify the sender promptly by e-mail that you have done
so. The content of this e-mail and any attachments sent with it may have
been altered without the consent or knowledge of the author.=20
 =20
       This message may contain privileged and/or confidential =
information.  If you have received this e-mail in error or are not the =
intended recipient, you may not use, copy, disseminate or distribute it; =
do not open any attachments, delete it immediately from your system and =
notify the sender promptly by e-mail that you have done so.  Thank you.=20
=20

------_=_NextPart_001_01C5095D.768B1AC5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<HTML xmlns:eXclaimer=3D"http://www.exclaimer.co.uk">
<HEAD>
<META http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DUTF-16">
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUTF-16"><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Helvetica;
}
@font-face {
	font-family: Wingdings;
}
@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 612.0pt 792.0pt; margin: 72.0pt 90.0pt 72.0pt =
90.0pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0cm; MARGIN-RIGHT: 0cm; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle20 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD><BODY lang=3DEN-US vLink=3Dpurple link=3Dblue><DIV>
<DIV><SPAN class=3D262491119-02022005><FONT face=3DArial color=3D#0000ff =

size=3D2>PowerHouse itself is limited to 2 Gig records in its counters =
such as=20
REPORT LIMIT. My understanding is that C-ISAM is also limited to 2 Gig =
records.=20
There used to be a limitation of a 2 Gigabyte file size. Large file =
support=20
overcomes this size limitation but not the record count=20
limit.</DIV>
<DIV><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;</DIV>
<DIV>And I=20
apologize for the misuse of gigabyte in the Large File Support =
discussion. I=20
remember trying to be very careful about using records where I meant a =
count and=20
gigabyte where I meant the size in bytes. The last use of gigabyte was=20
incorrect.</DIV>
<DIV><FONT face=3DArial color=3D#0000ff =

size=3D2>&nbsp;</DIV>
<DIV>I do=20
not know about RMS ISAM specifically. I have never heard of any =
complaints=20
(which doesn't mean there weren't any) regarding number of=20
bytes.</DIV>
<DIV>
Bob=20
Deskin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
 Senior =
Product=20
Manager, Application Development Tools, Cognos Inc. =
 <SPAN=20
lang=3Den-us>bob.deskin@cognos.com (613) =
738-1338 ext 7268=20
FAX: (613) 727-1178 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9=20
CANADA </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
 <DIV></DIV>
 <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
 face=3DTahoma size=3D2>-----Original Message----- From:=20
 powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com] On=20
 Behalf Of Joe Boyle Sent: February 2, 2005 1:18 =
PM To:=20
 'Philip Jackson'; powerh-l@lists.sowder.com Subject: RE: =
2Gig=20
 limitation - is this limited to Unix or does it also affect=20
 VMS? </DIV>
 <DIV class=3DSection1>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">the details =
below=20
 would suggest that you are correct when you say =
&#8216;<FONT=20
 face=3DHelvetica color=3Dblue size=3D2><SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Helvetica">the =
limitation=20
 was more in the C-ISAM libraries than the PowerHouse=20
 libraries/products.&#8217;<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Helvetica">, but if that is the =
case why=20
 limit the number of records to 2^31, unless there is a PH internal =
issue after=20
 all; and if there is a PH internal problem, does it affect VMS also ? =
Which is=20
 where I started <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Wingdings">J<FONT =

face=3DArial size=3D2><SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p>
 <DIV>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Regards,=20
 Joe.=20
 <o:p></o:p></DIV>
 <DIV>
 <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
 face=3D"Times New Roman" size=3D3>
 <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D3>
 </DIV>
 <SPAN=20
 style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:<FONT=20
 face=3DTahoma size=3D2>=20
 powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com]=20
 On Behalf Of Philip=20
 Jackson Sent: 02 =
February=20
 2005 17:47 To:=20
 powerh-l@lists.sowder.com <SPAN=20
 style=3D"FONT-WEIGHT: bold">Subject: RE: 2Gig limitation - =
is this=20
 limited to Unix or does it also affect =
VMS?<o:p></o:p></DIV>
 <SPAN=20
 style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">From the =
manual for=20
 8.4<SPAN=20
 style=3D"FONT-SIZE: 18pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 18pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 18pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">Large File=20
 Support (UNIX)<SPAN=20
 style=3D"FONT-SIZE: 18pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">Direct and=20
 sequential files, non-indexed subfiles and portable subfiles can now =
exceed=20
 the two<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">gigabyte=20
 limit in total number of bytes.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier New'">The =
file must=20
 be recreated to be able to grow beyond two gigabytes. An existing file =
cannot=20
 grow<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">beyond the=20
 two gigabyte limit.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier New'">The =
file=20
 system must be able handle large files and must be configured to allow =

them.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">PowerHouse=20
 4GL can still only process up to 2,147,483,647 =
records.<FONT=20
 face=3DArial size=3D2><SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
'Courier New'">Note:=20
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">PowerHouse=20
 8.43 supports large files for C-ISAM within the limit set by C-ISAM=20
 version<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier =
New'">7.25 which is=20
 greater than 2 gigabytes. The maximum number of records supported by=20
 C-ISAM<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: 'Courier New'">is =
the same=20
 as for flat files, 2 gigabytes.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Helvetica">which I =
take to=20
 mean that non-indexed files can exceed 2,147,483,647 records now with =
some=20
 system&nbsp;changes/file recreations, but that indexed ones=20
 can't.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Helvetica">Bit =
confusing the=20
 way they seem to use gigabytes to mean the number of records, as =
opposed to=20
 the number of bytes.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Helvetica">I =
actually=20
 understood the limitation was more in the C-ISAM libraries than the =
PowerHouse=20
 libraries/products.<SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Helvetica">Cheers,<FONT=20
 face=3DArial size=3D2><SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Helvetica">Philip<FONT=20
 face=3DArial size=3D2><SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p>
 <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
 face=3D"Times New Roman" size=3D3>
 <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D3>
 </DIV>
 <SPAN=20
 style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:<FONT=20
 face=3DTahoma size=3D2>=20
 powerh-l-admin@lists.sowder.com =
[mailto:powerh-l-admin@lists.sowder.com]=20
 On Behalf Of Joe=20
 Boyle Sent: 02 =
February 2005=20
 17:15 To: 'Johnson, =
Harold A=20
 EDUC:EX'; powerh-l@lists.sowder.com <SPAN=20
 style=3D"FONT-WEIGHT: bold">Subject: RE: 2Gig limitation - =
is this=20
 limited to Unix or does it also affect =
VMS?<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I think a =
test case=20
 was logged on Unix using a QTP which attempted to write records out to =
a=20
 subfile, and once the number of bytes written out exceeded 2^31 a =
fatal error=20
 occurred.&nbsp; I then recall that this behaviour was fixed to the =
extent that=20
 now the failure ( not error as this is a new limitation ) will occur =
when 2^31=20
 &#8216;records&#8217; have been written.<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I assume =
that quick=20
 would have the same problem when reading or writing similar numbers of =

  records, but I am not clear if this affects Unix only, or if VMS would =
suffer=20
  similarly.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I seem to =
recall that=20
  BD once said that this would affect RDB&#8217;s also, as the call =
originally related=20
  to CISAM, I do not know if RMS on VMS is=20
affected.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I&#8217;m =
not thinking of=20
  the quick screen call issue, but the underlying causes might be =
related as far=20
  as I know.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I seem to =
recall that=20
  the limitation was a result of PH being a 32 bit application &#8211; =
and presumably=20
  able to map to &#8216;only&#8217; 2^31 addresses on the=20
stack.<o:p></o:p></SPAN></FONT></P>
  <DIV>
  <P><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Regards,=20
  Joe.</SPAN></FONT><FONT color=3Dnavy><SPAN style=3D"COLOR: navy">=20
  <o:p></o:p></SPAN></FONT></P></DIV>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D3>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  Johnson, Harold A EDUC:EX [mailto:Harold.A.Johnson@gems1.gov.bc.ca]=20
  <BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 02 February =
2005=20
  16:37<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> 'Joe =
Boyle';=20
  powerh-l@lists.sowder.com<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: 2Gig=20
  limitation</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Do you mean =
in QTP=20
  (ie: total size of records accessed?) or =
QDESIGN/QUICK?&nbsp;&nbsp;&nbsp;=20
  There is a problem on OpenVMS/Powerhouse when calling screens (run =
screen) in=20
  batch processing using QUICK - there is a limit as to how many=20
  times&nbsp;screens can be called (~32k times).&nbsp; Otherwise, I've =
never=20
  experienced a problem with the number or size of data=20
  processed.&nbsp;&nbsp;&nbsp; (our main application is current hovering =
around=20
  the 160gb size)</SPAN></FONT><o:p></o:p></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
  <DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
  <BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; =
MARGIN-RIGHT: 0cm">
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
    Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
    powerh-l-admin@lists.sowder.com=20
    [mailto:powerh-l-admin@lists.sowder.com]<B><SPAN=20
    style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Joe =
Boyle<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 2005 February 2 5:08=20
    AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
    powerh-l@lists.sowder.com<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> 2Gig=20
    limitation</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- Converted from =
text/rtf format -->Hi=20
    all,</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Does anyone know if =
the 2 Gig=20
    processing limitation applies on VMS platforms as well as Unix=20
    ?</SPAN></FONT> <o:p></o:p></P>
    <P><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If the problem is due =
to the=20
    fact that PH is a 32 bit application, and</SPAN></FONT> <FONT =
face=3DArial=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I am =
assuming=20
    that</SPAN></FONT> <FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">PH is a 32 bit =
application on=20
    both VMS and Unix, then the problem is likely to exist on =
both</SPAN></FONT>=20
    <FONT face=3DArial size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Arial">-=20
    any ideas ?</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">For those that may not =
be aware=20
    of it, the limitation on Unix was that processing would stop after=20
    processing 2</SPAN></FONT> <FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Gig bytes had been =
processed.=20
    This was then partially fixed so that</SPAN></FONT> <FONT =
face=3DArial=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">processing would=20
    stop when 2 Gig records ( of any acceptable byte length =
)</SPAN></FONT>=20
    <FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">had been=20
    processed.</SPAN></FONT><o:p></o:p></P>
    <P><A name=3D""><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Regards,=20
    Joe.</SPAN></FONT></A><o:p></o:p></P>
    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This e-mail and all =
information=20
    contained in it is confidential and may be legally privileged. If =
you are=20
    not the intended recipient, your access to this e-mail is =
unauthorized. Any=20
    use, dissemination, distribution, publication or copying by you of =
this=20
    e-mail or any of the information contained within it is prohibited =
and may=20
    be unlawful. Do not open any attachments, delete it immediately from =
your=20
    system and notify the sender promptly by e-mail that you have done =
so. The=20
    content of this e-mail and any attachments sent with it may have =
been=20
    altered without the consent or knowledge of the=20
    =
author.</SPAN></FONT><o:p></o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE></DIV=
>
<DIV>&nbsp;</DIV>
<DIV>
<P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<FONT FACE=3D"Arial" =
SIZE=3D"2">This message may contain privileged and/or confidential =
information.&nbsp; If you have received this e-mail in error or are not =
the intended recipient, you may not use, copy, disseminate or distribute =
it; do not open any attachments, delete it immediately from your system =
and notify the sender promptly by e-mail that you have done so.&nbsp; =
Thank you.</FONT>
</P>
</DIV></BODY></HTML>

------_=_NextPart_001_01C5095D.768B1AC5--