PHD

[Hamilton, Allison]

I'd like to clarify something here.  On VMS, there is no difference between
the resulting format of a PHD created or a PDL created dictionary.  They
create the same dictionary, just using two different methods.  The PHDMaint
method allows you to modify the dictonary while it's being used, which can
be a very questionable activity, but is allowed. 
In PDL, if you have done a SETDICT to the production dictionary before
recompiling, yes, you will get a file conflict, which is very valid, as it
takes time to create all new 5 files and someone using the dictionary could
get a mis-match of files in the process.  However, simply create the
dictionary somewhere else and move all 5 files into the production area at
once, and you have no conflict. Even when we used PHD as a maintenance
utility for our production dictionaries, we never actually modifed the live
dictionary while it was being used.  We modified the master dictionary in
the development area, and copied the result into the production area when we
were done and tested.  This is usually a much safer scenario for all
concerned, providing a consistent, stable environment.   Just my 2 cents
worth.
Allison Hamilton

> ----------
> From: 	Chris Sharman[SMTP:Chris.Sharman@ccagroup.co.uk]
> Sent: 	Thursday, November 19, 1998 3:42 AM
> To: 	Bob.Deskin@cognos.com
> Cc: 	Chris.Sharman@ccagroup.co.uk; powerh-l@lists.swau.edu
> Subject: 	RE: PHD
> 
> >PhD and PDL are the same regarding when you must recompile screens,
> reports,
> >and runs. If you add or change a file to a PhD dictionary (via the
> >appropriate screen), or to a PDL dictionary (by adding the syntax and
> >recompiling the dictionary), you still have to recompile any screens,
> >reports, and runs that use that file.
> >
> >In your example of adding an item to an existing file, you would have to
> >recompile any screen, report, or run that used that file. And again, this
> is
> >no different for PhD or PDL.
> 
> This isn't true: changes that don't affect the length of records don't
> require a recompile. If a field becomes obsolete, and I rename it to
> obsolete-garbage, I don't have to recompile anything that wasn't using it.
> When I reuse it, again I don't have to recompile anything which doesn't
> use it.
> This saves a lot of work, and hopefully will still be the case with PDL,
> even with a full re-compile from source.
> 
> Someone mentioned that you can't PDL a dictionary while it's in use: I
> think
> that's why we never use it.
> 
> If PHD is getting dumped, how about putting the sources in the public
> domain,
> with appropriate disclaimers. That way those of us really fond of it can
> put
> the work in to keep it going as freeware.
> ______________________________________________________________________
> Chris Sharman			Chris.Sharman@CCAgroup.co.uk
> CCA Stationery Ltd, Eastway, Fulwood, Preston, Lancashire, PR2 9WS.
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> =
> 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.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
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.