sequence + execute command activity + passing parameters
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 12
- Joined: Tue May 31, 2005 5:01 am
sequence + execute command activity + passing parameters
!hello!
i built a sequence justa as simple as this:
- 1st stage = execute command activity
- command = dir
- parameters = #directoria_saida# /B
- 2nd stage = another sequence
- parameter1 = 1st stage.$CommandOutput (string type)
this always fails, the log being:
sequnce.JobControl (@Job_Activity_5): Controller problem: Error calling DSSetParam(resultado), code=-4
[ParamValue/Limitvalue is not appropriate]
there is only one file in the directory #directoria_saida#
can someone help me ? i'm getting crazy ...
i built a sequence justa as simple as this:
- 1st stage = execute command activity
- command = dir
- parameters = #directoria_saida# /B
- 2nd stage = another sequence
- parameter1 = 1st stage.$CommandOutput (string type)
this always fails, the log being:
sequnce.JobControl (@Job_Activity_5): Controller problem: Error calling DSSetParam(resultado), code=-4
[ParamValue/Limitvalue is not appropriate]
there is only one file in the directory #directoria_saida#
can someone help me ? i'm getting crazy ...
Re: sequence + execute command activity + passing parameters
If B is a file and if you are on windows then it should be a back slash ""jsgoncalves wrote: parameters = #directoria_saida# /B
Code: Select all
#directoria_saida#\B
Kris
Where's the "Any" key?-Homer Simpson
Where's the "Any" key?-Homer Simpson
-
- Participant
- Posts: 12
- Joined: Tue May 31, 2005 5:01 am
Re: sequence + execute command activity + passing parameters
thank you ,
but
B is not a file, it is an option for the dir command, for the result of dir to only use bare format (no heading information or summary), e.g lixeira.txt instead of all the information/overhead
thnxs
but
B is not a file, it is an option for the dir command, for the result of dir to only use bare format (no heading information or summary), e.g lixeira.txt instead of all the information/overhead
thnxs
What version are you on? If it's earlier to 7.5 then there are known problems while passing parameters within the Execute Command Activity stage. What is your JobActivity5 stage?sequnce.JobControl (@Job_Activity_5): Controller problem: Error calling DSSetParam(resultado), code=-4
[ParamValue/Limitvalue is not appropriate]
Kris
Where's the "Any" key?-Homer Simpson
Where's the "Any" key?-Homer Simpson
-
- Participant
- Posts: 12
- Joined: Tue May 31, 2005 5:01 am
! Hello !
jobactivity5 is the one receiving the command.output
thnxs,
joaquim
version = 7.5.1kris007 wrote:What version are you on? If it's earlier to 7.5 then there are known problems while passing parameters within the Execute Command Activity stage. What is your JobActivity5 stage?sequnce.JobControl (@Job_Activity_5): Controller problem: Error calling DSSetParam(resultado), code=-4
[ParamValue/Limitvalue is not appropriate]
jobactivity5 is the one receiving the command.output
thnxs,
joaquim
Hi,
Can you check with parameter values in the Job activity5. The error shows that the parameter value or the limit value is not correct.
And next you are doing wrong in the execute command activity.
1) I think there is no command called 'dir' in unix.
2) parameter assinged is also wrong.
Can you check with parameter values in the Job activity5. The error shows that the parameter value or the limit value is not correct.
And next you are doing wrong in the execute command activity.
1) I think there is no command called 'dir' in unix.
2) parameter assinged is also wrong.
If possible can you just explain us what exactly you want to do?
built a sequence justa as simple as this:
- 1st stage = execute command activity
- command = dir
- parameters = #directoria_saida# /B
- 2nd stage = another sequence
- parameter1 = 1st stage.$CommandOutput (string type)
sequnce.JobControl (@Job_Activity_5): Controller problem: Error calling DSSetParam(resultado), code=-4
[ParamValue/Limitvalue is not appropriate]
jobactivity5 is the one receiving the command.output
-
- Participant
- Posts: 12
- Joined: Tue May 31, 2005 5:01 am
dir + job paraemteres + sequence
! hi !
I just want to do a simple thing:
job1 - to know which file is in the directory (windows = dir vs unix ls) (i always know there is only one file in the directory, that being garanteed by another 3rd party application that generates a file which keeps changing its name automatically generated) and have this filename passed into the 2nd job
job2 - get the filename from job1 (this job will have a ftp stage thus sendinf this file via ftp to another company ftp server)
1 - to know the file i dir directory /B
2 - to get the file name on job2 there is a parameter (job1.$CommandOutput)
thanxs,
joaquim
I just want to do a simple thing:
job1 - to know which file is in the directory (windows = dir vs unix ls) (i always know there is only one file in the directory, that being garanteed by another 3rd party application that generates a file which keeps changing its name automatically generated) and have this filename passed into the 2nd job
job2 - get the filename from job1 (this job will have a ftp stage thus sendinf this file via ftp to another company ftp server)
1 - to know the file i dir directory /B
2 - to get the file name on job2 there is a parameter (job1.$CommandOutput)
thanxs,
joaquim
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You may need to trim the command output of extraneous field marks and leading and trailing spaces.
Code: Select all
TrimF(TrimB(Trim(CommandActivity.$CommandOutput,@FM)))
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 12
- Joined: Tue May 31, 2005 5:01 am