Re: SQL query to know lines of code for all the programs and it's associated modules

Hi,

Thanks much for these inputs.

For "DSPFD will definitely report the number of records in a source member"

Could you please mention exact full command for the same (DSPFD) and point
out in which field of outfile this information could be found exactly?


Thanks much...

On Wed, Jun 28, 2023, 22:02 Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 6/28/2023 3:49 AM, tim ken wrote:

For This I mean count of the lines of all the source members which are
compiled successfully and whose objects are also present with respect to
their source code.

There is no simple way to do this.

I tried both DSPFD and DSPFFD both to an OUTFILE() but could not find

any

such field in their outfiles which shows the total number of lines of

code

for a particular source member.

DSPFD will definitely report the number of records in a source member,
but SYSPARTITIONSTAT will do so as well.

For comments i did not want to make it much complicated ,I simply meant
commented lines irrespective of source member 's attribute type and

either

in continuation or in multi lines and for blank lines
yes of course they are also counted even if they are blanks because blank
line also occupies a sequence number if we browse a particular member's
source code.However there could also be such source members for which
sequence numbers are shown in points like '1234.56' for such I am also

not

sure how to count them in a complete number.

This is already quite complicated.

There is no attribute in a line of source code that indicates whether a
particular line is a comment or not. You yourself would need to write
that code.

But is it possible to include all of IBM's
proprietary system programs as well here?

No, IBM does not supply source code.
Nor do many 3rd party applications.
All you get is object code.

This statistics is required to have a complete overview of how complex a
particular IBM i environment is?

If my manager were to say something like this to me, I would mention:

Triggers
RCAC
SQL (think UPDATE vs SELECT, MERGE vs UPDATE)
Constraints (think error handling/reporting)
Web services
PASE/Open source
Library lists
SQL procedures and functions
3rd party applications
Change management (think source code at different levels/versions in
different libraries)
Data imports/exports (think utilities like CPY vs CPYFRMSTMF)
IBM utilities (Query/400, STRQM etc)
Commitment control
Auditing (think HIPAA, DCI, Sarbanes-Oxley, GDPR)
Size of the database
Transaction rate
Number of end users (don't forget the web)

I am deeply curious what you and your management will do with a system
wide complexity metric. None of my managers ever had an action plan - it
was always a matter of curiosity. In which case, the less work I had to
put into it, the better for everyone.

--
--buck

http://wiki.midrange.com
Your updates make it better!


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.