Thread: need help w/ multiple file handles

Hi, I need to write a program which reads in some data file and in the event of
the occurance of a certain phrase writes something to an output file. Now the problem is that this phrase might occur more than just once in that data file so
I would need to open another file handle once I trip over that phrase again.
Well, is there anybody who can help me solve this problem ?

PS: I had to write that program for a UNISYS (if anyone knows what that is)
which is why I don't bother typing the true code here, it'd be too long and misleading. It is very important though that your suggestions are in Ansi-C since that unisys machine only accepts that.

We also have a UNISYS mainframe but all our mainframe programmers use cobol. Is C an extra package that you loaded on your mainframe?

As far as the multiple handles why can't you just keep using the same data file or do you have to seperate them? If you need to seperate them you could just write it all to one file then make another function to seperate them after.

well, i'm going to try that *fp[256] stuff, hope it works.
BTW, I'm actually the only unlucky guy (along w/another colleague) who's got to do C on that unisys. The other guys do cobol as well.

Is your UNISYS a clearpath? I am intrested in programming for out mainframe in C but we do not have it on there that I know of. I looked at the UNISYS website and they only talk about having java for the UNISYS (at least for MCP). I have been using a pc to connect to out databases on the mainframe using visual basic I am not to thrilled about vb so if you have to info on using C on the UNISYS I would be glad to hear about it...

I don't know about that clearpath stuff. I'm actually not that familiar with the UNISYS in general, what I know is basically what I need in order to develop for that mainframe. So it goes like this: I write C codeusing Borland CBuilder or UltraEdit, then I send it to the mainframe via an ftp-connect, then I open a terminal emulation program which is called Info-connect that lets me work right on the mainframe itself. Yeah, when I fire Infoconnect up, it says UNISYS operating environment v1100/2200 or something similar like this. What comes now is a bit hard to explain, but I'll try: Assuming the code's been uploaded successfully, I'll do something like "ADD filename-ext/L" in the workspace which compiles the source file. I usually then do "BRK" and then "L ERROR" which lists all errors and warnings generated by the compiler. If everything went alright, I eventually type "ADD filename/R" which generates a run. Again, if looking at the BRK-file does not bring up errors I go ahead and transfer whatever output the program did via FTP to my workstation to have a much more comfortable look at it.
I've got some information on how to program in C @work, I could of course copy some of those guidelines, so if anyone's interested, write me an email: [email protected]
Oh, I forgot something: those guidelines are in GERMAN.