I'm using this post to try to answer another related post that I just can't find right now (my desktop Linux system crashed, so I am forced to use a webmail interface... It is a pain, but it kinda works).
There was a question about why one is doing this external to ISPF so that one doesn't have the stats. Well, if you are using Panvalet and want to get the stats to ISPF, you will have to make them up. Panvalet does have an off load, but if you use it, you get NO stats. If you want stats you have to use a PAN#2 execution and tell it that you want the directory info with the "extdir" option. Now you get to take that output and massage it into ISPF stats info. You can do that for each member (as it comes out in member order). And there is some info that matches what ISPF does and some info that just does not. Then I used LMMSTATS to make it all happen. I've just been down this road (pan to PDSE). And I think the same problem holds true with Librarian and if one is migrating from DOS to z/OS with ICCF (been years since I've touched that one). Now let us assume that you have been doing development off mainframe and you want the stats from the file system where you are importing from.... These are just a few reasons why one would need to "make up" stats. Regards, Steve Thompson --- [email protected] wrote: From: Steve Horein <[email protected]> To: [email protected] Subject: Re: [IBM-MAIN] Running ISPF's 3.5 utility from a clist Date: Sat, 15 Sep 2018 20:03:04 -0500 +1 for LMMSTATS On Fri, Sep 14, 2018 at 12:24 PM Jim Ruddy <[email protected]> wrote: > Dave, > > Do you have the stats already from the generation of the members? Maybe I > am missing something but is there a re reason you cannot use LMMSTATS to > set the statistics for each member? > > Jim Ruddy > Retired ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
