Where do shell scripts live?

What directory should shell scripts be kept in?
There are lots of tutorials explaining how to write shell scripts but now that I'm writing and using them I don't know where they should be saved. Where can a beginner find out these things?

What directory should shell scripts be kept in?
One convention is to put your personal shell scripts in
$HOME/bin
and add *$HOME/bin* to your PATH environment variable via your $HOME/.bash_profile
export PATH="$PATH:$HOME/bin"
The convention for scripts that are intended for all users on the system are put into
/usr/local/bin
and of course the users would need to put that into PATH vi their $HOME/.bash_profile
export PATH="$PATH:/usr/local/bin"
These are just conventions and not hard and fast rules.

Similar Messages

How to use "do shell script" when Terminal replies with a prompt?

Hey all,
I'm wondering how to properly use "do shell script" when Terminal replies with a question? In this example, I'm building a small tool in AppleScript that will auto-update the Android SDK via command line prompts. The problem is when I tell it to update all ("update sdk --no-ui"), I need to accept licence agreements before it continues, and the amount of licence agreements brought up is different every time.
So, basically, I'm wondering how to handle a case where "do shell script" encounters a case where Terminal would normally need a user's response to?
Thanks,
Behn

If it is variable number of prompts that is a problem. Look around hd and figure out how many prompts there will be. Ask around android forum for a bash solution. There are some test case apps that will let you put conditionals on output from running programs.
# traditional way. Pipe output to command.
do script "echo 'ok' | update sdk --no-u"
Here is the preferred way of getting administrator privileges.
It is easier to diagnose problems with debug information. I suggest adding log statements to your script to see what is going on. Here is an example.
    Author: rccharles
    For testing, run in the Script Editor.
      1) Click on the Event Log tab to see the output from the log statement
      2) Click on Run
    For running shell commands see:
    http://developer.apple.com/mac/library/technotes/tn2002/tn2065.html
on run
    -- Write a message into the event log.
    log " --- Starting on " & ((current date) as string) & " --- "
    -- debug lines
    set unixDesktopPath to POSIX path of "/System/Library/User Template/"
    log "unixDesktopPath = " & unixDesktopPath
    set quotedUnixDesktopPath to quoted form of unixDesktopPath
    log "quoted form is " & quotedUnixDesktopPath
    try
        set fromUnix to do shell script "sudo ls -l " & quotedUnixDesktopPath with administrator privileges
        display dialog "ls -l of " & quotedUnixDesktopPath & return & fromUnix
    on error errMsg
        log "ls -l error..." & errMsg
    end try
end run

Shell Scripts for installation / migration of an object

Hi All,
We are on Oracle Applications R12 and we are settling down with it. Our database and app servers are on Linux. To migrate objects from one instance to another or to install objects, we use two different approaches. One is to move objects manually using the installation instructions (MD120) and another to use Shell script. Now we need to choose any of these two approaches. But we are not able to decide. Appreciate if you can help me answering following questions. This will help us greatly in finalizing the process. I am for Shell Script. But if I get proper arguments / reasons, I am not against it.
1. Who should be responsible for moving or migrating objects? Is it DBAs? If not, who? At our place, DBAs are performing this task.
2. Our DBAs have argument that if they move it using script, there will be a big control issue over what is moving in to database / app server. (Our DBA does not have any prior experience of managing Oracle Applications instance. He used to be a Oracle DBA for Peoplesoft)
3. If we have some side by side comparison or link to that, that will be perfect.
4. If someone has a case study and / or the industry best practices document on it, please share it with me. My email id is [email protected]
Earlier I have worked only in consulting companies where only Shell script was the standard and best practice. This is my first end user company.
Appreciate help and thank you in advance.
CAH

Hi,
1. Who should be responsible for moving or migrating objects? Is it DBAs? If not, who? At our place, DBAs are performing this task.The DBA.
2. Our DBAs have argument that if they move it using script, there will be a big control issue over what is moving in to database / app server. (Our DBA does not have any prior experience of managing Oracle Applications instance. He used to be a Oracle DBA for Peoplesoft)Both approach would work. Personally, I prefer the script approach and the DBA can review the code before running any script.
3. If we have some side by side comparison or link to that, that will be perfect. I do not think such a link exist.
Thanks,
Hussein

Executing shell script using OSLinetoken fetchlet

Hii,
I do have a requirement. I need to use a shell script in the OSLineToken fetchlet. In response metric i will be checking whether the directory exists or not on the server. In order to check the existence of the directory, i have created a shell script. But how can i relate its result with the Response metric? The shell script is as follows:
Shell Script:
if test -d $1 ; then
echo "DIR exist"
else
echo "false"
fi
The Response metric for the same will be:
<QueryDescriptor FETCHLET_ID="OSLineToken">
     <Property NAME="command" SCOPE="GLOBAL">
          sh {dir_name where the shell script is uploaded}/{shell script file name} {dir_name_parameter} </Property>
     <Property NAME="startsWith" SCOPE="GLOBAL">em_result=</Property>
     <Property NAME="delimiter" SCOPE="GLOBAL">|</Property>
</QueryDescriptor>
Please suggest what is the use of em_result here?
once the existence of the directory is checked, if it up then i need to call another shell script in order concatenate the contents of all the files with extension .log(this will be the parameter of shell script). Get the output from shell script and display it into custom management plug-in. As i am using cat *.log>>consolidatefile command to concatenate the data, i need to read consolidatefile file from the server and return this concatenated file data into plug-in. Again, how can i read the content of consolidatefile file in EMF? I will be creating another matric for this purpose say "read_content". the querydesciptor of the same will be as follows:
<QueryDescriptor FETCHLET_ID="OSLineToken">
     <Property NAME="command" SCOPE="GLOBAL">
          sh {dir_name where the shell script is uploaded}/{shell script file name} {dir_name_parameter} {extension of the files to concatenated} </Property>
     <Property NAME="startsWith" SCOPE="GLOBAL">em_result=</Property>
     <Property NAME="delimiter" SCOPE="GLOBAL">|</Property>
</QueryDescriptor>
I am not sure which all properties to be used in this case..I have seen multiple sample files some of them uses perbin, scriptsdir but some of them does not..The related pdf also does not say anyhting about such kind of properties. Please suggest.
I hope the explaination of the problem is not so cumbersome. Please let me know if you have any query to understand.
Thanks,
AS

If you notice, localScriptsDir is a directory within scriptsDir. If you package your plug-in up and deploy it through the UI, any scripts you create will go into %scriptsDir%/emx/<target_type>. So localScriptsDir just specifies that directory for you. You don't need it but then in the command paramater you'll have something like:
sh %scriptsDir%/emx/yourtargettype/yourscript...
So whether you specify it in the command or another property (localScriptsDir) doesn't really matter.
You can create your own properties in the QueryDescriptor. Just make sure you have the correct scope specified and it should be fine (options for scope are described in the Enterprise Manager DTD section of the Extensibility Guide).
Metric collection isn't really meant for dynamic specification of input parameters. I can think of a few solutions:
1) Create a target instance for each log directory. When you create the instance, the directory is specified. If you need to monitor a different directory, you can just create another instance. Upside is that it's flexible and scalable, and also, when you get an error you'll know exactly which directory it is based on which instance throws the error. Downside is that you have to have a separate instance for each directory.
2) If the log directories are well known and finite (and won't change names), hardcode them into the target metadata. Have a different metric collect for each log directory, so you'll have as many metrics as log directories you want to monitor. Even if the names of the directories are different, you can use instance properties to map them, so if you know there will always be 5 log directories you want to monitor, you can have 5 instance properties to map the names into the metrics, although this won't work if you don't have the same number each time. Upside is that there is only a single target instance. Downside is that it's not as flexible.
3) Use a job rather than a target type to find out this information. You could create a new job type which scans the logs for information and have the directory as an input parameter to the job. You could have this job on a repeating schedule to duplicate the effect you are trying to get out of creating a target type. The upside is that you can start the job whenever you want from the UI and specify exactly which directory whenever you run it. The downside is that the job system is centered on the OMS rather than the agent, so every time it runs it will have to contact the agent to do the work. In the case of the target type, the agent acts autonomously without contact from the OMS.
There are probably other options, but these are the quick ones off the top of my head.
Chris

Power Shell Script for Check Remote machinces are live or not

I have required a Power Shell Script for Check multiple Remote machines are live or not.Please guide me

This will do it.
http://gallery.technet.microsoft.com/Ping-IP-Adress-Range-d90ce82d
¯\_(ツ)_/¯

Where is the Shell Script directory?

I have been asked to run a script in the Shell Script directory.
I found the directory /library/scripts ... when I ran the script in there I did not get the expected results, so I assume the directory is incorrect.
Please help..

AFAIK, that folder's for AppleScripts, not shell scripts. For shell scripting, see https://developer.apple.com/library/mac/#documentation/OpenSource/Conceptual/She llScripting/Introduction/Introduction.html

From Where i can help or manual about writing shell script in oracle

can any one help me to write shell script in oracle.

not sure what you meant by shell script in oracle. If ou want to write a shellscript that interacts with an oracle database, you ma want to refer to an unix programming book and sqlplus manual.
Rgds
Arvind Balaraman

Running a shell script in a Cocoa-Applescript, from the Resources folder?

Hello!
I need to use a bash script, but the script must be IN the application. I placed them in the "Supporting files", but i am not able to find them using "do shell script"
Thanks!

If you stick the script in the Resources folder you can get it by
path to resource "Bash Script"
If you want to put it in the folder Supporting files you need to construct the path
(path to me as string) & "Contents:Resources:Supporting files:Bash Script"
(where Bash Script is the name of your script)
Don;t know if there is a shorter way for the second case.

Do shell script problem in Applescript

Hi,
I am an Applescript novice and have been trying to write a code to go to a particular folder, look for all files in the folder tree with extension .m2v and run an executable file to decode them. My problem is that when I run my code (containing do shell script), it searches through all files and folders on Mac HD and starts decoding .m2v files elsewhere that I don't want.
Eventually it runs out of space (.m2v file decoding takes a lot of space), because it is dumping all decoded .yuv files onto the HD.
When I run the command on Terminal, it executes the decoding perfectly and stores the decoded files in the same folder.
Please help me about what's going on.
My code is something like:
tell application "Finder"
set DestinationFolder to "xxxxxx:xxxx:xxxx"
set NumFolders to (get count of folders under Destination folder)
repeat for SomeVar from 1 to NumFolders
set FolderinQuestion to folder SomeVar of DestinationFolder
-- Tried tell application "Terminal" here, but did not know --how to export the FolderinQuestion variable from Finder to --Terminal
do shell script " \" cd \" & (POSIX path of (result as text));
for file in `find $pwd \"*.mov\"`
do
/usr/local/bin/decode file
done"
end repeat
end tell
I would greatly appreciate some guidance.

The root of the problem is that you're trying to quote the cd command for some reason:
<pre class=command>do shell script " \" cd \" & (POSIX path of (result as text));
...</pre>
In addition to that you're including the & (POSIX path of (result as text)) as part of the shell command whereas this should be OUTSIDE of the quotes in order to get evaluated
If you work that through you'll end up with a shell command that looks like:
<pre class=command>" cd " & (POSIX path of (result as text))</pre>
If you try to run that in a terminal you'll get a cd : command not found error and that's why the rest of it appears to fail.
The solution to that one is simple - just don't bother quoting the cd and put the POSIX path stuff outside of the quotes to get it evaluated at runtime:
<pre class=command>do shell script "cd " & quoted form of POSIX path of (FolderInQuestion as text)) & ";
# rest of shell commands here"</pre>
Now, as for the rest of the script there are a few things I would change.
First, unless you need to know the index, don't do:
>repeat for SomeVar from 1 to NumFolders
set FolderinQuestion to folder SomeVar of DestinationFolder
the issue is that the number of folders to process may change during the script's execution (other processes may create or remove folders). This will, at best, cause some folders to be skipped and, at worst, cause the script to fail.
If you're iterating through a list, the best option is to just:
<pre class=command>repeat with FolderInQuestion in (folders of DestinationFolder)
...</pre>
This automatically sets the iterator (in this case, FolderInQuestion, to the first item in the list and increments it for each iteration through the loop.
Secondly, in your shell script itself, scrub the entire do/done loop. You're already using find, so have that do the hard work using the -exec switch:
<pre class=command>find path -name "*.mov" -exec /usr/local/bin/decode {} \;</pre>
In find's case, {} is substituted with the current file's path.
Putting this together you'd get:
<pre class=command>tell application "Finder"
set DestinationFolder to "xxxxxx:xxxx:xxxx"
repeat with folderInQuestion in (get folders of folder DestinationFolder)
do shell script "cd " & quoted form of POSIX path of folderInQuestion & "; find . -name \"*.mov\" -exec /usr/bin/decode {} \\;"
end repeat
end tell</pre>
Note that I've used 'quoted form of POSIX path' - this takes care of any shell-unsafe characters like spaces in the path name. I've also used \\; for the -exec switch - this is so that AppleScript passes the \ to the shell command rather than using it for its own escaping.
But you're not done yet!
There's still one fatal flaw in this process - and that is the fact that find by default, is recursive - it will walk through every directory that it finds.
This means that if you start at the top folder and iterate through, find will find all .mov files and decode them. Your script then cd's to the first subdirectory and repeats the process - decoding all the .mov files in that directory and all its subdirectories even though they've ALREADY been decoded.
The upshot is that you only need to run one loop starting at the top level. You don't need to iterate through all the subdirectories since find will do that for you.
In addition to that, there might not be a need to use cd at all since the first argument to find is the directory to start searching in. Unless there's some reason that you need to start decode from the top level directory (e.g. is that where it saves the files?), you can drop the whole repeat loop altogether and just run with:
<pre class=command>set startFolder to (choose folder)
do shell script "find " & quoted form of posix path of startFolder & " -name \"*.mov\" -exec /usr/bin/decode {} \\;"</pre>
That's the entire script - a radical compression of your original.

Problem with backtick replacing apostroph in applescript/shell script

I've got a script that appears to be using a backtick instead of an apostrophe which is causing an error in my shell script. For the life of me I can't seem to find where the error is being generated?
The script is attached below. I'm using Exiftool, an app that writes metadata to image files. The shell script
set cmd to "exiftool -CopyrightNotice=" & exifCopyright & " " & thisFilePath & ""
set theResult to do shell script cmd
works fine but the following shell script
set cmd to "exiftool" & space & authorStr & " " & thisFilePath & ""
set theResult to do shell script cmd
returns the error "sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file" number 2. The code in the event log in applescript editor looks exactly the same to me but one fails in the shell script.
It has been suggested by the developer of Exiftool, Phil Harvey, that there is a backtick in the second shell script. I read somewhere in the applescript docs that this is due to a change in OS 10.6? Any suggestions on how to fix this?
Thanks.
Pedro

Yea, the authorStr value has a space like "Joe Smith"
Then you need to use quoted form of this string, too:
set cmd to "exiftool " & quoted form of authorStr & space & thisFilePath
although the format looks wrong to me - shouldn't there be some kind of switch, such as "-author=' before it?
You have to consider how you'd enter this at the command line to work out how best to translate it to AppleScript. For example, if the command line version were:
exiftool -author='John Doe' /path/to/some.jpg
you can see the quotes are around the name, not the entire -author switch. In this case you should be looking at something like:
set authorStr to "John Doe"
set theFilePath to "/path/to/some.jpg"
set theCmd to "exiftool -author=" & quoted form of authorStr & space & quoted form of theFilePath
Now you could, of course, use quoted form when you create the variables (e.g. set authorStr to quoted form of "John Doe"), but that may screw you up later on if/when you try to use authorStr in some other way, so I find it best to use quoted form only where it's needed.

Executing if condition in a sql prompt with in a shell script

Hi all,
i need to write a shell script where i need to execute a sql statement. if the count from the above sql is greater than certain value i need to execute a another sql statement.After some time i need to check the count again using above sql and if the count is less than certain value i need to execute a different sql statement. One more time i need to check the count and then i need to get an email.
Could anyone help me in completing this script
Thanks,

Could anyone help me in completing this scriptNot really because "shell script" is OS & Shell dependent & you decided to NOT share these details with us.
Just write a PL/SQL procedure & then you have an OS independent solution!

Problem-Report generation using shell script

Hi
We have the Production database and the Reporting database (copy of Production database),
both on Oracle 9.2.0.5 and Solaris 5.8. There is a package inside the Oracle database, which extracts some data from inside the
database, and would generate a report. A shell script has been created in Solaris which would
send in the parameters and call the pakage to generate the report. The parameters it is sending is
the name of report to be generated, and the location where it is to be generated, both hard-coded into
the script. The script is scheduled to run through crontab.
The problem we are facing is that, if we run the script for Reporting database, it successfully
generates the report. But if we use that script for Production database, it gives the error
"Invalid directory Path". I have tried using various other directory paths, even '/tmp'
and '/', but it still gives the same error when executed for Production dataabse.
Could somebody provide any ideas what might be going wrong.
The reasons it is to be executed on Prod db and not the Reporting database are unavoidable.
It anyway runs in off business hours and takes about 10secs to execute.
Please do let me know if there is any other info that I missed to provide here.
Thanks in advance...

I will be just guessing because you didn't provide contents of script and package.
The "Invalid directory path" as you said could be ORA-29280 due non existent directory.
Try execute (as sys or system) select * from dba_directories; (or select * from all_directories; as user which the script is login to) on both databases and compare the results. If there is missing your important directory then create it using create directory <dirname>; (from sqlplus and don't forget to grant rights for user).
This error could come from shell script. In that case you should find resolution yourself because you didn't provide script source.

Calling a report from unix shell script

Hi,
I had to call a report from unix shell script.
May i know the procedure to accomplish this
Thanks in Advance
A.Gopal

First you should not include the whole path to your report in the call ...
Use like this:
/ora/u01/oracle/v101/as2/bin/rwrun.sh report=an_stati destype=file desname=/ora/u01/oracle/v101/as2/test.pdf desformat=pdf
In $ORACLE_HOME/bin/reports.sh:
1) Verify that you have updated the REPORTS_PATH variable to include your folder where you have the report in question
REPORTS_PATH=/ora/u20/app/qits/env1/run:$ORACLE_HOME/reports/templates:$ORACLE_HOME/reports/samples/demo: ....
2) Verify that the REPORTS_TMP variable is pointing to a valid location and that the oracle user has access to write on it.
After that, post the content of the tracefile located at $ORACLE_HOME/reports/logs/{in-process report server name folder}/rwserver.trc
If no file is present then it means that you need to enable trace in your reports's conf file.... go to the $ORACLE_HOME/reports/conf folder and and locate the .conf file that correspond to your in-process reports server name (as specified in the rwservelet.properties file)... open/edit the file to enable trace logs ..
i.e.
Change the following line:

