Difference between revisions of "SQWareProduction:db2:bin:sqwdb2 RunJob.ksh"
m (Updated by BatchUser) |
m (Updated by BatchUser) |
||
| (25 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
| | | | ||
<pre> | <pre> | ||
| − | + | Not sending mail because you are in connected mode !!! | |
Lack 'instance' parameter | Lack 'instance' parameter | ||
| − | ./sqwdb2_RunJob.ksh[ | + | ./sqwdb2_RunJob.ksh[1918]: db2: not found [No such file or directory] |
</pre> | </pre> | ||
| | | | ||
{{SQWareProduction_sqwdb2_RunJob.ksh_example}} | {{SQWareProduction_sqwdb2_RunJob.ksh_example}} | ||
}} | }} | ||
Latest revision as of 15:53, 31 October 2024
Contents
Presentation
Script $gvsqw_D2db2Bin/sqwdb2_RunJob.ksh :
Run Db2 scripts and generate log and error file
based on $gvsqw_RootCfg/sqwdb2_Jobs.cfg configuration file
compress and purge oldest log files
Online help
The online help is available for most scripts with the -h option.
Ex: $gvsqw_D2db2Bin/sqwdb2_RunJob.ksh -h
Content of this assistance :
Sourcing sqwdb2_Global.lib v2024.07 SQWareProduction for Db2 (dbSQWare) ...
Usage: sqwdb2_RunJob.ksh [-h] -I <instance> -A <action> [+ options]
DESCRIPTION
sqwdb2_RunJob.ksh run script associated to the action parameter
SUPPORT
All rdbms type and version
PARAMETERS
-I instance : Target instance to action (or 'SQWareCentral').
-A action : Action to execute.
OPTIONS
-Locale locale : Force Locale for help display (fr,en).
-h : Display the full usage.
-s : Display samples of usage.
Error management
Errors passing arguments
This type of message is generated:
Lack 'instance' parameter, Usage: sqwdb2_RunJob.ksh [-h] -I <instance> -A <action> [+ options] For full help : sqwdb2_RunJob.ksh -h
If you are connecting through a terminal, no mail will be sent and you will have more this kind of message:
Not sending mail because you are in connected mode !!! Lack 'instance' parameter ./sqwdb2_RunJob.ksh[1918]: db2: not found [No such file or directory]
If you are not connected to a terminal, the error message appears and is sent by mail to the address contained in the variable $gvsqw_GlobalMail (See help customize this variable). The subject line will always start by "$gvsqw_MailMsg_db2 : " (See help customize this variable).
Execution errors
Whether you are or not connected to a terminal, the error message appears and an email containing a summary of treatment errors is sent to the address contained in the variable $gvsqw_Mail_db2 (See help customize this variable). The subject line will always start by "$gvsqw_MailMsg_db2 : " (See help customize this variable).
Usage examples
Sourcing sqwdb2_Global.lib v2024.07 SQWareProduction for Db2 (dbSQWare) ... #Standard generic help for script sqwdb2_RunJob.ksh: $gvsqw_Db2/sqwgen_RunJob.ksh -h #Display online help for this script $gvsqw_Db2/sqwgen_RunJob.ksh -Locale en -h #Display online help for this script with forcing of the 'en' locale (by default locale managed by $gvsqw_Locale) $gvsqw_Db2/sqwgen_RunJob.ksh -s #Display usage examples for this script $gvsqw_Db2/sqwgen_RunJob.ksh -I <Instance> -A <action> #Search action <action> in $gvsqw_RootCfg/sqwdb2_Jobs.cfg #and execute command line with eval function #genarate log file "$gvsqw_LogDir/"$(basename $lvsqw_Script|sed 's,.ksh$,,')_$(date +'%Y%m%d_%H%M%S').log #genarate error file "$gvsqw_LogDir/"$(basename $lvsqw_Script|sed 's,.ksh$,,')_$(date +'%Y%m%d_%H%M%S').err
