HP 3000 Manuals HP 3000 Manuals
APPLICATION
APPLICATION {application name}
FILE=[filename]
INTERACTIVE=[filename]
BATCH=[filename]
USER=[job/session name,]{username.acctname}[,groupname]
QUEUE [execution priority]
OR
SERVICE LEVEL [FIRST=seconds ]
[RESPONSE=seconds]
where:
The application name parameter identifies an application that groups
multiple program files together and reports on their combined activities.
The application name is a string of up to 20 characters identifying that
application.
One or more application definitions should follow the APPLICATION
command. An application definition consists of combinations of FILE,
INTERACTIVE, BATCH, USER, or QUEUE parameters.
The OR parameter is used to separate multiple definitions for the same
application.
All application definitions apply to the last APPLICATION command
entered.
The parameters for application definitions fall into three categories:
File name: FILE
INTERACTIVE
BATCH
User logon: USER
Execution QUEUE
priority:
If a parameter from a category is used in an application definition, a
process will not belong to that application unless a match for that
category is made.
If no parameters in a category are used in an application definition,
then a process does not have to match that category.
For example, there can be any number of FILE and USER parameters
following an APPLICATION directive, but if there is no QUEUE parameter, a
process could belong to any queue and still belong to the application.
It would have to match at least one of the FILE parameters and one of the
USER parameters.
Or, as another example, if an application consisted of USER and QUEUE
parameters but had no FILE, INTERACTIVE, or BATCH parameters, then any
program file name could belong to the application as long as the
user logon and execution queue matched one of the USER and QUEUE
specifications.
Use the OR parameter when you want more than one application definition
to apply to the same application.
You can define up to 15 applications on MPE V and 31 applications on
MPE/iX. Performance Collection Software predefines an application called
OTHER that collects all processes not defined by APPLICATION directives
in the PARM file.
If a process file is included in more than one application, it is logged
in the first application in which it is defined.
APPLICATION=Order Processing
FILE=@.@.OFICPROD,@.@.PAPRPROD,@.@.SUPPLIES
APPLICATION=Office Products
FILE=@.FURNITUR.OFICPROD,@.ELECTRON.OFICPROD
Since @.@.OFICPROD is included in Order Processing, any programs in
@.FURNITUR.OFICPROD or @.ELECTRON.OFICPROD will be logged in the Order
Processing application, not in Office Products. However, if the order of
the applications is reversed, any programs in the groups FURNITUR and
ELECTRON in the OFICPROD account will be logged in the Office Products
application, not in Order Processing.
By default, no user applications are defined.
NOTE Since any process on the system can belong to only one application,
no process will be counted in more than one application. The PARM
file is processed in the order entered, and the first match of a
program name, user logon, and queue will define the application to
which a particular process belongs.
FILE=filename
The FILE parameter specifies which program files belong to an
application. It includes all interactive or batch executions of these
programs and applies to the last APPLICATION directive issued. An error
is generated if no APPLICATION directive is found.
The filename can be any of the following:
* A simple, fully qualified MPE file name. For example,
EDITOR.PUB.SYS
* A generic file name. For example,
VOODOO#.@.@
* A partially-qualified file name. For example,
SPOOK5
In this case, all groups and all accounts are assumed
(SPOOK5.@.@).
Multiple file names can be entered on the same line, separated by commas,
or in separate FILE parameters.
INTERACTIVE=filename
The INTERACTIVE parameter acts the same as the FILE parameter except it
signifies that only interactive executions of the program (sessions) are
included in the application class.
BATCH=filename
The BATCH parameter acts the same as the FILE parameter except it
signifies that only batch executions of a program (jobs) are included in
the application class.
USER=[job/session name,]{username.acctname}[,group]
The USER parameter identifies the job or session, user, account, and
group to be included in the application class.
* job/session name,
The job/session name is an optional part of a user logon that can
be used for identification. If this parameter is included, it
must be terminated by a comma. If this parameter is not supplied,
all job/session names are matched.
* username
The username specifies the name of the user as defined by the MPE
accounting structure.
* acctname
The accountname specifies the name of the logon account as defined
by the MPE accounting structure.
* group
The groupname specifies the logon group of a particular job or
session. It is optional, but if it is included, it must be
preceded immediately by a comma. If this parameter is not
supplied, all logon group names are matched.
NOTE Since commas are allowed within the parameter string in the USER
parameter, they cannot be used to separate one logon string from
another. You must use another character (such as a space) to
separate parameters or use a separate USER line for each logon.
QUEUE [L,A,B,C,D,E]...
Usually, the execution priority of a process is CS, DS, or ES. Special
accounts can log on or run programs with ;PRI=BS, whereas privileged mode
and system processes can place themselves in the AS or linear queues.
(Linear queue can be any priority you want, but it is not subject to the
normal priority adjustments of the MPE dispatcher.)
You can restrict processes in an application to those belonging to
selected execution priority queues using the QUEUE parameter. More than
one queue can be indicated. The following example specifies any process
running in either the DS or ES queue:
QUEUE=D,E
NOTE The AS and BS queues are special cases of the linear execution
queue. If you specify QUEUE=L, processes executing as AS or BS
priority are included. Specifying QUEUE=A,B is not the same as
specifying QUEUE=L since the linear queue can be outside the range
of the A and B queues.
A process with process-handling capabilities can change its execution
queue as it runs. A process's execution priority can be altered also by
an external tool, such as HP GlancePlus.
The process execution queue is sampled at the end of each 1-minute sample
interval. If the process changed queues, it can change applications.
All activity for a process during the 1-minute sample interval is assumed
to have occurred in the new queue and as such is attributed to the
application that matches the process at the end of each 1-minute sample
interval.
OR
Use the OR parameter to allow more than one application definition to
apply to the same application. Within a single application definition, a
process must match at least one of each category of parameters.
Parameters separated by the OR parameter are treated as independent
definitions. If a process matches the conditions for any definition, it
will belong to the application, as in the following example:
APPLICATION=CONSOLE
USER=OPERATOR.SYS
OR
USER=MANAGER.SYS
FILE=STORE.PUB.SYS,SYSDUMP.PUB.SYS
This defines an application (CONSOLE) that consists of any programs run
by the user OPERATOR.SYS plus two programs (STORE.PUB.SYS and
SYSDUMP.PUB.SYS), if they are executed by the user MANAGER.SYS.
SERVICE LEVEL [FIRST=seconds][RESPONSE=seconds]
The SERVICE LEVEL parameter defines the response time or times used in
measuring an application's service agreements. See appendix B for a
discussion of service levels.
Sample Application Definition
The following is an example of how an application can be defined:
APPLICATION=Program Development
INTERACTIVE=EDITOR.PUB.SYS, QEDIT.@.@, VOODOO#, TDP
USER=@.TEST @.@,TESTGROUP LABTEST,@.@
SERVICE LEVEL FIRST=1.0
APPLICATION=Other Editors
FILE=EDITOR.PUB.SYS, QEDIT.@.@, VOODOO#, TDP
APPLICATION=Compilers
FILE=COBOL@.PUB.SYS,FORTRAN.PUB.SYS,FTN@.PUB.SYS
FILE=PASCAL.PUB.SYS, SPL.PUB.SYS, RPG.PUB.SYS
APPLICATION=HP Products
FILE=@.PUB.SYS
The following is an example of how programs would be logged using the
preceding PARM file:
----------------------------------------------------------
| | | |
| Program | User Logon | Application |
| | | |
----------------------------------------------------------
| | | |
| EDITOR.PUB.SYS | GERRY.TEST | Program |
| | | Development |
| | | |
| EDITOR.PUB.SYS | SAM.SNEED | Other Editors |
| | | |
| HPSLATE.PUB.SYS | SAM.SNEED | HP Products |
| | | |
| PASCAL.PUB.SYS | GERRY.TEST | Compilers |
| | | |
| EDITOR.UTIL.SYS | GERRY.TEST | OTHER |
| | | |
----------------------------------------------------------
If the HP products' application in the previous example was defined
first, the first four examples would belong to it.