Well, ok, from apples to oranges we go ... Last time, you complained about bash (or any shell for that matter) interfering with the content of the message being sent to the VM CP. OK, that's fixable from the user's end. SMSG is a totally different beast. While it indeed is a Class G command, it's also designed to communicate special messages between guests, one that the receiver is programmed to deal with and maybe even reply to. Note the difference between the two on the initiator's end: your terminal will lock up on a CP command until the response + a READY is received; but you'll get back a READY from SMSG immedately. There's a reason for this: one protocol is synchronous, and the other (SMSG) isn't.
That would be my guess as to why you don't see SMSG replies, but I'll betcha its author (Neale?) could jump in here and confirm (or not) that. I don't get responses from "hcp smsg" at my ssh terminal, either. But if I set myself as SECUSER to the Linux guest, I can see all the responses to my SMSGs on the CMS tube as SECUSER traffic. Big help, huh? Sorry, --Jim-- James S. Tison Senior Software Engineer TPF Laboratory / Architecture IBM Corporation "A bird in hand is safer than one overhead."
