RE: Commands to joblog

Thanks to all those who have replied to my request.  I have an acceptable
(but not what I want) solution.

I really, really, REALLY want to have a "Command" type of message instead
of a Request message (yes, the two are very different in function and in
the joblog... try it).  If anything were to go wrong with the program after
sending the *RQS message but before receiving it to make it old, the
request will be processed after the program ends... and I don't like that.
I'd rather just have a log.  But I suppose it's acceptable risk.

Thanks so much for the great pointers and advice regarding this.  I did
have to roll my own, but it wasn't a big deal.

Dennis






Anton Gombkötö <gombkoetoe@assoft.com>@midrange.com on 01/17/2002 12:26:22
PM

Please respond to mi400@midrange.com

Sent by:  mi400-admin@midrange.com


To:   mi400@midrange.com
cc:
Subject:  RE: [MI400] Commands to joblog


The following is my understanding and how i use it in my - for me! - 95%
perfect menu programs:

There is no "command" message type. Commands are "requests".
A CL program with a RCVMSG *RQS in it is called a "request processor" in
the manual.

I send them and receive them with the QMHxxxxx APIs.
And these messages are read by OS/400 command lines, too. So entering
commands in my program and retrieving them in a OS/400 command line works.

I have to check out the QCAPCMD API - that was new for me!

And: You'll find everything in Gene Gaunt's article  - link posted by
Carsten Flensburg - thanks!

0.02 Euro

best regards, Anton Gombkötö

_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/mi400
or email: MI400-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.