03-01-2019
How to compile a Datastage Job using Execute Command Stage or Routines in Datastage 11?
I am trying to compile the datastage jobs using the Execute Command stage in datastage 11 or any Routines if possible. My datastage is on Unix machine.
So, How can I Compile a datastage job in UNIX from command line or any Routines.
Please help me in doing so.
Thank you.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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... (0 Replies)
Discussion started by: sureshg_sampat
0 Replies
2. UNIX for Advanced & Expert Users
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? (0 Replies)
Discussion started by: anaconga
0 Replies
3. Shell Programming and Scripting
Hi all,
My aim is to get the log details of datastage job using unix scipt.
we know that DSjob are used to get the log details from datastage universe through the adminstrator.can we call that DSjob rountine in our unix script.
Thanks in advance
Regards,
NimmyRaju:) (0 Replies)
Discussion started by: nimmyraju
0 Replies
4. UNIX and Linux Applications
hi,does anybody familiar with datastage tx.?
added your particular question:
I have to modify a map to drop a timestamp from the filename variable and pass that value down to the transform/validation maps.
thanks,,
Edit/Delete Message (1 Reply)
Discussion started by: sonja
1 Replies
5. Shell Programming and Scripting
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 (3 Replies)
Discussion started by: dsnaveen
3 Replies
6. Shell Programming and Scripting
We have a requirement as follows.
We have created a datastage job that will be doing the select operation from table (select query from a table).
The datastage job is being invoked by a unix shell script(ksh).
We are passing the "table name (STUD_DETAILS)" and a "where clause condition... (4 Replies)
Discussion started by: kmanivan82
4 Replies
7. UNIX for Advanced & Expert Users
HI,
I am trying to install IBM infosphere Datastage on my machine. which is
# uname -a
Linux "hostname" 2.6.18-238.el5 #1 SMP Sun Dec 19 14:22:44 EST 2010 x86_64 x86_64 x86_64 GNU/Linux
AS per the IBM DOC, we need to install the WAS (Websphere Administration Server ) and then proceed... (4 Replies)
Discussion started by: amarn48
4 Replies
8. Shell Programming and Scripting
Hi All,
I am using ETL tool Datastage and is installed on Linux environment. Few environment variables are set in datastage. Now my requirement is to use those environment variables in a unix script.
Is there any option I can do it?
Sugeestions from people working on datastage and linux... (1 Reply)
Discussion started by: bghosh
1 Replies
9. HP-UX
Hi All,
I am new to datastage just managing to modify packages with my prior knowledge in ETL tools like DTS and SSIS.
Now have ran in to a connectivity issue between datastage and unidata DB.
Software environment-
Datastage 7.5.2 running on windows server accessing unidata 7 on HP UX machine.... (1 Reply)
Discussion started by: roopeshvp
1 Replies
10. AIX
I am new to unix.
I started learning unix. Where can we practice unix commands.
Is there any free online tools are available? or Is there any free software ? (14 Replies)
Discussion started by: lucky20
14 Replies
LEARN ABOUT XFREE86
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)