Additional text in the output of Execute Commant Stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
Additional text in the output of Execute Commant Stage
Hi,
I have a sequencer job that has three stages that are called in series
Stage 1: Job Activity Stage - It calls a multiple instance job (Job1)
Stage 2: Execute Command Stage - It executes a unix command.
Stage 3: Job Activity Stage - It calls another job (Job2) based on the output of unix command in previous stage.
I am facing strange problem. At times the output of stage 2 is appended by the text mentioned below
"[4444511] Done : DSD.RUN Job1.38 0/50/1/0/0"
Because of this the job called in Stage 3 does not get triggered as the output from the Stage2 does not match the required condition.
I am not sure why is this additional text coming intermittently.
Whenever I face this issue I simply run the job again without making any change to the code and it works fine.
Could you please through some light on this.
Thanks in advance for your help
-Sumit
I have a sequencer job that has three stages that are called in series
Stage 1: Job Activity Stage - It calls a multiple instance job (Job1)
Stage 2: Execute Command Stage - It executes a unix command.
Stage 3: Job Activity Stage - It calls another job (Job2) based on the output of unix command in previous stage.
I am facing strange problem. At times the output of stage 2 is appended by the text mentioned below
"[4444511] Done : DSD.RUN Job1.38 0/50/1/0/0"
Because of this the job called in Stage 3 does not get triggered as the output from the Stage2 does not match the required condition.
I am not sure why is this additional text coming intermittently.
Whenever I face this issue I simply run the job again without making any change to the code and it works fine.
Could you please through some light on this.
Thanks in advance for your help
-Sumit
-
- Participant
- Posts: 612
- Joined: Thu May 03, 2007 4:59 am
- Location: Melbourne
Done : DSD.RUN indicates a run of a server job. Now why this is appending to your Execute Command Stage can be figured out only by knowing what exactly your are doing with Execute Command Stage.
Joshy George
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
Thank you for your replyJoshGeorge wrote:Done : DSD.RUN indicates a run of a server job. Now why this is appending to your Execute Command Stage can be figured out only by knowing what exactly your are doing with Execute Command Stage.
In the Execute Command Stage I am running the following code:
grep 'TRAILER' #$FilePathDir#/#FileName# | wc -l
$FilePathDir is an environment variable for file path directory
FileName is a job parameter for File Name
This code will tell me if there is a record in the file that has text 'TRAILER'. If it is present then the output of the command would be the count of records that have text 'TRAILER'. If there are no such records the command should return zero.
The additional that I am talking about does not always get appended to the output of the command. It happens only sometimes.
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I have seen something similar to this in the past, where DataStage (UniVerse) was running out of file units in the rotating file pool, and data destined for one file unit was misdirected to another. Were there very many files open at the time?
Does the problem occur reliably? If not, is it only at busy times and not at quiet times?
Does the problem occur reliably? If not, is it only at busy times and not at quiet times?
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.