Job Management Partner 1/Performance Management - Agent Option for Enterprise Applications Description, User's Guide and Reference

[Contents][Glossary][Index][Back][Next]

6.3.2 Settings

Specify the settings in the environment parameters file in the following format:

[section]
label=value
label=value
...
...
[section]
label=value
label=value

Notes
  • Do not specify any unneeded characters, such as spaces at the beginning of a line or before and after an equals sign (=).
  • The values specified in section and label are not case-sensitive.
  • A line beginning with a semicolon (;) is treated as a comment.

The following tables describe the contents of each section in the environment parameters file.

Organization of this subsection
(1) TARGET section
(2) EXTRACTFILE section
(3) FORMAT section
(4) TRACE section
(5) CONNECT section

(1) TARGET section

The TARGET section specifies information that identifies the CCMS alert information to be extracted.

Table 6-1 Values permitted in the TARGET section

Label Description Permitted values Default value
MONITOR_SET# Monitor set name (name displayed as CCMS monitor set on the SAP system Alert Monitor (transaction code RZ20)) 1-60 single-byte alphanumeric characters SAP CCMS Monitor Templates
MONITOR# Monitor name (name displayed in the tree of the CCMS monitor set on the SAP system Alert Monitor (transaction code RZ20)) 1-60 single-byte alphanumeric characters Entire System

#
Specifying multiple targets is not permitted. To monitor multiple monitors, use the CCMS function of the SAP system to combine all the targets to be monitored into a single monitor, and then monitor this monitor from PFM - Agent for Enterprise Applications.

(2) EXTRACTFILE section

The EXTRACTFILE section specifies information about the file to which CCMS alert information is to be output.

Table 6-2 Values permitted in the EXTRACTFILE section

Label Description Permitted values Default value
SIZE Size of output file:
  • 0: Maximum value for the system#1
  • 1-65535: Wraparound within the specified size (in kilobytes)
 0-65535 1024
X2PATH Path to the output file#2, #3 1-255 single-byte alphanumeric characters. If a relative path is specified, it is treated as the path relative to the instance environment directory.
  • In Windows: log\ALERT
  • In UNIX: log/ALERT

#1
This is 0x7FFFFFFF (about 2 gigabytes), which can be expressed as a 32-bit signed integer.

#2
A management file named output-file-name.ofs is created in the same directory as the specified output file (for example, if ALERT is specified as the output file name, ALERT.ofs is created as a management file in addition to the ALERT file). If you delete this output file, make sure that you also delete the management file.

#3
If the default storage location is changed, the jpcras command cannot collect the information in the event of a problem.

(3) FORMAT section

The FORMAT section specifies the output format of the CCMS alert information.

Table 6-3 Values permitted in the FORMAT section

Label Description Permitted values Default values
COLUMN Output format of CCMS alert information Field ID. For details about the field ID, see 10. Commands. Column 1: <ALERTDATE>
Column 2: <ALERTTIME>
Column 3: <MTSYSID>
Column 4: <MTMCNAME>
Column 5: <OBJECTNAME>
Column 6: <FIELDNAME>
Column 7: <VALUE>
Column 8: <SEVERITY>
Column 9: <MSG>
TIMEZONE Time zone specification for the time information of the following field IDs
  • <ALERTDATE>
  • <ALERTTIME>
  • <STATCHGDAT>
  • <STATCHGTIM>
  • UTC
    The command will output time information in UTC (Coordinated Universal Time).
  • LOCAL
    The command will output time information in the local time of the user who executes the command.
 UTC

(4) TRACE section

The TRACE section specifies information about the message log and data log that store the history of CCMS alert information extraction.

Table 6-4 Values permitted in the TRACE section

Label Description Permitted values Default value
MSGLOG_LEVEL Message log collection level for saving application trace information:
  • 0: Do not collect
  • 1: Collect only errors
  • 2: Standard
  • 3: Details
  • 4: Debug
 0-4 2
MSGLOG_SIZE File size for collecting the message log:
  • 0: Maximum value for the system#
  • 1-65535: Wraparound within the specified size (in kilobytes)
 0-65535 512
MSGLOG_DIR Message log file (jr3alget.log) collection-target directory (Cannot be changed) log
DATALOG_LEVEL Data log collection level for saving various types of data information for applications:
  • 0: Do not collect
  • 1: Collect only errors
  • 2: Standard
  • 3: Details
  • 4: Debug
 0-4 2
DATALOG_SIZE File size for collecting the data log:
  • 0: Maximum value for the system#
  • 1-65535: Wraparound within the specified size (in kilobytes)
 0-65535 512
DATALOG_DIR Data log file (jr3alget.dat) collection-target directory (Cannot be changed) log

#
This is 0x7FFFFFFF (about 2 gigabytes), which can be expressed as a 32-bit signed integer.

(5) CONNECT section

The CONNECT section specifies information needed to establish RFC connection with the SAP system.

Table 6-5 Values permitted in the CONNECT section

Label Description Permitted values Default value
LANG User language used for connection 2-byte ISO ID or 1-byte language key that is used in the SAP system:
  • EN or E
 None
CODEPAGE Code page used to convert character codes in the Unicode version of the SAP system at the destination Value combined with the language code in the LANG label# None

#
Set the LANG and CODEPAGE labels in the applicable combination shown below. If any other combination of language and code page is specified, an encoding error might occur in the information acquired from the SAP system.

Table 6-6 Combination of language and code page specifications

Connection-target SAP system Connection language Language (LANG) Code page (CODEPAGE)
Unicode version English EN No need to specify. If you specify a code page, specify 1100.
Non-Unicode version English EN No need to specify. If you specify a code page, specify 1100.
If you omit specification of the LANG label, the user language defined in the connection-target system is assumed.
If you omit specification of the CODEPAGE label, the default code page in the connection-target system is assumed.

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2010, Hitachi, Ltd.