Martin Packer on IBM Mainframe Discussion List wrote
on 08/31/2011 07:31:23 AM:
> DFSORT can process VBS. Whether it goes to 32767 or not I'll leave to
> Frank to clear up.
>
> A useful technique I've found in the past is to make DFSORT do my I/O to
> SMF and use an exit to pick up the records in
DFSORT can process VBS. Whether it goes to 32767 or not I'll leave to
Frank to clear up.
A useful technique I've found in the past is to make DFSORT do my I/O to
SMF and use an exit to pick up the records in a buffer.
Martin
Martin Packer,
Mainframe Performance Consultant, zChampion
Worldwide
While I'm no BSAM/QSAM expert, and while it is possible
to create sequential files with LRECL=32767, I do know
that very few, if any, applications, other than perhaps
a rose-colored ASM program, can actually process that
record length.
VBS records written to SMF are limited to LRECL=32760
and ex
Shmuel Metz (Seymour J.) wrote:
> I generally look at the world through assembler-colored glasses.
:-D Where can I get those glasses? Are 3D versions available? :-D
Groete / Greetings
Elardus Engelbrecht
--
For IBM-MAIN subscr
In
,
on 08/30/2011
at 02:19 PM, Don Imbriale said:
>Perhaps a small clue as to what those other options are would be
>useful.
Another poster has already said that COBOL doesn't support them. I
generally look at the world through assembler-colored glasses.
--
Shmuel (Seymour J.) Metz,
Perhaps a small clue as to what those other options are would be useful.
- Don Imbriale
On Mon, Aug 29, 2011 at 5:10 PM, Shmuel Metz (Seymour J.) <
shmuel+ibm-m...@patriot.net> wrote:
> In <1314648996.7200.58.ca...@mckown5.johnmckown.net>, on 08/29/2011
>at 03:16 PM, John McKown said:
>
> >
In <1314648996.7200.58.ca...@mckown5.johnmckown.net>, on 08/29/2011
at 03:16 PM, John McKown said:
>As I recall, QSAM/BSAM can have a "logical record" >32K. But __only__
>if it is VBS and __ONLY__ if you process each logical segment
>separately in your own code.
I believe that there are a cou
W dniu 2011-08-29 19:05, Frank Swarbrick pisze:
Even using Spanned (record format is S) or Undefined (record format is U) Cobol
(Enterprise COBOL 4.2) appears to not allow a record length more than 32K:
32 IGYGR1224-E The maximum calculated record size of file
"WIRE-DOCUMENT-FILE" was great
As I recall, QSAM/BSAM can have a "logical record" >32K. But __only__ if
it is VBS and __ONLY__ if you process each logical segment separately in
your own code. That is, you cannot request that QSAM merge the segments
together into a single logical record for you. The reason being that
each segment
On 8/29/2011 11:05 AM, Frank Swarbrick wrote:
Even using Spanned (record format is S) or Undefined (record format is U) Cobol
(Enterprise COBOL 4.2) appears to not allow a record length more than 32K:
32 IGYGR1224-E The maximum calculated record size of file
"WIRE-DOCUMENT-FILE" was greater
: IBM-MAIN@bama.ua.edu
Subject: Cobol and large QSAM record length
Even using Spanned (record format is S) or Undefined (record format is
U) Cobol (Enterprise COBOL 4.2) appears to not allow a record length more
than 32K:
32 IGYGR1224-E The maximum calculated record size of file
"WIRE-DOC
Even using Spanned (record format is S) or Undefined (record format is U) Cobol
(Enterprise COBOL 4.2) appears to not allow a record length more than 32K:
32 IGYGR1224-E The maximum calculated record size of file
"WIRE-DOCUMENT-FILE" was greater than the maximum allowable size
12 matches
Mail list logo
