Windows Server

Guest · Posted: Sat Dec 04, 2004 5:34 am Post subject: Pooling with User assignment

How would I configure a set of LUs to Pool but only have the User get his
assigned LUs and not another user's assigned LUs even though they are in
the same Pool?

The Problem: If a user is assigned 3 LUs (not through a pool). When the
user launches the HIS Client the first time, he gets his first assigned
LU. When the User launches the HIS Client the second time, he gets and
error stating "Open(SSCP) has already been issued." The user would then
have to go to his settings and select his second LU, then connect to use
his second session. Same thing for Third and subsequent sessions. This
can be a training nightmare for a large company with medium to high
turnover.

Further Information:
1) The first possible workaround for this situation is to save a
configuration file for each session assigned to the user and then create
shortcuts to launch the HIS with the configuration file. Since the
sessions are pre assigned in the configuration files, the user just clicks
the shortcut for the session they want to launch. This solution, while
effective, is very costly in PC management when you think of 6000 users
with 3 LUs each.
2) The second possible solution is to set the LUs to pool and
assign the pool to the users. In this senerio when the user launches the
HIS Client the second time, they receive the next available LU from the
pool. (This is the desired result) However due to our environment it is
a stipulation that each user is assigned their own LUs and they are the
only ones with access to those LUs. This aids the Mainframe Services team
in Tracking and Troubleshooting issues back to a workstation or user. If
all the LUs are pooled then there is not a way to tell which user was
using the LU at the time of the incedent thus hendering the
troubleshooting and recovery process.
3) A third solution would be to configure a pool for each user
that contained only their LUs and assign the Pool to that users. In this
senerio the overall desired result is reached. When the user launches the
client the second time they get their second LU as assigned and available
from their pool. Also in this solution the user only gets the LU they are
assigned, however, as in the first solution, this results in a great
amount of administrative cost when looking at 6000 users.

Desired Result:
The desired result would be something similar to the following.
Create a single Pool. Add all LUs for your users to the single pool.
Assign the LUs in the pool to individual users. Assign the Pool to all
the users. When the HIS Client requests it's LUs, it only receives the
LUs that are assigned to that user, however because the LUs are pooled,
when the user launches the client the second time they receive their next
assigned LU from the pool.

Please let me know if this is possible.

Thanks,

Curtis L. Smith

Charles Ezzell (MSFT) · Guest

Curtis,

Sorry, but what you are asking for can not be done in that manner. We can
limit LUs "somewhat" like what you are asking, but on a workstation versus
user record. So, you could assign a pool to the "Everyone" account, then
assign specific LUs to a workstation, then on the workstation configuration
indicate whether you want to limit the LUs to those assigned to the
"Workstation" or "both" the user record and workstation record. I'm not sure
if it would work in the way you are asking however, since the workstation
would not "know" the Pool name if you only set it to allow access to the
"workstation" records.

You can script the configuration, using either WMI or SNACFG.EXE, which
would make things easier for setting up the user records:

For instance, using snacfg.exe:
// add pool SYSPOOL
snacfg POOL SYSPOOL /ADD /DISPLAYMODEL:Mod2 /ALLOWMODELOVERRIDE:No
/ASSOCPRINT:No /COMMENT:""
// add user "BOB"
snacfg USER BOB /ADD /DOMAIN:BOBSDOMAIN /COMMENT:"Everyone" /ENCRYPT:No
// validate user records, normally done after adding multiple users via
snacfg
SNACFG USER /VALIDATE
// add pool SYSPOOL to "BOB"
snacfg USER BOB /DOMAIN:BOBSDOMAIN /INSERT:SYSPOOL
// add LUs SYS002, SYS003, and SYS004 and assign to Pool "SYSPOOL"
snacfg LU SYS002 /ADD /LUNUMBER:2 /CONNECTION:SYS1/POOL:SYSPOOL
/LUTYPE:Display /DISPLAYMODEL:Mod2 /ALLOWMODELOVERRIDE:No /COMMENT:""
/COMPRESSION:No /WORKSTATIONSECURE:No
snacfg LU SYS003 /ADD /LUNUMBER:2 /CONNECTION:SYS1/POOL:SYSPOOL
/LUTYPE:Display /DISPLAYMODEL:Mod2 /ALLOWMODELOVERRIDE:No /COMMENT:""
/COMPRESSION:No /WORKSTATIONSECURE:No
snacfg LU SYS004 /ADD /LUNUMBER:2 /CONNECTION:SYS1/POOL:SYSPOOL
/LUTYPE:Display /DISPLAYMODEL:Mod2 /ALLOWMODELOVERRIDE:No /COMMENT:""
/COMPRESSION:No /WORKSTATIONSECURE:No

