× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Dale, guessing on this, i am wondering of the spacing after the E and before
the ) is an issue.

On Thu, Jul 15, 2010 at 4:22 PM, dale janus <dalejanus@xxxxxxxxxxxxxxxxx>wrote:

After much tweaking, I finally have my RPG program calling QCMDEXC and
sending a properly formatted message. I had problems with the length
parm (I had 15s 5, it must be 15p 5). Debug shows I have a properly
formatted command with quotes and everything.

SNDMSG MSG(' Billing batch 1714B entered on 07/14/10 has not
been updated ' ) TOMSGQ(DALE )


After all that work, the message does not appear to be sent.


If I type SNDMSG and prompt at the command line it sends the message.

If I paste the command above and press enter, it never appears in the
message que.

So what am I missing here?

My RPG program is reading a file that has the user name that I put into
the TOMSGQ parm. I suppose I could change it to workstation name and
try sending a break message, but I don't see how that would work any
differently.

Where is the message going to?

---Dale





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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.