|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
maximum value of polling interval for FileInput node |
« View previous topic :: View next topic » |
Author |
Message
|
Vitor |
Posted: Tue Oct 18, 2016 8:35 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
Then you only have to worry about missed files, files processed out of sequence, codepage issues, files part processed when failures occur in the flow and all other wonderful issues that using a transactionally unsafe protocol entails. |
No, no I don't. The business users will have endured my standard lecture on sequencing and affinity so if they choose to ignore my sage advice then sympathetic as am I to them in their predicament I'm fine and thanks for taking an interest.
Likewise code pages and error handling. There's standard advice on the subject which these people ignore at their peril.
(The twin perils being explaining to our freakishly tall CTO what went wrong with their code and listening to me going "told you so") _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 18, 2016 8:39 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Joking somewhat aside, files for all their obviously flaws and faults are a transport mechanism that's not going away any time soon. The best we can do as a group of professionals is try to enforce good practice and proper procedures. Clearly the very best we can do is to eliminate files, and I do aspire to that, but in the short to medium term they're like the common cold; you keep up with your vitamins but expect that you're going to catch one sooner or later.
Especially with mainframe. Once the CTG and zOS Connect roll out then there will be better options to move data to and from that platform but until then (and possibly after the current generation of coders have retired) we're wedded to DD cards. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
rekarm01 |
Posted: Tue Oct 18, 2016 5:02 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 1415
|
zpat wrote: |
Then you only have to worry about missed files, files processed out of sequence, codepage issues, files part processed when failures occur in the flow and all other wonderful issues that using a transactionally unsafe protocol entails. |
Entails? Which of these issues are actually resolved by switching to a "transactionally safe" protocol? |
|
Back to top |
|
 |
smdavies99 |
Posted: Wed Oct 19, 2016 12:33 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
rekarm01 wrote: |
zpat wrote: |
Then you only have to worry about missed files, files processed out of sequence, codepage issues, files part processed when failures occur in the flow and all other wonderful issues that using a transactionally unsafe protocol entails. |
Entails? Which of these issues are actually resolved by switching to a "transactionally safe" protocol? |
How about all of them if the setup is done correctly and something like MQ is used. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|