SCLM build and control timestamps

SCLM uses the System Status Index (SSI) field to signify that the last update of a load module was made through SCLM. The SSI field data that SCLM generates consists of the following bits: the most significant bit is defined as a flag; the next most significant 11 bits specify hour and minute in binary form; and the least significant 20 bits specify Julian date in packed decimal form. SCLM sets the flag bit and writes these items into the SSI field during build processing when it generates a load module.

Table 1. SCLM System Status Index Field Data
Bit	Definition	Form
0	flag	bit
1-5	hour	binary
6-11	minute	binary
12-31	Julian date	packed decimal

Note: To update the SSI information for a PDSE, SCLM uses the IEWBIND macro. The IEWBIND macro provides the invoking program with access to binder services. Not-editable PM2 and higher format program objects cannot be reprocessed by the binder. The advantage of PM2 or higher format program object created with the not-editable option is that they may require much less space on DASD.

In some cases SCLM Build fails when EDIT=NO is specified. For example, the output from the C or C++ compiler is an extended object file (XOBJ). The lowest compatibility of the binder with XOBJ format input without going through the Language Environment® prelinker is PM3. In addition there are some restrictions on the usage of the not-editable attribute for PM2 or higher format program objects. Therefore we recommend not to use EDIT=NO binder option with SCLM-controlled members. See z/OS MVS Program Management: Advanced Facilities and z/OS MVS Program Management: User's Guide and Reference for more details.