Fix .p and .w calls

[jdpjamesp]

Our current file structure means that we have the following directories in our PROPATH

SOURCE
SOURCE/WCODE
SOURCE/ICODE
SOURCE/PCODE

etc.

This nested structure of folders is causing us some issues, particularly in PDSOE (11.2.1). So I've started to tidy things up to include the subdirectory in the call, meaning we can eventually do away with the nesting. The icode is easy to sort as everything fails to compile as soon as you remove the propath entry making it easy to spot and fix.
Is there a way I can narrow down all .p and .w calls easily or is it just a case of searching for "RUN *.p" and trawling through?
Windows 7.

 

[tamhas]

I would imagine a query on ABL2DB would give you the needed information ...

 

[jdpjamesp]

Yeah I guess it would but I've still not finished getting that working.

 

[tamhas]

Well, new motivation then!

 

[jdpjamesp]

True enough... DBA Bootcamp in Bracknell next week, so maybe after that.

 

[tamhas]

Lots of new stuff in there for you when you get to it.

 

[TheMadDBA]

If you aren't using RUN VALUE(program.p) you can just compile all of your code with XREF and look for the RUN references, ABL2DB does that kind of stuff for you though

 

[tamhas]

Yes, and the point of the ribbing was that James has been working on implementing ABL2DB ... in fact, a number of the changes and enhancements I have made have been because of issues with his code base. It is just that day to day work pressures keep getting in the way!