Information logs

The Metadata Analyzer generates logs showing the activity of the Metadata Server, collections, Learner, and Metadata Analyzer. The primary focus of these logs is to help you diagnose problems. The focus of the learner log is to determine whether programs have been successfully learned.

The logs

Each log is written to a text file that can be opened with a text editor, and shows the following information:

  • What you have requested of the Metadata Analyzer (not applicable to the Learner log)
  • What the Metadata Analyzer was able to accomplish
  • Error information to help you correct errors
  • Product and environment information that can be valuable to Customer Support when needed

Metadata Server logs

There are two types of server logs: a run log and a cumulative log. The run log is written to the console and to a text file located on the machine on which the Metadata Server is running in a Logs directory in the UserDataPath specified during the installation (which is available in the About dialog box). Users who are remote to the server where the logs are located must use the UNC path (\\<machine name>\DevEnterpriseLogs by default). The cumulative log is written to a text file only.

  • MetadataServer_portxxxx.log is a run log that contains information for the last run of the Metadata Server. xxxx is the port number the Metadata Server is listening to.
  • MetadataServer_rolling.log is a cumulative log that contains information from all previous Metadata Server runs during the month. On the first of every month, the previous month's log is renamed (to MetadataServer_rolling.log.mmm-yyyy) and a new MetadataServer_rolling.log is created for the new month.

Collector logs

There are two types of collector logs: a run log and a cumulative log. The run log is written to the console and to a text file located in a Logs directory on the machine on which the collection was run in the UserDataPath specified during the installation (which is available in the About dialog box). Users who are remote to the server where the logs are located must use the UNC path (\\<machine name>\DevEnterpriseLogs by default).The cumulative log is written to a text file only.

  • collectionname.log is a run log that contains information for the last run of the collector. Collectionname is the name of the collector being run (for example, the log for a collection called CICSSource would be called CICSSource.log).
  • Collectors_rolling.log is a cumulative log that contains information from all previous collector runs during the month. On the first of every month, the previous month's log is renamed (to Collectors_rolling.log.mmm-yyyy) and a new Collectors_rolling.log is created for the new month.

Browse this log to get details on the status of collections you have run.

Learner log

There is one learner log for each Metadata Server. This log is located in a Logs directory on the machine on which the Metadata Server is running in the UserDataPath specified during the installation (which is available in the About dialog box). Users who are remote to the server where the logs are located must use the UNC path (\\<machine name>\DevEnterpriseLogs by default).

Learner_portxxxx.log (where xxxx is the port number of the Metadata Server) is a cumulative log that contains information about the state of the learning process. It gives the following status information for every 10 programs learned:

  • Number of programs learned
  • Number of programs still in the queue to be learned
  • Average time to learn a program

When applicable, the learner log also indicates when a program has been moved to the top of the learning queue and when learning has been temporarily suspended and the reason.

Browse this log to determine whether programs of interest have been successfully learned or, if they have failed, why they failed.

Metadata Analyzer log

There is one Metadata Analyzer log, called MetadataViewer.log, which is a run log that contains information about any error activity of the Metadata Analyzer. This log is located in a Logs directory on the machine the Metadata Analyzer was run on in the UserDataPath specified during the installation (which is available in the About dialog box). Users who are remote to the server where the logs are located must use the UNC path (\\<machine name>\DevEnterpriseLogs by default).

Batch Impact Analysis log

The batch impact analysis log, called BatchImpact.log, lists any error information that occurred while impact analysis was run in batch mode. This log is located in a Logs directory on the machine the Metadata Analyzer was run on in the UserDataPath specified during the installation (which is available in the About dialog box). Users who are remote to the server where the logs are located must use the UNC path (\\<machine name>\DevEnterpriseLogs by default).

Information in each log message

Each log message contains the following information:

  • Date/time of run
  • Logging level
  • Collection name or server machine name and port number (not applicable to the Learner log)
  • Message, which may suggest actions for you to take to resolve an issue

Logging level

Logs can collect varying levels of information about a run: FATAL, ERROR, WARN, INFO, and DEBUG. While you can change the logging level, it should always be set to INFO unless you have been directed to change it by Compuware Customer Support. When you select a logging level, you will get all messages at that level and each higher level. For example, if you set the level to WARN, your log will contain WARN, ERROR, and FATAL error messages.

  • FATAL: Indicates that DevEnterprisewas unable to operate, typically due to an environmental constraint or issue, or a missing source file. Processing stops. A log set to FATAL will contain only FATAL messages. Sample FATAL messages are:

    2003-01-30 09:06:48,540 FATAL [MetadataServer_port1240] Msg=[Connection refused: connect]

    2004-01-07 11:29:38,693 FATAL [JCL coll ] Msg=[Unable to locate Data Set Name: JCL]
  • ERROR: Indicates that the Metadata Analyzer was unable to accomplish the task you have requested, possibly due to incorrect or insufficient user-provided information. Processing may stop or the action in error may be retried. A log set to ERROR will contain ERROR and FATAL messages. A sample ERROR message is:

    ERROR [SYS01_COBOL ] Msg=[Program=CWXTCOBX not found in any specified Source Libraries ]
  • WARN: Indicates a partially successful completion of what you requested. Processing continues and you are notified of potentially harmful situations. A log set to WARN will contain WARN, ERROR, and FATAL messages. A sample WARN message is:

    WARN [COBOL_EXAMPLE] Msg=[Source library: X2.MISSING.SOURCE was not found]
  • INFO: Indicates a sharing of information between DevEnterpriseand the user. Lists information about the progress of the run, such as when the process started and completed, the completion code, number of items processed, and the time it took to process. A log set to INFO will contain INFO, WARN, ERROR, and FATAL messages. A sample INFO message is:

    INFO [COBOL_EXAMPLE] Msg=[Collection ended: Name=COBOL_EXAMPLE;
     Status=Successful; Duration=0:0:50]
  • DEBUG: The most comprehensive log. Gives detailed tracing information to help you debug the run. A log set to DEBUG will contain DEBUG, INFO, WARN, ERROR, and FATAL messages.
  • OFF: Disables logging.

To change the level of information shown in logs

The default level is INFO, however, you can change the level. You may at first want to set the logs to INFO and monitor the various runs to become familiar with the process. To change the level:

  1. Open the appropriate .LCF file. Each is located in the UserDataPath specified during the installation (which is available in the About dialog box). Users who are remote to the server where the logs are located must use the UNC path (\\<machine name>\DevEnterpriseLogs by default).
    • MetadataServer.LCF (the LCF file for the Metadata Server log)
    • Collectors.LCF (the LCF file for the Collector log)
    • MetadataViewer.LCF (the LCF file for the Metadata Analyzer log)
  2. On the first line of the file, change the current level (such as INFO) to the level you want (such as DEBUG).
  3. Save and close the file.
  4. Restart the collection or Metadata Server to create logs with the new level.

To make any other types of changes to the .LCF file, refer to Jakarta's log4j documentation.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*