to <trace traceOpts="trace_all"/>
Bounce the reports server and try to run the report again, this time the .trc file should be generated, post the content so that we can take a look.

How can i pass parameter values from html to a shell script

Hi Guys...
I had a requirement where i need to execute a sql statement and print the output in HTML page. This report has parameters to enter. So i created a HTML form which accepts parameters. When the submit button is pressed, the action tag in the form invokes unix shell script file. It will open sqlplus and run the sql script file .sql and print the output in the HTML page.
sql script contains the query and some set options which prints the output in HTML page. Like "SET MARKUP HTML ON"... The query has some parameters like "select * from emp where empno = &&empnumber. I will use the same name "empnumber" while created the HTML parameter form like " <input type = "text" name="empnumber" size="10" align="left">.
user sees this parameter form and enters some value in to that empno text box.
My question is how can i catch these parameter values in a shell script and pass it to the sql script to execute it.
Help Appreciated
Thanx

This is a A Bad Idea (tm). This type of CGI processing is old and were (and still is) full of security holes. Very easy to inject stuff (Unix commands and SQL) into it.. To get those parameters into SQL*Plus requires using Unix shell commands to process it - and something like a backquote allows all kinds of nasty stuff to be injected. The Unix shell was never designed to be used as a secure CGI environment.
There are far better and far superior alternatives. Perl (with Perl_DBI) and PHP (using Zend Core for Oracle) come to mind as web scripting languages.
Even easier is using HTMLDB. Very few moving parts. Is free. Supports Oracle 9.2 and 10G.

How Can i get PLSQL Procedure out values in Shell Script?

