PROBLEM:	(UVO104297)	(Patch ID: OSF415-400118)
********
This patch fixes a problem that occurs when using the Korn shell (ksh).

Keyboard input is not echoed when a user exits via a trap, after editor
options have been set in ksh.

To restore the tty modes, enter the following command:
    <newline> stty sane <newline>

To reproduce the problem execute the following:
    /usr/bin/ksh
    set -o emacs
    touch /tmp/foo
    trap 'rm -f /tmp/foo' EXIT
    TMOUT=1

Now wait 60 seconds.  When ksh exits, the keyboard should echo characters.
If it does not, then this bug has occurred.

PROBLEM:        (QAR 50297)     (Patch ID: OSF415-400169)
********
The ksh shell program prevents a command, which runs in a sub-process, from
writing to a tape device.

For example:

$ /usr/bin/ksh -c "/bin/echo foo | /bin/cat > /dev/rmt0h"
/usr/bin/ksh: /dev/rmt0h: cannot create

PROBLEM:  	(QAR 51086)	(Patch ID: OSF415-410057)
********
Set  old-obreak = 0 breaks ksh will be fixed by this patch.

PROBLEM:  (QAR  26933)		 (Patch ID: OSF415-400270)
********
This patch fixes a problem in which the ksh command periodically prints
erroneous characters instead of the command that was typed.

The only identifiable effects are loss of logging information and the loss
of access to the command from the command line edit.

PROBLEM:  (QAR 52892  QAR 49928)	 (Patch ID: OSF415-400304)
********
This patch fixes a problem in which the ksh shell sometimes reverses the group
id (GID) and the effective group id (egid) of the calling process.

For example if the calling process (starter) spawns ksh to execute the
"/usr/bin/id" command, the output would be:

$ ./starter xx
uid=4294967200(vsctest) gid=15(users) egid=4(bin) groups=0(system)
uid=4294967200(vsctest) gid=4(bin) egid=15(users) groups=0(system)
$
### Note that the gid and egid have been interchanged

PROBLEM:  (CLD HGOQ50006, QAR 52992) (Patch ID: OSF415-400326)
********
This patch fixes problems that occur when using the ksh shell. When the PATH
for a command is not found, the following error message is displayed.  Also,
when the set command is executed, the system core dumps.

     /bin/ksh: invalid multibyte character

PROBLEM:  (USG-05628)		 (Patch ID: OSF415-400435)
*********
This patch fixes a problem that occurs when using the Korn shell (ksh).
Variables set with the typeset -L[n] built-in command do not work correctly
when other subshells are spawned. For example:

Example: < Incorrect results >
$ /usr/bin/ksh
$ typeset -xL3 var=hello
$ typeset | grep var
export 3 leftjust 3 var
$ echo $var
hel
$ /usr/bin/ksh
$ typeset -xL3 var=hello
$ typeset | grep var
export 3 leftjust 3 var
$ echo $var

$
Example: < Correct results >
$ /usr/bin/ksh
$ typeset -xL3 var=hello
$ typeset | grep var
export 3 leftjust 3 var
$ echo $var
hel
$ /usr/bin/ksh
$ typeset -xL3 var=hello
$ typeset | grep var
export 3 leftjust 3 var
$ echo $var
hel
$

PROBLEM:  (QAR 45801,QAR 61048,EVT102530)    (Patch ID: OSF415-405301)
********
This patch fixes a problem that was caused by the Korn shell running in EMACS
mode.  When a window was resized  with a width that exceeded 160 characters,
the next command (or even a return) would cause the ksh utility to core dump.

PROBLEM:  (BCPM40XKX, 53066)    (Patch ID: OSF415-405331)
********
This patch fixes a problem in the kornshell in which the "lt" operator didn't
work correctly when the first expression was more than ten digits.

PROBLEM:  (CLD MGO103483)    (Patch ID: OSF415-405343)
********
This patch fixes a problem when builtin variables (ex. TMOUT) are exported
as readonly with values > 256. The 'set' command (display all variables) will
cause ksh to core dump with the error "stack overflow".

PROBLEM:  (QAR 41085)    (Patch ID: OSF415-400193)
********
Fixes a problem in which the :q history substitution modifier in csh may
result in a syntax error.

PROBLEM:  (QAR 41087)    (Patch ID: OSF415-400193)
********
Fixes a problem in which the :x history substitution modifier in csh may
result in a syntax error.

PROBLEM:  (QAR 41746)    (Patch ID: OSF415-400193)
********
Fixes a problem in which receipt of a SIGALRM signal by a child process of
csh does not result in csh reporting the death of the child process with
the message 'Alarm clock'. Instead the system displays the following
message:

        auto-logout

PROBLEM:  (QAR 42250)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh erroneously jumps to the middle of an embedded
if-then statement. This occurs upon reaching the end of a while loop, when
the loop is entered manually, rather than executed from a script.

