Hello,
How do we call the sdk/Utility Transforms like
UtilityRunJob, UtilityGetRunJobInfo etc. from our
job control scripts? How do we define these functions
in our job control scripts?
Is it a good practise to use these utilities for
running our jobs?
Regards
Shrikanth
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
sdk/Utility Transforms
If theyre transform functions (and everything under sdkUtility is), you can declare them as functions. For example: DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit) Calling "DSU.UtilityRunJob" The "DSU" prefix stands for "DataStage User-written".
As to whether its a good practice, only you can make that decision in your own particular environment. My preference is to keep total control in my own job control routines, by calling the lower level functions such as DSRunJob, DSGetJobInfo, etc., directly. The sdk routines are (a) utilities,
(b) examples of what can be done, and (c) capable of improvement.
-----Original Message-----
From: Shrikanth Ramanathan [mailto:ar_shriks@yahoo.com]
Sent: Monday, 03 September 2001 00:08
To: datastage-users@oliver.com
Subject: sdk/Utility Transforms
Hello,
How do we call the sdk/Utility Transforms like UtilityRunJob, UtilityGetRunJobInfo etc. from our job control scripts? How do we define these functions in our job control scripts?
Is it a good practise to use these utilities for running our jobs?
Regards
Shrikanth
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
As to whether its a good practice, only you can make that decision in your own particular environment. My preference is to keep total control in my own job control routines, by calling the lower level functions such as DSRunJob, DSGetJobInfo, etc., directly. The sdk routines are (a) utilities,
(b) examples of what can be done, and (c) capable of improvement.
-----Original Message-----
From: Shrikanth Ramanathan [mailto:ar_shriks@yahoo.com]
Sent: Monday, 03 September 2001 00:08
To: datastage-users@oliver.com
Subject: sdk/Utility Transforms
Hello,
How do we call the sdk/Utility Transforms like UtilityRunJob, UtilityGetRunJobInfo etc. from our job control scripts? How do we define these functions in our job control scripts?
Is it a good practise to use these utilities for running our jobs?
Regards
Shrikanth
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
I defined the function UtilityRunJob in my job
control, as I would define any other user-defined
function. i.e.
DEFFUN UtilityRunJob(JobName, ParamList, RowLimit,
WarnLimit) Using "DSU.UtilityRunJob"
But on running the compiled job, it aborted with the
following message:
DataStage Job 235 Phantom 1327
Program "JOB.1353853337.DT.1230149925": Line 12,
Unable to open the operating system file "RT_BP235.O/DSU.UtilityRunJob". [ENOENT] No such file or directory Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load file "DSU.UtilityRunJob". Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load subroutine. Attempting to Cleanup after ABORT raised in stage testsdk.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
I presume that this happens because UtilityRunJob is
a built-in function and not a user-defined function. I
made a copy of this utility and saved it in different
name and my job ran fine. The help on DEFFUN
function states that it Defines a user-written
function.
Is anyone making use of these utilities and if so, how
have you defined it in your job control scripts?
Thanks,
Shrikanth
--- Ray Wurlod wrote:
> If theyre transform functions (and everything under sdkUtility is),
> you can declare them as functions. For example:
> DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit)
> Calling
> "DSU.UtilityRunJob"
> The "DSU" prefix stands for "DataStage
> User-written".
>
> As to whether its a good practice, only you can
> make that decision in your
> own particular environment. My preference is to
> keep total control in my
> own job control routines, by calling the lower level functions such as
> DSRunJob, DSGetJobInfo, etc., directly. The sdk
> routines are (a) utilities,
> (b) examples of what can be done, and (c) capable of
> improvement.
>
> -----Original Message-----
> From: Shrikanth Ramanathan
> [mailto:ar_shriks@yahoo.com]
> Sent: Monday, 03 September 2001 00:08
> To: datastage-users@oliver.com
> Subject: sdk/Utility Transforms
>
>
> Hello,
>
> How do we call the sdk/Utility Transforms like
> UtilityRunJob,
> UtilityGetRunJobInfo etc. from our job control
> scripts? How do we define
> these functions in our job control scripts?
>
> Is it a good practise to use these utilities for
> running our jobs?
>
> Regards
> Shrikanth
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
control, as I would define any other user-defined
function. i.e.
DEFFUN UtilityRunJob(JobName, ParamList, RowLimit,
WarnLimit) Using "DSU.UtilityRunJob"
But on running the compiled job, it aborted with the
following message:
DataStage Job 235 Phantom 1327
Program "JOB.1353853337.DT.1230149925": Line 12,
Unable to open the operating system file "RT_BP235.O/DSU.UtilityRunJob". [ENOENT] No such file or directory Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load file "DSU.UtilityRunJob". Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load subroutine. Attempting to Cleanup after ABORT raised in stage testsdk.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
I presume that this happens because UtilityRunJob is
a built-in function and not a user-defined function. I
made a copy of this utility and saved it in different
name and my job ran fine. The help on DEFFUN
function states that it Defines a user-written
function.
Is anyone making use of these utilities and if so, how
have you defined it in your job control scripts?
Thanks,
Shrikanth
--- Ray Wurlod wrote:
> If theyre transform functions (and everything under sdkUtility is),
> you can declare them as functions. For example:
> DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit)
> Calling
> "DSU.UtilityRunJob"
> The "DSU" prefix stands for "DataStage
> User-written".
>
> As to whether its a good practice, only you can
> make that decision in your
> own particular environment. My preference is to
> keep total control in my
> own job control routines, by calling the lower level functions such as
> DSRunJob, DSGetJobInfo, etc., directly. The sdk
> routines are (a) utilities,
> (b) examples of what can be done, and (c) capable of
> improvement.
>
> -----Original Message-----
> From: Shrikanth Ramanathan
> [mailto:ar_shriks@yahoo.com]
> Sent: Monday, 03 September 2001 00:08
> To: datastage-users@oliver.com
> Subject: sdk/Utility Transforms
>
>
> Hello,
>
> How do we call the sdk/Utility Transforms like
> UtilityRunJob,
> UtilityGetRunJobInfo etc. from our job control
> scripts? How do we define
> these functions in our job control scripts?
>
> Is it a good practise to use these utilities for
> running our jobs?
>
> Regards
> Shrikanth
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
As Ray notes, I usually stick to the base routines when using Job Control...
however, the SDK routines are especially nice when you want to issue one of these commands from within a Transform.... in the depths of a job.
Ernie
-----Original Message-----
From: Shrikanth Ramanathan [mailto:ar_shriks@yahoo.com]
Sent: Tuesday, September 04, 2001 12:27 PM
To: datastage-users@oliver.com
Subject: RE: sdk/Utility Transforms
I defined the function UtilityRunJob in my job
control, as I would define any other user-defined
function. i.e.
DEFFUN UtilityRunJob(JobName, ParamList, RowLimit,
WarnLimit) Using "DSU.UtilityRunJob"
But on running the compiled job, it aborted with the
following message:
DataStage Job 235 Phantom 1327
Program "JOB.1353853337.DT.1230149925": Line 12,
Unable to open the operating system file "RT_BP235.O/DSU.UtilityRunJob". [ENOENT] No such file or directory Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load file "DSU.UtilityRunJob". Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load subroutine. Attempting to Cleanup after ABORT raised in stage testsdk.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
I presume that this happens because UtilityRunJob is
a built-in function and not a user-defined function. I
made a copy of this utility and saved it in different
name and my job ran fine. The help on DEFFUN
function states that it Defines a user-written
function.
Is anyone making use of these utilities and if so, how
have you defined it in your job control scripts?
Thanks,
Shrikanth
--- Ray Wurlod wrote:
> If theyre transform functions (and everything under sdkUtility is),
> you can declare them as functions. For example:
> DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit)
> Calling
> "DSU.UtilityRunJob"
> The "DSU" prefix stands for "DataStage
> User-written".
>
> As to whether its a good practice, only you can
> make that decision in your
> own particular environment. My preference is to
> keep total control in my
> own job control routines, by calling the lower level functions such as
> DSRunJob, DSGetJobInfo, etc., directly. The sdk
> routines are (a) utilities,
> (b) examples of what can be done, and (c) capable of
> improvement.
>
> -----Original Message-----
> From: Shrikanth Ramanathan
> [mailto:ar_shriks@yahoo.com]
> Sent: Monday, 03 September 2001 00:08
> To: datastage-users@oliver.com
> Subject: sdk/Utility Transforms
>
>
> Hello,
>
> How do we call the sdk/Utility Transforms like
> UtilityRunJob,
> UtilityGetRunJobInfo etc. from our job control
> scripts? How do we define
> these functions in our job control scripts?
>
> Is it a good practise to use these utilities for
> running our jobs?
>
> Regards
> Shrikanth
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
however, the SDK routines are especially nice when you want to issue one of these commands from within a Transform.... in the depths of a job.
Ernie
-----Original Message-----
From: Shrikanth Ramanathan [mailto:ar_shriks@yahoo.com]
Sent: Tuesday, September 04, 2001 12:27 PM
To: datastage-users@oliver.com
Subject: RE: sdk/Utility Transforms
I defined the function UtilityRunJob in my job
control, as I would define any other user-defined
function. i.e.
DEFFUN UtilityRunJob(JobName, ParamList, RowLimit,
WarnLimit) Using "DSU.UtilityRunJob"
But on running the compiled job, it aborted with the
following message:
DataStage Job 235 Phantom 1327
Program "JOB.1353853337.DT.1230149925": Line 12,
Unable to open the operating system file "RT_BP235.O/DSU.UtilityRunJob". [ENOENT] No such file or directory Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load file "DSU.UtilityRunJob". Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load subroutine. Attempting to Cleanup after ABORT raised in stage testsdk.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
I presume that this happens because UtilityRunJob is
a built-in function and not a user-defined function. I
made a copy of this utility and saved it in different
name and my job ran fine. The help on DEFFUN
function states that it Defines a user-written
function.
Is anyone making use of these utilities and if so, how
have you defined it in your job control scripts?
Thanks,
Shrikanth
--- Ray Wurlod wrote:
> If theyre transform functions (and everything under sdkUtility is),
> you can declare them as functions. For example:
> DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit)
> Calling
> "DSU.UtilityRunJob"
> The "DSU" prefix stands for "DataStage
> User-written".
>
> As to whether its a good practice, only you can
> make that decision in your
> own particular environment. My preference is to
> keep total control in my
> own job control routines, by calling the lower level functions such as
> DSRunJob, DSGetJobInfo, etc., directly. The sdk
> routines are (a) utilities,
> (b) examples of what can be done, and (c) capable of
> improvement.
>
> -----Original Message-----
> From: Shrikanth Ramanathan
> [mailto:ar_shriks@yahoo.com]
> Sent: Monday, 03 September 2001 00:08
> To: datastage-users@oliver.com
> Subject: sdk/Utility Transforms
>
>
> Hello,
>
> How do we call the sdk/Utility Transforms like
> UtilityRunJob,
> UtilityGetRunJobInfo etc. from our job control
> scripts? How do we define
> these functions in our job control scripts?
>
> Is it a good practise to use these utilities for
> running our jobs?
>
> Regards
> Shrikanth
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
It seems the SDK routines are not catalogued in the standard way. The DEFFUN statement you need is DEFFUN UtilityRunJob(JobName, ParamList, RowLimit, WarnLimit) Using "DSX.UTILITYRUNJOB" Note that the catalog name is all upper case.
-----Original Message-----
From: Shrikanth Ramanathan [mailto:ar_shriks@yahoo.com]
Sent: Wednesday, 05 September 2001 02:27
To: datastage-users@oliver.com
Subject: RE: sdk/Utility Transforms
I defined the function UtilityRunJob in my job
control, as I would define any other user-defined
function. i.e.
DEFFUN UtilityRunJob(JobName, ParamList, RowLimit,
WarnLimit) Using "DSU.UtilityRunJob"
But on running the compiled job, it aborted with the
following message:
DataStage Job 235 Phantom 1327
Program "JOB.1353853337.DT.1230149925": Line 12,
Unable to open the operating system file "RT_BP235.O/DSU.UtilityRunJob". [ENOENT] No such file or directory Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load file "DSU.UtilityRunJob". Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load subroutine. Attempting to Cleanup after ABORT raised in stage testsdk.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
I presume that this happens because UtilityRunJob is
a built-in function and not a user-defined function. I
made a copy of this utility and saved it in different
name and my job ran fine. The help on DEFFUN
function states that it Defines a user-written
function.
Is anyone making use of these utilities and if so, how
have you defined it in your job control scripts?
Thanks,
Shrikanth
--- Ray Wurlod wrote:
> If theyre transform functions (and everything under sdkUtility is),
> you can declare them as functions. For example:
> DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit)
> Calling
> "DSU.UtilityRunJob"
> The "DSU" prefix stands for "DataStage
> User-written".
>
> As to whether its a good practice, only you can
> make that decision in your
> own particular environment. My preference is to
> keep total control in my
> own job control routines, by calling the lower level functions such as
> DSRunJob, DSGetJobInfo, etc., directly. The sdk
> routines are (a) utilities,
> (b) examples of what can be done, and (c) capable of
> improvement.
>
> -----Original Message-----
> From: Shrikanth Ramanathan
> [mailto:ar_shriks@yahoo.com]
> Sent: Monday, 03 September 2001 00:08
> To: datastage-users@oliver.com
> Subject: sdk/Utility Transforms
>
>
> Hello,
>
> How do we call the sdk/Utility Transforms like
> UtilityRunJob,
> UtilityGetRunJobInfo etc. from our job control
> scripts? How do we define
> these functions in our job control scripts?
>
> Is it a good practise to use these utilities for
> running our jobs?
>
> Regards
> Shrikanth
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
-----Original Message-----
From: Shrikanth Ramanathan [mailto:ar_shriks@yahoo.com]
Sent: Wednesday, 05 September 2001 02:27
To: datastage-users@oliver.com
Subject: RE: sdk/Utility Transforms
I defined the function UtilityRunJob in my job
control, as I would define any other user-defined
function. i.e.
DEFFUN UtilityRunJob(JobName, ParamList, RowLimit,
WarnLimit) Using "DSU.UtilityRunJob"
But on running the compiled job, it aborted with the
following message:
DataStage Job 235 Phantom 1327
Program "JOB.1353853337.DT.1230149925": Line 12,
Unable to open the operating system file "RT_BP235.O/DSU.UtilityRunJob". [ENOENT] No such file or directory Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load file "DSU.UtilityRunJob". Program "JOB.1353853337.DT.1230149925": Line 12, Unable to load subroutine. Attempting to Cleanup after ABORT raised in stage testsdk.JobControl
DataStage Phantom Aborting with @ABORT.CODE = 3
I presume that this happens because UtilityRunJob is
a built-in function and not a user-defined function. I
made a copy of this utility and saved it in different
name and my job ran fine. The help on DEFFUN
function states that it Defines a user-written
function.
Is anyone making use of these utilities and if so, how
have you defined it in your job control scripts?
Thanks,
Shrikanth
--- Ray Wurlod wrote:
> If theyre transform functions (and everything under sdkUtility is),
> you can declare them as functions. For example:
> DEFFUN UtilityRunJob(Jname,Jparams,Rlimit,Wlimit)
> Calling
> "DSU.UtilityRunJob"
> The "DSU" prefix stands for "DataStage
> User-written".
>
> As to whether its a good practice, only you can
> make that decision in your
> own particular environment. My preference is to
> keep total control in my
> own job control routines, by calling the lower level functions such as
> DSRunJob, DSGetJobInfo, etc., directly. The sdk
> routines are (a) utilities,
> (b) examples of what can be done, and (c) capable of
> improvement.
>
> -----Original Message-----
> From: Shrikanth Ramanathan
> [mailto:ar_shriks@yahoo.com]
> Sent: Monday, 03 September 2001 00:08
> To: datastage-users@oliver.com
> Subject: sdk/Utility Transforms
>
>
> Hello,
>
> How do we call the sdk/Utility Transforms like
> UtilityRunJob,
> UtilityGetRunJobInfo etc. from our job control
> scripts? How do we define
> these functions in our job control scripts?
>
> Is it a good practise to use these utilities for
> running our jobs?
>
> Regards
> Shrikanth
>
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com