Product Information > JADE Schema Load Utility User’s Guide > Chapter 1 - Using the Schema Load Utility > Loading a Schema and Forms in Batch Mode

Loading a Schema and Forms in Batch Mode

The jadloadb program enables you to automate the Schema Load utility by running it in batch mode. Run the batch Schema Load utility (for example, from a command script), specifying the following.

jadloadb path=database-path
         [ddbFile=forms-file-name.ddb]
         ini=initialization-file-name
         [allowCircularPackages=boolean-value]
         [clearRestart=boolean-value]
         [commandFile=command-file-name]
         [compileUnchangedMethods=boolean-value]
         [createDeltaIfMissing=boolean-value]
         [deleteIfAbsent=boolean-value]
         [deleteMethodsIfAbsent=boolean-value]
         [deletePropertiesIfAbsent=boolean-value]
         [deleteSchema=schema-name]
         [delta=delta-name]
         [dontSaveSources=boolean-value]
         [executeSchema=RootSchema executeClass=Schema
          executeMethod=_removeSourceFromSchema executeParam=schema-name]
         [ignoreEmptyMethods=boolean-value]
         [initiateTransition=boolean-value]
         [loadStyle=currentSchemaVersion|latestSchemaVersion|
                    onlyStructuralVersioning]
         [noReorgRecovery=boolean-value]
         [overridePatchVersion=patch-version-number]
         [production=boolean-value|nochange]
         [reorgAllowUpdates=boolean-value]
         [replayableReorg=boolean-value or default]
         [reportDefnFile=report-definitions-extract-file-name.rwr]
         [reportFoldersFile=report-folders-extract-file-name.rwf]
         [reportFormatsFile=report-formats-extract-file-name.rwo]
         [reportLoadAllFile=report-all-extract-file-name.rwa]
         [reportReplaceView=boolean-value]
         [reportUsersFile=report-users-extract-file-name.rwu]
         [reportViewFile=report-view-extract-file-name.rwv]
         [schemaFile=schema-file-name.scm]
         [server=singleUser|multiUser]
         [showProgress=boolean-value]
         [suppressReorg=boolean-value]
         [targetSchema=schema-name [subschemaOf=schema-name]]
         [unversionAllSchemas=boolean-value]
         [unversionSchema=boolean-value]
         [userName=user-name]
         [waitForReorg=boolean-value]
         [help]

The following is an example of the command for loading the Test schema.

jadloadb path=d:\jade\system schemaFile=d:\jade\scm\test.scm ddbFile=d:\jade\scm\test.ddb dontSaveSources=true ini=d:\jade\myjade.ini deletePropertiesIfAbsent=true loadStyle=onlyStructuralVersioning replayableReorg=true compileUnchangedMethods=true

As the batch Schema Load utility does not read parameter values (for example, the IniFile and Path parameters) from the [JadeLoader] section of the JADE initialization file, you must specify all values on the command line if you do not want to use default values.

If a schema load is attempted when a reorganization is in progress, the load fails. For details about reorganizing schemas, see "Reorganizing Your Schema", in Chapter 3 of the JADE Development Environment User’s Guide.

The batch Schema Load utility program displays a progress report of each phase of the load operation. Standard load information is output to stdout and error information is output to stderr. (For details about displaying and redirecting the output from JADE batch utilities, see the DisplayApplicationMessages, LogServer, and UseLogServer parameters under "JADE Log Section [JadeLog]", in the JADE Initialization File Reference.)

An error is returned if a file listed in a multiple (.mul) file does not exist.

At the end of the load operation, the running display provides a completion report. If the jadloadb executable program fails, a non-zero exit code is returned and an error message is displayed; for example, if the database directory was invalid.

Detailed results of the loading of files extracted from the JADE Report Writer, including the success or otherwise of the load, are logged to the jadereportwritern.log file in the log directory.

If an exception occurs during the load process, the exception text is output to the console window and the exit code from the process is non-zero.

An exception (that is, 8510 – Methods in error were detected by the schema load) is raised if the batch schema load process detected methods that are in error. Although this is a warning only and the loading of the schema has completed, you should correct the methods that are in error and then run the batch schema load again.

The batch Schema Load program parameters are described in the following subsections.

path

ddbFile

ini

allowCircularPackages

clearRestart

commandFile

Delete Instances Command

Delete Class Command

Rename Class Command

Move Class Command

Create DbFile Command

Delete DbFile Command

Remap Class Command

Delete Interface Command

Rename Interface Command

Delete Property Command

Rename Property Command

Delete Method Command

Delete Constant Command

Delete GlobalConstant Command

Delete GlobalConstantCategory Command

Delete ExternalFunction Command

Create Locale Command

Modify Schema Command

Rename Schema Command

Delete Schema

Delete Locale Command

Delete Package Command

Delete LocaleFormat Command

Delete TranslatableString Command

Delete WebServiceConsumer Command

Exclude Table Command

Exclude Column Command

MoveInstances Command

compileUnchangedMethods

createDeltaIfMissing

deleteIfAbsent

deleteMethodsIfAbsent

deletePropertiesIfAbsent

deleteSchema

delta

dontSaveSources

execute{elements}

Stripping Method Source Code

Unloading All Report Writer Data to a Single File

ignoreEmptyMethods

initiateTransition

loadStyle

noReorgRecovery

overridePatchVersion

production

reorgAllowUpdates

replayableReorg

reportDefnFile

reportFoldersFile

reportFormatsFile

reportLoadAllFile

reportReplaceView

reportUsersFile

reportViewFile

schemaFile

server

showProgress

subschemaOf

suppressReorg

targetSchema

unversionAllSchemas

unversionSchema

userName

waitForReorg

help