- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Is there a NiFi processor for mainframe VSAM ingest?
- Labels:
-
Apache NiFi
Created ‎08-04-2016 07:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there a processor to ingest a mainframe VSAM file? If not, is anyone aware of work in progress for this?
Created ‎08-30-2016 07:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@gkeys, in short no. There's nothing out of the box for integrated mainframe offload/ingest. That said there are several options that people have been pursuing for mainframe data movement using Apache NiFi (I've seen/talked to people doing all of these):
- Text flat file export with List/FetchSFTP and SplitText
- Binary flat file export with custom processors for record processing (e.g., using JRecord or 100% homegrown code)
- 3rd party mainframe offload/ETL tools like Syncsort
While dumping the data out in other formats or writing a custom processor works well, in scenarios with large numbers of record formats this doesn't scale in terms of processor or data flow development. That's when you should turn to products whose sole purpose is handling mainframe data.
Created ‎08-30-2016 07:34 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@gkeys, in short no. There's nothing out of the box for integrated mainframe offload/ingest. That said there are several options that people have been pursuing for mainframe data movement using Apache NiFi (I've seen/talked to people doing all of these):
- Text flat file export with List/FetchSFTP and SplitText
- Binary flat file export with custom processors for record processing (e.g., using JRecord or 100% homegrown code)
- 3rd party mainframe offload/ETL tools like Syncsort
While dumping the data out in other formats or writing a custom processor works well, in scenarios with large numbers of record formats this doesn't scale in terms of processor or data flow development. That's when you should turn to products whose sole purpose is handling mainframe data.
Created ‎03-18-2019 11:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
SYNCSORT Ironstream is the best option in this case.
