concurrent versions

[John Pearce]

Kevin O'Sullivan wrote:
>
>Obviously, we'll need to be able to discriminate which version of PH we are
>using at any given time, but that shouldn't
>be a great problem.

I still find it necessary to switch between PH 6.09, 7.29, and 8.19.  I
have created a set of command files (not UDC) in PUB.COGNOS to manage the
user level UDC.  I have SETCAT6, SETCAT7, SETCAT8, and SETCAT (really
should be RESETCAT) command files.

Each SETCAT# contains SETCATALOG <udcfile>;DELETE statements for each PH
version and for Architect.  That's a total of five delete's.  Then
SETCATALOG <udcfile>;APPEND for the PH version number as indicated by the #
character.  For 6 and 7, there is also a SETCATALOG <arcudc>;APPEND
command.  The SETCAT file has only the DELETE lines which removes all the
PH UDC's from the user level catalog allowing the account level to control
the PH version.

The command files provide the flexibility to change the user level catalog
no matter which account I am logged into.  Hopefully this won't be
necessary after March 31, as that's the target to be rid of 6.09 and 7.29
code.


------------------------------------------------------------------
John Pearce  <jpearce@rmi.net>       | Bethesda Management Company 
Speaking for only myself             | Colorado Springs, CO  USA
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.