-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
See more than one level deep for the tree visual of JCL #178
Comments
Sort of. If you run your COBOL source code through the CallTree.jar in the mapa/cobol directory, you will get an output file detailing information about each COBOL program. You might also need the DB2zSQL.jar file. The intended use of these delimited output files is they can be processed in any way you like. You could load them into a database and process them from there with SQL or you could just read the files and process those to produce whatever sort of output meets your needs. So, you could process the JCL with JCLParser.jar, then process the COBOL with CallTree.jar, then put the two outputs together in a nice report or tree structure represented in a GUI with code you write. |
Ah this is great thank you! We may try to add this functionality from the csv files output or potentially intercepting the intermediary AST from ANTLR. Re: the docs around -include / -includeList:
These are required flags, so I'm wondering what the purpose of providing these are -- our initial assumption when reading these docs were that it would "resolve" program files and unfurl them under the call site of procs or programs in the csv / tsv output, but that doesn't appear to be happening at first glance / from your response. What does providing these flags do? Thanks again for your prompt replies! |
Those options are for specifying a directory or directories for resolving cataloged procedures and JCL |
Hi,
I am wondering if it is at all possible to see more than one level deep for JCL files? Ie:
Imagining you have a JCL Proc named PROC001 that calls out to another PGM called FORMATPGM:
And the FORMATPGM file looks like the following:
I have provided the
-include PATH.TO.FOLDER.CONTAINING.FORMATPGM
in the command:The output from running this, namely the PROC001.proclib.tsv, looks like the following:
I was anticipating that FORMATPGM's definition would be parsed and unfurled in the tree as well, but it seems as though that may not be supported, at least for this given invocation of the JCL jar. Is there some way to get the parser to output an outtree that resolves the FORMATPGM tree, and any programs IT calls as well?
Thanks in advance!
The text was updated successfully, but these errors were encountered: