Shell Programming and Scripting

Hi ,
I am writing a unix script, calls an PL/SQL block which uses the parameters I passed to the Unix script.

There are 3 sets of parameters I am passing:
set 1 - a or b (only one parameter)
set 2 - 2 2 (two parameters)
set 3 - 2 10000 20000 (three parameters)

Now, my question is I want to use these parameters in my PL/SQL block. Can someone ....?

reddyp,

Are you making calls to an stored procedure or a PL/SQL block that you are constructing on the fly? The following is an example of passing a couple of shell based parameters to a call to a stored procedure:

Given a shell script named test.ksh:

$ cat test.ksh

sqlplus -s username/password@sid << EOF
exec myproc(p_first => $1, p_second => $2, p_third => $3);
/
EOF

$ ./test.ksh 11 22 33

If I didn't understand your question correctly, please elaborate.

Cheers,

Keith

Keith,

My intesion is to run a query on oracle database via., a unix script that can take upto 3 parameters as mentioned below:

$ ./test.ksh a (I am using only one parameter here)
$ ./test.ksh 1 1 (I am using 2 parameters here)
$ ./test.ksh 1 1000 99999 (I am using 3 parameters here)

Now, my requirement is to pass the total number of parameters supplied (i.e., $#) and all different parameters (i.e., $1, $2, $3) from this unix script to the my calling PL/SQL script (it is not a procedure or function) and I want to use these in IF clause of the PL/SQL block.

thanX.

I don't know what PL/SQL is, so I may be off-base here. But I do know how to pass args from one ksh script to another. That turns out to be a rough problem because of this:
/some/script one "two three" four

With ksh, to pass those arguments as 3 arguments, you would use:
/some/other/script "$@"
but read on for another option.

If you used just:
/some/other/script $@
the "two three" would become 2 separate arguments.

And if you tried:
/some/other/script "$*"
you will pass only one argument. This is the difference between $* and $@.

With ksh, unlike the old bourne shell, if there are no argument at all,
/some/other/script "$@"
passes no arguments to the other script. With the bourne shell, you pass a single null argument, sort of like this:
/some/other/script ""

So with the old bourne shell, you had to use the syntax:
/some/other/script ${1+"$@"}
which still works with ksh. I think that syntax is clever and I'm used to it for passing all arguments to a inner command. So this is what I tend to use. Some people don't agree with me that ${1+"$@"} to more clear than "$@". Go figure.