Anonymous_User Absent Member.
Absent Member.
205 views

RACF Driver Crashing frequenty after z/OS upgrad1.11 to 1.13


Hi,

We have IDM 4.0.1 installed on our Environment. And we have couple of
RACF drivers running via Remote Loaders. The RACF driver version is
1.0.3.

Few weeks back the RACF OS- Z/OS is upgraded from 1.11 to 1.3. After the
upgrade the RACF driver is getting crashed/stopped every day frequently,
and we see the below error from the logs.


Message: Code(-9005) The driver returned a "fatal" status
indicating that the driver should be shut down. Detail from driver:
<description>Driver exception.</description>
<exception
class-name="com.Omnibond.system.Command.CommandSessionException">
<message>Error occured during writeLine():
com.Omnibond.system.Command.ScriptException: linenum=11 cursor=0 :
Unexpected Response from LDXSERV</message>

<stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
occured during writeLine(): com.Omnibond.system.Command.ScriptException:
linenum=11 cursor=0 :
Unexpected Response from LDXSERV


<status event-id="12264256" level="warning" type="driver-status">
<description>Driver
exception.</description>
<exception
class-name="com.Omnibond.system.Command.CommandSessionException">

<message>Error occured during readLine():
java.net.SocketTimeoutException: Read timed out</message>

<stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
occured during readLine(): java.net.SocketTimeoutException: Read timed
out
at
com.Omnibond.system.Command.TelnetCommandSession.error(TelnetCommandSession.java:138)
at
com.Omnibond.system.Command.TelnetCommandSession.ProcessAndTranslateException(TelnetCommandSession.java:263)
at
com.Omnibond.system.Command.TelnetCommandSession.readLine(TelnetCommandSession.java:315)
at
com.Omnibond.nds.dirxml.driver.MVSDriver.RACFDriver.RACFUserQuery.<init>(RACFUserQuery.java:28)


<status event-id="12238088" level="warning" type="driver-status">
<description>Driver exception.</description>
<exception
class-name="com.Omnibond.system.Command.CommandSessionException">
<message>Error occured during readLine():
java.net.SocketTimeoutException: Read timed out</message>
<stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
occured during readLine(): java.net.SocketTimeoutException: Read timed
out


The driver was working perfect before upgrade. But after upgrade, the
driver stops almost everyday very frequently.

Is there any known issue for the driver and the OS upgrade 1.13? And is
there any reason and any fix how to resolve this issue.

Then environment details:

eDirectory: 8.8 SP3
IDM 4.0.1
RACF driver version : 1.0.3

Thanks in Advance.


Thanks,
Dina


--
dinanovell
------------------------------------------------------------------------
dinanovell's Profile: https://forums.netiq.com/member.php?userid=1056
View this thread: https://forums.netiq.com/showthread.php?t=46356

Labels (1)
0 Likes
5 Replies
Knowledge Partner
Knowledge Partner

Re: RACF Driver Crashing frequenty after z/OS upgrad1.11 to 1.13

I asked one fo the RACF driver guys to come take a look, lets see what
he has to say.

