ParamValue/Limitvalue is not appropriate

[kondeti]

Hi Everyone,
This is my sequencer design.

Job1 ---> Execute Command ----> Job2

Job1 ---> In job1 I am generating one job name into a text file.

Execute Command ---> I am executing "type path....file.txt".

Job2 ---> I am passing the job name value as a parameter to the job2.

The above sequencer is Aborting and it is generating the below error message. I already searched for the same in the site. But, I didn't understand the exact problem for my sequencer failure. Can anyone help me on this? Thank you.

[b]"POC_Sequencer..JobControl (@Job_Activity_16): Controller problem: Error calling DSSetParam(pJobName), code=-4
[ParamValue/Limitvalue is not appropriate]"[/b]

[chulett]

There are 62 matches for that error message. I picked one at random and it seems to have everything you need in it. If it doesn't help, please let us know why, which part isn't making enough sense and we'll see what we can do about that.

[kondeti]

Thank you so much Chulett.

I am passing the Execute_Command output to a Before Subroutine as a job name to generate dsjob -report. With your suggestion I used below code in the job activity and it resolved my issue. Thank you.

Code: Trim(EReplace(Execute_Command_18.$CommandOutput,@FM,""),("":'"':""), "A")

Here I was trying to understand @FM behavior, I have gone thru the DataStage documentation this is what I got.

@FM Field mark.
@IM Item mark.
@SM Subvalue mark.
@TM Text mark.
@VM Value mark.

Can you please explain me how @FM is helped to resolve this problem. Thank you.

[priyadarshikunal]

look for the last comment by Craig in the topic mentioned below

viewtopic.php?p=308527&highlight=#308527