Basically, I want to copy all files (F03*) in this directory and merge/paste them into a new file (called SMER_2.03.12.SPU), yet the error message is "no such file or directory." I listed what is in my working directory, and the files do exist, so I'm not sure what's going on. The code's at the bottom.*
Thanks, Ellen
Moderator's Comments:
Please use code tags next time for your code and data.
I am trying to build a tuxedo server which in turn depends on several Pro*C programs. I am doing it on HP-UX system.
It looks to me that the ORACLE_HOME is set properly.
But I am getting error message when trying to build.
PCC-F-NOERRFILE, unable to open error message file, facility PR2
exit... (1 Reply)
Hi all,
i have a log file that captures success or failure messges when i run a daily job.
here is a sample of my log.
20060312 start
successful
successful
failure
failure
20060312 end
i need to write a subroutine that opens up the log daily after my job completes to examine the log... (2 Replies)
I am using the "find" command below and it respond with the error message " find: cannot open /: Stale NFS file handle"
what does it mean?
what can I do about it?
Need advice, thanks.
below are the command that I enter, the respond and the error message:
root@ScripServer:/# find / -name... (1 Reply)
hi
i am using the below code
grep -v '^$' file1.lst >file1.lst
but it gives file1.lst already exists.
And i want to over rite on the same file
Whats the work around? (5 Replies)
Hi,
I was compiling few C programs in the unix server and getting the following error message
rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent
proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE
INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE ... (1 Reply)
I get this message when I write myshell.c program "VM pagefault:SIGSEGV bad add 0x0 err 0x4 nopage read myshell PM: ciredump signal 11 for 1725 /myshell memory fault (core dumped)"
/* RCS information: $Id: myshell.c,v 1.2 2006/04/05 22:46:33 elm Exp $ */
#include <stdio.h>
#include <unistd.h>... (1 Reply)
Hi
#Testing for file existence
if ; then
echo 'SCHOOL data is available for processing'
else
echo 'SCHOOL DATA IS NOT AVAILABLE FOR PROCESSING'
:
i wrote a script, where it begins by checking if file exists or not.
If it exists, it truncates the database... (2 Replies)
Hello all, I have a question about creating a script that will look for messages on one of our MQ series systems, and fix them.
Currently, if we issue a command for example
Command.sh errors
it gives us:
ID:c3e2d840d4f3f3d74040404040404040cb2ef4e62f70f702 <?xml version="1.0"... (3 Replies)
Hi All,
Would like to ask on how to refrain the message file not exists from display out.
if ; then
When it execute, the OS will throw the error file does not exists
ls: 0653-341 The file COL_*/*.CTL does not exist.
Thanks. (3 Replies)
Hi All,
I have created a unix script to mail the xls file.This is being done using mailx command
fdate=`tail -1 abc.xls | cut -c1-8`
SUBJECT="CARD GL Exceptions : ${ENV} for ${fdate}"
destname=CARD_GL_Exceptions_$fdate
sed 's/#BUSINESS/BUSINESS/1' abc.xls > abc2.xls
mv abc2.xls abc.xls... (2 Replies)
Discussion started by: karthik adiga
2 Replies
LEARN ABOUT OSF1
install
install(1) General Commands Manual install(1)NAME
install - Installs a command
SYNOPSIS
install [-sS] [-c targetdir] [-g group] [-m mode] [-u owner] file [searchdir...]
install [-osS] [-f targetdir] [-g group] [-m mode] [-u owner] file [searchdir...]
install [-g group] [-iosS] [-m mode] [-n targetdir] [-u owner] file [searchdir...]
install [-g group] [-MosS] [-m mode] [-u owner] file [searchdir...]
The install command installs file in a specific place within a file system. It is most often used in makefiles.
OPTIONS
Installs file in targetdir only if there is not already a copy there. If there is a copy of file in targetdir, the command issues a mes-
sage to that effect and exits without overwriting the file. This option can be used alone or with the -g, -m, -s, -S, or -u options.
Forces installation of file in targetdir even if a copy already exists there. If there is already a copy of file in targetdir, the command
sets the new copy's mode and owner to those of the old copy. If there is not already a copy of file in targetdir, the command sets the
mode to 755 and the owner to bin. This option can be used alone or with the -g, -m, -o, -s, -S, or -u options. Specifies a group other
than bin for the destination file. Ignores the default directory search list. Searches for the file to be installed only in the directo-
ries specified on the command line (searchdir ...). This option cannot be used with the -c, -f, or -M options. Moves file to targetdir
instead of copying it. This option cannot be used with the -c, -f, -i, or -n options. Specifies a mode other than 755 for the destination
file. Installs file in targetdir if there is no copy in any of the searched directories (searchdir ...). Sets the mode of the file to 755
and the owner to bin. This option cannot be used with the -c, -f, or -M options. Saves the old copy of file by renaming it OLDfile and
leaving it in the directory where it was found. This option cannot be used with the -c option. Specifies an owner other than bin for the
destination file. Suppresses the display of all but error messages. Causes the binary to be stripped after installation; see strip(1).
DESCRIPTION
The install command copies (or moves) file into the appropriate directory, retaining the owner and permissions of the existing copy, if
any. A newly created file has permission code 755, owner bin, and group bin. The install command writes a message telling you which files
it is replacing or creating and where they are going.
If you supply no options or search directories (searchdir ...), the install command searches the /bin, /usr/bin, /etc, /lib, and /usr/lib
directories in that order for a file with the same name as file. The command overwrites the first matching file with file and issues a
message indicating that it has done so. If no match is found, the command tells you and exits without taking further action.
If any search directories (searchdir ...) are specified on the command line, the install command searches them before it searches the
default directories.
EXAMPLES
To replace a command that already exists in one of the default directories, enter: install fixit
This replaces the file fixit if it is found in the /bin, /usr/bin, /etc, /lib, or /usr/lib directory. Otherwise, the file fixit is
not installed. For example, if /usr/bin/fixit exists, then this file is replaced by a copy of the file fixit in the current direc-
tory. To replace a command that already exists in a specified or default directory while preserving the old version, enter: install
-o fixit /etc /usr/games
This replaces the file fixit if it is found in the /etc or /usr/games directory, or in one of the default directories. Otherwise,
the file fixit is not installed. If the file is replaced, the old version is preserved by renaming it OLDfixit in the directory in
which it was found. To replace a command that already exists in a specified directory, enter: install -i fixit /u/judith/bin
/u/bernice/bin /usr/games
This replaces the file fixit if it is found in the /u/judith/bin, /u/bernice/bin, or /usr/games directory. Otherwise, the file is
not installed. To replace a command found in a default directory, or install it in a specified directory if it is not found, enter:
install -n /usr/bin fixit
This replaces the file fixit if it is found in one of the default directories. If the file is not found, it is installed as
/usr/bin/fixit. To install a new command, enter: install -c /usr/bin fixit
This creates a new command by installing a copy of the fixit file as /usr/bin/fixit, but only if this file does not already exist.
To install a command in a specified directory whether or not it already exists, enter: install -f /usr/bin -o -s fixit
This forces the fixit file to be installed as /usr/bin/fixit whether or not /usr/bin/fixit already exists. The old version, if any,
is preserved by renaming it to /usr/bin/OLDfixit (a result of the -o option). The messages that tell where the new command was
installed are suppressed (a result of the -s option).
SEE ALSO
Commands: chgrp(1), chmod(1), chown(1), cp(1), installbsd(1), make(1), mv(1), strip(1)install(1)