Re: System 390 connectivity to AS/400 'problem'

["Genyphyr Novak" <novakg@xxxxxxxx>]

Hi,

There is a sort of workaround, but not 100% complete solution. Rename the
QPADEVxxx devices to shorter names. You can vary off existing QPADEVxxxx
devices which are the same type device that starts up during a S/390 session
when they are not in use by someone at that moment. Change the device. Make
sure the device is set to vary on at IPL, so it is back when the system
restarts. Then you can rename the device to 'George' 'John' 'Paul' 'Ringo'
etc.. Then vary them back on.

The system will keep using these names instead of creating new QPADEVxxxx
until it runs out of alreay created devices. So, if you manage to rename all
your QPADEVxxxx devices which are used by the S/390 Telnet sessions to
shorter names, the system will use those first. A QPADEVxxxx will only be
created for a brand new session if, for example more users than normal sign
onto the system and you run out of the already varied on and renamed
devices.

Now you have devices with unique names. This still does not guarantee that
each time someone does a TELNET that they will get the SAME device (they
definitely won't) but at least when they do get a device they can go in and
update the Workstation Data Area and affect only themselves and not 8 other
people too. You will have to then educate the users to check the data area
and adjust as required whenever they get a new session started.

I have tried this here on our boxes, where we TELNET around between AS/400s
on occaision, and it does work.

Hope this helps relieve the problem somewhat.

Thanks

Genyphyr Novak
SSA

-----Original Message-----
From: Zzbpcs@aol.com <Zzbpcs@aol.com>
To: BPCS-L@midrange.com <BPCS-L@midrange.com>
Cc: chip.johnson@prodigy.net <chip.johnson@prodigy.net>
Date: Tuesday, August 22, 2000 9:34 AM
Subject: System 390 connectivity to AS/400 'problem'


>Good Morning,
>
>We are using BPCS 405CD, although I don't believe that is pertinent.
>This is probably an AS/400   - S/390  specific question rather than a BPCS
>question
>but here'e the situation:
>
>We are connecting a System 390 (mainframe) to an AS/400.
>OS 390 (MVS) using TSO telenet client to the AS/400 telenet server.
>The 'problem' is the workstation IDs are :  QPADEV0001, QPADEV0002, etc etc
>Unfortunately BPCS takes only the first 8 characters of the workstation
idea
>to build a data area for SFC500 ( and other programs). And the first 8
>characters means that
>many workstations that look unique do not have a unique data area

>SFQPADEV00)
>We know how to solve the problem using PC's and Client Access.
>But we have a lot of 'dumb' terminals around we do not want to throw
away....
>(yet).
>Any suggestions ?
>
>Peace,
>Jim Barry
>+---
>| This is the BPCS Users Mailing List!
>| To submit a new message, send your mail to BPCS-L@midrange.com.
>| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
>| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
>| Questions should be directed to the list owner: dasmussen@aol.com
>+---
>

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---