When the upload is complete, the screen will display the total bytes received and the…

June 24, 2002 1230 2002–25 I.R.B.

Press ENTER to continue. If you have more files to send for the same TCC/EIN, enter “y” ; otherwise, enter “n” .

It is your responsibility to check the acceptability of your file; therefore, be sure to dial back into the system in 1-2 business days.

At the Main Menu:

Enter “B” for file status. Press the Tab key to advance to TCC box; otherwise, enter “E” to exit. Enter your TCC : Enter your EIN : Enter “B” for the current year file results. Tab to the appropriate file and press ENTER .

If “Results” indicate:

“Good, Not Released” and you agree with the “Count of Payees”, you are finished with this file. The file will automatically be released in 10 calendar days unless you contact us within this timeframe.

“File Released” - File has been released to our mainline processing.

“File Bad” - Correct the errors and timely resubmit the file as a replacement.

“Not Yet Processed” - File has been received, but we do not have results available yet. Please check back in a few days.

When you are finished, enter “E” from the Main Menu to logoff. Enter “2” to hang-up.

Sec. 10. Modem Configuration

.01 Hardware features

(a) Enable hardware flow control (b) Enable modem error control (c) Enable modem compression

Sec. 11. Common Problems and Questions Associated with Electronic Filing

.01 Refer to Part A, Sec. 16, for common format errors associated with electronic/magnetic files. .02 The following are the major non-format errors associated with electronic filing:

1. Transmitter does not dial back to the electronic system to determine file acceptability.

The results of your file transfer are posted to the FIRE System within two business days. It is your responsibility to verify file acceptability and, if the file contains errors, you can get an online listing of the errors. Date received and number of payee records are also displayed. If the file is good, but you do not want the file processed, you must contact IRS/MCC within 10 days from the transmission of your file.

2. Incorrect file is not replaced timely.

If your file is bad, correct the file and timely resubmit as a replacement.

3. Transmitter compresses several files into one.

Only compress one file at a time. For example, if you have 10 uncompressed files to send, compress each file separately and send 10 separate compressed files.

4. Transmitter sends a file and File Status indicates that the file is good, but the transmitter wants to send a replacement or correction file to replace the original/correction/replacement file.

Once a file has been transmitted, you cannot send a replacement file unless File Status indicates the file is bad (1-2 business days after file was transmitted). If you do not want us to process the file, you must first contact us toll-free at 1–866–455–7438 to see if this is a possibility.

2002–25 I.R.B. 1231 June 24, 2002

5. Transmitter sends an original file that is good, then sends a correction file for the entire file even though there are only a few changes.

The correction file, containing the proper coding, should only contain the records requiring correction, not the entire file.

6. File is formatted as EBCDIC.

All files submitted electronically must be in standard ASCII code.

7. Transmitter has one TCC number, but is filing for multiple companies, which EIN should be used when logging into the system to send the file?

When sending the file electronically, you will need to enter the EIN of the company assigned to the TCC. When you upload the file, it will contain the EIN’s for the companies, for whom you are filing. This information will be passed forward.

8. Transmitter sent the wrong file, what should be done?

Call us as soon as possible toll-free at 1–866–455–7438, ext. 3 . We may be able to stop the file before it has been processed. Please do not send a replacement for a file that is marked as a good file.

.03 The following are the most common problems encountered when connecting with dial-up networking/web browser:

1. Transmitter is unable to connect to the FIRE System using dial-up networking.

• The user name and password should be blank when trying to connect unless it is needed by your system.

• Windows 95/98: Disable “enable software compression”

• Windows NT/2000: Disable both “enable software compression” and “enable PPP/LCP extensions”

• TCP/IP should be the only network protocol that is enabled.

(Make sure you are using analog lines rather than digital.)

2. Transmitter is connecting using dial-up networking, but is unable to bring up the URL address using the web browser.

• Proxy server should be disabled for a dial-up connection.

• “Using a modem” option should be selected.

• The home page should either display http://10.225.224.2 or be set to “about:blank” .

• The security level should be set at medium.

  • The option “enable software compression” should be disabled under Dial-Up Networking.

3. Transmitter clicks on “start the fire application”, but the logon screen is displayed again.

Your browser must be set to receive “cookies” .

4. Transmitter is getting a menu when connecting with dial-up networking.

The option “pop-up a terminal window” should be disabled.

