CA/Platinum LRECL Usage

Billy Shears

CA/Platinum LRECL Usage
I have a question to all CA/Platinum utility users:

We need to extend our LRECL beyond what Pt/Unload would normally generates.
It seems there is a LRECL parameter in the utility that can do the trick.
Questions: Are there any users using this feature? How does it work? Are
there any things I should know (e.g. what comes in the extra bytes)?

Thanks,
Bill Shears - [login to unmask email]
DB2 DBA
HOLO Enterprises Inc.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com



Rob Crane

Re: CA/Platinum LRECL Usage
(in response to Billy Shears)
The intended benefit of using the LRECL-USER value is to allow the
unloaded data (sysrec dd) to have a specified length greater than what
fast unload would have calculated (based on # of columns and length of
those columns). Probably tied over to the old vsam days when everyone
wanted to unload DB2 tables to a flat file and then process the flat
file instead of the DB2 table. Having the ability to have a set LRECL
in a program and the unload file would allow the vsam program to not
change if the table added columns or deleted columns, etc. The extra
length is padded with blanks.

Here are the warnings, etc.

Fast Unload determines the record length for the unload dataset, based
upon the number of columns and the sizes of the columns being unloaded.
However, you can force the record length for subsequent application
processing by specifying both the LRECL and the LRECL-USER YES parameter
on the DD statement. The LRECL you specify must be at least as large as
the record length Fast Unload would assign to the unload dataset; any
extra space is padded with blanks.

Note • While an effort has been made to minimize its impact, forcing the
record length could result in performance degradation as more blocks of
data are written for an LRECL that is longer than the Fast
Unload-determined record length.

WARNING • This feature can be unintentionally influenced by SMS ACS
routines that provide default LRECL values. Using Fast Unload with a
data class that provides this feature is not recommended.

-Rob


Billy Shears wrote:
>
> I have a question to all CA/Platinum utility users:
>
> We need to extend our LRECL beyond what Pt/Unload would normally generates.
> It seems there is a LRECL parameter in the utility that can do the trick.
> Questions: Are there any users using this feature? How does it work? Are
> there any things I should know (e.g. what comes in the extra bytes)?
>
> Thanks,
> Bill Shears - [login to unmask email]
> DB2 DBA
> HOLO Enterprises Inc.
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
>



Steen Rasmussen

Re: CA/Platinum LRECL Usage
(in response to Rob Crane)
If you need to extend the UNLOAD LRECL created by Batch Processor Unload, so the unloaded records fit into ONE-RECORD-PER-ROW - this can be done too:

ROWLEN ( [F,V] )
B
The ROWLEN keyword directs the UNLOAD to unload the table one row per record.
Specify F for fixed blocked records, or V for variable blocked records. The LRECL and
BLKSIZE will be determined for you. The LRECL will equal the maximum length of the
row.
An example of the ROWLEN keyword being used is shown below.
.CALL UNLOAD
.DATA
DSN(TSUSER.TSUSER.SYSTABLE.DATA)
UNIT(SYSDA)
ALLOCATE(100,60)
ROWLEN(F)
SELECT *
FROM SYSIBM.SYSTABLES
FOR FETCH ONLY
;
LIMIT(ALL)
.ENDDATA

best regards
Steen Rasmussen

> -----Original Message-----
> From: Rob Crane [SMTP:[login to unmask email]
> Sent: 18 December 2000 16:48
> To: [login to unmask email]
> Subject: Re: CA/Platinum LRECL Usage
>
> The intended benefit of using the LRECL-USER value is to allow the
> unloaded data (sysrec dd) to have a specified length greater than what
> fast unload would have calculated (based on # of columns and length of
> those columns). Probably tied over to the old vsam days when everyone
> wanted to unload DB2 tables to a flat file and then process the flat
> file instead of the DB2 table. Having the ability to have a set LRECL
> in a program and the unload file would allow the vsam program to not
> change if the table added columns or deleted columns, etc. The extra
> length is padded with blanks.
>
> Here are the warnings, etc.
>
> Fast Unload determines the record length for the unload dataset, based
> upon the number of columns and the sizes of the columns being unloaded.
> However, you can force the record length for subsequent application
> processing by specifying both the LRECL and the LRECL-USER YES parameter
> on the DD statement. The LRECL you specify must be at least as large as
> the record length Fast Unload would assign to the unload dataset; any
> extra space is padded with blanks.
>
> Note > *> While an effort has been made to minimize its impact, forcing the
> record length could result in performance degradation as more blocks of
> data are written for an LRECL that is longer than the Fast
> Unload-determined record length.
>
> WARNING > *> This feature can be unintentionally influenced by SMS ACS
> routines that provide default LRECL values. Using Fast Unload with a
> data class that provides this feature is not recommended.
>
> -Rob
>
>
> Billy Shears wrote:
> >
> > I have a question to all CA/Platinum utility users:
> >
> > We need to extend our LRECL beyond what Pt/Unload would normally generates.
> > It seems there is a LRECL parameter in the utility that can do the trick.
> > Questions: Are there any users using this feature? How does it work? Are
> > there any things I should know (e.g. what comes in the extra bytes)?
> >
> > Thanks,
> > Bill Shears - [login to unmask email]
> > DB2 DBA
> > HOLO Enterprises Inc.
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
> >
> >
>
>
>