RECEIVE(1)

** RAW DRAFT ** RAW DRAFT ** RAW DRAFT ** RAW DRAFT **

NAME
receive, transfer - bitnet incoming file processing programs

SYNOPSIS

receive [-n] [-a|-b] [-asa|-rawpun|-bitraw|-bcat] [-d] [-u username ] [-o outpath ] {filepath|spoolid}

/usr/lib/huji/transfer DestUser@DestNode /absolute/file/path

DESCRIPTION

Receive is a relatively simple minded tool for receiving files. Default usage is to translate incoming EBCDIC PUNCH or PRINT records to ASCII, and output them with appended newlines. Trailing spaces may get removed at first, as they are (usually anyway) unnecessary. At the NETDATA receiving, no such stripping is done.

Receive can enter -d (debug) mode, and display the contents of the spool file. At that mode it will display symbolically NJE header contents, and also analyze NETDATA records. No output file is created in this mode.

Receive can control output conversion with several keys:

-b  Turns on enforced binary mode, which outputs the incoming file as is; NETDATA content is analyzed and output as is, and other PUNCH modes get also handled in raw manner. This is default mode for a class N NETDATA file, and must be explicitely turned off with -a.

-a  Turns on enforced EBCDIC-ASCII conversion, even when a NETDATA file has class N.

-rawpun
    Outputs nominal size record contents; usually 80 characters per record (PUNCH) without adding anything to the records, nor translating them.

-bcat
    outputs non-translated records in format: <char of reclen> <chars of record>

-asa
    Affects PRINT files which contain MCC carriage control codes (see bitspool(5)) by translating them to FORTRAN-style carriage control.

Receive outputs to a file whose location is current working directory, and in non-NETDATA -case the name is formed from spool entry by lowercasing FileName.FileExt, unless `-o', is used to override it. With `-o' one can specify `-' to denote STDOUT. In case the spool-file contains NETDATA, default filename is taken from inside the NETDATA INMR02 control records; The INMDSNAM contains (usually) three entries: and they get mapped into UNIX file as: In case the original file is from MVS TSO, and has INMMEMBR key defined, resulting UNIX filename is:

Debug output goes to STDERR as usual.

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.

OUTPUT FILE NAME MAPPING
User can explicitely define a name for the output file, or let the receive to invent on its own.

Default output name is formed from

When input processing reaches records to be output, the output file is opened.

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(8), ebcdictbl(5), mailify(8), sysin(8), qrdr(8), rdrlist(1)

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, Finland <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.