PCOMM 4.2 and Windows 2000

[Jim Snively]

Has anyone been successful getting PCOMM to work under the Winodws 2000
beta? I am getting a hung emulation window and task not responding before
the configuration dialog appears.

--
Jim Snively
Sunoco, Inc.

[Rod Little]

You would be unsupported at this time, so the following advice is "as is".
.

1) Use directory structures WITHOUT spaces for the PCOMM program directory
and location of config files.

2) Try starting PCOMM using a WS file that you create and know works on an
NT/95/98 setup. Start this session from DOS like this :

'c:\pcomm\pcsws.exe d:\pcomm\private\tn3720.ws'

3) If this session starts and works ok, Then choose FILE/SAVE AS and save
it as a new name. This will generate an ICON for you, that you may then be
able to start the session from in future.

I am sure the PCOMM lab folks are working on official support for PCOMM on
Windows2000, but until the Windows2000 code goes gold I doubt they can say
anything officially.

I ( and I guess others ) would be interested to hear how you get on.

Jim Snively wrote in message <7igrn3$ano$1...@news.software.ibm.com>...

[Jim Snively]

No luck. Had a power crash during the uninstall of PCOMM 4.2 so cleaned it
up by hand. Reinstalled to C:\PCOMM. Mapped E: to my WIN98 configuration
C: drive and positioned to the PRIVATE subdirectory by hand. Also
positioned C: to the PCOMM dorectory and invoked C:\>pcsws.exe e:tn3270.ws.
The session appears and can be made active once only. As soon as you leave
the windows it only "beeps" when you click in it again. There seems to be
some interaction between the PCSWS.EXE session startup and the W2K
environment. Probably a difference in the networking protocols(?).

--
Jim Snively
Sunoco, Inc.

Rod Little <rod_l...@uk.ibm.com> wrote in message
news:7ih30r$pt2$1...@news.software.ibm.com...

[Rod Little]

Sorry, I did not notice you are on PCOMM v4.2, I believe some sucess has
been had with PCOMM v4.3. Again, this is try and see "advice"

Jim Snively wrote in message <7ih9h3$rcc$1...@news.software.ibm.com>...

[Jim Snively]

I have the PCOMM 4.3 "beta" code but never got the "gold" code. Just
ordered it.

[Rod Little]

As I said, I am sure we will all be interested in the results of your
"testing"

Jim Snively wrote in message <7ijfq0$p0u$1...@news.software.ibm.com>...

[Don Brady]

Rod Little wrote:
>
> You would be unsupported at this time, so the following advice is "as is".
> .
>
> 1) Use directory structures WITHOUT spaces for the PCOMM program directory
> and location of config files.
>
> 2) Try starting PCOMM using a WS file that you create and know works on an
> NT/95/98 setup. Start this session from DOS like this :
>
> 'c:\pcomm\pcsws.exe d:\pcomm\private\tn3720.ws'
>
> 3) If this session starts and works ok, Then choose FILE/SAVE AS and save
> it as a new name. This will generate an ICON for you, that you may then be
> able to start the session from in future.

OK I tried re-installing Pcom 4.3 carefully following the above steps.
It made no difference.

The behavior is still exactly the same: The Pcom Windows appears but
you
cannot type anything into it. And once you select elsewhere, you
cannot
select the Pcom Window again with the mouse. It will not take the
selection
by illuminating its title bar. It is as if it were already half-dead,
which I
think it in fact is. Then the only way to kill it completely is to use
the Task
Manager to terminate it.

> I am sure the PCOMM lab folks are working on official support for PCOMM on
> Windows2000, but until the Windows2000 code goes gold I doubt they can say
> anything officially.
>
> I ( and I guess others ) would be interested to hear how you get on.

I do not need support, I would just like a fix for whatever bug it is
that
is showing up under Win2000 so that the program is totally inoperable.
I have
many other IBM and other programs which run fine under Win2000.

I think Build 2031 of Win2000 ("beta 3") is more than a beta since many
vendors are
supporting it on their on systems to a degree. For IBM, for example,
see
http://www.pc.ibm.com/software/windowsnt/windows2000.html , which says
in part:

"IBM is participating in several joint marketing programs with Microsoft
to support customers who are making the transition
to Microsoft Windows 2000."

Thanks a lot for your efforts.

Don

[Rod Little]

Sorry I can be no more help Don, as I said at the start it was a best
effort basis from my own experiances.

Perhaps someone from development will chip in now ?

Don Brady wrote in message <3758B8A8...@pobox.com>...

[Don Brady]

Rod Little wrote:
>
> Sorry I can be no more help Don, as I said at the start it was a best
> effort basis from my own experiances.

So you did get it working then. Hmmmmm.

>
> Perhaps someone from development will chip in now ?

I checked the Pcom log and found that the folllowoing error is always
there, under both Pcom 4.2
and Pcom 4.3 when trying to run them under Win200:

"6/10/99 21:25:24.000 SNA Communications Subsystem anflcom.c 184
PCS1543E The APPNAPI driver is not running "

Does this suggest anything to anyone?

Thanks.

Don

[Don Brady]

I think I may have just fixed it, for my limited purposes anyway, by
applying the fix for APAR IC22939.

At the moment I am only trying to get the TN62 subset of Pcom working
that is used by Cics Client. This does not use the PCOM GUI.

But it may (or may not) fix your problem also.

You can download the fix from

ftp://ftp.software.ibm.com/ps/products/pcom/fixes/v4.2x/WIN95_WINNT/ic22939/ic22939.exe

with description at

ftp://ftp.software.ibm.com/ps/products/pcom/fixes/v4.2x/WIN95_WINNT/ic22939/ic22939.txt

I think it is probably good for 4.3 also.

Don

[Jim Snively]

