PH Cleanup Routines

[georgia miller]

Peter,

What we use to identify code that could cause problems when going to a new 
release of Powerhouse, is MPEX a utility program from VESoft Inc.  With this 
program we can use the PRINT command to search a set of files (@.source) for 
a litteral value ("DATE"), then print each occurence of the value.  Only 
files that contain that value are selected to print.  I usually print 5 lines 
before and after the found value.  Then I check the list to see what source 
may need to be changed to bring the source code in line with the Powerhouse 
version changes.  I am currently using the MPEX print command to find the 
date issues to bring our systems up to year 2000 compliance.

An example of the MPEX command is:

:MPEX
>FILE LP;DEV=LP
>PRINT @.SOURCE.@ &
  (FSEARCHEXP ("'DATE' OR 'date'")>0); &
  SEARCH=CL "DATE"; &
  OUT=*LP;PAGEHEAD;NUM;CONTEXT=-5,+5
>EXIT

Since MPEX is a machine hog (HP3000), we only run these in a job in the E 
que.
______________________________________________________________________________
_
From: Watt Peter (Van) on Tue, Feb 24, 1998 7:29 PM
Subject: PH Cleanup Routines

>Not sure if this has made it on this list server so I will pose the
>question.

>Does anyone know of, or developed some PH cleanup routines.  For
>example, something to identify which internal procedures, temps and
>defines that are no longer referenced in the PH code.  I think we are in
>the same boat as many other companies, that our source has continued to
>grow over the years without ever having an efficient way to cleanup the
>code.  Someone recently suggested to me a cross-reference utility, that
>would help.

>My thoughts are that this would require some sort of pre-compiler that
>could be used to create the cross-reference document/utility.  Think
>Cognos would be willing to part with the compiler?  Didn't think so...  

>So, has anybody been adventurous enough to try this?

>Peter Watt
>peter.watt@artioslink.com