HIS LU assignment

[HansHans]

Hi all,

If we are using pool in HIS, can anyone tell us how HIS assign the LU? The manual mentioned that the LUs are randomly assigned. However, it seemed that if one is assign to one LU, next time he/she will probably get the same LU.
Thanks.

HansHans

 

[Concepts2000]

You don't say whether you are using a pool of LU 2 names or a pool of LUA names. They are different!

It the case of a pool of LU 2 names, it would not be safe to assume if a session got an LUname, that they would get that name back if the session was interrupted and restarted. In other words LUname assignment doesn't resemble IP adddress assignment by a DHCP server.

Nor would it be safe to assume that the names are assigned "up the ladder", ie in the order they are listed in the pool. It is true that this is what HIS does when absolutely no external forces affect selection. But that's a lot of ifs.

An LU pool is, strictly speaking, not an SNA concept - it is a purely logical construct of the Communications Resource Manager (CRM). For it to be of much use, assignment of live users to pools should reflect something about the live user's status or organization. You don't say why the question of LU name assignment arises.

Thanks.

 

[HansHans]

Hi Concepts2000,

Thanks for your advice. We are using LUA. The reason that we asked the previous is because we have a problem. The problem is as the follows.

There has been a LU connection built between the client, the server and host. For some reason, the host message cannot arrive at the client site within certain time period. The client will treat this timeout and logout. If the client logon using the same LU. The previous (garbage) message may treat as an valid message if the same user use the same LU.

So we would like to see whether there is a setting that can set HIS to really randomly assign the LU or put the LU to the back of the queue.

Thanks for your help

 

[Concepts2000]

I'm wondering if I'm getting confused between the LU name and the LUA_SID number.

It is considered good practice for an LUA application to specify the POOL name at the beginning of the conversation, and than would use the LUA_SID in subsequent LUA calls.

In other words, if you start a conversation with RUI_INIT or SLI_OPEN with an LUA pool, you would normally specify the pool name with the lua_luname member. Subsequently, in the same conversation, you would normally use the lua_sid member returned from RUI_INIT or SLI_OPEN to specify the conversation.

Hmm. I suspect any one of a number of programming techniques could be used to establish that a new conversation has been initiated - e.g. save the lua_sid.

When you issue RUI_INIT or SLI_OPEN, the lua_luname member contains the actual name of the LU used. This might also be useful in keeping "buffered" data from being mistaken for dat from a valid conversation.

Your questions and my answers seem to be a bit orthogonal, still. Let me know if this is helping.




--------------------------------------------------------------------------------

 

[HansHans]

Concepts2000,

Thanks. We will try to see whether your suggested way work. On the othe hand, we are wondering that there is a few of document to talk about this issue - how to assign the LU...

Hans