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 have CA FileMaster, and their browse can handle very large file sizes.  
Sometimes I forget that and just try to use BROWSE instead.  My bad.

Anyway, batch SORT gave me what I needed so I am good, but those 878 abends are 
just plain annoying.  There is no reason I can think of why they should occur 
at all, which is where the frustration lies.

'Nuff said.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of 
Steve Thompson
Sent: Tuesday, May 23, 2023 4:38 PM
To: [email protected]
Subject: Re: Why does ISPF BROWSE abend with S878 searching a large sequential 
file?

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 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 with 
> S878 and throws me off TSO entirely, requiring me to login again each time.
>
> My TSO logon region size is set to 48000, so what in the world is making 
> browse consume so much memory that it runs out and crashes my TSO session 
> entirely?
>
> I know, OCO prevents anyone knowing for sure, but if you have any clue I'd 
> appreciate knowing the answer.
>
> I've been forced to search that file using SORT in a batch job to keep the 
> frustration level lower.
>
> Peter
--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to