Vernooy, C.P. - SPLXM wrote:
"R.S." <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
Vernooy, C.P. - SPLXM wrote:
"R.S." <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
After RRS restart, DB2 restart is required as well.
Q: is DB2 restart required ? Does any other method exist to
"re-register" DB2 to RRS ?
--
Radoslaw Skorupka
Lodz, Poland
Radoslaw,
From our experience there is no need to restart DB2 after an RRS
restart.
Only IMS has/had an issue with RRS restart, if you like I can dig up
the
details.
I believe there is a method to avoid DB2 restart, however I can't find
it. I browsed DB2 Admin. Guide (chapter 4.2.9: DB2 & RRS), have found
no
clue.
For sure, applications using RRS gives error message after RRS
restart.
DSNRLI function IDENTIFY gives return-code = 8 and reason-code =
00F30091.
--
That's a different view: When RRS is down, you will have problems, when
you also bring down DB2, your applications will have problems too.
However, DB2 detects and picks up an RRS restart without problems and I
understood that that was the question.
Kees,
You understood it correctly. However previous sentence is not true in my
environment. DB2 does not recognize RRS after it is restarted. The
return code means - according to manual - that RRS is down. Howerver it
is up again. This is my problem. The only resolution I found is restart
DB2 after RRS is up again. Obviously I should avoid restarting RRS. <g>
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