On 12/11/2012 2:54 AM, dinanovell wrote:
>
> Hi,
>
> We have IDM 4.0.1 installed on our Environment. And we have couple of
> RACF drivers running via Remote Loaders. The RACF driver version is
> 1.0.3.
>
> Few weeks back the RACF OS- Z/OS is upgraded from 1.11 to 1.3. After the
> upgrade the RACF driver is getting crashed/stopped every day frequently,
> and we see the below error from the logs.
>
>
> Message: Code(-9005) The driver returned a "fatal" status
> indicating that the driver should be shut down. Detail from driver:
> <description>Driver exception.</description>
> <exception
> class-name="com.Omnibond.system.Command.CommandSessionException">
> <message>Error occured during writeLine():
> com.Omnibond.system.Command.ScriptException: linenum=11 cursor=0 :
> Unexpected Response from LDXSERV</message>
>
> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
> occured during writeLine(): com.Omnibond.system.Command.ScriptException:
> linenum=11 cursor=0 :
> Unexpected Response from LDXSERV
>
>
> <status event-id="12264256" level="warning" type="driver-status">
> <description>Driver
> exception.</description>
> <exception
> class-name="com.Omnibond.system.Command.CommandSessionException">
>
> <message>Error occured during readLine():
> java.net.SocketTimeoutException: Read timed out</message>
>
> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
> occured during readLine(): java.net.SocketTimeoutException: Read timed
> out
> at
> com.Omnibond.system.Command.TelnetCommandSession.error(TelnetCommandSession.java:138)
> at
> com.Omnibond.system.Command.TelnetCommandSession.ProcessAndTranslateException(TelnetCommandSession.java:263)
> at
> com.Omnibond.system.Command.TelnetCommandSession.readLine(TelnetCommandSession.java:315)
> at
> com.Omnibond.nds.dirxml.driver.MVSDriver.RACFDriver.RACFUserQuery.<init>(RACFUserQuery.java:28)
>
>
> <status event-id="12238088" level="warning" type="driver-status">
> <description>Driver exception.</description>
> <exception
> class-name="com.Omnibond.system.Command.CommandSessionException">
> <message>Error occured during readLine():
> java.net.SocketTimeoutException: Read timed out</message>
> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
> occured during readLine(): java.net.SocketTimeoutException: Read timed
> out
>
>
> The driver was working perfect before upgrade. But after upgrade, the
> driver stops almost everyday very frequently.
>
> Is there any known issue for the driver and the OS upgrade 1.13? And is
> there any reason and any fix how to resolve this issue.
>
> Then environment details:
>
> eDirectory: 8.8 SP3
> IDM 4.0.1
> RACF driver version : 1.0.3
>
> Thanks in Advance.
>
>
> Thanks,
> Dina
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: RACF Driver Crashing frequenty after z/OS upgrad1.11 to 1.13


Hi Dina, this is a know issue with 1.13 and IBM released the following
APAR to correct line-mode telnet for us. A more permanent solution is
to move to the 4.0 RACF driver, which no longer uses telnet for
communication:


Currently IBM have provided a short-term fix, so any other customers
with the same problem would be able to request the ++APAR fix for
PM58814. Eventually there will be a PTF fix for the problem. I believe
the issue is isolated to z/OS V1R13 although I don't know if all z/OS
V1R13 sites will see the problem.
Here are the details of the APAR:
APAR
Identifier ...... PM58814 Last Changed ........ 12/02/24
A LINEMODE CLIENT RECEIVES GARBLED DATA FROM TELNET SERVER

Symptom ...... IN INCORROUT Status ........... OPEN
Severity ................... 2 Date Closed .........
Component .......... 5655HAL00 Duplicate of ........
Reported Release ......... 1D0 Fixed Release ............
Component Name TCP/IP V3 MVS Special Notice
Current Target Date ..12/04/12 Flags
SCP ...................
Platform ............
Status Detail: REVIEW - APAR solution is being reviewed.
PE PTF List:
PTF List:

Parent APAR:
Child APAR list:

ERROR DESCRIPTION:
A linemode (VT100) client connects to the Telnet server. TSO is
entered as the target application. The 'HELP' command is entered
from the TSO READY prompt. The HELP response, however, is
garbled. Translation of EBCDIC newlines (x'15') into the ASCII
string x'0D0A' does not always occur. If DEBUG DETAIL is
specified in the Telnet profile then the following message
will also be produced:
EZZ6035I TN3270 DEBUG CONN DETAIL 755
IP..PORT: ::FFFF:nn.nn.nn.nn..nnnn
CONN: nnnnnnnn LU: luname MOD: EZBTPLMT
RCODE: nnnn-00 Return code explanation not available.
PARM1: 00000000 PARM2: 00000000 PARM3: 00000000
Note: The RCODE will contain a random value.

LOCAL FIX:
Connect to the Telnet server with either a TN3270 or TN3270E
type client.



