Re: Logical File Access -- COBOL400-L

It is an X(15).
No messages in the JOBLOG as it is not erroring out.

Running the debugger, I can see the field values and all iscorrect............

Are logicals treated differently that physical files?? I have this same(generically speaking) code running on several physical files and have neverhad this type problem.

----- Original Message -----From: "Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>

To: "COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx>
Sent: Monday, May 01, 2006 10:28 AM
Subject: Re: [COBOL400-L] Logical File Access

Don,

A quick review ot the APAR's and PTF's didn't reflect any problems
at V5R2.

One other possibility is that your variable named ITEM-NO is a
different length than the LDITEM key although I'm sure you've
probably already checked that ;-)  Are there any additional
messages in the job log?

Terry Winchester
Programmer/Analyst
________________________________
The Raymond Corporation
terry.winchester@xxxxxxxxxxxxxxx

-----Original Message-----
From:
cobol400-l-bounces+terry.winchester=raymondcorp.com@xxxxxxxxxx
om
[mailto:cobol400-l-bounces+terry.winchester=raymondcorp.com@mi
drange.com] On Behalf Of Don Stafford
Sent: Monday, May 01, 2006 10:17 AM
To: COBOL Programming on the iSeries/AS400
Subject: Re: [COBOL400-L] Logical File Access

5.2

----- Original Message -----From: "Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>

To: "COBOL Programming on the iSeries/AS400" <cobol400-l@xxxxxxxxxxxx>
Sent: Monday, May 01, 2006 10:07 AM
Subject: Re: [COBOL400-L] Logical File Access


> Don,
>
> Hmmmm...other than initializing your File Status variable
> I don't see anything wrong!  Technically, it shouldn't be
> necessary to do this since the START statement will do
> this automagically.  The fact that all of your keys are
> ascending eliminates any "descending" key problem.
>
> What release level are you on?  You might try going here:
>
> http://www-912.ibm.com/ImprovedSearch/searchoptions.jsp
>
> and searching for "Cobol Start". I noticed that there
> were some problems with packed fields in prior releases.
>
> Terry Winchester
> Programmer/Analyst
> ________________________________
> The Raymond Corporation
> terry.winchester@xxxxxxxxxxxxxxx
>
>> -----Original Message-----
>> From: cobol400-l-bounces@xxxxxxxxxxxx
>> [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Don Stafford
>> Sent: Monday, May 01, 2006 9:44 AM
>> To: COBOL Programming on the iSeries/AS400
>> Subject: Re: [COBOL400-L] Logical File Access
>>
>> Sounds that way doesn't it......
>> But, in fact, there are more than 50,000 records from this
>> starting point to
>> the end of the file.
>> And, in fact, there are 9 records that have 40152 as the item
>> # (the one I'm
>> using).
>>

>> ----- Original Message ----->> From: "Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx>

