|
View previous topic :: View next topic
|
| Author |
Message |
socker_dad
Active User
Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA
|
|
|
|
I'm using File Aid 9.3.1.
Using the online panels, I can go into Entended Utilities (Option 3), Library Utilitiy (Option 1) and leaving the panel Option blank, get an excellent list of all the members in the PDS, along with the Create/Last Modified Dates, Size, ID, etc.
However, when I try to use the batch option on the Library Utility (Process Option = B), it will not accept blank as a valid entry (or, actually, any of its listed options), because this is a PDS of source code (COBOL, Assembler, etc.).
I read through the Batch manual and played with some variations on LIST and LMODDIR to no avail. These are great if I want a listing of the contents of the PDS members - all I want is this:
| Code: |
------------------------------------------------------------------------------
S NAME RENAME VV.MM CREATED LAST MODIFIED SIZE INIT MOD ID
CYO500 08.01 98/09/23 12/09/04 15:59 652 3914 1 TSO6077
CZS951 03.06 96/10/08 07/04/24 15:32 478 368 0 TSOPJC
HAB501 64.80 99/05/04 07/04/13 08:21 973 973 0 TSOPJC
HAB502 64.75 98/01/19 07/04/03 14:05 1148 959 0 TSOPJC
HAE000 64.77 98/10/02 07/04/24 15:32 400 400 0 TSOPJC
HAE010 64.72 98/04/14 07/04/24 15:32 1395 1395 0 TSOPJC
HAE020 64.73 98/04/14 07/04/24 15:32 1473 1473 0 TSOPJC
HAE021 64.72 98/04/14 07/04/24 15:32 1842 1842 0 TSOPJC
HAE030 64.72 98/04/14 07/04/24 15:32 430 430 0 TSOPJC
HAE031 64.72 98/04/14 07/04/24 15:32 1890 1890 0 TSOPJC |
...in a dataset so I can move it to the PC for a report I am working on. No, screen printing to a file isn't going to cut the mustard: there are over 300 PDS files with thousands and thousands of programs.
Any suggestions? |
|
| Back to top |
|
 |
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
ever thought of using SAVE <listname> while in a standard ISPF member display,
instead of having to learn how to use a tool that
though your company
paid money for the rights of use
never bothered to train the personnel that use it. |
|
| Back to top |
|
|
socker_dad
Active User
Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA
|
|
|
|
Ouch!
Of course there is no training! That would require a "training budget"!
I'll give the "save" a try and report back. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
300 PDS, sorry missed that. manual will not suffice.
usually I use IEBPTPCH to print directories, followed by a sort to reformat the output.
i set it up as a proc,
and then invoke the proc for each pds.
i take a list of all the pds's,
format the pds dsn as a symbolic on an exec statement,
then run the job.
output of sort is always mod'ed onto the last output.
here is a link to EIBPTPCH
publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2u111/9.7.8?SHELF=EZ2ZO108&DT=20020722161259&CASE=
hope that solves your issue, and sorry about the pain that i inflicted.
I have to admit, that your's was the last of several,
'i can not make this work, and google will not find the answer'.
so, i apologize for my lack of manners,
though it does make sense to have some type of training..... |
|
| Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009
Posts: 1306
Location: Vilnius, Lithuania
|
|
|
|
| Try invoking mlrexx.txt by Doug Nadel in batch. You may have to update it to handle extended statistics. |
|
| Back to top |
|
|
socker_dad
Active User
Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA
|
|
|
|
I tried the IEBPTPCH utility and basically got output similar to the File-Aid job: a listing of every program line - not just the directory information.
So I stumbled into the REXX suggestion (I don't know REXX from succotash!) from Prino and finally was able to generate the listing I wanted, but only on PDS libraries with my HLQ.
So far, this is the most workable solution, so I'll keep stabbing at the REXX code. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
| a listing of every program line - not just the directory information. |
to only get directory info, the dcb for the pds must be correct,
and the typorg=ps must be there in the sysin.
i have used this a million times and know that it works.
but, for over 300 pds, would make a job exceed the allowable number of steps,
thus making it a 2 job utility.
have fun with the rexx, which in the case of so many pds's
would probably the easier solution, once you have rexx conquered.
| Code: |
//PRINTDIR JOB ...
//STEP1 EXEC PGM=IEBPTPCH
//SYSPRINT DD SYSOUT=A
//SYSUT1 DD DSNAME=MAIN.PDS,
// DISP=(OLD,KEEP),DCB=(RECFM=U,BLKSIZE=256)
//SYSUT2 DD SYSOUT=A
//SYSIN DD *
PRINT TYPORG=PS,TOTCONV=XE
TITLE ITEM=('PRINT PARTITIONED DIRECTORY OF PDS',10)
TITLE ITEM=('FIRST TWO BYTES SHOW NUM OF USED BYTES',10)
LABELS DATA=NO
/* |
|
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
| Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix
|
|
|
|
| Thanks Robert. |
|
| Back to top |
|
|
socker_dad
Active User
Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA
|
|
|
|
The REXX JCL needed triple single-quote marks (''') on each side of the PDS name due to the parser.
Works great now! |
|
| Back to top |
|
|
|
|
