BITCAT(1)

** TO BE DELETED ** TO BE DELETED ** TO BE DELETED ** TO BE DELETED **

NAME
bitcat, ndparse, transfer - bitnet incoming file processing programs

SYNOPSIS

bitcat [ -asa | -b | -d | -rawpun ] filepath

ndparse [ -n ] [ -a | -b ] [ -rawpun|-bitraw ] [ -d ] [ -o outpath ] filepath

/usr/lib/huji/transfer /absolute/file/path DestUser@DestNode **Under developement!**

DESCRIPTION

Bitcat is a simple minded tool for receiving files. Default usage is to translate EBCDIC PUNCH or PRINT records to ASCII and output them with appended newlines. Trailing spaces are removed at first, as they are (usually anyway) unnecessary.

Bitcat can enter -d (debug) mode, and display raw contents of spool file. (Occasionally interesting.)

Bitcat can also enter -b (binary) mode where it outputs every record of file in following (raw) format:
<char of reclen> <chars of record>

Alternatively bitcat can enter -rawpun state, where it outputs punch file in 80 characters per record format, no intermediate newlines or other fuss.

Non-binary mode uses internally compiled EBCDIC-ASCII translation table, and outputs are in ASCII.

When feed a print file, bitcat can convert it to raw ASCII with as accurate representation of carriage control, as possible. It is also possible to get FORTRAN-style carriage control mapped from MCC (see bitspool(5)), and that be outputed. (Option -asa)

Bitcat outputs file to STDOUT, and if wanted, debug output to STDERR.

Ndparse outputs to a file whose location is current working directory, and name is formed from spool entry by lowercaseing FileName.FileExt, unless `-o', is used to override it. With `-o' one can specify `-' to denote STDOUT. Debug output goes to STDERR as usual.

With ndparse ASCII (`-a', default when file does not have class N) output is plain translated records of original data with added separating newlines. (Not even chopping of the trailing spaces -- XX: could it be usefull still ?) Binary (with `-b', a default, if file has class N) mode is plain raw data from records. Nothing extra like bitcat's `-b' produces..

Ndparse is able to take input in varying formats:
- Standard spool files
- Bitcat -b -bitraw
- Raw 80 chars/rec punches -rawpun

Transfer program is under developement!

Transfer modifies file headers changing its destination address so it is possible to send that file again to NJE network for new destination. However other security related aspects may not allow all tricks. (For now origination address in headers will not be changed to point local user, and thus it is possible to create a file which seems to be traversing the network in wrong direction.) Transfer does also requeueing for file transmission. For this ABSOLUTE path (one starting with `/') is necessary.

OPTIONS

none
    Punch files are output as is, and Print files get converted from whatever carriage-control format they use to ASCII-CR/LF/FF format.

-asa
    Print files are output with FORTRAN-style carriage controls. One line per input record.

-b  Binary output. See DESCRIPTION on each command.

-bitraw
    Special input format switch for ndparse. Globs output from bitcat -b

-d  Debug output. To STDERR.

-n  Original `spool' file should not be removed after successfull file processing is done. (Successfull == No errors, Netdata file translated to ASCII using bitcat might not be usefull.)

-rawpun
    Special input format switch for ndparse.

ENVIRONMENT
With environment variable EBCDICTBL user can select alternate EBCDIC <-> ASCII translation tables. For more info, see ebcdictbl(5).

FILES
/etc/funetnje.cf
/etc/funetnje.pid
File processing exit config file, which is defined in funetnje.cf.

SEE ALSO
funetnje(8), bitspool(5), send(1), sendfile(1), bmail(1), ebcdictbl(5), mailify(8), sysin(8), qrdr(8), rdrlist(8)

BUGS

Ndparse should be able to dig original dates and names from ND file.

Sometimes ndparse fails to understand received netdata file. Subject for further study.

DIAGNOSTICS
When any of these programs is fed a file containing errorneous data (not funetnje(8) spool file,) these mostly recover with a burp, sometimes these might even drop a core on pathological input case.

WARNING
With ndparse it is one time mistake to forget to use -n when peeking a file. That file goes to bit bucket at that moment if no errors are detected. (rc=0 -> no file...)

AUTHORS

Yehavi Bourvine, Hebrew University of Yerusalem, Israel <yehavi@hujivms.bitnet>.

Matti Aarnio, Finnish University and Research Network - FUNET <mea@nic.funet.fi> <mea@finfiles.bitnet>.

Original (VMS oriented package) software by Yehavi Bourvine, UNIX features, plenty of modifications, man-pages by Matti Aarnio.