Generating the compilable assembler CSECT for the message table

Start of change The message table is loaded into private storage of the Health Checker address space and should be a single CSECT load module. End of change

You can generate the messages from the SGML message definition file into a compilable assembler CSECT using the message generation exec HZSMSGEN. The input and output DD names for HZSMSGGEN can be allocated to a data set, PDS member or z/OS® UNIX file.

Start of change A sample job invoking HZSMSGEN is contained in member HZSMSGNJ of SYS1.SAMPLIB. End of change

HZSMSGEN can also generate the national language support (NLS) message skeletons for message translation of check message text, if desired. See Support for translating messages to other languages.

To use the message generation JCL to generate check messages into a CSECT, do the following:

Get the HZSMSGNJ message generation JCL from SYS1.SAMPLIB. Also in SYS1.SAMPLIB, you will find the following files referenced in the HZSMSGNJ JCL:
- Member HZSSMSGT containing a sample message definition file.
- Member HZSSSYMD containing a sample local symbol.

Customize your copy of HZSMSGNJ as indicated in the prolog.

Note that specifying NLSCHECK(Y) does not specify that message skeletons be generated! NLSCHECK(Y) specifies that you want HZSMSGEN to enforce the message translation guidelines that will make it possible to generate message skeletons (see Support for translating messages to other languages). If you want to generate message skeletons for message translation, you must uncomment the HZSNPSKE and HZSLNSKE DD statements:

Set HZSNLSKE to the name of the NLS skeleton output data set. This data set should be blocked variable with a record length of 259. After HZSMSGEN runs, this data set contains the prolog from HZSNPSKE and the completed message skeletons for the check messages.

Set HZSNPSKE to the name of the NLS skeleton prolog input data set. This data set must contain the version record required for MVS™ message service (MMS) translation and should contain a copyright statement. The following shows an example HZSNPSKE data set:

.VENUNHBB7730 5650-A010601                                         
.*                                                                   
.******************************************************************* 
.*                                                                   
.* COPYRIGHT  -                                                      
.*        5650-ZOS                                                   
.*        THIS MESSAGE INSTALL FILE IS "RESTRICTED MATERIALS OF IBM" 
.*        (C) COPYRIGHT IBM CORP. 1988, 2005                         
.*        LICENSED MATERIALS  - PROPERTY OF IBM                      
.*                                                                   
.* STATUS = HBB7730                                                  
.*                                                                   
.*                                                                   
.*                                                                   
.* NOTE: VERSION RECORD (.V IN COLS. 1-2) MUST APPEAR FIRST IN THIS  
.*       FILE. FOR UPDATES, REFER TO APPLICATION DEVELOPMENT GUIDE:  
.*       ASSEMBLER LANGUAGE PROGRAMS.                                
.*                                                                   
.* CHANGE-ACTIVITY:                                                  
.* $L0=HCHECK   HBB7730,050731,PD00ZJ: HCR8                          
.*                                                                   
.*******************************************************************

The version record must be the first non-comment record in each install message file identified by the '.v' in columns 1 and 2 of the HZSNLSKE data set. See Creating a version record in z/OS MVS Programming: Assembler Services Guide for the complete format of the version record.

To run the message generation JCL, Issue the following command from TSO:
```
SUB 'your.dataset.name(HZSMSGNJ)'
```

HZSMSGEN writes a message generation report to either the data set or UNIX System Services file specified in HZSEDSN, if specified, or to the SYSTSPRT file. The following shows an HZSMSGEN report for both CSECT and NLS skeleton generation:

IBM Health Checker For Z/OS HBB7730 NLSCHECK(Y) SOURCE(ERROR) 

10 May 2006 

RulesLevel 2 (HBB7730 and up) was selected for processing 

System execution level: z/OS 01.08.00 HBB7730 TSO/E 3060 

Source data set 'SYS1.SAMPLIB(HZSSMSGT)'

Setup entity data set: 'SYS1.SAMPLIB(HZSSSYMD)' 

Assembler source MSGTBL: 'userid.your.dsname(csect)' 

NLS skeleton prologue: 'input.nls.version.record' 

NLS skeleton source:'output.nls(skeleton)' 


HZSM0133 The assembler source for the message table was created 

Return Code: 0 

HZSM0133 The NLS message skeleton source was created 

Return Code: 0