Employment and Training Data Validation for WIA Title 1B, Wagner-Peyser, and TAA Programs

Workforce Innovation and Opportunity Act Joint Quarterly Narrative Progress Report

DRVS LX Users Guide

Employment and Training Data Validation for WIA Title 1B, Wagner-Peyser, and TAA Programs

OMB: 1205-0448

⚠️ Notice: This form may be outdated. More recent filings and information on OMB 1205-0448 can be found here:

Document [pdf]

Download: pdf | pdf

Labor Exchange
DRVS Software
Version 6.3
User’s Guide
November 2006

Table of Contents
I.

OVERVIEW ................................................................................................. 3
A. Structure of User Guide.......................................................................... 3
B. List of Data Directories .......................................................................... 4

II.

INSTALLATION ......................................................................................... 5

III. TUTORIAL................................................................................................. 18
A.
B.
C.
D.
E.
F.

Signing In ............................................................................................. 20
Preparing and Importing Records......................................................... 26
ETA 9002 and VETS 200 Reporting.................................................... 42
Report Validation ................................................................................. 50
Data Element Validation ..................................................................... 56
Database Management.......................................................................... 63

IV. REFERENCE GUIDE ................................................................................ 69
A.
B.
C.
D.
E.
F.
G.
H.

File Menu.............................................................................................. 69
Import Menu......................................................................................... 70
Reporting Options Menu ...................................................................... 71
Report Validation Menu ....................................................................... 71
Data Element Validation Menu ............................................................ 73
Admin Menu......................................................................................... 73
Utilities Menu....................................................................................... 74
Help Menu ............................................................................................ 74

APPENDIX A. REPORTING SCHEDULE.............................................. 75
APPENDIX B. JOB SEEKER RECORD LAYOUT AND EDITS .......... 79
APPENDIX C. JOB OPENING RECORD LAYOUT AND EDITS ........ 89
APPENDIX D. PERFORMANCE GROUPS............................................ 91
APPENDIX E. CLIENT SERVER SETUP............................................... 94
APPENDIX F. TROUBLESHOOTING.................................................. 100

I. OVERVIEW
A. Structure of User Guide
The purpose of this User’s Guide is to guide states through the process of using the
ETA Data Reporting and Validation System (DRVS) to produce and validate the
Labor Exchange (LX) 9002 and VETS 200 quarterly reports. The DRVS
incorporates ETA’s common measures reporting requirements as specified in
TEGL 28-04 and approved under OMB Control Number 1205-0420. The DRVS
covers both LX and Workforce Investment Act (WIA) reporting as specified in
these guidance documents. This User’s Guide contains the following sections:
II. Installation: Provides a step-by-step description of how to install the software
on your PC or in a limited client/server setup, for both MSDE and SQL Server
users. Also includes instructions for logging on.
III. Tutorial: Provides information on the menus and functions of the software.
Describes how to build job seeker and job opening extract files, import data,
generate 9002 and VETS 200 quarterly reports, and export those reports into
formatted files that can be uploaded to ETA’s Labor Exchange Reporting System
(LERS). Describes how to conduct report validation and data element validation.
Also describes the DRVS database management functions.
IV. Reference Guide: Provides a condensed list of all the menus and functions
for quick reference.
Appendix A. Reporting Schedule: Provides the quarterly report due dates and
the participant and exiter cohorts to be included on each quarterly report.
Appendix B. Job Seeker Record Layout: Provides the record layout for the job
seeker extract file. The record layout provides field level and cross field error
checks and the accompanying error messages that may occur during a data import.
Appendix C. Job Opening Record Layout: Provides the record layout for the
job opening extract file. This record layout provides field level and cross field edit
checks and the accompanying error messages that may occur during a data import.

I. OVERVIEW
Appendix D. Performance Outcome Groups: Specifies the performance
outcome groups used in calculating the entered employment, retention, and
earnings increase measures.
Appendix E. Client Server Setup: Provides instructions for installing the DRVS
using a client/server setup.
Appendix F. Troubleshooting: Provides solutions for common problems that may
occur while installing or using the DRVS.
Please contact Mathematica Policy Research, Inc. at [email protected] for information about application installation, LX data files, performance
reports, or any other issues related to the DRVS.

B. List of Data Directories
The DRVS uses a number of data directories. The following table provides a list
of the data directories that the user is most likely to access.
Application Folder or File

Directory Location

Application default directory

C:\ Program Files\DRVS
(user can rename directory or install in another location)

Database default

C:\ProgramFiles\DRVS\User Data\
(user can create and name own databases)

Error log default

C:\Program Files\DRVS\Logs

Exported numerators and
denominators default

C:\Program Files\DRVS\Performance Groups Export\

Export files for LERS

C:\Program Files\DRVS\Labor Exchange Export\

RV/DEV XML results

C:\Program Files\DRVS\XML

DRVS User Guides

C:\Program Files\DRVS\Help Documents\

II. INSTALLATION
This chapter provides DRVS system requirements and installation instructions.

Step 1—Minimum System Requirements
Following are the minimum system requirements. Recommendations for greater
than minimum requirements are indicated in parentheses where applicable.
Item

Requirement

Processor

Pentium 4 CPU 1.80GHZ (more is
recommended)

Operating System

Windows 2000 or Windows XP

Memory

1 GB (more is recommended)

Application Hard Disk
Space

350 MB (more is recommended)

Database Hard Disk
Space

Varies by state.

Database

Varies by state. States that exceed MSDE
maximum per database must install SQL
Server.

Display

1024x768 or higher-resolution display with
256 colors

Other

MSDE or SQL Server must be installed prior
to installing the DRVS.
Latest Windows service packs and critical
updates should also be installed.

II. INSTALLATION
Hard disk requirements will vary depending on the state’s database size. For
example, some states may exceed the current MSDE 2000 2 GB per database size
limit. If any database exceeds the MSDE 2000 limit, users will need to license,
install, and set up Microsoft SQL Server to run the DRVS. Any licensed version of
SQL Server should allow the user to install and run the DRVS. SQL Express
(MSDE 2005) has not yet been fully tested for compatibility with the DRVS.
The DRVS will install all required .Net Framework and Crystal Reports
components.
DRVS installation requires Read/Write access to the system registry, Program
Files folder, Windows\System32 folder and the Global Assembly Cache. Registry
entries are made in HKEY_LOCAL_MACHINE\SOFTWARE\DRVS and in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft uninstall areas. DRVS users
will need Read access to the registry and Read/Write access to the Program File
folders, as well as Read/Write/Delete access to the SQL database.

Step 2—Uninstalling Prior Versions
Users should uninstall previous versions of the software before installing the
DRVS. DRVS versions 5.0 through 6.2 will automatically uninstall during the 6.3
installation process.
Following are instructions for uninstalling LX version 2.01 or earlier on a
Windows 2000 or Windows XP machine. These instructions can also be used to
uninstall the DRVS, if the user prefers to uninstall prior to beginning installation of
version 6.3. Procedures for uninstalling may differ slightly on different machines,
but are generally self-explanatory. On any machine, users should be sure to
uninstall through the control panel rather than by deleting the installation directory
for the prior version; uninstalling by deleting the installation directory may cause
problems with the subsequent installation.
• Click the Start button, then select Settings, Control Panel.

II. INSTALLATION
• Click on Add/Remove Programs.
• Click on the ES Data Validation icon.
uninstall the DRVS.)

