I once wasted several days trying to get two machines running pipes to send a simple message via TCPIP back and forth. According to the article I had read (perhaps by Rob? I don't really remember) it was supposed to be a piece of cake, but I never got it to work, and had to move on to other things.
I already saw the starmsg response you got, but if anyone has a working sample of a TCPIP pipe, I would love to see it. My need was to set up a server that would accept a one line class D spool query command and the name of a requestor, such as "LAUREL Q R HARDY ALL" and *if the requestor (LAUREL) was in a list of authorized users*, perform the query and send back the CP response lines. This was for semi-admins, to whom I did NOT want to give class D. Thanks for any ideas, and Richard, I hope you don't mind my hitching a ride on your thread, but you say you are good to go now, and the subject fit. :-) Shimon ---- Original message ---- >Date: Thu, 26 Feb 2009 12:57:39 -0800 >From: "Schuh, Richard" <[email protected]> >Subject: [CMS-PIPELINES] Handling of Messages >To: [email protected] > >I have a need for two machines on different VM systems to be able to >periodically exchange messages. These two systems have two connections- >RSCS TCPNJE and ISFC. I thought that the simplest might be passing >messages via RSCS and Pipelines. I have been having a bit of a problem >in my trials that is illustrated below: > >pipe (end \) starsys *msg cp set msg iucv | take 1 | pipestop | cons >RSCS From VMLX1(VTADMIN): HELLO >FPLSMG346E No message found (id 1321502363) >FPLMSG003I ... Issued from stage 1 of pipeline 1 >FPLMSG001I ... Running "starsys *msg cp SET MSG IUCV" > >The first line is a pipe whose only function is to receive one message >and display it on the console. Line 2 is the message received and >displayed. It is the other 3 lines hat are the problem. I have tried >various combinations and settings. The ones that produce the message all >get the error messages. The others do not display the message, >apparently because they do not receive it. > >The message was produced by the command "#cp smsg rscs msg node userid >hello" . Neither machine has RSCS command privileges. > >Regards, >Richard Schuh
