🚀 go-pugleaf

Hi Jody,

The basic things you need to know to get started is the following:

Parse the command line parameters:

$# = number of parameters passed to your program
$1 = parameter 1
$2 = parameter 3
etc...

You may have to surround variables and parameters in double quotes
if they contain more than one word.

Use the redirection symbol ">" to redirect the standard output from a
process to a new file.
Use the append symbol ">>" to append the standard output from a process
to an existing file.  (It will be created if it doesn't exist.)

That should help you get started...

Jin

In article <3A2E6922.61778861@siliconmetrics.com>,
  Jody Zung <jzung.zung@siliconmetrics.com> wrote:
> Hi folks. I'm new to writing shell scripts in unix so maybe someone
> could help me out here.
> I'm lookin to run some automated test cases. What I need to do is run
a
> process and output the results. Actually there is more I need to do
but
> I need to walk before I can run.
>
> So basically it'll look like this.
>
> I have a process called OMC that I run on a file. There are options as
> well, so a command from the unix prompt would look like this:
>
> omc  -dtmlckf -o <output dir> <filename.lib>
>
> Then the thing runs for a while and ouputs a huge amount of stuff.
> After this I want to check the output directory for the correct files.
>
> So i'll cd to the output directory, do an ls, or ll and visually check
> for the needed files.
>
> Is there a way i can do all of this in a script and output to a
results
> file??
>
> thanks in advance.
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.