PK44799: RECEIVING ONCODE350 STRINGRANGE CONDITION RAISED IN GOC2CMR AT ENTRY POINT ADD_OBJECT AT STATEMENT 2080

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Object Comparison Tool encountered oncode350 stringrange
  condition in GOC2CMR at entry point ADD_OBJECT at statement 2080
  Also seen:
  IBM0441W  ONCODE=150  The STRINGSIZE condition was raised.
  From compile unit GOC2CMF at entry point ALTERED_ADDPK at
  statement 908 entry offset +00000F76 at address 2D2B556A.
  
  From compile unit GOC2CMF at entry point COMPARE_TABLES at
  statement 38
  

Local fix

• A possible circumvention to this issue is to manually define
  the sort work files (SCRWWK01-xx) as:
  The JCL cards used are :
  //SRCSWK01 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //SRCSWK02 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //SRCSWK03 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //SRCSWK04 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  .
  Additional symptoms: oncode150
  //SRCSWK05 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //SRCSWK06 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //SRCSWK07 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //SRCSWK08 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //TGTSWK09 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //TGTSWK10 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //TGTSWK11 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  //TGTSWK12 DD UNIT=(SYSDA),SPACE=(CYL,(02500,00500),,,ROUND)
  .
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: In R710 & R720,when user does DDL to         *
  *                 DDL compare of large SAP files.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Oncode 350 occurs in GOC2CMR when       *
  *                      preparing ALTER and CREATE set of       *
  *                      statements to be written in changes     *
  *                      file. additional symptom sort error     *
  *                      'SORT CAPACITY EXCEEDED ' is seen in    *
  *                      when performing DFSORT of source and    *
  *                      target version files.                   *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  The procedure which results in Oncode 350 is been corrected.
  SIZE parameter is added to existing SORT FIELDS for DFSORT to
  overcome 'SORT CAPACITY EXCEEDED ' error.
  

Problem conclusion

• The problem is been fixed both in V7.1 and V7.2.
  

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:

Modules/Macros

•    GOC2CMP  GOC2CMR  GOC2DTC
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R710 PSY UK36525

     UP08/05/28 P F805

• R720 PSY UK36526

     UP08/05/30 P F805

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.