07-03-2013
Parameter file with changing date
Hi,
I have a trigger file which looks like this abcdefgh_YYYYMMDD.trg The YYYYMMDD is the year, month and the date. So for example today the trigger file would be abcdefgh_20130703.trg similarly tomorrow it would be abcdefgh_20130704.trg
I need to write a script to check if the trigger file exists. If the trigger file does not exists then I have to send a mail stating that Trigger file does not exist and the load cannot start. If the trigger file exists then the rest of the workflow (I am using Informatica) should continue.
Thanks in advance.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Dear Expert,
Is there a command to do that in Unix?
In such a way that we don't need to actually "write" or
modified the content.
-- monkfan (4 Replies)
Discussion started by: monkfan
4 Replies
2. Shell Programming and Scripting
Hi,
I am using the below copy command, to copy the file sbn to sbn1,
cp sbn sbn1
but its changing the date stamp of file sbn1, but i dont want to change the date stamp of sbn1.
Could you please help me out in this. (3 Replies)
Discussion started by: shivanete
3 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Please help me out on this one.
I want to send the output of a file as input for changing the date using date command.
Example, i have a file date.txt whose contents are 081014462009
I need to use the date in that file as input for date command.
I tried cat date.txt | date ; but it... (2 Replies)
Discussion started by: foxtron
2 Replies
4. IP Networking
Hi , Can some one tell me , is there a way to change the existing network parameter in existing OS image , or do i have to create a new image to have new network parameters . (0 Replies)
Discussion started by: thana
0 Replies
5. UNIX for Dummies Questions & Answers
Does anyone know how I can create a file like this:
blue 0
red 0
yellow 0
green 0
orange 0
blue 2
red 2
yellow 2
green 2
orange 2
blue 4
red 4
yellow 4
green 4
orange 4
blue 6
red 6 (5 Replies)
Discussion started by: cosmologist
5 Replies
6. Shell Programming and Scripting
Hi...
I have an inputfile name as :- abc_test_20120213.dat (date in yyyymmdd format)
I need the output file name as abc_test_13022012.dat (date in ddmmyyyy format)
Please help me on this...
Thanks in advance. (5 Replies)
Discussion started by: gani_85
5 Replies
7. Shell Programming and Scripting
the following was taken from a perl script:
my $date = strftime "%B %d %H:%M:%S", localtime;
how can i modify it so this date outputs the date in the form of the date of the messages file. for example:
Sep 20 11:48:44
As it is right now, the perl script outputs the date like this:
... (1 Reply)
Discussion started by: SkySmart
1 Replies
8. Shell Programming and Scripting
I have a CSV file with a date format like this;
11/19/2012 17:37:00,1.372,121.6
11/19/2012 17:38:00,0.743,121.6
Want to change the time stamp to seconds after 1970 so I can get the data in rrdtool. For anyone interested, this is data from a TED5000 unit and is Kwatts and volts.
Needs to... (3 Replies)
Discussion started by: ottsm
3 Replies
9. Shell Programming and Scripting
Hello,
I use a program using an input stream of parameters:
./my_prog.out <parameters.txt
The parameters.txt file has the following structure:
name
date
number1
number2
system
now imagine i would like to execute several times (>200) this program, but with different sets of number1... (2 Replies)
Discussion started by: shamsfield
2 Replies
10. UNIX for Beginners Questions & Answers
Hello All,
we what we call a parameter file (.txt) where my application read dynamic values when the job is triggered, one of such values are below:
abc.txt
------------------
line1
line2
line3
$$EDWS_DATE_INSERT=08-27-2019
line4
$$EDWS_PREV_DATE_INSERT=08-26-2019
I am trying to... (1 Reply)
Discussion started by: pradeepp
1 Replies
LEARN ABOUT MOJAVE
dpkg-trigger
dpkg-trigger(1) dpkg suite dpkg-trigger(1)
NAME
dpkg-trigger - a package trigger utility
SYNOPSIS
dpkg-trigger [option...] trigger-name
dpkg-trigger [option...] command
DESCRIPTION
dpkg-trigger is a tool to explicitly activate triggers and check for its support on the running dpkg.
This can be used by maintainer scripts in complex and conditional situations where the file triggers, or the declarative activate triggers
control file directive, are insufficiently rich. It can also be used for testing and by system administrators (but note that the triggers
won't actually be run by dpkg-trigger).
Unrecognized trigger name syntaxes are an error for dpkg-trigger.
COMMANDS
--check-supported
Check if the running dpkg supports triggers (usually called from a postinst). Will exit 0 if a triggers-capable dpkg has run, or 1
with an error message to stderr if not. Normally, however, it is better just to activate the desired trigger with dpkg-trigger.
-?, --help
Show the usage message and exit.
--version
Show the version and exit.
OPTIONS
--admindir=dir
Change the location of the dpkg database. The default location is /var/lib/dpkg.
--by-package=package
Override trigger awaiter (normally set by dpkg through the DPKG_MAINTSCRIPT_PACKAGE environment variable of the maintainer scripts,
naming the package to which the script belongs, and this will be used by default).
--no-await
This option arranges that the calling package T (if any) need not await the processing of this trigger; the interested package(s) I,
will not be added to T's trigger processing awaited list and T's status is unchanged. T may be considered installed even though I
may not yet have processed the trigger.
--await
This option does the inverse of --no-await (since dpkg 1.17.21). It is currently the default behavior.
--no-act
Just test, do not actually change anything.
EXIT STATUS
0 The requested action was successfully performed. Or a check or assertion command returned true.
1 A check or assertion command returned false.
2 Fatal or unrecoverable error due to invalid command-line usage, or interactions with the system, such as accesses to the database,
memory allocations, etc.
ENVIRONMENT
DPKG_ADMINDIR
If set and the --admindir option has not been specified, it will be used as the dpkg data directory.
SEE ALSO
dpkg(1), deb-triggers(5), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 dpkg-trigger(1)