PROBLEM:  (QAR 43026, QAR 45613, QAR 47089, QAR 47146, HPXQC14BV, HPXQC15ND)
********  (Patch ID: OSF415-400193)
Fixes a problem in which an error in a file sourced by csh results in a
logout of the csh process.

PROBLEM:  (QAR 44539)    (Patch ID: OSF415-400193)
********
Fixes a problem in which the default value for prompt2 in csh is ">" instead
of "?".

PROBLEM:  (QAR 46802)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh can core dump when expanding a large "*" pattern.

PROBLEM:  (QAR 45059)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh fails to do file name substitution on the result
of a command substitution.

PROBLEM:  (QAR 46160, QAR 47019, TKTQB1363) (Patch ID: OSF415-400193)
********
Fixes a problem in which csh expands metacharacters (for example, "*") even
when they are inside quoted strings. This problem can cause the grep, sed,
and find commands to fail when "*" appears inside a quoted regular expression
argument.

PROBLEM:  (QAR 45632)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh does not expand tilde ("~") in a path name that
also contains a backquoted expression ("`...`").

PROBLEM:  (QAR 47453)    (Patch ID: OSF415-400193)
********
Fixes a problem in which the autologout feature of csh is by default enabled
for pseudo ttys (for example, during an rlogin session).

With this patch, autologout is enabled by default if csh runs as a login
shell and if the standard input stream is not a pseudo tty and the DISPLAY
environment variable is not set.  Autologout under these conditions can be
disabled by adding the following line to your .login or .cshrc file:

                set autologout = 0

If autologout is set to a value greater than 0 (zero), csh terminates if a
command is not entered within the prescribed number of minutes after issuing
the csh prompt. You can find out whether the autologout feature is enabled
for the session by checking the value of $autologout.

PROBLEM:  (QAR 48250)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh can core dump while using the history facility
when edit mode is set to emacs.

PROBLEM:  (QAR 46161)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh does not read the .cshrc and .login files in
the user's home directory if they are not owned by the user and in the same
group as the user.

PROBLEM:  (QAR 44298)    (Patch ID: OSF415-400193)
********
Fixes a problem in which csh prints a misleading message ("No match") when a
command line contains characters such as "*" or "?" and the user does not
have read access to the current directory. With this patch, csh will print
the more more descriptive message "Glob aborted - Permission denied".

PROBLEM:  (QAR 26082)    (Patch ID: OSF415-400193)
********
Fixes a problem in which a csh loop that runs background processes exits
when too many processes have been created. With this patch, csh works like
ksh in that it waits for process creation to succeed.

PROBLEM:  (ZUO101309)            (Patch ID: OSF415-400434)
********
This patch fixes a problem that occurs when using the C shell (csh).  When a
command that does both wildcard expansion and command substitution is run in
csh, incorrect results are produced.  For example:

$ /usr/bin/csh
$ ls *.c `ls *.h`
*.c not found
a.h b.h
example: <Correct results>
$ /usr/bin/csh
$ ls *.c `ls *.h`
a.c  a.h  b.c  b.h

PROBLEM:  (CLD TKTQ20082) (Patch ID: OSF415-405159)
********
The data byte 0x80 is a valid second byte of a 2-byte character in the SJIS
and BIG-5 character sets. However, this data byte also has special meaning
within the C shell (csh). This leads, in some cases, to incorrect processing
of multibyte characters that contain 0x80 as the second byte.

For instance, under the ja_JP.SJIS locale, the following echo command produces
the wrong result:

        % echo `printf "\217\200"` | od -xc
        0000000     0a8f
                       \n
        0000002

This patch prevents the 0x80 data byte from being omitted.  Using the new csh
command included in the patch, the echo command returns the correct result:

        % echo `printf "\217\200"` | od -xc
        0000000     808f    000a
                    **  \n
        0000003

Also by using the new csh, users can print out a single 0x80 character using
the echo command.  However, quoting is necessary to prevent unwanted removal
of the 0x80 character.  For example:

        % echo "`printf '\200'`" | od -xc
        0000000     0a80
                       \n
        0000002
        % echo `printf '\200'` | od -xc
        0000000     000a
                  \n
        0000001

PROBLEM:  (UVO105992)    (Patch ID: OSF415-405365)
********
This patch corrects a problem which results in a superuser being able to
inadvertently bring the system down to single user mode by accidentally
killing pid 1 (init) when trying to kill a background job (%1).

PROBLEM:  (CLDs HPAQ50F5M HPAQ21LTJ QAR 53389)  (Patch ID: OSF415-405389)
********
File globbing in ksh sometimes does not list all the files in the
directory.

PROBLEM:  (CLDs  DMO100352 QAR 57030)    (Patch ID: OSF415-405389)
********
This patch fixes a memory managment problem that occurs on systems running
the Korn shell.  Incorrect results occur when the length of the parameter to
the echo command is altered.

PROBLEM: (QAR 56531 QAR 56516 QAR 56530 QAR 56529) (Patch ID: OSF415-400437)
********
Commands vquota, vedquota, quota, edquota, dump, csh, and nslookup will
sometimes display the incorrect error message for non-english locales.