Hi,
I need to check for value not equal (<>) to 21 and not equal empty or null values.
Please modify this script
if
then
echo "$VALUE,$BSC_NAME,$BSC_ID" > $OUT_FILE/power_up.out
end if
TQ (5 Replies)
Hello All,
I have written shell script whcih at the max 3 parameters.
When only one commandline argument and other two command line arguments are passed as empty string like
eg : archive ' ' ' '
Then i need to check whether the commandline... (12 Replies)
Hi Masters.....
I have problem !!!
I need to check number of records in a file and if it is zero or file is empty i need to do some task.
if ; then
echo "File s empty"
else
echo "Not empty"
fi
so how to check this condition.
I used wc -l < filename.txt => 1 for zero records
same result... (1 Reply)
I have the list of users in user.log, under each user folder there is sub1 folder is there. i want to check whether sub1 is empty or not, if it is empty i have to skip that user user folder and iterate next user folders. i have the sample code,its not giving not proper results.
while read line... (8 Replies)
I need to check if a directory is empty using an if condition
in the pseudocode below
if ; then
else
although i looked at a few forums on this topic, I left feeling a little unclear and i could not use the command successfully
what can i substitute in the if conditon above,... (2 Replies)
hi,
i want to check whether a a variable contains some value or is empty in a shell script. so if the variable contains some value i want to do some job and if the variable doesnt contain any value then i need to skip that job.
here is a sample script
read_filenames.sh contains
... (5 Replies)
Hi gurus ,
I have two files and i want to perform different action based on the condition if both or either is empty
If
then
Do something
elif
then
do something
elif
then
do something
else
do something
fi
I have tried the below bt its not... (4 Replies)
Hello
So i have that script collection, in which i have a single script to create a configuration file.
In there, i have multiple occourences of something like this:
prj_title=$(tui-read "What is the TITLE? ($prj_name):")
] && prj_title="${prj_name/_/ }"
They all work as expected, if... (5 Replies)
Discussion started by: sea
5 Replies
LEARN ABOUT OSF1
jobs
jobs(1) General Commands Manual jobs(1)NAME
jobs - Displays status of jobs in the current session
SYNOPSIS
jobs [-l | -p] job_id...
[Tru64 UNIX] jobs [-n] job_id...
Note
The C shell has a built-in version of the jobs command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/jobs. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
jobs: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Provides more information about each job listed. This information includes the job number, current job, process group ID, state and the
command that formed the job. Displays only the process IDs for the process group leaders of the selected jobs. [Tru64 UNIX] Displays
jobs that have stopped or exited since last notified.
By default, the jobs utility displays the status of all stopped jobs, running background jobs and all jobs whose status has changed and has
not been reported by the shell.
OPERANDS
Specifies the jobs for which the status is to be displayed. If no job_id operand is given, the status information for all jobs is dis-
played. The format of job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
The jobs utility displays the status of jobs that were started in the current shell environment.
When jobs reports the termination status of a job, the shell removes its process ID from the list of those "known in the current shell exe-
cution environment". See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
The jobs utility does not work as expected when it is operating in its own utility execution environment because that environment has no
applicable jobs to manipulate.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of jobs: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error and informative messages written to standard output.
Determines the location of message catalogues for the processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), fg(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)jobs(1)