All,
It seems we have several versions of how Freespace operates in a KSDS. I
recall that FreeSpace was maintained when records are inserted at the end of
file, but not SIS.
I found the following reference at
"http://www.slideshare.net/danjodea/basic-vsam.";
"When records are inserted be
On Sat, 2010-07-31 at 10:36 -0500, Rick Fochtman wrote:
> Long ago, before the advent of SMS, IBM made a commitment to not change
> device geometry after the 3390 was introduced. I, for one, salute IBM
> for living up to that commitment.
>
> Rick
In many ways, I agree with that sentiment. Howe
On Fri, 30 Jul 2010 10:20:51 -0400 Gerhard Postpischil
wrote:
:>On 7/29/2010 7:08 AM, Binyamin Dissen wrote:
:>> There is very little difference (from the programmers view) between BSAM and
:>> BPAM. QSAM and BSAM, on the other hand, are quite different.
:>I guess it depends on your definition o
---
But this reminds me of the current struggle to extend DASD volume sizes
beyond 54GB, largely because IBM apparently at the introduction of the
3390 made a committment to support forever programmers with the
unconscionab
On Sat, 2010-07-31 at 08:18 -0500, Eric Bielefeld wrote:
> What is the new JEW Spool data set browse? Is that a new command, or a
> vendor product? I've never heard of it before or remember it mentioned on
> this list.
>
> Eric Bielefeld
> Sr. Systems Programmer
>
http://publibz.boulder.ibm.
What is the new JEW Spool data set browse? Is that a new command, or a
vendor product? I've never heard of it before or remember it mentioned on
this list.
Eric Bielefeld
Sr. Systems Programmer
- Original Message -
From: "Monika Amiss"
Dear group,
i'm making some tests with t
W dniu 2010-07-31 00:30, Paul Gilmartin pisze:
On Tue, 20 Jul 2010 08:01:09 -0700, Edward Jaffe wrote:
I've seen other "old" programs with many hard-coded offsets and lengths
and always wondered why this was such common practice back then.
Was it because there were a lot of inexperienced assem
>It looks like your ALTXTPRE includes a length field. Since IAZBTOKP includes
>the length of each subparameter, it should not follow >ALTXTPRE but, rather,
>overlay the last two bytes of ALTXTPRE. So,
>ALTXTU3 DSXL(ALTXTPRE)
>TU0002TK DSCL(BTOKSIZE)
>should be
It looks like your ALTXTPRE includes a length field. Since IAZBTOKP includes
the length of each subparameter, it should not follow ALTXTPRE but, rather,
overlay the last two bytes of ALTXTPRE. So,
ALTXTU3 DSXL(ALTXTPRE)
TU0002TK DSCL(BTOKSIZE)
should be
ALTXT
The FM (z/OS V1R12.0 MVS Authorized Assembler Services Guide) confirms TUNUM=7.
Did you ensure that BTOKLSDL=0?
> Date: Sat, 31 Jul 2010 03:13:59 -0400
> From: jayare...@hotmail.com
> Subject: Re: AW: Dynalloc error: 037C006E (spool data set browse)
> To: IBM-MAIN@bama.ua.edu
>
> There is s
There is some confusion regarding the browse token. Is it a single token that
just happens to have seven subparameters (TUNUM=1) or is it seven distinct
subparameters that need to be reflected in TUNUM (TUNUM=7)?
There is a SHARE presentation
http://ew.share.org/client_files/callpapers/attac
On 7/31/2010 1:09 AM, Monika Amiss wrote:
> MVC U3.S99TUKEY,=AL2(DALBRTKN)
> MVC U3.S99TUNUM,=AL2(7)
> MVC U3.S99TULNG,=AL2(L'TU0002TK)
> Any hint appreciated. Have a nice day.
> You're misreading the message. Note that you stuff a 7 into TUNUM, which is
> the
12 matches
Mail list logo