dinanovell;223193 Wrote:
> Hi,
>
> We have IDM 4.0.1 installed on our Environment. And we have couple of
> RACF drivers running via Remote Loaders. The RACF driver version is
> 1.0.3.
>
> Few weeks back the RACF OS- Z/OS is upgraded from 1.11 to 1.3. After the
> upgrade the RACF driver is getting crashed/stopped every day frequently,
> and we see the below error from the logs.
>
>
> Message: Code(-9005) The driver returned a "fatal" status
> indicating that the driver should be shut down. Detail from driver:
> <description>Driver exception.</description>
> <exception
> class-name="com.Omnibond.system.Command.CommandSessionException">
> <message>Error occured during writeLine():
> com.Omnibond.system.Command.ScriptException: linenum=11 cursor=0 :
> Unexpected Response from LDXSERV</message>
>
> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
> occured during writeLine(): com.Omnibond.system.Command.ScriptException:
> linenum=11 cursor=0 :
> Unexpected Response from LDXSERV
>
>
> <status event-id="12264256" level="warning" type="driver-status">
> <description>Driver
> exception.</description>
> <exception
> class-name="com.Omnibond.system.Command.CommandSessionException">
>
> <message>Error occured during readLine():
> java.net.SocketTimeoutException: Read timed out</message>
>
> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
> occured during readLine(): java.net.SocketTimeoutException: Read timed
> out
> at
> com.Omnibond.system.Command.TelnetCommandSession.error(TelnetCommandSession.java:138)
> at
> com.Omnibond.system.Command.TelnetCommandSession.ProcessAndTranslateException(TelnetCommandSession.java:263)
> at
> com.Omnibond.system.Command.TelnetCommandSession.readLine(TelnetCommandSession.java:315)
> at
> com.Omnibond.nds.dirxml.driver.MVSDriver.RACFDriver.RACFUserQuery.<init>(RACFUserQuery.java:28)
>
>
> <status event-id="12238088" level="warning" type="driver-status">
> <description>Driver exception.</description>
> <exception
> class-name="com.Omnibond.system.Command.CommandSessionException">
> <message>Error occured during readLine():
> java.net.SocketTimeoutException: Read timed out</message>
> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
> occured during readLine(): java.net.SocketTimeoutException: Read timed
> out
>
>
> The driver was working perfect before upgrade. But after upgrade, the
> driver stops almost everyday very frequently.
>
> Is there any known issue for the driver and the OS upgrade 1.13? And is
> there any reason and any fix how to resolve this issue.
>
> Then environment details:
>
> eDirectory: 8.8 SP3
> IDM 4.0.1
> RACF driver version : 1.0.3
>
> Thanks in Advance.
>
>
> Thanks,
> Dina



--
jgrieshop
------------------------------------------------------------------------
jgrieshop's Profile: https://forums.netiq.com/member.php?userid=483
View this thread: https://forums.netiq.com/showthread.php?t=46356

0 Likes
Knowledge Partner
Knowledge Partner

Re: RACF Driver Crashing frequenty after z/OS upgrad1.11 to 1.13

Now that is what I call an answer! Thanks Jeremy!

