0

I have implemented a custom extractor for NetCDF files and now I'm trying to implement a custom outputter for NetCDF files. When extracting from and outputting to NetCDF files, in the outputter I need to use some of the structural information found in the input files during extraction. Is there some way to store information when extracting that can be used in a custom outputter?

Magnus Johannesson
  • 432
  • 7
  • 20

1 Answers1

0

You would have to flow the information from your extract statement as part of the rowset into your output statement if the information is not known at compile time.

Michael Rys
  • 6,684
  • 15
  • 23
  • I now have two extract statements. One which extracts the real input data and one that extracts some metadata about the input data. Then I do some processing of the input data and now I'm implementing a custom outputter to output the processed input data. In the custom outputter, I need the metadata and I would like to pass it into the custom outputter in some way, but I don't know how. – Magnus Johannesson Dec 02 '16 at 15:07
  • You can use DEPLOY RESOURCE "adlspath"; to have the file containing the metadata copied to the custom outputter's local working directory. So you can read the file content inside your outputter code. – Michael Rys Dec 05 '16 at 04:33