Somewhat easy to setup, especially with a little work in Excel and your LUs
are in "incrementing numbers" or some such that Excel can increment
automatically.

If you already have the LUs configured, but not added to a pool, you could
do the following to add the LUs to the pool:
snacfg LU SYS002 /POOL:SYSPOOL
snacfg LU SYS003 /POOL:SYSPOOL
snacfg LU SYS004 /POOL:SYSPOOL

HTH
Charles

<Curtis.Smith@Daltile.com> wrote in message
news:%23fa2tCZ2EHA.1408@TK2MSFTNGP10.phx.gbl...

How would I configure a set of LUs to Pool but only have the User get his
assigned LUs and not another user's assigned LUs even though they are in the
same Pool?

The Problem: If a user is assigned 3 LUs (not through a pool). When the
user launches the HIS Client the first time, he gets his first assigned LU.
When the User launches the HIS Client the second time, he gets and error
stating "Open(SSCP) has already been issued." The user would then have to
go to his settings and select his second LU, then connect to use his second
session. Same thing for Third and subsequent sessions. This can be a
training nightmare for a large company with medium to high turnover.

Further Information:
1) The first possible workaround for this situation is to save a
configuration file for each session assigned to the user and then create
shortcuts to launch the HIS with the configuration file. Since the sessions
are pre assigned in the configuration files, the user just clicks the
shortcut for the session they want to launch. This solution, while
effective, is very costly in PC management when you think of 6000 users with
3 LUs each.
2) The second possible solution is to set the LUs to pool and
assign the pool to the users. In this senerio when the user launches the
HIS Client the second time, they receive the next available LU from the
pool. (This is the desired result) However due to our environment it is a
stipulation that each user is assigned their own LUs and they are the only
ones with access to those LUs. This aids the Mainframe Services team in
Tracking and Troubleshooting issues back to a workstation or user. If all
the LUs are pooled then there is not a way to tell which user was using the
LU at the time of the incedent thus hendering the troubleshooting and
recovery process.
3) A third solution would be to configure a pool for each user that
contained only their LUs and assign the Pool to that users. In this senerio
the overall desired result is reached. When the user launches the client
the second time they get their second LU as assigned and available from
their pool. Also in this solution the user only gets the LU they are
assigned, however, as in the first solution, this results in a great amount
of administrative cost when looking at 6000 users.

Desired Result:
The desired result would be something similar to the following.
Create a single Pool. Add all LUs for your users to the single pool.
Assign the LUs in the pool to individual users. Assign the Pool to all the
users. When the HIS Client requests it's LUs, it only receives the LUs that
are assigned to that user, however because the LUs are pooled, when the user
launches the client the second time they receive their next assigned LU from
the pool.

Please let me know if this is possible.

Thanks,

Curtis L. Smith

Guest · Posted: Fri Dec 10, 2004 5:22 am Post subject: Re: Pooling with User assignment

Charles, thanks for the response. After trying the different solutions
you have suggested, I will post the results on what works best for me.

Thanks again

Curtis L. Smith

Guest · Posted: Sat Dec 11, 2004 1:35 am Post subject: Re: Pooling with User assignment

I tried the following suggestion unsuccessfully.

(We can limit LUs "somewhat" like what you are asking, but on a
workstation versus
user record. So, you could assign a pool to the "Everyone" account, then
assign specific LUs to a workstation, then on the workstation
configuration
indicate whether you want to limit the LUs to those assigned to the
"Workstation" or "both" the user record and workstation record. I'm not
sure
if it would work in the way you are asking however, since the workstation
would not "know" the Pool name if you only set it to allow access to the
"workstation" records.)

In testing, I created a pool with 6 LUs and assigned that pool to
everyone. Then
I defined a workstation and assigned 2 of the 6 LUs specifically to the
workstation
(being sure to select "Use workstation LUs only") As anticipated the only
LUs
availabe to the client where the 2 LUs assigned specifically to the
workstation.
However when launching the client for a second time, I received the same
issue as
before (LU already issued). I could then go through the setting of the
client and
select the second LU and connect, but as you see there is no change in the
ammount
of administration caused by this problem.

My only recourse at this point is to manually create configuration files
or to create
a tool to make management of a Pool for each user feasible. However I do
not know how
having 6,000 pools will impact the stability of the HIS System.

Thanks again for the suggestions.

Charles Ezzell (MSFT) · Guest

6000 Pools are not a problem. You can have up to 10,000. Below are our
limits:

