27-Nov-87 13:01:34-EST,2187;000000000001
Return-Path: <FDCCU@CUVMA.BITNET>
Received: from CUVMA.COLUMBIA.EDU by CU20B.COLUMBIA.EDU with TCP; Fri 27 Nov 87 13:01:32-EST
Received: from CUVMA.COLUMBIA.EDU(MAILER) by CUVMA.COLUMBIA.EDU(SMTP) ; Fri, 27 Nov 87 13:00:28 EST
Received: by CUVMA (Mailer X1.25) id 9710; Fri, 27 Nov 87 13:00:20 EST
Date: 11/27 12:17:13
From: FDCCU@CUVMA
Subject: RECK NOTE - PUN file from RSCS
Tag: FILE (8546) ORIGIN DBNUAMA1 RECK     11/27/87  7:17:40 E.S.T.
To: SY.FDC@CU20B
Reply-To: RECK%DBNUAMA1.BITNET@CUVMA.COLUMBIA.EDU

Date: 27 November 1987, 18:00:36 SET
From: Gisbert W.Selke           +49 228 225888       RECK     at DBNUAMA1
To:   FDCCU at CUVMA
cc:   ZRWA001 at DTUZDV1
Re:   MSBPCT.PAS with error checking

As I promised some time ago, here's a beefed-up version of MSBPCT.PAS. The
data handling is exactly as in the current version at CUVMA, as written by
Helmut Waelder; hence, it's very speedy.
In addition, it allows the user to override the original file name that
comes with the BOO file, and it performs a rudimentary check if the format
of the name in the boo file is ok. But what is more important: data integrity
checks are performed on the BOO file. Blanks are always discarded (even in the
middle of a line), and lines that are longer than permissible are flagged to
the user. (This costs nearly no execution time.) In addition, the user may
specify command line option '/c' to enable more rigorous checking: each
character outside the permissible range (depending on where in a chunk we are)
is flagged to the user. Execution, however, takes considerably longer in this
case, as you might expect it to do.
Anyway, this might be useful to users connected through EBCDIC hosts in order
to track down what exactly is going wrong. (I wish I'd had that some time
ago...)

I sent you the .PAS source, a BOO file (watch out for conversion errors -
I'm at an EBCDIC site :-)), and a HEX file produced by the public domain
utility HC.COM (checksum included at end of file). Apart from the checksum,
every vanilla de-hexer should be able to process that file. - Pick your
choice as to which files to install at CUVMA, if at all.


\Gisbert

