RE: Easy virtual device cleanup - tips?

Yep - I meant devices.  Looks like if I do a WRKDEVD DEVD(*VRTDSP) I can
get a decent list anyway - the main problem isn't with the QPAD* ones,
it's folks who have left the "Use PC Name" checked in iSeries Access
5250 or decide to define their own session names - and thus have strange
device sessions created on assorted boxes. 

Thanks for the info.

Justin C. Haase - iSeries System Administrator
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation
email - justin.haase@xxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Monday, September 05, 2005 6:37 PM
To: Midrange Systems Technical Discussion
Subject: Re: Easy virtual device cleanup - tips?

Justin

I assume you mean devices, not sessions. The sessions would need to be
ended, then it should be possible to delete the device descriptions. You
COULD use

ERASE OBJLNK('/qsys.lib/qpadev*.devd')

to get rid of all of them in QSYS, which is where they all are, IIRC.
Use

wrkobj *all/qpadev*

to find them. I found a couple on a system that were named
QPADEV,QPADEVA1, and QPADEVA2, so you might want to use something like

ERASE OBJLNK('/qsys.lib/qpadev0*.devd')

ERASE OBJLNK('/qsys.lib/qpadev1*.devd')

etc, to limit what is deleted.

Of course, you need to deal with MSGQs and OUTQs of the same names as
the devices. I forget, does deleting a device description also delete
the attendant output queue?

A harder way? Use QUSLOBJ with appropriate parameters to get the list of
device descriptions, use another API I don't remember to determine the
status of each device in turn, filter according to your naming rules,
then use DLTDEVD for each one selected.

HTH
Vern

At 05:59 PM 9/5/2005, you wrote:

>Happy Labor Day, all - quick question.
>
>If I wanted to get rid of *EVERY* virtual 5250 session on the system - 
>every QPADEV*, every incorrectly named session that people have created

>with Client Access - what would be the easiest way to get rid of them 
>all and start over?  On some older systems which have been around for 
>ages there's sometime hundreds of oddly-named sessions, and I'd just 
>like to get rid of them ALL and start over, either with defined session

>names mapped to PCs, or creating 100 devices and turning autoconfig
off.
>
>Any thoughts or assistance is appreciated!  Thanks!
>
>Justin C. Haase - iSeries System Administrator IBM Certified Systems 
>Expert - eServer i5 Kingland Systems Corporation email - 
>justin.haase@xxxxxxxxxxxx
>
>
>CONFIDENTIALITY NOTICE:  This e-mail communication, including 
>attachments, is covered by the Electronic Communications Privacy Act,
18 U.S.C.
>2510-2521, is confidential, and may be legally privileged.  If you are 
>not the intended recipient or believe you received this communication 
>in error, please reply to the sender indicating that fact and delete 
>the copy you received.  In addition, retention, dissemination, 
>distribution, copying, or otherwise use of the information contained in

>this communication is strictly prohibited.  Thank you.
>
>--
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
>list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
>unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a

>moment to review the archives at 
>http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.