Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
howto:freq [2021/03/19 10:08] – move the line describing the caret wkitty42 | howto:freq [2021/03/19 10:19] – a little more clearer by grouping examples better 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 ' | + | 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, | + | |
- | + | ||
- | 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 and since the extensions in BSO are limited to three charcters, | + | |
So, a request to 618:3634/12 would look like this. | So, a request to 618:3634/12 would look like this. | ||
< | < | ||
+ | |||
+ | The ' | ||
+ | |||
+ | When your BSO mailer scans its outbound directories and sees the file 0e32000c.flo, | ||
NOTE: In the above you will note that we used the ">>" | NOTE: In the above you will note that we used the ">>" |