Richard Troth wrote:
Thanks, Mark.
I accept the offer.
But even before trying running your build I suspect that there's
something wrong in my config. Another weirdness I encountered was
that certain device types were rendered unknown (by Hercules) when I
included a MODPATH statement. Took that out and 3215, 3270, 3505 and
others were honored again. Strange.
-- R; <><
Not really..
The MODPATH statement is something you would only use in a development
environment or in an emergency situation.. Otherwise, you don't really
want MODPATH.
I'm not sure of how your setup is rigged, but you may be running into a
case of mixed up libraries (call it linux' version of DLL hell)..
So what you may really want to try is to build from source and make sure
you do a 'make install', then ensure (before running your test) that the
PATH environment variable contains the path the the executable (the
location of the shared libraries is hinted in the binaries) - and
especially that it goes before any other instance !
For info, the reason you may fail on DIAG 308 is simply that we didn't
really understand how Diag 308 worked at the time we attempted an
implementation. The implementation was so incomplete that it lead to
recurrent crashes (basically setup of Diag 308 worked, but trying to use
it would break things).. The faulty Diag 308 was removed (until we get a
better grasp of it) and just Prog Int on it (Specification Exception)..
Linux treats this gracefully (Oh.. ok.. no diag 308.. will have to make
do without it).
--Ivan
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
