Igor Micev wrote:
> Hi
>
> I know that there are commands like truss, tusc. I tried them and they
> work well, but did't manage to apply them on a jBase commands. I
> really don't know how to do that.
> Anyway, I want to parse routines' code and when i meet T24 routines
> like EB.ROUND.AMOUNT(), CDD(), F.WRITE/READ() ... to be able to get
> all the tables in the system that are checked.
>
>
To do this from source code would be rather more difficult than you
expect. For instance I doubt that you could reliably do this with static
analysis and flow analysis between subroutines in jBC is essentially a
global analysis for which you need source code for everything, or at
least a reliable description of the interface. As a somewhat contrived
example designed to point out various cases, think of things like this:
SUBROUTINE(i1, s2)
BEGIN CASE
CASE i1=1
fName = s2[1,1]:"f_":i1
CASE i1 =7
fName = s2[1, 4]:"f_":i2
CASE i1 = 88
CALL calcFname(fName, DATE(), s2)
DEFAULT
fName = s2[1,i1]:"FB"
END CASE
CALL F.OPEN(fName, ......
The best you could do is guess. However, with truss or perhaps the jBASE
jprof related commands, you can pick up the actual file names at
runtime, and the trace output can easily be processed with awk or even grep.
Jim
--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---
