Yes indeed: in execs CP's line editing characters it should not be interpreted but remain part of the command string. And, this should be straigthforward: XEDIT interprets it always (terminal or execs), CP only on terminal input.
So on a terminal, CP commands should be interpreted. Confusion started -in my eyes- with XAUTOLOG (but I guess CP SET PF was acting like this since ages). An interesting case is CP commands from an XEDIT session: many people think that entering #CP Q T in XEDIT's command line goes directly to CP, just like #CP in linemode. False: it seems to work, but only as long as XEDIT's linend is set to #. It is XEDIT that splits it's command string in 2 pieces: an empty command and CP Q T. The same is true for any fullscreen application, like VM:OPER or even "Fullscreen CMS": it is the the fullscreen application that must pass the command to CP (or CMS), and for CP this is then not a command coming from a terminal. Another command with confusion is CP SEND: the operands you enter become linemode terminal input for the target machine, so that string is at execution time interpreted with the TERM settings of the target machine. But, care must be taken at the sending side too, at least when entered on a terminal.... Now you should be ready to consult the online help and explain the difference between 'CP SEND CP userid Q T' and 'CP SEND userid CP Q T', or even '#CP SEND userid "#CP Q T' (the first will always work, the send often not, the last one always if the TERM defaults are active) 2007/5/8, Ian S. Worthington <[EMAIL PROTECTED]>:
Kris -- The problem is, if I understand it correctly, that the "#", (or in my case the ";") *is* being issued from an exec and the ";" is being interpreted as the linend character. ian ...
-- Kris Buelens, IBM Belgium, VM customer support
