Hi,
Im not using Datastage for the moment so I cannot test,
but if I remember right it should be possible to define a
function and therethrough send multiple variables to a
routine. The command is something like "deffun"...
I cannot remember but You could search in the help, there
should be something, or maybe this rings a bell for someone
else?
Hope this helps, sorry not to be more exact.
Regards,
Per
---------------------------------------------------------
Right idea, but...
The #parameter# construct will only work if it is directly
referenced in the
call of the routine, which doesnt get you around the one
parameter limit.
You could still use the idea of a job parameter, but inside
the routine,
call DSGetJobInfo to check if the required job parameter
exists and then
DSGetParamInfo to get the parameter value.
In the case of a before job routine, alternatively, you can
put whatever
code you like directly into the job control and this will
execute before the
stages in the job.
Then of course, as someone else suggested, you can
concatenate with a
separator like @VM (or anything else you like) and then
decompose the string
in the routine.
Food for thought.
-----Original Message-----
From:
Saravanan_Thirugnanam@singaporeair.com.sg
[mailto:
Saravanan_Thirugnanam@singaporeair.com.sg]
Sent: Wednesday, 17 October 2001 6:04 PM
To:
datastage-users@oliver.com
Subject: Re: Before/after stage routines
Hi,
Define all required parameters as job parameters and use it
with
#parameter# in befer/after stage/job routines. It should
work.
Rgds
Saravanan
"Ricketts, James"
cc:
Subject:
Before/after stage
routines
17-Oct-2001 03:37
Please respond to
datastage-users
Sender Info:
No Sender Info
found in the
address Book
Dear all
Before/after stage routines provide a single parameter for
use at
execution time. What hints or tricks do people use where
its appropriate
or
necessary to provide multiple parameters?
Cheers
James
This email and any files transmitted with it are
confidential and
intended solely for the use of the individual or entity to
whom they
are addressed. If you are not the intended addressee, you
must
not disclose, copy or take any action in reliance of this
transmission.
Although this message and its contents have been scanned for
viruses and no
viruses were detected, no responsibility whatsoever is
accepted by the
Company, or any of its offices or companies for any loss or
damage
arising in any way from receipt or use thereof.
If you have received this email in error please delete this
message and
notify the Polk System Administrator at
postmaster@polkglobal.com.
-----------------------------------------------
Right idea, but...
The #parameter# construct will only work if it is directly
referenced in the
call of the routine, which doesnt get you around the one
parameter limit.
You could still use the idea of a job parameter, but inside
the routine,
call DSGetJobInfo to check if the required job parameter
exists and then
DSGetParamInfo to get the parameter value.
In the case of a before job routine, alternatively, you can
put whatever
code you like directly into the job control and this will
execute before the
stages in the job.
Then of course, as someone else suggested, you can
concatenate with a
separator like @VM (or anything else you like) and then
decompose the string
in the routine.
Food for thought.
-----Original Message-----
From:
Saravanan_Thirugnanam@singaporeair.com.sg
[mailto:
Saravanan_Thirugnanam@singaporeair.com.sg]
Sent: Wednesday, 17 October 2001 6:04 PM
To:
datastage-users@oliver.com
Subject: Re: Before/after stage routines
Hi,
Define all required parameters as job parameters and use it
with
#parameter# in befer/after stage/job routines. It should
work.
Rgds
Saravanan
"Ricketts, James"
cc:
Subject:
Before/after stage
routines
17-Oct-2001 03:37
Please respond to
datastage-users
Sender Info:
No Sender Info
found in the
address Book
Dear all
Before/after stage routines provide a single parameter for
use at
execution time. What hints or tricks do people use where
its appropriate
or
necessary to provide multiple parameters?
Cheers
James
This email and any files transmitted with it are
confidential and
intended solely for the use of the individual or entity to
whom they
are addressed. If you are not the intended addressee, you
must
not disclose, copy or take any action in reliance of this
transmission.
Although this message and its contents have been scanned for
viruses and no
viruses were detected, no responsibility whatsoever is
accepted by the
Company, or any of its offices or companies for any loss or
damage
arising in any way from receipt or use thereof.
If you have received this email in error please delete this
message and
notify the Polk System Administrator at
postmaster@polkglobal.com.