RE: iNav Messages replacement

I'm thinking something went awry with your post.



-----Original Message-----
From: Jack Woehr [mailto:jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 20, 2017 1:48 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: iNav Messages replacement

# autoreply.ublu ... Find and reply to all *INQ & *NOTIFY messages in a given MSGQ# Example from Ublu Midrange and Mainframe Life Cycle Extension language# https://github.com/jwoehr/ublu# Copyright (C) 2016 Jack J. Woehr http://www.softwoehr.com# See the Ublu license (BSD-2 open source)# jack j. woehr jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx jwoehr@xxxxxxxxxxxxx# 2015-03-10 # instance message queue*FUNC* getMsgQ *(* *system* *user* password ifspath *msgq* *)* *$[*
*LOCAL* @as400
*as400* *-to* @as400 @@system @@user @@password
*msgq* *-to* @@msgq *-as400* @as400 *-new* @@ifspath*]$* # get list of messages needing reply*FUNC* getReplyMsgs *(* *msgq* replylist *)* *$[*
*msgq* *--* @@msgq *-query* *-reply* *-to* @@replylist*]$* # get messages, walk list and offer user chance to reply to each*FUNC* autoreply *(* *system* *user* password ifspath *)* *$[*
*LOCAL* @msgq *LOCAL* @replylist *LOCAL* @key
*LOCAL* @answer *LOCAL* @tf *LOCAL* @reply
getMsgQ *(* @@system @@user @@password @@ifspath @msgq *)*
getReplyMsgs *(* @msgq @replylist *)*
*FOR* @msg in @replylist *$[*
*msg* *--* @msg *-to* @key *-key*
*put* *-from* @msg
*ask* *-to* @answer *-say* ${ Do you wish to reply to this message? (y/n) }$
*test* *-to* @tf *-eq* @answer y
*IF* @tf *THEN* *$[*
*ask* *-to* @reply *-say* ${ Please enter your reply }$
*msgq* *--* @msgq *-sendreplybinkey* @key @reply
*put* ${ Reply sent. }$
*]$*
*]$**]$*


On Wed, Sep 20, 2017 at 12:43 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

This is for info messages on QSYSOPR. We have a monitor that handles
inquiry messages. It's just the info messages that do matter. I'm
not sure you can do a monitor for that. There's no way to predefine
every message that matters.



-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Wednesday, September 20, 2017 1:04 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: iNav Messages replacement

Some people leave a dedicated 5250 session open for break messages.
They insist their messages be in break mode so they get them in a
timely fashion. However they also always find it extremely disruptive
and never use that session for anything else and leave it in the background.
See why I am not a big fan of break messages?

Also, it's also quite common, with messaging software to just have it
monitor a message queue and send them on as email, or some such thing.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all attachments is for the intended recipient(s) only and may contain confidential and privileged information. If you are not the intended recipient of this communication, any disclosure, copying further distribution or use of this communication is prohibited. If you received this communication in error, please contact the sender and delete/destroy all copies of this communication immediately.