home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!mips!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: bob@camb.com (Bob Tinkelman)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: Request for minor changes to installation procedure
- Message-ID: <01GMP0R17ASQ90MTNY@camb.com>
- Date: 23 Jul 92 02:06:12 GMT
- Organization: Cambridge Computer Associates, Inc.
- Lines: 11
- Resent-Date: 22 Jul 1992 22:06:12 -0400 (EDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Cc: ipmdf@INNOSOFT.COM
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-Id: <01GMOUN39MSI94DO0Q@INNOSOFT.COM>
- X-Vms-To: IN%"SMITH@MCCLB0.MED.NYU.EDU"
- X-Vms-Cc: IN%"info-pmdf",TINKELMAN
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- SMITH@MCCLB0.MED.NYU.EDU writes:
-
- > Now that we are in nit-pick mode, I guess it is fair to ask again that the
- > PMDF logicals, like those that provide the Organization name and the periodic
- > job frequency be preserved in the PMDF_STARTUP file.
-
- I *never* edit pmdf_startup.com. I create a second command file called
- pmdf_startup_local.com that contains any local customizations (including
- setting the organization and timezone). At startup it is executed right
- after pmdf_startup.com. I switched to this scheme after I continued to
- forget to deal with this issue at the end of an upgrade.
-