Re: OCL -- RPG400-L

--
[ Picked text/plain from multipart/alternative ]
Thanks Steven.... I may need that tidbit tomorrow! I am working on this in
the evenings now, so I will mess with it again tomorrow night....
Thanks again
Kathie



In a message dated 09/24/2001 10:26:09 PM Central Daylight Time,
STEVEN.J.RYAN@denso.com.au writes:


> Subj: Re: OCL
> Date: 09/24/2001 10:26:09 PM Central Daylight Time
> From:    STEVEN.J.RYAN@denso.com.au
> Sender:    rpg400-l-admin@midrange.com
> Reply-to: <A HREF="mailto:rpg400-l@midrange.com">rpg400-l@midrange.com</A>
> To:    rpg400-l@midrange.com
>
>
>
>
>
>
> This may not be your problem, but I believe you need an 'R' or 'L'
> (depending on
> whether you use CHAIN or READ) in your F spec.
>
> i.e.
> FIC935U2 UF  F  64  64 13AI    52 DISK
> should be
> FIC935U2 UF  F  64  64L13AI    52 DISK
>
> The other thing, of course, is to double check that you did make you key 13
> long
> at position 52.
>
>
>
>
> Kmh0421@aol.com on 25/09/2001 13:13:24
>
> Please respond to rpg400-l@midrange.com
>
> To:   rpg400-l@midrange.com
> cc:    (bcc: STEVEN J RYAN/DIAU)
>
> Subject:  Re: OCL
>
>
>
>
> --
> [ Picked text/plain from multipart/alternative ]
> Lars;
> I did have the key length in the f spec... but still got the error.
> Thanks your help!
> Kathie
> FIC935U2 UF  F  64  64 13AI    52 DISK
> FIC935U  O   F  64  64            DISK                      A
>
>
>
> In a message dated 09/24/2001 1:58:15 AM Central Daylight Time,
> lv@sanistaal.dk writes:
>
>
> > Subj: Re: OCL
> > Date: 09/24/2001 1:58:15 AM Central Daylight Time
> > From:    lv@sanistaal.dk (Lars Villadsen)
> > Sender:    rpg400-l-admin@midrange.com
> > Reply-to: <A HREF="mailto:rpg400-l@midrange.com">rpg400-l@midrange.com</A>
> > To:    rpg400-l@midrange.com
> >
> >
> >
> >
> >
> > Hi Kathie (and David)
> >
> > To David : this is indeed an rpg question
> >
> > To Kathie :
> >
> > You have to specify the key length in the f-spec :
> >
> > FFILE    IC        512R 8AI  EXTK DISK
> >
> > the key in this example is 8 long
> >
> > good luck
> >
> > Lars
> >
> >
> >
> >
> >                     Kmh0421@aol.com
> >                     Sent by:                To:     RPG400-L@midrange.com
> >                     rpg400-l-admin@mi       cc:
> >                     drange.com              Subject:     OCL
> >
> >
> >                     21-09-01 20:57
> >                     Please respond to
> >                     rpg400-l
> >
> >
> >
> >
> >
> >
> > --
> > [ Picked text/plain from multipart/alternative ]
> > Hi again...
> > Does anyone know OCL?
> > Do I have to somehow define the length of the key to a logical in the OCL?
> > I am almost finished with all of these programs, about 4 left.... then
> back
> > to the future!
> > Thanks....Again!
> > Kathie
> >
> >
> > I did a BLDINDEX and created a logical over my physical, keyed by the last
> > 13
> > bytes of my flat file, positions 52 to 64. (U2 is the logical) My OCL now
> > looks like this:
> > *************** Beginning of data ***************************
> > // LOCAL OFFSET-102,DATA-'?WS?'
> > // OVRDBF FILE(IC935U) TOFILE(KMHFILES/IC935U)
> > // OVRDBF FILE(IC935U2) TOFILE(KMHFILES/IC935U2)
> > // OVRDBF FILE(DE400A) TOFILE(KMHFILES/DE400A)
> > // OVRDBF FILE(IC052A) TOFILE(KMHFILES/IC052A)
> > // OVRDBF FILE(IC040A) TOFILE(KMHFILES/IC040A)
> > // LOAD IC935U
> > // FILE NAME-IC935U,DISP-SHR,RECORDS-500,EXTEND-10
> > // FILE NAME-IC935U2,DISP-SHR,RECORDS-500,EXTEND-10
> > // FILE NAME-DE400A,DISP-SHR
> > // FILE NAME-IC052A,DISP-SHR
> > // FILE NAME-IC040A,DISP-SHR
> > // RUN
> > When I call it... I get an error:
> >
> > SYS2206 Options (  23)
> > IC935U2. This file accessed with wrong key length.
> >
> > Cause . . . . . :   In referencing the file identified in the message, the
> >    program running is using the wrong key length value.  If you are
> running
> >    a procedure, you incorrectly entered a procedure name or parameter.
> > Recovery  . . . :   Enter option 2 or 3 and give the programmer the
> > message
> >    ID (SYS2206) and the file name identified in the message.
> > Possible choices for replying to message . . . . . . . . . . . . . . . :
>