>> To: "COBOL Programming on the iSeries/AS400"
<cobol400-l@xxxxxxxxxxxx>
>> Sent: Monday, May 01, 2006 9:36 AM
>> Subject: Re: [COBOL400-L] Logical File Access
>>
>>
>> > It sounds like your key value has pushed you past the
>> > end of the index because your using NOT LESS in the
>> > START statement.
>> >
>> > Terry Winchester
>> > Programmer/Analyst
>> > ________________________________
>> > The Raymond Corporation
>> > terry.winchester@xxxxxxxxxxxxxxx
>> >
>> >> -----Original Message-----
>> >> From: cobol400-l-bounces@xxxxxxxxxxxx
>> >> [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Don Stafford
>> >> Sent: Monday, May 01, 2006 9:00 AM
>> >> To: COBOL Programming on the iSeries/AS400
>> >> Subject: [COBOL400-L] Logical File Access
>> >>
>> >> Is there a trick to accessing files via logical files?
>> >> When I do the START, it returns with an file-status of
>> >> '23'..... BEFORE the
>> >> READ statement
>> >> Anyone have any ideas or suggestions?
>> >> ----------------------------------------------------------
>> >> Here is the SELECT STATEMENT
>> >>
>> >>  select WFLOD
>> >>      assign to database-WFLOD
>> >>      organization indexed
>> >>      access dynamic
>> >>      record key externally-described-key with duplicates
>> >>      file status WFLOD-FS.
>> >> ----------------------------------------------------------
>> >> Here is the FD STATEMENT
>> >>
>> >>  FD  WFLOD
>> >>      label records are standard.
>> >>  01  WFLOD-record.
>> >>      COPY DDSR-WFLOD00 OF UAVBASEF-WFLODL02.
>> >>
>>
--------------------------------------------------------------------
>> >> Here is the paragraph containing the code referred to above
>> >>
>> >>
>> >>  PROC-ITEMS.
>> >>
>> >>      INITIALIZE WFLOD-RECORD.
>> >>
>> >>      IF ITEM-NO NOT = "*ALL"
>> >>         MOVE ITEM-NO TO LDITEM.
>> >>
>> >>      START WFLOD KEY NOT < EXTERNALLY-DESCRIBED-KEY.
>> >>      IF WFLOD-FS < "03"
>> >>         READ WFLOD NEXT RECORD
>> >>         IF WFLOD-FS < "03"
>> >>            PERFORM CHK-THIS-ITEM
>> >>            IF TFITM-FS = "00"
>> >>               MOVE LDITEM TO SAV-ITEM
>> >> -----------------------------------------------------------
>> >> Here is the code from the source listing referring to the file
>> >>
>> >>     37     004500 FD  WFLOD
>> >>            004600     label records are standard.
>> >>     38     004700 01  WFLOD-record.
>> >>            004800     COPY DDSR-WFLOD00 OF UAVBASEF-WFLODL02.
>> >>           +000001*    I-O FORMAT:WFLOD00    FROM FILE
>> >> WFLODL02   OF LIBRARY
>> >> UA
>> >>           +000002*                          Location Detail
>> >>           +000003*THE KEY DEFINITIONS FOR RECORD FORMAT  WFLOD00
>> >>           +000004*  NUMBER               NAME
>> >> RETRIEVAL
>> >> A
>> >>           +000005*   0001   LDITEM
>>   ASCENDING
>> >>           +000006*   0002   LDWHS
>>   ASCENDING
>> >>           +000007*   0003   LDASLE
>>   ASCENDING
>> >>           +000008*   0004   LDBAY
>>   ASCENDING
>> >>           +000009*   0005   LDLVL
>>   ASCENDING
>> >>           +000010*   0006   LDLCPL
>>   ASCENDING
>> >>     39    +000011       05  WFLOD00.
>> >>     40    +000012           06 LDWHS                 PIC X(3).
>> >>           +000013*                  Warehouse
>> >>     41    +000014           06 LDASLE                PIC X(3).
>> >>           +000015*                  Aisle
>> >>     42    +000016           06 LDBAY                 PIC X(3).
>> >>           +000017*                  Bay
>> >>     43    +000018           06 LDLVL                 PIC X(3).
>> >>           +000019*                  Level
>> >>     44    +000020           06 LDLCPL                PIC S9(20)
>> >> COMP-3.
>> >>           +000021*                  License Plate ID
>> >>     45    +000022           06 LDOLCP                PIC S9(20)
>> >> COMP-3.
>> >>           +000023*                  Orig License Plate
>> >>     46    +000024           06 LDITEM                PIC X(15).
>> >>           +000025*                  Item Number
>> >>     47    +000026           06 LDVRSN                PIC X(3).
>> >>           +000027*                  Version
>> >>     48    +000028           06 LDLOT                 PIC X(15).
>> >>           +000029*                  Lot ID
>> >>     49    +000030           06 LDISTS                PIC X(3).
>> >>           +000031*                  Inventory Status
>> >>     50    +000032           06 LDLZON                PIC X(6).
>> >>           +000033*                  Locating Zone
>> >>     51    +000034           06 LDAZON                PIC X(6).
>> >>           +000035*                  Allocation Zone
>> >>     52    +000036           06 LDLTYP                PIC X(6).
>> >>           +000037*                  Location Type
>> >>     53    +000038           06 LDAGDT                PIC S9(7)
>> >> COMP-3.
>> >>
>> >>          More...
>> >> --------------------------------------------------------------
>> >> ----------
>> >> Don Stafford, Director of Information Technologies
>> >> UAV Entertainment Corporation
>> >> 2200 Carolina Place
>> >> Fort Mill, SC  29708
>> >> 803-548-1056  x1159
>> >> 803-548-2493 - Fax
>> >> don.stafford@xxxxxxxxx
>> >>


Confidentiality Notice:

The preceding e-mail message (including any attachments) containsinformation that may be confidential, protected by applicable legalprivileges, or constitute non-public information. It is intended to beconveyed only to the designated recipient(s). If you are not an intendedrecipient of this message, please notify the sender by replying to thismessage and then delete it from your system. Use, dissemination,distribution or reproduction of this message by unintended recipients is

not authorized and may be unlawful.




--

This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailinglist

To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

at http://archive.midrange.com/cobol400-l.