Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

RAP import generates incorrect DDL for Sample database on z/OS

SA-51362

Summary



PRException occurs on importing RAP with tables mapped to a Sample database when generating the DDL.


Error Messages



252 INFO [stdout] (Log4j2-AsyncLoggerConfig-1) Caused by: com.pega.pegarules.pub.PRException: DB2 zOS logical database name must be specified for Next TableSpace Name routines. Missing setting for Sample.


Steps to Reproduce



Import Sample Data RAP file (for example, CPMHC_713_SampleDatabase).


Root Cause



In Pega 7.3.1, the ability to create tablespace and AUX tables DDL for a Db2 for z/OS database is added to the Import wizard. For a Database-Admin-DB-Name (D-A-DB-Name) rule for a Db2 for z/OS database, Dynamic System Settings (DSS) are required. For PegaRULES and PegaDATA databases, Dynamic System Settings are set up as part of an installation or upgrade. To use this feature for other D-A-DB-Name rules, the database configuration properties must be set up within Pega using prpcUtils.

Resolution



Perform the following local-change:

Specify the below parameter in the prpcUtils.properties file:

Settings For z/OS Config Import Tool

  1. Full path to file containing DB2 z/OS site-dependent properties (the required properties are in scripts/config/db2zos/DB2SiteDependent.properties).

    pega.zos.properties=<path to DB2SiteDependent.properties file>
  2. Create settings for #Data-Admin-DB-Names (for example, DBName1,DBName2).

    pega.zos.database.names=<comma-delimited list of D-A-DB-Names>
  3. Run the prpcUtils importZosConfig.


Suggest Edit

Published April 12, 2018 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us