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. 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 reader and receive it into a file (or a stem). To my knowledge there are at least two ways to do this. 1) the RECEIVE command (issued from an EXEC) 2) the Pipe READER FILE function both work but not the way I want. From a REXX EXEC, I issue the RECEIVE command. It brings the RDR file in and sticks it in a file called ALL NOTEBOOK even if I specify a file_name, file_type, file_mode. From a PIPE READER FILE function I am able to stick it in the file name, file type that I want but it is not formatted correctly(missing carriage returns and line feeds). I looked at some examples in some IBM manuals, but none touch on how to format it. Bottom line, I want it to be in the format that the RECEIVE command does but I want to give it a unique file name. The name ALL NOTEBOOK or any derivative there of is not an option. Any suggestions? Again, TIA, Steve G.
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@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. 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 reader and receive it into a file (or a stem). To my knowledge there are at least two ways to do this. 1) the RECEIVE command (issued from an EXEC) 2) the Pipe READER FILE function both work but not the way I want. From a REXX EXEC, I issue the RECEIVE command. It brings the RDR file in and sticks it in a file called ALL NOTEBOOK even if I specify a file_name, file_type, file_mode. From a PIPE READER FILE function I am able to stick it in the file name, file type that I want but it is not formatted correctly(missing carriage returns and line feeds). I looked at some examples in some IBM manuals, but none touch on how to format it. Bottom line, I want it to be in the format that the RECEIVE command does but I want to give it a unique file name. The name ALL NOTEBOOK or any derivative there of is not an option. Any suggestions? Again, TIA, Steve G. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Programmable operator working: my bad; next opportunity
As long as you're in PIPES, take a look at the example for DEBLOCK NETDATA in the author's help (PIPE AHELP DEBLOCK). Marty Martin Zimelis Principal maz/Consultancy _ 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 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. 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 reader and receive it into a file (or a stem). To my knowledge there are at least two ways to do this. 1) the RECEIVE command (issued from an EXEC) 2) the Pipe READER FILE function both work but not the way I want. From a REXX EXEC, I issue the RECEIVE command. It brings the RDR file in and sticks it in a file called ALL NOTEBOOK even if I specify a file_name, file_type, file_mode. From a PIPE READER FILE function I am able to stick it in the file name, file type that I want but it is not formatted correctly(missing carriage returns and line feeds). I looked at some examples in some IBM manuals, but none touch on how to format it. Bottom line, I want it to be in the format that the RECEIVE command does but I want to give it a unique file name. The name ALL NOTEBOOK or any derivative there of is not an option. Any suggestions? Again, TIA, Steve G.
Re: Programmable operator working: my bad; next opportunity
I just tried READCARD. It munges all the lines together, it doesn't respect CR and LF. This is the problem I have with Pipe READER FILE I didn't use EXECIO 'cause I thought it was deprecated or something like that. Stracka, James (GTI) [EMAIL 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 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 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. 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 reader and receive it into a file (or a stem). To my knowledge there are at least two ways to do this. 1) the RECEIVE command (issued from an EXEC) 2) the Pipe READER FILE function both work but not the way I want. From a REXX EXEC, I issue the RECEIVE command. It brings the RDR file in and sticks it in a file called ALL NOTEBOOK even if I specify a file_name, file_type, file_mode. From a PIPE READER FILE function I am able to stick it in the file name, file type that I want but it is not formatted correctly(missing carriage returns and line feeds). I looked at some examples in some IBM manuals, but none touch on how to format it. Bottom line, I want it to be in the format that the RECEIVE command does but I want to give it a unique file name. The name ALL NOTEBOOK or any derivative there of is not an option. Any suggestions? Again, TIA, Steve G. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Programmable operator working: my bad; next opportunity
If it makes any difference, the file is coming from VM SMTP as a PUN file Stracka, James (GTI) [EMAIL 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 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 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. 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 reader and receive it into a file (or a stem). To my knowledge there are at least two ways to do this. 1) the RECEIVE command (issued from an EXEC) 2) the Pipe READER FILE function both work but not the way I want. From a REXX EXEC, I issue the RECEIVE command. It brings the RDR file in and sticks it in a file called ALL NOTEBOOK even if I specify a file_name, file_type, file_mode. From a PIPE READER FILE function I am able to stick it in the file name, file type that I want but it is not formatted correctly(missing carriage returns and line feeds). I looked at some examples in some IBM manuals, but none touch on how to format it. Bottom line, I want it to be in the format that the RECEIVE command does but I want to give it a unique file name. The name ALL NOTEBOOK or any derivative there of is not an option. Any suggestions? Again, TIA, Steve G. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Programmable operator working: my bad; next opportunity
PIPE AHELP READER has the following example that might interest you: Examples: A subroutine pipeline that deblocks a reader file that has been sent as a note or with the SENDFILE command: /* Now get the file */ 'callpipe (name READER)', '| reader ', /* Read cards */ '| strfind x41 ', /* Take only cards */ '| spec 2-* 1.80 ',/* Remove CCW code */ '| deblock netdata ', /* Get logical records */ '| strfind xc0 ', /* Take only data */ '| spec 2-* 1 ', /* Remove control byte */ '| *: '/* Pass on */ Doug Breneman z/VM Development IBM Endicott New York Wednesday, April 11, 2007 1:55 PM To: IBMVM@LISTSERV.UARK.EDU cc: From: Steve Gentry [EMAIL PROTECTED] Subject: Re: Programmable operator working: my bad; next opportunity I just tried READCARD. It munges all the lines together, it doesn't respect CR and LF. This is the problem I have with Pipe READER FILE I didn't use EXECIO 'cause I thought it was deprecated or something like that. Stracka, James (GTI) [EMAIL 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 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 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. 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 reader and receive it into a file (or a stem). To my knowledge there are at least two ways to do this. 1) the RECEIVE command (issued from an EXEC) 2) the Pipe READER FILE function both work but not the way I want. From a REXX EXEC, I issue the RECEIVE command. It brings the RDR file in and sticks it in a file called ALL NOTEBOOK even if I specify a file_name, file_type, file_mode. From a PIPE READER FILE function I am able to stick it in the file name, file type that I want but it is not formatted correctly(missing carriage returns and line feeds). I looked at some examples in some IBM manuals, but none touch on how to format it. Bottom line, I want it to be in the format that the RECEIVE command does but I want to give it a unique file name. The name ALL NOTEBOOK or any derivative there of is not an option. Any suggestions? Again, TIA, Steve G. If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. http://www.ml.com/email_terms/
Re: Programmable operator working: my bad; next opportunity
/* 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
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 the prop server with the contents. Tom Duerbusch THD Consulting Steve Gentry [EMAIL PROTECTED] 4/9/2007 12:12 PM I'm trying to get a programmable operator to do something and it isn't working. I've done some reading in the manual and have looked at some existing code but no luck. What I want to accomplish is to send an e-mail to a userid called PROPSCAN ([EMAIL PROTECTED]) The message gets sent to our VM SMTP server with no problem and SMTP then sends it/delivers it/routes it to PROPSCAN's RDR and there it sits. In the RTABLE for PROPSCAN I have it coded such that anything come from SMTP will start an EXEC. The EXEC will then parse that RDR file and I'll take appropriate actions based on key words I'm looking for. Is this doable? If so, what have I missed? Thanks, Steve G.
Re: Programmable operator
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? This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Steve Gentry Sent: Monday, April 09, 2007 1:12 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Programmable operator I'm trying to get a programmable operator to do something and it isn't working. I've done some reading in the manual and have looked at some existing code but no luck. What I want to accomplish is to send an e-mail to a userid called PROPSCAN ([EMAIL PROTECTED]) The message gets sent to our VM SMTP server with no problem and SMTP then sends it/delivers it/routes it to PROPSCAN's RDR and there it sits. In the RTABLE for PROPSCAN I have it coded such that anything come from SMTP will start an EXEC. The EXEC will then parse that RDR file and I'll take appropriate actions based on key words I'm looking for. Is this doable? If so, what have I missed? Thanks, Steve G.
Re: Programmable operator
PROP can react to files hitting its reader queue - you have to code the RTABLE to react as you wish to the messages received when files are delivered. The following is an extract from the RTABLE for one of our PROP-enabled ids: $PRT/FILE$FROM/ 1 35 7 YourExec $PUN/FILE$FROM/ 1 35 7 YourExec $RDR/FILE$FROM/ 1 35 7 YourExec Tom Rae Senior Director, Technical Services Western Canada Loblaw Companies Limited Information Systems Division Notice: This e-mail transmission may contain confidential, proprietary and/or legally privileged information and is intended only for the individual or entity named in the e-mail address. Any disclosure, copying, distribution, or reliance upon the contents of this e-mail not authorized by the sender is strictly prohibited. If you have received this e-mail transmission in error, please immediately reply to the sender, so that proper delivery of the e-mail can be effected, and then please delete the message from your Inbox. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: April 9, 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 (with wakeup rdr specified), and have it process the reader entry and msg the prop server with the contents. Tom Duerbusch THD Consulting Steve Gentry [EMAIL PROTECTED] 4/9/2007 12:12 PM I'm trying to get a programmable operator to do something and it isn't working. I've done some reading in the manual and have looked at some existing code but no luck. What I want to accomplish is to send an e-mail to a userid called PROPSCAN ([EMAIL PROTECTED]) The message gets sent to our VM SMTP server with no problem and SMTP then sends it/delivers it/routes it to PROPSCAN's RDR and there it sits. In the RTABLE for PROPSCAN I have it coded such that anything come from SMTP will start an EXEC. The EXEC will then parse that RDR file and I'll take appropriate actions based on key words I'm looking for. Is this doable? If so, what have I missed? Thanks, Steve G.
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 be able to handle more than 1 file sitting in the reader. This way, when a new file arrives it will handle all files it didn't see yet. For this reason, a server that uses WAKEUP (RDR is better suited. WAKEUP will wake up when new files arrive as well as when old files are waiting in the RDR queue. Have a look at my RxSERVER package on VM's download lib. The stanbard code we deliver will react to RDR files, and will check authority etc. For special handling (i.e. more than simply receiving it on the A-disk) you have to insert some REXX lines at the provided exit points. 2007/4/9, Tom Duerbusch [EMAIL PROTECTED]: 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 the prop server with the contents. Tom Duerbusch THD Consulting Steve Gentry [EMAIL PROTECTED] 4/9/2007 12:12 PM I'm trying to get a programmable operator to do something and it isn't working. I've done some reading in the manual and have looked at some existing code but no luck. What I want to accomplish is to send an e-mail to a userid called PROPSCAN ([EMAIL PROTECTED]) The message gets sent to our VM SMTP server with no problem and SMTP then sends it/delivers it/routes it to PROPSCAN's RDR and there it sits. In the RTABLE for PROPSCAN I have it coded such that anything come from SMTP will start an EXEC. The EXEC will then parse that RDR file and I'll take appropriate actions based on key words I'm looking for. Is this doable? If so, what have I missed? Thanks, Steve G. -- Kris Buelens, IBM Belgium, VM customer support
Re: Programmable operator
Steve, You might consider having PROPSCAN's PROFILE EXEC check for and handle existing RDR files before it starts PROP, otherwise existing RDR files will have to wait for a new file to arrive to trigger the EXEC that handles them all. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Monday, April 09, 2007 2:59 PM To: IBMVM@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 be able to handle more than 1 file sitting in the reader. This way, when a new file arrives it will handle all files it didn't see yet. For this reason, a server that uses WAKEUP (RDR is better suited. WAKEUP will wake up when new files arrive as well as when old files are waiting in the RDR queue. Have a look at my RxSERVER package on VM's download lib. The stanbard code we deliver will react to RDR files, and will check authority etc. For special handling ( i.e. more than simply receiving it on the A-disk) you have to insert some REXX lines at the provided exit points. 2007/4/9, Tom Duerbusch [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] : 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 the prop server with the contents. Tom Duerbusch THD Consulting Steve Gentry [EMAIL PROTECTED] 4/9/2007 12:12 PM I'm trying to get a programmable operator to do something and it isn't working. I've done some reading in the manual and have looked at some existing code but no luck. What I want to accomplish is to send an e-mail to a userid called PROPSCAN ( [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ) The message gets sent to our VM SMTP server with no problem and SMTP then sends it/delivers it/routes it to PROPSCAN's RDR and there it sits. In the RTABLE for PROPSCAN I have it coded such that anything come from SMTP will start an EXEC. The EXEC will then parse that RDR file and I'll take appropriate actions based on key words I'm looking for. Is this doable? If so, what have I missed? Thanks, Steve G. -- Kris Buelens, IBM Belgium, VM customer support
Re: Programmable operator
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 build a hot reader application using WAKEUP. (I think there are prebuilt hot reader apps on the VM Download Library.) Alan Altmark z/VM Development IBM Endicott
Re: Programmable operator
CPCONIO IUCV is turned on. I have also followed everyone elses suggestions and still no go. I have also moved the RDR code to be the first entry in the table (after TEXTSYS and LGLOPER) below is a section of the log . . log 07/04/09 15:33:16 PROP LLIC: PROP running with routing table LLSCAN RTABLE A5 07/04/09 15:34:06 : RDR FILE 0112 SENT FROM SMTP PUN WAS 0511 RECS 0017 CPY 001 A NOHOLD NOKEEP /log Here are the two RTABLE entries I'm trying. rtable /RDR FILE $ FROM SMTP 3 SMTPTEST $RDR/FILE$FROM/1 35 7 SMTPTEST /rtable The following is what I get when I issue a QUERY SET to the PO MSG IUCV, WNG IUCV, EMSG IUCV, ACNT OFF, RUN ON LINEDIT ON , TIMER OFF , ISAM OFF, ECMODE ON ASSIST OFF , PAGEX OFF, AUTOPOLL OFF IMSG IUCV, SMSG IUCV, AFFINITY NONE , NOTRAN OFF VMSAVE OFF, 370E OFF STBYPASS OFF , STMULTI OFF 00/000 MIH OFF , VMCONIO IUCV, CPCONIO IUCV, SVCACCL OFF , CONCEAL OFF MACHINE XA , SVC76 CP, NOPDATA OFF, IOASSIST OFF CCWTRAN ON, 370ACCOM OFF, TIMEBOMB IDLE Command complete Steve G. Alan Altmark [EMAIL 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 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 build a hot reader application using WAKEUP. (I think there are prebuilt hot reader apps on the VM Download Library.) Alan Altmark z/VM Development IBM Endicott
Re: Programmable operator
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): |...+1+2+3+4+5+6+7 $RDR FILE$1 80 ANSWERIT READER The ANSWERIT EXEC then grabs the spool ID from the incoming message and decides what to do with the reader file. Mike Donovan Steve Gentry Stephen_R_Gentry @LafayetteLife.co To mIBMVM@LISTSERV.UARK.EDU Sent by: The IBM cc z/VM Operating SystemSubject [EMAIL PROTECTED] Re: Programmable operator ARK.EDU 04/09/2007 03:45 PM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU CPCONIO IUCV is turned on. I have also followed everyone elses suggestions and still no go. I have also moved the RDR code to be the first entry in the table (after TEXTSYS and LGLOPER) below is a section of the log . . log 07/04/09 15:33:16 PROP LLIC: PROP running with routing table LLSCAN RTABLE A5 07/04/09 15:34:06 : RDR FILE 0112 SENT FROM SMTP PUN WAS 0511 RECS 0017 CPY 001 A NOHOLD NOKEEP /log Here are the two RTABLE entries I'm trying. rtable /RDR FILE $ FROM SMTP 3 SMTPTEST $RDR/FILE$FROM/1 35 7 SMTPTEST /rtable The following is what I get when I issue a QUERY SET to the PO MSG IUCV, WNG IUCV, EMSG IUCV, ACNT OFF, RUN ON LINEDIT ON , TIMER OFF , ISAM OFF, ECMODE ON ASSIST OFF , PAGEX OFF, AUTOPOLL OFF IMSG IUCV, SMSG IUCV, AFFINITY NONE , NOTRAN OFF VMSAVE OFF, 370E OFF STBYPASS OFF , STMULTI OFF 00/000 MIH OFF , VMCONIO IUCV, CPCONIO IUCV, SVCACCL OFF , CONCEAL OFF MACHINE XA , SVC76 CP, NOPDATA OFF, IOASSIST OFF CCWTRAN ON, 370ACCOM OFF, TIMEBOMB IDLE Command complete Steve G. Alan Altmark [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDUIBMVM@LISTSERV.UARK.EDU cc: Subject: 04/09/2007 03:12 PM Re: Programmable operator Please respond to The IBM z/VM Operating System 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 build a hot reader application using WAKEUP. (I think there are prebuilt hot reader apps on the VM Download Library.) Alan Altmark z/VM Development IBM Endicott
Re: Programmable operator
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): |...+1+2+3+4+5+6+7 $RDR FILE$1 80 ANSWERIT READER The ANSWERIT EXEC then grabs the spool ID from the incoming message and decides what to do with the reader file. Mike Donovan You contradict yourself: the last sentence suggests you only handle the last arriving spool file. -- Kris Buelens, IBM Belgium, VM customer support
Re: Programmable operator
Kris, The exec handles any reader file which appears while PROP is running. It does not handle files which are in the reader when PROP starts. Thanks! Mike --- Law of Logical Argument: Anything is possible if you don't know what you are talking about. Kris Buelens [EMAIL PROTECTED] il.comTo Sent by: The IBM IBMVM@LISTSERV.UARK.EDU z/VM Operating cc System [EMAIL PROTECTED] Subject ARK.EDU Re: Programmable operator 04/09/2007 05:36 PM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU 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): |...+1+2+3+4+5+6+7 $RDR FILE$1 80 ANSWERIT READER The ANSWERIT EXEC then grabs the spool ID from the incoming message and decides what to do with the reader file. Mike Donovan You contradict yourself: the last sentence suggests you only handle the last arriving spool file. -- Kris Buelens, IBM Belgium, VM customer support
Re: Programmable Operator: The epic conclusion
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? /snip
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 at 01:10 MST, Don Russell [EMAIL PROTECTED] wrote: Steve Gentry wrote: Hello. We use a Programmable Operator to run certain functions. We send a command to the PropOp using the MSG command. Is there a maximum length the sent MSG can be? If so, can it be changed somewhere? We're having a problem getting some things to work that used to work on VM 4.3 (and I thought was working on 5.2). We're running VM 5.2 on a z9 box. Thanks, Steve G. From help cp msg... 1. If a message is issued from a CMS environment, the command and the message text cannot be longer than 240 characters. But if it used to work on 4.3, then it should continue to work in 5.2. And to answer Steve's question, no, you can't change the 240-character limit on CMS commands. Better is to use e.g. diag(8,'MSG ') to bypass CMS command processing if possible. Alan Altmark z/VM Development IBM Endicott
Re: Programmable Operator
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 some work I am doing where this was a design issue. My only defense is: Chuckie made me do it. ;-) Alan Altmark z/VM Development IBM Endicott
Re: Programmable Operator some additional info
Thanks for the responses to far. We definitely use MSG. I need to elaborate. I have an EXEC that runs on my userid, lets call that user STEVE The PropOp userid is HAL g The EXEC I run on STEVE basically edits what is typed in and if the data typed in meets the req'd criteria, it repackages the input, adds a few pieces (key words) and then does a CP MSG HAL repackaged input. HAL is sitting there waiting for something to come his way. The specific char string will kick off an EXEC based on definitions in the RTABLE. The first thing that EXEC (on HAL) does is to display a message that it is starting (time stamp, etc.) I never see this message. . . . even more detail . . . The command I issue from STEVE to HAL is MSG HAL PUT file name file type and then some more key words for the EXEC on HAL This entire string is never longer than 95 characters. The length can from vary from 80 chars to 95 chars. PUT is the keyword in the RTABLE. 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 get to HAL. As mentioned earlier, this all worked in VM 4.3 but has appeared to quite working in VM 5.2 Thanks, Steve G. Kris Buelens [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 08/03/2006 06:32 AM Please respond to The IBM z/VM Operating System To:IBMVM@LISTSERV.UARK.EDU cc: 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 at 01:10 MST, Don Russell [EMAIL PROTECTED] wrote: Steve Gentry wrote: Hello. We use a Programmable Operator to run certain functions. We send a command to the PropOp using the MSG command. Is there a maximum length the sent MSG can be? If so, can it be changed somewhere? We're having a problem getting some things to work that used to work on VM 4.3 (and I thought was working on 5.2). We're running VM 5.2 on a z9 box. Thanks, Steve G. From help cp msg... 1. If a message is issued from a CMS environment, the command and the message text cannot be longer than 240 characters. But if it used to work on 4.3, then it should continue to work in 5.2. And to answer Steve's question, no, you can't change the 240-character limit on CMS commands. Better is to use e.g. diag(8,'MSG ') to bypass CMS command processing if possible. Alan Altmark z/VM Development IBM Endicott
Re: Programmable Operator some additional info
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: |...+1+2+3+4+5+6+7.. /PUT / 1 4STEVE HALEXEC ___ James Vincent Systems Engineering Consultant Nationwide Services Co., Technology Solutions Mainframe, z/VM and z/Linux Support One Nationwide Plaza 3-20-13 Columbus OH 43215-2220 U.S.A Voice: (614) 249-5547Fax: (614) 677-7681 mailto:[EMAIL PROTECTED] The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 08/03/2006 09:34:24 AM: IBMVM@LISTSERV.UARK.EDU Thanks for the responses to far. We definitely use MSG. I need to elaborate. I have an EXEC that runs on my userid, lets call that user STEVE The PropOp userid is HAL g The EXEC I run on STEVE basically edits what is typed in and if the data typed in meets the req'd criteria, it repackages the input, adds a few pieces (key words) and then does a CP MSG HAL repackaged input. HAL is sitting there waiting for something to come his way. The specific char string will kick off an EXEC based on definitions in the RTABLE. The first thing that EXEC (on HAL) does is to display a message that it is starting (time stamp, etc.) I never see this message. . . . even more detail . . . The command I issue from STEVE to HAL is MSG HAL PUT file name file type and then some more key words for the EXEC on HAL This entire string is never longer than 95 characters. The length can from vary from 80 chars to 95 chars. PUT is the keyword in the RTABLE. 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 get to HAL. As mentioned earlier, this all worked in VM 4.3 but has appeared to quite working in VM 5.2 Thanks, Steve G.
Re: Programmable Operator some additional info
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 get to HAL. As mentioned earlier, this all worked in VM 4.3 but has appeared to quite working in VM 5.2 You can create a default entry in your RTABLE to catch anything that slips through your filters. Just leave all the filters blank. Have that action routine MSG you back (maybe with the data) or log it. That way you'll know what PROP is doing. Make sure you have breadcrumbs in your PUT action routine so you can figure out if it's doing something different (maybe because of the release change). Alan Altmark z/VM Development IBM Endicott
Re: Programmable Operator
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 supports commands send in sections, what measn you can send it commands of any length. this was required as we often send PIPE commands to these servers. The DOME EXEC is what can be used to send commands to the servers and DOME knows how to segment long commands for our servers. Kris, IBM Belgium, VM customer support Hello. We use a Programmable Operator to run certain functions. We send a command to the PropOp using the MSG command. Is there a maximum length the sent MSG can be? If so, can it be changed somewhere? We're having a problem getting some things to work that used to work on VM 4.3 (and I thought was working on 5.2). We're running VM 5.2 on a z9 box. Thanks, Steve G.
