The sample JCL from step (c) produces the following listing on
the //SYSPRINT DD:
CUN1000I Z/OS SUPPORT FOR UNICODE VERSION V1R6
CUN1001I PROCESSING STARTED ON 01/29/2004 AT 14:13:14
Source Listing ----+----1----+----2----+----3----+----4----+----5----+----6--+
1
2 /********************************************
3 * INPUT STATEMENTS FOR THE IMAGE GENERATOR *
4 ********************************************/
5
6 NORMALIZE; /* ENABLE NORMALIZATION */
7 COLLATE; /* ENABLE COLATION */
8 CASE NORMAL; /* ENABLE TOUPPER AND TOLOWER */
9 CASE LOCALE; /* ENABLE LOCALE */
10 CASE SPECIAL; /* ENABLE SPECIAL */
11 CONVERSION 1047,850; /* EBCDIC -> ASCII */
12 CONVERSION 850,1047; /* ASCII -> EBCDIC */
13
Statement Report --+----1----+----2----+----3----+----4----+----5----+----6--+
1 CONVERSION 1047,850,;
/* 01047-00850-R using CUNRM0EB */
2 CONVERSION 850,1047,;
/* 00850-01047-R using CUNREBM0 */
3 CASE NORMAL;
/* to-upper normal using CUNANUUP */
/* to-lower normal using CUNANULO */
4 CASE LOCALE;
/* to-upper locale using CUNASCUP */
/* special casing table using CUNASCAS */
/* category table using CUNASCLT */
/* to-lower locale using CUNASCLO */
/* special casing table using CUNASCAS */
/* category table using CUNASCLT */
5 CASE SPECIAL;
/* to-upper special using CUNASUUP */
/* special casing table using CUNASCAS */
/* category table using CUNASCLT */
/* to-lower special using CUNASULO */
/* special casing table using CUNASCAS */
/* category table using CUNASCLT */
6 NORMALIZE;
/* canonical decomposition table.......... using CUNNCDTB */
/* canonical decomposition stop table..... using CUNNCDST */
/* compatibility decomposition table...... using CUNNKDTB */
/* compatibility decomposition stop table. using CUNNKDST */
/* composition table...................... using CUNNCOMT */
/* composition stop table................. using CUNNCOST */
/* canonical class table.................. using CUNNCACT */
/* canonical class non zero table ........ using CUNNCCNZ */
7 COLLATE;
/* CE Main Table.............................. using CUNOBACE */
/* Expansions Index Table..................... using CUNOEXIN */
/* Expansion Elements Table................... using CUNOEXDA */
/* Contraction Index Table.................... using CUNOTIDX */
/* Contraction Elements Table................. using CUNOCODA */
/* Main Index Table........................... using CUNOMIDX */
/* Rearrangement Values - Thai and Lao........ using CUNOTHLA */
/* Fast Canonical Decomposition Stop Table.... using CUNOFCD */
/* Fast Compatibility Decomposition Stop Tbl.. using CUNOFKD */
/* Fast Composition Stop Table................ using CUNOFCO */
CUN1014I INPUT READ 13 RECORDS
CUN1015I STATEMENTS PROCESSED 7
CUN1016I STATEMENTS FLAGGED 0
CUN1017I GENERATED IMAGE SIZE 522 PAGES
CUN1002I PROCESSING ENDED. HIGHEST RETURN CODE WAS 0
The listing can be divided into four sections:
- The identification section. This section shows the product version
and when the job was started.
- The source listing. This section repeats the data from //SYSIN
DD exactly as entered.
- The statement report. This section shows the recognized statements
and how they were resolved.
- The statistic section. This section gives an overview of the complete
process.
The following descriptions explain how the listing can be used
to manage the generated images.
- The identification section
- If you have already generated a lot of images and keep them in
data sets, it might be of interest to match an image generator listing
with an existing image. For this reason there is a readable time stamp
in the first record of the image. This time stamp matches the time
stamp on message CUN1001I.
CUN1000I Z/OS SUPPORT FOR UNICODE VERSION V1R6
CUN1001I PROCESSING STARTED ON 01/29/2004 AT 12:11:09
- The source listing
- Especially when concatenated data sets are used on the //SYSIN
DD statement, it is important to check which control statements were
provided in the input stream. The source listing shows exactly what
was read from //SYSIN DD and the number that is assigned to each input
record.
- The statement report
- In the statement report you can see what the image generator has
interpreted from the provided input. All comments, blanks, and line
breaks have been removed. Each recognized statement is printed in
a normalized form and a statement number is assigned. Comments are
inserted after the statement to explain what was generated by the
system.
...
Statement Report --+----1----+----2----+----3----+----4----+----5----+----6----+-
1 CONVERSION 933,1200,RE;
/* 00933-01200-RE */
/* 00833-01200-R using CUNRDIPG */
/* 00834-01200-R using CUNRDMPG */
...
The left hand side in the comment shows a hierarchy of
the top-level and sub-level conversions. The right hand side shows
the name of the tables used.
- The statistics sections
- The most important information from the statistic section is the
return code. If the return code is 0, processing was successful from
the technical point of view. You should always check the statement
report carefully to ensure the generated image contains the necessary
tables and correct CCSIDs.
Error situations: The following paragraphs show how the
listing can be used in error situations:
- Environmental errors:
Before processing starts all the
required resources are checked and allocated. When errors occur in
that phase no source listing and no statement report are generated.
The identification and statistic sections are printed. No image is
generated. A listing with an environmental error might look like this:
CUN1000I Z/OS SUPPORT FOR UNICODE VERSION V1R6
CUN1001I PROCESSING STARTED ON 01/29/2004 AT 14:13:14
CUN1007E ERROR OCCURRED OBTAINING TEMPORARY WORK STORAGE RC=00000004
CUN1014I INPUT READ 0 RECORDS
CUN1015I STATEMENTS PROCESSED 0
CUN1016I STATEMENTS FLAGGED 0
CUN1017I GENERATED IMAGE SIZE 0 PAGES
CUN1002I PROCESSING ENDED. HIGHEST RETURN CODE WAS 12
- Syntactical errors:
Once the initialization phase has
successfully been executed the input stream is read from //SYSIN DD
and the source listing is produced. The input stream then is parsed
for syntactical errors. The values of the parameters are not checked
at this point. Syntactical errors are for instance:
- unrecognized statement keywords
- missing/excessive parameters
- missing/excessive commas or semicolons
The statement report is not printed. No image is generated.
A listing with a syntactical error might look like this:
CUN1000I Z/OS SUPPORT FOR UNICODE VERSION V1R6
CUN1001I PROCESSING STARTED ON 01/29/2004 AT 15:16:17
Source Listing ----+----1----+----2----+----3----+----4----+----5----+----6--+
1
2 /********************************************
3 * INPUT STATEMENTS FOR THE IMAGE GENERATOR *
4 ********************************************/
5
6 NORMALIZE; /* ENABLE NORMALIZATION */
7 COLLATE; /* ENABLE COLATION */
8 CASE NORMAL; /* ENABLE TOUPPER AND TOLOWER */
9 CASE LOCALE; /* ENABLE LOCALE */
10 CASE SPECIAL; /* ENABLE SPECIAL */
11 CONVERSION 1047; /* EBCDIC -> ASCII */
12 CONVERSION 850,1047; /* ASCII -> EBCDIC */
13
CUN4005E MANDATORY PARAMETER(S) MISSING FROM STATEMENT
'CONVERSION' IN LINE 11.
A MINIMUM OF TWO PARAMETERS IS REQUIRED
CUN1014I INPUT READ 13 RECORDS
CUN1015I STATEMENTS PROCESSED 0
CUN1016I STATEMENTS FLAGGED 0
CUN1017I GENERATED IMAGE SIZE 1 PAGES
CUN1002I PROCESSING ENDED. HIGHEST RETURN CODE WAS 8
- Semantical errors:
When the syntax of a statement is
correct the specified parameters are checked for reasonable values.
Semantical errors are for instance:
- CCSIDs out of range
- invalid technique-characters
- invalid case conversion modes
- conversion table not found
The statement is printed in the statement report followed
by the error messages issued. No image is generated. A listing with
a semantical error might look like this:
CUN1000I Z/OS SUPPORT FOR UNICODE VERSION V1R6
CUN1001I PROCESSING STARTED ON 01/29/2004 AT 15:23:14
Source Listing ----+----1----+----2----+----3----+----4----+----5----+----6--+
1
2 /********************************************
3 * INPUT STATEMENTS FOR THE IMAGE GENERATOR *
4 ********************************************/
5
6 NORMALIZE; /* ENABLE NORMALIZATION */
7 COLLATE; /* ENABLE COLATION */
8 CASE NORMAL; /* ENABLE TOUPPER AND TOLOWER */
9 CASE LOCALE; /* ENABLE LOCALE */
10 CASE SPECIAL; /* ENABLE SPECIAL */
11 CONVERSION 1047,85000; /* EBCDIC -> ASCII */
12 CONVERSION 850,1047; /* ASCII -> EBCDIC */
13
Statement Report --+----1----+----2----+----3----+----4----+----5----+----6--+
1 CONVERSION 1047,85000,;
CUN1023E ERROR DURING CCSID VALIDATION. INVALID CCSID '85000'
2 CONVERSION 850,1047,;
/* 00850-01047-R using CUNREBM0 */
3 CASE NORMAL;
/* to-upper normal using CUNANUUP */
/* to-lower normal using CUNANULO */
4 CASE LOCALE;
/* to-upper locale using CUNASCUP */
/* special casing table using CUNASCAS */
/* category table using CUNASCLT */
....
....
/* Fast Canonical Decomposition Stop Table.... using CUNOFCD */
/* Fast Compatibility Decomposition Stop Tbl.. using CUNOFKD */
/* Fast Composition Stop Table................ using CUNOFCO */
CUN1014I INPUT READ 13 RECORDS
CUN1015I STATEMENTS PROCESSED 7
CUN1016I STATEMENTS FLAGGED 7
CUN1017I GENERATED IMAGE SIZE 1 PAGES
CUN1002I PROCESSING ENDED. HIGHEST RETURN CODE WAS 8
After generating the conversion image, copy it to SYS1.PARMLIB
or any other data set in the logical parmlib concatenation.
After completing the steps a to d, continue with Calculating the storage needed for a conversion image.
z/OS Unicode Services User's Guide and Reference
Copyright IBM Corporation 1990, 2014