|
|
NTS BATCH FILE TRANSFER (NTS Class Radiograms via WL2K) |
Contents of this page:
1. TRANSPORT OF NTS RADIOGRAMS USING WL2K
3. EXAMPLES OF EMAILS CONTAINING NTS MESSAGE TRAFFIC
EXAMPLE BATCH FILE ATTACHED TO AN EMAIL
EXAMPLE BATCH FILE IN THE EMAIL TEXT
4. EXPORTING AND IMPORTING BATCH FILES - WINLINK CLASSIC
5. STATION-TO-STATION TRANSFERS - AIRMAIL
1. TRANSPORT OF NTS RADIOGRAMS USING WL2K
|
The WL2K system is an email transport system, not a BBS or MBO (mailbox) type system. WL2K used very much the same way the internet is used for sending and receiving email.
MANUAL MESSAGING ISSUESMessages without WL2K or internet addresses and in the standard ARRL Radiogram format (NTS class messages, MPG-1, PSCM Appendix B) need to be handled by NTS or NTSD stations and ultimately delivered manually by outlet stations at local levels. Automatic routing of such messages is always limited by the uncertainty of knowing exactly which stations can deliver a given message in a local calling area at a given hour. Section and local manual nets are often used to hand off such messages for local delivery by experienced operators. Packet keyboarders may also selectively download messages from MBOs for delivery. The issues involved in this entire process may be summarized as follows: · Originators need to get outbound NTS radiograms into the hands of the NTS/NTSD for movement around the country. Within the “last mile” disaster area this needs to be done without encumbering local limited manpower or nets. · NTS/NTSD stations need to route volumes of this traffic as quickly as possible into all delivery areas within Sections nationally. · Sections need to distribute or post messages within “reach” of local nets and experienced operators for delivery. Stations within the “last mile” disaster area also need to be able to receive large volumes of incoming welfare inquiries to be processed by sheltering agencies, or delivered with replies, and handled without encumbering local limited manpower or nets.
WL2K comes into play by providing a real-time network capability to move radio-email carrying NTS radiograms automatically in all three cases above. Thus large volumes of traffic may be transported via WL2K radio-email from originators and to outlets within minutes anywhere in the country. No intermediate amateur relaying manpower is required for reaching properly equipped outlets or MBOs directly. NTSD MBO operators will be able to manually post received messages for download with minimal effort.
BATCH FILESTo provide a simple way to carry NTS radiograms by email the Batch File Format has been adopted from the Winlink Classic MBO software used by many NTSD stations. A Batch File is simply a text file containing one or more NTS radiograms each with an added two line header and ending line. A Batch File can be easily created and read in any text editor such as Notepad™, and any ARES® operator in the field with WL2K will have this capability. A Batch File therefore is simply an envelope full of radiograms carried by an email addressed to a designated target on the WL2K network or public internet.
|
2. THE BATCH FILE FORMAT
|
The format for creating a batch file of NTS radiograms which may be imported into Winlink Classic MBO software is as follows (this is the batch format exported from Winlink Classic and the format which may also be used by ARES® or NTS stations to originate batch files with text editors at shelters in the field):
|
|
|
|
ST [zip] @ NTS[st] < [station of origin] [town] [area code] [prefix] (blank line for readability optional) [preamble] [address] BT [text] BT [sig] (blank line for readability optional) /EX |
|
· The first line of the message frame, and the file, is the standard NTSD BBS “To” line entry beginning with “ST [zip] @ NTS[st]”, where [zip] is the addressee’s zip code and [st] is the addressee’s state two letter abbreviation. The “< [station of origin]” entry indicates the source of the message. A space follows ST. A space may follow [zip] and @ for readability. The NTS[st] must be one group, as in NTSCO or NTSMD. · The second line is “[town] [area code] [prefix].” The prefix is often omitted in the NTS but can be very useful in Sections with large numbers of prefixes, some toll free and others not, for downloading stations to consider. (This line is sometimes introduced with “QTC” but this is not required for this export/import format.) · The Preamble, Address, Text and Signature are in the standard ARRL radiogram format (MPG-1, PSCM Appendix B). Booking is not permitted without special permission. Create Batch Files with individual messages only. · The Text is framed by the break (BT) on a separate line each. · The message ends with the “/EX” entry on the last line by itself.
|
|
3. EXAMPLES OF EMAILS CONTAINING NTS MESSAGE TRAFFIC
ADDRESSING THE EMAIL
To: Address the Batch File email to a designated NTS/NTSD station, MBO or outlet station using a call sign address, Tactical Address (Paclink only), or internet address, as in: [call sign]@winlink.org, or [name]@domain.ext.
Cc: You may include a copy to your home email address or to another station so long as that station knows not to duplicate handling of the attached NTS traffic.
Subj: The subject line may contain information to make it easy for the recipient to know the content without preview or opening the email. ·
For an email containing more than one message (2 - the number
of messages): ·
For an email containing only one message: · The “Please HXC this email” is optional to request that the email addressee confirm receipt of the NTS traffic email. Any HXC or HXD or HXE requests for the ARRL Radiograms are contained within the respective Preambles and ARL SEVEN requests are placed within the Texts.
A given Batch File should contain messages of only one Precedence. In the Subject line R for Routine is omitted. P and W are used for Priority and Welfare. Booked messages are not permitted in Batch Files without special permission from the receiving station. Create Batch Files with complete individual messages only. This is to ensure compatibility with Winlink Classic Message Manager importing and posting. If a Batch File is addressed directly to a delivering or forwarding station not using Classic or willing to reformat the file then booking may be used with permission.
|
EXAMPLE BATCH FILE ATTACHED TO AN EMAIL
|
To: |
kw1u@winlink.org |
Post via: |
WL2K |
|
|
Cc: |
|
|||
|
Subj: |
NTS TRAFFIC 2. Please HXC this email. |
|||
|
Two NTS messages attached: N3QA and Baltimore, MD
|
||||
|
k6yr.txt |
|
|||
|
(ATTACHMENT: k6yr.txt - Text Batch File from disk attached to the email. Numerous radiograms may be included. The file may be created and read in any text editor such as Notepad™, or it may be exported from the NTSD Winlink Classic MBO Message Manager.) |
|
ST 21201 @ NTSMD |
(SEND TFC)* |
|
BALTIMORE 410 555 |
(SUBJECT) |
|
|
(Optional blank line.) |
|
78 R WA1QAA 15 ELLICOTT CITY MD SEP 20 |
(MSG 2) |
|
BACI EOC BALTIMORE MD 21201 410 555 1212 |
|
|
BT |
(TEXT FRAME) |
|
TWELVE SUPPORT TEAMS IN ROUTE TO YOUR EOC X DO YOU HAVE EMERGENCY POWER QUERY |
|
|
BT |
(TEXT FRAME) |
|
MIKE WA1QAA MDC SEC |
|
|
|
(Optional blank line.) |
|
/EX |
|
|
ST N3QA |
(SEND TFC)** |
|
QTC N3QA |
(SUBJECT) |
|
|
(Optional blank line.) |
|
2403 R KJ3E 18 CALIFORNIA MD AUG 24 |
(MSG 1) |
|
CAL N3QA |
(known MBO user) |
|
BT |
(TEXT FRAME) |
|
HAL HF MODEM ARRIVED THIS AFTERNOON X LOOKS GOOD X TAKING MY TIME SETTING IT UP X 73 |
|
|
BT |
(TEXT FRAME) |
|
AL KJ3E |
|
|
|
(Optional blank line.) |
|
/EX |
(END MSG) |
|
* Station call sign addressee known to the posting MBO shown for example. ** Next “ST” must follow last “/EX” immediately with no blank line (mandatory). This Batch File format may be imported into Winlink Classic. |
EXAMPLE BATCH FILE IN THE EMAIL TEXT
|
To: |
kw1u@winlink.org |
Post via: |
WL2K |
|
|
Cc: |
|
|||
|
Subj: |
NTS TRAFFIC 21201@NTSMD. Please HXC this email. |
|||
|
ST 21201 @ NTSMD |
(SEND TFC)* |
|||
|
BALTIMORE 410 555 |
(SUBJECT) |
|||
|
|
(Optional blank line.) |
|||
|
78 R WA1QAA 15 ELLICOTT CITY MD SEP 20 |
(MSG 2) |
|||
|
BACI EOC BALTIMORE MD 21201 410 555 1212 |
|
|||
|
BT |
(TEXT FRAME) |
|||
|
TWELVE SUPPORT TEAMS IN ROUTE TO YOUR EOC X DO YOU HAVE EMERGENCY POWER QUERY |
|
|||
|
BT |
(TEXT FRAME) |
|||
|
MIKE WA1QAA MDC SEC |
|
|||
|
|
(Optional blank line.) |
|||
|
/EX |
(END MSG) |
|||
|
* The message format is compatible with the NTSD Winlink Classic MBO software. This message may be copied from the text to Notepad™ and saved to disk for direct importing into the Winlink Classic Message Manager. It saves steps to attach even the single radiogram to the email as a Batch File. The attached file can be saved directly to disk as an option when opening the attachment. |
4. EXPORTING AND IMPORTING BATCH FILES - WINLINK CLASSIC
|
Any station may create a Batch File of NTS Radiograms, attach the file to a WL2K email, and send the email to an NTSD MBO or outlet station. The MBO operator using the Winlink Classic software may open the email, save the attached Batch File to disk, and then import the Batch File into the Classic Message Manager. Messages posted on the MBO may be downloaded by connecting stations, sorted for forwarding, or sorted and exported to be sent via WL2K to any other station.
Exporting-Importing-Winlink Classic.
An expanded version with screen images is presented on the following page.
Batch Files for importing may also be transferred using the AirMail station-to-station and relay capabilities presented in the next section. |
5. STATION-TO-STATION TRANSFERS - AIRMAIL
|
The WL2K AirMail client software permits sending an email directly to any other AirMail client via packet radio or HF Pactor. The transfer of the properly addressed email takes place automatically when one station connects to the other using the terminal window.
These two features permit AirMail client users to move messages in full email format, perhaps including Batch Files of NTS traffic, station-to-station, radio-all-the-way, using packet or HF. Thus ARES®/NTS/NTSD stations equipped with AirMail and appropriate radios can move fully formatted email traffic anywhere in the country independent of the infrastructure. This is a major step ahead for the ARES®/NTS/NTSD national networking system.
Instructions and examples for the station-to-station, relay and re-filing methods are explained on the following page: AirMail Station-to-Station Transfers
|
_____________________________________
Page last updated JUN 20, 2006
ARES® is a registered trademark of the ARRL.
Notepad and
operating system references are trademarks of the Microsoft Corp.
W3YVQ, DEC 27, 2004