Using Error, Exception and Summary Logging
This section discusses using error. exception and summary logging.
The COBOL Unicode conversion utility for z/OS produces a set of error and informational logs with messages that identify inconsistencies and problems. The utility also logs conversion exceptions that may require manual review.
|
Log |
Description |
|---|---|
|
Error log |
This log is produced when serious error occurred in the conversion, and provides detailed information of the error. |
|
Exception log |
This log lists all conversion exceptions found in the programs. |
|
Summary log |
This log provides general statistics regarding the number of programs that are processed. |
To set logging parameters, set the following parameters on the conversion utility command line:
|
Parameter |
Description |
|---|---|
|
-r |
Produces the summary log. |
|
-rd |
Produces the summary log and the exception log. |
When called from the server transfer process, the conversion utility produces the summary log in the staging directory, but does not produce an exception log.
The following table summarizes all of the messages that can appear in the exception log file.
|
Message |
Note |
|---|---|
|
File Name: Not converted because this is Unicode file. |
COBOL source that is already converted (has “Converted for Unicode” marker on the first line), or COBOL source files under \unicode subdirectory under the source directory, will not be converted. |
|
File Name: Not converted because it is not used in DATA or PROCEDURE division of any program. |
The utility converts copybooks on the fly when they are used in COPY statement in the data division or procedure division of the program. Copybooks not used from data division or procedure division of program sources will not be modified. |
|
File Name(Line Number): Field Name not converted because it is file status field. |
The utility does not convert file status field because COBOL requires file status field to be a two-byte alphanumeric field. |
|
File Name(Line Number): Size of Field Name expanded but not converted to PIC N because it is -SETUP data. |
In the SELECT-SETUP or BIND-SETUP group, the utility does not change data field usage. Instead, character data field size is expanded to match the size of the corresponding PIC N field in the SELECT-DATA or BIND-DATA group. |
|
File Name(Line Number): Field Name not converted because of redefinition. |
In the SELECT-DATA or BIND-DATA group, the character field redefining binary, packed decimal, or pointer data field will not be converted to PIC N. |
|
File Name(Line Number): Removed GROUP-USAGE form group Group Field Name |
The utility removes the GROUP-USAGE clause from a group declaration if the group is used in the context where GROUP-USAGE NATIONAL cannot be used. This message typically appears when a group in a copybook can be USAGE NATIONAL in the context of one program, but later found that it cannot be NATIONAL in the context of another program. |
|
File Name(Line Number): Data item Field Name not found. |
The utility checks the data field when processing procedure division of COBOL programs, typically to determine if it should add the DISPLAY-OF() function. This message appears on the log when the utility failed to look up the data field. |
The summary log lists the number of programs and copybooks read, modified, and not modified. The following is an example of the summary log.
If you are converting PeopleSoft- delivered application program sources, it is typical that not all the programs and copybooks are modified. The utility converts a copybook when it is called from data division or procedure division of any program source using COPY statement. There are several PeopleSoft delivered copybooks that are not called from data division or procedure division of any program. PeopleSoft also provides Unicode-specific COBOL source code that the utility does not modify and counts as a “not modified” program or copybook.