On Sun, 11 Jan 2009 17:39:06 +0100, Rob wrote:
>But I think that's because the file is to yourself... When the file
>is sent both sender and recipient get the info. The sender as
>synchronous message (trapped by diag8) and the recipient by IMSG. When
>you're both, then the IMSG is skipped.
They'r
On Sat, Jan 10, 2009 at 11:46 PM, Glenn Knickerbocker wrote:
> I'm not talking about poorly-behaved or malicious programs. I'm talking
> about perfectly ordinary things like SENDFILE EXEC using Diag(8, 'CLOSE
> PUN') to capture the file sent message. That was the very first thing I
> tried to c
On Sat, 10 Jan 2009 23:03:48 +0100, you wrote:
>And what do you think WAKEUP will do if someone steals the external
>PSW and inserts its own handler?
I'm not talking about poorly-behaved or malicious programs. I'm talking
about perfectly ordinary things like SENDFILE EXEC using Diag(8, 'CLOSE
PUN
On Sat, Jan 10, 2009 at 9:27 PM, Glenn Knickerbocker wrote:
> Not quite. There's not a trivial way to know if some other program has
> messed with the IMSG setting while it had control, or captured the
> arrival message in sending a file to itself. You could, of course,
> inject periodic querie
On Sat, 10 Jan 2009 20:46:20 +0100, Rob wrote:
>Well, starmsg is just that... doing a Q RDR * ALL to mimic the events
>after starmsg has started is trivial.
Not quite. There's not a trivial way to know if some other program has
messed with the IMSG setting while it had control, or captured the
a
On Sat, Jan 10, 2009 at 6:32 PM, Bob Cronin wrote:
> Indeed, which is why I am a bit down on using anything that relies on
> looking for IMSG's to know when a reader file has arrived. Pity there's no
> WAKEUP pipe stage ...
Well, starmsg is just that... doing a Q RDR * ALL to mimic the events
a
Indeed, which is why I am a bit down on using anything that relies on
looking for IMSG's to know when a reader file has arrived. Pity there's no
WAKEUP pipe stage ...
Bob
On Sat, Jan 10, 2009 at 7:15 AM, Kris Buelens wrote:
> When handling RDR files based on an IMSG that arrives, you need some
>
When handling RDR files based on an IMSG that arrives, you need some
mechanism to handle RDR files arrived when the servers wasn't
listening for IMSGs, for example issue a CP Q RDR at startup, and
maybe also every time an RDR files arrives.
WAKEUP (RDR hasn't that problem as it doesn't wait for IMS
Bob,
Look for SERVUS REXX on the pipelines home page. It contains the
immediate command infrastructure you might want: STOP, CMS, JEREMY,
and more.
Just do
pipe (end \)
\s:servus
\starmsg
|s:
|
You might even add a facility to allow your own user ID to send
commands, all it t
I wrote:
> CP SET CPCONIO IUCV
Whoops, I meant IMSG, not CPCONIO. File arrival messages are IMSG. No
need to examine all the other console output.
¬R
Kris Buelens wrote:
> I'll send you my PIPE code that waits for some accounting records, midnight,
> CP/CMS commands, etc. It may inspire you. And, it has a STOP command...
The part he's missing, Bob said offline, is a way to wait for a RDR
file, a la WAKEUP. PIPESERV just does it by watching I
Bob Cronin wrote:
> like it should be simple enough to roll my own, if only I knew where to
> begin.
CP SET CPCONIO IUCV
CP SET SMSG IUCV
PIPE STARMSG *MSG | etc.
and you'll want IMMCMD|PIPESTOP in there somewhere to let you stop it
cleanly.
¬R
I'll send you my PIPE code that waits for some accounting records, midnight,
CP/CMS commands, etc. It may inspire you. And, it has a STOP command...
2009/1/9 Bob Cronin
> Oh and I really (really) do not want to use PIPESERV (or any other tools
> beyond native built-in stages and/or Rexx stages
Oh and I really (really) do not want to use PIPESERV (or any other tools
beyond native built-in stages and/or Rexx stages I write myself). This feels
like it should be simple enough to roll my own, if only I knew where to
begin.
Bob Cronin
On Fri, Jan 9, 2009 at 3:52 PM, Glenn Knickerbocker wrote
This is a brand new application, so I am OK with starting with PIPE. The
thing I don't know how to do is to wait for SMSGs, reader files, etc. and
how to then do things with them, all in the context of the pipeline. I need
a simple example that I can build on. I just don't know where to begin ...
Bob Cronin wrote:
> been too complex for me to get my head around how I'd do them entirely in
> the pipeline, and I've always fallen back to using the standard
> WAKEUP-driven Rexx "Do Forever" loop.
The starting point is just to move that DO FOREVER loop into the
pipeline. Use ADDRESS COMMAND to
Glenn has been after me for years to build my servers such that they run
entirely in the pipeline. Thus far the servers I've needed to write have all
been too complex for me to get my head around how I'd do them entirely in
the pipeline, and I've always fallen back to using the standard
WAKEUP-driv
17 matches
Mail list logo
