| Author |
Message
|
| sjp |
 Posted: Tue Nov 11, 2008 8:06 am Post subject: Problem using FileINput node on Mainframe |
 |
|
Novice
Joined: 21 Aug 2008
Posts: 18
|
Using FileInput Node, where set Message Domain = MRM and other Message parameters. Deployed flow locally and it is working.
But when I moved my flow and input file to Mainframe, nothing happened. FileInput node does not read file. It definitly see this file,
because if I change the Message Domain to BLOB, it consume this file and transfer it the following node. So, the matter in MessageDomain MRM.
Maybe something wrong with MRM Parser on Mainframe? If I connect fault terminal to Trace node - it is empty. Debug also does not help here,
because it happened right on first node. Any suggestions? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Nov 11, 2008 9:20 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Sounds as if you need to find out what the broker was doing, and whether it is reporting any errors. Where have you looked for errors? |
|
| Back to top |
|
|
| sridhsri |
| Posted: Tue Nov 11, 2008 10:59 am Post subject: |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
| I have no knowledge of mainframes but I know that there is a VSAM node in broker to read files on mainframe. Maybe you should check if you need that. |
|
| Back to top |
|
|
| mqpaul |
| Posted: Wed Nov 12, 2008 4:03 am Post subject: CCSID and Encoding may trouble FileInput node on mainframe |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
| sjp wrote: |
Using FileInput Node, where set Message Domain = MRM and other Message parameters. Deployed flow locally and it is working.
But when I moved my flow and input file to Mainframe, nothing happened. FileInput node does not read file. It definitly see this file,
because if I change the Message Domain to BLOB, it consume this file and transfer it the following node. So, the matter in MessageDomain MRM.
... |
I wonder if you are being caught out by the mainframe's CCSID. You are probably using a variant of ASCII or UTF-8 on your local machine, but the mainframe files will usually be in some form of EBCDIC. The broker will use the Queue Manager's default CCSID, and on a mainframe that's likely to be EBCDIC, such as 500 or 037. If your files are actually ASCII or UTF-8, you'll need to change the FileInput node's Parser properties page to use the correct CCSID. If your MRM message set uses TDS, it will not recognize the tags and delimiters if you use the wrong code page.
You might also be caught out by the mainframe's Encoding. PC-based local systems use little-endian binary data, but mainframes use big-endian. If your MRM message set uses CWF, numeric data is sensitive to the Encoding. Again, if your data is not generated by the mainframe (where it would use Encoding 785) you might need to change it to match the system originating the files.
_________________
Paul |
|
| Back to top |
|
|
| sjp |
| Posted: Wed Nov 12, 2008 10:44 am Post subject: |
|
|
Novice
Joined: 21 Aug 2008
Posts: 18
|
| I forgot to mention, that Even I run on a Mainframe, my files located on Unix System Service. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Nov 12, 2008 2:02 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
OK, I'm starting to sound like a one-trick pony lately, but I claim that's because of the type of problems which crop up on this forum.
You said
| Quote: |
| But when I moved my flow and input file to Mainframe, nothing happened |
It did though! What you meant was 'I could not see what was happening'. I assume that you have already checked the system log for errors. So the next step is to find out what really did happen. The only way I know to do that is to take a....sigh....user trace.
My guess is that you have a CCSID problem, as mqpaul suggested. But if so, I would have expected you to see an error in the system log. However, you will not see the full text of the error on a mainframe because only the first line of the message is written to the system log. The only way to see the full text of the error messages is to take a....user trace. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 12, 2008 4:56 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| In your defense, it's a very *good* trick. |
|
| Back to top |
|
|
| sjp |
| Posted: Thu Nov 13, 2008 4:56 am Post subject: |
|
|
Novice
Joined: 21 Aug 2008
Posts: 18
|
| There is no trick here: as I said, if I defined this file as BLOB, FileInput see this file and start processing, but I defined it as MRM, NOTHING going on. I mean NOTHING - no trace, no log errors, like file is not there. The problem with BLOB, if I use RCD node after FileInput to change definition, I get Parse error. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 13, 2008 5:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The trick in question is "Please Run User Trace".
It will tell you, far better than we can, exactly what's going on or not going on. |
|
| Back to top |
|
|
| sjp |
| Posted: Thu Nov 13, 2008 5:07 am Post subject: |
|
|
Novice
Joined: 21 Aug 2008
Posts: 18
|
| The problem with Trace node is, it located right after FileInput Node and because flow does not pick up the message NOTHIHNG in Trace file |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 13, 2008 5:16 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
User Trace has nothing to do with a Trace node, except that you can tell a Trace Node to output your own stuff to User Trace.
 |
|
| Back to top |
|
|
|
|
