Re: 6.1.1 system never ended based on this command ENDSBS SBS(*ALL) OPTION(*CNTRLD) DELAY(*NOLIMIT)

On 27-Jan-2012 06:22 , Jack Kingsley wrote:

The system was active and running when the command was issued, after
3 hours via lan console the only job that would not finally end was
performance data job in qsyswrk subsystem. The NFS jobs took forever.
In any event I wanted to know what a work around to this might be.

Aside from a specific time limit for the controlled-end processing allowed for the subsystems [their jobs] to complete, being both a period after which those jobs would be ended immediately and something that might not assist anyhow [given some job would not end]...

Investigate the reason for the _unnamed_ jobs not ending in a timely fashion when requested to do so by either an ENDSBS or ENDSYS request. Apply the preventive fixes [or perform the procedures necessary; IMO a cop-out for a sfw provider] to ensure that those job will henceforth end properly and timely.

Searching APAR and PTF for the job name that does not end might be helpful in that regard. Or perhaps instead, contact a service provider to assist in that research and perhaps a more thorough review of the incident [though apparently after-the-fact] either to ensure a good match [for a preventive fix] or to report the issue as what is presumed to be a new problem.

Regards, Chuck