• Subject: RE: READE Problem at V4R3
  • From: "Graap, Ken" <keg@xxxxxxxxxxxxxxxxxx>
  • Date: Wed, 20 Jan 1999 16:02:19 -0800

Download and apply PTF MF20516.

This will fix your problem.

Note: You don't even have to IPL. MF20516 can be applied IMMED....

Good luck


       Kenneth  E.  Graap
    IBM Certified Specialist
          AS/400   Professional 
          System  Administrator
 NW Natural - Information Services
           System Services
        503 226 4211 X5537
          FAX  503 721 2521

-----Original Message-----
From: Cyndi Bradberry [mailto:CyndiB@IHFA.ORG]
Sent: Wednesday, January 20, 1999 3:12 PM
To: MIDRANGE-L@midrange.com
Subject: READE Problem at V4R3

Help !!!
We just went from V3R7 to V4R3 over the last weekend. Since then we have had
programs act weird all centered around the READE op code.

Here is a code snippet:

1375.00  * Declare restrictor key work fields

1376.00 C     *LIKE         DEFINE    DBAPYR        WQSD01
Application yea          
1377.00 C     *LIKE         DEFINE    DBOFCD        WQSD02
Office code              
1378.00 C     *LIKE         DEFINE    DBTNNB        WQSD03
Tenant number            
1379.00  * Define keylist

1380.00 C     KRSSD         KLIST

1381.00 C                   KFLD                    WQSD01
Application yea          
1382.00 C                   KFLD                    WQSD02
Office code              
1383.00 C                   KFLD                    WQSD03
Tenant number            
1384.00  * Move fields to key list

1385.00 C                   MOVEL     #1APYR        WQSD01
Application yea          
1386.00 C                   MOVEL     #1OFCD        WQSD02
Office code              
1387.00 C                   Z-ADD     #1TNNB        WQSD03
Tenant number            
1388.00 C     KRSSD         SETLL     @TNTFMI1
1389.00 C     KRSSD         READE     @TNTFMI1
90    *                        
1390.00  * DBF record not found

1391.00 C   90              MOVEL     'HUD0252'     W0RTN             7

1392.00 C     *IN90         DOWEQ     '0'

1393.00  * USER: Process DBF record

1394.00  * CASE: DB1.Wage type EQ PAR.Wage type
1395.00 C     DBJJST        IFEQ      'W'
*IF                      00
1396.00 C     DBJJST        OREQ      'N'
1397.00 C     DBJJST        OREQ      'B'
1398.00 C     DBJJST        OREQ      'M'
1399.00 C     DBJJST        OREQ      'F'
1400.00 C     DBIBAS        MULT      DBIMLT        WUEIVA
Total base Wage          00
1401.00 C                   MULT      DBAATR        WUEIVA
Total base Wage          00
1402.00 C                   ADD       WUEIVA        WUEGVA
Total year wage          95
1403.00 C                   END
*FI                      00
1404.00 C     KRSSD         READE     @TNTFMI1
90    *                        00
1405.00 C                   END

KRSSD represents a partial key of the file TNTFMI1. The full key of the file
has two more fields each 2.0 long. Prior to V4, the READE would retrieve the
records that matchted the partial key. Since then, The setll would set the
file and then it would retrieve all the records until the end of the file.
Is this some sort of 'feature' that no one documented?  Or have our programs
been working for all these years and we just never knew that we were wrong?


Cyndi Bradberry
Idaho Housing and Finance Association
Boise, Idaho
 <<Cyndi Bradberry (E-mail).vcf>> 
| 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 thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].