.
John Reda
Syncsort, Inc.
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of ??? ?? ???
Sent: Wednesday, December 31, 2008 6:56 AM
To: IBM-MAIN@bama.ua.edu
Subject: Syncsort Oddity
Hi,
I've encountered something in Syncsort, and I'm
Sounds like the file was created with RECFM=V writes,
and was never blocked when created, inspite of the
DCB attributes.
Barry
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Walt Farrell
Sent: Thursday, January 01, 2009 3:09 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syncsort Oddity
On Wed, 31 Dec 2008 19:16:43 +, Ted MacNEIL eamacn...@yahoo.ca
wrote:
When using VB, some code will write a short block if the space
Hi,
I’ve encountered something in Syncsort, and I’m looking for an explanation.
One of our users used Syncsort to copy a dataset.
The input file had 93386 tracks in 10 extents.
The output file had 64815 tracks in 2 extents.
Both files are LRECL=27904 BLKSIZE=27998 RECFM=VB
On Wed, 31 Dec 2008 13:56:20 +0200 ??? ?? ??? gad...@malam.com wrote:
:Ive encountered something in Syncsort, and Im looking for an explanation.
:One of our users used Syncsort to copy a dataset.
:The input file had 93386 tracks in 10 extents.
:The output file had 64815 tracks in 2 extents.
Gadi,
May Syncsort truncate the record if trailing x'00'' or blanks are padded at
end of some of the records? I would look into the shorter records in the
file to see if they are realy shorter...
Itschak
2008/12/31 גדי בן אבי gad...@malam.com
Hi,
I've encountered something in Syncsort,
I would look at the raw input file and see how it was blocked. Perhaps the
program that created the file wrote smaller blocks.
The OP did say they both had the same block size.
-
Too busy driving to stop for gas!
--
For
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of ??? ?? ???
Sent: Wednesday, December 31, 2008 5:56 AM
To: IBM-MAIN@bama.ua.edu
Subject: Syncsort Oddity
Hi,
=20
I=92ve encountered something in Syncsort, and I=92m looking
Use SAS to find the actual physical block size of the two files:
// EXEC SAS
//FILEONE DD DSN=FILEONE,DISP=SHR
//FILETWO DD DSN=FILETWO,DISP=SHR
//SYSIN DD *
DATA SIZEONE;
INFILE FILEONE RECFM=U BLKSIZE=32760 LENGTH=LEN;
INPUT;
LENGTH=LEN;
PROC FREQ:
TABLES LENGTH;
TITLE TABULATION OF BLOCK SIZES
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Barry Merrill
Sent: Wednesday, December 31, 2008 9:30 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syncsort Oddity
Use SAS to find the actual physical block size of the two files:
SNIP
On Wed, 31 Dec 2008 15:00:35 + Ted MacNEIL eamacn...@yahoo.ca wrote:
:I would look at the raw input file and see how it was blocked. Perhaps the
program that created the file wrote smaller blocks.
:The OP did say they both had the same block size.
The same maximum block size. Not
The same maximum block size. Not necessarily the same sizes for specific
blocks.
Eh?
-
Too busy driving to stop for gas!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with
When using VB, some code will write a short block if the space remaining in the
current block is less than the DCB LRECL, even though the actual length of the
next record is unknown. This results in a lot of short blocks, particularly
when the LRECL is large, as in this case.
Ted MacNEIL
On Wed, 31 Dec 2008 18:35:20 +, Ted MacNEIL wrote:
The same maximum block size. Not necessarily the same sizes for specific
blocks.
Eh?
Ever heard of TRUNC?
--
Tom Marchant
--
For IBM-MAIN subscribe / signoff / archive
When using VB, some code will write a short block if the space remaining in
the current block is less than the DCB LRECL, even though the actual length of
the next record is unknown.
This results in a lot of short blocks, particularly when the LRECL is large,
as in this case.
So, SYNCSORT
On Wed, 31 Dec 2008 13:56:20 +0200, #1490;#1491;#1497; amp;#1489;#1503;
#1488;#1489;#1497; gad...@malam.com wrote:
Ive encountered something in Syncsort, and Im looking for an explanation.
One of our users used Syncsort to copy a dataset.
The input file had 93386 tracks in 10 extents.
At 14:22 +0200 on 12/31/2008, Binyamin Dissen wrote about Re: Syncsort Oddity:
On Wed, 31 Dec 2008 13:56:20 +0200 ??? ?? ??? gad...@malam.com wrote:
:I¹ve encountered something in Syncsort, and I¹m looking for an explanation.
:One of our users used Syncsort to copy a dataset.
:The input
And if you don't have SAS, user SYNCSORT's HISTOGRM program to get a
distribution of block sizes.
// EXEC PGM=HISTOGRM
//SYSUT1 DD DISP=SHR,
// DSN=
//SYSPRINT DD SYSOUT=*
Bob
Barry Merrill wrote:
Use SAS to find the actual physical block size of the two files:
Washington State Univsersity
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of
Robert A. Rosenberg
Sent: Wednesday, December 31, 2008 12:15 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syncsort Oddity
At 14:22 +0200 on 12/31/2008, Binyamin Dissen
: Fw: Syncsort Oddity
If, for example, the original file were created by a COBOL program that was
compiled with the NOAWO option (or the older OS/VS COBOL apply write only
syntax), then it is QUITE possible that there are many short blocks in a
VB file.
When NOAWO is in effect for a COPY program
On Wed, 31 Dec 2008 19:16:43 +, Ted MacNEIL eamacn...@yahoo.ca wrote:
When using VB, some code will write a short block if the space remaining
in the current block is less than the DCB LRECL, even though the actual
length of the next record is unknown.
This results in a lot of short blocks,
: Thursday, January 01, 2009 3:09 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Syncsort Oddity
On Wed, 31 Dec 2008 19:16:43 +, Ted MacNEIL eamacn...@yahoo.ca wrote:
When using VB, some code will write a short block if the space remaining
in the current block is less than the DCB LRECL, even though
22 matches
Mail list logo
