Crispin, >From your description, you're counting on the CMS guest to be able to execute the name resolver, then open a socket to the Linux rexecd host. This all sounds so simple that I wonder if something critical in your VM configuration didn't change when you went to z/VM 4.4. Perhaps the global DIRMAINT user profile changed to omit profile TCPPROF, or similar?
I'd suggest you post this on a VM specialty list somewhere. I am able to run the REXEC client from my CMS guest right to the Linux guest running on the same VM LPAR. I have absolutely no idea what's required to make this work; but I just wanted to let you know that it *does* work on a properly configured z/VM 4.4 LPAR. One very reliable alternative I know of depends on the privilege class of the (ex-)rexec client, or its secondary user status relative to the Linux machine (assuming same VM LPAR). You could use CP SEND <command text here> if your sender has class C privilege. If your sender has class G, it needs to be SECUSER. If the client & server are on different z/VM LPARs, I'm not sure how to handle this. Peace, --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation "If dogs don't go to heaven, then, when I die, I want to go where they do." -- Will Rogers ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
