Allen-Bradley PLC-5 MAP/OSI, User Manual, Page: 85 / 135

Chapter 5
Addditional and Advanced
Programming Techniques
5-14
The same rules apply for deleting domain–scope variable that apply for
defining them. For the rules, see the section titled Rules for Specifying
Domain–specific Scopes, earlier in this chapter.
Within the SET and the MOVE command lines, you have the opportunity
to specify the scope of an MMS named variable. If you do not specify the
scope of the MMS named variable, it is assumed that variable has
VMD–specific scope.
You can specify each of the scope types:
VMD–specific
application association (AA)
domain
The same rules for specifying scopes within the SET command line apply
to specifying them with the MOVE command line. The following sections
provide examples of the SET command first. We show examples of the
MOVE command after that.
Important: Domain variable scope is only supported by the OSI
coprocessor as a client, not a server. Therefore, you can specify all three
domain types in client–type applications, but only VMD and AA scope
will be accepted by server applications. For example, you can define (and
therefore transfer within SET) MMS named variables with VMD–specific
and AA scope in the OSI coprocessor, but not domain scope. You can,
however, define (and transfer) MMS named variables with domain scope
for other vendors’ devices (if supported by those devices).
Specifying VMD-specific Scope Within the SET Command Line
You can transfer MMS named variables of VMD–specific scope within the
SET command line.
You can specify VMD scope in two ways:
by placing /vmd/ just before the MMS named variable within the single
quotes in the SET command line.
NOT specifying any scope type. If no scope is specified, VMD scope is
assumed.
The following example shows how to specify VMD–specific scope:
Specifying MMS Named
Variable Scope Within SET
and MOVE
AB Parts