+==================+================================================+===========+
| Area | Object |
Maximum |
+==================+================================================+===========+
| Server | Servers per SNA subdomain | 15
|
+==================+================================================+===========+
| Server | Nodes per server | 4
|
+==================+================================================+===========+
| Server | Nodes per SNA subdomain | 60
|
+==================+================================================+===========+
| Server | Connections per node | 250
|
+==================+================================================+===========+
| Server | Active client sponsor connections per server | 8000
|
+==================+================================================+===========+
| | |
|
+==================+================================================+===========+
| Link Service | Link services per server | 64
|
+==================+================================================+===========+
| Link Service | Links (adapters) per server | 1,024
|
+==================+================================================+===========+
| Link Service | Connections per adapter | 250
|
+==================+================================================+===========+
| | |
|
+==================+================================================+===========+
| LUs | LUs per node (30,000 maximum per server) | 15,000
|
+==================+================================================+===========+
| LUs | LUs per user/group | 4,000
|
+==================+================================================+===========+
| LUs | Dependent LUs per connection | 255
|
+==================+================================================+===========+
| LUs | LUs per passthrough connection | 255
|
+==================+================================================+===========+
| | |
|
+==================+================================================+===========+
| Pools | LUs assigned per pool | 30,000
|
+==================+================================================+===========+
| Pools | 3270 pools | 10,000
|
+==================+================================================+===========+
| Pools | LUA pools | 10,000
|
+==================+================================================+===========+
| Pools | Downstream LU pools | 10,000
|
+==================+================================================+===========+
| | |
|
+==================+================================================+===========+
| Users | Users per pool | 10,000
|
+==================+================================================+===========+
| Users | Users per LU | 10,000
|
+==================+================================================+===========+
| | |
|
+==================+================================================+===========+
| APPC | Modes per LU | 64
|
+==================+================================================+===========+
| APPC | Partners per LU | 250
|
+==================+================================================+===========+
| APPC | LUs per mode | 10,000
|
+==================+================================================+===========+
| APPC | APPC LUs per node | 3,000
|
+==================+================================================+===========+
| APPC | APPC Remote LUs per connection | 10,000
|
+==================+================================================+===========+
| | |
|
+==================+================================================+===========+
| CPIC | CPIC symbolic destination names | 481
|
+==================+================================================+===========+
<Curtis.Smith@Daltile.com> wrote in message
news:ephhr9u3EHA.1404@TK2MSFTNGP11.phx.gbl...

I tried the following suggestion unsuccessfully.

(We can limit LUs "somewhat" like what you are asking, but on a workstation
versus
user record. So, you could assign a pool to the "Everyone" account, then
assign specific LUs to a workstation, then on the workstation configuration
indicate whether you want to limit the LUs to those assigned to the
"Workstation" or "both" the user record and workstation record. I'm not sure
if it would work in the way you are asking however, since the workstation
would not "know" the Pool name if you only set it to allow access to the
"workstation" records.)

In testing, I created a pool with 6 LUs and assigned that pool to everyone.
Then
I defined a workstation and assigned 2 of the 6 LUs specifically to the
workstation
(being sure to select "Use workstation LUs only") As anticipated the only
LUs
availabe to the client where the 2 LUs assigned specifically to the
workstation.
However when launching the client for a second time, I received the same
issue as
before (LU already issued). I could then go through the setting of the
client and
select the second LU and connect, but as you see there is no change in the
ammount
of administration caused by this problem.

My only recourse at this point is to manually create configuration files or
to create
a tool to make management of a Pool for each user feasible. However I do
not know how
having 6,000 pools will impact the stability of the HIS System.

Thanks again for the suggestions.

Tavish · Guest

3098 LU Pools
878 Printer LUs

The set limit for LUs per User/Group is 4000.
All our Pools and Printer LUs are defined in one Group. We will shortly
reach this limit. How can we solve this problem - any ideas?

Neil Pike · Guest

Tavish - why so many pools? I only have about a dozen defined despite the HIS
domain providing access to several different mainframes (and hundreds of apps
within those mainframes).

And why do they all need to be assigned to the same group?

Tavish · Guest

Neil,

thanks for your quick reply.

I will try to answer your question as to why we have so many pools...:
The reason is, that we have to provide high availability and have therefore
introduced dedicated backup servers. These hold backup PUs and LUs.
(We use a backup Lu for every active LU)
The active/backup LUs are grouped in pools.

"Neil Pike" wrote:

Neil Pike · Guest

Tavish,

Needing HA is very common, but unless you're needing to assign individual LU's to
individual users I don't see why so many pools are needed. And if you were doing
individual LU's/pools for individual users, then I can't see why they all need to be
assigned to the same user/group.