Hi,
I need to use PLSQL Procedure out values in shell script by using that parameter i need to check and call the other procedure. Please can you guide me how can i?
#!/bin/ksh
# Function to call validation program
SQL_PKG_CALL()
echo "Inside SQL_PKG_CALL for $file"
sqlplus -s /nolog << EOF
     whenever sqlerror exit failure
     connect ${APPS_LOGIN}
     variable exit_value NUMBER
     set serveroutput on size 100000
     DECLARE
          l_errbuf VARCHAR2(10000) := NULL; l_retcode NUMBER := NULL;lv_test VARCHAR2(4000) := NULL;
     BEGIN
          fnd_global.apps_initialize ( USER_ID => ${USER_ID}, RESP_ID => ${RESP_ID}, RESP_APPL_ID => ${RESP_APPL_ID}
                         , SECURITY_GROUP_ID => ${SECURITY_GROUP_ID}
          #Calling PLSQL procedure for create and attache document
          XXAFPEEP_SO_DOC_ATTACH_INT.DOCUMENT_ATTACH (p_errbuf => l_errbuf, p_retcode => :RETMSG, p_fileName => $file
                                   , p_debug => 'Y', p_rettest => lv_test);
          # to print the procedure return values
          DBMS_OUT.PUT_LINE('Return Message: '|| lv_test);
          #${RETCODE}=l_retcode;
          print :RETMSG;
     END;
EXIT 0
EOF
# Program starts here
echo "+---------------------------------------------------------------------------+"
echo "Program Start"
APPS_LOGIN=${1} # Apps Login
USER_ID=${2} # User ID
RESP_ID=${5} # Responsiblity ID
RESP_APPL_ID=${6} # Responsiblity Application ID
SECURITY_GROUP_ID=${7} # Security Group ID
DIRECTORY_PATH=${8} # Directory --Attached file locations
DIRECTORY_NAME=${9} # Directory Name for plsql
echo "User ID : $USER_ID"
echo "Responsibility ID : $RESP_ID"
echo "Responsibilith Application ID : $RESP_APPL_ID"
echo "Security Goup ID : $SECURITY_GROUP_ID"
echo "Directory Path : $DIRECTORY_PATH"
echo "Direcotry Name : $DIRECTORY_NAME"
echo
#files direcotry
cd $DIRECTORY_PATH
echo Present Working Directory: `pwd`
echo
#for all file names
ALL_FILES=`ls *.pdf`
for file in $ALL_FILES
do
     if [ -f $file ]
     then
          #log "Processing $file" # future
          echo Processing: $file
          # Calling the PL/SQL Program
          SQL_PKG_CALL;
          #echo "Retcode : $RETCODE"
          echo "RetMessage : $RETMSG"
     else
          log "Skipped $file: invalid file"
          echo "Skipping current file $file: not a valid file."
     fi
done
Thanks
Sudheer

Saubhik's provided the solution, but just for fun:
Test procedure:
create or replace procedure get_ename
   ( p_empno in emp.empno%type
   , p_ename_out out emp.ename%type )
is
begin
   select ename into p_ename_out
   from   emp
   where empno = p_empno;
end get_ename;Test data:
SQL> select empno, ename from emp order by 1;
EMPNO ENAME
7369 SMITH
7499 ALLEN
7521 WARD
7566 JONES
7654 MARTIN
7698 BLAKE
7782 CLARK
7788 SCOTT
7839 KING
7844 TURNER
7876 ADAMS
7900 JAMES
7902 FORD
7934 MILLER
14 rows selectedTest call from SQL*Plus to show it working:
SQL> declare
2     v_ename emp.ename%type;
3 begin
4     get_ename(7844,v_ename);
5     dbms_output.put_line(v_ename);
6 end;
7 /
TURNER
PL/SQL procedure successfully completed.Demo shellscript (borrowing the function idea from Saubhik):
#!/bin/ksh
empno=${1:-NULL}
exec_sql() {
    sqlplus -s william/w@//vm.starbase.local:1521/eleven <<END_SQL
    spool get_out_value.sh.log
    set serverout on size 2000 feedback off
    declare
       v_name emp.ename%type;
    begin
       get_ename(${empno},v_name);
       dbms_output.put_line('# ' || v_name);
    end;
    spool off
    exit
END_SQL
ename=$(exec_sql ${empno} | awk '/^# / {print $2}')
print Employee ${empno} = ${ename}Demo:
/Users/williamr: get_out_value.sh 7844
Employee 7844 = TURNER
/Users/williamr: get_out_value.sh
Employee NULL =Note this substitutes the word NULL if no empno is passed, and it ignores error output or anything else by only looking for lines beginning '# ' and then taking the following word. Error messages will appear in the logfile. (In this example it probably doesn't need the NULL substitution because a missing parameter would cause a syntax error which the script will handle anyway, but it could be useful in more complex examples.)
For a production script you should probably use an OS authenticated account so you don't have to deal with password strings.

Where do shell scripts live?

Similar Messages

Maybe you are looking for