HP 3000 Manuals HP 3000 Manuals
SCOPE
[STATUS ]
SCOPE [KILL ]
[NEWPARM ]
[NOTE [message]]
The SCOPE command allows you to communicate with the SCOPE(XL) data
collector as it runs. If the Performance Collection Software data
collector is not running and logged on to the SCOPE.SYS group, all SCOPE
commands indicate that SCOPE(XL) is not running and the commands fail.
NOTE To issue a command to the SCOPE(XL) data collector, you must have
SM or OP capability and execute access to files in the SCOPE.SYS
group.
If the SCOPE(XL) collector is running, the SCOPE command looks for
commands once a minute. You may have to wait as long as 60 seconds for
SCOPE(XL) to recognize and act on any command you issue.
Commands that expect responses back from SCOPE(XL) wait until the
response is received (or no more than 90 seconds), during which time you
cannot enter additional UTILITY commands.
If the user running UTILITY does not have write and save access to files
in their logon group, it may be impossible to retrieve information. A
local response file called SCOPEOUT is created to receive data from
SCOPE(XL). If two users in the same group attempt to receive data from
SCOPE(XL) at the same time, the first user to create the SCOPEOUT file
succeeds. The second user fails and will get a file-create error on this
file.
SCOPE
The SCOPE command without a parameter quickly indicates whether SCOPE(XL)
is running. (This command may be executed by users without SM or OP
capability).
SCOPE STATUS
SCOPE with the STATUS parameter asks the currently executing SCOPE(XL) to
return its version number and data collection information.
Most of this report is similar to part of the SCAN report (initial PARM
file global information). Also, a report on the amount of disc space
used in the four main log files--LOGGLOB, LOGAPPL, LOGPROC, and
LOGDISC--is returned.
SCOPE KILL
SCOPE with the KILL parameter asks the currently executing SCOPE(XL) to
terminate in an orderly fashion. UTILITY will wait until SCOPE(XL)
terminates before continuing.
If you issue the SCOPE KILL command interactively, you are asked to
verify that you actually want to kill SCOPE(XL)--you are given a chance
to change your mind.
Batch execution of the SCOPE KILL command requires no further input.
Sample SCOPE KILL Task
You can use the SCOPE KILL command to stop SCOPE(XL):
SCOPE KILL
You are asked to verify this command:
KILL THE SCOPE COLLECTOR, ARE YOU SURE?
Respond with YES to kill SCOPE(XL).
You can also purge the RUN.SCOPE.SYS file to stop SCOPE(XL):
PURGE RUN.SCOPE.SYS
SCOPE NEWPARM
SCOPE with the NEWPARM parameter instructs SCOPE(XL) to reprocess its
PARM file. Any changes found in the PARM file are acted upon without
stopping and restarting the data collection job. (You cannot change the
system ID at this time.)
SCOPE NOTE
SCOPE with the NOTE parameter places a user note into the Performance
Collection Software global log file. Such notes may be viewed by
performing a SCAN with NOTES=ON or NOTES=100. If no message is entered,
you are prompted to enter a message (in interactive mode), or the job
terminates (in batch mode).
Sample SCOPE NOTE Task
You can add a message to the Performance Collection Software log file.
SCOPE(XL) must be running in order to execute this command.
SCOPE NOTE This will be a user-defined note.