Re: Jobd - Last used date

[CRPence <CRPbottle@xxxxxxxxx>]

John Earl wrote:
> If the last used date is blank, then the JOBD has not been used
> since it was created, that's pretty straightforward.

  Not so simple.  The last used information *also* could have been 
explicitly reset [CHGOBJD USECOUNT(*RESET)] or the object could have 
been restored.  The former leaves the current date, and IIRC the 
latter sets the date to blanks like a create will.

> Lots of folks are paranoid about deleting anything (some of
> those apparently haunt this list, too), but there are several
> safe ways to delete objects, all include some version of using a
> SAV command.
>
> If you have objects you suspect are unused, create a library
> called something like "QUARANTINE", secure the library to *PUBLIC
> Exclude, and move the objects to that library for a period of
> time (90-180 days?). Don't change the authorities on the library
> (in case you have to move it back) and do put an indication of
> what library you moved it from in the object description.  Also,
> be sure to include the QUARANTINE library in some back up
> procedure, and then after the quarantine time has expired, clear
> the objects from the library.

  Move updates the /last change date/ which might interfere with 
attempts to identify currency of the object.  Some object types can 
not be moved.  Changing the text of the object is probably not the 
best option not only for change date, but the original text may be 
considered important & expected to be recovered so a restore versus 
a move back would become desirable.  Personally I would track 
objects in a database file, leaving the original alone, and 
comparing a new inquiry to an old inquiry looking for differences 
that might indicate good reason to remove the object from the list.

> If at anytime you discover that you need the object, you can
> easily restore it to it's original library and carry on as
> needed.  But the fact that you moved it to QUARANTINE in the
> first place means that you're not likely to need it.

  Be sure to save the object private authorities, getting the 
authorities back can be problematic; i.e. newer SAVSYS [SAVSECDTA 
actually] could be from after the object deletion.

> But don't be afraid to delete something when all the empirical
> evidence indicates its not needed.

  Other information besides just the /last used/ really *should be* 
considered as part of the evidence before any action against the object.

> On Nov 20, 2009, at 6:16 AM, Tim Gornall wrote:
>
> > I'm doing some system cleanup.  If the last used date is equal
> > zero, is it safe to assume the object is not needed?  Is there
> > any type of process that would need the object to exist, yet
> > would never update the last used date or number of days used?

  The blank date and zero used days count do not by themselves 
indicate the object is unneeded.  Consider information such as when 
the object was last restored, changed, or created relative to the 
inquiry about the need & currency of the object.  The "object used" 
is an indication that the object was used /for the intended purpose/ 
of the object type and of the feature(s) that utilize the object; 
what those purposes are may not match the expectations of everyone 
similarly.  For example: the DSPSAVF is IMO not a "use", but is 
reflected as such; F5=Display_Report in Query/400 was not originally 
a /use/ of the *QRYDFN object, nor was RTVQMQRY of a *QRYDFN object, 
but 5=Display of a *QRYDFN object is *not* a "use".

Regards, Chuck