You're not going to find what other systems know as libc on zOS.  at least 
not as a supported package.
zOS uses LE (Language Environment 
http://www-03.ibm.com/systems/z/os/zos/features/lang_environment/) to 
handle the same thing
On zOS we support not just c/c++ and java but we have cobol, pl1, fortran 
and even our assembler is supported in our langauge enviroment (that's not 
saying others don't but we may have all running in a single lpar and often 
do)
While some have ported libc to zOS it is not an offciatlly supported 
package by anyone it seems so it's use is on a 'you use it, you support 
it' basis

a nm if libc.a shows
CARROS1:/usr/lib: >nm libc.a
__lib__.o:
          0 D @@DOPLNK
          0 U @@XINIT@
          0 D @STATIC
          0 U CEESG003
          0 U CEESTART
          0 T __lib__very_unlikely_to_be_referenced_external_function
          0 U printf
          0 t private

the CEE references are I beleive stubs into LE,  CEE is the C Language 
Enviroment.
If you want some of the night time reading you can look at the C docs for 
zOS
http://www-03.ibm.com/systems/z/os/zos/library/bkserv/v2r1pdf/#CBC

Sandra




From:   Karl Williamson <[email protected]>
To:     "[email protected]" <[email protected]>, Perl5 Porters 
<[email protected]>, Jarkko Hietaniemi <[email protected]>, John Goodyear 
<[email protected]>
Date:   10/06/2015 08:45 PM
Subject:        z/OS and libc



I'm working on continuing to port perl5 to z/OS.  One test that is 
failing is beyond my knowledge level.  The Dynaloader module has a 
function dl_findfile() which looks for libraries in the path.  It is 
expecting to find libc at least, but is finding nothing.

This test does not work on several platforms, even some Unix-like ones, 
and my guess is it doesn't work on z/OS either.  But I am hoping someone 
can give me more information.

One of the comments in the perl source says:
     # On OS/390, libc.a doesn't really hold anything at all,
 
And that makes me think that looking for it (and perhaps any Unix-y 
library) is futile.

Reply via email to