Schema files and RCP via Hamlet: To use or not to use?
Posted: Wed Aug 18, 2010 9:59 am
I'm building a new application that on the surface is relatively simple. I have a list of data sources that are mostly mainframe datasets with a shorter list of copybooks involved, meaning that some record formats are for more than one dataset.
My goal is to parameterize the application as much as is practical.
I'm looking for general experience and/or advice on using schema files, and the difficulties it introduces in exchange for not having to explicitly define columns for every DS table. I want to avoid RCP as much as possible, because from the production support view this makes finding and diagnosing problems more difficult unless a DS person is brought in for every problem. We have a centralized support group that has no plans (for now) to have their own DS technical resource.
The basic job design I'm using as a template is also simple: Read the source (using FTP Enterprise as much as possible), if necessary run through a filter to remove data not needed for that feed, use a transformer to a common format for the load on the other side, and write to a sequential file (or FTP to a staging area) in the format the load process requires. The final destination is an Oracle database created for a vendor product that the internal clients will use. The vendor is providing a proprietary load utility, hence the common load format.
I know how to use RCP and schema files. I'm looking for general advice that will help me decide at the design level if I should use schema files.
Thanks,
Franklin
My goal is to parameterize the application as much as is practical.
I'm looking for general experience and/or advice on using schema files, and the difficulties it introduces in exchange for not having to explicitly define columns for every DS table. I want to avoid RCP as much as possible, because from the production support view this makes finding and diagnosing problems more difficult unless a DS person is brought in for every problem. We have a centralized support group that has no plans (for now) to have their own DS technical resource.
The basic job design I'm using as a template is also simple: Read the source (using FTP Enterprise as much as possible), if necessary run through a filter to remove data not needed for that feed, use a transformer to a common format for the load on the other side, and write to a sequential file (or FTP to a staging area) in the format the load process requires. The final destination is an Oracle database created for a vendor product that the internal clients will use. The vendor is providing a proprietary load utility, hence the common load format.
I know how to use RCP and schema files. I'm looking for general advice that will help me decide at the design level if I should use schema files.
Thanks,
Franklin