There is no need to specify any DCB information on //SYSMDUMP. Just don't,
and you'll get what's best.
sas
On Wed, May 24, 2023 at 3:19 PM Steve Thompson wrote:
> Thank you. I knew I was missing something. I just couldn't
> remember that "S". How many times has that bitten me...
>
> But
Thanks Sri, I see that is in the IPCS User's Guide.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Sri
h Kolusu
Sent: Wednesday, May 24, 2023 5:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: SYSMDUMP blocking [was: Why does ISPF BROWSE abend with S878
>> Can you share where that may be documented?
Peter,
Since z/OS 1.6 IPCS supported SDB (System Determined Blocksize)
https://www.ibm.com/docs/en/zos/2.3.0?topic=sources-dump-data-set-processing
Thanks,
Kolusu
--
For
ERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
On Wed, 24 May 2023 11:35:19 -0400, Steve Thompson wrote:
>RECFM=F,LRECL=4160,BLKSIZE=0 (I think blocking works with dumps now)
Yes SYSMDUMP can be blocked. But if it is going to be blocked, RECFM
Thank you. I knew I was missing something. I just couldn't
remember that "S". How many times has that bitten me...
But IEBGENER to FBS fixes it.
And I was thinking that what I had specified would handle a TSO
user address space, unless it didn't have enough space for
secondaries That's
On Wed, 24 May 2023 11:35:19 -0400, Steve Thompson wrote:
>RECFM=F,LRECL=4160,BLKSIZE=0 (I think blocking works with dumps now)
Yes SYSMDUMP can be blocked. But if it is going to be blocked, RECFM must be
FBS. RECFM=F will be unblocked.
>And SPACE=(CYL,100,30) I think that should be able to
gure out
where the problem is.
Thanks for the idea though.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Thompson
Sent: Wednesday, May 24, 2023 11:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequentia
Of
Steve Thompson
Sent: Wednesday, May 24, 2023 11:35 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
Peter:
You can allocate a SYSMDUMP data set using the DDNAME SYSMDUMP
within your TSO session, and if DAE doesn't kill it, you
,
and slim retired.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jim
Mulder
Sent: Tuesday, May 23, 2023 11:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
I would set a SLIP and take a dump
is slim and none,
and slim retired.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jim
Mulder
Sent: Tuesday, May 23, 2023 11:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
I would
On Wed, 24 May 2023 03:35:52 +, Jim Mulder wrote:
> I would set a SLIP and take a dump of the 878 abend, and then look to see
> what
>is consuming the storage. ...
>
You would do that, but you have the source code.
--
gil
On Wed, 24 May 2023 00:43:05 +, Alan Young wrote:
>Is the file RECFM=V? For me, variable records seem to vex ISPF browse and edit
>more than RECFM=F files. It runs out of storage sooner with the variable
>length files. That is with a TSO region of 131072.
>
ISPF Edit and View (and, I
rame Discussion List On Behalf Of
Farley, Peter
Sent: Tuesday, May 23, 2023 5:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
Possibly. But if so we are in a lot more trouble than annoying abends out of
TSO, as this is cust
23, 2023 4:37 PM
To:
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
Your system is a lot less busy than the one I use. Just maxing to the bottom of
a smaller 8,778 cylinder generation of the same file set I mentioned earlier in
BROWSE didn't complete
On Tue, 23 May 2023 20:50:16 +, Farley, Peter wrote:
>VIEW is limited in what size file it can handle, the entire file has to fit in
>available memory under TSO. For very large files like the one I am searching
>it forces BROWSE anyway and you do not have the VIEW capabilities.
>
>We also
: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
Possibly. But if so we are in a lot more trouble than annoying abends out of
TSO, as this is customer data with legal archiving requirements. If it is
somehow corrupted by compression (not sure at this point
Sent: Tuesday, May 23, 2023 4:56 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
EXTERNAL EMAIL
I agree that Browse isn't supposed to require enough memory to hold the file,
so it should work.
But.
Is "compressed
@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
EXTERNAL EMAIL
I agree that Browse isn't supposed to require enough memory to hold the file,
so it should work.
But.
Is "compressed data" the key? How is it compressed? Doe
: Why does ISPF BROWSE abend with S878 searching a large sequential file?
This has happened to me twice this afternoon, and several other times in the
last few months - I am trying to browse (from ISPF 3.4) a quite large
sequential file (> 14500 cylinders of compressed data) for a record with a
.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Thompson
Sent: Tuesday, May 23, 2023 4:38 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential
file?
Have you tried View? It behaves the same as Edit
Have you tried View? It behaves the same as Edit, but does not
save. I have found that it handles things a bit better than
browse does at times.
Steve Thompson
On 5/23/2023 4:12 PM, Farley, Peter wrote:
This has happened to me twice this afternoon, and several other times in the last
few
Used to use REGION=6M on batch jobs, and about 1% of jobs would abend
with S878. To cure they would have to bounce the initiator to clear
up all memory allocation. Maybe bump up to 64000 to see if that is
enough memory? I don't know if you can specify REGIONX=(24,31,64) for
TSO.
On Tue, May 23,
This has happened to me twice this afternoon, and several other times in the
last few months - I am trying to browse (from ISPF 3.4) a quite large
sequential file (> 14500 cylinders of compressed data) for a record with a
specific 31-byte key at the beginning of the record, and browse abends
23 matches
Mail list logo
