David:
I am somewhat suspicious of a PDS library that is "normally looked"
at and specifying a member name for SYSLIB. ex:
DD DSNAME=SSOP.TZ13.GLD.SGLDEXPC(GLDCLDPX),DISP=SHR
Just does not sit with me right. It may be valid in a prelinker
situation but it just doesn't look right.
Ed
On Dec 10, 2013, at 10:05 PM, David Crayford wrote:
Henrique,
If it's possible (you can use a PDS/E) I would suggest you abandon
the pre-linker. It's deprecated and a real PITA. The binder does a
much better job, but you will need to move to GOFF which requires a
PDS/E load library.
On 11/12/2013 11:15 AM, Henrique Seganfredo wrote:
Thanks for the feedback,
I realized that my current z/OS (1.13) the prelinker has no SYSN2
card, but then I tried using the SYSLIB (secondary input) in this
following ways:
//SYSLIB DD DSNAME=SSOP.TZ13.CEE.SCEECPP,DISP=SHR
// DD DSNAME=SSOP.TZ13.GLD.SGLDEXPC,DISP=SHR
or being more explicit
//SYSLIB DD DSNAME=SSOP.TZ13.CEE.SCEECPP,DISP=SHR
// DD DSNAME=SSOP.TZ13.GLD.SGLDEXPC(GLDCLDPX),DISP=SHR
In both way I still get unresolved references on the ldap
functions when I get to the link step.
---------------------------------------------------------------------
-
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-
MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
