OCL

[Kmh0421@xxxxxxx]

--
[ 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 . . . . . . . . . . . . . . . :