-- Original Message -
From: "MAJ Programming" <[EMAIL PROTECTED]>
To:
Sent: Friday, June 29, 2007 7:38 PM
Subject: Re: [AD] [U2] Basic developments "reverse engineering" tool ?
While your examples are not false, they're hardly true either. In my many
years of MV
e code was
> written too.
>
> My 1.5"
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Norman Morgan
> Sent: Friday, June 29, 2007 9:02 AM
> To: u2-users@listserver.u2ug.org
> Subject: RE: [AD] [U2] Basic developments
TECTED]>
To:
Sent: Friday, June 29, 2007 9:20 AM
Subject: Re: [AD] [U2] Basic developments "reverse engineering" tool ?
> > One of my clients has procs like this:
> >
> > HRUN BP SOP1500
> > STON
> > HORDER<
> > HCUSTOMER<
> > HPRO
iddlefield Road
Redwood City, CA 94063
Tel 650-780-7087
Fax 650-556-9204
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stevenson,
Charles
Sent: Friday, June 29, 2007 7:28 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [AD] [U2] Basic de
f Of Norman Morgan
Sent: Friday, June 29, 2007 9:02 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [AD] [U2] Basic developments "reverse engineering" tool ?
Joking aside, that looks almost like something written by someone who
was accustomed to writing mainframe COBOL where actual file ass
If I recall correctly, SoftWhere handled that sort of thing.
I do remember seeing it pick up subroutine's uses of files where the
file variable was passed as an argument from the calling program.
-Original Message-
How does it work with parameter driven code.
One of my clients has procs l
uot; as a COBOL programmer.
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Timothy
> > Snyder
> > Sent: Friday, June 29, 2007 8:21 AM
> > To: u2-users@listserver.u2ug.org
> > Subject: Re: [
black dress.
===
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Timothy Snyder
> Sent: Friday, June 29, 2007 8:21 AM
> To: u2-users@listserver.u2ug.org
> Subject: Re: [AD] [U2] Basic developments "rev
> One of my clients has procs like this:
>
> HRUN BP SOP1500
> STON
> HORDER<
> HCUSTOMER<
> HPRODUCT<
> HVENDOR<
> P
>
> whereby the program (BP SOP1500) has the corresponding INPUT statements
for
> the file names and opens them as F1, F2, F3 which is a real bear when
> reading the code.
Wow -
That's very difficult to trap.
Mark
It's a valid point and a common scenario.
I've taken two approaches in the past:
1. Dynamic analysis
This replaces certain constructs in the source code automatically with calls to
subroutines or external functions that update the maps in real time. So for
From: "Laura Hirsh" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 28, 2007 2:26 PM
Subject: [AD] [U2] Basic developments "reverse engineering" tool ?
> The type of Technical Documentation that Susan mentions is a part of
> DocuSys! Not only does DocuSys comb through
The type of Technical Documentation that Susan mentions is a part of
DocuSys! Not only does DocuSys comb through basic code, and also the gamut
of SB+ bits, but it sends it to MS Word - nicely formatted, with a table of
contents, pagination, Styles, etc. Options include both User Documentation
(for
We have a series of programs that will dissect a U2 application and create a
series of documentation databases. We have some canned reports or you can
simply use LIST to generate your own reports. The application is available
for installation on one of your systems so you can maintain this level
13 matches
Mail list logo