I followed your instructions; installed PCOMM 4.3 to C:\PCOM43 (under W2KP
2031) and copied TN3270.WS from my WIN98 setup. I still get the same
result: PCSWS.EXE opens to the emulation window, but no keys are active.
When end task is selected from task manager it says PCSWS.EXE is not
responding. I guess PCOM in this environment will have to wait for IBM
development :(

[Don Brady]

Ddi you see my post above that APAR IC22939 may fix it?

[Jim Snively]

I do not have an original c:\winnt\system32\drivers\anydlc.sys file to
update. My installation choice was Mirrosoft SNA client. I'm not sure but
suspect this driver may be part of the IBM client. I too would be happy if
TN3270 worked.

[Jim Snively]

Where is pcom.log. I have no such file.

[Don Brady]

Jim Snively wrote:
>
> Where is pcom.log. I have no such file.

Try Start/Programs/ IBM Personal Communications/Administrative and PD Aids/Log
Viewer

[Don Brady]

Well unfortunately, upon further experimentation, while the fix for
APAR IC22939 does allows PCom's TCP62 to work for CICS Client,
the PCOM Gui still does not work. It still hangs there unresponsive
to anything.

If people inside IBM know how to make Pcom 4.x work under Win2000, I
really hope they post here. Or if anyone can think of a way of
submitting a valid APAR, please let me know. (The problem is that
Win2000 has "beta" in its official name, even though it has been
released to some manufacturers for shipment).

[Rod Little]

If you are still willing to try and get this working ?. . . . . .

The hang in PCSWS during startup can be caused by the PCOMM toolbar being
active.

As I guess you cannot start a PCOMM session and hide the toolbar using the
GUI, take a look at the PCSWIN.INI file, in the [LastExitView] section,
try this line ( instead of whatever line is already there for session A ).

A=3 1 229 808 530 83 10 14 400 0 IBM3270

Here it's 83 that denotes the toolbar=hidden attribute. Other values
are 93 (toolbar hidden, menu hidden), 13 (toolbar visible, menu
hidden) and 3 (toolbar visible, menu visible).

Using 13 or 3 will hang PCOM, when it starts.

As I have said all along, this is a best efforts basis.

Would be interested in the results.

Don Brady wrote in message <37607DC6...@pobox.com>...

[Jim Snively]

My PCOM43 was a new installation on W2KP 2031. There was no PCSWIN.INI so I
went to WIN98 hid my tool bar and copied PCSWIN.INI to the W2KP private
subdirectory. The TN3270 session window launched without the tool bar but
still was "not responding". Any other suggestions?

[Pravin Patel]

If you need only Telnet connectivity, then do custom install and do not
install
IBM SNA stack and Socket over SNA, which might work.

[Jerry Nance]

Rod,
This worked for me!!! I'm a happy camper now.
I'm using W2KP 2031. I copied over the PCSWIN.INI file and *.WS files from
my Win98 instance of PCOMM 4.3.
I am using the Pcomm default directory names which has spaces in it.

If I do a Pcom "Start or Configure Session" off the START menu, it still
hangs. But when I double click on a .WS file that I copied over from my
Win98 system with the copied PCSWIN.INI file that defines the toolbar
invisible, it works fine.
Jerry Nance

Rod Little <rod_l...@uk.ibm.com> wrote in message

news:7k8ogt$ed2$1...@news.software.ibm.com...

[Don Brady]

Wow - I have it working that way now too!

Thanks a million to Rod Little for coming up with the solution,
and also to Jim, Jerry and others for reporting their results.

As Jerry did, I also

(1) Did a standard install of PCom 4.3 (no special directory name
needed)
(2) Added a PCSWIN.INI and a *.WS file obtained from elsewhere to the
PRIVATE subdirectory.
(3) Edited the PCSWIN.INI file as Rod described.

It still hung if started from the System menus but runs fine if I
start it by clicking on the .WS file, again just as Jerry describes.

Thanks again,

Don
==============================

[Rod Little]

Phew,

Gald that we got there in the end :-)

Jerry Nance wrote in message <7kepkl$mtu$1...@news.software.ibm.com>...

[Rod Little]

Thanks to Jerry for the final tip and everyone else for chipping in.

Don Brady wrote in message <376BF08F...@pobox.com>...

>Wow - I have it working that way now too!
>
>Thanks a million to Rod Little for coming up with the solution,
>and also to Jim, Jerry and others for reporting their results.
>
>As Jerry did, I also
>
>(1) Did a standard install of PCom 4.3 (no special directory name
>needed)
>(2) Added a PCSWIN.INI and a *.WS file obtained from elsewhere to the
> PRIVATE subdirectory.
>(3) Edited the PCSWIN.INI file as Rod described.
>
>It still hung if started from the System menus but runs fine if I
>start it by clicking on the .WS file, again just as Jerry describes.
>
>Thanks again,
>
>Don
>==============================
>
>Jerry Nance wrote:
>>

[Jim Snively]

I finally got an FMI connection working on W2KP 2031 following the
suggestions in this newsgroup. In my case I reinstalled to C:\Personal
Communications (to match a shortcut in our standard menuing system). I did
try a "save as" to create a shortcut and got an error message and a
application shut down. It looks like this was a problem caused by spaces in
the path. Looks like we will have to do manual configuration of shortcuts
but at least the basic application in functional.

[Jerry Nance]

So now that we know what the problem is, what's the chances of IBM getting
us a patch? Will we have to wait for the W2KP GA code?
Jerry Nance

Rod Little <rod_l...@uk.ibm.com> wrote in message

news:7klb54$l9m$1...@news.software.ibm.com...

> Phew,
>
> Gald that we got there in the end :-)
>
> Jerry Nance wrote in message <7kepkl$mtu$1...@news.software.ibm.com>...