I would use QMHSNDM, that is the Send Nonprogram Message API. You can send
a message to an array of message queues that are not associated with a
specific program. the User message queue is named the same as the user id.
If you are not sure that your system uses the same name for user message
queue and the user id, you can retrieve the name of the user message queue
and library with QSYRUSRI.

On Thu, Sep 14, 2017 at 9:37 PM, Dan <dan27649@xxxxxxxxx> wrote:

I'm trying to send a message longer than 76 characters to a user from a RPG
program running in batch.

SNDMSG is limited to 76 characters that will display in the user's message

I thought SNDPGMMSG TOUSR() MSGTYPE(*INFO) would be an option, but
apparently this isn't allowed in RPG, although it was submitted to run in
batch. CPD0031 "Command SNDPGMMSG not allowed in this setting."

The API for SNDPGMMSG, QMHSNDPM does not appear to have an option to send a
message to a user, even though SNDPGMMSG has the TOUSR parameter. Am I
missing something?

Also tried QEZSNDMG, but that sends a message to every workstation to which
the user is signed on. That would be a last resort.

- Dan
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related

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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].