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

Wed, 2 Feb 2005 17:47:21 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0052_01C5094F.3F611300
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

>From the manual for 8.4

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.

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.

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

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

Cheers,
Philip

  _____  

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.

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.

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.

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

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. 

  _____  

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

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)

-----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 ? 

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.

------=_NextPart_000_0052_01C5094F.3F611300
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD><TITLE>2Gig =
limitation</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: 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-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue><FONT face=3DArial =
size=3D2><FONT size=3D5>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D760363817-02022005><FONT =
color=3D#0000ff=20
size=3D2>From the manual for 8.4</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D760363817-02022005></SPAN><FONT=20
color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><STRONG><FONT face=3D"Courier New" =
color=3D#0000ff>Large=20
File Support (UNIX)</FONT></STRONG></DIV></FONT>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>Direct and =
sequential=20
files, non-indexed subfiles and portable subfiles can now exceed the=20
two</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>gigabyte =
limit in total=20
number of bytes.</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>The file =
must be=20
recreated to be able to grow beyond two gigabytes. An existing file =
cannot=20
grow</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>beyond the =
two gigabyte=20
limit.</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>The file =
system must be=20
able handle large files and must be configured to allow =
them.</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>PowerHouse =
4GL can still=20
only process up to 2,147,483,647 records.</FONT></DIV><B>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>Note: =
</FONT></B><FONT=20
face=3D"Courier New" color=3D#0000ff>PowerHouse 8.43 supports large =
files for C-ISAM=20
within the limit set by C-ISAM version</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>7.25 which =
is greater=20
than 2 gigabytes. The maximum number of records supported by =
C-ISAM</FONT></DIV>
<DIV align=3Dleft><FONT face=3D"Courier New" color=3D#0000ff>is the same =
as for flat=20
files, 2 gigabytes.</FONT></DIV>
<DIV align=3Dleft><FONT face=3DHelvetica =
color=3D#0000ff></FONT>&nbsp;</DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff>which I take to mean that non-indexed files can exceed=20
2,147,483,647 records now with some system&nbsp;changes/file =
recreations, but=20
that indexed ones can't.</FONT></SPAN></DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff>Bit confusing the way they seem to use gigabytes to mean =
the=20
number of records, as opposed to the number of =
bytes.</FONT></SPAN></DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff>I actually understood the limitation was more in the =
C-ISAM=20
libraries than the PowerHouse libraries/products.</FONT></SPAN></DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff></FONT></SPAN>&nbsp;</DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff>Cheers,</FONT></SPAN></DIV>
<DIV align=3Dleft><SPAN class=3D760363817-02022005><FONT =
face=3DHelvetica=20
color=3D#0000ff>Philip</FONT></SPAN></DIV></FONT><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
powerh-l-admin@lists.sowder.com=20
[mailto:powerh-l-admin@lists.sowder.com] <B>On Behalf Of </B>Joe=20
Boyle<BR><B>Sent:</B> 02 February 2005 17:15<BR><B>To:</B> 'Johnson, =
Harold A=20
EDUC:EX'; powerh-l@lists.sowder.com<BR><B>Subject:</B> RE: 2Gig =
limitation - is=20
this limited to Unix or does it also affect VMS?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I think a =
test case was=20
logged on Unix using a QTP which attempted to write records out to a =
subfile,=20
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></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 assume that =
quick=20
would have the same problem when reading or writing similar numbers of =
records,=20
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 =
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 the=20
quick screen call issue, but the underlying causes might be related as =
far as I=20
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 =
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 =

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"> Johnson,=20
Harold A EDUC:EX [mailto:Harold.A.Johnson@gems1.gov.bc.ca] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 02 February 2005 =
16:37<BR><B><SPAN=20
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 (ie:=20
total size of records accessed?) or QDESIGN/QUICK?&nbsp;&nbsp;&nbsp; =
There is a=20
problem on OpenVMS/Powerhouse when calling screens (run screen) in batch =

processing using QUICK - there is a limit as to how many =
times&nbsp;screens can=20
be called (~32k times).&nbsp; Otherwise, I've never experienced a =
problem with=20
the number or size of data processed.&nbsp;&nbsp;&nbsp; (our main =
application is=20
current hovering around the 160gb =
size)<o:p></o:p></DIV>
<DIV>
<SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></DIV>
<DIV>
<SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></DIV>
<BLOCKQUOTE style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; MARGIN-RIGHT: =
0cm">
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
 Message----- From:=20
 powerh-l-admin@lists.sowder.com=20
 [mailto:powerh-l-admin@lists.sowder.com]On=20
 Behalf Of Joe Boyle <SPAN=20
 style=3D"FONT-WEIGHT: bold">Sent: 2005 February 2 5:08 =
AM <SPAN=20
 style=3D"FONT-WEIGHT: bold">To: =
powerh-l@lists.sowder.com <SPAN=20
 style=3D"FONT-WEIGHT: bold">Subject: 2Gig=20
 limitation<o:p></o:p>
 Hi=20
 all,<o:p></o:p>
 <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
 <o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If the problem is due to =
the fact=20
 that PH is a 32 bit application, and I am =
assuming=20
 that <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">PH is a 32 bit =
application on both=20
 VMS and Unix, then the problem is likely to exist on =
both <FONT=20
 face=3DArial size=3D2>- any=20
 ideas ?<o:p></o:p>
 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">For those that may not =
be aware of=20
 it, the limitation on Unix was that processing would stop after =
processing=20
 2 <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Gig bytes had been =
processed. This=20
 was then partially fixed so that <SPAN=20
 style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">processing would stop =
when 2 Gig=20
 records ( of any acceptable byte length ) had been=20
 processed.<o:p></o:p>
 <A name=3D"">Regards,=20
 Joe.</A><o:p></o:p>
 This e-mail and all =
information=20
 contained in it is confidential and may be legally privileged. If you =
are not=20
 the intended recipient, your access to this e-mail is unauthorized. =
Any use,=20
 dissemination, distribution, publication or copying by you of this =
e-mail or=20
 any of the information contained within it is prohibited and may be =
unlawful.=20
 Do not open any attachments, delete it immediately from your system =
and notify=20
 the sender promptly by e-mail that you have done so. The content of =
this=20
 e-mail and any attachments sent with it may have been altered without =
the=20
 consent or knowledge of the=20
author.<o:p></o:p></BLOCKQUOTE></DIV></BODY></HTML>

------=_NextPart_000_0052_01C5094F.3F611300--