Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Steve Gentry
I finally got the programmable operator piece working. I'm a little embarrassed by my mistake. I had a misplaced RETURN command in the EXEC. I looked at the EXEC I don't know how many times and didn't see it. Do'h! Now my next opportunity. I want to take the file that was placed in the

Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Stracka, James (GTI)
Try READCARD or EXECIO? -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Steve Gentry Sent: Wednesday, April 11, 2007 11:23 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Programmable operator working: my

Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Marty Zimelis
Of Steve Gentry Sent: Wednesday, April 11, 2007 11:23 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Programmable operator working: my bad; next opportunity I finally got the programmable operator piece working. I'm a little embarrassed by my mistake. I had a misplaced RETURN command in the EXEC

Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Steve Gentry
System IBMVM@LISTSERV.UARK.EDU 04/11/2007 11:28 AM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: Programmable operator working: my bad; next opportunity Try READCARD or EXECIO? -Original Message- From

Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Steve Gentry
cc: Subject:Re: Programmable operator working: my bad; next opportunity Try READCARD or EXECIO? -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Steve Gentry Sent: Wednesday, April 11, 2007 11:23 AM To: IBMVM

Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Doug Breneman
PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/11/2007 11:28 AM Please respond to The IBM z/VM Operating System To:IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: Programmable operator working: my bad; next opportunity

Re: Programmable operator working: my bad; next opportunity

2007-04-11 Thread Alan Ackerman
/* Read in a NOTE file but do not put it in ALL NOTEBOOK */ /* Untested !!! */ arg spid fn ft fm 'MAKEBUF' buf = rc push 'FILE' fn ft fm 'EXEC PEEK' spid '(FOR *' code = rc 'DROPBUF' buf 'ESTATE' fn ft fm if rc = 0 then 'CP PURGE READER' spid exit code

Re: Programmable operator

2007-04-09 Thread Tom Duerbusch
I wasn't aware that PROP will act upon something being delivered in the reader queue. It likes messages, not queue elements. The only thing I can think of, is to route the rdr queue elements to another service machine (with wakeup rdr specified), and have it process the reader entry and msg

Re: Programmable operator

2007-04-09 Thread Romanowski, John (OFT)
Steve, Could you post the part of your RTABLE that handles the SMTP RDR file message? Do you have a PROPSCAN logfile that shows the incoming messages and post the SMTP RDR file message too that's supposed to trigger the RTABLE entry?

Re: Programmable operator

2007-04-09 Thread Tom Rae (WFF)
, 2007 12:41 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Programmable operator I wasn't aware that PROP will act upon something being delivered in the reader queue. It likes messages, not queue elements. The only thing I can think of, is to route the rdr queue elements to another service machine

Re: Programmable operator

2007-04-09 Thread Kris Buelens
You need to trap the message RDR FILE FROM in class 3 (async CP message). A problem is that when a RDR file arrives when the PROP machine would not be active, your action routine will not see the RDR file. Therefore, an action routine for RDR files should be able to handle more than 1 file

Re: Programmable operator

2007-04-09 Thread Romanowski, John (OFT)
@LISTSERV.UARK.EDU Subject: Re: Programmable operator You need to trap the message RDR FILE FROM in class 3 (async CP message). A problem is that when a RDR file arrives when the PROP machine would not be active, your action routine will not see the RDR file. Therefore, an action routine for RDR files should

Re: Programmable operator

2007-04-09 Thread Alan Altmark
On Monday, 04/09/2007 at 01:41 EST, Tom Duerbusch [EMAIL PROTECTED] wrote: I wasn't aware that PROP will act upon something being delivered in the reader queue. It likes messages, not queue elements. If you have CP SET CPCONIO IUCV, the RDR FILE message will be seen by PROP. Or you can

Re: Programmable operator

2007-04-09 Thread Steve Gentry
PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/09/2007 03:12 PM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject:Re: Programmable operator On Monday, 04/09/2007 at 01:41 EST, Tom Duerbusch [EMAIL

Re: Programmable operator

2007-04-09 Thread Michael Donovan
by: The IBM cc z/VM Operating SystemSubject [EMAIL PROTECTED] Re: Programmable operator ARK.EDU

Re: Programmable operator

2007-04-09 Thread Kris Buelens
2007/4/9, Michael Donovan [EMAIL PROTECTED]: Steve, I've always let my PROP action routine exec see all incoming reader files and then let the exec sort out what it wants. The following line in the PROP RTABLE works for me (the scale is there just to show column placements):

Re: Programmable operator

2007-04-09 Thread Michael Donovan
] Subject ARK.EDU Re: Programmable operator 04/09/2007 05:36

Re: Programmable Operator: The epic conclusion

2006-08-07 Thread Jon Brock
Tomangle Terry Pratchett, a one-in-a-million-chance will come through nine times out of ten. Jon snip I have an entry in the RTABLE to look for NOT in positions 10 thru 13. The last three letters of the file name just so happen to be in 10 thru 13. What are the chances?

Re: Programmable Operator

2006-08-03 Thread Kris Buelens
But, even with DIAG 8, the limit is 240 chars for the command. 'CP MSG ' silently truncates the message call diag 8,'MSG ...' gives a REXX syntax error if the command is too long. Kris, IBM Belgium, VM customer support On Wednesday, 08/02/2006 at 01:10 MST, Don Russell [EMAIL PROTECTED]

Re: Programmable Operator

2006-08-03 Thread Alan Altmark
On Thursday, 08/03/2006 at 01:32 ZE2, Kris Buelens [EMAIL PROTECTED] wrote: But, even with DIAG 8, the limit is 240 chars for the command. 'CP MSG ' silently truncates the message call diag 8,'MSG ...' gives a REXX syntax error if the command is too long. Duh. I know this. There is

Re: Programmable Operator some additional info

2006-08-03 Thread Steve Gentry
: Subject:Re: Programmable Operator But, even with DIAG 8, the limit is 240 chars for the command. 'CP MSG ' silently truncates the message call diag 8,'MSG ...' gives a REXX syntax error if the command is too long. Kris, IBM Belgium, VM customer support On Wednesday, 08/02/2006

Re: Programmable Operator some additional info

2006-08-03 Thread Jim Vincent
That should be simple enough and should work without a hitch on 5.2 (or any release). Are you really really sure that the RTABLE is not catching the message somewhere else? Can you copy your RTABLE entry and post it? I would sort of expect it to look like:

Re: Programmable Operator some additional info

2006-08-03 Thread Alan Altmark
On Thursday, 08/03/2006 at 08:34 EST, Steve Gentry [EMAIL PROTECTED] wrote: When the file name is 7 chars or less it works fine, when file name is 8, it appears to never get to HAL. The problem is I don't know if it's getting to HAL and the RTABLE is ignoring it or if it plain doesn't

Re: Programmable Operator

2006-08-02 Thread Kris Buelens
Yes, both MSG and SMSG have length restrictions. An MSG can be longer than an SMSG: MSG is around 229, SMSG (to send via RSCS) 132. So, TELL to a local ystem can send longer commands than TELL to a remote system. My RxServer package allows to create servers that can execute commands. It