Siemens BS2000/OSD Manual de usuario descargar pdf (Pagina 9)

o The SYSREP.SM2.150 loader must be generated from the

SYSRMS.SM2.150 delivery set with the product RMS.

o SM2 expects the following files:

SPMLNK.SM2.150 or SYSLNK.SM2.150,

SYSREP.SM2.150 and

SYSNRF.SM2.150

under a standard user ID (defined with the DEFLUID system

parameter) which must have the SWMONADM (Software Monitor

Administration) privilege.

TSOS has this privilege by default. If the three files are

set up under a different user ID, the SWMONADM privilege

must be assigned to this user ID and the name of the user ID

must be changed accordingly in the subsystem declaration.

o The SYSMES.SM2.150 message file must be merged in using the

BS2000 /MODIFY-MSG-FILE-ASSIGNMENT command.

o The SDF SYSSDF.SM2.150 syntax file must be registered.

This is done with the following command:

/MODIFY-SDF-PARAMETER SCOPE=*PERMANENT, -

/SYNTAX-FILE-TYPE= -

/*SUBSYSTEM(NAME=SYSSDF.SM2.150,SUBSYSTEM-NAME=SM2)

o The file SYSSSC.SM2.150 must not be modified, apart from the

ID under which the files required for dynamic loading are

stored. The file contains the SM2 subsystem declarations and

is required to update the DSSM catalog.

3.4 Product use

o The SM2 subsystem is loaded and started the first time it is

called under a user ID with the SWMONADM privilege. Only the

SM2 modules required for running the basic functions are

loaded.

o However, the SM2 subsystem can also be loaded via the DSSM

/START-SUBSYSTEM SUBSYSTEM-NAME=SM2 command. SM2 can then be

started under any desired ID.

o The SM2 subsystem SM2 exists until it is unloaded via the

DSSM command

/STOP-SUBSYSTEM SUBSYSTEM-NAME=SM2

o Unconditional unloading using /STOP-SUBSYSTEM

SUBSYSTEM-NAME=SM2,FORCED=YES is possible but should only be

used if problems are encountered.

o The SUBSYSTEM-MANAGEMENT privilege is required for the DSSM

/START-SUBSYSTEM and /STOP-SUBSYSTEM commands.

1 2 3 4 5 6 7 8 9 10 11 12 13 14

Sin comentarios

Siemens BS2000/OSD Manual de usuario Pagina 9