Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| howto:freq [2021/03/19 10:10] – remove some blarg wkitty42 | howto:freq [2021/03/19 10:24] – a little refinement wkitty42 | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| This page describes how to create a FTN style FREQ (FileREQ) and send it to a destination system. There are at least two methods this can be done with. Currently we will describe only one of those methods. | This page describes how to create a FTN style FREQ (FileREQ) and send it to a destination system. There are at least two methods this can be done with. Currently we will describe only one of those methods. | ||
| - | The first step is to create a .req file. This file contains the filenames of the files you are requesting, one filename per line. | + | The first step is to create a .req (REQuest) |
| eg:< | eg:< | ||
| echo anotherfile.bar >> / | echo anotherfile.bar >> / | ||
| - | Now that we have the filenames in a .req file, we want to send it to a destination system. One way this is done is to add myfreq.req to a .FLO file. This requires some understanding of how BSO (Binkley Style Outbound) works so we can determine the proper FLO file name of the destination system. Basically, the zone is determined by the outbound directory in your BSO tree. The outbound directory for your default zone has no extension. The extensions on your other outbound directories are zero padded to three HEX characters. The net and node of the destination are zero-padded HEX to four places. | + | Now that we have the filenames in a .req file, we want to send it to a destination system. One way this is done is to add myfreq.req to a .FLO file. This requires some understanding of how BSO (Binkley Style Outbound) works so we can determine the proper FLO file name of the destination system. Basically, the zone is determined by the outbound directory in your BSO tree. The outbound directory for your default zone has no extension. The extensions on your other outbound directories are zero-padded |
| eg: 1:3634/12 breaks down like this. | eg: 1:3634/12 breaks down like this. | ||
| Line 25: | Line 25: | ||
| < | < | ||
| - | The '^' (caret) tells your BSO mailer | + | Let's say we want to send a FREQ to a system in Micronet. Micronet is zone 618. In HEX that is 26a so the outbound would be outbound.26a. So, a request to 618:3634/12 would look like this. |
| - | When your BSO mailer scans its outbound directories and sees the file 0e32000c.flo, | + | < |
| - | If the destination system is in another zone, then the outbound directory for that zone has an extension like we show above where outbound.001 is the outbound for zone 1 if you are not in zone 1. Let's say we want to send a FREQ to a system in Micronet. Micronet is zone 618. In HEX that is 26a so the outbound would be outbound.26a. | + | When your BSO mailer scans its outbound directories and sees the file 0e32000c.flo, it will attempt to connect to 1:3634/12 and deliver |
| - | So, a request to 618:3634/12 would look like this. | ||
| - | < | + | NOTES: |
| + | The '^' (caret) tells your BSO mailer to delete the req file after it has been sent. More details about FLO file formatting are available in the original Binkleyterm Mailer documentation. | ||
| - | NOTE: In the above you will note that we used the ">>" | + | In the above you will note that we used the ">>" |
| ===== See Also ===== | ===== See Also ===== | ||
