Instead of WAKEUP, a Pipe using the starmsg driver would also work. If I am only waiting for 1 thing and the process has to be synchronous, I usually use a structure like:
'CP SET SMSG IUCV' 'PIPE (end ? NAME SMsg)', '? starmsg *msg cp xautolog userB #EXEC Y', <if this is the is the correct message then end the program>, '| cons' The stages implied by the <...> would presumably end with a pipestop stage when the expected message is received.. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Kern > Sent: Thursday, December 04, 2008 4:03 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Starting an exec on a remote machine > > I can think of two mechanisms off-hand. > > 1) after X xautologs user B with command EXEC Y, it loops > checking for user B being logged on. Once user B is no longer > logged on, exec X can continue. > > 2) after X xautologs user B..., it waits for an SMSG from > user B using the WAKEUP program. The EXEC Y needs to send X > and SMSG just before logging indicating a > successful/unsuccessful completion. > > /Tom Kern > > Howard Rifkind wrote: > > I'm running exec X on cms user 'A' > > > > I exec X has to start exec Y running on cms user 'B' and > after exec Y > > terminates it has to return control to the exec on cms user 'A' > > > > I could use some suggestions as to the best way to do this. > > > > Thanks >
