Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
IMPORT: Import a function or external variable z/OS MVS Program Management: Advanced Facilities SA23-1392-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
IMPORT describes a function or external variable to be imported and the library member where it can be found. The syntax of the IMPORT call is:
Processing notesIf DLLNAME was not specified, the IMPORT statement will be ignored. Otherwise, if the symbol is unresolved at the end of autocall and all references have SCOPE=X, the IMPORT request will be converted to an entry in binder class B_IMPEXP. A bind job for a DLL application should include an IMPORT control statement for any DLLs that application expects to use. Otherwise if the DLL name is unresolved at static bind time it will not be accessible at run time (cannot be loaded). Typically, a library of DLLs has an associated side file of IMPORT control statements, and you can include this side file when statically binding a module that imports functions or variables from that library. You can also edit the records in the side file or substitute your own IMPORT control statements so that some symbols are imported from DLLs in a different library. Return and reason codesThe common binder API reason codes are shown in Table 1.
Parameter listIf your program does not use the IEWBIND macro, place the address of the IMPORT parameter list in general purpose register 1.
Note: X'80000000' must be added
to either the NAME
parameter (for Version 1 through 3) or the OFFSET parameter (for Version
4 or higher).
|
Copyright IBM Corporation 1990, 2014
|