> The F1 relfile is the JCLIN data. Ours includes:
> //SYSLIN DD *
> LIBRARY '&USSPATH.lib/libsapi.a'
Plenty of others have already stated these points, but I can't help to
reiterate:
1. JCLIN is not JCL. It looks like it but is never ever used as such by SMP/E.
SMP/E scans the JCLIN to pick out information to define target library
content. In the case of a link edit JCLIN step, it defines LMODs and the MODs
which are included in them.
2. SMP/E does not support substitution in JCLIN like is possible with JCL and
the JCL interpreter/converter.
And now for the most important point I hope you take away from this discussion:
3. The binder LIBRARY statement in JCLIN is not supported by SMP/E. The
LIBRARY statement tells the binder to "include this thing when building the
load module". If you want to include a file when building a load module, and
if that file is not a module defined by ++MOD (or from assembled source) then
use the INCLUDE statement, specify the target library ddname (instead of the
more DISTLIB ddname used when including a MOD) and add the comment "TYPE=UTIN".
Like this:
INCLUDE tgtddname('libsapi.a')
You can read all about which binder statements SMP/E supports and generally how
SMP/E processes link edit steps in JCLIN here:
https://www.ibm.com/docs/en/zos/3.2.0?topic=processing-link-edit-steps
Kurt Quackenbush
IBM | z/OS SMP/E and z/OSMF Software Management | [email protected]
Chuck Norris never uses CHECK when he applies PTFs.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
