|
The BLDFILE is essentally doing the CRTPF for you, and generically
naming the fields. I did the following:
BLDFILE TEST1,I,RECORDS,10,170,,T,157,5,DFILE
and this is the Display File Field Description (DSPFFD)
Field Level Information
Data Field Buffer Buffer Field
Field Type Length Length Position Usage
F00001 CHAR 156 156 1 Both
K00001 CHAR 5 5 157 Both
F00002 CHAR 9 9 162 Both
I personally like creating the DDS & CRTPF. Then, when a native pgm
or query/sql works best, the file is ready. BTW - a BLDINDEX does the
logical file with the substrings. And you can access BLDINDEX files in a
native pgm, even if non-contiguous key fields.
Jim Franz
----- Original Message -----
From: "Larry Bolhuis" <lbolhuis@arbsol.com>
To: <MIDRANGE-L@midrange.com>
Sent: Saturday, July 08, 2000 10:13 PM
Subject: Re: OCL and CL
> Booth,
>
> Coupla choices:
>
> a) Define the file in DDS as field1 156 long, field2 5 long, field3 9
> long. Then key it by field 2. Assuming you are using the file only by
> programs with internally defined file descriptions, this will work fine.
>
> b) Create the file with CRTPF fixed record of 170 characters. Then
> create DDS for an LF that uses SUBST to create a keyfield starting in
> 157 for 5 long.
>
> I guess I'd use 'a'.
>
> But then, why not use OCL BLDFILE??? (Just asking)
>
> - Larry
>
> booth@martinvt.com wrote:
> >
> > I need to create a physical file in QS36F. The file is 170 characters
> > long and has a 5-digit key starting in position 157. I know how to do
it
> > in OCL but how does one do it in CL? CRTPF lets me specify 170
characters
> > but I can not see how to specify the key. I was thinking of defining
the
> > file in DDS but there is no clear definitions available for the record
> > beyond the 5-digit key at 157.
>
> --
> Larry Bolhuis |
> Arbor Solutions, Inc | IBM AS/400e - Get There First!
> (616) 451-2500 |
> (616) 451-2571 -fax | It's 10PM. Has your NT Server had it's
> lbolhuis@arbsol.com | theraputic re-boot yet today?
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.