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 HPUX

sh

sh(1)							      General Commands Manual							     sh(1)

NAME

       sh - overview of various system shells

SYNOPSIS

   POSIX Shell
       option] ...  string] [arg ...]

       option] ...  string] [arg ...]

   Korn Shell
       option] ...  string] [arg ...]

       option] ...  string] [arg ...]

   C Shell
       [command_file] [argument_list ...]

   Key Shell
DESCRIPTION

   Remarks
       The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX
       systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line.

       However, the command has historically been associated with the conventional Bourne shell, which could confuse some users.   To  meet  stan-
       dards  requirements  and also clarify the relationships of the various shells and where they reside on the system, this entry provides com-
       mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in  greater
       detail.

       The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5.  Please use the POSIX shell as an alternative.

   Shell Descriptions
       The HP-UX operating system supports the following shells:

	      POSIX-conforming command programming language and command interpreter
			residing  in  file Can execute commands read from a terminal or a file.  This shell conforms to current POSIX standards in
			effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects.	Similar in
			many  respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various
			other useful features.

	      Korn-shell command programming language and commands interpreter
			residing in file Can execute commands read from a terminal or a file.  This shell, like the POSIX shell, contains  a  his-
			tory mechanism, supports job control, and provides various other useful features.

	      A command language interpreter
			that incorporates a command history buffer, C-language-like syntax, and job control facilities.

	      Restricted version of the POSIX shell command interpreter.
			Sets  up  a  login  name  and  execution  environment whose capabilities are more controlled (restricted) than normal user
			shells.

	      restricted version of the Korn-shell command interpreter
			Sets up a login name and execution environment whose capabilities  are	more  controlled  (restricted)	than  normal  user
			shells.

	      An extension of the standard Korn Shell
			that uses hierarchical softkey menus and context-sensitive help.

							  +--------------+--------------------+
							  | To obtain:	 |  Use the command:  |
							  +--------------+--------------------+
							  | POSIX Shell  |  /usr/bin/sh ...   |
							  | Korn Shell	 |  /usr/bin/ksh ...  |
							  | C Shell	 |  /usr/bin/csh ...  |
							  | Key Shell	 |  /usr/bin/keysh    |
							  +--------------+--------------------+
       These shells can also be the default invocation, depending on the entry in the file.  See also chsh(1).

WARNINGS

       Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref-
       erence to ``see sh(1)''.

SEE ALSO

       For more information on the various individual shells, see:

       keysh(1)       Key Shell description.

       ksh(1)	      Korn Shell description.

       sh-posix(1)    POSIX Shell description.

       csh(1)	      C Shell description.

																	     sh(1)

Shell Programming and Scripting