Published Release Notes

Data schema error on z/OS split schema upgrades from versions before Pega 7.1.8

When upgrading to a split schema on Pega 7.x with IBM DB2 for z/OS, you see an error during the data schema upgrade when the system tries to drop the PRPC_Updatescache procedure. Because triggers on rules tables use PRPC_Updatescache, you must use the ZOSDisableTriggerScripts to disable these triggers before you update the data schema.

1. Follow the instructions in the Pega 7 Platform Upgrade Guide to upgrade the rules schema, but stop immediately before you upgrade the data schema with the upgrade.bat or upgrade.sh script. The Pega 7 Platform Upgrade Guide is on the Support > Deployment Guides page.
2. Copy the contents of the <distribution>\ResourceKit\ZOSDisableTriggerScripts directory into the <distribution>\scripts\ directory.
3. Run fixZosTriggers.bat or fixZosTriggers.sh with the following arguments:
   --action preupgrade
--dataschema <data schema name>
   --oldrulesschema <old rules schema name. If you are upgrading from a single-schema system, this is the data schema name.>
   --newrulesschema <new rules schema name>
   --automaticddl <Optional. Set to true to automatically apply the disable trigger SQL scripts.>

   For example:
   fixZosTriggers --action preupgrade --dataschema pegadata --oldrulesschema pegarules --newrulesschema newrules --automaticddl false

4. If you did not set --automaticddl to true in the previous step, run the <distribution>\schema/disable.sql script to manually disable the trigger SQL scripts.
5. Run the data schema upgrade as described in the Pega 7 Platform Upgrade Guide.

Naming pattern changed for file data sets

File data sets are used to import from and export data to a file repository. In case of data export, prior to version 8.6.3, the first file exported had the same file name that was provided by the user in the data set, and any subsequent file exported to the repository had a unique identifier appended to it. Starting in Pega Platform version 8.6.3, each file has a unique identifier, automatically generated based on the data flow node, thread ID, and timestamp.

Upgrade impact

If your process to consume output files expects files with a specific name, it may not be able to process the resulting files correctly.

What steps are required to update the application to be compatible with this change?

If you have configured the process before updating to Pega Platform version 8.6.3, but the exported files are no longer recognized by downstream processing logic after the upgrade, ensure that the downstream tool is configured to recognize the files by a pattern rather than the full name. For example, when referring to files exported to the repository, use the * character to indicate a pattern instead of using the full file name. For example, use Export*.csv to refer to the files.