|
I have the ILEPARSER working for parsing source members with copybooks. Nested copybooks are currently not supported... Anyway I have posted a V5R1 compliant save file on the ftp site & have performed an SVN commit for those using it. I'm planning on adding the module, program & service program API checks to the parser. That way the entire object data will be loaded into a single XML document. If you download the save file, the control file is already populated with the keywords. If you would like to see the output from the parser as it currently stands you can parse a single member using the ILEPARSE command. You can parse an entire source file using the BUILDXML command or parse an entire library using the BLDXMLLIB command. I ran the BLDXMLLIB command over the ILEDOCS library & it parsed the whole thing in 7 seconds in batch mode. Of course larger libraries will take longer but I'm kinda pleased with the results so far. The parser currently loads the XML data into '/tmp/test' directory on the IFS (if the '/test' directory isn't there it will create it. The XML files are named like so: QRPGLESRC_ILEPARSER_RPGLE.xml Ok to heck with it.... Here is the output from parsing the ILEPARSER program source itself. <<qrpglesrc_ileparser_rpgle.xml.txt>> Just remove the .txt from the file to make it an xml file...the mailing list will kill the attachment if it's not a .txt file.... Currently there is a small issue with the "&" sign in the XML data...browsers balk when it hits them. The above file I manually replaced the "&" that is the only change from the original output. Thanks, Tommy Holden
<XML> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/27/2006</value>
</DATE>
<TEXT>
<value>This Program Is Used to parse ILE Source Members For Internal
Documentation. The extracted data is placed into an XML file on the IFS. The
XML file name is constructed by concatenating the Source file name, member name
and member type.</value>
</TEXT>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,IFSAPI</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/28/2006</value>
</DATE>
<TEXT>
<value>This Copybook Contains The IFS API Prototypes, Constants and
Relevant Data Structures</value>
</TEXT>
</COPYBOOK>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,USRSPCPR</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/27/2006 @Author: Tommy Holden</value>
</DATE>
<TEXT>
<value>This Copybook Contains All Prototypes For User Space APIs.</value>
</TEXT>
</COPYBOOK>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,USERSPCHDR</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/28/2006</value>
</DATE>
<TEXT>
<value>This Copybook Contains The Generic User Space Header Information
Data Structure</value>
</TEXT>
</COPYBOOK>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,ILEDOCSPR</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/28/2006</value>
</DATE>
<TEXT>
<value>This Copybook Contains The Prototypes, Constants and Global Data
Structures Use In The ILEDOCSP1 Utility Service Program</value>
</TEXT>
</COPYBOOK>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,RTVCTLVAL</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/28/2006</value>
</DATE>
<TEXT>
<value>This Copybook Contains The Prototypes For Exported Procedures In
the CONTROLSP Service Program</value>
</TEXT>
<TEXT>
<value>Retrieve Control File Values Export Procedure Returns the Value
For The Received Parameters Of Library And Record Type</value>
</TEXT>
<TEXT>
<value>Update Control File Values Export Procedure Receives the Values
For The Update Of KRCONTROL</value>
</TEXT>
</COPYBOOK>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,JOBATTR</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/28/2006</value>
</DATE>
<TEXT>
<value>This Copybook Contains All Data Structures and Prototype For Using
the QUSRJOBI API to Retrieve Job Attributes.</value>
</TEXT>
</COPYBOOK>
<COPYBOOK>
<NAME>ILEDOCS/QCOPYSRC,PGMSTSDS</NAME> <AUTHOR>
<value>Tommy Holden</value>
</AUTHOR>
<DATE>
<value>07/28/2006 @Author: Tommy Holden</value>
</DATE>
<TEXT>
<value>This Copybook Contains The Program Status Data Structure</value>
</TEXT>
</COPYBOOK>
<TEXT>
<value>Main Procedure recieves 3 parameters Qualified Source File Name: 20
Alphanumeric Source Member Name: Source Type/Attribute: 10
Alphanumeric</value>
</TEXT>
<TEXT>
<value>The DataDS data structure is used for parsing the data read in by the
IFS APIs</value>
</TEXT>
<TEXT>
<value>The CtlData data structure is used for processing the Source member
keywords retrieved from the KRCONTROL file via the CONTROLSP service program
module RTVCTLVAL</value>
</TEXT>
</XML>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.