Upgrade questions

Witkopp, Richard Richard.Witkopp@idt.com
Tue, 11 Jun 2002 10:29:35 -0700


It was for more than Cobol. You could generate
definitions for DEC's integrated dictionary that
interfaced with several DEC languages. I can't remember
what it's called, haven't used it in 7 or 8 years.

> -----Original Message-----
> From: Hasse, Christina [mailto:Christina.Hasse@COGNOS.com]
> Sent: Tuesday, June 11, 2002 10:13 AM
> To: 'Edis, Bob'
> Cc: 'powerh-l@lists.swau.edu'
> Subject: RE: Upgrade questions
> 
> 
> Hi Bob,
> 
> It was used to integrate Cobol with PowerHouse.  You could create copy
> libraries from PowerHouse and vice-versa.  The only problem 
> with it was that
> from Cobol to PowerHouse, you did not get the indexing, 
> because the Cobol
> copy libraries don't contain that information.
> 
> Regards,
> 
> Christina Hasse
> ADT North American Technical Manager
> COGNOS CORPORATION
> christina.hasse@cognos.com
> 425 N. Martingale Road, Suite 600
> Schaumburg, IL  60173
> Office:  847 - 285 - 2905
> Cell:  847 - 612 - 6854
> 
> 
> -----Original Message-----
> From: Edis, Bob [mailto:BEdis@usbnc.org]
> Sent: Tuesday, June 11, 2002 1:09 PM
> To: PowerHouse List (E-mail)
> Subject: RE: Upgrade questions
> 
> 
> What is PHIntegrator?
> 
> -----Original Message-----
> From: Hamilton, Allison [mailto:Allison.Hamilton@Cognos.COM]
> Sent: Tuesday, June 11, 2002 11:20 AM
> To: 'Johnson, Harold A EDUC:EX'; 'powerh-l@lists.swau.edu'
> Subject: RE: Upgrade questions
> 
> 
> VMS symbol and logical support has been in 8.xx for awhile.  
> POW dictionary
> support is in 8.30 and above. PowerHouse 8.30 supports both 
> PDC and POW(PHD)
> dictionaries. There was a list posted here awhile ago of all 
> the VMSisms
> that we ported into the 8.30 code stream from the 7.10 one.  
> We ported over
> as much as we could find with the exception of AllInOne and 
> RMS Journalling
> support and PhIntegrator.  PHIntegrator is currently under 
> investigation for
> inclusion.  I think that you will find that PowerHouse 8.30 
> is much more
> OpenVMS friendly than 8.20 was.  There are some differences 
> in behaviour,
> and we have documented as many of those as we know of in the 
> Release Notes
> for 8.30, for those that were a concern we have provided an 
> option to get
> the 7.10 behaviour in 8.30 if needed.  
> 
> If you are supported, you should be receiving 8.30D in the 
> near future, if
> you have not already, and you can read the Release Notes to get more
> information.
> 
> -----Original Message-----
> From: Johnson, Harold A EDUC:EX
> [mailto:Harold.A.Johnson@gems1.gov.bc.ca]
> Sent: Tuesday, June 11, 2002 12:06 PM
> To: 'powerh-l@lists.swau.edu'
> Subject: RE: Upgrade questions
> 
> 
> What about VMS symbol support; POW dictionary support; etc...?  We are
> currently using 710g1 because these functions were lost in 
> the so-called
> "improved" version of PH.
> 
> 
> -----Original Message-----
> From: Hamilton, Allison [mailto:Allison.Hamilton@Cognos.COM]
> Sent: Tuesday, June 11, 2002 6:40 AM
> To: 'Hoppe, Eric EP'; 'powerh-l@lists.swau.edu'
> Subject: RE: Upgrade questions
> 
> 
> PowerHouse 8.30x is built on OpenVMS version 6.2 and 
> certified against 7.2.
> Mailbox support is in 8.30x and above.
> 8.40x is built against OpenVMS 7.2
> 
> -----Original Message-----
> From: Hoppe, Eric EP [mailto:Eric.Hoppe@steelscape-inc.com]
> Sent: Monday, June 10, 2002 11:37 AM
> To: 'powerh-l@lists.swau.edu'
> Subject: Upgrade questions
> 
> 
> All-
> 
> We currently have: OpenVMS 7.1, UCX Ver 4.1 - ECO 9 on an 
> AlphaServer 4000
> using PH 7.10G1.  Our current setup is working great, but we 
> are starting to
> get hints from Compaq it is time to upgrade.
> 
> I am under the impression in order to go to PH 8.x we need to 
> upgrade to UCX
> 5.  I am also under the impression that UCX 5 does not support the RMS
> mailbox function which we use heavily.  I also think PH 8.x requires a
> higher ver of operating system.
> 
> Before I start opening trouble tickets with the vendors, I 
> thought I would
> fish out here in the ether for comments from anyone who has 
> been through
> this already.
> 
> Thanks and I hope there is enough info in this msg.
> 
> ---ehops
> 
> Eric Hoppe
> Steelscape, Inc.
> Senior Systems Analyst
> 360.673.8247
> 
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to 
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" 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.
> 
> 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.
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to 
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" 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" 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.
> 
> 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.
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to 
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" 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" 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.
> 
> 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.
> 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to 
> powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" 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.
>