SMP/E support of additional data element MCS types incorporating expanded use of NLS localization.

Data element MCSs describe elements that are neither macros, modules, or source. Any type of data element may be installed in any target or distribution library that meets documented requirements for data set organization, LRECL, and BLKSIZE. IBM documents approximately 28 MCSs of which two types are restricted for exclusive internal IBM use in the z/OS SMP/E Reference, SA23-2276, Chapter 2.

MCS data elements ++USER1-++USER5 are defined in the SMP/E Reference as ‘User defined data types 1-5. These are for user-defined elements that are not covered by any existing data types.' Additionally, IBM defines ‘++DATA1-++DATA5' and ‘++DATA6xxx' (NLS support) for its use only. There is one other MCS, ++DATA, which is defined as ‘Data not covered by other types.', which customers are free to use.

Unlike IBM, customers are not provided any ++DATA types for use with national language localization. Problematically, the language used by IBM in the SMP/E Reference to define and distinguish differences between ++DATA and ++USERx MCS is too broad and subject to considerable interpretation when constructing/coding MCSs.

Data element MCSs are extremely useful when packaging and refactoring new or legacy products for installation and service. Fundamentally, MCSs eliminate the need for creating JCLIN when propagating (i.e. ‘copying') distinctly unique varieties of data from the SMPTLIBs to target and distribution libraries during APPLY and ACCEPT processing, respectively.

See below for use cases that further examine and describe the core requirements.