Jerry,
this is a know problem with the USS client. The reason is probably a memory
leak somewhere. Check with you local IBM support, as this has an apar
attached to it. If I'm correct, a start/stop of the schedule process should
fix it.


Wim Feyants

Reply via email to