HP System Dictionary/XL SDMAIN Reference Manual (32256-90001)

4- 69

remote system name in the dictionary name. For example, the DEFINE command could be speciﬁed in the

following form:

DEFINE DICTIONARY=SYSDIC.PUB.SYS:NODEB;

It is also possible to use a ﬁle equation to completely identify the remote dictionary, as shown in the

following example.

FILE RDICT1=SYSDIC.PUB.CORPINFO:REMOTESYS

where RDICT1 would be passed to the DICTIONARY parameter when using the DEFINE command, as

shown in the following example.

DEFINE DICTIONARY=RDICT1

RUNNING WITH DS3000

When either the local or remote system (or both) is a DS3000 node the above methods of addressing the

remote dictionary do not work. Instead, the device number of the remote node must be used, as shown in

the following example.

FILE RDICT1=SYSDIC.PUB.CORPINFO;DEV=17#

where 17 is the device number of the remote system, and must be known to the user. The DEFINE

command can then be used as follows:

DEFINE DICTIONARY=RDICT1

NOTE The dictionary on the remote system must be compatible with the System Dictionary

software on the local system, that is, it must be the same version. If it is not, the DE-

FINE command will fail.

Note also, that as with any subsystem or program being accessed on a remote system, the performance of

System Dictionary is likely to be slower than when run on a local system.

Example

The ﬁrst of the following examples opens the dictionary sysdic for the scope manager in customization

open mode. The password Mgr* allows access to the scope.

The second of the following examples changes the current scope leaving the dictionary open in the same

state otherwise. Note that the password was prompted for (with echo off) since the SCOPE keyword clause

is speciﬁed without a PASSWORD clause.

>DEFINE DICTIONARY = sysdic;

>>SCOPE = manager;

>>PASSWORD = Mgr*;

>>OPEN-MODE = customization.

>DEFINE SCOPE = da.

Scope Password>>