Received SIGPIPE signal caused by closing of the socket
Moderators: chulett, rschirm, roy
Received SIGPIPE signal caused by closing of the socket
Hi,
We are getting the below error when we are using & in the input file name.
main_program: Received SIGPIPE signal caused by closing of the socket on port 13,400.
No output will be sent to port 13,400 for the rest of the job.
The job is showing no counts on the links and job monitor count is coming as 0 in the log. When we remove the & the count is coming in the log.
The job has one input sequential stage and output oracle stage and the datastage version is 7.5.2.
Is there any problem with & in the input filename.
Regards,
Suman
We are getting the below error when we are using & in the input file name.
main_program: Received SIGPIPE signal caused by closing of the socket on port 13,400.
No output will be sent to port 13,400 for the rest of the job.
The job is showing no counts on the links and job monitor count is coming as 0 in the log. When we remove the & the count is coming in the log.
The job has one input sequential stage and output oracle stage and the datastage version is 7.5.2.
Is there any problem with & in the input filename.
Regards,
Suman
-
- Participant
- Posts: 334
- Joined: Fri Dec 01, 2006 5:17 am
- Location: Texas
Hi,
Detail of SIGPIPE error can be get by refering to following links:
viewtopic.php?t=85983&highlight=received+sigpipe
and this
viewtopic.php?t=95618&highlight=received+sigpipe
In the last link kumar_s has mentioned the solution ...as per his post ...
Detail of SIGPIPE error can be get by refering to following links:
viewtopic.php?t=85983&highlight=received+sigpipe
and this
viewtopic.php?t=95618&highlight=received+sigpipe
In the last link kumar_s has mentioned the solution ...as per his post ...
Code: Select all
SIGPIPE signal was received from the job Monitor. Its a known bug, and as advised by IBM, change the time based monitor to Size based monitor.
This information is available in release notes as well.
This is done by unsetting the APT_MONITOR_TIME environment
variable and setting the APT_MONITOR_SIZE variable to a suitable number,
e.g. 1000000. This will cause the job to update row count information
every 1000000 rows. The environment variables can be set in the Project
Properties (in the Administrator) - this will affect all jobs.
Alternatively, they be set for an individual job using the Job
Properties screen in the Designer.
To ensure the case, you can turn off the monitor for serveral runs.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 30
- Joined: Mon Sep 14, 2009 10:34 am
- Location: Omaha NE
-
- Premium Member
- Posts: 30
- Joined: Mon Sep 14, 2009 10:34 am
- Location: Omaha NE
Reviving an extinct thread may not be the best option .
What are you trying to do with the switch stage, can you give some more details on the job design ?
IBM best practices section 5.7.4 does not recommend using switch or filter when transformer stages are suitable. Only if your link execution conditions use runtime values ( using job parameters) , then consider filter or switch.
Best Practices URL http://www.redbooks.ibm.com/redbooks/SG ... wwhelp.htm
Sec 9.3 says this
--------------------------------------------------------------------------------
What are you trying to do with the switch stage, can you give some more details on the job design ?
IBM best practices section 5.7.4 does not recommend using switch or filter when transformer stages are suitable. Only if your link execution conditions use runtime values ( using job parameters) , then consider filter or switch.
Best Practices URL http://www.redbooks.ibm.com/redbooks/SG ... wwhelp.htm
Sec 9.3 says this
Code: Select all
9.3 Filter and Switch stages
The Filter and Switch stages evaluate their expressions at runtime for every input row. Because it is compiled, a parallel Transformer with output link constraints is faster than a Filter or Switch.
Use of Filter and Switch stages must be limited to instances where the entire filter or switch expression must be parameterized at runtime. In a Parallel Transformer, link constraint expressions, but not data, is fixed by the developer.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Learn the effect of the following special characters in the operating system shell:
- &
;
|
>
<
&&
||
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.