Page 1 of 1
Any Env Variable to Suppress Warnings in DS
Posted: Tue Jun 07, 2011 9:10 am
by vvsaucse
Hello,
My job aborts after 50 Warnings, as per the scheduled default limit, is there an alternative approach, to avoid this, perhaps like addition of an Env Variable, which ignores the same and continues execution even after 50 Warnings? I cannot run the job individually from Director since its triggered from Ctrl M.
Cheers
Subbu,
Posted: Tue Jun 07, 2011 9:16 am
by MarkB
No need for an ENV variable. Just go to the Limits tab and check 'No Limit' under warnings.
Posted: Tue Jun 07, 2011 9:19 am
by vvsaucse
@Mark,
Yes, thats a possible option, but this job is triggered from CtrlM via unix scripts. so we cannot do that.... Apologies, i havent' mentioned that in the first place.
Cheers
Subbu.
Posted: Tue Jun 07, 2011 9:52 am
by FranklinE
Here is a sample of what we use in the script called by Control-M. It is taken out of context of the whole script with details replaced:
Code: Select all
CM Command line: DS_ccc_dsjob_run.ksh -d aaa -e bbb -g ccc -p ddd -j %%JOBNAME
# Input Parameters: -d <IT Subdivision name>. Required Argument.
# -e <DS Environment>. Required Argument.
# -g <UNIX Group>. Required Argument.
# -p <DS Project Short name>. Required Argument.
# -j <DS job or sequence name>. Required Argument
# -i <ssi file / app_job identifier>. Optional. Example: XXX_myjob1
# -w <Warning limit>. Optional, defaults to 50 warnings.
# -r <Row limit>. Optional, defaults to no limit.
# -R Optional, reset jobs.
###
# process input parameters.
###
while getopts d:e:g:p:j:w:r:Rh param
do
case ${param} in
d) ITDIV=${OPTARG};;
e) PRJENV=${OPTARG};;
g) PRJGRP=${OPTARG};;
p) PRJNAME=${OPTARG};;
j) DSSEQNAME=${OPTARG};;
w) WARN_LIMIT="-warn ${OPTARG}";;
r) ROWS_LIMIT="-rows ${OPTARG}";;
P) PARAMSTRING="${PARAMSTRING} -param ${OPTARG} ";;
R) J_RESET=1;;
h) Usage; exit 0;;
\?) Usage; exit 8;;
esac
done
${DSHOME}/bin/dsjob ${G_DS_PORT_NUMBER} -run -jobstatus ${WARN_LIMIT} ${ROWS_LIMIT} ${PARAMSTRING} ${G_DS_PROJ_NAME} ${DSSEQNAME}
Refer to the manual for dsjob. The uppercase "-P" is used to carry other parameters from the CM command line, order date being the most common, and in this usage can repeat as many times as you have parameters you need to pass.
Re: Any Env Variable to Suppress Warnings in DS
Posted: Tue Jun 07, 2011 1:13 pm
by dspxguy
vvsaucse wrote:Hello,
My job aborts after 50 Warnings, as per the scheduled default limit, is there an alternative approach, to avoid this, perhaps like addition of an Env Variable, which ignores the same and continues execution even after 50 Warnings? I cannot run the job individually from Director since its triggered from Ctrl M.
Cheers
Subbu,