freezeSchemaFiles

The freezeSchemaFiles command changes the volatility of the _userint, _userscm, and _userxrf schema files to frozen.

Setting the file volatility to Frozen overrides object volatility for objects stored in that file.

Freezing schema files provides performance improvements, by reducing the number of lock and unlock operations and fetched user schema objects. This benefit is a result of ignoring implicit lock requests on those objects stored in the frozen schemas. For details about object volatility, refer to "Cache Concurrency", in Chapter 6 of the JADE Developer’s Reference.

Attempts to create or maintain any development objects (for example, all schemas, classes, methods, forms, and so on) are disallowed while the schema files are in a frozen state. An attempt to modify any such object raises exception 1106 (Cannot update a frozen object).

This also applies to maintenance activities outside the JADE development environment, including jadloadb batch JADE Database utility operations.

The syntax of the freezeSchemaFiles command in the jdbutilb command line is as follows.

jdbutilb path=database-path
         ini=initialization-file-name
         freezeSchemaFiles