Page 1 of 1
Ehllapijni dll for Windows7 64 bit OS
Posted:
Mon Nov 03, 2014 2:50 pmby suganthi
We have a Java application that invokes a mainframe page.
We are using EHLLAPIJNI.dll (32bit) ,EHLLAPIDLL.jar and Attachmate to perform communication with mainframe and gather required data.
It was working fine in Windows XP 32 bit OS. When we migrated our application to Win 7 64 bit OS it is not launching the mainframe page.
Initially there was a issue- Error trying to load EHLLAPIJNI dll file. Can't find dependent libraries but when we installed Attachmate this error is resolved
Log says ehllapii dll loaded,but We are not getting the return code when we call EHLLAPI() function.
Kindly suggest if there an EHLLAPIJNI.dll for 64 bit OS or how can we use this existing 32bit dll to work in win 7 64 bit OS
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Mon Nov 03, 2014 7:44 pmby Ed Goodman
Haven't used that version of Attachmate, but you might want to check the HLLAPI setting on it. There are some options for choose which version of HLLAPI to activate during a session. I would check the settings on an older, working machine and compare againt the newer machine.
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Tue Nov 04, 2014 4:02 pmby suganthi
Have set the Global preferences and chosen the HLLAPI short name - associated the session and selected the HLLAPI transport type as Standard as done for older version.Kindly suggest if there is any other option for chosing the version of HLLAPI in Attachmate Extra! X-treme
Thanks in advance
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Tue Nov 04, 2014 8:13 pmby Ed Goodman
When you call the EHLLAP function, you say you don't get a return code...do you get anything at all, even a time out or a "function not available?"
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Wed Nov 05, 2014 5:56 pmby suganthi
To Perform communication with mainframes (ie) While connecting to the presentation space (Attachmate),I am setting the session parameters with the following values
SET_SESSION_PARAMETERS = 9
sessionParams=STRLEN,SRCHALL,SRCHFRWD,AUTORESET,NWAIT
SessionParams.length() = 39
PARAM_WAIT_STATE =NWAIT ( No wait)
if (doEHLLAPI(SET_SESSION_PARAMETERS, sessionParams, sessionParams.length(), ZERO) == OK) then success
inside this we call this method,
i = EHLLAPIJNI.EHLLAPI(function, buffer, bufferSize, returnCode);it fails in this point
but no return code and no exception caught in try catch blocks
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Wed Nov 05, 2014 7:10 pmby Ed Goodman
Is "doEHLLAPI" a function in your code, or part of the API?
It may be returning OK when nothing really happens.
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Wed Nov 05, 2014 7:33 pmby suganthi
doEHLLAPI is a function in my code.
HLLAPI(&HllFunc, HllDataStr, &HllDataLgth, &PsPos) this is the exact API call , EHLLAPIJNI.EHLLAPI(function, buffer, bufferSize, returnCode)-which is used inside my custom code.
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Thu Nov 06, 2014 8:17 pmby Ed Goodman
Ok then....what is the return code from the ACTUAL hllapi call?
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Fri Nov 07, 2014 12:23 pmby suganthi
I am not receiving the return code from the hllapi call
Re: Ehllapijni dll for Windows7 64 bit OS
Posted:
Fri Nov 07, 2014 7:32 pmby Ed Goodman
I have a Delphi program that uses HLLAPI, and here is the function for SetParameters:
function Set_Session_Parameters(parms : string) : Boolean;
begin
HLLAPI_Func := HLLAPI_SET_SESSION_PARAMETERS;
HLLAPI_Parm2 := parms;
HLLAPI_Parm3 := Length(HLLAPI_Parm2);
HLLAPI_Parm4 := 0; //not used for set_session_parms
HLLAPI(HLLAPI_Func, HLLAPI_Parm2, HLLAPI_Parm3, HLLAPI_Parm4);
if HLLAPI_Parm4 = 0 then
begin
Set_Session_Parameters := True;
end else begin
showmessage(format('Attempt to set session parms got rc %d', [HLLAPI_Parm4]));
Set_Session_Parameters := False;
end;
end; //Set_Session_Parameters
Notice how I'm checking the value in HLLAPI_Parm4 after the call.
If the call makes it to the DLL, but has a problem, then HLLAPI_Parm4 will have a non-zero value. If the DLL connection is not defined, then the program will get a Windows error, like "no object found" or something like that.