6.4.6 Checking the debug log to determine whether user-created data is correct

The debug log is used to check whether the user-created data is correct. If you want to output debug log information, specify the -debug 1 or -debug 2 option in the jpcuser command.

In the debug log, a check result code, such as OK (success), NG (failure), or WG (warning), is output for each data line in the user-created data. If NG or WG is output in the debug log, the user-created data might be invalid. If NG or WG has been output, check the user commands by which the user-created data was created, and make any necessary corrections for outputting the data in the correct format. For the correct format, see 6.4.5 Format of user-created data files.

The following shows the location and name of a debug log file:

/opt/jp1pc/agtu/agent/jpcuser/debug/jpcuser_dbg_{01|02|03|04|05}.log

The following describes the debug log file format.

Organization of this subsection
(1) Debug log file format
(2) Example of information output to a debug log file

(1) Debug log file format

A debug log file consists of four sections:

A check result is output for each data line in the user-created data. A comma is used to separate items.

The following table explains the items that are output to a debug log file.

Table 6-28 Items that are output to a debug log file

No.SectionItemValueExplanation
1Product informationProduct nameProduct Name=PFM-Agent for Platform (UNIX)The PFM-Agent product name.
2Format versionFormVer=0001The version of the user-created data format.
3Execution time and process ID of the jpcuser commandExecution timeYYYY/MM/DD hh:mm:ssYYYY: Year
MM: Month
DD: Day
hh: Hour
mm: Minute
ss: Second
4Process IDPID=xxxxThe process ID of the jpcuser command.
5Header lineHeaderExample (for the PD_UPD record):
LineNumber, Result, APITime, Recordtype, Transactiontype, t, ks, ki, L1, L2, UL1, UL2, F1, F2, SS1, SS2, SS3, SS4, SM1, SM2, SL1
The debug log header.
The header names correspond to the field options and field names specified on the option header line in a user-created data file. For the correspondence, see Table 6-29 Header line items in a debug log file and their corresponding field options and field names.
Note that the header items differ depending on the user-defined records that are to be stored.
6Check resultUser-created data file nameExample:
File=/opt/jp1pc/agtu/agent/jpcuser/sample_01.txt
The user-specified path name of a user-created data file that is read is output.
7Error or warning messageKAVFxxxxx-xIf an error or other problem that the user should be made aware of occurs on a line in the user-created data, the applicable error and warning messages are output at the beginning of the line.
8Line numberNumeric valueThe number of a line in the user-created data.
9Result codeOKSuccess.
The line in the user-created data was free of problems and was converted successfully.
10WGWarning.
The line in the user-created data contained a problem but was converted nevertheless.
When WG is output, a warning message is also output.
11NGFailure.
The line in the user-created data contained a problem and was not converted.
When NG is output, a warning message or error message, depending on the cause of the problem, is also output. If a warning message is output, processing continues. If an error message is output, processing stops.
12BLNull line.
The line in the user-created data is empty and is ignored.
13DataDataThe contents of the line in the user-created data.
For an empty numeric field, 0 is output.
For an empty string field, two quotation marks ("") are output.

The following table lists the items output on the header line in a debug log file and their corresponding field options and field names specified on the option header line in a user-created data file.

Table 6-29 Header line items in a debug log file and their corresponding field options and field names