On 12/11/2012 8:54 AM, jgrieshop wrote:
>
> Hi Dina, this is a know issue with 1.13 and IBM released the following
> APAR to correct line-mode telnet for us. A more permanent solution is
> to move to the 4.0 RACF driver, which no longer uses telnet for
> communication:
>
>
> Currently IBM have provided a short-term fix, so any other customers
> with the same problem would be able to request the ++APAR fix for
> PM58814. Eventually there will be a PTF fix for the problem. I believe
> the issue is isolated to z/OS V1R13 although I don't know if all z/OS
> V1R13 sites will see the problem.
> Here are the details of the APAR:
> APAR
> Identifier ...... PM58814 Last Changed ........ 12/02/24
> A LINEMODE CLIENT RECEIVES GARBLED DATA FROM TELNET SERVER
>
> Symptom ...... IN INCORROUT Status ........... OPEN
> Severity ................... 2 Date Closed .........
> Component .......... 5655HAL00 Duplicate of ........
> Reported Release ......... 1D0 Fixed Release ............
> Component Name TCP/IP V3 MVS Special Notice
> Current Target Date ..12/04/12 Flags
> SCP ...................
> Platform ............
> Status Detail: REVIEW - APAR solution is being reviewed.
> PE PTF List:
> PTF List:
>
> Parent APAR:
> Child APAR list:
>
> ERROR DESCRIPTION:
> A linemode (VT100) client connects to the Telnet server. TSO is
> entered as the target application. The 'HELP' command is entered
> from the TSO READY prompt. The HELP response, however, is
> garbled. Translation of EBCDIC newlines (x'15') into the ASCII
> string x'0D0A' does not always occur. If DEBUG DETAIL is
> specified in the Telnet profile then the following message
> will also be produced:
> EZZ6035I TN3270 DEBUG CONN DETAIL 755
> IP..PORT: ::FFFF:nn.nn.nn.nn..nnnn
> CONN: nnnnnnnn LU: luname MOD: EZBTPLMT
> RCODE: nnnn-00 Return code explanation not available.
> PARM1: 00000000 PARM2: 00000000 PARM3: 00000000
> Note: The RCODE will contain a random value.
>
> LOCAL FIX:
> Connect to the Telnet server with either a TN3270 or TN3270E
> type client.
>
>
>
> dinanovell;223193 Wrote:
>> Hi,
>>
>> We have IDM 4.0.1 installed on our Environment. And we have couple of
>> RACF drivers running via Remote Loaders. The RACF driver version is
>> 1.0.3.
>>
>> Few weeks back the RACF OS- Z/OS is upgraded from 1.11 to 1.3. After the
>> upgrade the RACF driver is getting crashed/stopped every day frequently,
>> and we see the below error from the logs.
>>
>>
>> Message: Code(-9005) The driver returned a "fatal" status
>> indicating that the driver should be shut down. Detail from driver:
>> <description>Driver exception.</description>
>> <exception
>> class-name="com.Omnibond.system.Command.CommandSessionException">
>> <message>Error occured during writeLine():
>> com.Omnibond.system.Command.ScriptException: linenum=11 cursor=0 :
>> Unexpected Response from LDXSERV</message>
>>
>> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
>> occured during writeLine(): com.Omnibond.system.Command.ScriptException:
>> linenum=11 cursor=0 :
>> Unexpected Response from LDXSERV
>>
>>
>> <status event-id="12264256" level="warning" type="driver-status">
>> <description>Driver
>> exception.</description>
>> <exception
>> class-name="com.Omnibond.system.Command.CommandSessionException">
>>
>> <message>Error occured during readLine():
>> java.net.SocketTimeoutException: Read timed out</message>
>>
>> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
>> occured during readLine(): java.net.SocketTimeoutException: Read timed
>> out
>> at
>> com.Omnibond.system.Command.TelnetCommandSession.error(TelnetCommandSession.java:138)
>> at
>> com.Omnibond.system.Command.TelnetCommandSession.ProcessAndTranslateException(TelnetCommandSession.java:263)
>> at
>> com.Omnibond.system.Command.TelnetCommandSession.readLine(TelnetCommandSession.java:315)
>> at
>> com.Omnibond.nds.dirxml.driver.MVSDriver.RACFDriver.RACFUserQuery.<init>(RACFUserQuery.java:28)
>>
>>
>> <status event-id="12238088" level="warning" type="driver-status">
>> <description>Driver exception.</description>
>> <exception
>> class-name="com.Omnibond.system.Command.CommandSessionException">
>> <message>Error occured during readLine():
>> java.net.SocketTimeoutException: Read timed out</message>
>> <stack-trace>com.Omnibond.system.Command.CommandSessionException: Error
>> occured during readLine(): java.net.SocketTimeoutException: Read timed
>> out
>>
>>
>> The driver was working perfect before upgrade. But after upgrade, the
>> driver stops almost everyday very frequently.
>>
>> Is there any known issue for the driver and the OS upgrade 1.13? And is
>> there any reason and any fix how to resolve this issue.
>>
>> Then environment details:
>>
>> eDirectory: 8.8 SP3
>> IDM 4.0.1
>> RACF driver version : 1.0.3
>>
>> Thanks in Advance.
>>
>>
>> Thanks,
>> Dina

>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: RACF Driver Crashing frequenty after z/OS upgrad1.11 to 1.13


Thanks jgrieshop & geoff.

If the temporary fix has to be applied, I believe this has to be applied
on RACF side and if applied, do you know the time how long it will take
to apply the fix.

if you could share the link to how to apply the temporary fix, it will
be helpful.

And do we need to change anything on the IDM/Driver side for this
temporary fix?

Thanks!
Dina


--
dinanovell
------------------------------------------------------------------------
dinanovell's Profile: https://forums.netiq.com/member.php?userid=1056
View this thread: https://forums.netiq.com/showthread.php?t=46356

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: RACF Driver Crashing frequenty after z/OS upgrad1.11 to 1.13

On Wed, 12 Dec 2012 15:44:02 +0000, dinanovell wrote:

> If the temporary fix has to be applied, I believe this has to be applied
> on RACF side and if applied, do you know the time how long it will take
> to apply the fix.


Correct. Your system admins should be able to handle PTF installation.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.