RE: Break handling program

One of the reasons I used a special message queue is because it can be
protected better than the workstation message queue.

I am not sending messages to batch jobs just interactive jobs. I can include
the command in the message but it has to be prefixed with a special code
word before the break handling program will execute it.

Normally, the QSECOFR signon doesn't execute the program which creates the
message queue so you can't send commands to its job.

Albert 


        -----Original Message-----
        From:   midrange-l-bounces@xxxxxxxxxxxx
[SMTP:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Duzenbury
        Sent:   Friday, August 27, 2004 11:28 AM
        To:     Midrange Systems Technical Discussion
        Subject:        RE: Break handling program

        On Fri, 2004-08-27 at 10:26, York, Albert wrote:
        > I had a similar situation a few years ago. However, I changed the
initial
        > program. It creates a message queue in the QRPLOBJ library named
BRKMxxxxxx,
        > where xxxxxx is the job number (i.e. BRKM407689), and puts it n
break mode
        > with a break handling program. If I want that job to execute a
command I
        > send a message to its message queue.

        Albert, this sounds interesting.  But why not CHGMSGQ the
workstation
        message queue?  Are you sending commands to batch jobs?

        Also, do you send the command in the message?  If so, what's to
prevent
        someone from subverting the entire system by sending a malicious
message
        command to, say, QSECOFR?

        >  
        > Albert 
        --
        Regards,
        Rich

        Current Conditions in Des Moines, IA
        Broken Clouds
        Temp 77F
        Winds out of the Northeast at 10mph

        --
        This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list
        To post a message email: MIDRANGE-L@xxxxxxxxxxxx
        To subscribe, unsubscribe, or change list options,
        visit: http://lists.midrange.com/mailman/listinfo/midrange-l
        or email: MIDRANGE-L-request@xxxxxxxxxxxx
        Before posting, please take a moment to review the archives
        at http://archive.midrange.com/midrange-l.