Well , *MSGALL to *MSG helped: testmail * From SMTP: Received Spool File 0042 00000001SMTP * From SMTP: Mail delivered to: <[email protected]> Ready; T=0.03/0.03 10:38:44
Not sure, yet, how the 1st message is being received. Frank M. Ramaekers Jr. > -----Original Message----- > From: CMSTSO Pipelines Discussion List [mailto:CMS- > [email protected]] On Behalf Of Larson, John E. > Sent: Friday, September 21, 2012 10:29 AM > To: [email protected] > Subject: Re: [CMS-PIPELINES] Help with STARMSG > > Any chance that the mail server is using CP WARNING instead of CP MSG? > If so you would need to "CP SET WNG IUCV". > > Also, I'm not sure about your use of *MSGALL > > 5. You cannot connect to "*MSGALL" when CMS FULLSCREEN is ON because > CMS is > already connected to the service; CP rejects further attempts to connect. > > And: > > *MSG specifies that you want to connect to the message service. > *MSGALL specifies that you want to connect to the message all service. > > Isn't MSGALL a special form of CP MSG that sends a CP MSG to all active and > disconnected users on the system?? > > The more I think about it, it is definitely *MSGALL that is the problem, the > email server isn't using CP MSGALL. > It would just be using CP MSG. > > So, STARMSG *MSG > Or since it defaults, just STARMSG with no operands. > > > -----Original Message----- > From: CMSTSO Pipelines Discussion List [mailto:CMS- > [email protected]] On Behalf Of Frank M. Ramaekers > Sent: Friday, September 21, 2012 7:59 AM > To: [email protected] > Subject: Re: Help with STARMSG > > Thanks, but it still misses it and never exits: > > testmail > * From SMTP: Received Spool File 0038 > > TESTMAIL EXEC: > /* */ > Trace "O" > MailTo="[email protected]" > > "PIPE (endchar ?)", > "| LITERAL QUERY SET", > "| CP", > "| SPLIT AT /,/", > "| STRIP", > "| FIND MSG_"||, > "| SPEC W2-*", > "| VAR SETMSG" > "PIPE LITERAL SET MSG IUCV | CP | HOLE" > "EXEC MAILIT TO("MailTo")", > "FROMNAME(TMK z10 VM System EREP)", > "LOG", > "TITLE(Test EMail)", > "TEXT(Body of Email)", > > "PIPE (endchar ?)", > "| STARMSG *MSGALL", > "| CONSOLE", > "? LITERAL +15", > "| DELAY", > "| PIPESTOP" > "PIPE LITERAL SET MSG" SetMsg "| CP | HOLE" > > > Frank M. Ramaekers Jr. > > > > -----Original Message----- > > From: CMSTSO Pipelines Discussion List [mailto:CMS- > > [email protected]] On Behalf Of Larson, John E. > > Sent: Friday, September 21, 2012 9:41 AM > > To: [email protected] > > Subject: Re: [CMS-PIPELINES] Help with STARMSG > > > > From the first page of the help: > > > > STARMSG > > > > .-*MSG----. > > > >>--STARMSG--+---------+--.---------------.----------------------------- > ---->< > > '-service-' '-commandstring-' > > > > Purpose > > > > Use the STARMSG stage to write lines from a CP message service. > > STARMSG uses > > Inter-User Communication Vehicle (IUCV) to connect to a message > service > > (such > > as *ACCOUNT, *ASYNCMD, *LOGREC, *MSG, *MSGALL, or *SYMPTOM). > > A STARMSG stage > > can be used only as the first stage of a pipeline. > > > > Note: Before issuing STARMSG, you must use the IUCV directory > control > > statement to authorize yourself to connect to a CP message > service. > > For > > more information about the IUCV statement, see the z/VM: > CP > > Planning > > and Administration book. YOU MUST ALSO ISSUE THE CP > COMMAND > > SET MSG > > IUCV TO ENSURE MESSAGES WILL BE PASSED TO THE VIRTUAL > > MACHINE THROUGH > > IUCV IF A CONNECTION TO THE MESSAGE SYSTEM SERVICE EXISTS. > For > > more > > information about the SET MSG IUCV command, see the z/VM: > CP > > Commands > > and Utilities Reference book. > > > > The 2nd sentence in the "Note:" is your first concern. > > You must "CP SET MSG IUCV" before using STARMSG. > > > > That should at least get you to the next series of issues/questions:-) > > > > John > > > > > > -----Original Message----- > > From: CMSTSO Pipelines Discussion List [mailto:CMS- > > [email protected]] On Behalf Of Frank M. Ramaekers > > Sent: Friday, September 21, 2012 7:33 AM > > To: [email protected] > > Subject: Help with STARMSG > > > > I need a little help in coding a PIPELINE using STARMSG, not having > much > > experience with this stage. What I have is an EXEC that sends email > > (via MAILIT EXEC). I now wish to capture the messages sent back from > the > > SMTP server to log. For instance: > > > > > > > > * From SMTP: Received Spool File 0028 > > > > > > * From SMTP: Mail delivered to: <[email protected]> > > > > * From SMTP: Mail delivered to: <[email protected]> > > > > * From SMTP: Unable to deliver mail to: <[email protected]> > > > > > > > > I tried, as a test: > > > > > > > > "PIPE (endchar ?)", > > > > "| STARMSG *MSGALL", > > > > "| CONSOLE", > > > > "? LITERAL +15", > > > > "| DELAY", > > > > "| PIPESTOP" > > > > > > > > But never received a response (echoed by the CONSOLE stage), instead I > still > > received the MSG (as above). > > > > > > > > Frank M. Ramaekers Jr. | Systems Programmer | Information Technology | > > American Income Life Insurance Company | 254-761-6649 > > > > > > > > > > _____________________________________________________ > > > > This message contains information which is privileged and confidential > and is > > solely for the use of the > > > > intended recipient. If you are not the intended recipient, be aware > that any > > review, disclosure, > > > > copying, distribution, or use of the contents of this message is > strictly > > prohibited. If you have > > > > received this in error, please destroy it immediately and notify us at > > [email protected]. > > _____________________________________________________ > > This message contains information which is privileged and confidential and is > solely for the use of the > > intended recipient. If you are not the intended recipient, be aware that any > review, disclosure, > > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > > received this in error, please destroy it immediately and notify us at > [email protected]. _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at [email protected].
