FOCUS AREAS

ARM - Application Response Measurement

%ARMJOIN

Inputs the six SAS data sets that are created by the %ARMPROC macro and creates data sets that contain common information about applications and transactions

Type: ARM post-processing macro

Syntax

%ARMJOIN(<option(s)>)

Options

LIBIN=
is the SAS data library input that contains the six data sets from %ARMPROC.
Default:  WORK
 
LIBOUT=
is the SAS data library output that contains the application and transaction data sets.
Default:  WORK
 
TXNDS=YES | NO
specifies whether the transaction data sets are created.
Default:  YES
 
UPDTDS=YES | NO
specifies whether the update data sets are created.
Default:  YES

 


Description

The %ARMJOIN macro inputs the six output data sets that are produced by %ARMPROC. It merges the information from those data sets to produce a variety of output data sets and views for efficient reporting of ARM data.

Note:   The %ARMJOIN macro does not work from SCL.  


Input

The input is the SAS data sets from %ARMPROC; therefore, you must run %ARMPROC before you run %ARMJOIN.


Output

The output is a single data set that contains information about applications, transaction data sets, update data sets, and two views.

The application data set is named APP and contains one observation for every application that is found in the input data. Each observation contains information such as application name, user ID, transaction counts, average application response time, and so on. Additionally, each observation contains a numeric variable APPNO that is the identifier of the related transaction or update data set that contains more detailed transaction information.

The transaction data sets are named TXN1, TXN2, TXN3, and so on. Each data set corresponds to a single application, and each observation represents a single ARM transaction that contains start/stop times, elapsed wall clock times, and CPU time.

The TXNVIEW view joins all transaction data sets and presents them as a single data set.

The update data sets are named UPDT1, UPDT2, UPDT3, and so on. Each data set corresponds to a single application and contains multiple observations for each ARM transaction. Each observation contains the ARM call datetime, an ARM call sequence ID, and, if applicable, elapsed time, CPU time, and update data.

The UPDTVIEW view joins all update data sets and presents them as a single data set.

The transaction data sets are more useful for analyzing individual ARM transactions because all information about a transaction is collapsed into one observation. However, the transaction data sets do not contain any information from %ARMUPDT calls.

The update data sets are similar to the transaction data set; however, information about a single transaction is spread over several observations. These data sets contain logged data buffer information from all %ARMUPDT calls.

Examples:

Example 1: Basic usage

 filename ARMLOG 'd:\armlog';
   %armproc();
   %armjoin();

Example 2: Supply LIBOUT= parameter

 finename armlog 'c:\arm\rawlog.dat';
 libname armout 'c:\armlib\';
  %armproc();
  %armjoin(libout=armout);