Re: Deletion of Virtual Display Devices

["Larry \"DrFranken\" Bolhuis" <midrange@xxxxxxxxxxxx>]

Problem with the system value (QAUTOVRT) is that when you hit it the 
next guy can't get on. THat's OK for everyone else, but not for ME!! :-)

One of the things I talk about in my session 'Clean up your i' is 
communications and devices like this. They don't take significant disk 
space, that's not the point. They do consume a small bit of resource as 
the system needs to keep track of them and decide for every line, 
controller, and device if it needs be brought on line and for printer 
devices if a writer needs starting.

More importantly though is when stuff stops working and you need to 
figure out how to fix it. "Hmmm, there are fourteen line descriptions 
out there, and two are active. But EDI has stopped and 7 of those lines 
reference EDI stuff. Which one of those am I using?" (hint: likely 
NONE!) I'm a BIG FAN of smoking all those old lines, controllers, and 
devices and keeping the system clean. When something does break things 
that aren't 'clutter' making troubleshooting simpler!

I compare this to removing all those extra Ethernet and other cables 
from the racks in the data center. When you don't keep them cleaned up 
and you find a cable just hanging, you can't know if it's supposed to be 
hanging or connected!
	-DrF

On 9/7/2022 8:47 AM, Jim Oberholtzer wrote:
> The number of virtual devices can be controlled by a system value as well.  I don’t see the value in removing virtual devices in most environments, the exception being where specific authority to devices is set due to security requirements.  Then again in those environments we don’t automatically create them either.
>
> Jim Oberholtzer
> Agile Technology Architects
>
>
>
> > On Sep 7, 2022, at 7:39 AM, Rob Berendt <rob@xxxxxxxxx> wrote:
> >
> > I rather manually do it, if the mood strikes me.  And I do it by
> > WRKDEVD DEVD(*VRTDSP)
> > Sure I may be deleting someone's current workstation but it will automatically rebuild also.  Some of these haven't been used in a long time.
> >
> > Odd that it would delete the message queue and not the device.  I can think of a few oddball scenarios where this would happen.
> > - QSECOFR not specifically authorized to this workstation.  (See QLMTSECOFR)
> > - Workstation using a different message queue
> > But instead of guessing I'd look at the joblog.
> >
> > The object description does have a last used date.
> >
> > Rob Berendt
> > --
> > IBM Certified System Administrator - IBM i 6.1
> > Group Dekko
> > Dept 1600
> > Mail to:  7310 Innovation Blvd, Suite 104
> >           Ft. Wayne, IN 46818
> > Ship to:  7310 Innovation Blvd, Dock 9C
> >           Ft. Wayne, IN 46818
> > http://www.dekko.com
> >
> > -----Original Message-----
> > From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Sizer, Joseph via MIDRANGE-L
> > Sent: Wednesday, September 7, 2022 8:21 AM
> > To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
> > Cc: Sizer, Joseph <JSizer@xxxxxxxxxx>
> > Subject: Deletion of Virtual Display Devices
> >
> > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
> >
> >
> > There is a job on my system that I have inherited that executes at 3:00 AM.  The job varies off all virtual display devices (QPAD*) and then deletes them.  If they are needed again, the system will recreate them.
> >
> > Does anyone else utilize this practice and do you see any benefit to purging virtual display devices rather than just allowing them to accumulate?
> >
> > We have had a couple recent occasions where the device description was not deleted but the associated message queue was.
> >
> >
> > Joe Sizer
> > IBM I Power9 Administrator
> > Pencor Digital Services
> >
> > Pencor Services, Inc.
> > 462 Delaware Ave
> > Palmerton Pa 18071
> > Office: 610.826.9080   Ext. 2117
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
> >
> > Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com