Thanks to everyone who replied. Unfortunately all your suggestions have not yet
solved the problem, I seem to be in
very dense mode today. I have discovered the following things:
1. If I don’t use the pre-linker none of my assembler entry points get
upper-cased and mayhem results in the link step.
Also, despite including the side-file in the link step, none of the gsk
references get resolved.
2. If I use GOFF and the pre-linker the assembler entry points don't get upper
cased.
3. So with NOGOFF and including the side file in the pre-linker gets the
messages:
WARNING EDC4015: Unresolved references are detected:
CEEBETBL CEEROOTA CEESG003
gsk_environment_open gsk_attribute_set_
enum gsk_attribute_set_buffer gsk_environment_init gsk_envir
onment_close
WARNING EDC4049: Unresolved references could not be imported:
gsk_environment_open gsk_attribute_set_enum gsk_attribute_set_
buffer gsk_environment_init gsk_environment_close
and I still get the @ST000nn entries which cause the link step to fail; I also
concatenated the side-file to SYSLIN for good
measure. FWIW, in the pre-link step I have PARM='MAP,UPCASE' and in the link
step
PARM='DYNAM=DLL,CASE=MIXED,COMPAT=CURR'.
Thanks
Robin
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Thomas David Rivers
Sent: 11 March 2016 02:45
To: [email protected]
Subject: Re: Linking C module with SSL
Robin Atwood wrote:
>I am trying to convert an XL/C module to use SSL. From the pre-link-edit step
>I get messages like:
>
>
> @ST00010 gsk_environment_init
>
>and then from the link-edit:
>
>IEW2456E 9207 SYMBOL @ST00010 UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM
> THE DESIGNATED CALL LIBRARY.
>
>The routines I need are in SYS1.SIEALNKE(GSKSSL). I have added this
>library to SYSLIB in both the
>
> pre-linker and link-edit step, included it in the SYSIN and SYSLIN, but
> nothing works. The manual says:
>
>Include the /usr/lib/GSKSSL.x or /usr/lib/GSKSSL64.x sidedeck in the prelink
>or bind step input.
>
>But that is not very helpful with JCL (and eventually SCLM). Has anyone any
>idea how to do this?
>
>Thanks
>Robin
>
>
>
The routines aren't in SYS1.STEALNKE(GSKSSL) - I believe that is the actual
load module that represents the runtime DLL that is invoked.
To properly pre-link SSL code you need to include the side-deck on the pre-link
step; this causes the pre-linker to create DLL stubs to invoke the proper
routines within the DLL.
So, you need to include /usr/lib/GSKSSL.x in your input for your pre-linkstep.
From JCL, you can either copy the file to a PDS (FB 80 would suffice) and
point to that PDS member; or you can define a DD with a PATH to point to it an
INCLUDE that DD.
- Dave Rivers -
--
[email protected] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
----------------------------------------------------------------------
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
