RE: Problem with Starting QINTER

[qsrvbas@xxxxxxxxxxxx]

Shannon:

I'd guess that this most often happens when someone tries to return from 
restricted state by calling the QSTRUPPGM directly rather than by starting the 
controlling subsystem (which should cause the startup program to be called _in 
addition to_ setting the status of the controlling subsystem).

Perhaps the best way to clear things up is to do ENDSYS and then STRSBS QCTL. 
I'm not totally sure that ENDSYS will work properly if the controlling 
subsystem isn't already started. You might need to end all other subsystems 
manually.

Tom Liotta


midrange-l-request@xxxxxxxxxxxx wrote:

>   1. Problem with Starting QINTER  (Shannon ODonnell)
>
> date: Mon, 21 Aug 2006 19:29:22 -0500
>
> On our i5 530 we have a job that runs from the job scheduler every evening
> around 6, which does an ENDSBS QINTER. At 6 the next morning, another job
> kicks off from the job scheduler and the only thing it does is STRSBS
> QINTER. 
>
> As soon as the command is issued, an error message is fired off to the
> QSYSOPR message queue which says, "* ATTENTION * Controlling subsystem QCTL
> should be started."  (error message ID CPI0906). 
>
> The strange thing is, QCTL is already running. It's never taken down. And of
> course, the system is NOT! In a restricted state anyway.
>
> Even stranger, this same pattern of jobs (i.e., ENDSBS QINTER at night and
> STRSBS QINTER the next morning) when ran, on a 270 (both are at V5R3 with,
> to my knowledge, equal PTF levels),  the error message about starting QCTL
> is never issued.