PADS migration to 830D4

Hamilton, Allison Allison.Hamilton@Cognos.COM
Tue, 7 Oct 2003 14:45:01 -0400


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C38D03.1D47F820
Content-Type: text/plain;
	charset="iso-8859-1"

Daniel, thanks for providing that information.  

For general information, you could not examine this dictionary prior to 710G
because the dictionary was built with the NOSHOW option.  In 710G we opened
up the dictionary so that it could be examined in QSHOW.  You can also use
QUIZ to display the contents of your user dictionary, however because both
the user dictionary and pdschema are PHD dictionaries you have to 'fool'
QUIZ to use the correct dictionary for the right thing.  To do this:

$SETDICT <user dictionary>
$QUIZ dict=phd_location:pdschema
>....

This causes QUIZ to use the pdschema as it's underlying dictionary, but the
logical names for PHD0-4 (or 3 in 8.xx) are still set and these logicals
tell pdschema where to find the user dictionary files to report.  In this
case the user dictionary becomes just a set of data files.  

In the Upgrade Guide for 8.30 it mentions the things that are different in
the dictionary between 7.10 and 8.30.  The main difference causing the
record length changes was the upgrade from 32 to 64 characters for all
PowerHouse names.  We also added in Transactions, and a number of other new
features, many of which caused an increased record length, particularly in
the phd01 data file where the vast bulk of the dictionary specifics is kept.
Several of the files in the pdschema are coded records.  For PHD01 the
record OBJECTS contains the generic layout for that file.

-----Original Message-----
From: Miller, Daniel [mailto:Daniel.Miller@nightfreight.co.uk]
Sent: Monday, October 06, 2003 12:16 PM
To: Powerhouse List 3 (E-mail)
Subject: RE: PADS migration to 830D4


Hi Bruce,

Try:
	setdict phd_location:pdschema
	qshow

You should be able to see the files have open names of phd00, phd01 etc 



Out of interest, what is PADS?  I was considering writing some ph programs
to write programs which would check phd01 etc to validate files & elements
that i wanted to use.  Is this something similiar?


Daniel Miller

Any views expressed in this message are those of the sender and not
necessarily those of Nightfreight


-----Original Message-----
From: Migration Specialties International
[mailto:msi1@mail.earthlink.net]
Sent: Monday, October 06, 2003 4:18 PM
To: powerh-l@lists.swau.edu
Subject: PADS migration to 830D4


We're trying to port PADS (Powerhouse Application Development System) from
version 710G to version 830D4 under OpenVMS on an Alpha processor.  After
recompiling all of the PADS programs, most functions appear to work.
However, when using the PADGREP.QZS program we get the error:

*E* The actual record length doesn't match the length in the dictionary.

The error is generated by the PADS-PHD-OBJECTS select.  PADS-PHD-OBJECTS
points at the PHD01.PHD dictionary file.  It would appear the internal
layout of the PHD01 dictionary file has changed between 710G and 830D4.

Does anyone have a fix for this or information concerning the internal
structure of the PHD01.PHD dictionary file?

Thanks,

Bruce C.

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.

= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.

Join us at Cognos' biggest event of the year Enterprise 2003, The Cognos
Business Forum.  Taking place in over 25 cities around the world, it's an
opportunity for Business and IT leaders to learn about strategies for
driving performance. Visit http://www.cognos.com/enterprise03 for more
details. 

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.

------_=_NextPart_001_01C38D03.1D47F820
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: PADS migration to 830D4</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Daniel, thanks for providing that information.&nbsp; =
</FONT>
</P>

<P><FONT SIZE=3D2>For general information, you could not examine this =
dictionary prior to 710G because the dictionary was built with the =
NOSHOW option.&nbsp; In 710G we opened up the dictionary so that it =
could be examined in QSHOW.&nbsp; You can also use QUIZ to display the =
contents of your user dictionary, however because both the user =
dictionary and pdschema are PHD dictionaries you have to 'fool' QUIZ to =
use the correct dictionary for the right thing.&nbsp; To do =
this:</FONT></P>

<P><FONT SIZE=3D2>$SETDICT &lt;user dictionary&gt;</FONT>
<BR><FONT SIZE=3D2>$QUIZ dict=3Dphd_location:pdschema</FONT>
<BR><FONT SIZE=3D2>&gt;....</FONT>
</P>

<P><FONT SIZE=3D2>This causes QUIZ to use the pdschema as it's =
underlying dictionary, but the logical names for PHD0-4 (or 3 in 8.xx) =
are still set and these logicals tell pdschema where to find the user =
dictionary files to report.&nbsp; In this case the user dictionary =
becomes just a set of data files.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>In the Upgrade Guide for 8.30 it mentions the things =
that are different in the dictionary between 7.10 and 8.30.&nbsp; The =
main difference causing the record length changes was the upgrade from =
32 to 64 characters for all PowerHouse names.&nbsp; We also added in =
Transactions, and a number of other new features, many of which caused =
an increased record length, particularly in the phd01 data file where =
the vast bulk of the dictionary specifics is kept. Several of the files =
in the pdschema are coded records.&nbsp; For PHD01 the record OBJECTS =
contains the generic layout for that file.</FONT></P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Miller, Daniel [<A =
HREF=3D"mailto:Daniel.Miller@nightfreight.co.uk">mailto:Daniel.Miller@ni=
ghtfreight.co.uk</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, October 06, 2003 12:16 PM</FONT>
<BR><FONT SIZE=3D2>To: Powerhouse List 3 (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: RE: PADS migration to 830D4</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi Bruce,</FONT>
</P>

<P><FONT SIZE=3D2>Try:</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>setdict =
phd_location:pdschema</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT =
SIZE=3D2>qshow</FONT>
</P>

<P><FONT SIZE=3D2>You should be able to see the files have open names =
of phd00, phd01 etc </FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>Out of interest, what is PADS?&nbsp; I was =
considering writing some ph programs to write programs which would =
check phd01 etc to validate files &amp; elements that i wanted to =
use.&nbsp; Is this something similiar?</FONT></P>
<BR>

<P><FONT SIZE=3D2>Daniel Miller</FONT>
</P>

<P><FONT SIZE=3D2>Any views expressed in this message are those of the =
sender and not</FONT>
<BR><FONT SIZE=3D2>necessarily those of Nightfreight</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Migration Specialties International</FONT>
<BR><FONT SIZE=3D2>[<A =
HREF=3D"mailto:msi1@mail.earthlink.net">mailto:msi1@mail.earthlink.net</=
A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, October 06, 2003 4:18 PM</FONT>
<BR><FONT SIZE=3D2>To: powerh-l@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Subject: PADS migration to 830D4</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>We're trying to port PADS (Powerhouse Application =
Development System) from</FONT>
<BR><FONT SIZE=3D2>version 710G to version 830D4 under OpenVMS on an =
Alpha processor.&nbsp; After</FONT>
<BR><FONT SIZE=3D2>recompiling all of the PADS programs, most functions =
appear to work.</FONT>
<BR><FONT SIZE=3D2>However, when using the PADGREP.QZS program we get =
the error:</FONT>
</P>

<P><FONT SIZE=3D2>*E* The actual record length doesn't match the length =
in the dictionary.</FONT>
</P>

<P><FONT SIZE=3D2>The error is generated by the PADS-PHD-OBJECTS =
select.&nbsp; PADS-PHD-OBJECTS</FONT>
<BR><FONT SIZE=3D2>points at the PHD01.PHD dictionary file.&nbsp; It =
would appear the internal</FONT>
<BR><FONT SIZE=3D2>layout of the PHD01 dictionary file has changed =
between 710G and 830D4.</FONT>
</P>

<P><FONT SIZE=3D2>Does anyone have a fix for this or information =
concerning the internal</FONT>
<BR><FONT SIZE=3D2>structure of the PHD01.PHD dictionary file?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>Bruce C.</FONT>
</P>

<P><FONT SIZE=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>Mailing list: powerh-l@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Subscribe: &quot;subscribe&quot; in message body to =
powerh-l-request@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Unsubscribe: &quot;unsubscribe =
&lt;password&gt;&quot; in message body to =
powerh-l-request@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://lists.swau.edu/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.swau.edu/mailman/listinfo/powerh-l</A></F=
ONT>
<BR><FONT SIZE=3D2>This list is closed, thus to post to the list you =
must be a subscriber.</FONT>
</P>

<P><FONT SIZE=3D2>=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D</FONT>
<BR><FONT SIZE=3D2>Mailing list: powerh-l@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Subscribe: &quot;subscribe&quot; in message body to =
powerh-l-request@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2>Unsubscribe: &quot;unsubscribe =
&lt;password&gt;&quot; in message body to =
powerh-l-request@lists.swau.edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://lists.swau.edu/mailman/listinfo/powerh-l" =
TARGET=3D"_blank">http://lists.swau.edu/mailman/listinfo/powerh-l</A></F=
ONT>
<BR><FONT SIZE=3D2>This list is closed, thus to post to the list you =
must be a subscriber.</FONT>
</P>

<P><FONT SIZE=3D2>Join us at Cognos' biggest event of the year<I> =
Enterprise 2003, The Cognos Business Forum</I>.&nbsp; Taking place in =
over 25 cities around the world, it's an opportunity for Business and =
IT leaders to learn about strategies for driving performance. Visit<U> =
<A HREF=3D"http://www.cognos.com/enterprise03" =
TARGET=3D"_blank">http://www.cognos.com/enterprise03</A></U> for more =
details. </FONT></P>

<P><FONT SIZE=3D2>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>

</BODY>
</HTML>
------_=_NextPart_001_01C38D03.1D47F820--