P/H on Unix
Deskin, Bob
Bob.Deskin@Cognos.COM
Tue, 4 Feb 2003 07:03:14 -0500
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_01C2CC45.651AA550
Content-Type: text/plain;
charset="iso-8859-1"
Since you are doing a database conversion anyway, your IMAGE files, records,
and items will not be used. The elements will provide the logical view
(labels, edits, etc.). I recommend that you convert to a numeric type that
is supported. Presumably, you're writing out your IMAGE data as portable
subfiles and using QTP to load the new Sybase database. Unless you force a
character conversion, PowerHouse will quite happily move numeric to numeric
even though the storage type is different.
Unless you're doing a lot of substructuring or manipulation based on the
fact that the items are zoned, you should not have major code changes in
your PowerHouse code. You may not even need to change the dictionary from
the original.
You may have some work up front, but you'll save a lot of grief later.
Bob Deskin
PowerHouse Web Product Manager, Application Development Tools
Cognos Inc. 3755 Riverside Drive, Ottawa ON K1G 4K9 CANADA
bob.deskin@cognos.com (613) 738-1338 ext 7268
-----Original Message-----
From: Patrick Wright [mailto:pwright@mhg.co.za]
Sent: February 4, 2003 2:07 AM
To: 'powerh-l@lists.swau.edu'
Cc: Derick Snyders; Mark Toms
Subject: P/H on Unix
<http://196.22.0.16/RocketSeed/mail/433a313a31303438393a39313a2d323a30>
Metropolitan Health Group - always innovating.
... for more info visit our website: http://www.mhg.co.za
I am in the process of converting an HP3000 P/H, Turboimage system to HP-UX
with Sybase.
One of the main migration issues is that many elements and items in the
HP3000 dict are defined as Zoned. No such data type exists on Sybase.
Consequently the Sybase PDL defines the old Zoned fields as character.
As the Sybase dictionary is used to as a subdict to P/H, P/H now sees these
fields as character and numerous code changes need to be made in order to
cater for these now c\character fields.
The questions is: is it possible in any way to use the P/H dictionary to
overwrite the SQL (Sybase) element definitions ?
Regards
Patrick Wright
Head: Newmed Systems
Metropolitan Health Group
Tel: (021) 480 478 6
Fax: (021) 480 4932
Mobil: 082 652 7474
eMail: pwright@mhg.co.za
www.mhg.co.za
**********************************************************************
------
NOTICE
------
This message contains privileged and confidential information intended
only for the person or entity to which it is addressed.
Any review, retransmission, dissemination, copy or other use of, or
taking of any action in reliance upon this information by persons or
entities other than the intended recipient, is prohibited.
If you received this message in error, please notify the sender
immediately by e-mail, facsimile or telephone and thereafter delete the
material from any computer.
Metropolitan Health Group, its subsidiaries or associates
do not accept liability for any personal views expressed in
this message.
**********************************************************************
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_01C2CC45.651AA550
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4807.2300" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=111065711-04022003><FONT face=Arial color=#0000ff size=2>Since
you are doing a database conversion anyway, your IMAGE files, records, and items
will not be used. The elements will provide the logical view (labels, edits,
etc.). I recommend that you convert to a numeric type that is supported.
Presumably, you're writing out your IMAGE data as portable subfiles and using
QTP to load the new Sybase database. Unless you force a character conversion,
PowerHouse will quite happily move numeric to numeric even though the storage
type is different.</FONT></SPAN></DIV>
<DIV><SPAN class=111065711-04022003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=111065711-04022003><FONT face=Arial color=#0000ff size=2>Unless
you're doing a lot of substructuring or manipulation based on the fact that the
items are zoned, you should not have major code changes in your PowerHouse code.
You may not even need to change the dictionary from the
original.</FONT></SPAN></DIV>
<DIV><SPAN class=111065711-04022003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=111065711-04022003><FONT face=Arial color=#0000ff size=2>You
may have some work up front, but you'll save a lot of grief
later.</FONT></SPAN></DIV>
<DIV><SPAN class=111065711-04022003>
<P><FONT face=Arial size=2>Bob
Deskin
</FONT><BR><FONT face=Arial size=2>PowerHouse Web Product Manager</FONT><FONT
face=Arial size=2>,</FONT> <FONT face=Arial size=2>Application Development
Tools</FONT> <BR><FONT face=Arial size=2>Cognos Inc.</FONT><FONT face=Arial
size=2></FONT> <FONT face=Arial size=2>3755 Riverside Drive</FONT><FONT
face=Arial size=2>,</FONT> <FONT face=Arial size=2>Ottawa ON K1G 4K9
CANADA</FONT> <BR><FONT face=Arial size=2>bob.deskin@cognos.com</FONT><FONT
face=Arial size=2></FONT> <FONT face=Arial size=2>(613) 738-1338 ext</FONT>
<FONT face=Arial size=2>7268</FONT> </P></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Patrick Wright
[mailto:pwright@mhg.co.za]<BR><B>Sent:</B> February 4, 2003 2:07
AM<BR><B>To:</B> 'powerh-l@lists.swau.edu'<BR><B>Cc:</B> Derick Snyders; Mark
Toms<BR><B>Subject:</B> P/H on Unix<BR><BR></FONT></DIV><A
href="http://196.22.0.16/RocketSeed/mail/433a313a31303438393a39313a2d323a30"><!-- RS-STRIP-BEGIN MTk2LjIyLjAu --><IMG
alt="Metropolitan Health Group - always innovating. ... for more info visit our website: http://www.mhg.co.za"
src="http://196.22.0.16/RocketSeed/mail/563a313a31303438393a39313a2d323a30.gif"
border=0 NOSEND="1"> <!-- RS-STRIP-END MTk2LjIyLjAu --></A>
<P>I am in the process of converting an HP3000 P/H, Turboimage system to
HP-UX<BR>with Sybase.<BR><BR>One of the main migration issues is that many
elements and items in the<BR>HP3000 dict are defined as Zoned. No such data
type exists on Sybase.<BR>Consequently the Sybase PDL defines the old Zoned
fields as character. <BR>As the Sybase dictionary is used to as a subdict to
P/H, P/H now sees these<BR>fields as character and numerous code changes need
to be made in order to<BR>cater for these now c\character fields.<BR><BR>The
questions is: is it possible in any way to use the P/H dictionary
to<BR>overwrite the SQL (Sybase) element definitions
?<BR><BR>Regards<BR><BR>Patrick Wright<BR><BR>Head: Newmed
Systems<BR>Metropolitan Health Group<BR>Tel: (021) 480 478 6<BR>Fax: (021) 480
4932<BR>Mobil: 082 652 7474<BR>eMail:
pwright@mhg.co.za<BR>www.mhg.co.za<BR><BR><BR><BR><BR>**********************************************************************<BR>------<BR>NOTICE<BR>------<BR>This
message contains privileged and confidential information intended <BR>only for
the person or entity to which it is addressed. <BR><BR>Any review,
retransmission, dissemination, copy or other use of, or <BR>taking of any
action in reliance upon this information by persons or <BR>entities other than
the intended recipient, is prohibited.<BR><BR>If you received this message in
error, please notify the sender<BR>immediately by e-mail, facsimile or
telephone and thereafter delete the<BR>material from any
computer.<BR><BR>Metropolitan Health Group, its subsidiaries or associates
<BR>do not accept liability for any personal views expressed in <BR>this
message.<BR><BR>**********************************************************************<BR></P>
<P></P>
<P></P></BLOCKQUOTE></BODY></HTML>
<BR>
<P><FONT SIZE=2 FACE="Arial">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.</FONT></P>
------_=_NextPart_001_01C2CC45.651AA550--