| Author |
Message
|
| jefflowrey |
 Posted: Tue Feb 12, 2008 9:54 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I *think*, and will gladly defer to mqpaul's guidance on this, that if you're reading the file record by record - then each record will be it's own transaction.
If you want to process all the records in one transaction, I think you have to use your MRM to break your file into records, and propagate each one to the MQOutput node.
Again, that's what I think.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| mqpaul |
| Posted: Wed Feb 13, 2008 3:28 am Post subject: FileInput node starts a new transaction for each record |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
Jeff's right - there's one transaction per record. Since we're talking about transactions, I better repeat what's in the documentation - the File nodes are not themselves transactional. This means that a failing transaction will roll back downstream actions on transactional nodes, but won't roll back any file activity, so you need to code your own back-out/recovery file processing. 
_________________
Paul |
|
| Back to top |
|
|
| jharringa |
| Posted: Wed Feb 13, 2008 11:42 am Post subject: |
|
|
Acolyte
Joined: 24 Aug 2007
Posts: 70
|
Yep. That works perfectly. Thank you for your help with this. I think that we're good to go now.
mqpaul - yeah, I did notice that about file processing with respect to transactionality (and that makes sense).
This is a really neat node. Kudos to the Broker team! Hopefully this will be a useful thread for others too. Thanks again!
 |
|
| Back to top |
|
|
| kzhou |
| Posted: Tue May 13, 2008 8:16 am Post subject: FileInput 6.1 for grabbing files from the mainframe |
|
|
Newbie
Joined: 13 May 2008
Posts: 2
|
I have the same issue as jharringa had initially: I'm trying to transfer a file from mainframe to a unix server via FTP using FileInput 6.1. My understanding is that jharringa set up a unix server on the mainframe side to do the file transfer, i.e. the file transfer is between two unix servers. Is there a way to transfer files directly from the mainframe to another unix server? I have configured my FileInput node with the following values:
- Message Domain : BLOB
- Message Coded Character Set ID : Broker system default
- FTP server and port : myMainframeServer
- Security identity : testFileInputNodeMF
- Server directory : .
- Transfer mode : Binary / ASCII --- [i]tried both modes but none is working[/i]
and the message flow I created is very simply, just FileInput node -> MQOutput node. I just wanted to test out if the file is successfully ftped from the mainframe to the broker server. But it seems that nothing happened. The file is not ftped. I then connected the failure and catch terminals on the FileInput node to output. Still nothing is captured.
Could someone help me on this issue please?
Thank you! |
|
| Back to top |
|
|
| mqpaul |
| Posted: Tue May 13, 2008 9:46 am Post subject: V6.1 FileNode FTP client works with UNIX and Windows servers |
|
|
Acolyte
Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK
|
The File nodes FTP client can talk to UNIX or Windows FTP servers. The z/OS USS is a UNIX environment, so the File nodes can talk to an FTP server running there.
The native z/OS FTP server responds differently, because z/OS datasets are not organized into directories in quite the same way. The File Nodes' FTP client does not understand the file lists it gets from z/OS FTP servers.
_________________
Paul |
|
| Back to top |
|
|
| kzhou |
| Posted: Tue May 13, 2008 11:10 am Post subject: |
|
|
Newbie
Joined: 13 May 2008
Posts: 2
|
Paul,
Thank you so much for your prompt response!
Kate |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Aug 11, 2008 7:49 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
When you contact the FTP server on z/OS it can respond by mapping native (OS) datasets or it can use the HFS (or ZFS).
The latter two are exactly like a Unix file system, hosted on z/OS using a special type of VSAM dataset.
The former is slightly different which can confuse some FTP client software (although many of them have an option to deal with it).
USS is not UNIX, it is an emulation by mapping to z/OS services.
You might run a program on the mainframe to copy a native OS dataset to a HFS file. thus making it accessible by this FTP client.
There is only one type of FTP server on z/OS.
z/OS also has a FTP client, so you can push the dataset onto another FTP server (ie. the the WMB broker) to avoid this problem. |
|
| Back to top |
|
|
|
|
