Hi,
I want to convert some 100 seq file to 100 hash files.I found that i could convert it one by one.Any option of doing it at one stretch.
Multiple seq file to Hash file conversion
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 90
- Joined: Mon Dec 08, 2003 4:48 am
- Location: Chennai
Multiple seq file to Hash file conversion
Think Ahead,
Raj.D
Raj.D
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Do they all have the same record (line) layout? If so you can create a multi-instance job with the file name and hashed file name parameterized, and fire off all instances out of a job control that uses a loop of some kind to deliver parameter values to the separate instances.
If they have differing layouts, or even have to have different column names, you're pretty much stuck with the one at a time approach.
If they have differing layouts, or even have to have different column names, you're pretty much stuck with the one at a time approach.
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.
Well, you don't need 100 jobs to do this. You could do it in one or perhaps a small number of jobs by dropping multiple "copies" into the same job. A series of streams in the same job will (essentially) run in parallel.
I'm assuming here that the 100 files are not identically formatted. If they are, you could build a looping construct in a Batch to iterate thru the files one-by-one and call a single parameterized job. Assuming, again, that the files identical from a metadata standpoint and you could generate (parameterize) the names of the hash files to build, perhaps from the filename.
I'm assuming here that the 100 files are not identically formatted. If they are, you could build a looping construct in a Batch to iterate thru the files one-by-one and call a single parameterized job. Assuming, again, that the files identical from a metadata standpoint and you could generate (parameterize) the names of the hash files to build, perhaps from the filename.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers