Page 1 of 3

Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Fri Aug 27, 2010 6:59 pm
by LotharLochkarte
Dear folks,

I try to compile and link a OO Cobol program, but the link-step abends with the messages:

IEW2456E 9207 SYMBOL GetJVMPtr UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL GetEnvPtr UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL GetClassObject UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM THE DESIGNATED CALL LIBRARY.


I modified the sample JCL in the "COBOL programming guide" example. Maybe the following lines of the JCL are relevant:

//OBJMOD DD DISP=SHR,DSN=*.COMP001.SYSLIN
//SYSDEFSD DD DUMMY
//SYSLIN DD *
INCLUDE '/usr/lpp/java/J5.0/bin/j9vm/libjvm.x'
INCLUDE '/usr/lpp/cobol/lib/igzcjava.x'
INCLUDE OBJMOD

If I delete the "INCLUDE OBJMOD" line, the messages disappear, but of course the Object is needed in this statement.

I compiled the example Hello1.java file with omvs and the class is located in /u/myuserid where I also set the classpath to. (Don't know if it is important)

Can somebody make an educated guess what is going wrong here?

Thank you very much in advance!

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Fri Aug 27, 2010 7:00 pm
by LotharLochkarte
Sorry, the sample JCL is to be found on page 322 in this document: http://publibfp.boulder.ibm.com/epubs/pdf/igy3pg50.pdf

Thanks

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Fri Aug 27, 2010 7:58 pm
by Robert Sample
I just entered and compiled the indicated test program from the COBOL manual. The library members your linkage editor / binder step are not finding are all in /usr/lpp/cobol/lib/igzcjava.x so you need to contact your site support group to find out where they installed this library. It is also possible that they defined a mount point for this library but it is not being mounted after an IPL -- all I can say for sure is that the library wasn't found in your compile and link-edit for some reason.

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Fri Aug 27, 2010 8:33 pm
by LotharLochkarte
Thank your for the reply!

I'll check it out on monday.

I remember to have inspected the file /usr/lpp/cobol/lib/igzcjava.x and I found only one line in there (which I do not remember right now). The same issue with '/usr/lpp/java/J5.0/bin/j9vm/libjvm.x'.

Is this normal or is the file corrupt/incomplete?

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Fri Aug 27, 2010 9:08 pm
by Robert Sample
That's normal -- those are object / load modules and as such are not human-readable.

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Thu Sep 02, 2010 3:06 am
by LotharLochkarte
Thank you again, now the linkage-editor steps works fine and gives RC=0! :-)

However, I am not finished yet. The GO-step (again I copied from the sample JCL above) abends with RC=16 and the message "Exception in thread 'main'".

I guess the system cannot find Hello1.class file. I compiled the Hello1.java file unter USS (with omvs shell) and the resulting class file is located in /u/myuserid/Hello1.class.

The ENV-file, which I specify in the GO-step looks like this:

PATH=/bin:/usr/lpp/java/J5.0/bin.
LIBPATH=/lib:/usr/lib:/usr/lpp/java/J5.0/bin:/usr/lpp/java/J5.0/bin/j9vm
CLASSPATH=/u/myuserid

Do you have an idea how to solve this?

Thanks. :-)

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Thu Sep 02, 2010 4:40 am
by Robert Sample
My experiments came up with the same error. I haven't had time to go back and figure out what's going on, yet, but hopefully things will slow down soon and I can work out the "exception in thread main" error.

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Thu Sep 02, 2010 9:10 am
by dick scherrer
Hello,

Just a couple of thoughts/guesses. . .

Is there a "class" directory beneath /u/myuserid?

Might it help to add /u/myuserid to the end of LIBPATH?

I've not done this on the mainframe, but when i worked on different UNIX systems, it was often product dependent as to which directories had to be named in various "..path" variables.

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Fri Sep 03, 2010 1:38 am
by LotharLochkarte
Dear Dick,

I have tried out your ideas, but unfortunately they didn't solve the problem...

Re: Linking OO Cobol gives "GetClassObject UNRESOLVED" error

PostPosted: Tue Sep 07, 2010 9:31 pm
by LotharLochkarte
I tried out several things in the meantime, but it still doesn't work...

If somebody has an idea... :-)