12-29-2005
check the status and send an email with status
Hi,
We have a text file which has the following data.
ISA~00~ ~00~ ~ZZ~VISTN ~ZZ~U1CAD ~051227~183
7~U~00200~000011258~0~P~<
GS~FA~EE05J~U1CAD~051227~1831~000011258~X~002002
ST~997~0001
AK1~SH~247
AK2~856~2470001
AK5~A
AK2~856~2470002
AK5~A
AK9~A~2~2~2
SE~8~0001
GE~1~000011258
IEA~00001~000011258
ISA~00~ ~00~ ~ZZ~F159B ~ZZ~U1CAD ~051227~191
3~U~00200~000011467~0~P~<
GS~FA~AF52M~U1CAD~051227~1913~000011467~X~002002
ST~997~0001
AK1~SH~53
AK2~856~530001
AK5~A
AK9~A~1~1~1
SE~6~0001
The data I am looking for is in the first line that starts with ISA and the third column data is “~ZZ~F159B” and “~ZZ~VISTN”.
On the basis of the above mentioned segments, I have to assign them status either as pass or fail, which has been accomplished by the code snippet provided by Vgersh99 and Rancha.
grep "~ZZ~" <data file> | nawk '{ print ($3=="~ZZ~VISTN") ? "passed":"failed" }'
Now the new requirement is that I have to send an email, which should have the status in the body of the email. Can this be achieved in one script or I have to write two scripts like one has the static body of the email and it just expects two arguments.
Template for static email:
Please be advised that the EDI ASN has been “status” (either passed or failed).
Hope this is not too confusing.
Regards,
Inder
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I believe i have most of samba configured right but i get this error each time time try to run it. I was given suggestion that i touch the file, i did, but i still cannot rid myself of this error.
Any suggestions (2 Replies)
Discussion started by: macdonto
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I have a datafile which has the following data and it can have much more records. The data set is as follows:
ISA~00~ ~00~ ~ZZ~F159B ~ZZ~U1CAD ~051215~184
3~U~00200~000011432~0~P~<
GS~FA~TC11A~U1CAD~051215~1843~000011432~X~002002
ST~997~0001... (6 Replies)
Discussion started by: isingh786
6 Replies
3. Red Hat
I have successfully installed RedHat 8.0 onto a Dell PowerEdge SC1425 today. This server has two SATA hard drives, and an IDE DVD-ROM drive.
Using the following kernel parameters, i successfully installed across both hard drives from CD:
ide0=0x1f0,0x3f6,14 vga=791 resolution=1024x768 expert... (5 Replies)
Discussion started by: fishsponge
5 Replies
4. UNIX for Dummies Questions & Answers
rshstatus=`rsh -n lilo /db/p2/oracle/names9208/restart_names.sh`
if $rshstatus <>0 then
errstatus=1
mailx -s "xirsol8dr" ordba@xxx.com >> $log_dr
else if errstatus=0
echo "status to xirsol8dr successful"
can anyone provide if this is t he correct way to do this or is there a better way? (1 Reply)
Discussion started by: bpm12
1 Replies
5. Shell Programming and Scripting
I have written a bash script to to sort the data from logs i need some help in printing the outputs , i dont have much ideas in bah scripting.
Sample script
-----------------------
#!/bin/bash
a=`date | cut -d " " -f2,2,3`
cat /var/log/maillog |grep "$a" |grep -E -e 'deferred|bounced'... (9 Replies)
Discussion started by: unimaxlin
9 Replies
6. Shell Programming and Scripting
I have some server ( IBM , Dell ) , our data center is not in the same location with office , therefore , I do not know if the HD lamp is flash when the HD is fault , can advise if I can write a script to check if the HD is normal running or not ?
thanks (1 Reply)
Discussion started by: ust
1 Replies
7. Shell Programming and Scripting
Hi,
I have few processes in the server continuous run few jobs, each of the process will generate a log file which detailing when its jobs are completed.
the logfile will has the name something like this, result1.log, result2.log, result3.log,.... result10.log, result11.log, result12.log.......... (8 Replies)
Discussion started by: khchong
8 Replies
8. Shell Programming and Scripting
autorep -m bogus
Machine Name Max Load Current Load Factor O/S Status
___________ ________ ___________ ______ ________ ______
bogus --- --- 1.00 Sys Agent Online
Status
______
Online
Offline
Missing
Unqualified
The "Status" always "Online". I like create a script execute run... (6 Replies)
Discussion started by: dotran
6 Replies
9. Shell Programming and Scripting
Hi Guys,
Is there any way I can write a script that sends DISK SPACE USAGE STATUS via email once a week?
Thanks, (5 Replies)
Discussion started by: g4v1n
5 Replies
10. Programming
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies
LEARN ABOUT XFREE86
systemd-notify
SYSTEMD-NOTIFY(1) systemd-notify SYSTEMD-NOTIFY(1)
NAME
systemd-notify - Notify service manager about start-up completion and other daemon status changes
SYNOPSIS
systemd-notify [OPTIONS...] [VARIABLE=VALUE...]
DESCRIPTION
systemd-notify may be called by daemon scripts to notify the init system about status changes. It can be used to send arbitrary
information, encoded in an environment-block-like list of strings. Most importantly, it can be used for start-up completion notification.
This is mostly just a wrapper around sd_notify() and makes this functionality available to shell scripts. For details see sd_notify(3).
The command line may carry a list of environment variables to send as part of the status update.
Note that systemd will refuse reception of status updates from this command unless NotifyAccess= is set for the service unit this command
is called from.
Note that sd_notify() notifications may be attributed to units correctly only if either the sending process is still around at the time PID
1 processes the message, or if the sending process is explicitly runtime-tracked by the service manager. The latter is the case if the
service manager originally forked off the process, i.e. on all processes that match NotifyAccess=main or NotifyAccess=exec. Conversely, if
an auxiliary process of the unit sends an sd_notify() message and immediately exits, the service manager might not be able to properly
attribute the message to the unit, and thus will ignore it, even if NotifyAccess=all is set for it.
systemd-notify will first attempt to invoke sd_notify() pretending to have the PID of the invoking process. This will only succeed when
invoked with sufficient privileges. On failure, it will then fall back to invoking it under its own PID. This behaviour is useful in order
that when the tool is invoked from a shell script the shell process -- and not the systemd-notify process -- appears as sender of the
message, which in turn is helpful if the shell process is the main process of a service, due to the limitations of NotifyAccess=all
described above.
OPTIONS
The following options are understood:
--ready
Inform the init system about service start-up completion. This is equivalent to systemd-notify READY=1. For details about the semantics
of this option see sd_notify(3).
--pid=
Inform the init system about the main PID of the daemon. Takes a PID as argument. If the argument is omitted, the PID of the process
that invoked systemd-notify is used. This is equivalent to systemd-notify MAINPID=$PID. For details about the semantics of this option
see sd_notify(3).
--uid=USER
Set the user ID to send the notification from. Takes a UNIX user name or numeric UID. When specified the notification message will be
sent with the specified UID as sender, in place of the user the command was invoked as. This option requires sufficient privileges in
order to be able manipulate the user identity of the process.
--status=
Send a free-form status string for the daemon to the init systemd. This option takes the status string as argument. This is equivalent
to systemd-notify STATUS=.... For details about the semantics of this option see sd_notify(3).
--booted
Returns 0 if the system was booted up with systemd, non-zero otherwise. If this option is passed, no message is sent. This option is
hence unrelated to the other options. For details about the semantics of this option, see sd_booted(3). An alternate way to check for
this state is to call systemctl(1) with the is-system-running command. It will return "offline" if the system was not booted with
systemd.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
EXAMPLE
Example 1. Start-up Notification and Status Updates
A simple shell daemon that sends start-up notifications after having set up its communication channel. During runtime it sends further
status updates to the init system:
#!/bin/bash
mkfifo /tmp/waldo
systemd-notify --ready --status="Waiting for data..."
while : ; do
read a < /tmp/waldo
systemd-notify --status="Processing $a"
# Do something with $a ...
systemd-notify --status="Waiting for data..."
done
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), sd_notify(3), sd_booted(3)
systemd 237 SYSTEMD-NOTIFY(1)