1. RE: X-Ref software for BPCS (Debra Ivey)

Using one X-ref package or the other...... 

They will all have to cope with AS/SET renaming fields and creating piles of
internal work variables. Please let me know if any of the X-ref packages
does this without intervention.

And remember BPCS LX is NOT "everything back in RPG"!! The base source code
is still the one generated from AS/SET - and then SSA put BMRs in the
generated RPG-code manually!

Poor souls!! Some of us are so old we can remember when SSA "lost" the
AS/SET source for ORD570 and we had to put client modifications into the
code generated..........:-(

Cheers
Bent Nielsen



-----Original Message-----
message: 1
date: Mon, 5 Dec 2005 16:36:23 -0500 
from: Debra Ivey <divey@xxxxxxxxxxx>
subject: RE: [BPCS-L] X-Ref software for BPCS

One warning I will throw out is that you are on a version of BPCS that is
all AS/SET source code.  This adds some complexity to using x-ref tools like
Hawkeye's Pathfinder because they seem to expect RPG source code.  We didn't
want to generate RPG from all of our AS/SET code, so we use Pathfinder for
our custom code and non-BPCS packages.  For straight BPCS x-ref info we use
the Access database x-ref that you can download from SSA.  I'm not sure at
what version they started creating those x-refs.  We are on 8.2.  This
problem should go away with LX, since everything will be back in RPG (except
for what's in Java.  What will we do then? :)

Debbie
 


========================================================================This 
email, its content and any files transmitted with it are intended solely for 
the addressee(s) and may be legally privileged and/or confidential. Access by 
any other party is unauthorised without the express written permission of the 
sender. If you have received this email in error you may not copy or use the 
contents, attachments or information in any way. Please delete it and contact 
the GET Business Systems Department via the email address mis@xxxxxxxxxxxxx 
Internet communications are not secure unless protected using strong 
cryptography. This email has been prepared using information believed by the 
author to be reliable and accurate, but GET PLC makes no warranty as to 
accuracy or completeness. In particular does not accept responsibility for 
changes made to this email after it was sent. 
========================================================================