10-20-2016
Also, Linux/GNU versions of grep, sed, awk, etc have extended features which may not be compatible with AIX. If these features aren't used, that's OK.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I wrote a script in ksh93 (the OS is AIX 5.2, ML7), which failed to run. After some testing i found out why, but the answer is a bit dissatisfying. Look for yourself:
#!/bin/ksh93
# --------- Step Names
typeset achStepName="foo"
typeset achStepName="bar"
typeset achStepName="fubar"... (3 Replies)
Discussion started by: bakunin
3 Replies
2. Shell Programming and Scripting
Any means of running ksh93 in a ksh88-mode?
Might sound odd, but I want/need to restrict U/Win-developed scripts to correspond to the ksh88 version on my Solaris environment(s). Thanks. (2 Replies)
Discussion started by: curleb
2 Replies
3. Shell Programming and Scripting
Hi all!
Does anybody know how can I check if any UNIX installation has implemented ksh88 or ksh93?
Thanks in advance.
Néstor. (3 Replies)
Discussion started by: Nestor
3 Replies
4. Shell Programming and Scripting
Hi,
I have a script that calls an external program to perform some calculations and then I read with "grep" and "sed" values from the output files. I've noticed that performance of KSH93 degrades with every iteration. The output files are all the same size, so I don't understand why after the... (2 Replies)
Discussion started by: i.f.schulz
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
Does anyone know where can I get ksh93 for installation on CYGWIN. Thanks? (1 Reply)
Discussion started by: devtakh
1 Replies
6. UNIX for Dummies Questions & Answers
Hi ,
I am working on Linux, with ksh93 installed.
The following statement
echo \\n
just prints
\n on this shell.
However on pdksh
echo \\n gives a blank new line as a output.
What is the correct way of printing a new line character on the ksh93? (4 Replies)
Discussion started by: neeto
4 Replies
7. Shell Programming and Scripting
This problem seems to be specific to ksh93.
If you run with set -x some scripts don't work properly. For example:
$ cat ksh.test2
] && print FUBAR! || print OK!
$
$ /bin/ksh93 ksh.test2
OK!
$ /bin/ksh93 -x ksh.test2
+ ]
+ print FUBAR!
FUBAR!
$
Trying to find out why this is... (8 Replies)
Discussion started by: lthorson
8 Replies
8. UNIX for Advanced & Expert Users
Hello everyone,
I am trying to embed some tcl code inside a ksh93 script but I am not having any success.
I even tried the simplest of code, something like this:
.
.
jk=$(echo $(tcl << |
write_file junkme "test"'
|
))
just to see if a file gets written. When I run there are no errors, but ... (3 Replies)
Discussion started by: gio001
3 Replies
9. Shell Programming and Scripting
My OS is Linux (kernel 4.08.something) and AIX (7100-04-01-1543), the used ksh versions are:
ksh88: Version M-11/16/88f (AIX)
ksh93: Version M 93t+ 2009-05-01 (AIX), Version M 93u (Linux)
When writing a parser for stanza files in ksh i encountered a rather strange behavior. Here is a... (4 Replies)
Discussion started by: bakunin
4 Replies
10. AIX
Hi everyone !
Im trying to know from wich version of AIX KSH93 is available ?
Internet tell me 6.x and 7.x AIX are available, bue what about 5.x ?
Is KSH93 available on AIX 5.x ?
Is it the same way to manipulate variables as KSH93 on 7.x ?
Thanks for your support and have a nice day ! (2 Replies)
Discussion started by: majinfrede
2 Replies
EX(1) General Commands Manual EX(1)
NAME
ex, edit - text editor
SYNOPSIS
ex [ - ] [ -v ] [ -t tag ] [ -r ] [ +command ] [ -l ] name ...
edit [ ex options ]
DESCRIPTION
Ex is the root of a family of editors: edit, ex and vi. Ex is a superset of ed, with the most notable extension being a display editing
facility. Display based editing is the focus of vi.
If you have not used ed, or are a casual user, you will find that the editor edit is convenient for you. It avoids some of the complexi-
ties of ex used mostly by systems programmers and persons very familiar with ed.
If you have a CRT terminal, you may wish to use a display based editor; in this case see vi(1), which is a command which focuses on the
display editing portion of ex.
DOCUMENTATION
The document Edit: A tutorial (USD:14) provides a comprehensive introduction to edit assuming no previous knowledge of computers or the
UNIX system.
The Ex Reference Manual - Version 3.7 (USD:16) is a comprehensive and complete manual for the command mode features of ex, but you cannot
learn to use the editor by reading it. For an introduction to more advanced forms of editing using the command mode of ex see the editing
documents written by Brian Kernighan for the editor ed; the material in the introductory and advanced documents works also with ex.
An Introduction to Display Editing with Vi (USD:15) introduces the display editor vi and provides reference material on vi. In addition,
the Vi Quick Reference card summarizes the commands of vi in a useful, functional way, and is useful with the Introduction.
FILES
/usr/share/misc/exstrings error messages
/usr/libexec/exrecover recover command
/usr/sbin/expreserve preserve command
/etc/termcap describes capabilities of terminals
~/.exrc editor startup file
/tmp/Exnnnnn editor temporary
/tmp/Rxnnnnn named buffer temporary
/usr/preserve preservation directory
SEE ALSO
awk(1), ed(1), grep(1), sed(1), grep(1), vi(1), termcap(5), environ(7)
AUTHOR
Originally written by William Joy
Mark Horton has maintained the editor since version 2.7, adding macros, support for many unusual terminals, and other features such as word
abbreviation mode.
BUGS
The undo command causes all marks to be lost on lines changed and then restored if the marked lines were changed.
Undo never clears the buffer modified condition.
The z command prints a number of logical rather than physical lines. More than a screen full of output may result if long lines are
present.
File input/output errors don't print a name if the command line `-' option is used.
There is no easy way to do a single scan ignoring case.
The editor does not warn if text is placed in named buffers and not used before exiting the editor.
Null characters are discarded in input files, and cannot appear in resultant files.
4th Berkeley Distribution October 21, 1996 EX(1)