The optional executeMethod argument enables you to specify the name of a user‑defined schema whose JADE method source code you want stripped.
You must specify the executeSchema argument with a value of RootSchema, the executeClass argument with a value of Schema, the executeMethod argument with a value of _removeSourceFromSchema, and the executeParam argument with the name of your user schema from whose JADE methods you want source code stripped.
The syntax of the execute arguments in the jadclient command line is as follows.
jadclient path=database-path
ini=initialization-file-name
app=RootSchemaApp
schema=RootSchema
executeSchema=RootSchema
executeClass=Schema
executeMethod=_removeSourceFromSchema
executeParam=schema-name
The following example strips the source from all JADE methods in the TestBaseSchema schema.
jadclient path=d:\jadesystems\jade\system ini=c:\jade\jade.ini app=RootSchemaApp schema=RootSchema executeSchema=RootSchema executeClass=Schema executeMethod=_removeSourceFromSchema executeParam=TestBaseSchema
An error is returned if the schema with the name specified in the executeParam argument does not exist or if it is a system schema.
As these arguments are case‑sensitive, you must specify the JADE schema, class, method, and user schema names exactly. For example, TestBaseSchema is valid but if you were to specify executeParam=Testbaseschema, an error would be output.
You can specify only one user-defined schema for the removal of source code from all JADE methods. If you want to remove source code from methods in more than one schema (for example, subschemas and then their superschema), you must run separate copies of the jadclient program.