RE: QShell GOTCHA

It has to do with the file system your in.

QOpenSys is case sensitive
The root "/" is not.

Two different file systems, two different behaviors.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James
H. H. Lampert
Sent: Friday, December 01, 2017 1:34 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: QShell GOTCHA

On 12/1/17, 11:01 AM, Nathan Andelin wrote:

Unix convention. Case matters. Not that I think it was a good idea.

It gets weirder.

On my Mac (remember, Mac OS X is a fork of BSD), "echo" and "ECHO" both work
like QShell "ECHO"; i.e., they don't resolve escapes (or at least, they
don't resolve an "\r" escape). "echo" has a man entry, but "ECHO"
does not.

On our Debian box, "echo" works like QShell "ECHO," and "ECHO" doesn't work
at all.

Clearly somebody thought it was a good idea to have an "echo" that resolves
escapes, and an "ECHO" that doesn't, in QShell. Not quite sure why, beyond
sheer perversity and/or "cussedness."

I'm also a bit irritated that, given that keyboards lacking a caps lock key
have become quite rare, SEU still defaults to uppercase-only for OPM CL.
That was probably a contributing factor in my having been caught by this
"gotcha."

--
JHHL