Working with logsets

MainView for Java Environments logs data in multiple logsets.  Allocation and retention of a logset is controlled by the BBIPARM member MJELGnxx:

  • n represents the type of data contained in the logset. Possible values are:
    • A, all JVM CPU data
    • G, SMF garbage-collection data
    • C, SMF CPU data
    • V, environmental data
    • L, loaded classes data
    • O, object allocation data
  • xx represents the suffix of the logset. The default logsets use the suffix 00.

The logset names are MVJEn_xxxx:

  • n, as described above.
  • xxxx, representing the NGL ID

You will see logsets 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 MainView for Java Environments. If you want 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 MainView for Java Environments PAS starts, it searches for logset definitions with the new suffix in the UBBPARM data set. If the PAS does not find all of the required logsets with the new suffix, the remaining logsets default to 00 logset definition members.

Example

The PAS requires six logsets. You create two new logset members with the suffix yy and specify MJELOG=yy. When you restart the PAS, it responds as follows:

  • Searches for members with the yy suffix and finds two members
  • Requires an additional four logset members
  • Uses four default logset members with the suffix 00


Related topic

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments