You should up your buffers (and NCP). Two will be spending a lot of time
waiting.
Just remember that after a CHECK shows EOF, you should not expect a valid
status from the pending reads.
On Fri, 28 Nov 2014 12:20:08 -0500 Sam Golob wrote:
:>Hi Folks,
:>
:> I was just involved in an exercis
In <5478aec8.8020...@cbttape.org>, on 11/28/2014
at 12:20 PM, Sam Golob said:
>uses BSAM with double buffers
I would expect QSAM with lots of buffers to outperform that, but it's
not that hard to do BSAM with lots of buffers.
>To avoid such problems,
You might also want to add code to avoid
On 11/28/2014 12:20 PM, Sam Golob wrote:
Hi Folks,
I was just involved in an exercise to improve an old file
copying program from CBT Tape File 316. It is called FFYCOPY,
and it was written in the mid-1970's by Frank Yates (courtesy of
Jim Marshall). This program's "copy engine" uses BSAM
sometimes
gets overlooked as a viable alternative.
Cheers,
Alan
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Sam Golob
Sent: Friday, November 28, 2014 12:20 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Copying sequential files - BSAM an
Hi Folks,
I was just involved in an exercise to improve an old file copying
program from CBT Tape File 316. It is called FFYCOPY, and it was
written in the mid-1970's by Frank Yates (courtesy of Jim Marshall).
This program's "copy engine" uses BSAM with double buffers, and for its
time,
