Starting the System Object Model (SOM) subsystem
Use the START SOM command to start the distributed system object model (SOM) subsystem. This is the extension to the SOMobjects® product that allows programs to communicate with objects in other processes that reside in other address spaces or on other systems. Your installation may place this command in a COMMNDxx member of the logical parmlib data set.
Note: You must activate the OMVS address space before you issue a
START SOM command.
See "Configuring Your SOMobjects Environment"
in SOMobjects Configuration
and Administration Guide, GC28-1851, for more information on
what things you must do before starting SOM.
|
The parameters are:
- SOM
- The name for the SOM subsystem. It corresponds to the cataloged procedure in SYS1.PROCLIB that starts SOM.
- procedure_name
- Your installation's name for the SOM subsystem. The name must correspond to a procedure cataloged in SYS1.PROCLIB or to a data set concatenated to SYS1.PROCLIB. IBM® recommends that an installation use the name SOM. If your installation uses a different name, that name must be one to four characters long, begin with an alphabetic character (A-Z), contain only alphanumeric characters (A-Z or 0-9), and not conflict with any other subsystem name in the same system, or with the name of any system command.
- SUB=subsystem name
- Specifies the subsystem you designate to process the task, such
as MSTR (the master subsystem) or JES2 or JES3 to specify that subsystem's
scheduler. (Make sure to send all your output to a data set if you
specify MSTR.)
If you omit this parameter, the JES subsystem scheduler starts SOM. The resulting dependency on JES requires SOM to be stopped when stopping JES.
Example:
The following command starts the SOM subsystem:
S SOM