I think it's due to the CASE binder option. Here's what we use:

IEW2278I B352 INVOCATION PARAMETERS - 
MAP,RENT,DYNAM=DLL,CASE=MIXED,COMPAT=CURR,LIST=NOIMP        


In article <[email protected]> you wrote:
> Thanks Don!

> I switched the SYSLIN to include the .x file

> //SYSLIN   DD  *                                     
>  INCLUDE   '/u/Java6_31/J6.0/bin/j9vm/libjvm.x'      
>  INCLUDE OBJECT                                      
>  NAME    CALLJAVA(R)                                 
> //*                                                  

> The binder output shows this now

> IEW2278I B352 INVOCATION PARAMETERS - 
> LIST(NOIMP),AMODE=31,MAP,RENT,DYNAM(DLL)  
> IEW2322I 1220  1    INCLUDE   '/u/Java6_31/J6.0/bin/j9vm/libjvm.x'            
>   
> IEW2322I 1220  160    INCLUDE OBJECT                                          
>   
> IEW2322I 1220  161    NAME    CALLJAVA(R)                                     
>   
> IEW2456E 9207 SYMBOL JNI_CreateJavaVM UNRESOLVED.  MEMBER COULD NOT BE 
> INCLUDED 

> Why isn't JNI_CreateJavaVM resolved by libjvm.x?

> Janet

> >It's the .x file that needs to be included in SYSLIN. I've never heard of
> >SIDEFILE as a DD name. The .so file is the "shared object" or DLL file. 
> >That's only needed at run-time. If you're using some Apace SDK, I would
> >look for a side file that comes with it. Again, you'd also need the Apache
> >.so file available somewhere at run-time. Make sure you set the DYNAM(DLL)
> >binder option.

-- 
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
[email protected]           (919) 531-5637                Cary, NC 27513

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to