× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



There was a thread on BPCS_L about this some years ago, because BPCS creates work areas, members, data areas, all sorts of objects, named after work sessions. We try to name our sessions after WHERE twinax is in the offices, like dept, but naming after PERSON office is more popular.

If you do a DSP* whatever directory of objects to some *OUTFILE you can get at DATE last used, so you want to keep all that were used in the last month or so, and also know naming conventions for a few odd ball objects that need to be kept even if not used recently. Feed this into some kind of CL that will delete 100% of what the *OUTFILE found, excluding a few special cases.

For each device name, we'd need to know the kinds of objects created named after them, and condition the delete, because not all device names will have all the BPCS objects that can be created.

On my to do list.

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.