(Click on the DRVS icon to

• Click on the Remove button.
• A message will display confirming that you want to remove the
application. Click on Yes.

• When the uninstall progress window no longer displays, close the
Add/Remove Programs window.
Users may need to contact their system administrator to uninstall the application.
Because DRVS 5.0 through 6.3 reflect substantial changes to the LX reporting
requirements, states must use version 2.01 of the LX reporting/validation
application to analyze or amend reports for Program Year 2004 and earlier. The
participant counts and performance measures generated by DRVS 6.3 are in
general not comparable to those generated by prior versions of the application.

Step 3—Download from the Internet
To download the DRVS from the Internet:
1.

Open your Internet browser and go to:
www.doleta.gov/performance/reporting/tools_datavalidation.cfm.

II. INSTALLATION
2.

Click on the DRVS 6.3 software link from the "In this section" side bar.

If a file download message displays, click on Save.

Select the location where you want to store the installation file.
Suggestion: C:\Temp. Click on Save.

A dialog box will chart the progress of the download of the installation
file. When the “Download Complete” message box appears, click on
Open. (If “close this dialog box when download completes” is checked,
when download is complete, you should go to C:\Temp or wherever you
stored the installation file to open it.)

A “WinZip Wizard – Unsupported Archive Type” message box may
display. Choose “Open the archive using the classic interface” and then
click on OK.

II. INSTALLATION
7.

Click on the DRVS.exe file and then click on Extract from the tool bar at
the top of the WinZip application screen.

Select a location for the extraction of the zip file. C:\Temp is the default.

Click on the Extract button.

10.

If a Confirm File Overwrite message displays, click Yes.

11.

Close the WinZip window.

Step 4—Application Installation
Based on the size of the state’s DRVS import file, either Microsoft SQL Server
2000 Desktop Engine (MSDE) or Microsoft SQL Server 2000 must be installed
prior to installing the DRVS. MSDE is a free version of SQL Server that can be
used with client applications. When installing MSDE, users must set a “strong”
password. Users should go to http://www.microsoft.com/sql/msde/default.mspx
for more information about MSDE and to download MSDE. SQL Express (MSDE
2005) is not compatible with the DRVS.
If the user’s estimated database size exceeds the MSDE limit, then Microsoft SQL
Server will need to be installed prior to installing the DRVS. Users can find more
information about SQL Server at http://www.microsoft.com/sql/default.mspx.
Users may need to contact their system administrator to install MSDE or SQL
Server. Installation procedures may differ slightly on different machines, but are
generally self-explanatory.
Users who prefer a client/server setup should review Appendix E in conjunction
with the instructions in this section. Only users with full SQL Server with
Enterprise Manager should use a client/server setup.

II. INSTALLATION
Before starting installation of the DRVS, close all applications and programs that
are open.
1. Open Windows Explorer and go to C:\Temp (or wherever you stored the
application files).
2. Double click on DRVS.exe.
3. If you haven’t uninstalled prior versions of the DRVS, the DRVS will
display a window asking if you would like to.

4. Click on Yes to automatically uninstall prior versions. A progress bar
will show the status of the uninstall process.

II. INSTALLATION
5. At the Welcome to the DRVS Installation Wizard window click on Next.
If you are installing the DRVS for the first time, you may be prompted to
reboot prior to beginning the installation routine.

II. INSTALLATION
6. Read the License Agreement and, if you accept, click on the “I accept the
license agreement” button.

Read the Readme Information screen and click on Next.

On the User Information screen, make any necessary modifications to
the user information. Then click on Next.

II. INSTALLATION
9.

On the Destination Folder screen, the destination location will default to
C:\Program Files\DRVS.

10. If you prefer a different destination location, click on Browse on the
Destination Folder screen to navigate to a different location. Click on
Next.

II. INSTALLATION
11. In the “SQL Server Connection” window, enter your server name in the
SQL Server Name box. If you did not name your database instance,
your server name is “(local)”. If you don’t know the name of your
database instance, contact your system administrator.
12. For Database Authentication, click on Windows NT Authentication. If
you can’t use Windows Authentication (e.g. Win 98 or ME users), click
on SQL Authentication and complete the SQL User Name and SQL
Password boxes. Click on Next.

II. INSTALLATION
If the DRVS Installation Wizard does not progress beyond this point, the user must
determine if an incorrect or inactive server name has been entered in the SQL
Server Name field. If a name that does not match any of the state’s servers is
entered, there will be a delay or a failure to progress to the next screen.
If a name is entered that matches one of the servers, but the server is inactive, the
Installation Wizard may also stop at this point. To find out if the server is active
go to Start/Settings/Control Panel/Administrative Tools/Services. Microsoft SQL
Server should be on the list of services and the task/service should be started. If it
is on the list but not started, start it and reboot. If it is not on the list, SQL Server
was not installed. There should also be a SQL Service icon on the bottom part of
your screen, on the desk tray as a little box with a green arrow or red square. The
green arrow indicates the service is started and the red square indicates it is not.
Right click on the icon to open the SQL Service manager, then start the service.

II. INSTALLATION
13.

On the “Install the DRVS Database Screen” check “I want to create a
DRVS database.” If the user instead checks “I DO NOT want to
create a DRVS database” the DRVS will continue to use the database
from the prior version of the DRVS, yielding performance results that
appear valid but in fact may not be. However, states using a
client/server setup should check “I DO NOT want to create a DRVS
database”, and refer to the instructions in Appendix E of this guide.

14. Click on Next on the “Ready to Install the Application” screen. This
screen also allows you to exit the installation wizard or, if necessary, to
return to the previous screen to change server connection information.
15. The “Updating System” screen will display, showing installation
progress. However, this screen may display for several minutes with no
indication of progress.

II. INSTALLATION
16. Click on Finish on the “DRVS has been successfully installed.” screen
to exit the DRVS Installation Wizard.

17. Reboot your computer after completing the DRVS installation. You
may delete the DRVS.exe used to install the application once the
installation process is successfully completed.
18. There are no further installation steps for a PC setup.

III. TUTORIAL
This chapter provides information on the various functions of the DRVS software.
Users can navigate between functions using the menu bar at the top of the active
DRVS window, or by using the side bar at the left of the active DRVS window.
Users are encouraged to click on Labor eXchange on the side bar to leave the
active window, before selecting a new function.
Following are brief summaries of each section of the tutorial.

A. Signing In
Section A describes how to open and sign in to the DRVS for specified reporting
periods, and how to change reporting options.

B. Preparing and Importing Records
Section B describes how to build and import files of job seeker and job opening
records so the application can produce the ETA 9002 and VETS 200 quarterly
reports, and generate the report validation values and the data element validation
sample worksheets. This section also describes how to access and review duplicate
detection and error reports of records rejected by the DRVS during the import
process.

C. ETA 9002 and VETS 200 Reporting
Section C describes how to access and review the ETA 9002 and VETS 200
quarterly report facsimiles, and how to export the quarterly reports to formatted
files which can be uploaded to LERS to fulfill ETA’s quarterly reporting
requirements. This section also describes how to access and analyze records by
performance outcome group and by the numerators and denominators of the
performance measures.

III. TUTORIAL
D. Report Validation
This section describes how to complete ETA’s report validation (RV)
requirements, and the minimized RV requirements applicable to states that
generate their quarterly 9002 and VETS 200 reports from the DRVS or DART.
Specifically, this section describes how to import reported values for comparison
to validation values on the report validation summary. This section also describes
how to view the report validation summary and submit the results to ETA.

E. Data Element Validation
This section describes how to select a sample of job seeker records, validate the
sampled records, generate the summary/analytical report, and submit the results to
ETA.

F. Database Management
Section F describes how to create new databases to use with the DRVS, how to
open existing databases, and how to save databases in alternate locations. Users
must create separate databases prior to importing the job seeker and job opening
extract files. This section also describes how to maintain database security.

III. TUTORIAL
A. Signing In
Step 1—Opening the Application
The installation wizard places a DRVS icon on your desktop. Double click on the
icon to open the application. Alternatively, click on the Start button, click on
Programs, select DRVS, and click on the DRVS icon to open the application.
The DRVS Log In screen will display. This is your indication that the application
has installed properly. Log on using the default User ID and Password:
LXAdmin4, LXAdmin4. The User ID is not case sensitive, but the Password is
case sensitive.
Click Login.

III. TUTORIAL
This default User ID and Password will provide access to the LX component of the
DRVS. For access to the WIA component of the DRVS, the defaults are
WIAAdmin, WIAAdmin. As described in the database management section of this
chapter, the user may change his or her own password to ensure database security.

III. TUTORIAL
Step 2—Reporting Options Screen
After the user logs in with an acceptable User ID and Password, the Reporting
Options screen appears. The user should maximize the screen to ensure that all
DRVS screens can be viewed in their entirety. The screen is maximized when the
user can see “Database: (name of open database)” in the lower left corner.

III. TUTORIAL
The Reporting Options screen provides several blank fields that the user must
complete so that the DRVS will produce the correct quarterly ETA 9002 and
VETS 200 reports and validation values.
• Select the Group from the drop down menu, either group 1/9002A-D,
VETS 200A-C for job seekers, or group 2/9002E for job openings.
• A warning will appear that changing the group will invalidate any data
currently in the application database. Section D of this chapter provides
more information on creating two separate databases, one for the job
seeker group and one for the job opening group, to retain all imported
data. Click Yes if appropriate.

• Select the applicable State name from the drop down menu.
• Select the appropriate Program Year from the drop down menu.
• Select the report due date from the Quarter drop down menu. The
applicable date ranges for the participant/job opening, exiter, entered
employment, and employment retention/earnings cohorts will then auto
fill based on the reporting schedule in Appendix A of this guide.
• After all options are selected, click on Save. “Reporting options saved
successfully” will then appear in red type at the bottom left of the screen.

III. TUTORIAL
The Refresh button on the upper right resets the screen if the user changes the
Group or the Date Ranges. The Clear All button clears the screen of all dates.
The Re-Calculate button will recalculate the 9002 and VETS 200 report values for
the active database, based on changes in the Date Ranges on the Reporting Options
screen. Users must click Save, then Re-Calculate, and then the Refresh button to
ensure that the correct recalculation is done.
The Re-Calculate button should only be used when Date Ranges are changed to
subsets of the Date Ranges entered for the initial file import. For example, the user
may import a file of job seekers for the four quarter report period ending 12/31/05.
The user can select the final quarter of the four quarter reporting period—10/1/05
through 12/31/05—on the Participant row, and then click on Re-Calculate to obtain
the counts of participants in just the last quarter of the original reporting period.
The Re-Calculate button cannot be used to obtain accurate counts or performance
outcomes for Date Ranges that start earlier or end later than those selected for the
original import, because edit checks have not been applied based on the new Date
Ranges.
The DRVS has the functionality to filter import files after the initial sign-in based
on the WIB name, case manager, office name, and the two user fields. The options
in the drop down menus for each of these fields are derived from the unique values
in these fields in the import file. Users can filter on these fields to create subsets of
the state level reports.
After all options are selected or refreshed, click on Save and then Re-Calculate to
calculate reports for the selected filter(s) only. A message box will appear, asking
users to confirm recalculation. Click Yes. “Re-Calculation successful” will appear
in red type at the bottom left of the screen. Click the Refresh button after
recalculation is complete. Whenever a filter is used, the report facsimile will
display the selected filter(s) on the last page of the facsimile.

III. TUTORIAL

III. TUTORIAL
B. Preparing and Importing Records
After signing in, states must import an extract file containing the job seeker (both
participant and exiter) records for all individuals included in the ETA 9002 and
VETS 200 quarterly reports selected on the Reporting Options screen. States must
also import a separate file of job openings to create the 9002 E report. Section D
of this chapter provides instructions for creating separate databases for the job
seeker and job opening imports. See Appendix A for a reporting schedule which
specifies the participant/exiter and job opening cohorts included on each quarterly
9002 and VETS 200 report.

Step 1—Create Job Seeker File Based on Record Layouts
The job seeker extract file layout is in Appendix B of this User’s Guide, together
with the field level and cross-field edit checks. Users should also download the
LX
conversion
rules
from
http://www.doleta.gov/performance/
reporting/reporting_requirements.cfm. This document cross-references each field
on the current record layout to the corresponding field(s) on the record layout used
in version 2.01 of ETA’s LX reporting/validation software. Both the Appendix B
record layout and the conversion rules should be used in building the import file.
The import file should include a separate record for each spell of participation that
falls within the reporting schedule parameters in Appendix A; for some
participants there will be multiple records in the import file.
The extract file type is ASCII, comma-delimited. Files can be in *.txt or *.csv
format, but *.dat or other file types are not accepted. Fields must be in the order
listed on the record layout. Eighty-two fields (81 commas) are accepted by the
application. If the exact number of fields or columns listed in the record layout is
not included, all the records will be rejected.
The job seeker record layout includes all the fields necessary for generating the
9002 A-D and VETS 200 A-C reports, with the addition of six fields. The
additional six fields are observation number (at the beginning of the record), and

III. TUTORIAL
WIB name, office name, case manager, and two user fields (at the end of the
record). The user fields are for any additional data (e.g. participant's name) that the
state wishes to include.
Data Element Issues
The observation number (field 1), individual identifier (field 2), and date of
program participation (field 5) are mandatory fields and, if left blank, will result in
the record being rejected. If possible, states should include the participant’s Social
Security Number (SSN) as the individual identifier (field 2) or in one of the user
fields, because SSNs are required to obtain wage records and to measure
performance outcomes.
Users should pay special attention to how their job seeker files are saved and
resaved. There are two fields in the record layout that require two digit numerical
codes—field 21/Highest School Grade Completed and field 66/Other Reasons for
Exit—and some of the codes have lead zeros. Various file management programs
(including .csv) may drop the lead zeros in these two fields as the files are saved
and resaved. The DRVS will reject records when codes in these two fields are
missing lead zeros. States can treat these two fields as text fields to preserve the
lead zeros.
Several fields in the record layout relate to the participant’s status as an eligible
veteran (field 14), campaign veteran (field 15), disabled or special disabled veteran
(field 16), recently separated veteran (field 17), and homeless veteran (field 18).
Appendix B details a number of edit checks that are applied to these fields to
ensure that the veteran status data values are consistent within a participant record.
If the participant is a disabled or special disabled veteran as indicated in field 16,
then the participant’s record should have a code of 2=Yes, Eligible Veteran in field
14 even if the participant served in the military for 180 days or less. Campaign and
recently separated veterans cannot be so designated unless they are also eligible
veterans who served greater than 180 days. Therefore, campaign and recently
separated veterans would also have a code of 2=Yes, Eligible Veteran in field 14.
If the participant is a homeless veteran as indicated in field 18, then either a 1 or 2
is acceptable in field 14.

III. TUTORIAL
In PY 2004, states were required to start a new registration year record if a
Transitioning Service Member (TSM, field 19) became a veteran while receiving
LX services. Beginning in PY 2005, states should no longer start a new record
simply because the participant’s status changes from TSM to veteran. If the
participant’s status changes from TSM to veteran during the same participation
cycle, simply retain the TSM code of 1=Yes in field 19, and code the applicable
veteran fields when the participant becomes a veteran. The participant can thus be
counted in both TSM and applicable veteran fields based on the same record.
Two fields relate to the participant’s educational status—Highest School Grade
Completed (field 21) and School Status at Participation (field 22). DRVS edit
checks are applied to these two fields to ensure that the data are consistent for a
given participant. However, there may not always be data in both fields for selfservice customers, so ETA has provided decision rules for how to address missing
data. First, the user should ensure that PY 04 data values have been properly
converted to PY 05 data values using the LX conversion rules. For example, if
there are a lot of records with a code of 12=number of elementary/secondary
school grades completed in field 21, then you may not have followed the
conversion document, which instructs you to convert PY 04 12s to 87=Attained HS
Diploma. Once all values have been converted, then fill missing data as follows:
• If field 21= 00-12 then field 22=1
• If field 21= 13-15 then field 22=3
• If field 21= 16-17, 87-91 then field 22=5

Users should also note that the DRVS record layout includes fields 38 and 39 for
Most Recent Date Attended TAP Employment Workshop (DVOP) and Most
Recent Date Attended TAP Employment Workshop (LVER). The DRVS uses
these fields to calculate Row 9—Attended TAP Employment Workshop on the
VETS 200 A, B and C reports. Because OMB has not yet approved the
requirement to report attendance at TAP employment workshops, states have two
options with respect to fields 38 and 39: 1) leave these fields blank until OMB
approves the reporting requirement; 2) collect TAP employment workshop data

III. TUTORIAL
and place it in fields 38 and 39 as appropriate. If option 2 is chosen, users should
be sure to advise ETA that the LERS upload is reporting on TAP workshop
attendance.
It is no longer necessary to place a Most Recent Date Received Staff Assisted
Services in fields 27, 28, and/or 29 if the job seeker received one of the staff
assisted services recorded in fields 30-35, or 37-64. The DRVS calculates Row 13
on the 9002 A, Row 8 on the 9002 B, Rows 10-12 on the 9002 D, and Rows 8 and
17-19 on the VETS 200 A-C reports using the specific service type fields rather
than fields 27, 28, and 29.
For participants who receive only self-assisted services, often from the Internet, the
participant record may only have a Date of Program Participation. There would be
no specified service dates, and possibly no exit date even if the Date of Program
Participation is well in the past. This is because there is no self-service data field
on the record layout, but self-services are reportable. Self-service participant
records may not have employment status so would be excluded from the entered
employment rate. States should still conduct wage record matches to determine if
the self-service participants can be measured in the retention and earnings
measures. However, if the state does not have SSNs for these participants (e.g.
because they received services through the Internet) then the state should place a
code of 99=Invalid SSN in the Other Reasons for Exit field.
Identifying Exit Dates
The group 1 file should always contain nine quarters worth of data on job seeker
registrations, services, exits and post-exit employment. In the group 1 file, the
state should include a separate record for each discrete participation spell for a
given job seeker. A participation spell ends when the job seeker has not received
any services for 90 days. When 90 days have passed since the last service, the last
service date is also the exit date for that spell of participation.
The previous LX concept of reporting discrete registration years for a given job
seeker is not applicable under the common measures reporting requirements. As
mentioned, the previous LX concept of starting a new registration year when a

