![](media/image1.png){width="4.1in" height="3.092361111111111in"}

**\[This page intentionally left blank.\]**

Table of Contents

1\. Introduction [1](#introduction)

1.1. Purpose [1](#purpose)

1.2. Scope [1](#scope)

2\. Overview of Process [2](#overview-of-process)

3\. Application File [3](#application-file)

3.1. File Naming Convention [3](#file-naming-convention)

3.1.1. Application File [3](#application-file-1)

3.1.2. Response File [3](#response-file)

3.2. File Format [3](#file-format)

3.3. Record Types [4](#record-types)

4\. Response File 9

4.1. File Format 9

4.2. Record Types 9

5\. Status and Error Codes 12

5.1. Status Codes 12

5.2. Error Codes 12

List of Tables

**VEC Session Data [4](#__RefHeading___Toc78882718)**

Application Data [5](#__RefHeading___Toc78882719)

Session Response 9

Application Response 10

Status Codes 12

Common Error Codes [12](#__RefHeading___Toc78882723)

**List of Figures**

Figure 1 - Order of Record Types in Application File
[4](#__RefHeading___Toc78882724)

Figure 2 - Sample VE Record [4](#__RefHeading___Toc78882725)

Figure 3 - Sample VA Record using FRN [6](#__RefHeading___Toc78882726)

Figure 4 - Sample VA Record using Social Security Number
[6](#__RefHeading___Toc78882727)

Figure 5 - Sample VA Record for Modification of a License
[7](#__RefHeading___Toc78882728)

Figure 6 - Order of Record Types in Response File 9

Figure 7 - Sample RS Record 10

Figure 8 - Sample RA Record Where Application Is Granted 10

Figure 9 - Sample RA Record For Application Filed on a Weekend 11

Figure 10 - Sample RA Record For Rejected Application 11

Figure 11 - Sample RA Record for Vanity Renewal 11

# Introduction

This document contains information that enables Amateur VECs to file
applications through an electronic batch means.

## Purpose 

The purpose of this document is detail the changes to the process that
will enable VECs to file Vanity renewals via batch.

## Scope

This document contains the information from the original document,
information about https as well as the changes to support vanity renewal
filings.

# Overview of Process

VECs send files containing information about examinations as well as
amateur applications. The files are transmitted to the Wireless
Telecommunications Bureau of the Federal Communications Commission using
https. The processing of these files entails entering information into
the Universal Licensing System (ULS). ULS creates a response file for
each data file received. The response file contains data informing the
VEC what happened when ULS processed each of the applications in the
data file. Each response file is emailed to the VEC using the email
address on file with ULS. VECs may indicate additional email addresses
that should also receive the response files. The response file is placed
on a Wireless https server to be picked up either manually or using any
one of a number of software packages available that enable a batch
process to execute https commands. https is used because it is a secure
transmission method.

The VEC is responsible for ensuring that each application file sent is
uniquely named and correctly formatted. A VEC can send multiple
application files per day. Files can be posted at any time of the day,
seven days a week. ULS processes application files received from VECs
every hour on the half-hour (i.e., 3:30 AM, 4:30 AM, 5:30 AM, etc.)
except when the ULS nightly batch process is running. On FCC business
days, ULS will autogrant each application that it can. If there is a
problem with an application, an appropriate error code will be returned
indicating to the VEC why the application was not granted. Application
files received on non-business days (i.e., weekends and federal
holidays) will be entered into ULS but not granted. The application is
not granted until the next business morning.

The first step ULS takes with each application file is to verify the
file format. If there is any problem with the format of the file, e.g.,
an unprintable character contained in the data, the file is not
processed. A response file is created with an appropriate error code
indicating the file could not be processed.

Assuming the format is acceptable; the file content is processed. When
ULS has finished processing the file, the response file is emailed to
the VEC and posted on the https server for pick up. The response file is
not be encrypted. The response file contains either positive
confirmation, including file number, FCC Registration Number (FRN),
status of the application and the call sign or appropriate error
messages.

# Application File 

One response file is created for each application file received.

## File Naming Convention

### Application File

The Application File being sent to the FCC must be uniquely named. In
order to ensure uniqueness, the file name should have the format
vmmddnn.dat where *v* is the VEC code, *mmdd* is the month and day the
file is sent and *nn* is a unique sequential number. The *mmdd* is not
used to determine the receipt date, it is simply a mechanism for naming
files, so if a file is created one day and sent on another, there is no
need to change the *mmdd*. The receipt date of the applications within
the file will be determined by the date and time the file is physically
received at the FCC, i.e., the date it is placed on the https server.
The *nn* is to allow a VEC to send more than one file on the same day,
for example, the first file could be 01, the second 02 and so on.
Regardless of what software the VEC uses to create this file, there is
probably a "SAVE AS" menu option or, if using a database, an EXPORT
command. In either case, choose the file type described as "MS DOS Text"
or "Text Only". If your software enables you to do so, change the file
type to "dat". If it does not allow this change, after the file is
saved, you can use Windows 3.1 File Manager, Windows Explorer or DOS
commands to rename it from *vmmddnn*.txt to vmmddnn.dat.

### Response File

The response file that the FCC returns has the same name as the file
received with a file extension of "rsp", i.e., *vmmddnn*.rsp, where *v*
is the VEC code, *mmdd* is the month and day the file is sent and *nn*
is a unique sequential number. This file can be opened by any software
that can open a file ending in "txt".

## File Format

The Application file is an ASCII file (DOS or Windows text file) with
variable length records containing only printable characters. The file
consists of two record types. The contents of each record type is
pipe-separated, i.e., there is a \"\|\" that separates each data field
in the record from the data field next to it. Each record type starts
with a unique two-character record type code. The length of each record
is dependent upon the actual data contents of the fields in that record.
The last data field of the record is not followed by a \"\|\".

The file must start with a VEC record (record type VE) which is followed
by one application data record (record type VA) for each application.

VE... identifies the VEC and will usually contain exam information

VA... contains first applicant's data

VA... contains second applicant's data

VA... contains third applicant's data that has an attachment

VA... contains fourth applicant's data

1.  []{#__RefHeading___Toc78882724 .anchor}Order of Record Types in
    Application File

If an applicant requests a waiver by answering yes to question #8 on
Form 605, the applicant must provide an attachment file to the VEC. That
attachment must be faxed to the Wireless Telecommunications Bureau is
Gettysburg, PA. Please write the applicant's FRN and file number or call
sign, if available, on the fax to identify it.

## Record Types

  ---------------------------------------------------------------------------------------------------
  []{#__RefHeading___Toc78882718                                           
  .anchor}VEC Session Data                                                 
  -------------------------------- -------------------------- ------------ --------------------------
  Position                         Data Element               Definition   Content

  1                                Record Type                char(2)      \"VE\"

  2                                VEC Code                   char(1)      

  3                                Session Date               date         mm/dd/yyyy

  4                                Exam Session City          char(20)     

  5                                Exam Session State         char(2)      

  6                                Number of Applicants       integer      
                                   Tested                                  

  7                                Number of Applicants That  integer      
                                   Passed                                  

  8                                Number of Applicants That  integer      
                                   Failed                                  

  9                                Number of Elements Passed  integer      

  10                               Number of Elements Failed  integer      
  ---------------------------------------------------------------------------------------------------

**VE\|L\|02/28/1999\|WOODSFIELD\|OH\|1\|1\|3\|3\|3**

2.  []{#__RefHeading___Toc78882725 .anchor}Sample VE Record

+------+-------------------------+----------+-------------------+----+
| []   |                         |          |                   |    |
| {#__ |                         |          |                   |    |
| RefH |                         |          |                   |    |
| eadi |                         |          |                   |    |
| ng__ |                         |          |                   |    |
| _Toc |                         |          |                   |    |
| 7888 |                         |          |                   |    |
| 2719 |                         |          |                   |    |
| .an  |                         |          |                   |    |
| chor |                         |          |                   |    |
| }App |                         |          |                   |    |
| lica |                         |          |                   |    |
| tion |                         |          |                   |    |
| Data |                         |          |                   |    |
+======+=========================+==========+===================+====+
| Posi | Data Element            | De       | Content           |    |
| tion |                         | finition |                   |    |
+------+-------------------------+----------+-------------------+----+
| 1    | Record Type             | char(2)  | \"VA\"            |    |
+------+-------------------------+----------+-------------------+----+
| 2    | Pending File Number for | char(14) | Form 605 box 4    |    |
|      | Withdrawals or          |          |                   |    |
|      | Amendments              |          |                   |    |
+------+-------------------------+----------+-------------------+----+
| 3    | Call Sign               | char(6)  | Form 605 box 5    |    |
+------+-------------------------+----------+-------------------+----+
| 4    | Social Security Number  | char(9)  | Form 605 box 9a   |    |
|      | (or Licensee ID)\*      |          |                   |    |
|      |                         |          | If sending FRN in |    |
|      |                         |          | Position 31,      |    |
|      |                         |          | ***do not*** send |    |
|      |                         |          | SSN               |    |
+------+-------------------------+----------+-------------------+----+
| 5    | Entity Name (e.g.,      | varc     | Form 605 box 12   |    |
|      | club, military rec, and | har(200) |                   |    |
|      | races)                  |          |                   |    |
+------+-------------------------+----------+-------------------+----+
| 6    | First Name              | char(20) | Form 605 box 11   |    |
+------+-------------------------+----------+-------------------+----+
| 7    | MI Name                 | char(1)  | Form 605 box 11   |    |
+------+-------------------------+----------+-------------------+----+
| 8    | Last Name               | char(20) | Form 605 box 11   |    |
+------+-------------------------+----------+-------------------+----+
| 9    | Name Suffix             | char(3)  | Form 605 box 11   |    |
+------+-------------------------+----------+-------------------+----+
| 10   | Attention To            | char(35) | Form 605 box 14   |    |
+------+-------------------------+----------+-------------------+----+
| 11   | Street Address          | char(60) | Form 605 box 16   |    |
+------+-------------------------+----------+-------------------+----+
| 12   | PO Box                  | char(20) | Form 605 box 15   |    |
+------+-------------------------+----------+-------------------+----+
| 13   | City                    | char(20) | Form 605 box 17   |    |
+------+-------------------------+----------+-------------------+----+
| 14   | State                   | char(2)  | Form 605 box 18   |    |
+------+-------------------------+----------+-------------------+----+
| 15   | Zip Code                | char(9)  | Form 605 box 19   |    |
+------+-------------------------+----------+-------------------+----+
| 16   | Telephone Number        | char(10) | Form 605 box 21   |    |
+------+-------------------------+----------+-------------------+----+
| 17   | Fax Number              | char(10) | Form 605 box 22   |    |
+------+-------------------------+----------+-------------------+----+
| 18   | Email Address           | char(50) | Form 605 box 23   |    |
+------+-------------------------+----------+-------------------+----+
| 19   | Application Purpose     | char(2)  | Form 605 box 2    |    |
|      | Code                    |          |                   |    |
+------+-------------------------+----------+-------------------+----+
| 20   | Operator Class          | char(1)  | [Defini           | [C |
|      |                         |          | tion]{.underline} | od |
|      |                         |          |                   | e] |
|      |                         |          | Technician        | {. |
|      |                         |          |                   | un |
|      |                         |          | General           | de |
|      |                         |          |                   | rl |
|      |                         |          | Extra             | in |
|      |                         |          |                   | e} |
|      |                         |          |                   |    |
|      |                         |          |                   | T  |
|      |                         |          |                   |    |
|      |                         |          |                   | G  |
|      |                         |          |                   |    |
|      |                         |          |                   | E  |
+------+-------------------------+----------+-------------------+----+
| 21   | Valid Signature         | char(1)  | Y/N; based on     |    |
|      |                         |          | content of Form   |    |
|      |                         |          | 605 Schedule D    |    |
|      |                         |          | Signature block   |    |
+------+-------------------------+----------+-------------------+----+
| 22   | Physician Certification | char(1)  | Y/N; based on     |    |
|      |                         |          | content of Form   |    |
|      |                         |          | 605               |    |
+------+-------------------------+----------+-------------------+----+
| 23   | Requested Expiration    | mmdd     | Form 605 box 6    |    |
|      | date                    |          |                   |    |
+------+-------------------------+----------+-------------------+----+
| 24   | Waiver Request          | char(1)  | Form 605 box 7    |    |
+------+-------------------------+----------+-------------------+----+
| 25   | Attachments             | char(1)  | Form 605 box 8    |    |
+------+-------------------------+----------+-------------------+----+
| 26   | Attachment File Name    | char(12) | *Do Not Use*      |    |
+------+-------------------------+----------+-------------------+----+
| 27   | Attachment to be Faxed  | char(1)  | Y/N; send "Y" if  |    |
|      |                         |          | there is an       |    |
|      |                         |          | attachment is to  |    |
|      |                         |          | be faxed          |    |
+------+-------------------------+----------+-------------------+----+
| 28   | Change Call Sign        | char(1)  | Form 605 Sched D  |    |
|      | Systematically?         |          | box 1             |    |
+------+-------------------------+----------+-------------------+----+
| 29   | Trustee/Custodian Call  | char(10) | only send if a    |    |
|      | Sign                    |          | club, etc.; no    |    |
|      |                         |          | corresponding     |    |
|      |                         |          | form location     |    |
+------+-------------------------+----------+-------------------+----+
| 30   | Applicant Type          | char(1)  | [Defini           | [C |
|      |                         |          | tion]{.underline} | od |
|      |                         |          |                   | e] |
|      |                         |          | Individual        | {. |
|      |                         |          |                   | un |
|      |                         |          | Races             | de |
|      |                         |          |                   | rl |
|      |                         |          | Amateur Club      | in |
|      |                         |          |                   | e} |
|      |                         |          | Military          |    |
|      |                         |          | Recreation        | I  |
|      |                         |          |                   |    |
|      |                         |          |                   | R  |
|      |                         |          |                   |    |
|      |                         |          |                   | B  |
|      |                         |          |                   |    |
|      |                         |          |                   | M  |
+------+-------------------------+----------+-------------------+----+
| 31   | FCC Registration Number | numeric  | Form 605 box 9c   |    |
|      | (FRN)                   | (10,0)   |                   |    |
|      |                         |          | ***Note:*** value |    |
|      |                         |          | must be a valid   |    |
|      |                         |          | FRN in CORES; the |    |
|      |                         |          | FRN must be 10    |    |
|      |                         |          | digits, use       |    |
|      |                         |          | leading zeroes if |    |
|      |                         |          | necessary         |    |
+------+-------------------------+----------+-------------------+----+
| 32   | Date of Birth           | datetime | Form 605 box 11a  |    |
|      |                         |          |                   |    |
|      |                         |          | mm/dd/yyyy        |    |
+------+-------------------------+----------+-------------------+----+
| 33   | **\***Licensee Name     | char(1)  | If the licensee   |    |
|      | Change                  |          | name in position  |    |
|      |                         |          | 5 or 6-9 is       |    |
|      |                         |          | different than    |    |
|      |                         |          | what is on the    |    |
|      |                         |          | license, this     |    |
|      |                         |          | field must be     |    |
|      |                         |          | sent as N.        |    |
|      |                         |          |                   |    |
|      |                         |          | If you are not    |    |
|      |                         |          | changing the      |    |
|      |                         |          | name, send this   |    |
|      |                         |          | as Null.          |    |
|      |                         |          |                   |    |
|      |                         |          | **F**orm 605 box  |    |
|      |                         |          | 13                |    |
+------+-------------------------+----------+-------------------+----+
| 34   | Personal Security       | va       | [Defini           | [C |
|      | Question Code           | rchar(4) | tion]{.underline} | od |
|      |                         |          |                   | e] |
|      |                         |          | Custom PSQ        | {. |
|      |                         |          |                   | un |
|      |                         |          | Original City of  | de |
|      |                         |          | Birth             | rl |
|      |                         |          |                   | in |
|      |                         |          | Pet's Name        | e} |
|      |                         |          |                   |    |
|      |                         |          | Corp Internal     | 1  |
|      |                         |          | Employee ID       |    |
|      |                         |          |                   | 2  |
|      |                         |          | Mother's Maiden   |    |
|      |                         |          | Name              | 3  |
|      |                         |          |                   |    |
|      |                         |          |                   | 4  |
|      |                         |          |                   |    |
|      |                         |          |                   | 5  |
+------+-------------------------+----------+-------------------+----+
| 35   | Custom Personal         | var      | If the applicant  |    |
|      | Security Question       | char(60) | chooses to use a  |    |
|      |                         |          | custom security   |    |
|      |                         |          | question, it will |    |
|      |                         |          | be sent in this   |    |
|      |                         |          | position.         |    |
+------+-------------------------+----------+-------------------+----+
| 36   | PSQ Answer              | var      | The answer to the |    |
|      |                         | char(60) | applicant's       |    |
|      |                         |          | security question |    |
|      |                         |          | will be sent in   |    |
|      |                         |          | this position.    |    |
+------+-------------------------+----------+-------------------+----+

**\* Note: In ULS, a name change indicates a sale (or transfer of
control) of the license(s) to another party and for which proper
Commission approval has not been received or proper notification not
provided and that is what this field is used for. This is why this field
is sent as N. For example, a name change due to marriage does not meet
this criteria.**

**VA\|\|\|\|\|William\|A\|Brown\|II\|\|5 Main
Street\|\|Hartford\|CT\|06335\
[\|0000000000\|\|billb@mynet.com\|NE\|N\|Y\|N\|\|\|N\|\|\|\|I\|0004283453\|10/06/1969\|\|1\|Favorite](mailto:|0000000000||billb@mynet.com|NE|N|Y|N|||N||||I|0004283453|10/06/1969||1|Favorite)
Color\|Blue**

3.  []{#__RefHeading___Toc78882726 .anchor}Sample VA Record using FRN
    and choosing a custom personal security question

**VA\|\|\|923121234\|\|Mary\|J\|Marks\|II\|\|128 Main
St\|\|Annapolis\|MD\|21401\|4105551212\|\|mmarks@hereintown.net\|NE\|N\|Y\|N\|\|\|N\|\|\|\|I\|\|12/15/1957\|\|2\|\|Arlington**

4.  []{#__RefHeading___Toc78882727 .anchor}Sample VA Record using Social
    Security Number and security question 2

**VA\|\|WB4TZP\|\|\|Mary\|\|Brown\|\| \|100 Peachtree Way\|\|Atlanta\|\
GA\|88427\|4041231234\|4041211212\|\|MD\|G\|Y\|N\|\|N\|Y\|\|N\|\
\|I\|0003569855\|\|N\|3\|\|Spot**

5.  []{#__RefHeading___Toc78882728 .anchor}Sample VA Record for
    Modification of a License with a Name Change and security question 3

In the above example, Mary White holds license WB4TZP. Mary got married
and changed her name to Mary Brown. Even though she changed her name,
position 33, Licensee Name Change, is sent as an N. The rule is if there
is no name change to send the field as null. If there is a name change
the rule is to send it as an N. Never send it as a Y.

Mary also selected security question 3 to use in the event that she
forgets her password. In the event that she forgets her password she
will be prompted with question 3 'What is your pet's name'. If she
answers the recorded answer of Spot Mary will be able to continue with
the login process.

If an applicant does not want to provide a social security number to the
VEC, the applicant is responsible for registering with the Commission
Registration System (CORES) prior to filing in order to be assigned an
FCC Registration Number (FRN). To register, the applicant should go to
http://www.fcc.gov and click on the link labeled "Commission
Registration System".

# Response File

## File Format

The Response File is an ASCII file (DOS or Windows text file) with
variable length records containing only printable characters. The file
consists of two record types. The contents of each record type is
pipe-separated, i.e., there is a \"\|\" that separates each data field
in the record from the data field next to it. Each record type starts
with a unique two-character record type code. The length of each record
is dependent upon the actual data contents of the fields in that record.
The last data field of the record is not followed by a \"\|\".

The file always starts with an RS record. (If ULS could not process the
file at all, then the response file will only contain an RS record.)
Following the RS record will be one RA record per application received.

RS... contains exam information to identify the contents

RA... status of first application

RA... status of second application

RA... status of third application

6.  Order of Record Types in Response File

## Record Types

The response file comprises two record types, the Session Response and
the Application Response. The Session Response is always the first
record in the file.

  -----------------------------------------------------------------------------
  Session                                            
  Response                                           
  ---------- -------------------------- ------------ --------------------------
  Position   Data Element               Definition   Content

  1          Record Type                char(2)      \"RS\"

  2          VEC Code                   char(1)      From the Application File

  3          Session Date               date         mm/dd/yyyy

  4          Exam Session City          char(20)     From the Application File

  5          Exam Session State         char(2)      From the Application File

  6          File Status                integer      Indicates if the file was
                                                     successfully processed. If
                                                     there is a problem this
                                                     field will contain an
                                                     appropriate error code.
  -----------------------------------------------------------------------------

**RS\|L\|02/28/1999\|WOODSFIELD\|OH\|0**

7.  Sample RS Record

  -------------------------------------------------------------------------------
  Application                                           
  Response                                              
  ------------- -------------------------- ------------ -------------------------
  Position      Data Element               Definition   Content

  1             Record Type                char (2)     \"RA\"

  2             ULS File Number            char (14)    Assigned by ULS if status
                                                        code is 0 (zero), G, D,
                                                        R, 1, or 2

  3             Applicant First Name       varchar (20) 

  4             Applicant Middle Initial   char (1)     

  5             Applicant Last Name        varchar (20) 

  6             Applicant Suffix           char (3)     

  7             Applicant Zip Code         char (9)     

  8             Call Sign                  char (6)     

  9             Operator Class Code        char (1)     

  10            FRN                        numeric      
                                           (10,0)       

  11            Status Code                char (5)     Indicates that the
                                                        application was accepted
                                                        for filing (0), the
                                                        processing status of the
                                                        application (G, D, R, 1,
                                                        or 2) or the error that
                                                        kept the application from
                                                        being accepted for
                                                        filing.

  12            Payment Type Code          char(4)      

  13            Quantity                   integer      

  14            Fee Amount                 money        
  -------------------------------------------------------------------------------

**RA\|0000162008\|JOHN\|Q\|PUBLIC\|JR\|21532\|WZ6ZAA\|T\|\
000123546\|G\|\|\|**

8.  Sample RA Record Where Application Is Granted

**RA\|0000162009\|JANE\|\|DOE\|\|21403\|\|E\|000123547\|0\|\|\|**

9.  Sample RA Record For Application Filed on a Weekend

**RA\|\|Arnold\|A\|Andrews\|\|78729\|KA2FXE\|\|\|9840\|\|\|**

10. Sample RA Record For Rejected Application

**RA\|\|John\|\|Doe\|\|22030\|KN2REB\|\|\|2\|WAVR\|1\|16.30**

11. Sample RA Record for Vanity Renewal

# Status and Error Codes

## Status Codes

Assuming the file format has the correct file format and therefore could
be processed, there is at least one "RA" record per "VA" record
received. For application files received on FCC business days, if the
application data on the "VA" record is complete, a "G" is returned to
indicate that the application was received and granted. The call sign is
also returned in the response file. For application files received on
weekends and holidays, if the application data on the "VA" record is
complete, a zero is returned to indicate that the application was
created and is accepted for filing, i.e., has been entered into ULS but
is not yet processed. These applications are processed the morning of
the next business day. If the application is accepted for filing, it can
be downloaded in the daily Amateur data file from
ftp://ftp.fcc.gov/pub/Bureaus/Wireless/Databases/uls/daily/ or
http://wireless.fcc.gov/cgi-bin/wtb-transactions.pl. It is also
available in the following weekend's complete database download file
from ftp://ftp.fcc.gov/pub/Bureaus/Wireless/Databases/uls/complete/ or
<http://wireless.fcc.gov/cgi-bin/wtb-datadump.pl>. It can also be
accessed online using ULS Application Search to check its status. If it
has been granted, it can be accessed online using ULS License Search.

  -------------- --------------------------------------------------------
  Status Codes   

  Status Code    Meaning

  G              The application was granted.

  R              The application was created but was returned to the
                 applicant.

  D              The application was created and dismissed by ULS.

  W              The application was successfully withdrawn.

  0              The application was filed on a non-business day (weekend
                 or federal holiday). The application will be processed
                 on the next business day.

  2              The application is waiting for the Vanity renewal fee to
                 be paid or it was offlined for processing by staff.
  -------------- --------------------------------------------------------

## Error Codes

***Note:*** Refer to web site
http://www.fcc.gov/wtb/uls/ebf/errcodes.txt for a current list of error
codes and their meanings. This file is updated daily.

The following table contains some of the more common error codes
returned.

  -------------------------------- ----------------------------------------------------------------
  []{#__RefHeading___Toc78882723   
  .anchor}Common Error Codes       

  Error Code                       **Description**

  9505                             Applicant already has one Amateur license.

  9605                             Trustee call sign invalid.

  9740                             Untimely renewal

  9750                             Invalid format for EBF file. ULS did not process

  10675                            FRN is invalid

  10895                            Provide one and only one of the following: FRN, TIN/SGIN, or
                                   Licensee ID/SGIN.

  11835                            TIN registered to multiple FRNs in CORES. Please file again
                                   using FRN.
  -------------------------------- ----------------------------------------------------------------