Problems with virtual device connections

I am in the process of upgrading my old F45 computer (V2R3) to a 310 machine
(V3R2). In the conversion, several people will need to access both systems
using pass-thru from one system to another. I cannot establish more than two
virtual sessions on my v2r3 machine.

Procedure:
1. Deleted all virtual devices attached to QPACTL01. These were named
QPADEV0001-0003.
2. From 310, strpasthr to F45 on two sessions. Everything works fine.
Creates QPADEV0001 & 0002
3. On the 310, attempt to strpasthr to F45; the following occurs
(automatically by system):
        a. On the F45, a device named QPADEV0003 is created, and is varied
on
        b. On the 310, the following job log is created:
                > strpasthr s10b4250                                        
                Virtual device QPADEV0003 selected at system S10B4250.
(CPI8903)
                Device QPADEV0003 not accessed by system S10B4250.
(CPF8919)
4. If I repeat procedure step 3 above for more sessions, it will create
QPADEV000x for each session, but the same job log appears for any connection
not named QPADEV001 or QPADEV002.

Facts:
1. Dial in connections that use the virtual devices have the same problem as
the 310 does when connecting to the F45.
2. The virtual devices connect to a controller called "QPACTL01". 
3. System value  QAUTOCFG is set to 1 (on).
4. System value  QAUTOVRT is set to 100.
5. For the subsystem QCMN, MAXACT is set to *NOMAX.
6. QCMN has three jobs running, and the load is non-existent. CPU use
average is < 20%.

Anyone have any suggestions on fixing or getting around this problem?

Thank you.
Patrick Shrader
White Knight Engineered Products

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---