Hi all,

Thanks for the responses so far!

I did get a couple of replies along the lines of:

   > You've got to be kidding!!  Do you want to count all the lines of code we
   > have in all of our programs?

(To which I said: No...only the first half, then multiply by 2  :)

Actually, if most of your source code is in one group, you could do:
   :LISTF @, 2
and add the EOF columns.

Bob asks:
> We keep our source code in 'C' or 'SPL' groups in each account.
> Anyone have a way to count number of lines in all files in all
> these groups?
> MPEX is available.

Here's an MPEX LISTF setup that will do the job, courtesy of
Michael Hensley:

   First, create a file named linetot.listf.vesoft that contains:

   ---cut here---
   for rfile in mpexfileset
      alreadysorted (account:8, group:8)
      onbreakbefore 1
         begin
            writeln(" Account: ",account:8);
         end
      onbreakafter 1
         begin
            writeln(" ",account:8," total: ",
               total(1,1):8," files ",
               total(1,EOF):8, " lines ");
            writeln(" ");
         end
      onbreakafter 2
         begin
            writeln("    ",group:8," total: ",
               total(2,1):8," files ",
               total(2,EOF):8, " lines ");
         end
   finally
     writeln("    Grand Total: ",
       total(0,1):8," files ",
       total(0,EOF):8," lines ");
   ---cut here---

   Now you can do something like this:

   %listf @[log in to unmask]@[log in to unmask],linetot
    Account: FOO
       C        total:        1 files       40 lines
       SPL      total:        1 files       26 lines
       COBOL    total:        2 files       83 lines
       PASCAL   total:        1 files       43 lines
    FOO      total:        5 files      192 lines

       Grand Total:        5 files      192 lines


But...I thought it might be useful to indicate why I'm surveying...

I'm looking for rough estimates, trying to gather evidence to show
HP that there's interest in the user community to:

   1) improve support COBOL:
        a) continuing optimizer improvements for COBOL/iX;
        b) implement future (current?) COBOL standards;
        c) moving COBOL/iX to HP-UX;
        d) support efficient third-party COBOLs compilers on MPE
           and HP-UX, with COBOL/iX compatibility;

   2) improve support for C/iX (aka: move existing HP-UX C to MPE/iX):
        a) provide missing C functionality (e.g., 64-bit integers)
        b) provide better optimization

      (The MPE and HP-UX C compilers used to be identical ... compiled
      from the same source code.  A few years ago, the MPE version was
      essentially frozen.  Since then, HP-UX C has had new language
      features and two new (and higher) levels of optimization added.)

   3) optionally emit PA-RISC 8000 specific code for COBOL/iX, Pascal/iX,
      and C/iX.  (Potentially significant performance increase)

--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html
--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html