RE: How to "reallocate" Session B in Client Access?

I haven't seen that issue in a long time. I'm on the version you mention, though I haven't checked my service pack level in a while.

The options are plentiful as compared to the older versions. It used to be I'd edit the pcswin.ini in "C:\Program Files\IBM\Client Access\Emulator\Private\" to fix issues like that. Now some of that information can be stored in your .ws files directly.

Mine for example are in:
C:\Users\<username>\AppData\Roaming\IBM\Client Access\Emulator\private

I haven't tried to hack this version.

Your best result on the version number is from System i Access for Windows Properties. I have V6R1M0 SI42423.
--
Sean Porterfield


-----Original Message-----
From: John Yeung

Every so often I am futzing around with multiple sessions and I eventually lose the ability to create Session B. I have a few .ws files and if I open one, I get Session A; but then if I open another one, I get Session C. In the past, through much aimless rejiggering of settings, opening and closing things, etc. I have eventually been able to convince Client Access that I really don't want it to reserve Session B anymore, and that I really want to open a new Session B.
But for the life of me, I can't figure it out now. Does anyone know how to do this, besides sacrificing a small goat at the altar of the i?

In case it makes a difference, I used to use the Client Access that came with V5R2, from Windows XP. I recently got a new machine at work and now I'm using the Client Access that comes with 6.1 (clicking the About... in the Help menu tells me it's version 5.9) on Windows 7 Pro 64-bit (but still connecting to the same V5R2 box).

John
--


This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.