Suspending Oxs Processes: suspend
The suspend application causes OOMMF Oxs processes (Oxsii and Boxsi) to write
out checkpoint (.restart) files and exit. This allows jobs to be
resumed at a later time via the Oxsii/Boxsi restart
controls. The suspend application is the equivalent of the
Oxsii/Boxsi interactive interface Suspend menu option,
but allows targeting of multiple Oxs processes.
Launching
The suspend command line is:
tclsh oommf.tcl suspend [standard options] [-account name] \
[-hostport port] [-pid] [-q] [-show] [-shownames] [-test] \
[-timeout secs] oid [...]
where
- -account name
- Specify the account name. The default is the same used by
mmLaunch:
the current user login name, except on Windows 9X, where the dummy
account ID “oommf” may be used
instead.
- -hostport port
- Use the host server listening on port. Default is set by the
Net_Host port setting in oommf/config/options.tcl, or by
the environment variable OOMMF_HOSTPORT (which, if set,
overrides the former). The standard setting is 15136.
- -pid
- Select processes by system pid rather than OOMMF oid.
- -q
- Quiet; don't print informational messages.
- -show
- Don't suspend anything, just print matching targets.
- -shownames
- Don't suspend anything, just print nicknames of matching targets, where
nicknames are as set by OOMMF command line utility
nickname
or the MIF 2.1 Destination
command.
- -test
- Don't suspend anything, just test that targets are responding.
- -timeout secs
- Maximum time to wait for response from servers, in seconds. Default
is five seconds.
- oid ...
- List of one or more oids (OOMMF ID's), application names, nicknames,
or keywords “oxsii”, “boxsi”, or “all”. Glob-style wildcards
may also be used. This field is required (there are no default
suspend targets). If the -pid option is specified then numbers
are interpreted as referring to system process ID's rather than
OOMMF ID's.
The suspend command only affects Oxs processes, that is,
Oxsii and Boxsi. The filenames of the resulting checkpoint
files (.restart) can be found in the corresponding log files
(default oxsii.log and boxsi.log, respectively).
OOMMF Documentation Team
September 30, 2025