When transferring the file from the PC using nc (which is an abbreviation for
netcat, I think) and the socket interface (and the VM reader), I get the ^ char
translated to X'5F', and the compiler does not complain any more. The char is
shown as the traditional "Not" character on wc3270. But I don't know how to get
it on my (German) keyboard.
Drawback: the chars that I use for concatenation are translated to the wrong
target characters, but that can easily be fixed using the CMS editor. Now the
program runs without error and gives the desired result.
I now have to find out how the translation of wc3270 can be configured ... for
short corrections. The big edits will be done on the PC, because some PC based
editors (like KEDIT, for example) are much more powerful than the CMS EDIT of
I have a PC based REXX routine, that puts a line like the following in front of
the source code:
USERID BERND CLASS A NAME TESTP3 PLI
:READ TESTP3 PLI A1
and then it does the nc and moves the file to Hercules. VM puts the file in the
virtual reader of the desired CMS user. So it appears there and can simply be
read into the A minidisk using READ *.
Am 20.05.2013 13:59, schrieb Bernd Oppolzer:
> It's X'B0'. Should probably be X'5F'.
> Can I change it to X'5F', using the CMS editor, by specifying some sort
> of change command?
> Or, using another tool available in CMS with VM Rel 6?
> Thank you, kind regards
> Am 20.05.2013 13:15, schrieb D.W.:
>> If you are using a TN3270 client like WC3270 then it controls the
>> ASCII conversion. Check the code page in WC3270.
>> You can use the
>> "TYPE fn ft fm (hex"
>> command to display a cms file in hex...
>> On 20 May 2013 11:55, Bernd Oppolzer <email@example.com> wrote:
>>> I have the same problem. I am using the VM sixpack release and also PL/1 (F).
>>> When entering a ^= condition using the ^ sign, the compiler complains.
>>> I'm using the wc3270 client and I entered the source code using CMS EDIT.
>>> I will now try to examine the hex code which is inserted into the source
>>> file for ^.
>>> Another way to transfer sources to Hercules (which I use) is through the
>>> VM virtual reader and the socket interface. I will try this, too.
>>> My Hercules Version is 3.07.
>>> Kind regards