On 04-Dec-2013 10:40 -0800, John McKee wrote:

That library does not exist, and, therefore the job submission fails.
Can anybody tell me if Service Director was abandoned and while the
library was removed the scheduled job just slipped through?

Prior to v4r1 the /Service Director/ (SD) function was made available in a library SVCDRCTR; I am unaware how it was delivered\installed, possibly LODRUN. At v4r1 the SD function was made available from an [option of an] LPP which was installed (RSTLICPGM) into the library QSVCDRCTR. In v5r3 the SD portion of that LPP function was eliminated from that LPP, and the library QSVCDRCTR became obsolete and could be deleted, because the SD feature had since been integrated into the OS itself. Apparently Service Director is since implemented via the function provided by the S9 component of the OS; not abandoned, rather, more integral.

Or, is that a separate maintenance thing, with the same result that
it was removed but job scheduler entry remained?

If the pre-v4r1 installation effected the Add Job Schedule Entry of the AUTOPTF entry, then presumably its uninstall function was never performed before the library was deleted. Possibly there was no such uninstall function and\or the user was expected to remove the job entry.

I am not eager to remove things without a good reason. This doesn't
cause harm, but appears to be useless. I can't get any answers here.

Too bad the entry does not reveal, beyond the user who added the entry, when the entry was added. Knowing it was added back in 1998 for example, would probably give great confidence in establishing its probable obsolescence :-) IMO knowing the library name represents something so old, would be sufficient.

This thread ...


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

This mailing list archive is Copyright 1997-2019 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].