Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Exit1 not to report failure in controlM Post 303043299 by Mi4304 on Thursday 23rd of January 2020 12:18:19 PM
Old 01-23-2020
Exit1 not to report failure in controlM

HI Team,

I running below script from controlM and job is reporting as failure everyday so i tried to change the if exitstatus=1 (send only email) but not to end as a job is failed. can you let me know where i have to change this script to make the script not to fail but instead send email and complete successfully
====
Code:
        && write_log "read complete and matched for ${YEAR}-${MONTH}-${DAY}" \
        && EXITSTATUS=0; } ;} \
        || { write_error "Failed read incomplete and is not matching with ${JOBFILE}" \
        && EXITSTATUS=1; }; }
return ${EXITSTATUS}
}

#
# Main
#

EXITSTATUS=1
[ $# -ne 7 ] && [ $# -ne 6 ] && usage && exit ${EXITSTATUS}
dfs fs -ls -d ${CLOUDDIR} > /dev/null 2>&1 || { write_error "${CLOUDDIR} does not exist. Exiting now!!!!" && exit ${EXITSTATUS}; }
dfs fs -ls ${JOBFILE} > /dev/null 2>&1 || { write_error "${JOBFILE} does not exist. Exiting now!!!!" && exit ${EXITSTATUS}; }

create_log_dir && create_log_files && read_check && EXITSTATUS=0

[ ${EXITSTATUS} -ne 0 ] && notify_error "!!!${ENVIRONMENT}: Validating ${SRCSYSTEMTYPE} files for job ${STATUS} failed!!!" ${LOG} ${ERROR}

exit ${EXITSTATUS}

Moderator's Comments:
Mod Comment Please use code tags when posting data and code samples!

Last edited by Neo; 01-24-2020 at 02:20 AM..
 

10 More Discussions You Might Find Interesting

1. Programming

ld failure

Hi, I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies

2. SCO

Raid5 Failure

Forgive me, I do not know much about RAID so I'm going to be as detailed as possible. This morning, our server's alarm was going. I found that one of our drives have failed. (we have 3) It is an Adaptec ATA RAID 2400A controller I'm purchasing a new SCSI drive today. My questions: ... (2 Replies)
Discussion started by: gseyforth
2 Replies

3. UNIX for Advanced & Expert Users

sudo comand with ControlM

I'm trying to change the user Id that the script is running under. I tried the sudo comand but the job was submitted under ControlM and it seems that controlM is not allowing the user id to change. I have included the job output below. The sudo comand was suppose to set the user id to "DWSOLAP"... (3 Replies)
Discussion started by: u156531
3 Replies

4. UNIX for Advanced & Expert Users

su failure

Usually when su rejects an attempt to switch user it responds with "Sorry" but with a certain username on some unix servers the response is "Killed". I'm guessing the su accepted the username/password but refused to spawn child shell with the specified username. What's causing this and what has to... (8 Replies)
Discussion started by: twk
8 Replies

5. UNIX for Dummies Questions & Answers

Identify File with ControlM Characters

Dear Members, I have a file which contains ControlM characters in it. I need a command by the means of which i should be able to identify if a file has controlM characters. How can this be achieved. Thanks Sandeep (4 Replies)
Discussion started by: sandeep_1105
4 Replies

6. Solaris

DMA failure ?

Our Solaris was hung yesterday, and dmesg show that, nxge3 : <== nxge_m_start: initialization failed nxge2 : nxge_dma_mem_alloc:ddi_dma_mem_alloc kmem alloc failed nxge2 : nxge_alloc_rx_buf_dma: Alloc Failed: dma 9 size_index 10 size requested 4194304 Does it mean the DMA failure ? How... (5 Replies)
Discussion started by: dehetoxic
5 Replies

7. Shell Programming and Scripting

Sftp failure

Hello, Sometimes when i execute my shell that makes sftp it gives me this error: Couldn't close file: Failure. What does it mean?, how can i make sure it will do ok?. Bye (2 Replies)
Discussion started by: rubber08
2 Replies

8. Red Hat

NT_STATUS_LOGON FAILURE

I am configuring Samba on one of my vmware.when i put smbclient -L local its showing error message : NT_STATUS_LOGON failure.I found that when i remove "Encrypted password entry from smb.conf" it works. pls help me ---------- Post updated at 08:39 PM ---------- Previous update was at 07:11 PM... (0 Replies)
Discussion started by: Vaibhav.T
0 Replies

9. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

10. Filesystems, Disks and Memory

MDADM Failure - where it came from?

Hello, i have a system with 6 sata3 seagate st3000dm01 disks running on stable Debian with software raid mdadm. i have md0 for root and md1 for swap and md2 for the files. i now want to add one more disk = sdh4 for md2 but i got this errors: The new disk is connected to an 4 port sata... (7 Replies)
Discussion started by: Sunghost
7 Replies
DH_INSTALLINIT(1)						     Debhelper							 DH_INSTALLINIT(1)

NAME
dh_installinit - install upstart jobs or init scripts into package build directories SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [-O] [--params] DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing upstart job files or init scripts with associated defaults files into package build directories, and in the former case providing compatibility handling for non-upstart systems. It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ and to start and stop the init scripts. FILES
debian/package.upstart If this exists, it is installed into etc/init/package.conf in the package build directory. debian/package.init Otherwise, if this exists, it is installed into etc/init.d/package in the package build directory. debian/package.default If this exists, it is installed into etc/default/package in the package build directory. OPTIONS
-n, --noscripts Do not modify postinst/postrm/prerm scripts. -o, --onlyscripts Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it. If no upstart job file is installed in the target directory when dh_installinit --onlyscripts is called, this program will assume that an init script is being installed and not provide the compatibility symlinks or upstart dependencies. -R, --restart-after-upgrade Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which stops the script in the prerm, and starts it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. -r, --no-restart-on-upgrade Do not stop init script on upgrade. --no-start Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts. -d, --remove-d Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ , or for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.) -uparams --update-rcd-params=params -- params Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8). --name=name Install the upstart job file or the init script (and default file) using the filename name instead of the default filename, which is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.upstart, debian/package.name.init and debian/package.name.default, instead of the usual debian/package.upstart, debian/package.init and debian/package.default. --init-script=scriptname Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file, if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks like package.scriptname and if so will install it as the init script in preference to the files it normally installs. This parameter is deprecated, use the --name parameter instead. This parameter will be ignored completely for upstart jobs. --upstart-only Only install an upstart job file, and do not include maintainer script code to replace an init script with that upstart job. This parameter is intended for use when the "package.upstart" file is new and only to be used on Upstart-based systems. --error-handler=function Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts, before the #DEBHELPER# token. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHORS
Joey Hess <joeyh@debian.org> Steve Langasek <steve.langasek@canonical.com> Scott James Remnant <scott@canonical.com> 8.9.0ubuntu2.1 2012-06-12 DH_INSTALLINIT(1)
All times are GMT -4. The time now is 06:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy