SQL Error causing CPF5257 DB2/400

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tunaclone
    New Member
    • Mar 2008
    • 1

    SQL Error causing CPF5257 DB2/400

    This is strange.. I have logical view created over all members of a multiple member file. If i do
    Code:
    Select * From POPVM102
    I get error CPF5257 Pointer not set for location referenced error. If I just select some fields it works just fine
    Code:
    SELECT PVPRD, PVVND, PVBUY FROM popvm102
    . It works fine using DBU. If I manually select all the fields and run it, I get the same error.
    Code:
     SELECT ACTIV, CMPNO, PLTNO, PVPRD, PVVND, PVBUY, PVPVP, PVDSC, 
    PVSUB, PVSB1, PVSB2, PVAPV, PVPAF, PVTOL, PVINS, PVRIN, PVBAK, 
    PFRTM, PFRTY, PVVFR, PVBSE, PVMIN, PVMAX, BSRCM, BSRCY, BPT01, 
    BPT02, BPT03, BPT04, BPT05, BPT06, BPT07, BPT08, BPT09, BPT10, 
    BPT11, BPT12, BPT13, BPL01, BPL02, BPL03, BPL04, BPL05, BPL06, 
    BPL07, BPL08, BPL09, BPL10, BPL11, BPL12, BPL13, ATRCM, FARCM, 
    ATRCY, FARCY, APT01, APT02, APT03, APT04, APT05, APT06, APT07, 
    APT08, APT09, APT10, APT11, APT12, APT13, FAT01, FAT02, FAT03, 
    FAT04, FAT05, FAT06, FAT07, FAT08, FAT09, FAT10, FAT11, FAT12, 
    FAT13, APL01, APL02, APL03, APL04, APL05, APL06, APL07, APL08, 
    APL09, APL10, APL11, APL12, APL13, FAL01, FAL02, FAL03, FAL04, 
    FAL05, FAL06, FAL07, FAL08, FAL09, FAL10, FAL11, FAL12, FAL13, 
    QTRCM, QTRCY, QRT01, QRT02, QRT03, QRT04, QRT05, QRT06, QRT07, 
    QRT08, QRT09, QRT10, QRT11, QRT12, QRT13, QRL01, QRL02, QRL03, 
    QRL04, QRL05, QRL06, QRL07, QRL08, QRL09, QRL10, QRL11, QRL12, 
    QRL13, QTRJM, QTRJY, QJT01, QJT02, QJT03, QJT04, QJT05, QJT06, 
    QJT07, QJT08, QJT09, QJT10, QJT11, QJT12, QJT13, QJL01, QJL02, 
    QJL03, QJL04, QJL05, QJL06, QJL07, QJL08, QJL09, QJL10, QJL11,   
    QJL12, QJL13, PVSCM, PVSCY, PVRTM, PVRTY, PVRWM, PVRWY, ERLYM,   
    ERLYY, ERT01, ERT02, ERT03, ERT04, ERT05, ERT06, ERT07, ERT08,   
    ERT09, ERT10, ERT11, ERT12, ERT13, ERL01, ERL02, ERL03, ERL04,   
    ERL05, ERL06, ERL07, ERL08, ERL09, ERL10, ERL11, ERL12, ERL13,   
    LATEM, LATEY, LTT01, LTT02, LTT03, LTT04, LTT05, LTT06, LTT07,   
    LTT08, LTT09, LTT10, LTT11, LTT12, LTT13, LTL01, LTL02, LTL03,   
    LTL04, LTL05, LTL06, LTL07, LTL08, LTL09, LTL10, LTL11, LTL12,   
    LTL13, ONTMM, ONTMY, OTT01, OTT02, OTT03, OTT04, OTT05, OTT06,   
    OTT07, OTT08, OTT09, OTT10, OTT11, OTT12, OTT13, OTL01, OTL02,   
    OTL03, OTL04, OTL05, OTL06, OTL07, OTL08, OTL09, OTL10, OTL11,   
    OTL12, OTL13, PFRDT, PLRDT, PVPOC, PVRCQ, PVSLT, PVDLT, PVUOM,   
    PVCNV, PVCCD, PVFFC, PVDFC, PVDBC, PVM1C, PVM2C, PVDTC, PVWGT,   
    PVVOL, PVPCT, PVCRL, PVLK2, PVTF1, PVTF2, PVHZ1, PVHA1, PVFG1,   
    PVHZ2, PVHA2, PVFG2, PVHZ3, PVHA3, PVFG3, PVPDT, PVPTM, PVCTY,   
    PVMAN, PVSHP, PVCNT, PVAPP, PVO1F, PVRVC, PVINH, PVO2F, PVCLP,   
    PVSTF FROM popvm102
    There are only 297 fields in this file. I use this technique on several other multiple membered files with considerably more fields than this one and have never encountered this problem. Any Ideas?
    Last edited by tunaclone; Mar 28 '08, 05:46 PM. Reason: make it more readable
  • luiscolorado
    New Member
    • Jan 2010
    • 1

    #2
    Maybe it's not the number of fields, but the size of them. Somebody suggested to use the reorganizae physical file... I guess that could work. By the way, V5R1 is notorious due to the abundance of bugs. If you can, upgrade to a later version.

    Comment

    Working...