Sequential File...footer record have different format

sudhirmah · Post by **sudhirmah** » Thu Apr 21, 2005 2:34 am

Hi,

I have a sequential file having footer record differrent format.
in sequential stage getting warning on the last record.
any workaround instead of multiple record type handling trick.

TIA
SAM

ArndW · Post by **ArndW** » Thu Apr 21, 2005 2:48 am

The answer depends upon the type of warning you are getting with the footer row - please tell us what the warning is. If it is a sequential-file read error there might not be a way to read that last errant row without generating a message, so you might need to execute a before-job command that strips out the last line, or does a "wc -l" to get the number of lines and use that value in your job.

sudhirmah · Post by **sudhirmah** » Thu Apr 21, 2005 3:15 am

Hi,

am getting the error in the sequential stage...as below...

SRC_SEQ,0: Delimiter for field "ASSET" not found; input: {0d}, at offset: 41
.
.
SRC_SEQ,0: Import complete. 1 records imported successfully, 1 rejected.

TIA
SAM

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Thu Apr 21, 2005 3:29 am

As you are using PX, stripping the last line will be the possibility. But using 'wc -l' may not be as the last record in the file may not be the last record processed.

ArndW · Post by **ArndW** » Thu Apr 21, 2005 3:40 am

Just saw the same thing, it is a PX job (but posted in the Server forum) so the solution is quite different. As Sainath stated, with a Px sequential file read you can specify "read first rows" to limit the number of rows read using the output from a "wc -l" UNIX command and using 1 node. The best solution if the input file isn't huge is to make a copy without the offending last line.

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Thu Apr 21, 2005 4:06 am

Try using 'external source'.

bcarlson · Post by **bcarlson** » Mon Apr 25, 2005 12:47 pm

Not sure if this is the 'best' way to do it, but it worked well for us. We had a file that had both header and footer records. On import, we specified the main record layout and then made sure there was a reject link. The reject from an import leaves the data as a raw field so on the reject link we used the field import stage. The field import used the layout for the header/footer (they happened to be the same layout). We also had a reject link coming out of the field import (for real rejected records) and those got dumped into a dataset.

If you just don't need the header/footer, you could just leave them as rejected records (and skip the field import).

bcarlson