problems with fscanf

Here is a problem that's causing a lot of trouble for a user of pC++, Mike 
Norman's student, at NCSA.  The problem is that although fopen is correctly
converted to pcxx_fopen, a susequent fscanf is not.  So if fopen and fscanf
appear, say, in main thread, processor zero will open the file, but all
processors will do fscanf.  Since the file is not opened on other processors,
the program will crash.  We need something similar to what we have for scanf.