capture last run log using dsjob

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Capture run time of python script executed inside shell script

I have bash shell script which is internally calling python script.I would like to know how long python is taking to execute.I am not allowed to do changes in python script.Please note i need to know execution time of python script which is getting executed inside shell .I need to store execution...

2. Shell Programming and Scripting

UNIX Sqlplus - Capture the sql statement about to run and execution status

Greetings Experts, I am on AIX using ksh. Created a unix script which generates the CREATE OR REPLACE VIEW ... and GRANT .. statements, which are placed in a single .txt file. Now I need to execute the contents in the file (there are around 300 view creation and grant statements) in Oracle and...

3. Shell Programming and Scripting

SFTP Scripting and Log capture

Hi All, Need help in below query, appreciate your help. We are changing a FTP process to SFTP ( passwordless SSH ) I had few queries on how to log the transfer details into a log file. ----------------------------------------------------- PUTLOGFILE= /xxx/ftp_log.log FAILPUTLOGFILE=...

4. Shell Programming and Scripting

DataStage log file output via dsjob command

Hi, I do have 2 files Job_Name Job1 Job2 Job3 Instance_Name USA IND SRI I need to write a script, i.e, output of job1.USA should come in log in unix. i.,e When it runs for the first time it should run as Job1.USA next run Job1.IND Job1.SRI

5. Shell Programming and Scripting

Log Capture for Background Process

Hi , I am running a backgorund process called hello.sh ./hello & Now i need to capture the log file as it produces the output . i am not able to use " >> " nor " tee " to capture the output file / log file . Please let me know how can i do it ? Regards, Deepak Konnur

6. Shell Programming and Scripting

How to capture output to log file

Hi I have a script that will run multiple unix & sql commands. I want to see the output as well as capture it to a log file for further analysis. Is there an easy way to do that instead of adding "tee -a logfile" on everyline or even on the execute line (i.e. script | tee -s logfile). Thanks

7. UNIX for Advanced & Expert Users

invoke windows datastage dsjob from unix

hello, i have a windows server with datastage. In another machine, unix machine, i have a shell script that need to invoke the datastage dsjob. Can anyone help me?

8. Shell Programming and Scripting

dsjob command to execute DataStage jobs

Hi Friends, I am using a dsjob command in a unix script to invoke DataStage jobs. DataStage server jobs (version 7.5.2) The command looks like thisL: $DSBinPath/dsjob -server :$SERVER_PORTID -run -mode NORMAL -jobstatus -param INPUT_GCDB_DIR=$InputFilePath -param...

9. Shell Programming and Scripting

Capture the command run in the log file

Hi , I have seen some log files where they have captured the command that is being executed, comments present in the scripts and the out put of the command as well, through scripts. could any one of you please let me know how do i do that? Thanks in advance. Cheers, Waseem

10. Shell Programming and Scripting

Sh Prgram to capture Log message.

Hi All, I have a log file which consists of log messages as follows -> GLOBALCALLID_CLUSTERID_B NEXT * , O(") CHARACTER JOINONBEHALFOF NEXT * , O(") CHARACTER Record 1: Rejected - Error on table IFA_MMV_CDR, column CDRRECORDTYPE....

LEARN ABOUT FREEBSD

ddb

DDB(8)							    BSD System Manager's Manual 						    DDB(8)

NAME

     ddb -- configure DDB kernel debugger properties

SYNOPSIS

     ddb capture [-M -core] [-N -system] print
     ddb capture [-M -core] [-N -system] status
     ddb script scriptname
     ddb script scriptname=script
     ddb scripts
     ddb unscript scriptname
     ddb pathname

DESCRIPTION

     The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
     via sysctl(8) MIB entries.

     To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line.  An absolute pathname
     must be used.  The file will be read line by line and applied as arguments to the ddb utility.  Whitespace at the beginning of lines will be
     ignored as will lines where the first non-whitespace character is '#'.

OUTPUT CAPTURE

     The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
     a kernel on disk.	The following debugger commands are available from the command line:

     capture [-M core] [-N system] print
	     Print the current contents of the ddb(4) output capture buffer.

     capture [-M core] [-N system] status
	     Print the current status of the ddb(4) output capture buffer.

SCRIPTING

     The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
     ddb(4).  Each of the debugger commands is available from the command line:

     script scriptname
	     Print the script named scriptname.

     script scriptname=script
	     Define a script named scriptname.	As many scripts contain characters interpreted in special ways by the shell, it is advisable to
	     enclose script in quotes.

     scripts
	     List currently defined scripts.

     unscript scriptname
	     Delete the script named scriptname.

EXIT STATUS

     The ddb utility exits 0 on success, and >0 if an error occurs.

EXAMPLES

     The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:

	   ddb script kdb.enter.break="show pcpu; bt"

     The following example will delete the script:

	   ddb unscript kdb.enter.break

     For further examples, see the ddb(4) and textdump(4) manual pages.

SEE ALSO

     ddb(4), textdump(4), sysctl(8)

HISTORY

     The ddb utility first appeared in FreeBSD 7.1.

AUTHORS

     Robert N M Watson

BUGS

     Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).

BSD
								 December 24, 2008							       BSD

Shell Programming and Scripting