sorry, I have not much time at the moment to check these things out, but I'm
very interested to see how this turns out.
- do you really think that there was a modification to the VM 370/R6 sixpack
that causes this problem? I hoped (until now) that this is only a problem in the
way that some of the C libraries handle the CMS command line SVC etc.
- I only recall the CMS logic regarding command line tokenizing from very old
times. Is there a problem with the logic that CMS deliveres and that the C
runtime wants? The C runtime, too, wants the arguments of the command line to be
tokenized (blank separated) and distributed to the argv array, where argv[n] is
the n-th argument, argc is the number of arguments (maybe plus 1) and argv is
the program name.
Normal C programs (ANSI C) have no standard method to read the command line "as
a whole", so there is no need to provide such a function in the CMS environment.
Am 20.06.2013 19:03, schrieb D.W.:
> On 20/06/2013 10:41, D. wrote:
> > You cannot use Register 0 as a Base register
> I know others have commented, and I expect most folks understand, but I
> think its worth explaining properley. As the NUCON starts at address 0
> you don't want a base register when you access it. So you specify R0
> which means we use the value "0" and everything works...
> On the subject of command line processing vanilla VM/370 R6 only passes
> a tokenized parameter list. I seem to think Bob modified the sixpack so
> you get an un-tokenized list where available so it may be something in
> this logic is broken.