Re: Help with "Cannot automatically select virtual device" V5R2

Narayanan

A brute-force method is a communications trace. You can run it and filter
for TCP traffic, all incoming to the iSeries address. You'll get lots of
entries, and the data is arcane, but you should see the device names in
there somewhere, as well as IP addresses. But others may know less unwieldy
ways, I hope.

You activate a comm trace in 1 of 2 ways - STRSST has options to start
service tools, and a comm trace is one of these. This gives you some
(relatively) nice screens to work with the trace. If you are stout of
heart, you can use STRCMNTRC/ENDCMNTRC/PRTCMNTRC/DLTCMNTRC commands to
manage things.

HTH

Vern

At 02:26 PM 11/26/2002 -0500, you wrote:

This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Hi All,

We are at our wits end with the new installation of V5R2 that we did last
weekend. for some reason, our QSYSOPR message queue is filled with CPF87D7
messages ( Cannot automatically select virtual device ). The corresponding
telnet server job QTVDEVICE is running and has a joblog full of CPF8940 s.
We ran a TRCTCPAPP and saw a lot of MCH3401s in that trace

We are running a 2179-620 V5R2, on a LAN with a mixture of Win95, 98, NT
and CA 3.2, CA 3.1 and iseries Access 5.2

It is our belief that there is a PC out in the network that is causing
this error. But we may be completely off on this one.

Question : How do we get rid of this problem, and if it is ( as we believe
) caused by a PC on the network, how can we locate the offending one ?

Thanks and regards
Narayanan R Pillai
Senior Technical Architect
American Medical & Life Insurance
--