|
RCLSTG won't fix it. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Jones, John \(US\)" <John.Jones@xxxxx To l.com> "Midrange Systems Technical Sent by: Discussion" midrange-l-bounce <midrange-l@xxxxxxxxxxxx> s@xxxxxxxxxxxx cc Subject 02/14/2007 10:05 RE: Object with Invalid Name AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Suggestions: 1. Try iSeries Navigator. 2. Run a Reclaim Storage. 3. Try Qshell: rm /QSYS.LIB/YOURLIB.LIB/1.FILE -- John A. Jones, CISSP Americas Information Security Officer Jones Lang LaSalle, Inc. V: +1-630-455-2787 F: +1-312-601-1782 john.jones@xxxxxxxxxx -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jlowary@xxxxxxxxxxxxx Sent: Wednesday, February 14, 2007 8:54 AM To: midrange-l@xxxxxxxxxxxx Subject: Object with Invalid Name Anyone know of a way (other than maybe DST) to get ride of an object that has an invalid name? We have an file that has the name of "1", don't know how it got there but has been there since '98 (it might be the file formally named Prince). Only way we found it was thru some software we are using to monitor and keep authorities compliant. It showed up on the list as Non-Compliant. You can't delete/rename/etc or do a display of the File Description directly. Only way you can see it is to do a WRKOBJ or DSPFD for that library and do all files, then it will be in the list that it gives you. If you try and access it directly then you get the message that object name is not valid. Strange? Jim Lowary System Analyst, Salton Inc. (573) 447-5500 -- 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 email is for the use of the intended recipient(s) only. If you have received this email in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this email without the author's prior permission. We have taken precautions to minimize the risk of transmitting software viruses, but we advise you to carry out your own virus checks on any attachment to this message. We cannot accept liability for any loss or damage caused by software viruses. The information contained in this communication may be confidential and may be subject to the attorney-client privilege. If you are the intended recipient and you do not wish to receive similar electronic messages from us in future then please respond to the sender to this effect. -- 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 mailing list archive is Copyright 1997-2025 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.
midrange.com
