Working with logsets
- n represents the type of data contained in the logset. Possible values are:
- A—all JVM CPU data
- C—SMF CPU data
- E—JMX event data
- G—SMF garbage-collection data
- L—loaded classes data
- V—environmental data
- O—object allocation data
- Z—z/OS Connect EE request data
- xx represents the suffix of the logset. Default logsets use the suffix 00.
The logset names are MVJEn_xxxx:
- n, is as described for the member name.
- xxxx, represents the NGL ID.
Logsets are listed with this naming format in the PAS log. You can view and edit defined logset members on the PASPARM view.
Default logset definition members are shipped with the product. To change the parameters specified for a logset member, you must create a new member in the UBBPARM data set. You can then update the MJELOG parameter in MJEINIxx with the suffix of the new logset definition.
When the BMC AMI OpsMJE PAS starts, it searches for logset definitions with the new suffix in the UBBPARM data set. If the PAS does not find all of them, the remaining logsets revert to 00 logset definition members by default.
The following table describes the parameters in BBPARM member MJELGnxx.
Parameter | Default value | Description |
|---|---|---|
DSMIN=MinnumberofDataSets | 2 | (Required) Specifies the minimum number of data sets that constitute the logset Do not change this value unless requested by BMC Support. The minimum value is 2. Data type: numeric |
DSMAX=MaxNumberofDataSets | 3 | (Optional) Specifies the maximum number of data sets that constitute the logset Do not change this value unless requested by BMC Support. You can use the DSMAX parameter in conjunction with the RETENTION parameter to control the number of data sets allocated. If you do not specify a value for the RETENTION parameter, the DSMAX value takes the value specified in the DSMIN parameter by default. Data type: numeric |
RETENTION=[xx | 4] | 4 days | (Optional) Specifies how long BMC AMI Ops Monitor for Java Environmentsretains the data after being captured The RETENTION parameter controls both the number of log files that the NGL agent uses to record data and the number of log files that the NGL agent allocates during a logset start. NGL uses the RETENTION value to make sure that enough log files are allocated at logset startup to cover the retention period. The number of log files allocated is determined by the DSMIN and DSMAX parameter values or the actual number of log files in the NGL registry. If more log files are available in the NGL registry after the retention period elapses and the DSMAX parameter value is not yet reached, then NGL marks additional log files as candidates and allocates more log files to cover the retention period. Data type: Numeric or character. You can specify retention goals in days, hours, or minutes by using a D, H, or M suffix. If you do not provide a suffix, the default is D. |
SPACE= [30 | xxx] | 30 MB | (Required) Specifies (in megabytes) how much space BMC AMI Ops Monitor for Java Environments allocates for the logset and logspace We recommend that you allocate at least 30 MB. Data type: numeric |
DATACLAS | Not applicable | (Optional) Specifies the DFSMS data class to use when allocating the logset data set The DATACLAS element is used only if the repository data set does not yet exist. Data type: VARCHAR(8) |
STORCLAS | Not applicable | (Optional) Specifies the DFSMS storage class to use when allocating the logset data set Data type: VARCHAR(8) |
MGMTCLAS | Not applicable | (Optional) Specifies the DFSMS management class to use when allocating the logset data set Data type: VARCHAR(8) |
VOLSER | Not applicable | (Optional) Specifies the volume to use in allocating the log file or archive data set. Data type: VARCHAR(6) |