III. TUTORIAL
TSM becomes a veteran is also not applicable under the new common measures
requirements. Therefore, states will need to create new job seeker records and
cannot build on the registration year records used for reporting in Program Year
2004 and prior.
To create new job seeker records, first determine the earliest service date on or
after July 1, 2003. This will be the first Date of Program Participation in a new
record. Starting from the Date of Program Participation, look for a “chain” of
services provided by Wagner-Peyser, DVOP/LVER, or partner programs. In a
chain of services, each subsequent service date is no more than 90 calendar days
after the last service date. As long as the gap between each successive service is
less than 90 consecutive calendar days, the services are part of one record.
When the chain breaks—meaning that the job seeker has not received any services
funded by the program or a partner program for 90 consecutive calendar days, has
no planned gap in service, and is not scheduled for future services—then the date
of exit is applied retroactively to the last day on which the job seeker received a
service funded by the program or a partner program. For many job seekers, the
Date of Program Participation may also be the Date of Exit. A new record for that
individual will begin the first time a service is received after an exit date.
For example, the job seeker first receives a service on July 1, 2005. The seeker’s
Date of Program Participation and applicable service date are both recorded as July
1, 2005. The job seeker’s next service date is September 30, 2005. The gap
between these two service dates—the count of days from July 2 to September 29
inclusive—is 90 days. Therefore, the first participation record for the job seeker is
given an exit date of July 1, 2005. A second participation record is created with a
Date of Program Participation and an applicable service date of September 30,
2005. In this scenario, September 30 is the earliest date that a new service would
generate a new participation record.
Data Values in Post-Exit Fields
Regardless of the participant's exit and employment status, there must be
consistency across the post-exit fields in every record in the group 1 file.

III. TUTORIAL
Appendix B details the numerous edit checks that are applied to the post-exit
fields, and these edit checks are summarized below.
There are three sequences of post-exit fields:
• 1st quarter after exit—fields 67, 68, 75
• 2nd quarter after exit—fields 69, 70, 76
• 3rd quarter after exit—fields 71, 72, 77
The first field in each sequence (67, 69, 71) indicates the participant’s employment
status in the relevant quarter after the exit quarter. There must be a value of 1
(employed), 2 (not employed), or 3 (information not yet available) in each of these
three fields. These three fields cannot be left blank or the record will be rejected
by the DRVS.
If the participant exited and was employed in a post-exit quarter, place a 1 in field
67, 69, or 71 respectively. Place a 1, 2, 3, 4, or 5 as appropriate in field 68, 70 or
72 (type of employment match). If the type of employment match field has a value
of 1, 2, 3, or 4, there should be wages greater than zero in field 75, 76, or 77. If the
type of employment match field has a value of 5, then the wages should be zero or
blank in fields 75, 76, or 77.
If the participant exited and was unemployed in a post-exit quarter, place a 2 in
field 67, 69, or 71 respectively. Place a zero or blank in field 68, 70 or 72 (type of
employment match) respectively. Also place a zero or blank in field 75, 76, or 77
(wages).
If the participant has not yet exited, or if the participant exited so recently that
employment status and wage data are not yet available, place a 3 in field 67, 69, or
71 respectively. Place a 6 in field 68, 70 or 72 (type of employment match). Place
999999.99 in field 75, 76, or 77 to indicate that wages are pending.
If the data in each sequence of post-exit quarters are not consistent as described
above, the DRVS will reject the record.

III. TUTORIAL
In addition, if the participant exited and the post-exit quarter fields indicate that
employment status and wage data are not yet available, yet sufficient time has
passed that these data should be available, the DRVS will change the data values to
indicate that the participant was unemployed in the relevant post-exit quarter. The
DRVS will generate a warning message for each record where these data values
have been changed.

Step 2—Create Job Opening File Based on Record Layout
The job opening extract file layout is in Appendix C of this User’s Guide, together
with the edit checks. The Appendix C record layout should be used in building the
import file. The import file should include a separate record for each job opening
that has a job opening received date within the reporting schedule parameters in
Appendix A.
States may need one of the user fields as a workaround for preparing the group 2
job openings file. If the state’s system cannot easily generate records of job
openings, but only of job orders, the state will need to convert its job order file into
a job openings file. This can be done with the user field if in the state every job
opening within a job order is identical for reporting purposes. Following the group
2 record layout, pull an extract of job order records putting the number of job
openings for the job order in one of the user fields. Then create a routine that will
multiply that job order record by the number in the user field to obtain the proper
number of job opening records to load into the DRVS.

III. TUTORIAL
Step 3—Load Extract Data
Once the job seeker and job opening data files are prepared according to the record
layouts, they can be imported. The state can import either the 9002A-D job seeker
or 9002E job opening file first by following the instructions in this section.
However, the user should rename the initial database to distinguish it as containing
either job seeker or job opening records. The user must create a new database for
the second and all subsequent imports by following the instructions for database
creation in Section D of this chapter. If the user does not create new databases
for subsequent imports, previously imported data will be overwritten.
Click on Import on the menu bar and select Import File.
Database screen will appear.

The Load File to

Click on Extract. The DRVS should be preset to Extract. Then select the file to be
imported using the Browse button.
Click Open. Then click Add File to move the file into the Load File box. Click on
the Load File button.

III. TUTORIAL

A message box will appear, asking for confirmation that reporting options have
been set. Click on Yes to confirm, or No to return to the Reporting Options screen.

III. TUTORIAL
To terminate the import process, click on the X in the upper right corner of the
Load File to Database screen.
During import, the Load File to Database screen will display a progress bar and
status messages. The status messages appear from bottom to top.

When the import is complete, the progress bar will disappear and the following
message will appear at the top of the status message section: “DONE. File (file
name) processed. Please review the Error report.”

III. TUTORIAL
The file import time will vary based on system capabilities, the number of records
in the extract file, and the density of the records. If the MSDE database has
reached its maximum capacity, or if there are a significant number of edit check
failures, the software may generate a critical error. If the import fails, the progress
bar will stop before reaching completion and an error message will appear in the
status window.

III. TUTORIAL
Step 4—View Imported File
To view the imported file click on Import from the menu bar and select View
Source Table. This is a read-only screen and records are displayed in the order in
which they appeared in the import file. The source table displays all records that
passed the import edit checks or received only “warning” errors. Rejected records
are not displayed in the source table or included in any report calculations.
Users can sort on any column in the source table by clicking once on the relevant
column header. Note however that the source table does not assume lead zeros
because fields are recognized as text in the source table. So, for example, resorting
on OBSNumber will cause records to appear out of order. The example below
shows a source table sorted by Date of Birth.

III. TUTORIAL
Step 5—Review Error Reports
When the extract file is loaded, the application reads each record to ensure that all
fields are valid based on the record layout and the edit check specifications in
Appendix B (job seekers) and Appendix C (job openings) of the User's Guide. The
edit checks ensure that data are in the proper format, values are within the specified
range of values, and data are consistent across fields. Duplicate records and any
records with missing or invalid data in mandatory fields are rejected. Other types
of data errors will generate warning messages.
Import Errors can be viewed by clicking Import from the menu bar and selecting
Import Errors Report. The Import Errors report will display a separate row for
each error identified in the import file. Reject errors appear first, followed by
warnings.
Up to 15,000 records with reject conditions and 50,000 records with
warning conditions will be reported.
Errors are sorted by WIB Name, Office Name, and Case Manager if there are data
in these fields in the extract file.
If the number of errors in the file exceeds these limits, the file import will abort
although an error report is still produced. Excessive errors may be indicated in the
status messages if the processing stalls at the “Checking the data for errors” or
“Checking the data for warnings” messages. In some instances, this may be
indicated by a critical error message. Additional errors will be reported on the next
import of the file, as long as errors from the first import are corrected.

III. TUTORIAL
Import Errors Report

Click on the printer icon at the top of the report to print a paper copy. Users will
have the option to change the printer name, paper source and layout.
Click on the envelope icon to display an Export popup where users can select a
name, format and location for the report. For example, the Error Report can be
exported to an Excel file, so that the user can sort on and organize the errors for
analysis. This feature is very helpful when there are a large number of errors.
The Import Error report is not automatically saved to the DRVS install location
folder. To save an error report, the user must export the error report using the
envelope icon.
After reviewing error reports generated by the application, users should determine
if the extract must be regenerated or reformatted and reloaded. Note that rejected
records do not appear in the source table or in any report calculations. However,
records that receive warning errors are displayed in the source table and included

III. TUTORIAL
in all report calculations. Because warning errors may indicate data problems that
impact the calculations, users are strongly encouraged to review and correct
warning errors in addition to rejected records. If only a small number of records
are rejected, it may not be necessary to re-import the file.

Step 6—View Duplicates
This step allows the user to view the duplicate records identified and rejected by
the application. No data entry is required; this option is for analytical purposes
only. The duplicate detection criteria for job seeker records are specified in
Appendix B as cross-field edit checks. For job opening records, the observation
number must be unique for each record.
Click on Import from the menu bar and select View Duplicates.
A report will display the duplicate records from the import file. DRVS rejects job
seeker records with duplicate observation numbers and records with the same
Individual Identifier that have overlapping participation spells based on the Date of
Program Participation and Date of Exit.

III. TUTORIAL
If the user determines it is necessary to fix the import file, the duplicate records
must be removed and the file reimported.
Click on the printer icon at the top of the report to print a paper copy. Users will
have the option to change the printer name, paper source and layout.
Click on the envelope icon to display an Export popup where users can select a
name, format and location for the report. For example, the duplicates report can be
exported to an Excel file, so that the user can sort on and organize the errors for
analysis. This feature is very helpful when there are a large number of duplicates.
The Duplicate Detection report is not automatically saved to the DRVS install
location folder. To save a duplicate detection report, the user must export the
report using the envelope icon.

III. TUTORIAL
C. ETA 9002 and VETS 200 Reporting
The DRVS produces the ETA 9002 and VETS 200 quarterly reports from the
import files of job seekers and of job openings. Prior to submitting these reports to
ETA, states may analyze the ETA 9002 and VETS 200 counts and performance
rates by viewing the job seeker performance outcome groups and the numerators
and denominators as described in steps 1 and 2 below.

Step 1—View Report Validation Table
This function allows the user to view the imported records assigned to the entered
employment, retention and earnings performance outcome groups.
The
performance outcome groups are specified in Appendix D of this user’s guide. No
data entry is required; this function is for analytical purposes only.
Click on Report Validation on the menu bar. Select View Validation Tables from
the drop down menu. Two tabs are displayed. The LX Adult Performance Group
Validation tab shows the total number of records for each performance outcome
group. The Performance column on the summary tab provides the group number
corresponding to the performance outcome group numbers in Appendix D.

Click on the far left column to highlight a performance outcome group row on the
performance group tab. In this example, outcome group 3 is highlighted.

III. TUTORIAL
The detailed records for the highlighted group will then be displayed on the LX
Participant Data tab which is the right-most tab in this function. The ParticipantID
column numbers all of the participants in a given performance outcome group, so
that the ParticipantID number in the last row of the Participant Data tab will
correspond to the number of participants listed on the summary tab for that group.

The participant data records can be sorted by clicking once on the header of the
column to sort by. Note however that the table does not assume lead zeros because
fields are recognized as text in the report validation table. So, for example,
resorting on OBSNumber will cause records to appear out of order.
To increase the width of a column, click the mouse on the intersection of the
relevant column heading and drag to the desired width.
The DRVS only assigns records to performance measure cohorts if sufficient time
has passed for the state to determine the outcomes for the cohort. If sufficient time

III. TUTORIAL
has passed and the post-exit employment fields are still coded as pending, the
application will change the employment status to unemployed and assign the
record accordingly. This default edit is specified in more detail in Appendix B.
It is important to note that if the user decides to change the report due date or
program year after the file has been imported, and clicks on the Re-Calculate
button, the counts displayed in each performance outcome group in the report
validation table may not accurately reflect the report period selected. The user must
change the program year or the report due date and then re-import the file to obtain
the correct performance outcomes.

Step 2—Export Numerators, Denominators, and Counts
This function will create individual files of participant records (with the addition of
age and performance outcome group at the end of each record) for the numerators
and denominators of each core performance measure. These export files can be
used for analytical purposes, or they can be used to generate files to match against
wage records. The export file will retain the format of the job seeker import file.
Functionality to create files of records included in the participant and exiter counts
will be provided in a future release.
Click on Report Validation from the menu bar. Then click on Export Numerators,
Denominators, and Counts. A message box will ask the user to confirm that the
numerators, denominators, and counts should be exported. Click on Yes to export.

III. TUTORIAL
The application will indicate when the files have been exported by displaying an
Export Completed message that specifies the location in which the exported files
have been saved. The export files are saved to a subfolder titled “Performance
Groups Export” in the DRVS install location. If the DRVS is installed in the
default location, the export files will be saved to a C:\Program
Files\DRVS\Performance Groups Export\ subfolder.
Each export creates its own subfolder indicated by the date and time of the export,
so that the export files will not be overwritten by subsequent exports.

Following is a sample of the LX_EER_Denominator.txt export file.

III. TUTORIAL
Step 3—View Facsimiles
The Facsimile function displays the values generated by the DRVS in the formats
of the ETA 9002 and VETS 200 reports.
Click on Report Validation from the menu bar and select Facsimiles. Then select
the applicable facsimile. If you are signed in to group 1, then select one of the
9002 A-D or VETS 200 reports. The 9002 E will be grayed out. If you are signed
in to group 2, then the only available selection is the 9002 E.

Sample Facsimile Report

III. TUTORIAL
The header of the facsimile indicates the pertinent information from the sign in
screen including the type of report, the state name and the report due date. Users
will note however that some of the facsimile date headers do not match the
reporting period entered on the Reporting Options screen. This labeling error does
not impact calculations and will be corrected in a future release, together with
other facsimile formatting issues.
Click on the printer icon at the top of the report to print a paper copy. Users will
have the option to change the printer name, paper source and layout.
Click on the envelope icon to display an Export popup where users can select a
name, format and location for the report. For example, the facsimile report can be
exported to a PDF.
The facsimile is not automatically saved by the software, so the user must export
the facsimile report to retain it for future use.

III. TUTORIAL
Step 4—Export Reports
The state can export the reported values generated by the DRVS to files formatted
to upload to LERS. On the Report Validation menu select LERS Export. A
window will appear confirming that you want to create LERS export files.

Click on Yes to export all of the reports for the selected group. Another window
will indicate that the export files have been saved to the installation directory, in a
date and time stamped folder under the Labor Exchange Export subfolder. The job
seeker import file can be used generate the 9002 A through D and VETS 200 A
through C LERS files. The job opening import file can be used to generate the
9002 E LERS file.

III. TUTORIAL
This is an example of the 9002 A LERS export file:

States should contact their regional office or the ETA LERS informational website
at http://www.uses.doleta.gov/laborexchangereport.asp for more information about
procedures for submitting quarterly reports. Once the state accesses ETA’s LERS
upload function, the files created by the DRVS LERS export function can be
uploaded directly through the LERS web interface.
Users who have calculated values in Row 9 of the VETS 200 export file, but who
do not want to report TAP workshop attendance for the period prior to OMB
approval, may overwrite the calculated values in Row 9 with zeros.
Users should also be aware that LERS edit checks require the 9002 B to be
uploaded prior to the 9002 A, so cross-report edit checks can be applied.

III. TUTORIAL
D.

Report Validation

All states are required to e-submit report validation results to ETA every August.
However, states that use the DRVS or DART to generate their ETA 9002 and
VETS 200 reports do not need to import reported values and conduct a full report
validation. After loading their extract files into the DRVS as described in section
B of this chapter, DRVS and DART states should skip directly to Steps 2 and 3
below to view the report validation summaries and e-submit them to ETA.
To conduct a full report validation, states that do not use the DRVS or DART for
reporting must first import their job seeker and job order validation extract files
into the DRVS as described in section B. The software will generate ETA 9002
and VETS 200 validation values from these files. States must then prepare and
import a separate file of reported counts for each 9002 and VETS 200 report being
validated. Once each reported counts file has been loaded, the DRVS compares
the validation values derived by the software to the actual values reported by the
state on each of the reports. The software will then generate a separate RV
Summary for each 9002 and VETS 200 report.

Step 1—Import Reported Values
The format for the reported values import file mirrors the import file format
required for the LERS quarterly submission, and the state may simply import their
LERS files.
Click on the Import menu and select Import File. The Load File to Database
screen will appear. Click on Reported. Use the Browse functionality to find the
reported values file or files to upload; up to seven files can be selected at one time.
Click Open, then click Add File to move the selected file(s) to the Load File box.
The selected files should appear in the box. Click on the Load File button to
import the files. A message box will appear, asking for confirmation that reporting
options have been set. Click on Yes to confirm, or No to return to the Reporting
Options screen. The Import File screen will show the progress of the import.

III. TUTORIAL
Step 2—View Report Validation Summary
This function allows the user to view the Report Validation Summary, which
displays the validation values generated by the DRVS, the state’s reported values,
the difference between these two sets of values, and a percentage difference for
each value. No data entry is required; this option is a read only function.
For DRVS and DART states, no values will appear in the Reported Values column
and the summary will show percent differences of 100% for all values. States
should verify the accuracy of their reports prior to submitting the results to ETA.
Click on the Report Validation menu and select Report Validation Summary.
Select the applicable summary from the sidebar. Only one RV summary can be
viewed at a time. It may take several minutes for the first summary to open after
the reported counts file has been loaded.
Sample RV Summary

III. TUTORIAL
Users can enter comments for each individual RV Summary by selecting the Enter
RV Comments menu item under Report Validation after importing their reported
counts. Users may also enter comments about the RV summary in ETA’s RV
summary upload screen.
If users have selected a WIB, Office, or Case Manager filter on the Reporting
Options screen, RV summaries will be generated for that substate level only. The
footer of the report will display the substate unit selected.

Step 3—Submit Report Validation Summaries to National Office
To submit the 9002 and VETS 200 report validation results to the National Office,
click on the e-Submit function under the File menu. The LX E-Submission screen
will appear. The drop down menu allows the user to select RV, DEV, or both.

Select RV if you are ready to submit RV results, but have not yet completed data
element validation. Click on the Extract & Upload XML button.

III. TUTORIAL
A screen will appear providing the location of the RV XML files as well as a
warning. The XML file location is the default data directory for XML files, which
is C:\Program Files\DRVS\XML.
After reading and accepting the warning, click OK.

III. TUTORIAL
After clicking OK, the Grantee Reporting System login screen appears. It may
take a minute or two for the software to open the web browser.

Enter the state’s validation password provided by ETA and click on the Login
button (Please note that the validation password is different from the reporting
password, which is used to submit reports and WIASRD record. There are separate
validation passwords for the LX and WIA programs). Users should enter their
name, email address, and telephone number in the appropriate fields. Then click
on Browse. Use the Choose File window to find the XML file created by the
DRVS. The location and name of the file are listed in the white cell at the top of
the web browser. Click on the Open button and the name of the selected file will
appear in the Locate File box.

III. TUTORIAL
Using the Report Source dropdown menu, select the type of software that the state
uses for generating its quarterly reports (e.g., ETA (DRVS), DART, or another
program). Then click the Submit button in the web browser.
It may take some time for the XML file to upload. Once the file has been
successfully transmitted, a DRVS Confirmation of Submission screen will appear.
Users can print a copy of the confirmation, request an email copy of the
confirmation, or logout.

III. TUTORIAL
E.

Data Element Validation

In data element validation (DEV), the software selects a sample of 25 records from
the state’s extract file. The state must verify the accuracy of specific data elements
in each record using its source databases. After the sample is drawn, the software
displays the data elements from the sampled records on automated and printed
worksheets that provide a means for states to indicate whether each data element
passed or failed the validation. Once the state enters its pass/fail determinations
for all sampled records, the software produces a DEV Summary/Analytical Report
that lists the error rates for each data element validated. States submit this report to
ETA every August using the DRVS e-Submit functionality.

Step 1—Create the Validation Sample
In the DRVS states select their DEV sample after the state’s validation file has
been fully imported. The sample is not automatically selected during import.
Click on the Data Element Validation menu and select Sample DEV. A screen
will appear asking for confirmation that the sample should be selected. Click OK.
The software will then draw a validation sample of 25 records from the extract file.
A message box will appear to confirm the sampling is complete.

III. TUTORIAL
Step 2—Validate Sampled Cases
Click on the Data Element Validation menu and select Edit Worksheets. This
opens a window that displays a summary of the sample of 25 job seeker records.
The summary screen is read only.
Click on the arrow to open the worksheet for a particular record.
Sample Worksheet Summary

III. TUTORIAL
When all data elements of a record have been validated (i.e. either Pass or Fail is
checked), the record displays "True" under the IsValidated column. If any data
element is left blank, the record displays "False" and users should open the record
to complete validation.
When performing DEV and editing individual records be mindful not to navigate
to and from the Edit Worksheets and the individual record worksheets. From time
to time, a critical error could occur during this type of navigation. A critical error
could erase the state’s sample, requiring that the sample be redrawn. If DEV has
been completed on an individual worksheet and the user does not want to continue
to validate other DEV records, either save and close out of DEV by going to
another function or save and close out of the application.
To access, update, or print individual sampled cases, double click on the row of the
selected record. This will open a validation worksheet for the record. The
worksheet is on three tabs, for validation fields 1 through 31, 32 through 61, and
62 through 77 respectively. This allows easier navigation though all of the data
elements.
For each data element, the data on the worksheet should be compared to the data in
the state system. The validator begins validation by looking at the first data
element on the worksheet and then locating the corresponding documentation in
the state system. This entails checking all necessary screens or other source
documentation to determine if this data element is accurate. For example, wage
record information must be checked against the state wage record files.

III. TUTORIAL
Sample On-Line Validation Worksheet

Check either pass or fail for each element using the validation indicator dropdown,
or leave the checkbox blank if appropriate and select pass or fail later. When
finished, select Save at the bottom of the screen. A message box will appear
asking if users want to print the row. Check Yes or No as appropriate. A message
will appear on the worksheet indicating “Not Completed” if the validator has not
completely validated a record. When each record has been validated in its entirety,
the worksheet summary will display the updated information from the tabbed
worksheets.

III. TUTORIAL
Step 3—Print Validation Worksheets for Sampled Cases
At the state’s discretion, sampled cases can be validated on printed worksheets first
and then entered into the DRVS as a separate step. To print the validation
worksheets for the sample in batch mode, select Print Worksheets on the Data
Element Validation menu. Click the printer icon at the top left of the screen to
begin printing.
Sample Printed Worksheet

III. TUTORIAL
Step 4—View, Print, and Annotate Summary/Analytical Report
After the validation worksheets have been completed, the software generates a
summary/analytical report which summarizes the errors identified during the data
element validation process. Click on the Print Summary/Analytical Report
function under the Data Element Validation menu to view and print the
summary/analytical report. No data entry is required on this screen. The Number
of Records Invalid field on the report indicates the number of validated records
with at least one error. Records with one or more data errors fail the validation.
Sample Summary and Analytical Report
(prior to completion of DEV)

III. TUTORIAL
After analyzing the errors, states may choose to annotate the report with comments
about the error causes and planned corrections. To do so, click on the Enter Data
Validation Comments function under the Data Element Validation menu.
Select DEV from the drop down menu. This opens a box that allows users to enter
comments of up to 250 words. After entering comments, click on the Save
button—the comments will then appear on the DEV Summary/Analytical Report.

Step 5—Submit DEV Results to the National Office
To submit the 9002 and VETS 200 data element validation results to the National
Office, click on the e-Submit function under the File menu. The LX ESubmission screen will appear. The drop down menu allows the user to select RV,
DEV, or both. Select DEV if only the summary/analytical reports are being
submitted, or both if the summary/analytical reports are being submitted together
with the RV summaries.
Follow the instructions in Section D, Step 3 of this chapter, which described how
to upload RV XML results.
Data validation results and documentation should be retained for at least three
years after completion. Retention methods are at the state’s discretion and may
include an archived database, printed worksheets and reports, or other methods.

III. TUTORIAL
F.

Database Management

When you use DRVS for the first time, you are provided access using the default
User ID and Password and a blank database (LX.mdf) is automatically created.
This section describes how the user can change his or her own password to
maintain database security, and how to create additional databases, open existing
databases, and save databases in alternate locations.
The database creation and management functions are necessary for importing
discrete job seeker and job opening files, without losing one or the other data
set. States must set up two separate databases to load and preserve group 1
and group 2 data. Users can open and close the two separate databases to run
the group 1 and group 2 reports.

Step 1—Database Security
After the initial log in using the default User ID and Password, users can change
their own password by selecting the Utilities menu and the Change Password
submenu. In the Change Password window, the user should enter old and new
passwords, and click on Change Password.

III. TUTORIAL
Future versions of the DRVS will allow database administrators to set up and
modify multiple DRVS user profiles, each with a unique User ID and Password
and access to specified databases.

Step 2—Create a New Database
To create a new database, go to the File menu and select New DB. This opens the
Enter a New Database Name dialog box where you can create a new DRVS
database in the User Data folder. Type in the name of your new database in the
File Name field. Database names must start with a letter, although numbers can be
included in the name. Database names cannot include spaces or non-alphanumeric
symbols. The DRVS blocks data entry of invalid database names and provides an
error message when improper names are entered.
Click on Open.

III. TUTORIAL
A message box will appear indicating that the new database was successfully
created. Click OK.

The DRVS Login box will display. Enter your User ID and Password (or the
default User ID and Password) and click on Login. The new database name should
display in the footer of the application screen when the screen size is maximized.
If it does not, check the source table to confirm that you are in the new database.
The new database will be created in the User Data subfolder of the DRVS install
location (default install location is C:\Program Files\DRVS).

