It may not be your ACS routines.
I can reproduce this behavior on a "test" LPAR when allocating a PDSE
in ISPF 3.2 with RECFM=U. I get the warning message to either DELETE or KEEP
the dataset. If I keep it, I can't copy Load modules or program objects into
then newly created D/S.
If I allocate the PDSE with either a Fixed or Variable RECFM, then
BLKSIZE of 0 (or BLANK) is accepted. In the cases of RECFM = FB or VB, SDB
produces an optimum block size for my device type.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Paul Gilmartin
Sent: Thursday, January 12, 2017 4:47 PM
To: [email protected]
Subject: Re: SDB and Program Object Library
On 2017-01-12 14:23, Allan Staller wrote:
> Allocation
>
> Do these ACS routines operate
> o at data set creation?
> o at OPEN?
> o Both?
>
"Allocation" is dismayingly ambiguous. But I assume you mean allocation as in
DISP=NEW ratner than allocation as in DISP=OLD.
Data Set Utility tells me:
Data Set Name . : User.LOADE
Specified data set has zero block size.
The data set allocated contains inconsistent attributes as indicated by the
message displayed above. Prior to allocating a managed data set, ISPF cannot
always determine if the attributes are inconsistent. The data class used when
allocating the data set may contain inconsistent attributes, or the attributes
you specified on the allocation panel may conflict with those defined in the
data class. This panel gives you the opportunity to delete this data set. If
you keep the data set, other ISPF functions, such as edit, move, or copy, may
not be able to use the data set.
But I keep it. Then Data Set List says:
DSLIST - Data Sets Matching User.**.LOAD* Row 1 of 9
Command ===> Scroll ===> CSR
Command - Enter "/" to select action Dsorg Recfm Lrecl Blksz
-------------------------------------------------------------------------------
User.LOADE PO-E U 0 0
User.LOADU PO U 256 19069
and Move/Copy Utility says:
COPY From User.LOADU Invalid block size
Command ===>
To Other Partitioned or Sequential Data Set:
Name . . . . . . . LOADE
Volume Serial . . . (If not cataloged)
\u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510
\u2502 Block size of data set must not be zero. \u2502
F1=Help F
\u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518
ard F8=Forward
... so, why doesn't SDB fix it?
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
