|
That looks more coherent, but I still don't know what it is.
My plan B is a little auto-update web app, but I'm still holding on to
hope that IBM didn't leave me high and dry.
-----Original Message-----
From: Jack Woehr [mailto:jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, September 20, 2017 2:52 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: iNav Messages replacement
Midrange munged it. It's color syntaxed in HTML by JEdit. Here it is in
plain text.
# cimtest.ublu ... exercise Common Information Model support in Ublu #
Example from Ublu Midrange and Mainframe Life Cycle Extension language #
https://github.com/jwoehr/ublu # Copyright (C) 2017 Jack J. Woehr
http://www.softwoehr.com # See the Ublu license (BSD-2 open source)
include /opt/ublu/extensions/ux.cim.property.ublu
# cimtest ( url uid passwd namespc )
# ... url is something like https://myserver.foo.org:5989 # ... namespc
is something like root/cimv2 FUNC cimtest ( url uid passwd namespc ) $[
LOCAL @client LOCAL @path
cim -to @client
@client -cred @@uid @@passwd
cim -to @path -url @@url -path
@client -init @path
cim -to @path -namespace @@namespc -objectname CIM_LogicalIdentity
-path
put -n -s ${ Enumerate Instances for }$ put @path
@client -ei @path
string -to ~ -new
cim -to @path -namespace @@namespc -objectname ~ -path
put -n -s ${ Enumerate Classes for }$ put @path
@client -ec @path @true
cim -to @path -namespace @@namespc -objectname IBMOS400_NetworkPort
-path
put -n -s ${ Get Instances for }$ put @path
@client -to @instances -ei @path
FOR @i in @instances $[
put -n -s ${ (( Instance looks like this )) }$ put -from @i
@client -to ~ -gi @i @false @false
lifo -dup lifo -dup lifo -dup
put ~
put ${ *** Putting path for instance *** }$
~ -path
put ${ *** Putting keys for instance *** }$
~ -keys
put ${ *** Putting properties for instance *** }$
~ -to ~ -properties
lifo -dup put ~
FOR @i in ~ $[
put -n -s ${ ***** property is }$ put @i
ux.cim.property.getName ( @i )
put -n -s ${ ***** property name is }$ put ~
ux.cim.property.getValue ( @i )
put -n -s ${ ***** property value is }$ put ~
ux.cim.property.hashCode ( @i )
put -n -s ${ ***** property hashcode is }$ put ~
ux.cim.property.isKey ( @i )
put -n -s ${ ***** property is key? }$ put ~
ux.cim.property.isPropagated ( @i )
put -n -s ${ ***** property is propagated? }$ put ~
]$
]$
@client -close
]$
# end
On Wed, Sep 20, 2017 at 1:24 PM, Rob Berendt <rob@xxxxxxxxx> wrote:
No, he's really into ublu and it just looks different to us.*)* *$[*
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
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/20/2017 03:23 PM
Subject: RE: iNav Messages replacement
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
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*]$* # getthing.
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 thatbackground.
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
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
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.
--
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
--
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.
--
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
