In my experience, you've got to *always* drive 'CP MSG' from the Diag() function or DiagRC() function in REXX, or some equivalent. Going through normal CMS command processing performs an up-case on the command so that CMS can remain case insensitive.
On Mon, May 19, 2008 at 7:37 AM, Shimon Lebowitz <[EMAIL PROTECTED]> wrote: > Hi, > I was under the impression that a CP message/smsg could > be mixed case, as long as it was sent directly from an EXEC > or other program (and not from the command line which would > uppercase all the console input). > > 1) Is this in fact true? (documented?) > > 2) IF it's true, what could be causing my messages/smsgs > to be arriving in all uppercase? > > This is a serious problem, because I have a server virtual machine > to which I need to periodically send a bit of *non-printable-character* > data. I ran this data through a 64ENCODE pipe stage before SMSGing > it, with the server using 64DECODE on the received data. > Unfortunately, with the SMSG arriving uppercased, my data > gets klobbered. > I checked this with MSG to a spooled console and also see > arriving data in uppercase, even though the message was > sent from an exec with: > "CP MSG <target>" variable_with_mixedcase_text > > What have I missed? > > Thanks! > Shimon > > -- > ************************************************************************ > Shimon Lebowitz mailto:[EMAIL PROTECTED] > VM System Programmer . > Israel Police National HQ. > Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 > ************************************************************************ > -- -- R; <><
