The JCLIN command

JCLIN processing initializes entries in the target or distribution zone with the data required to install elements into the target libraries. SMP/E derives this data by scanning a job stream containing assembly, copy, and link-edit job steps. JCLIN processing is called by either the JCLIN command or as part of installing a SYSMOD containing ++JCLIN statements.

Note that SMP/E does not execute the JCLIN. It does not call the utilities specified in the job stream, and it does not update, modify, or look at any of the target libraries. Rather, JCLIN is a vehicle to describe the structure of the target libraries (and, ultimately, the structure of the load modules in those libraries). It is element statements (such as ++MOD) that cause SMP/E to actually invoke the utilities.

The purpose of this topic is to describe JCLIN processing and the requirements SMP/E has on the input, so that you can better understand how to construct JCLIN for your own use.

Note:

JCLIN processes only information about elements such as macros, modules, and source. It does not process information about data elements, except for totally copied libraries. Information about data elements is added to the zone when the data elements are installed in the libraries or when the distribution zone is copied into the target zone.
JCLIN processing does not cause SMP/E to update the target or distribution libraries; only the entries in the target and distribution zones are updated. These libraries are updated when SMP/E processes the elements in a SYSMOD. The element statements in a SYSMOD determine which elements should be installed.

The following terms are used in this topic:

JCLIN input: A job stream of assembly, link-edit, and copy job steps. This input is pointed to by the SMPJCLIN DD statement.
Inline JCLIN: JCLIN data pointed to by a ++JCLIN MCS. The actual JCLIN data can be packaged inline, following the ++JCLIN MCS, or it can be packaged in a RELFILE or TXLIB data set.

The description of the JCLIN command used here applies to processing both the JCLIN command and to inline JCLIN processed at APPLY or ACCEPT time. The utility and OPCODE operands that can be specified on the JCLIN command are also valid as operands on the ++JCLIN statement.

Reminder

The input for JCLIN must be free of JCL errors and must conform to the SMP/E restrictions. Incorrect input can cause unpredictable errors, or even cause the installation of SYSMODs that depend on the JCLIN to fail.