RE: Named 5250 telnet sessions

Create your own Virtual Controller, we use the system name appended with a
"V", and then your own devices. Attach the devices to the virtual controller
you created.  Create a command to accept the system you want to start pass
thru to.  The cl for the new command would be something like this:

PGM (&SYSTEM)

DCL &SYSTEM *CHAR 8
DCL &RMTCTLR *CHAR 10

CHGVAR &RMTCTLR (&SYSTEM *TCAT 'V')

STRPASTHR RMTLOCNAME(&SYSTEM)
          VRTCTL(&RMTCTLR)

ENDPGM

You give this to the users and lock down the STRPASTHR command.  This can
make your life a whole lot easier.

   

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


Hi,
We use rumba 5250 with named device support. This by itself works
fine.
Trouble starts when someone passes through (strpasthr) from another
system. Instead of using a qpadevxxx *DEVD it randomly uses one of the
'named' ones which then stops the owner of that devd from connecting
to the 400.
Is there any way I can force strpasthr to the qpadev... devices?
Regards,
Matthias
+---
| 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
+---