> It's certainly possible to have DSORG=PS,RECFM=U data set that does not
> contain load modules.  I've used them.  I believe it's also possible to
> have DSORG=PO,DSNTYPE=PDS,RECFM=U with content other than load
> modules, but ISPF refuses to recognize this fact.  I don't know whether
> DSORG=PO,DSNTYPE=LIBRARY,RECFM=U can have content other than
> program objects.
Yes, it can. I just ran my IEBDG job that allocated a PDS to allocate a PDSE 
instead, and it gets filled with text data by iebdg without a problem. ISPF 
does NOT support editing recfm=u data sets, which is clearly indicated in the 
ISPF books. ISPF statistics are *only* supported for fixed or variable record 
format.

This is the root of my first question: Application developers apparently call 
'ISPF statistics' what they see for recfm=u data sets (and most of them have 
never encountered a recfm=u data set that was NOT a load library). I believe 
the data shown by ISPF are stored in the directory entry itself mapped by 
IHAPDS owned by DFP. Unfortunately ISPF itself seems to call these directory 
data 'ISPF statistics', at least in the ISPF user guide(s).

ISPF just *assumes* that any RECFM=U data set is a load module, when in fact it 
isn't. As far as I can see 'real' load libraries always have an lrecl of zero. 
Which ISPF does not test. When I use a RECFM=U data set in ISPF (with LRECL 
other than zero), I get 'browse substituted' on any edit attempt.

> It has been announced that in 2.1 Rexx EXECIO will support RECFM=U.
> When we get 2.1 I'll need to experiment to discover the restrictions.
I believe what that means is that execio will make sure that the data in the 
directory entry IHAPDS are filled in correctly for a recfm=u data set, too. I 
do NOT believe that mixing of load modules and data members will be possible.

>ISPF might use this information to format the headers of
>the member list. 
No. For fixed and variable length records in a PO data set the user field of 
the directory entry IHAPDS points to the ISPF statistics, which can be 30 or 40 
byte long. They are mapped by ISPDSTAT and owned by ISPF. As I said before, 
ISPF clearly states that it does not maintain PDF statistics for recfm=u data 
sets. I also found some references to 'non-pdf form of statistics'. I'd dearly 
like to know who writes those (well, other than a dedicated program using STOW 
to put *something* into the user field).

Does anyone have an answer for my second question: How does the version in the 
pdf statistics get incremented (other than by some form of the VERSION command)?

Barbara

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to