Step 3—Open An Existing Database
The DRVS will automatically default to the database you were using the last time
you logged out of the application. That database name is displayed in the bottom
left footer of the application screen. To open a different database, go to the File
menu and select Open DB. This opens a dialog box where you can select an
existing database to open from the drop down menu.

III. TUTORIAL

Click on the drop down menu to access the list of databases that can be selected. If
no new databases have been created, a message will display stating that only the
default database exists. Choose a database and then click on the open database
button on the left of this screen. Click on the X button to exit this function and
return to the existing database.
Click on the open folder button. The following message will display.

Click OK. The Login box will then display. Enter your User ID and Password and
click Login. You will now be in the selected database. The new database name
should display in the footer of the application screen when the screen size is
maximized. If it does not, check the source table to confirm that you are in the
new database.

III. TUTORIAL
The open database functionality is necessary for preserving job seeker and job
opening imports, without losing one or the other. This functionality will also be
helpful if you:
• Have archived prior quarterly file imports but still want to easily access
them through the application.
• Have split the import file into two databases to keep the size manageable
in large states.

III. TUTORIAL
Step 4—Save a Database
To save an existing database go to the File menu and select Save As. This opens
the Save As dialog box where you can save a database and give the database a new
name or location.

Enter the new file name for the database and then click on Save. A message box
will indicate that the newly named database was successfully saved. Click OK.
The DRVS Login box will display. Enter your User ID and Password and click on
Login. The new database name should display in the footer of the application
screen. If it does not, check the source table to confirm that you are in the new
database. The newly named database will be saved in the User Data subfolder of
the DRVS install location (default install location is C:\Program Files\DRVS).

IV. REFERENCE GUIDE
This chapter of the User’s Guide provides a condensed list of all the application
menus and functions for quick reference.
A. File Menu
Options in this menu include:
1. New DB—Opens a dialog box where you can create a new database.
2. Open DB—Opens a dialog box where you can select another database to
open.
3. Save As—Opens a dialog box where you can save a database or file and
give the database a new name.
4. Link to Server—Opens a window where users can switch servers.
5. e-Submit—Opens a window where the user begins the process of
uploading XML files of RV and DEV results to ETA.
6. Exit—Select this to exit the DRVS.

IV. REFERENCE GUIDE
B. Import Menu
Options in this menu include:
1.

Import File—Select this option to import data into the application. See
the source table record layouts for the appropriate data record format.

Source Table Record Layout—This selection will be available in a
future release. It will display the record layout to use in developing the
job seeker import file. The record layout can currently be found in
Appendix B of this User’s Guide.

9002 E Source Table Record Layout—This selection will be available
in a future release. It will display the record layout to use in developing
the job opening import file. The record layout can currently be found in
Appendix B of this User’s Guide.

Reported Counts Record Layout—This function will be provided in a
future release.

View Source Table—This selection displays all of the records from the
job seeker extract file that were imported by the DRVS.

Import Errors Report—This selection displays the Import Errors
Report displaying the field level and cross-field edit check errors for the
job seeker file. Appendix B includes the import error messages for
each edit check.

Import 9002 E Errors Report—This selection displays the Import
Errors Report displaying the edit check errors for the job opening file.
Appendix B includes the import error messages for each edit check.

View 9002 E Source Table—This selection displays all of the records
from the job opening extract file that were imported by the DRVS.

IV. REFERENCE GUIDE
9.

View Duplicates—This selection displays a report that lists the
duplicate records identified and rejected by the DRVS when importing
the job seeker extract file.

C. Reporting Options Menu
The only option in this menu is Change. This selection opens an expanded version
of the Reporting Options screen that allows the user to change the program year,
report quarter due date, state name, program year start and end dates, and to select
subsets of participant records for analytical and management purposes. The
functionality to change reporting options, to generate local level or other substate
reports, will be provided in a future release.

D. Report Validation Menu
Options in this menu are:
1. View Validation Tables—This selection provides a window to view a
summary of each performance outcome group and totals of records for
each group. Highlight a performance outcome group row to view the
detailed records for that group.
2. Report Validation Summary—This function allows the user to select
from the sidebar the applicable RV summary to be viewed and printed.
3. Facsimiles—The Facsimile selection produces the 9002 and VETS 200
quarterly reports in the formats specified by the ET 406 Handbook.
4. LERS Export—This function allows the user to export the 9002 and
VETS 200 reports into files formatted to upload directly to ETA’s LERS
reporting system.

IV. REFERENCE GUIDE
5. Export Numerators, Denominators, and Counts — This selection
creates an export file for the numerator and denominator of each
performance measure. These export files are saved to the installation
directory, and can be used for analyzing the state’s performance.
Functionality to export participant and exiter counts will be included in a
future version of the DRVS.
6. Enter RV Comments — This function allows users to enter comments
for each individual RV Summary after importing their reported counts.

IV. REFERENCE GUIDE
E. Data Element Validation Menu
1.

Sample DEV—This function directs the DRVS to select the data
element validation sample of 25 records.

Edit Worksheets—This function accesses the worksheets for each of
the sampled records.

Print Worksheets—This function prints the worksheets in batch
mode.

Print Summary/Analytical Report—This function prints the
summary/analytical report.

Enter Data Validation Comments—This function provides a way
for the user to record comments about the DEV on the
summary/analytical report.

F. Admin Menu
1.

Add User—This function will be provided in a future release.

Modify User Details—This function will be provided in a future
release.

Delete/Deactivate User—This function will be provided in a future
release.

IV. REFERENCE GUIDE
G. Utilities Menu
The only function in this menu is Change Password. This allows the user to
change his or her own password.

H. Help Menu
Options in this menu include:

1. LX User’s Guide—This feature provides the DRVS user’s guide on-line.
To make the latest version of the user’s guide accessible through the
software, copy the guide from the ETA website into C:\Program
Files\DRVS\Help Documents with the title file name DRVS LX Users
Guide.pdf, and replace the existing guide. The file name must have the
spaces indicated.
2. Contacts—This feature provides contact information for users who
would like additional assistance using the application. For questions on
installing the software, LX data files, or performance reports users should
e-mail [email protected] by clicking on the email link.
Specify the version of the application being used, the question, and the
user’s contact information.
3. About—This feature provides the application version number and
version release date for the application.

APPENDIX A. REPORTING SCHEDULE
The following tables provide the program participation and exiter date ranges for
each quarterly report for program years 2005 through 2007.

Program Year 2005
Time Periods to Be Reported

Reporting Item
Report Quarter

July - Sept.

Oct. - Dec.

Jan. - Mar.

Apr. - June

Report Due Date

Nov. 14

Feb. 14

May 15

Aug. 14

9002 A and B; VETS 200 Participants and Exiters
Total Participants—job
seekers who received self
services or staff assisted
services during the time
period

10/01/04 to
09/30/05

01/01/05 to
12/31/05

04/01/05 to
03/31/06

07/01/05 to
06/30/06

Total Exiters—job seekers
with exit dates during the
time period

07/01/04 to
06/30/05

10/01/04 to
09/30/05

01/01/05 to
12/31/05

04/01/05 to
03/31/06

9002 C and D, VETS 200 Performance Measures
Entered Employment
Rate—job seekers with exit
dates during the time period

01/01/04 to
12/31/04

04/01/04 to
03/31/05

07/01/04 to
06/30/05

10/01/04 to
09/30/05

Employment Retention
Rate—job seekers with exit
dates during the time period

07/01/03 to
06/30/04

10/01/03 to
09/30/04

01/01/04 to
12/31/04

04/01/04 to
03/31/05

Six Months Earnings
Increase—job seekers with
exit dates during the time
period

07/01/03 to
06/30/04

10/01/03 to
09/30/04

01/01/04 to
12/31/04

04/01/04 to
03/31/05

04/01/05 to
03/31/06

07/01/05 to
06/30/06

9002 E
Job Openings—job
openings received during the
time period

10/01/04 to
09/30/05

01/01/05 to
12/31/05

Program Year 2006
Time Periods to Be Reported

Reporting Item
Report Quarter

July - Sept.

Oct. - Dec.

Jan. - Mar.

Apr. - June

Report Due Date

Nov. 14

Feb. 14

May 15

Aug. 14

9002 A and B; VETS 200 Participants and Exiters
Total Participants—job
seekers who received self
services or staff assisted
services during the time
period

10/01/05 to
09/30/06

01/01/06 to
12/31/06

04/01/06 to
03/31/07

07/01/06 to
06/30/07

Total Exiters—job
seekers with exit dates
during the time period

07/01/05 to
06/30/06

10/01/05 to
09/30/06

01/01/06 to
12/31/06

04/01/06 to
03/31/07

9002 C and D, VETS 200 Performance Measures
Entered Employment
Rate—job seekers with
exit dates during the time
period

01/01/05 to
12/31/05

04/01/05 to
03/31/06

07/01/05 to
06/30/06

10/01/05 to
09/30/06

Employment Retention
Rate—job seekers with
exit dates during the time
period

07/01/04 to
06/30/05

10/01/04 to
09/30/05

01/01/05 to
12/31/05

04/01/05 to
03/31/06

Average Earnings
—job seekers
with exit dates during the
time period

07/01/04 to
06/30/05

10/01/04 to
09/30/05

01/01/05 to
12/31/05

04/01/05 to
03/31/06

04/01/06 to
03/31/07

07/01/06 to
06/30/07

9002 E
Job Openings—job
openings received during
the time period

10/01/05 to
09/30/06

01/01/06 to
12/31/06

Program Year 2007
Time Periods to Be Reported

Reporting Item
Report Quarter

July - Sept.

Oct. - Dec.

Jan. - Mar.

Apr. - June

Report Due Date

Nov. 14

Feb. 14

May 15

Aug. 14

9002 A and B; VETS 200 Participants and Exiters
Total Participants—job
seekers who received self
services or staff assisted
services during the time
period

10/01/06 to
09/30/07

01/01/07 to
12/31/07

04/01/07 to
03/31/08

07/01/07 to
06/30/08

Total Exiters—job
seekers with exit dates
during the time period

07/01/06 to
06/30/07

10/01/06 to
09/30/07

01/01/07 to
12/31/07

04/01/07 to
03/31/08

9002 C and D, VETS 200 Performance Measures
Entered Employment
Rate—job seekers with
exit dates during the time
period

01/01/06 to
12/31/06

04/01/06 to
03/31/07

07/01/06 to
06/30/07

10/01/06 to
09/30/07

Employment Retention
Rate—job seekers with
exit dates during the time
period

07/01/05 to
06/30/06

10/01/05 to
09/30/06

01/01/06 to
12/31/06

04/01/06 to
03/31/07

Average Earnings
—job seekers
with exit dates during the
time period

07/01/05 to
06/30/06

10/01/05 to
09/30/06

01/01/06 to
12/31/06

04/01/06 to
03/31/07

04/01/07 to
03/31/08

07/01/07 to
06/30/08

9002 E
Job Openings—job
openings received during
the time period

10/01/06 to
09/30/07

01/01/07 to
12/31/07

APPENDIX B.
JOB SEEKER RECORD LAYOUT AND EDITS
The following table lists the field number, field name, valid values, edit checks,
and error messages for every field in the DRVS record layout for job seekers. The
functionality to view record layouts through the software by selecting Import/
Source Table Record Layout will be provided in a future release. See Chapter III
for detailed instructions for preparing the job seeker import file using the record
layout. Also see Appendix A for the reporting schedule and the date ranges of
participants/exiters to be included in each quarterly import file.

DRVS
Release 5.0
and later
Field No.

4/19/2006

Individual with a Disability

Date of Program Participation

1 = Male
2 = Female
0 or blank = not self-identified
YYYYMMDD

1 = Yes
2 = No
0 or blank = not self-identified
Race: American Indian or Alaska 1 = Yes
0 or blank = not self-identified
Native
1 = Yes
Race: Asian
0 or blank = not self-identified
Race: Black or African American 1 = Yes
0 or blank = not self-identified
1 = Yes
Race: Hawaiian Native or other
0 or blank = not self-identified
Pacific Islander
1 = Yes
Race: White
0 or blank = not self-identified
Race: Other

Gender

XXXXXXXXX
(No hyphens)
YYYYMMDD
blank = not self-identified

Date of Birth

Individual Identifier

DRVSLX-JS-ImportFile-EditChecks-041906.xls

Data Element Eliminated from Labor Exchange Reporting System

No additional edit checks.

Data Element Eliminated from Labor Exchange Reporting System

A. Mandatory field in DRVS version 5.0.

No additional edit checks.

A. Age (calculated at the Date of Program Participation when Date of Birth is
present) cannot be <9 or >100. [Logic change to be implemented in PY 06.]

A. Mandatory field in DRVS version 5.0.

B. Must be unique for each record.

A. Mandatory field in DRVS version 5.0.

Reject

Warning

Reject

Page 1 of 9

A. Date of Program Participation is missing or invalid.

A. Date of Birth is missing or invalid--age is <9 or >100 at Date
of Program Participation.

A. Individual Identifier is missing or invalid.

A. OBS Number is missing or is not unique.

