HP 3000 Manuals HP 3000 Manuals
Modifying Directives
You can use a text editor to create or modify PARM.SCOPE.SYS. The
following rules and conventions apply:
* Specify a directive only if you want to override a default
parameter.
* Begin each line in the PARM file with a PARM file directive. PARM
file values cannot be entered by themselves.
* Enter the directives into the PARM file in any order. Order is
not important, with the following exceptions:
* If a directive is entered more than once, the last one
entered is used.
* The FILE, INTERACTIVE, BATCH, USER, QUEUE, and SERVICE
LEVELS directives must follow the APPLICATION directives
that they define.
* The IF, THEN, FINISH, and REPEAT directives must follow the
ALARM directive they define.
* Use uppercase or lowercase letters or both for all directives and
parameters.
* Use blanks or any nonalphanumeric characters (such as semicolons,
commas, and equal signs) to separate parameters in each statement.
NOTE Since commas are allowed within the parameter string in the USER
parameter, they cannot be used to separate different logon strings.
You must use another character (such as a space) to separate
parameters or use a separate USER line for each logon.
* Comment the PARM file if you like. Blank lines and any lines
beginning with an asterisk (*) will be ignored.
To change configuration directives, do the following:
* Create or modify the PARM file in the SCOPE.SYS group on the HP
3000.
* Stop and restart SCOPE(XL) or use the UTILITY program to issue the
SCOPE NEWPARM command.
Starting SCOPE(XL)
Start SCOPE(XL) by streaming the job SCOPEJOB.SCOPE.SYS. Do this by
typing the following:
STREAM SCOPEJOB.SCOPE.SYS
Stopping SCOPE(XL)
There are three ways to stop SCOPE(XL) from collecting data:
* Log on as MANAGER.SYS and run the UTILITY program. Issue the
following command:
SCOPE KILL
You will be asked to confirm your request to stop SCOPE(XL). If
you confirm, UTILITY issues a programmatic command to stop data
collection. It can take as long as 60 seconds to end the
collection process. UTILITY notifies you when this happens.
This is the method of choice and results in the normal termination
of data collection.
* Purge the file RUN.SCOPE.SYS.
Each time SCOPE(XL) is executed, it creates a file called RUN in
its logon group. Once a minute, Performance Collection Software
checks to see if this file is still present. If it is absent,
Performance Collection Software terminates normally. Normal
termination means that whatever remains in the collection job
stream will then execute.
* Use the ABORTJOB command to abort the SCOPEJOB job stream.
The rest of the collection job stream is not executed. This is
not the preferred method for terminating collection.
Reminder SCOPE(XL) should run continuously. You should only stop it if
you are preparing to shut down your system, updating the
Performance Collection Software host software to a new release,
changing the size of a Performance Collection Software log
file, or performing a system backup and want to include the
Performance Collection Software log files.
Hint The easiest way to stop the SCOPE(XL) collector as a part of
another batch job (for example as part of the full system backup
job) is to issue the SCOPE KILL command in UTILITY. This command
pauses until the collector terminates insuring successful shutdown
before the job stream continues. The following command will stop
the SCOPE(XL) collector if executed by a user with SM or OP
capability:
:RUN UTILITY.SCOPE.SYS;INFO="SCOPE KILL"
When finished, the batch job can then restart the SCOPE(XL)
collector by streaming SCOPEJOB:
:STREAM SCOPEJOB.SCOPE.SYS