Question & Answer
Question
Why does my application reject the BIND with a sense code of 08060000, 080A0000, or 08450004?
Cause
The SCIP exit of an application that is the SLU in a session is driven with a BIND. The PLU name presented to the application is the PLU's symbolic name, if the session is PLU initiated. This name can be an LUALIAS name, a USERVAR name, or the name in the NSPLU name field of the BIND. This is true regardless of whether the USERVAR name is network qualified or not.
A BIND was sent to the SLU application. In this case, there was a USERVAR defined for the PLU name. The USERVAR was presented to the application's SCIP exit. The USERVAR name was not configured
as a valid session partner. The SLU application rejected the BIND with a sense of x'08060000', x'080A0000', or x'08450004'. (Other applications may use a different sense code, but these are the three that have been reported so far.)
This problem has been reported in IDMS and IMS configurations, but this symptom is not application-dependent.
Answer
If the session partner of the application can be represented by a symbolic name, such as a USERVAR, you must configure the application to accept the symbolic name.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21282983