A. Employment, Type of Employment Match, and Wages 3rd
Quarter After Exit Quarter cannot be pending when the report
quarter is 5 or more quarters after the exit quarter. Values for
these fields have been changed to Unemployed.

A. If field 71 (Employed in 3rd Quarter after Exit Quarter) is 3, field 72 (Type of Default Warning
Employment Match 3rd Quarter After Exit Quarter) is 6, and field 77 (Wages 1st
Quarter After Exit Quarter) is 999999.99, and the report quarter is 5 or more
quarters after the exit quarter, then change field 71 to 2, field 72 to 0, and field
77 to 0.

Edit check for Employed, Type of
Employment Match, and Wages -3rd Quarter After Exit Quarter

Observation Number

A. Employment, Type of Employment Match, and Wages 2nd
Quarter After Exit Quarter cannot be pending when the report
quarter is 4 or more quarters after the exit quarter. Values for
these fields have been changed to Unemployed.

A. If field 69 (Employed in 2nd Quarter after Exit Quarter)is 3, field 70 (Type of Default Warning
Employment Match 2nd Quarter After Exit Quarter) is 6, and field 76 (Wages
2nd Quarter After Exit Quarter) is 999999.99, and the report quarter is 4 or
more quarters after the exit quarter, then change field 69 to 2, field 70 to 0, and
field 76 to 0.

Edit check for Employed, Type of
Employment Match, and Wages -2nd Quarter After Exit Quarter

B. If multiple records have the same Individual Identifier, then only the record
with the most recent Date of Program Participation can have a blank Date of
Exit.

ERROR MESSAGES

A. Employment, Type of Employment Match, and Wages 1st
Quarter After Exit Quarter cannot be pending when the report
quarter is 3 or more quarters after the exit quarter. Values for
these fields have been changed to Unemployed.

Error Type

A. If multiple records have the same Individual Identifier (field 2), then no record Reject
can have a Date of Program Participation (field 5) or a Date of Exit (field 65)
between the Date of Program Participation and the Date of Exit plus 90 days of
any other record with the same Individual Identifier.

(all references refer to new
DRVS field numbers)

A. If field 67 (Employed in 1st Quarter after Exit Quarter) is 3, field 68 (Type of Default Warning
Employment Match 1st Quarter After Exit Quarter) is 6, and field 75 (Wages 1st
Quarter After Exit Quarter) is 999999.99, and the report quarter is 3 or more
quarters after the exit quarter, then change field 67 to 2, field 68 to 0 and field
75 to 0.

000000000
(No hyphens)

Additional Edit Checks
Edit Check Logic

Edit check for Employed, Type of
Employment Match, and Wages -1st Quarter After Exit Quarter

Program Source of Registration

