|
I'm trimming information, sorry.
DSPDLONAM DLO(*SYSOBJNAM) SYSOBJNAM(NHKS492176)
produces:
Display DLO Name
Document library object . . . . . : *NONE
Folder . . . . . . . . . . . . . : *NONE
Document identifier . . . . . . . : 2000060814492176DOLLAR2
LADN timestamp . . . . . . . . . . : 07D006080E31154C
System object name . . . . . . . . : NHKS492176
Object class . . . . . . . . . . . : *DOC
Auxiliary storage pool ID . . . . : 1
Object overflowed . . . . . . . : N
So, I know the system object name. I'd like to know what it is before I
delete it. I'm a little bit afraid because this was owned by a System
Administrator.
-Jim
-----Original Message-----
From: qsrvbas@xxxxxxxxxxxx [mailto:qsrvbas@xxxxxxxxxxxx]
Sent: Friday, May 07, 2004 3:56 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: finding a *DOC document
Jim:
There ought to be quite a bit more than that displayed. In particular there
ought to be a 'system object name'. It could easily be that this is
something such as a 'document list object' as an example. You can delete it
via DLTDLO specifying *SYSOBJNAM as the document name and *NONE for folder,
and also specifying the system object name in the SYSOBJNAM() parm, if so.
A document list object could be created by running a QRYDOCLIB command with
the right parms. I imagine these things are pretty much forgotten
nowadays... the curse of progress.
Tom Liotta
midrange-l-request@xxxxxxxxxxxx wrote:
> 10. RE: finding a *DOC document (Jim Damato)
>
>It's very weird. I've picked through the DLO commands. DSPDLONAM
produces:
>
>Document library object . . . . . : *NONE
> Folder . . . . . . . . . . . . . : *NONE
--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone 253-872-7788 x313
Fax 253-872-7904
http://www.powertech.com
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.