Re: Re: Compile and run later
Rick Fochtman <[email protected]>
| Newsgroups | gmane.comp.emulators.turnkey-mvs |
|---|---|
| Message-ID | <[email protected]> |
-------------------------------<snip>----------------------------- On my way to trying this I went to add another program to my linklib, but I got a SD37 abend - looks like I am out of disk space? -------------------------------<unsnip>----------------------------- Not necessarily. You've filled the PDS to where it needs another extent and it's not available. Either your secondary allocation was zero or you've already got 16 extents. All the example allocations via JCL that I've seen here have specified no secondary extents, so that's probably your problem. Send me, privately, the dsname and volser involved and I'll send you a deck to affect repairs. Also send the device type and I'll show you the optimal blksize for LMODs on that device type. In general, the optimal blksize for LMOD datasets is a full track, or 32,760, whichever is smaller. ---------------------------------<snip>----------------------------------- How do I check my disk space? ----------------------------------<unsnip>----------------------------- On the CBTTAPE web site, locate a program called LSPACE, download and assemble it. I'd suggest you link it into your SYS1.LINKLIB dataset, then issue the console command "F LLA,REFRESH". The comments in the code will tell you how to use it and how to interpret the results. ------------------------------<snip>---------------------------------- If my disk space is low what can I do to fix that (btw I compressed all my PDSs) -----------------------------<unsnip>-------------------------------- Let's not cross that bridge just yet. I'm sure you still have lots of space; it's just a question of understanding usage. -----------------------------<snip>----------------------------------- Is plain vanilla MVS38J really low on available disk space? (Do I need to 'buy' some more DASDs?) -----------------------------<unsnip>---------------------------------- MVS can use huge amounts of disk space, up to 256 devices on each channel. Your configuration may need adjustment but let's try to learn the basics of space management before we go "buying" DASD. ------------------------------<snip>---------------------------------- Is my linklib somehow confined to a single volume? ------------------------------<unsnip>------------------------------- All Partitioned Datasets (DSORG=PO) are limited to a single volume. That restriction has existed since PDS's were first introduced and still exists today under z/OS. Unlike Windoze and UNIX/LINUX, MVS requires that you estimate the space requirements before creating a dataset and you'll be held to those limits. I typically allocate 25 cylinders for the primary and 10 cylinders for the secondary space for a private linklib. I compute the number of directory blocks such that they take a integral number of tracks. BLKSIZE is as described above, LRECL is not specified and RECFM is always U. If there's enough interest, I'll make some excerpts from some manuals and pass them to somebody here to add to the files section of this list. They might be helpful in dealing with some of these "housekeeping" issues and save some headaches. Rick