No.Item on the header line in a debug log fileField option specified on the option header line in a user-created data fileField name
(PFM - View name)
Explanation
1Line Number----Number of the line on which the relevant data exists
2Result----Check result of the relevant data
3API Time--Collect TimeTime that the relevant data was converted
4Record type--Record TypeRecord type
5Transaction typettTrans TypeTransaction type
6ttUser Time 1Time value
7ksksTrans String KeyString-type transaction key
8kikiTrans Data KeyNumeric-type transaction key
9L1lUser Long 1Integer value of type long
10L2lUser Long 2Integer value of type long
11L3lUser Long 3Integer value of type long
12L4lUser Long 4Integer value of type long
13L5lUser Long 5Integer value of type long
14L1RlrUser Long Roll 1Cumulative integer value of type long
15L2RlrUser Long Roll 2Cumulative integer value of type long
16L3RlrUser Long Roll 3Cumulative integer value of type long
17L4RlrUser Long Roll 4Cumulative integer value of type long
18L5RlrUser Long Roll 5Cumulative integer value of type long
19UL1uUser Unsigned Long 1Integer value of type unsigned long
20UL2uUser Unsigned Long 2Integer value of type unsigned long
21UL3uUser Unsigned Long 3Integer value of type unsigned long
22UL4uUser Unsigned Long 4Integer value of type unsigned long
23UL5uUser Unsigned Long 5Integer value of type unsigned long
24UL1RurUser Unsigned Long Roll 1Cumulative integer value of type unsigned long
25UL2RurUser Unsigned Long Roll 2Cumulative integer value of type unsigned long
26UL3RurUser Unsigned Long Roll 3Cumulative integer value of type unsigned long
27UL4RurUser Unsigned Long Roll 4Cumulative integer value of type unsigned long
28UL5RurUser Unsigned Long Roll 5Cumulative integer value of type unsigned long
29F1fUser Float 1Floating point number value
30F2fUser Float 2Floating point number value
31F3fUser Float 3Floating point number value
32F4fUser Float 4Floating point number value
33F5fUser Float 5Floating point number value
34F1RfrUser Float Roll 1Cumulative floating point number value
35F2RfrUser Float Roll 2Cumulative floating point number value
36F3RfrUser Float Roll 3Cumulative floating point number value
37F4RfrUser Float Roll 4Cumulative floating point number value
38F5RfrUser Float Roll 5Cumulative floating point number value
39SS1ssUser String 116-byte character string
40SS2ssUser String 216-byte character string
41SS3ssUser String 316-byte character string
42SS4ssUser String 416-byte character string
43SS5ssUser String 516-byte character string
44SM1smUser String 5 (for the PD_UPD or PI_UPI record)
User String 6 (for the PD_UPDB or PI_UPIB record)
32-byte character string
45SM2smUser String 6 (for the PD_UPD or PI_UPI record)
User String 7 for the (PD_UPDB or PI_UPIB record)
32-byte character string
46SM3smUser String 832-byte character string
47SM4smUser String 932-byte character string
48SM5smUser String 1032-byte character string
49SL1slUser String 7 (for the PD_UPD or PI_UPI record)
User String 11 (for the PD_UPDB or PI_UPIB record)
64-byte character string
50SL2slUser String 1264-byte character string
51SL3slUser String 1364-byte character string
52SL4slUser String 1464-byte character string
53SL5slUser String 1564-byte character string
Legend:
--: Not applicable

(2) Example of information output to a debug log file

The following figure shows an example of information output to a debug log file.

Figure 6-5 Example of information output to a debug log file

[Figure]

The following explanations are keyed to the numbers in parentheses in the figure.

  1. This line is the header line.
  2. The user-specified path name of a user-created data file loaded into the command is output.
  3. Output of the check result for the user-created data file begins with this line. The number (4) at the beginning indicates the number of the line in the user-created data file. In a user-created data file, the first line contains product information, the second line contains version information, and the third line is the option header line. Therefore, checking normally begins with line 4. If the line contains no problems, OK is output for Result.
  4. The user-specified path name of another user-created data file that is read is output.
  5. This line warns the user of a problem on line 4 in the sample_02.txt file. Because the t value (2007/02/24,10:10:010) did not have the expected format, n/a has been output for the element corresponding to t (see (7) in the figure).
  6. This line also warns the user of a problem on line 4 in the sample_02.txt file. Because the specified ss value (abcdefghijklmnop) exceeded the predefined maximum of 15 bytes, a warning message has been output. and a truncated value (abcdefghijklmno) has been output for the element corresponding to SS1 (see (7) in the figure).
  7. Because the warnings indicated by (5) and (6) have been issued, the check result code WG has been output for Result for line 4.
  8. The check result code BL indicates that the line is a null line.
  9. This line warns the user of a problem on line 7. A warning message has been output because the specified ks value exceeded the predefined maximum of 19 bytes.
  10. Because the value of the ks unique key on line 7 in the user-created data file was incorrect, the value could not be used. Accordingly, NG has been output for Result. If the value of Transaction type, ks, or ki, which is a unique key, is incorrect, the line is not processed.