Re: ISPF list data set attributes?

I forgot to show what it looks like in my ISPVCALL output

Edit Backup Outlist
Block Size........ 13,680 Block Size........ 13,566
Primary blocks.... 40 Primary tracks.... 200
Secondary blocks.. 200 Secondary tracks.. 100
Record Length..... 133
SuperC Pgm interface..... YES
OUTDD Block Size.. 0 Profile Blk Size.. 0
DELDD Block Size.. 0 Stmts Block Size.. 0
List Primary...... 50 Update Primary.... 15
List Secondary.... 100 Update Secondary.. 30
Unit name........... DISK ICF printer support. NO
Use unit for TMP ds. NO PCF being used...... NO
Use UADS only....... A
Max. split screens.. 8 Check exp. dates.... YES


Lizette


I just tried to print a data set list from "ISRUDLP Data Set List
Utility". I got:

.-----------------------------------------------------------------------------.
| The listing of data sets was placed in the ISPF list data set. Lines have |
| been wrapped because the logical record length is less than 127 for RECFM F |
| or 131 for RECFM V. |
'-----------------------------------------------------------------------------'

o There's no code associated with this message. Is it supposed to
be "self-explanatory"? I know the modal reaction of this group
to self-explanatory messages. Or do I need to choose an option
to display the code?

o HELP key tells me nothing useful.

o Panel 0 doesn't show anything of interest.

o "z/OS V1R7.0 ISPF User's Guide Vol I" "1.5.9.3 Processing the Log
and List Data Sets" makes some passing mention of "preallocated
data sets", but doesn't describe how to preallocate them.

How can I cause the listing data set to be allocated with more
suitable attributes? If I can do this, what's the maximum
permissible? Will it cause problems if I allocate with LRECL(1000)
and seldom again worry about wrapping?

(The actual allocated attributes were RECFM=FBA,LRECL=121, clearly
smaller than ISRUDLP needs.)

Thanks,
gil


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.

Relevant Pages

  • : What happening on SMS managed volumes counts?
    ... IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET ... IDC3020I UNABLE TO ALLOCATE SPACE ON USER VOLUME ... MAXIMUM CONDITION CODE WAS 12 ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • LISTDSI and RENAME (was: ... alias in Rexx)
    ... Will RENAME work with a tape data set, ... If I allocate with overriding DCB parameters, ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: ALLOCATE, LISTDSI, and dangling catalog entry
    ... You can allocate a dataset which does not really exist on ... either through the catalog or by specifying UNIT and VOL. ... allocate a data set without really allocating a data set. ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)
  • Re: ALLOCATE, LISTDSI, and dangling catalog entry
    ... I managed do delete a data set ... allocate the data set, ALLOCATE apparently succeeded with RC=0, ... For IBM-MAIN subscribe / signoff / archive access instructions, send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html. ...
    (bit.listserv.ibm-main)
  • Re: Invalid DSN in Catalog
    ... CVAF seems to behave similarly when the VTOC is ... I believe you can only allocate a data set that has a "valid" ... For IBM-MAIN subscribe / signoff / archive access instructions, ...
    (bit.listserv.ibm-main)