Maintained for Historical Purposes

This resource is being maintained for historical purposes only and is not currently applicable.

Switching from DOS to Windows and handling the ISIRs

PublicationDate: 8/14/96
Summary: Switching from DOS to Windows and handling the ISIRs
Author: CPS - Central Processing System (CPS)

To: EDE Destination Points
From: CPS Customer Service
Date: August 14, 1996
Re: Switching from DOS to Windows and handling the ISIRs


Destination points which switch from using 1996-97 EDExpress for DOS to 1996-97
EDExpress for Windows should import each ISIR file individually into the Windows
software. The message classes that must be imported are:

SARA97OP (and any SARA97BK files that were created by the DOS software renaming
a SARA97OP file)
EAPS97OP (and any EAPS97BK files that were created by the DOS software renaming
EAPS97OP file)
SARR97OP (and any SARR97BK files that were created by the DOS software renaming a
SARR97OP file)
DUPS97OP (and any DUPS97BK files that were created by the DOS software renaming a
DUPS97OP file)
RADD97OP (and any RADD97BK files that were created by the DOS software renaming
a RADD97OP file)

NOTE: Not all users will have files from all message classes.

The suggested method is to import each file currently with BK in the file name
sequentially from the most recent to oldest, and then the OP files. This is because some
records in the earlier batches will be skipped due to the reprocessing that occurred early
in the year.

For example, import:
SARA97BK.XXX (Where XXX is the highest numbered extension) .
.
.
SARA97BK.001
SARA97BK.DAT
SARA97OP.XXX (Where XXX is the highest numbered extension) .
.
.
SARA97OP.001
SARA97OP.DAT

As you import the OP files they will be renamed to BK. Therefore you will want to
import the BK files first to avoid importing the same file more than once. When all OP
files have been imported no files will appear on the pick list.

If you have any questions, please call CPS customer support at (800) 330-5947, option 3.