By default, PIO handles errors internally by printing a string describing the error and then calling mpi_abort. Application developers can change this behaivior with a call to PIO_seterrorhandling

For example, if a developer wanted to see if an input netcdf file contained the variable 'U' they might do the following:

 call pio_seterrorhandling(File, PIO_BCAST_ERROR)
 ierr =  pio_inq_varid(File, 'U', uid)
 call pio_seterrorhandling(File, PIO_INTERNAL_ERROR)
 if(ierr/= PIO_NOERR) then
   write(stderr,*) 'Variable U not found on input file, setting to 0'
   U=0
 else
   ...
 endif

The three types of error handling methods are:

PIO_INTERNAL_ERROR : abort on error from any task
PIO_BCAST_ERROR : broadcast an error from io_rank 0 to all tasks in comm
PIO_RETURN_ERROR : do nothing - allow the user to handle it