PH15343: EXTRACT USING ROW LIST FAILS WITH SYSTEM ERROR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Two issues are addressed in this APAR, first issue:
  
  IBM InfoSphere Optim System Error Structure - ErrCB
  ErrCB.ID=      ZZZERRCBZZ
  SysRel=        11.7.0
  DB2Rel=        1115(NFM)
  ErrCB.Type=    SYSTEM_ERROR
  ErrCB.AuxInfo=
  ErrCB.Code=    -1
  ErrCB.U.Msg=   PS ColDef not = Table PK ColDef
  Number of Function Entries=  5
    ErrCB.N(0).Src=     FOPXMAIN 20190215 PH07856D
    ErrCB.N(0).Func=    (003226) ADDKeysToPSTempTable
    ErrCB.N(1).Src=     FOPXMAIN 20190215 PH07856D
    ErrCB.N(1).Func=    (000960) DXDataExtract
  
  Second issue:
  
  Optim may not recognize an IMS logical relationship, this is
  experienced when including related tables in the AD and when
  displaying table relationships.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: 1) Optim for z/OS IMS users with primary     *
  *                 keys described by NUM fields                 *
  *                 2) Optim for z/OS IMS users with logical     *
  *                 relationships                                *
  ****************************************************************
  * RECOMMENDATION: Apply the provided fix.                      *
  ****************************************************************
  1) Optim creates an implicit column list when processing the row
  list.  Latter it compares that column list to the columns
  defined for the segment and fails.  This is because the implicit
  column list does not have correct column attributes when the
  column is for a legacy NUM field.
  
  2) Optim was limiting itself to using a single column to
  describe the relationship key.  In addition, it requires that
  the key columns be consistent between the logical child and
  logical parent.
  

Problem conclusion

• 1) The creation of the internal column list is corrected.
  2) Optim does not permits multiple columns to describe the
  relationship key.  However, columns comprising the relationship
  key must be consistent and sometimes the original copybook does
  not provide a consistent description.  Often group fields can be
  added to one or both of the tables to provide the consistency.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PH15344 PH15345

Modules/Macros

• FOP1ODRV FOP1OSFN FOP4PEMN FOP4TRCE FOP9APIM FOPCFPMN FOPCXLIB
  FOPHSTM  FOPK12   FOPMADDE FOPMAIN  FOPMAMAI FOPMARCN FOPMCBMN
  FOPMCDRT FOPMCENU FOPMCMAI FOPMCOFN FOPMCOLA FOPMCOLP FOPMDDDL
  FOPMDMAI FOPMDPRC FOPMDXTR FOPMECMN FOPMEMAI FOPMMCMR FOPMMJBS
  FOPMMUNU FOPMMUTL FOPMSELM FOPMTMDB FOPMUXIM FOPODPP  FOPOMN
  FOPRS10  FOPT0P10 FOPT30H  FOPTOP9W FOPTUO47 FOPUMCBT FOPZFBMN
  FOPZFMMN FOPZMAIN FOPZSUB
  

Fix information

• Fixed component name

  OPTIM MOVE FOR

• Fixed component ID

  5655V0700

Applicable component levels

• RB30 PSY UI65281

     UP19/09/13 P F909

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.