load

Purpose

Load a Binary Model file.

Synopsis

procedure load(mo:Model)

procedure load(mo:Model, bimf:string|text)

procedure load(mo:Model, mr:Model)

procedure load(mi:Mosel, mo:Model, bimf:string|text)

procedure load(mi:Mosel, mo:Model, bimf:string|text, opt:string|text, pass:string|text, pke:string|text, kls:string|text)

Arguments

Model object to be initialized

Model object used as a reference

bimf

Bim file name

The instance on which the model will be run

opt

Loading options (may be separated by spaces or '-' symbols):

"c"	Check signature (if the file is signed)
"V"	If the file is signed, load it only if the signature is valid
"T"	Load only signed files with a valid signature
"F"	The argument pass is a file name (not the password itself)
"l"	Do not load required packages

pass

Password or password file (for encrypted bim files)

pke

Private key file (for encrypted bim files)

kls

File of public keys

Further information

1. This procedure initializes the model mo with the bim file bimf. If mo has already been initialized, the model it references is unloaded before trying to load the new file (note that this operations fails if the model is running). If the file bimf cannot be accessed or one of the required modules cannot be loaded, the procedure generates an IO error (which may be intercepted if the control parameter ioctrl is true).

2. When loading a model from a separate Mosel instance, it is important to keep in mind that the operation is performed in the environment of this instance (in particular its current working directory) and file names should be specified appropriately (the rmt: IO driver can be particularly helpful in this context).

3. The argument kls is a list of public key files ( i.e. each line of the file is a key file name): when a signed bim file is loaded, its signature is checked with the keys listed in this file. If this argument is not specified, the signing key is searched in the default public keys directory located at getparam("ssl_dir")+"/pubkeys".

4. Packages required for the loading of a model are located using the list of prefixes defined by the control parameter bimprefix (See section Directive uses).

5. When invoked with a single argument this routine creates a new model from the one being executed (without using any bim file): this clone can access data shared by its master model (see Section Data sharing between models). Similarly, when a model is used in place of a bim file the new generated model is a copy of the provided reference model. Note that all copies of a given model share the constant information (like constant strings or the code segment) of the reference model. As a consequence, during a debugging session, setting a breakpoint in a model loaded this way also installs the same breakpoint in all other models coming from the same source (including the reference model).

Contents

Index

Glossary

Search Results

load