5. Transmitter cannot find the browse button to upload file.

If using Internet Explorer, you must have version 4.0 or higher. If using Netscape Navigator, it must be version 2.0 or higher.

June 24, 2002 1232 2002–25 I.R.B.

6. The line is busy when dialed.

We have enough lines available that you should not get this message. Check the phone number being dialed. It should be 304– 262–2400 . If you need a number such as an 8 or a 9 to access an outside line, make sure it is present. Also, some companies require an access code for long distance dialing.

7. I am receiving the error message “Remote PPP Peer Not Responding” or receiving a 718 error with Windows 2000 or XP.

Disable “enable LCP Extensions” in Dial-Up Networking. (This is located in Dial-up Networking Properties, Networking, and Settings.)

.04 The following are the most common problems encountered when connecting with hyperterminal.

1. Transmitter is unable to connect using hyperterminal.

• If you need a number such as an 8 or a 9 to access an outside line, make sure it is present.

• Set the terminal emulation to VT100.

• Try lowering the modem speed.

• Turn the modem off and then back on to reset it.

(Make sure you are using analog lines rather than digital.)

2. Transmitter is getting the message “annex command line interpreter”.

Disconnect and try again. You may need to lower the modem speed if this happens several times in a row.

3. When trying to logon, the cursor is not in the correct box, or the menus are distorted.

The terminal emulation must be set to VT100. Also, verify that the data bits are set at 8, the stop bit is set at 1 and parity is set at None.

4. Transmitter was able to connect and the menu is displayed, but is unable to type anything.

Scroll lock cannot be turned on.

5. When transmitter connects, the menus keep scrolling and display garbage characters.

Make sure “Use error control” and “Compress data” are enabled under the Advanced Connection Settings.

6. Transmitter receives message “bad data packet” when the file is transmitting. What does this mean?

Your modem is having problems sending the data, so it is trying to resubmit it. Normally, if the transfer does not abort, the file will be sent successfully.

Part C. Magnetic Media Specifications

.01 Transmitters should be consistent in the use of recording codes and density on files. If the media does not meet these specifications, IRS/MCC will request a replacement file. Filers are encouraged to submit a test prior to submitting the actual file. Contact IRS/MCC for further information toll-free at 1–866–455–7438 . Transmitters should also check media for viruses before submitting it to IRS/MCC.

2002–25 I.R.B. 1233 June 24, 2002

Sec. 1. Tape Cartridge Specifications

.01 In most instances, IRS/MCC can process tape cartridges that meet the following specifications:

(a) Must be IBM 3480, 3490, 3490E, 3590, 3590E or AS400 compatible. (b) Must meet American National Standard Institute (ANSI) standards, and have the following characteristics:

(1) Tape cartridges will be ½-inch tape contained in plastic cartridges which are approximately 4-inches by 5-inches by

1-inch in dimension. (2) Magnetic tape will be chromium dioxide particle based ½-inch tape. (3) Cartridges must be 18-track, 36-track, 128-track or 256-track parallel ( See Note ). (4) Cartridges will contain 37,871 CPI, 75,742 CPI, or 3590 CPI (characters per inch). (5) Mode will be full function. (6) The data may be compressed using EDRC (Memorex) or IDRC (IBM) compression. (7) Either EBCDIC (Extended Binary Coded Decimal Interchange Code) or ASCII (American Standard Coded Information

Interchange) may be used. .02 The tape cartridge records defined in this Revenue Procedure may be blocked subject to the following:

(a) A block must not exceed 32,250 tape positions. (b) If the use of blocked records would result in a short block, all remaining positions of the block must be filled with 9s;

however, the last block of the file may be filled with 9s or truncated. Do not pad a block with blanks. (c) All records, except the header and trailer labels, may be blocked or unblocked. A record may not contain any control fields

or block descriptor fields which describe the length of the block or the logical records within the block. The number of logical records within a block (the blocking factor) must be constant in every block with the exception of the last block which may be shorter (see item (b) above). The block length must be evenly divisible by 750. (d) Records may not span blocks. .03 Tape cartridges may be labeled or unlabeled. .04 For the purposes of this Revenue Procedure, the following must be used:

Tape Mark: (a) Signifies the physical end of the recording on tape. (b) For even parity, use BCD configuration 001111 (8421). (c) May follow the header label and precede and/or follow the trailer label.