RE: Virtual Device spontaneous combustion!

John,
We are getting the same problem with APPC devices.  We contacted
IBM Support and they seem just as baffled as we are.  This is an
ongoing problem since we have 2500+ APPC devices defined.  We
averaged about 20 a week of devices being deleted and recreated
for awhile.  It seems since we went to V4R3, the problem has
been minimized.  It has dropped to about 5 a month now.

Jim K

> -----Original Message-----
> From: John Earl [SMTP:johnearl@toolnet.com]
> Sent: Tuesday, April 13, 1999 12:58 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re: Virtual Device spontaneous combustion!
> 
> Jeffrey,
> 
> Jeffrey Stevens wrote:
> 
> > Before named device support (TN5250E RFC), it didn't matter, since you
> > could only get QPADEVnnnn devices.  I suspect you are actually talking
> > about named device support not working the way you expected.  True?
> 
> Actually, no.  My problem stems from the fact that I have authorities (and an
> authority list) set on the device, and when the device gets deleted and 
>recreated,
> all my authorities go away.   This makes for the interesting situation where 
>someone
> can connect to the /400, delete an existing device description and then 
>create a new
> device that they are not authorized to use because the authority list is no 
>longer
> attached to the object.
> 
> I'm not crazy about having Telnet delete and recreate device descriptions, 
>but if
> other considerations make that necessary could the authority lists be 
>preserved?
> When a program  is re-compiled all of the old program's authorities are kept 
>in
> place...  couldn't device descriptions behave the same way?
> 
> 
> > You can acheive the desired actions, but it will require use of Telnet
> > Exit programs to accomplish.  The sample exits check for generic
> > compatibility, e.g. if you ask for VT100 terminal type then samples will
> > look for device type of V100 or V220.  Similarly, for 3270, we look for
> > devices of 3277/3278/3279 type.  Printers are 3812 or 5553.  Anything else
> > is 5250 terminal type.  If the device attributes being requested are
> > not radically different from the existing ones, the device is "updated"
> > rather than deleted/recreated (if you are changing NLS for a device,
> > then it is possible the device will be deleted/recreated).  It will be
> > deleted/recreated for sure if your switching generic types i.e., asking
> > for VT100 device which already exists as a 5250.
> 
> We're not changing NLS, and I'm pretty sure that the device type we're 
>talking about
> are all 5250 flavors.   But I can never be sure because I have people from 
>across the
> contry connecting to my AS/400..... and they all have their own favorite 
>emulation
> packages.   :(
> 
> 
> Thanks Jeffrey,
> 
> jte
> 
> 
> --
> John Earl   johnearl@toolnet.com
> 
> PowerTech Toolworks  206-575-0711
> PowerLock Network Security www.toolnet.com
> The 400 School   www.400school.com
> --
> 
> 
> +---
> | 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
> +---
+---
| 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
+---