To configure the arm.cfg

Edit the following parameters in the arm.cfg file. The arm.cfg file is located at $LAWDIR/system/arm.cfg
Parameter Description
USEWASCORR Whether or not to use the WebSphere correlator. The default is TRUE. Lawson recommends this setting as it enhances the display of data in the Enterprise Workload Manager.
UPDINTERVAL How often in seconds that the system will check the setup and filtering parameters. The default is 10.
TRACELEVEL

Match this to the value that you selected for the Trace Level field in the WebSphere administrator.

  • To match HOPS, enter HOPS or 1.

  • To match DEBUG, enter DEBUG or 3.

  • To match a value of none, enter no value or 0.

TRANS Set to ON or TRUE to monitor the Lawson transactions in the Java layer. If set to anything but ON or TRUE, transaction monitoring will turn off at the Java layer (monitoring will still include the transaction processing occurring through lacobrts until unldarmcfg is run).
USERNAME

The default is an asterisk (*), which allows the tracking of the transactions of all users.

- or -

Type an OS user account name (for example, jdoe) or a long name of a user, such as John_Doe, with any spaces replaced by an underscore, to track only those transactions performed by that user.

You can add up to five (5) total USERNAME parameter lines.

FORMID

The default is an asterisk (*), which allows the tracking of all update programs.

- or -

Type the name of the form ID to track a set of forms, such as CUO1.

- or -

Type the two-letter system code with an asterisk (*), such as HR* to track all forms that have that system code as a prefix.

You can add up to five (5) total FORMID parameter lines.

ARMLOG ON or OFF, depending on whether you want to store debug data.
ARMLIBPATH

You must set this parameter to the entire path and the full name of the library to be used. If the library cannot be located, cannot be loaded, or the functions cannot be attached, an error message is logged in $LAWDIR/system/arm.log.

The default is $GENDIR/bin/libarm4.ext.. Look to your third-party, ARM-compliant product for the specific path and library.