I'm probably mis-understanding your setup and why you have it configured the way
you do.

The short answer is that there's no way to increase the limits, so a
re-design/re-configure will probably be needed (hence trying to understand your
setup). You can always split your set-up into multiple subdomains and get over the
limits that way, but that's probably not going to be acceptable....

Stan Fry · Guest

I was told by several Microsoft individuals on this forum that the limit for
LU pools is 10,000 on HIS. So if your running HIS it should not be a
problem. I have a similar situation where I have individual LU's assigned to
users.

Stan

"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000628f.00fd193e@compuserve.com...

Tavish · Guest

Hi Neil,

We are planning to split users into additional groups. We know, that we now
have to accept the ‘4000’ limit. But, as we had to use existing groups (ADS)
we ran into problems with users which are members of both groups. (3270
displays 653 Error).
Is it possible to bind the pools to ‘Workstation’ and in doing so bypass
the set limit?

"Neil Pike" wrote:

Neil Pike · Guest

Tavish,

See instructions below...

Assigning LUs to Workstations
See Also
Associating 3270 Printer LUs with 3270 Display LUs
You can assign LUs to a workstation rather than a user, which makes it possible
to lock LUs to a particular workstation. Assigning an LU to a workstation makes
it easier for users to find and access different resources. For example, it
makes it easier for a user at a workstation to use a printer located near the
workstation, instead of one assigned to the user.

With this feature, you can insert a workstation object and define it by
specifying parameters such as IP address, workstation name, and others. You can
then assign 3270 display and printer LUs to the workstation. These LUs will be
accessible to any users connecting from those workstations. The LUs do not need
to be specifically assigned to the user.

For example, 200 hospital users share 50 workstations and 50 printers. Users
may want to use any of the 50 workstations and 50 printers. They can log on to
any of the 50 workstations and print using the printer attached to that
workstation. Instead of assigning all 50 printers to 200 user accounts, the
administrator can add the 50 workstations to Host Integration Server 2004 and
assign a printer LU to each workstation. When a user logs on to any of the 50
workstations, the printer attached to that workstation will be available in the
list of LUs.

You can also configure a workstation so that it will only allow the use of
those LUs assigned to the workstation, regardless of the user who is logged on.
You can assign LUs to workstations in the same manner that LUs are assigned to
users.

For example, if the workstation is flagged for restricted access, a user cannot
gain unauthorized access to other LUs regardless of the user ID and password
that is used. This feature enhances network security.

To assign LUs to workstations

In the Host Integration Server 2004 console tree, right-click Workstations,
point to New, and then click Workstation.
Fill in the Workstation Properties dialog box.
Click OK to add the new workstation.
To assign LUs to the workstation, click Connections, and then click the
connection that contains the LUs.
Right-click the LU that you want to assign, and click Assign to Workstation.
Click the workstation, and click OK.
On the Action menu, click Save Configuration.

Note All workstation users must be members of the same SNA subdomain. You can
avoid having to add each user to the subdomain by assigning the Everyone group
to the subdomain and assigning no LUs to the group.

Neil Pike. Protech Computing Ltd

Tavish · Guest

Neil,
Thank you for the instructions.
As we operate in a Citrix environment, we would like to define our terminal
servers (100) as ‘Workstation’. Will we encounter the same limit (4000 pools
per ‘Workstation’)?
And will we be able to bind all pools and printer LUs to ‘Workstation’
without encountering the ‘653’error?

"Neil Pike" wrote:

Charles Ezzell (MSFT) · Guest

The same limits apply as far as I know, as internally we treat a workstation
record as a user record.

Citrix (or Terminal Services itself) could throw other wrinkles into the
situation when trying to assign workstation addresses.
See
328524 Assigning Logical Units to Specific Terminal Server Clients
http://support.microsoft.com/?id=328524

You would need a post sp1 fix for Host Integration Server 2000 clients in
order to get this fix. It will be in Service Pack 2, which is being worked
on at this moment, but no time frame is currently set for it's release. This
fix is in Host Integration Server 2004.

Charles

"Tavish" <Tavish@discussions.microsoft.com> wrote in message
news:76B57FB5-F4AB-49A4-8735-BEBBA2F01336@microsoft.com...

Neil Pike · Guest

Tavish,

Does the Citrix server that a user connects to relate to what printer(s) they want
to use then? I've not come across a Citrix environment like that before, and I've
setup a few.

(Charles has answered the main Q)

	Windows Server Forum Index -> Host Integration Server	All times are GMT
Page 1 of 1