RE: Re: Prevent Operator From Running Backup From Console's Alternate Job

midrange-l-request@xxxxxxxxxxxx wrote:

>   2. Re: Prevent Operator From Running Backup From Console's
>      Alternate Job (Steve Richter)
>
>On 3/6/06, mschutte wrote:
>>
>> We have a need to make sure that the operator is submitting our nightly
>> back up from the console and to make sure that they are NOT doing it from
>> the alternate job.  To be clear, we don't want them on the alternate job
>> that you get by doing a system request and entering a "1".  I was wondering
>> if there anyway, programmatically, that you can tell if the backup is being
>> submitted from the first session or the alternate session (job).
>
>Do you automatically put the message queue of the user in break mode
>when they signon? If so, try using alcobj of the user's message queue.
>
>If this command executes without error:
>   ALCOBJ OBJ(( UserName *MSGQ *SHRRD)) WAIT(0)
>then the job running the ALCOBJ command is the first session to logon.
>( it is the session that user messges will break onto )


Just a minor note... SysReq ought to allow the same user *MSGQ to be locked on 
each side. If the msgq is automatically set at logon, then it will follow back 
and forth as SysReq switches between primary and secondary sessions. I.e., an 
ALCOBJ would succeed.

Tom Liotta