|
I was rather wondering why anyone would code something new to an API like
QUSRJOBI when the services are much more productive.
Unless, of course, one is still writing/maintaining applications for
obsolete versions of the OS.
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
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe
Pluta
Sent: Tuesday, August 20, 2019 9:41 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: How is a message key supposed to be used with SNDRPY
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
Yeah, it took me a while to work through that one. I also use a loop to
spin through all QSYSOPR messages looking for a specific message. That
requires using the same key and then passing back in to RCVMSG with
MSGTYPE(*NEXT); it's quite the adventure.
I have not been able to find that value with a traditional green command
like DSPMSG. However, you can get it from the DB2 service
MESSAGE_QUEUE_INFO. It's the MESSAGE_KEY column.
https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_74/rzajq/rzajqviewmessagequeueinfo.htm
On 8/20/2019 8:35 AM, B Stone wrote:
Thanks, Joe.hex value.
So I was really confirming if I needed the hex value or not. It
appears I do. :) Odd that the value is 4 char and you need to use a
value..
Here's a followup... when using SNDRPY manually, where would one find
the message key to enter there otherwise? I couldn't find it anywhere
in the message/job info just working with the job/messages.
On Tue, Aug 20, 2019 at 8:32 AM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
wrote:
Brad, once you get the hex value into a four-character CL field, you
then do this:
SNDRPY MSGKEY( &KEYVAR ) MSGQ( QSYSOPR ) RPY( 'G' ) +
RMV( *NO )
This sends a G to the message in question. The one example I have is
entirely CL, so I do a RCVMSG with KEYVAR, but the concept should be
the same.
On 8/20/2019 8:26 AM, B Stone wrote:
I am looking into the job apis and want to send a reply to a job inhttps://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/WMAttrD
MSGW using SNDRPY.
The Message Key required on SNDRPY is 4 char, and so is the message
key returned from QUSRJOBI:
esc.htm
But, the 4 characters returned are basically garbage and I can only
use SNDRPY if I use the hex value of the key value vs the actual text
ie:find
SNDRPY MSGKEY(x'00003E90') MSGQ(QSYSOPR) RPY('C') RMV(*NO)
works great..
SNDRPY MSGKEY('???°') MSGQ(QSYSOPR) RPY('C') RMV(*NO)
Doesn't work (obviously)
Am I required to use the hex value for SNDRPY? I haven't been able
to
much at all on these values and how they are supposed to be used.ability
Thanks!
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #15 <https://www.bvstools.com/mailtool.html>: The
to add a Footer to each email sent using an IFS stream file.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.