>>3. The binder LIBRARY statement in JCLIN is not supported by SMP/E.
> Well...not quite true per the book:
I stand by what I said: the LIBRARY statement is not supported by SMP/E. If
you code a LIBRARY statement in your JCLIN link edit step, you might get it to
work, but SMP/E makes no effort to recognize it or to ensure it keeps working
as you intend. For example, SMP/E does not ensure a ddname specified on the
LIBRARY statement gets allocated before calling the binder.
>> INCLUDE tgtddname('libsapi.a') TYPE=UTIN
> If I understood this, I'd do it. "use the INCLUDE statement"--where? In JCLIN?
In your JCLIN, within the stream of binder control statements, replace the
LIBRARY statement with an INCLUDE. Assuming the subject file resides in a
directory that is managed by SMP/E, specify on the INCLUDE the ddname that
corresponds to the target directory for that file. If a DD statement for that
ddname exists in the APPLY job, or a DDDEF entry with that name is defined in
the target zone, then SMP/E will ensure the ddname is allocated before calling
the binder so that the binder can find the subject file. And you can specify a
relative file name between the parenthesis if necessary to allow the binder to
find the file relative to the directory identified by the ddname.
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
