So,
don't try to allocate a file larger than 16MB with a units of "Bytes",
but use a space unit more appropriate to the size of the file --e.g.,
specify space units of "MB" and a primary of 100. So long as 5%
over-allocation because "MB" is interpreted as MiB is tolerable, you
can't get much more intuitive than that; and odds are the 100 MB
requirement is probably an approximation anyhow, and may or may not be
taking into account that not all the space within the HFS will actually
be usable for user data.
If you really needed as close to a true 100 MB allocation as possible
but not under, you could use a primary allocation of 96 "MB" (96MiB =
100,663,296 B), or get even closer with a primary of 97656 "KB"
(97656KiB = 100,000,768 B), but admittedly these values are less
intuitively obvious.
The syntax used to define files doesn't limit file size to 16MiB-1 but
to 16MiMiB - 16MiB, or close to 16TiB. The limitation you saw is only
on the size of the numeric value specified, not on the file size itself.
I think you will hit other constraints long before this syntax
constraint becomes an issue.
The corresponding form in JCL would be "SPACE=(1,(100,??)),AVGREC=M".
In JCL, the SPACE "average record size" of "1" when used with AVGREC and
record count is only used to determine the total byte requirement of the
dataset and doesn't need to have any relationship with actual records or
blocks present in the dataset (which in the case of an HFS is just a
series of 4 KiB blocks).
Another JCL possibility I would be tempted to try would be
"SPACE=(1000000,(100,??)),AVGREC=U" to get a true 100MB allocation; but
I can't recall ever testing this, so there might be some constraints on
"avg record length" in the SPACE parameter that might reject this. I
don't believe there is any equivalent under ISPF 3.2 to request this
kind of allocation (you can't independently specify the SPACE avg record
size, and 1,000,000 is definitely too large to specify as an actual
record size).
Paul Gilmartin wrote:
On Sun, 5 Aug 2007 13:58:17 -0400, Pinnacle wrote:
----- Original Message -----
From: "Paul Gilmartin" <[EMAIL PROTECTED]>
Sent: Sunday, August 05, 2007 9:46 AM
Help me get this straight again:
If I want to allocate a 100,000,000 byte HFS (round numbers),
what space parameters should I supply in ISPF 3.2? (The more
intuitive the better.)
Similar question for JCL.
Allocation unit: bytes, amount 100000000, TYPE HFS.
Alas, no luck:
Menu RefList Utilities Help
??????????????????????????????????????????????????????????????????????????????
ISRUAASE Allocate New Data Set Value out of range
Data Set Name . . . : SPPG.WOMBAT.HFS.ECC
Management class . . . (Blank for default management class)
Storage class . . . . (Blank for default storage class)
Volume serial . . . . (Blank for system default volume) **
Device type . . . . . (Generic unit or device address) **
Data class . . . . . . (Blank for default data class)
Space units . . . . . BYTE (BLKS, TRKS, CYLS, KB, MB, BYTES
or RECORDS)
Average record unit (M, K, or U)
Primary quantity . . 100000000 (In above units)
Secondary quantity ????????????????????????????????????????????????
Directory blocks . ? Enter a numeric value between 0 and 16777215 ?
Record format . . . ????????????????????????????????????????????????
Record length . . . . 0
Block size . . . . . 0
Data set name type HFS (LIBRARY, HFS, PDS, LARGE, BASIC, *
It's utterly bizarre that in this age when I can buy a 500 GB disk for $149
at CompUSA, IBM's "flagship" mainframe operating system won't let me simply
create a file larger than 16MiB-1.
I created it with a 10MB primary and 2MB secondary allocation which will get
me there, but I deem that a shabby circumvention.
-- gil
...
--
Joel C. Ewing, Fort Smith, AR [EMAIL PROTECTED]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