Edit Checks - Valid Values
(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Individual Information

Data
Element Name

Duplicate Record Detection Logic

Additional Global Edit Rules

PY 04 DRVS
Field No.

IMPORTANT NOTE: This document contains data element specifications and edit checks that are used to support implementation of the Employment and Training Administration's (ETA) Data
Reporting and Validation Software (DRVS) Release 5.0 and later for Labor Exchange programs. DRVS for Labor Exchange programs was upgraded to support state implementation of common
performance measures and other revised reporting requirements approved by the United States Office of Management and Budget (OMB) beginning PY2005. A crosswalk of the import file field
numbers from the PY04 DRVS to the DRVS Release 5.0 and later is also provided.

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

20
New
Element

22
23

Part of
25-27

Part of
24-26

4/19/2006

DRVS
Release 5.0
and later
Field No.

PY 04 DRVS
Field No.

Edit Checks - Valid Values

School Status at Participation

1 = In-school, H.S. or less
2 = In-school, Alternative School
3 = In-school, Post-H.S.
4 = Not attending school; H.S. Dropout
5 = Not attending school; H.S. graduate
0 or blank = unknown

(all references refer to new
DRVS field numbers)

Warning

A. Must be 1 or 2 if field 14 (Eligible Veteran Status) is 1 or 2.

No additional edit checks.

DRVSLX-JS-ImportFile-EditChecks-041906.xls

B. Must be 3 or 5 if field 21 is 13-17, 87-88, 90, or 91.

A. Must be 1, 2 or 4 if field 21 (Highest School Grade Completed) is 00-12.

Warning

Error Type

A. Must be 1, 2 or 3 if field 14 (Eligible Veteran Status) is 1 or 2.

A. Must be 1 or 2, if field 14 (Eligible Veteran Status) is 1 or 2.

D. Must be 1 or 2 if field 18 (Homeless Veteran) is 1.

C. Must be 2 if field 17 (Recently Separated Veteran) is 1.

B. Must be 2 if field 16 (Disabled Veteran) is 1 or 2

A. Must be 2 if field 15 (Campaign Veteran) is 1

No additional edit checks.

Additional Edit Checks
Edit Check Logic

Data Collection Integrated with New Field # 16 on Record Layout
A. Must be 1 or 2 if field 14 (Eligible Veteran Status) is 1 or 2.

1 = Yes
2 = No
0 or blank = unknown
1 = Employed
2 = Employed, but Received Notice of Termination
of Employment or Military Separation;
3 = Not Employed
0 or blank = unknown

1 = Yes
2 = No
0 or blank = unknown

1 = Yes
2 = Yes, special disabled
3 = No
0 or blank = unknown
1 = Yes
2 = No
0 or blank = unknown

1 = Yes
2 = No
0 or blank = unknown

1 = Yes
0 or blank = not self-identified
1 = Yes
2 = No
0 or blank = not self-identified
1 = Yes <= 180 days;
2 = Yes, Eligible Veteran;
3 = Yes, Other Eligible Person;
4 = No
0 or blank = unknown

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

No additional edit checks.
Highest School Grade Completed 00 = No school grades completed
01 - 12 = Number of elementary/secondary school grades
completed
13 - 15 = Number of college, or full-time technical or
vocational
school years completed
16 = Bachelor's degree or equivalent
17 = Education beyond the Bachelor's degree
87 = Attained High School Diploma
88 = Attained GED or Equivalent
89 = Attained Certificate of Attendance/Completion
90 = Attained Other Post-Secondary Degree or Certification
91 = Attained Associates Diploma or Degree
0 or blank = unknown

Employment Status at
Participation

Transitioning Service Member

Special Disabled Veteran
Homeless Veteran

Recently Separated Veteran (3
yrs)

Disabled Veteran

Campaign Veteran

Eligible Veteran Status

Ethnicity Hispanic/Latino

More Than One Race

Data
Element Name

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 2 of 9

A-B. School Status at Participation and Highest School Grade
Completed values are contradictory.

A. Homeless Veteran cannot be blank or 0 if participant is an
Eligible Veteran.

A. Recently Separated Veteran cannot be blank or 0 if
participant is an Eligible Veteran.

A. Disabled Veteran cannot be blank or 0 if participant is an
Eligible Veteran.

A. Campaign Veteran cannot be blank or 0 if participant is an
Eligible Veteran.

A-D. The value for Eligible Veteran Status does not meet one
of the following conditions:
- Eligible Veteran Status must be 2 (Yes, Eligible Veteran) if
Campaign Veteran is 1 (Yes).
- Eligible Veteran Status must be 2 (Yes, Eligible Veteran) if
Disabled Veteran is 1 or 2 (Yes).
- Eligible Veteran Status must be 2 (Yes, Eligible Veteran) if
Recently Separated Veteran is 1 (Yes).
- Eligible Veteran Status must be 1 or 2 (Yes, Eligible Veteran)
if Homeless Veteran is 1 (Yes).

ERROR MESSAGES

4/19/2006

DRVS
Release 5.0
and later
Field No.

PY 04 DRVS
Field No.

Date of Actual Qualifying
Dislocation

Interstate

MSFW

UC Eligible Status

Data
Element Name

1 = Yes
2 = No
0 or blank = unknown
1 = Yes
0 or blank = unknown
YYYYMMDD
Blank = No date of actual qualifying dislocation

1 = Claimant Referred by WPRS
2 = Claimant Not Referred by WPRS
3 = Exhaustee
4 = Neither Claimant nor Exhaustee
0 or blank = unknown

No additional edit checks.

Additional Edit Checks

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Edit Checks - Valid Values

Error Type

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

ERROR MESSAGES

Page 3 of 9

DRVS
Release 5.0
and later
Field No.

New
Element

4/19/2006

New
Element

41-43

Services & Activities

PY 04 DRVS
Field No.

Edit Checks - Valid Values

YYYYMMDD
Blank = Has not received service

Most Recent Date Received Staff YYYYMMDD
Assisted Workforce Information Blank = Has not received service
Services

Most Recent Date Received Self- YYYYMMDD
Blank = Has not received service
Service Workforce Information
Services

Most Recent Date Referred to
Support Services

Most Recent Date Received
Career Guidance (LVER)

Most Recent Date Received
Career Guidance (DVOP)

Most Recent Date Received
Career Guidance

Most Recent Date Received
Intensive Services (LVER)

Most Recent Date Received
Intensive Services (DVOP)

Most Recent Date Received
Intensive Services

Most Recent Date Received Staff YYYYMMDD
Blank = Has not received service
Assisted Services (LVER)

Most Recent Date Received Staff YYYYMMDD
Blank = Has not received service
Assisted Services (DVOP)

Additional Edit Checks

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65, if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

Data Elements Eliminated from Labor Exchange Reporting System

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Most Recent Date Received Staff YYYYMMDD
Blank = Has not received service
Assisted Services

Data
Element Name

Warning

Error Type

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 4 of 9

A. Most Recent Date Received Staff Assisted Workforce
Information Services is before the Date of Program
Participation or is after the Date of Exit.

A. Most Recent Date Received Self-Service Workforce
Information Services is before the Date of Program
Participation or is after the Date of Exit.

A. Most Recent Date Received Career Guidance (LVER) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Received Career Guidance (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Received Career Guidance is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Received Intensive Services (LVER) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Received Intensive Services (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Received Intensive Services is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Received Staff Assisted Services (LVER)
is before the Date of Program Participation or is after the Date
of Exit.

A. Most Recent Date Received Staff Assisted Services (DVOP)
is before the Date of Program Participation or is after the Date
of Exit.

A. Most Recent Date Received Staff Assisted Services is
before the Date of Program Participation or after the Date of
Exit.

ERROR MESSAGES

4/19/2006

Most Recent Date Referred to
Federal Training

Most Recent Date Referred to
Employment (LVER)

Most Recent Date Referred to
Employment (DVOP)

Most Recent Date Referred to
WIA Services

Most Recent Date Referred to
Employment

YYYYMMDD
Blank = Has not received service

Most Recent Date of Job Search YYYYMMDD
Blank = Has not received service
Activities (LVER)

YYYYMMDD
Blank = Has not received service

Most Recent Date of Job Search YYYYMMDD
Blank = Has not received service
Activities (DVOP)

Most Recent Date Received Job
Search Activities

Most Recent Date Referred to WIA
Services (LVER)

Most Recent Date Attended TAP YYYYMMDD
Employment Workshop (LVER) Blank = Has not received service

New
Element

Edit Checks - Valid Values
Additional Edit Checks

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

Data Element Eliminated from Labor Exchange Reporting System

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Most Recent Date Attended TAP YYYYMMDD
Employment Workshop (DVOP) Blank = Has not received service

Most Recent Date Referred to WIA
Services (DVOP)

New
Element

Data
Element Name

DRVS
Release 5.0
and later
Field No.

PY 04 DRVS
Field No.

Warning

Error Type

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 5 of 9

A. Most Recent Date Referred to Federal Training is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to Employment (LVER) is before
the Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to Employment (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Referred to Employment is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to WIA Services is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Received Job Search Activities (LVER) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Received Job Search Activities (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Received Job Search Activities is before
the Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Received TAP Employment Workshop
(LVER) is before the Date of Program Participation or is after
the Date of Exit.

A. Most Recent Date Received TAP Employment Workshop
(DVOP) is before the Date of Program Participation or is after
the Date of Exit.

ERROR MESSAGES

4/19/2006

DRVS
Release 5.0
and later
Field No.

PY 04 DRVS
Field No.

Most Recent Date Entered Into
Federal Job (LVER)

Most Recent Date Entered Into
Federal Job (DVOP)

Most Recent Date Entered Into
Federal Job

Most Recent Date Referred to
Federal Job (LVER)

Most Recent Date Referred to
Federal Job (DVOP)

Most Recent Date Referred to
Federal Job

Most Recent Date Placed in
Federal Training (LVER)

Most Recent Date Placed in
Federal Training (DVOP)

Most Recent Date Placed in
Federal Training

Most Recent Date Referred to
Federal Training (LVER)

Most Recent Date Referred to
Federal Training (DVOP)

Data
Element Name

YYYYMMDD
Blank = Has not received service

Additional Edit Checks

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Edit Checks - Valid Values

Warning

Error Type

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 6 of 9

A. Most Recent Date Entered Into Federal Job (LVER) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Entered Into Federal Job (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Entered Into Federal Job is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to Federal Job (LVER) is before
the Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to Federal Job (DVOP) is before
the Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to Federal Job is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Placed in Federal Training (LVER) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Placed in Federal Training (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Placed in Federal Training is before the
Date of Program Participation or is after the Date of Exit.

A. Most Recent Date Referred to Federal Training (LVER) is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Referred to Federal Training (DVOP) is
before the Date of Program Participation or is after the Date of
Exit.

ERROR MESSAGES

New
Element

4/19/2006

DRVS
Release 5.0
and later
Field No.

PY 04 DRVS
Field No.

Other Reasons for Exit

Date of Exit

Most Recent Date Entered Into
Federal Contractor Job (LVER)

Most Recent Date Entered Into
Federal Contractor Job (DVOP)

Most Recent Date Entered Into
Federal Contractor Job

Most Recent Date Referred to a
Federal Contractor Job (LVER)

Most Recent Date Referred to a
Federal Contractor Job (DVOP)

Most Recent Date Referred to a
Federal Contractor Job

Data
Element Name

01 = Institutionalized
02 = Health/Medical
03 = Deceased
04 = Family Care
05 = Reservists Called to Active Duty
98 = Retirement
99 = Invalid SSN
00 or Blank = Participant Has Not Exited or Exited for
Reason Other Than One of Conditions Listed Above

YYYYMMDD
Blank = Has not exited

YYYYMMDD
Blank = Has not received service

Additional Edit Checks

A. Reject
B. Reject

B. Must be blank, 00, or 99 if field 65 (Date of Exit) is blank.

B. Reject

A. Must be blank, 00, 01, 02, 03, 04, 05, 98, or 99.

A. Reject

B. Must not be blank if field 66 (Other Reasons for Exit) is 01 , 02, 03, 04, or
05.

Warning

Error Type

A. Must be blank or >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

B. Must be <= field 65 if field 65 (Date of Exit) is not blank.

A. Must be >= field 5 (Date of Program Participation).

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Edit Checks - Valid Values

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 7 of 9

A-B. Error in Other Reasons for Exit field caused by one of the
following conditions:
- Other Reasons for Exit value is invalid.
- Other Reasons for Exit is specified (01 - 06), but no Date of
Exit is given.

A. Date of Exit must be greater than or equal to the Date of
Program Participation, and cannot be blank if Other Reasons
for Exit is 01 - 06.

A. Most Recent Date Entered Into a Federal Contractor Job
(LVER) is before the Date of Program Participation or is after
the Date of Exit.

A. Most Recent Date Entered Into a Federal Contractor Job
(DVOP) is before the Date of Program Participation or is after
the Date of Exit.

A. Most Recent Date Entered Into a Federal Contractor Job is
before the Date of Program Participation or is after the Date of
Exit.

A. Most Recent Date Referred to a Federal Contractor Job
(LVER) is before the Date of Program Participation or is after
the Date of Exit.

A. Most Recent Date Referred to a Federal Contractor Job
(DVOP) is before the Date of Program Participation or is after
the Date of Exit.

A. Most Recent Date Referred to a Federal Contractor Job is
before the Date of Program Participation or is after the Date of
Exit.

ERROR MESSAGES

DRVS
Release 5.0
and later
Field No.

New
Element

4/19/2006

New
Element

Employment Outcomes

PY 04 DRVS
Field No.

Type of Employment Match 2nd
Quarter After Exit Quarter

Employed in 2nd Quarter after
Exit Quarter

Type of Employment Match 1st
Quarter After Exit Quarter

Employed in 1st Quarter after
Exit Quarter

Data
Element Name
Additional Edit Checks

Reject

Error Type

C. Must be 6 if field 76 is 999999.99

B. Must be 5, 0 or blank if field 76 is 0 or blank.

A. Must be 1-4 if field 76 (Wages 2nd Quarter After Exit Quarter) is >0 and less Reject
than 999999.99.

E. Must be 3 if field 65 (Date of Exit) is blank.

D. Must not be 3 if report quarter is 4 or more quarters after the exit quarter

C. Must be 3 if field 70 is 6.

B. Must be 2 if field 70 is 0 or blank.

A. Must be 1 if field 70 (Type of Employment Match 2nd Quarter After Exit
Quarter) is 1-5.

C. Must be 6 if field 75 is 999999.99

B. Must be 5, 0 or blank if field 75 is 0 or blank.

A. Must be 1-4 if field 75 (Wages 1st Quarter After Exit Quarter) is >0 and less
than 999999.99.

E. Must be 3 if field 65 (Date of Exit) is blank.

D. Must not be 3 if report quarter is 3 or more quarters after the exit quarter

C. Must be 3 if field 68 is 6.

B. Must be 2 if field 68 is 0 or blank.

A. Must be 1 if field 68 (Type of Employment Match 1st Quarter After Exit
Quarter) is 1-5.

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

1 = UI Wage Records (In-State & WRIS)
2 = Federal Employment Records (OPM, USPS)
3 = Military Employment Records (DOD)
4 = Other Administrative Wage Records
5 = Supplemental through case management,
participant survey, and/or verification with the employer
6 = Information not yet available
0 or blank = Not employed

1 = Yes
2 = No
3 = Information not yet available

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Edit Checks - Valid Values

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 8 of 9

A-C. The value for Type of Employment Match 2nd Quarter
After Exit Quarter does not meet one of the following
conditions:
- Type of Employment Match 2nd Quarter After Exit Quarter
must be 1-4 (Wage or Employment Records) if Wages is >0.
- Type of Employment Match 2nd Quarter After Exit Quarter
must be 5, blank or 0 (Supplemental or Not Employed) if
Wages is blank or 0.
- Type of Employment Match 2nd Quarter After Exit Quarter
must be 6 (Information Not Yet Available) if Wages are
999999.99 (Not Yet Available).

A-E. Error in Employed in 2nd Quarter After Exit Quarter field
caused by one of the following conditions:
- Employed in 2nd Quarter After Exit Quarter must be 1 (Yes) if
Type of Employment Match is 1-5 (Wage records, Employment
Records, or Supplemental).
- Employed in 2nd Quarter After Exit Quarter must be 2 (No) if
Type of Employment Match is blank or 0 (Not Employed).
- Employed in 2nd Quarter After Exit Quarter must be 3
(Information Not Yet Available) if Type of Employment Match is
6 (Information Not Yet Available).
- Employed in 2nd Quarter After Exit Quarter must be 3
(Information Not Yet Available) if Date of Exit is blank.
- Employed in 2nd Quarter After Exit Quarter cannot be 3
(Information Not Yet Available) if report quarter is 4 or more
quarters after exit quarter.

A-C. The value for Type of Employment Match 1st Quarter
After Exit Quarter does not meet one of the following
conditions:
- Type of Employment Match 1st Quarter After Exit Quarter
must be 1-4 (Wage or Employment Records) if Wages is >0.
- Type of Employment Match 1st Quarter After Exit Quarter
must be 5, blank or 0 (Supplemental or Not Employed) if
Wages is blank or 0.
- Type of Employment Match 1st Quarter After Exit Quarter
must be 6 (Information Not Yet Available) if Wages are
999999.99 (Not Yet Available).

A-E. Error in Employed in 1st Quarter After Exit Quarter field
caused by one of the following conditions:
- Employed in 1st Quarter After Exit Quarter must be 1 (Yes) if
Type of Employment Match is 1-5 (Wage records, Employment
Records, or Supplemental).
- Employed in 1st Quarter After Exit Quarter must be 2 (No) if
Type of Employment Match is blank or 0 (Not Employed).
- Employed in 1st Quarter After Exit Quarter must be 3
(Information Not Yet Available) if Type of Employment Match is
6 (Information Not Yet Available).
- Employed in 1st Quarter After Exit Quarter must be 3
(Information Not Yet Available) if Date of Exit is blank.
- Employed in 1st Quarter After Exit Quarter cannot be 3
(Information Not Yet Available) if report quarter is 3 or more
quarters after exit quarter.

ERROR MESSAGES

New
Element

4/19/2006

79, 80

76 -78

DRVS
Release 5.0
and later
Field No.

PY 04 DRVS
Field No.

User Field 2

User Field 1

Case Manager

Office Name

WIB Name

Wages 4th Quarter After
Registration Quarter
Employer Identification Number

Wages 3rd Quarter After Exit
Quarter

Wages 2nd Quarter After Exit
Quarter

Wages 1st Quarter Prior to
Registration Quarter
Wages 1st Quarter After Exit
Quarter

Wages 2nd Quarter Prior to
Participation Quarter

Wages 3rd Quarter Prior to
Participation Quarter

Type of Employment Match 3rd
Quarter After Exit Quarter

Employed in 3rd Quarter after
Exit Quarter

Data
Element Name

Alphanumeric - 75 characters maximum

000000.00
Blank = Does not apply

Additional Edit Checks

B. Must be <=100000.00 or = 999999.99.

A. Must be >=0 and <= 999999.99, or blank.

B. Must be <=100000.00 or = 999999.99.

A. Must be >=0 and <= 999999.99, or blank.

C. Must be 6 if field 77 is 999999.99

B. Must be 5, 0 or blank if field 77 is 0 or blank.

A. Must be 1-4 if field 77 (Wages 3rd Quarter After Exit Quarter) is >0 and less
than 999999.99.

E. Must be 3 if field 65 (Date of Exit) is blank.

D. Must not be 3 if report quarter is 5 or more quarters after the exit quarter

C. Must be 3 if field 72 is 6.

B. Must be 2 if field 72 is 0 or blank.

A. Must be 1 if field 72 (Type of Employment Match 3rd Quarter After Exit
Quarter) is 1-5.

(all references refer to new
DRVS field numbers)

Edit Check Logic

DRVSLX-JS-ImportFile-EditChecks-041906.xls

Not Applicable. User defined field.

Data Elements Eliminated from Labor Exchange Reporting System

Data Element Eliminated from Labor Exchange Reporting System

B. Must be <=50000.00 or = 999999.99.

A. Must be >=0 and <= 999999.99, or blank.

B. Must be <=50000.00 or = 999999.99.

A. Must be >=0 and <= 999999.99, or blank.

B. Must be <=50000.00 or = 999999.99.

A. Must be >=0 and <= 999999.99, or blank.

Data Element Eliminated from Labor Exchange Reporting System

1 = Yes
2 = No
3 = Information not yet available

(DRVS will identify invalid codes and display, where appropriate,
warning errors for each field.)

Edit Checks - Valid Values

A. Reject
B. Warning

Reject

Error Type

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

Page 9 of 9

A. Wages 3rd Quarter After Exit Quarter are invalid.
B. Wages 3rd Quarter After Exit Quarter cannot be > 50000.

A. Wages 2nd Quarter After Exit Quarter are invalid.
B. Wages 2nd Quarter After Exit Quarter cannot be > 50000.

A. Wages 1st Quarter After Exit Quarter are invalid.
B. Wages 1st Quarter After Exit Quarter cannot be > 50000.

A. Wages 2nd Quarter Prior to Participation are invalid.
B. Wages 2nd Quarter Prior to Participation cannot be >
100000.

A. Wages 3rd Quarter Prior to Participation are invalid.
B. Wages 3rd Quarter Prior to Participation cannot be >
100000.

A-C. The value for Type of Employment Match 3rd Quarter
After Exit Quarter does not meet one of the following
conditions:
- Type of Employment Match 3rd Quarter After Exit Quarter
must be 1-4 (Wage or Employment Records) if Wages is >0.
- Type of Employment Match 3rd Quarter After Exit Quarter
must be 5, blank or 0 (Supplemental or Not Employed) if
Wages is blank or 0.
- Type of Employment Match 3rd Quarter After Exit Quarter
must be 6 (Information Not Yet Available) if Wages are
999999.99 (Not Yet Available).

A-E. Error in Employed in 3rd Quarter After Exit Quarter field
caused by one of the following conditions:
- Employed in 3rd Quarter After Exit Quarter must be 1 (Yes) if
Type of Employment Match is 1-5 (Wage records, Employment
Records, or Supplemental).
- Employed in 3rd Quarter After Exit Quarter must be 2 (No) if
Type of Employment Match is blank or 0 (Not Employed).
- Employed in 3rd Quarter After Exit Quarter must be 3
(Information Not Yet Available) if Type of Employment Match is
6 (Information Not Yet Available).
- Employed in 3rd Quarter After Exit Quarter must be 3
(Information Not Yet Available) if Date of Exit is blank.
- Employed in 3rd Quarter After Exit Quarter cannot be 3
(Information Not Yet Available) if report quarter is 5 or more
quarters after exit quarter.

ERROR MESSAGES

APPENDIX C.
JOB OPENING RECORD LAYOUT AND EDITS
The following table lists the field number, field name, valid values, edit checks,
and error messages for every field in the DRVS record layout for job openings.
The functionality to view record layouts through the software by selecting Import/
Source Table Record Layout will be provided in a future release. See Chapter III
for detailed instructions for preparing the job opening import file using the record
layout. Also see Appendix A for the reporting schedule and the date ranges of job
openings to be included in each quarterly import file.

New
DRVS
Release 5.0
and later
Field No.

7
8
9

10
11

7
7,8
8

9
9

4/19/2006

Job Opening Information

Current
DRVS
Field No.

User Field 1
User Field 2

WIB Name
Office Name
Case Manager

(all references refer to new
DRVS field numbers)

Edit Check Logic

Additional Edit Checks

A. Mandatory field in DRVS version 5.0 and later.

B. Must be unique for each record.

A. Mandatory field in DRVS version 5.0 and later.

Small Integer - 2 characters maximum: No additional edit checks.
11,21,22,23,31,32,33,42,44,45,48,49,51,
52,53,54,55,56,61,62,71,72,81,92

Small Integer - 2 characters maximum: No additional edit checks.
11,13,15,17,19,21,23,25,27,29,31,33,35,
37,39,41,43,45,47,49,51,53,55

Alphanumeric - 4 characters maximum: No additional edit checks.
FCJL
or blank

Numeric - YYYYMMDD

Numeric - 000000000
(No hyphens)

(DRVS will identify invalid codes and display,
where appropriate, warning errors for each
field.)

Edit Checks - Valid Values

DRVSLX-9002E-ImportFile-EditChecks-041906.xls

Alphanumeric - 75 characters maximum Not Applicable. User defined field.
Alphanumeric - 75 characters maximum Not Applicable. User defined field.

Alphanumeric - 75 characters maximum Not Applicable. User defined field.
Alphanumeric - 75 characters maximum Not Applicable. User defined field.
Alphanumeric - 75 characters maximum Not Applicable. User defined field.

Employer Identification Number Alphanumeric - 75 characters maximum No additional edit checks.

NAICS Code

O*NET SOC Code

Employer Type

Date Received Job Opening

Observation Number

Data
Element Name

Reject

Page 1 of 1

Error Type

IMPORTANT NOTE: This document contains data element specifications and edit checks that will be used to support implementation of the Employment and Training
Administration's (ETA) Data Reporting and Validation Software (DRVS) Release 5.0 and later for Labor Exchange programs. DRVS for Labor Exchange programs was
upgraded to support state implementation of common performance measures and other revised reporting requirements approved by the United States Office of Management
and Budget (OMB) beginning PY2005. A crosswalk of the import file field numbers from the current DRVS to the new DRVS Release 5.0 and later is also provided.

LABOR EXCHANGE PROGRAMS
Import File Specifications & Edit Checks

Data Reporting and Validation Software (DRVS) Release 5.2

APPENDIX D. PERFORMANCE GROUPS
The attached table specifies the LX performance outcome groups.

Group A

Group B

Date of Exit
3&4 qtrs prior to
report qtr
3&4 qtrs prior to
report qtr
3&4 qtrs prior to
report qtr
3&4 qtrs prior to
report qtr
3&4 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr
5&6 qtrs prior to
report qtr

Group

Emp

UnEmp

Emp

UnEmp

Emp

UnEmp
UnEmp

Emp

UnEmp

Emp

Emp
Emp

UnEmp

Emp

UnEmp

Emp

Emp
qtr+1

Emp Status
at Part
UnEmp

Supp

Wage

N/A

Supp

Wage

Supp

Wage

N/A

Supp

Wage

Source of
Emp qtr+1

UnEmp

Emp

UnEmp

Emp

N/A

UnEmp

Emp

UnEmp

Emp

Pend

N/A

Pend

Emp qtr+2 &
qtr+3

N/A

Supp

Wage

N/A

Supp

Wage

N/A

Supp

Wage

N/A

Supp

Wage

Pend

N/A

Pend

Source of Emp
qtr+2 & qtr+3

Other Reasons
for Exit

Yes

EER
Num

Yes

EER
Den

TABLE C-1: PERFORMANCE OUTCOME GROUPS TABLE FOR EER, RETENTION, AND EARNINGS

Yes

Pend

ERR
Num

Yes

Pend

Yes

ERR
Den Earn

Group C

Group D

Date of Exit
7&8 qtrs prior to
report qtr
7&8 qtrs prior to
report qtr
7&8 qtrs prior to
report qtr
7&8 qtrs prior to
report qtr
7&8 qtrs prior to
report qtr
7&8 qtrs prior to
report qtr
7&8 qtrs prior to
report qtr
3 to 6 qtrs prior to
report qtr
3 to 8 qtrs prior to
report qtr

Group

N/A

Emp

N/A

UnEmp

Emp

N/A
N/A

Emp

N/A

Emp

Emp
qtr+1

Emp Status
at Part
N/A

N/A

Supp

Wage

Source of
Emp qtr+1

N/A

UnEmp

Emp

UnEmp

Emp

Emp qtr+2 &
qtr+3

N/A

Supp

Wage

N/A

Supp

Wage

Source of Emp
qtr+2 & qtr+3

Yes

Other Reasons
for Exit

EER
Num

EER
Den

Yes

ERR
Num

Yes

ERR
Den Earn

APPENDIX E. CLIENT SERVER SETUP
Following are client server setup instructions. It is recommended that the
state’s Database Administrator (DBA) perform all of the client server setups
tasks. Client server only recommended to those users who have full SQL
Server with Enterprise Manager.
Server Side
1.

Install the DRVS.
Server databases.

DBA must have administrative rights to SQL

After install is completed, open Enterprise Manager and find the
instance where databases were installed. Click on Databases
directory and find the master database. In the master database, rightclick on Users and select New Database User. Give client(s) log-on
capability by adding each client login name and giving them public
permission database role. Click OK after each client is added.

APPENDIX E. CLIENT SERVER SETUP

Create a shared folder on the server (i.e. C:\Temp) giving full
control security permissions to clients.

Copy and paste the FormatFiles folder, which is located in the
application directory (default location - C:\Program
Files\DRVS), to the shared folder (i.e C:\Temp\FormatFiles).

Before beginning DRVS installation on client side, the installer
must know the IP address of the server. This will be needed to
connect clients to the server.

APPENDIX E. CLIENT SERVER SETUP
Client Side
1. Begin installation of the DRVS. Proceed with normal installation until
reaching the SQL Server Connection page. In the SQL Server Name
box, type in the server’s IP address. For Database Authentication
select Windows NT Authentication. Click Next.

APPENDIX E. CLIENT SERVER SETUP
2. After clicking Next, in the “Do you want to install the DRVS Database?”
page, select “I DO NOT want to create a DRVS database.” Click
Next.

3. The rest of the installation should proceed normally. You might receive
an error saying that the login failed for the user (the user is expressed in
the error as the computer name of the user). Click OK on the error and
continue. This will not affect the installation on the client side.

APPENDIX E. CLIENT SERVER SETUP
4. After installation is complete, you must map a network drive from the
client to the shared folder on the server. To do this, open Explorer and
click Tools>>Map Network Drive. Select the name of your drive in the
Drive box and then click Browse to find the servername\folder that is
shared. This is how the file on the client side is copied and loaded onto
the server database. Click Finish once the folder is found.

5. Go to the install directory and find the WIAnLXApplication.config file
(the default location is C:\Program Files\DRVS\WIAnLX\bin\Config).
Right-click on the file and remove the Read-Only attribute in Properties.

6. In the config file, the DestinationDir, FileUploadPath, and
FormatFilePath must be changed to the server’s paths.
The
DestinationDir path is changed to the mapped drive path to the server.
For example, if the shared directory on the server is C:\Temp and that
was mapped on the client as the F: drive, the DestinationDir would look
like this in the config file—F:\—with
F: being the mapped drive to server C:\Temp directory.
The
FileUploadPath is the name of the server shared directory.

APPENDIX E. CLIENT SERVER SETUP
In our example it would look like this –
C:\Temp\.
The FormatFilePath would be the directory on the server where the
FormatFiles folder is located. In our example that folder is located in
C:\Temp so that would look like this in the config file:
C:\Temp\FormatFiles\.
After each path is changed, save the file. Below is an example of the
config file after making the changes.

Please note that the path name must always end with a slash.
7. After each step is complete for each client, the users are ready to load
their files.

APPENDIX F. TROUBLESHOOTING
This chapter provides solutions for common problems that may occur during
DRVS signing in and preparing and importing record.
A. Signing In
Following are solutions for three problems that may occur at sign in:
1. If the default User ID and Password are properly entered, but the DRVS
generates a critical error with the message: “Object reference not set to an
instance of an object”, then the user may have entered the wrong server
name in the SQL Server Connection screen/SQL Server Name box during
the installation. The Installation Wizard would have finished if any one of
the state’s correct server names was entered in that field. However, if the
appropriate server name for the DRVS installation was not entered, the
problem would appear at log in. To correct the problem, uninstall the DRVS
and then repeat the installation, ensuring that the correct server name is
entered. The “Object reference not set to an instance of an object” error may
also appear if the user does not have read/write access to the DRVS
installation folder. The user must have these rights to log in to the DRVS.

2. If the default User ID and Password are properly entered, but the DRVS
generates the message: “Event Log is Full” and quits, the user needs to clear
the event logs in the following way:
• Click on Start - Settings - Control Panel.
• Double click Administrative Tools, then Event Viewer.
• On the left side of the Event Viewer window, you will see three
logs listed.
• Right click on each of these logs separately and click on “Clear all
events.”

100

APPENDIX F. TROUBLESHOOTING
• As you clear these logs, the system may ask if you want to save
them. Click “No.”

3. If the default User ID and Password are properly entered, but the DRVS
generates the message: "Login failed for user 'DRVS User'. Reason: not
associated with a trusted SQL Server connection.", then the user needs to
update the registry setting. The error message will appear in red on the
Login screen.

101

APPENDIX F. TROUBLESHOOTING
The system will also register the following critical error in the error log:

Event ID: STOREDPROCEDURE_EXECUTION_ERROR
Error Message: System.Data.SqlClient.SqlException: Login failed for user
'DRVSUser'. Reason: Not associated with a trusted SQL Server connection.
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean&
isInTransaction)
at
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection
(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.OpenConnection()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteReader
(DBCommandWrapper command)
at WIAnLXControlLib.frmLogon.btnLogin_Click(Object sender,
EventArgs e)
Error executing the stored procedure. Stored Procedure Name =
spGetApplicationUser

102

APPENDIX F. TROUBLESHOOTING
MSDE users must update the registry setting as follows:
Select Start, Run, and in the Open box in the Run window type "regedit".
Click OK. This opens the Registry Editor. Drill down to the following
folder:
HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/MSSQLServer/
MSSQLServer
Double click on the LoginMode file. This opens the Edit DWORD Value
box. In the Value data box change the value from 1 to 2. Confirm that
Hexadecimal is selected in the Base box. Then click OK.

Reboot the PC and then reopen the DRVS. If the Login fails again, then the
user does not have the proper administrative rights to run the DRVS.

103

APPENDIX F. TROUBLESHOOTING
SQL Server users must update the registry setting as follows:
Open SQL Server Enterprise Manager and drill down to the SQL Server
Group, then right click the server name entered in step 11 of the installation.
Choose Properties from the menu displayed. This will open the SQL
Server Properties (Configure) window for the selected server. Click on the
Security tab. Under Authentication, select SQL Server and Windows. Click
OK.

You may be asked to restart SQL Server Service. Click Yes. Reboot the PC
and then reopen the DRVS. If the Login fails again, then the user does not
have the proper administrative rights to run the DRVS.

104

APPENDIX F. TROUBLESHOOTING
B. Preparing and Importing Records
Common File Errors
As described in Chapter III, section B, each record in the state extract files
for job seekers and job openings must have the specified number of fields
corresponding to the record layouts in Appendices B and C. Files that
contain records with too many or too few fields will cause a critical error
during file processing. In such cases, the DRVS log file will contain an
error message similar to the following:
Event ID: STOREDPROCEDURE_EXECUTION_ERROR
Error Message: System.Data.SqlClient.SqlException: Bulk Insert:
Unexpected end-of-file (EOF) encountered in data file.
…
Cannot Load. Error in file or error executing the stored procedure.
Stored Procedure Name = spBCPFile

Records that contain improper values in date fields due to typographical or
other date format errors (e.g., 22040112, 2004112, or 011204) may cause a
critical error during file processing. In such cases, the DRVS log file will
contain an error message similar to the following:
Event ID: STOREDPROCEDURE_EXECUTION_ERROR
Error Message: System.Data.SqlClient.SqlException: The conversion
of char data type to smalldatetime data type resulted in an out-of-range
smalldatetime value.
…
Cannot Load. Error in file or error executing the stored procedure.
Stored Procedure Name = spBCPFile

In each case listed above, the data error must be corrected in the file before
the file will be accepted by the software.

105

File Type	application/pdf
File Title	Microsoft Word - DRVS LX Users Guide 101806.doc
Author	GRoemer
File Modified	2006-11-13
File Created	2006-10-19