Satori ® Presort - Satori Software Inc.docs.satorisoftware.com/pst_rn_ss.pdf · Scalable...

Scalable Production Mailing Solutions

Simply Powerful

8.00c.15.00 - August 2014

Release NotesSatori® Presort

®Satori

Presort®

COPYRIGHT © 2014 SATORI SOFTWARE INC.

1301 5th Ave, Suite 2200

Seattle, WA 98101-2676

This manual and software are copyrighted by Satori Software Inc. All rights are reserved and neither manual nor software may be copied in any way without prior consent.

Satori and Satori Software are registered trademarks of Satori Software Inc. The Satori Software logo is a trademark of Satori Software Inc. in the United States and other countries.

The following trademarks are owned by the United States Postal Service: CASS™, CASS Certified™, DPV®, eLOT®, FASTforward®, First-Class Mail®, Intelligent Mail®, LACSLink®, NCOALink, Media Mail®, PAVE™, Post Office™, Postal Service™, PostalOne!®, POSTNET™, Standard Mail®, RDI, The Postal Service®, US Postal Service™, U.S. Postal Service®, USPS®, ZIPtm, ZIP Code™, ZIP + 4® and the United States Postal Service.

All other trademarks are the property of their respective owners.

V201409031021

1

ContentsWhat's new in this release? 3

Information about supported platforms 3

Satori Presort 8.00c.15.00 new features and updates 3

Monthly directory management 4

Auxiliary files 5

Auxiliary Files block (Presort) 6

Auxiliary Files block (ZIPCount) 11

Directory lifecycle 12

Directory filenames 13

Storing directories 14

Selecting the directory files 14

Presort can select the directories automatically 15

You can select the directories yourself 15

Which directories are valid for my mailing? 18

About estimated drop dates 20

Removing expired directories 23

Setting up multiple entry points in Presort Views 23

How Presort Views generates valid entry points 23

Creating entry point descriptions in chronological order 24

If the range of dates is too wide 26

"Forcing" Presort Views to select the same directories 26

IMb serial number tracking and assignment improvements 27

Serial number sequencing restarts for every job 27

Serial numbers can be unique for longer than 45 days 27

Excluding mail from FSS preparation 28

Exclude High Density and High Density Plus mail from FSS preparation 29

2

Turn off all FSS preparation 30

Specifying election mail or political mail content 30

Mail.dat changes 32

Mail.dat 14-2 32

Mail.dat 14-1 33

Postage Statement changes 34

Postage statement lengths 35

Other changes 35

DefMap and Edjob versions 35

Intelligent Mail™ Package Barcode (IMpb) Non-Compliance Update 35

Fixed issues 36

Using Presort during the transition period 37

Directory distribution from Satori Software 39

Downloading service packs and fix packs 40

Upgrading to Satori Presort 8.00c.15.00 41

Upgrading a Windows standalone, server, or Remote Views client 41

Post-installation tasks 42

Upgrading a Windows client 42

Upgrading a UNIX machine 42

Upgrading Remote Views 43

Running Edjob and patch scripts 44

Job file parameters that are added or changed by Edjob 44

Directory updates 47

Directory release schedule 47

Mail Direction files and labeling lists 47

Accessing Documentation 48

Contacting Satori Software Technical Support 49

3

What's new in this release?Satori Presort 8.00c.15.00 (Service Pack 15 or SP15) is a required release that supports the USPSSummer 2014Major PostalOne! Release changes that go into effect on September 7, 2014.

You can verify your mailingswith this release starting on August 24, 2014 when PostalOne! isdeployed, but you cannot submit them until September 7, 2014 when PostalOne! takes effect. (If youare usingMail.dat 14-1 with SP15, you can submit your mail starting August 24.) You can continueto use SP14 to process your jobs that will be entered before September 7, 2014.

Note: If you are strictly usingMail.dat 14-1 and generating postage statements from theMail.datfiles via PostalOne! or other means, you can continue to use SP14 until October 31. (Wewill provideSP14 compatible directories that contain date valid only throughOctober 31, 2014.)

See Important dates during the transition period for more information.

To access these release notes online, go to Satori Presort 8.00c.15.00 Release Notes.

Information about supported platformsWehave added support for the following platforms:

l Windows 8.0 Pro (32- and 64-bit)

l Windows 8.1 Pro (32- and 64-bit)

l WindowsServer 2012 (64-bit)

Important:Due to the discontinuation ofWindowsXP support byMicrosoft in April 2014, we areplanning to end support for Presort on theWindowsXP platform after the USPSWinter 2015MajorPostalOne! Release (in Q1 2015). The first release that will not support Presort on theWindowsXPplatformwill be the USPS Summer 2015Major PostalOne! Release (in Q3 2015).

Satori Presort 8.00c.15.00 new features and updatesThis release contains the following new features and updates

l Monthly directorymanagement

l IMb serial number tracking and assignment improvements

l Specifying electionmail or political mail content

l Excludingmail from FSS preparation

l The $datemacro is now available for the following parameters:

l AutoMatching/Coding Date

l CARTMatching/Coding Date

http://docs.satorisoftware.com/pst_rn_ss_1500.pdfl

4

l CART Sequencing Date

l LOT Database Date

l Simplified AddressDate

l MoveUpdate Date

l Mail.dat 14-2 and 14-1 Errata changes

l Postage Statement changes

l Other changes

l Fixed issues

Monthly directory managementThe USPS is now releasing data directory updates on amonthly basis. You will receive thedirectories around the second week of eachmonth prior to themonth that they become effective.

Presort has been enhanced tomanage themonthly directories. The process of selecting directorieshas changed significantly. Highlights include:

l You can choose to let Presort select the directories automatically or you can specify thedirectories you want to use yourself.

l Directories now have a lifecycle of threemonths.

l Directories are valid for twomonths.

l Directory filename structure has been updated to include the year andmonth of the firstmonth that they are valid.

l Directory validity is currently based on themailing verification date, but will be based onthe induction date in the next PostalOne! release (currently scheduled for November2014). The induction date in Presort is referred to as the "estimated drop date."

l If you drop ship, the estimated drop date is the day themailing is unloaded fromthe truck at the entry facility. Themail verification date is the date that theUSPS verifies and accepts themailing, which happens after the estimateddrop date.

l If you do not drop ship, themail verification and estimated drop dates are thesame. This change should not affect mailers who do not drop ship.

l Every entry point description requires an estimated drop date unless there is a defaultdate in the Entry Point Defaults block.

l Sequence of setting up entry point descriptions in Viewswhen Presort selects thedirectories automatically is critical.

5

Auxiliary files

With the software, you receive a set of supporting files that contain USPS data such as labeling lists,zone information, and facility information used for mail sortations.You will receive updated directoryfiles in themonth prior to when they become effective, and they are effective for twomonths. SeeDirectory lifecycle for more information.

The Auxiliary Files block is where you specify the locations of these files. Depending on how youspecify the path and filenames in theUSPS Presort Data Folder parameter and individualdirectory file parameters, Presort can select the directories automatically, or you can specify whichdirectories you want Presort to use. See Presort can select the directories automatically and Youcan select the directories yourself for more information.

This table contains information about the auxiliary files and how they are used.

Directoryname

Filename Applicablemailings

Purpose

ZIP-City File(ZCF) directory

YYMM_zcf.dir All mailings Can verify that zip codes are valid. Alsoused in sorting and labeling of 5 digitcontainers.

Mail ProcessingCenter (MPC)directory

YYMM_mpc.dir All mailings Contains information about the serviceareas of SCFs, ADCs, NDCs, and otherfacilities, which used for sortingmail and forforms and labels. Used in creatingcontainers and labeling using the USPSlabeling lists.

Zone directory YYMM_zone.dir PER, PSVCBPM, ParcelSelect

Determines the zone "distance" betweenentry and delivery point.

DeliveryStatistics File(DSF) directory

YYMM_dsf.dir Walk-sequencedmailings

Used for saturationmailings to check thenumber of stops to determine density wasmet for the saturation rate.

Facility directory YYMM_facility.dir All mailings Contains information about USPS drop shipfacilities, such as drop site keys, drop sitenames, and drop site delivery addresses.

Mail Directiondirectory

YYMM_maildirect.dir All mailings Used to determine wheremail should bedropped based on when the drop will occur,so that you can receive discounts.

Default Formatfile

<file>.fmt N/A Indicates to Presort the format file to use foryour input files if an FMT corresponding tothe input file is not found.

DefaultDefinition file

<file>.def N/A Indicates to Presort the definition file to usetomap input file fields to Presort fields if aDEF corresponding to the input file is notfound.

6

Auxiliary Files block (Presort)

Note: This block is required!

The Auxiliary Files block is where you specify the locations of the directory files, default format file,and default DEF file.

When specifying path and filenames, be sure to use the correct syntax for your operating system:

System Example locationWindows \ss\dirs

UNIX ss/dirs

Directory files

Presort can select the directories automatically, or you can specify which directories you wantPresort to use, depending on how you specify the path and filenames in the following parameters:

USPS Presort Data Folder (See Note).. =

ZCF Directory ([path]YYMM_zcf.dir)... =

Mail Proc Ctr Dir([path]YYMM_mpc.dir) =

PER/PSVC Zone Dir([path]YYMM_zone.dir)=

PER/STD Del Stats([path]YYMM_dsf.dir) =

MailDirect.([path]YYMM_facility.dir). =

MailDirect.([path]YYMM_maildirect.dir)=

See Selecting the directory files for more information.

Default format and definition files

The following parameters are used to specify the default format and definition files:

Default Format (path & file.fmt)..... =

Default DEF (path & file.def)........ =

See "Default Format and Default DEF parameters" in the Job File Reference for more information.

USPS Presort Data Folder parameter

This parameter is used to specify the path to the folder that contains the directories to use to processyour job.


7

Depending on whether you choose to let Presort select the directories automatically(recommended), or you select them yourself, enter the path to the folder or leave this parameterblank:

l If you want Presort to select the correct directories automatically, enter the pathto the folder into this parameter. Leave the individual filename parameters blank. Presortcan only select directories for you from one folder.

l If you want to specify the directories to use yourself and they are all located inthe same folder, enter the path to the folder into this parameter. Enter the filename ofeach directory into the individual filename parameters.

l If you want to specify the directories to use yourself and they are located indifferent folders, leave this parameter blank. Enter the full path and filename of eachdirectory into the individual filename parameters.

Note: We do not recommend storing directories in different folders. See "Storing Directories" in thePresort User Guide for more information.

Note: TheUSPS Presort Data Folder parameter and individual directory file parameters willaccept a relative path based on the current working directory. See Auxiliary Files block (Presort) forthe list of individual directory file parameters.

See Presort can select the directories automatically and You can select the directories yourself formore information.

ZCF Directory parameter

The ZIP City File (ZCF) directory can verify that zip codes are valid. It is also used in sorting andlabeling of 5-digit containers.

This parameter is located in the Auxiliary Files block and is used to specify the path and/or filenameof the ZCF directory ([path]YYMM_zcf.dir).


Depending on whether you choose to let Presort select the directories automatically(recommended) or you select them yourself, leave this parameter blank, enter just the filename, orenter the full path and filename of the directory.

Note: This parameter will accept a relative path based on the current working directory.


For Views only: In the Auxiliary Files window in Views, you can use theUse ZCF Path for allDirectories to duplicate the information from the ZCF Directory field, whether it is a full path andfilename or just a filename, into the remaining directory fields. The filenameswill be changed toreflect the respective directories and will have the samemonth and year as the ZCF Directory file. Ifthe ZCF Directory field is blank, clicking this button will clear any information in the remaining

8

directory fields. If these fields are already blank, nothing will be copied into them and theywill remainblank. See "Copying file paths in Views" in the Presort User Guide for more information.

The software verifies the internal date of the YYMM_zcf.dir file. If the data is current, the softwareprocesses your job. If it is not current, you will receive an error.

The Auxiliary Files section of the Job Summary report lists the file date and time, effective date, andfilename of the Presort directories that were used for thismailing. The USPS requires you to submitthemailing while all directories used are valid. The range of dates that youmust submit your mailingwithin appears on the job summary report just after the list of auxiliary files.

Mail Proc Ctr Dir parameter

This file contains information about SCFs, ADCs, NDCs, and other facilities used for sortingmailand for forms and labels. Used in creating containers and labeling using the USPS labeling lists.

This parameter is located in the Auxiliary Files block and is used to specify the path and/or filenameof theMPC directory ([path]YYMM_mpc.dir).





If you choose to create 5-digit-scheme containers, the software verifies the internal date of theYYMM_mpc.dir file. If the data is current, the software processes your job. If it is not current, youwill receive an error.


PER/PSVC Zone Dir parameter

The Zone directory is used for Periodicals, Package Services, Bound PrintedMatter, and ParcelSelect mailings.It determines the zone "distance" between entry and delivery point.

This parameter is located in the Auxiliary Files block and is used to specify the path and/or filenameof the Zone directory ([path]YYMM_zone.dir).


Depending on whether you choose to let Presort select the directories automatically

9

(recommended) or you select them yourself, leave this parameter blank, enter just the filename, orenter the full path and filename of the directory.



The software verifies the internal date of the YYMM_zone.dir file. If the data is current, thesoftware processes your job. If it is not current, you will receive an error.


+PER/STD Del Stats parameter

This directory is used for saturationmailings to check the number of stops to determine density wasmet for the saturation rate.

This parameter is located in the Auxiliary Files block and is used to specify the path and/or filenameof the Delivery Statistics directory ([path]YYMM_dsf.dir).





The software verifies the internal date of the YYMM_dsf.dir file. If the data is current, the softwareprocesses your job. If it is not current, you will receive an error.

The effective date of this directory is used to fill in the "For pieces bearing a simplified address enterdate of delivery statistics file or alternativemethod" field on the 3541, 3600 and 3602 postagestatements.


10

Mail Direction (facility.dir) parameter

This directory contains information about USPS drop ship facilities, such as site keys, site names,and site delivery addresses.

This parameter is located in the Auxiliary Files block and is used to specify the path and/or filenameof the Facility directory ([path]YYMM_facility.dir).





The software verifies the internal date of the YYMM_facility.dir file. If the data is current, thesoftware processes your job. If it is not current, you will receive an error.


Mail Direction (maildirect.dir) parameter

This directory is used to determine wheremail should be dropped based on when the drop willoccur, so that you can receive discounts.

This parameter is located in the Auxiliary Files block and is used to specify the path and/or filenameof theMail Direction directory ([path]YYMM_maildirect.dir).





The software verifies the internal date of the YYMM_maildirect.dir file. If the data is current,the software processes your job. If it is not current, you will receive an error.

11


Auxiliary Files block (ZIPCount)

BEGIN Auxiliary Files =====================Mail Proc Ctr Dir (Location & YYMM_mpc.dir).... =Mail Direction (Location & YYMM_facility.dir).. =Mail Direction (Location & YYMM_maildirect.dir) =Default ASCII FMT File (Location & <file>.fmt). =END

Mail Proc Ctr Dir (Location & YYMM_mpc.dir)

Contains information about SCFs, ADCs, NDCs, and other facilities used for sortingmail and forforms and labels. Also used in creating containers and labeling using the USPS labeling lists.

Type the name and location of theMail Processing Center Directory, for example:

l Windows: \ss\dirs\YYMM_mpc.dir

l UNIX: /ss/dirs/YYMM_mpc.dir

Mail Direction (Location & YYMM_facility dir)

Contains information about USPS drop ship facilities, such as site keys, site names, and site deliveryaddresses.

Type the location and file name of the Facility directory file, YYMM_facility.dir.

Mail Direction (Location & YYMM_maildirect.dir)

Used to determine wheremail should be dropped based on when the drop will occur, so that you canreceive discounts.

Type the location and file name of theMail Direction directory file, YYMM_maildirect.dir.

Default ASCII FMT File (Location & <file>.fmt)

Indicates to Presort the format file to use for your input files if a corresponding FMT file is not found.

If all your input files are in the same format, you do not need to create separate FMTs for each file.Create just one FMT file, and type its path and name on this line.

If you have input files that differ from the standard format, youmay create an individual FMT for theexceptions. ZIPCount looks for an individual FMT within the same directory and with the same basename as the input file. If one is found, it overrides the default FMT. You can use $JOB in thisparameter, which converts to the base job file name (without a path or extension).

12

Directory lifecycle

Directories have a three-month lifecycle, which is comprised of three phases:Notification, Active,and Outgoing. Directories are valid for mailingswith estimated drop dates that fall in either theActive phase orOutgoing phase for that directory release, which are during the second and thirdmonths of the lifecycle.

Notification phase

During the first month, the directories will be available around the second week of themonth so youcan review the upcoming changes and plan for mailingswith estimated drop dates that fall within thenext twomonths. The directories cannot be used for estimated drop dates in that month.

Active phase

During the secondmonth, the directories become effective on the first day of themonth and are validto use for mailingswith estimated drop dates in that month and the next month. This is the preferreddirectory set to use for mailing dates that fall within that month.

Outgoing phase

During the third month, the directories are valid to use only for estimate drop dates in that month andexpire at the end of that month. There is a newer set of data files in a different release that are inactive phase, but files in the outgoing phase are acceptable to use for mailingswith estimated dropdates in that month.

Example

The following example demonstrates the lifecycle for USPS Release 5, also referred to as the"September directories." These directories can only be used for estimated drop dates that fall inSeptember andOctober. The filename structure for each of the “September directories” will be1409_<directory>.dir. (See Directory filenames for information about the directory filenamestructure.)

l In August, the "September directories" in Release 5 are in theNotification phase andcannot be used for estimated drop dates in August. They can be used for estimated dropdates in September andOctober.

l In September, the "September directories" in Release 5 are in theActive phase and thedirectories can be used for estimated drop dates in September andOctober.

l In October, the "September directories" in Release 5 are in theOutgoing phase and thedirectories can still be used for estimated drop dates in October.

l In November, the "September directories" in Release 5 cannot be used because theywillbe expired byOctober 31. Either the "October directories" in Release 6 (1410_<directory>.dir) or "November directories" in Release 7 (1411_<directory>.dir) can be used for estimated drop dates that fall in November.

13

SeeWhich directories are valid for mymailing? for information about the directories that can be usedbased on your mailing's estimated drop date.

Directory filenames

Each directory file is uniquely namedwith a filename structure of YYMM_<directory>.dir. The prefixYYMM represents the year andmonth that the directory file first becomes effective. See Directorylifecycle for more information about when directories can be used for mailings.

Each file in a directory set for a givenmonth will have the same YYMMprefix. For example, theOctober 2014 directories are named as follows:

Directory name FilenameZIP-City File (ZCF) directory 1410_zcf.dirMail Processing Center (MPC) directory 1410_mpc.dirZone directory 1410_zone.dirDelivery Statistics File (DSF) directory 1410_dsf.dirFacility directory 1410_facility.dirMail Direction directory 1410_maildirect.dir

The YYMMprefix allows for chronological sorting of files within a folder so that all of the directoryfiles for one set will appear together. This is handywhen you are browsing to identify a specificdirectory when selecting the directories to use yourself. Because the filenames are unique, you canstore all directory files in one folder without risk of overwriting any files.

14

See Selecting the directory files for a list of the jobfile parameters that are used to specify thedirectory files.

Storing directories

Because each directory filename is unique, all directory files can be stored together in the samefolder, which we highly recommend. The ...\ss\dir folder is the default directory location.

At any given time, there are three sets of directories that are available to use for your mailing:Notification, Active, andOutgoing.Wehighly recommend storing these three directory sets in thesame folder. When allowing Presort to select the directories automatically, Presort will look fordirectories only in the folder you specify in theUSPS Presort Data Folder parameter. Presort willnot search for directories in other folders. See Directory lifecycle for more information about whendirectories are valid to use.

Keeping all directories in the same folder will allow Presort to find the appropriate directories to usefor your mailing. If you are selecting the directories yourself, this will make finding the appropriatedirectories easier. See Presort can select the directories automatically and You can select thedirectories yourself for more information about specifying the directories to use.

There is no automated way to "clean out" the directories from this folder that are no longer valid andexpired. Directories will continue to accumulate in this location until youmanually delete or removethem. See Removing expired directories for guidelines on removing expired directory files that youno longer use.

Selecting the directory files

To select the directory files, use the following parameters in the Auxiliary Files block.








See Auxiliary Files block (Presort) for specific information about these parameters.

You can configure Presort to select the directories automatically (recommended), or you can specifythe directory files yourself (default behavior). This depends on how you populate these parameters.See Presort can select the directories automatically and You can select the directories yourself formore information.

15

Presort can select the directories automatically

You can configure Presort to select the directories automatically. This is the recommendedmethodof selecting directories to ensure that correct oneswill always be used. Presort will select the correctdirectories based on the estimated drop dates of your mailing. SeeWhich directories are valid for mymailing? for details on how the correct directories for your mailing are determined.

To configure Presort to select the directories:

1. Specify the folder path and filename of where the directories are located in theUSPSPresort Data Folder parameter in the Auxiliary Files block. Presort will look for andchoose the correct directories from this folder. See USPS Presort Data Folder parameterfor details about this parameter.

2. Leave all of the individual directory file parameters blank. If these parameters arepopulated with any path and/or filenames, Presort will use those directories.

Note: In Views, you can quickly remove any existing information from the individualdirectory file parameters by using theUse ZCF Path for all Directories button. SeeCopying file paths in Views for more information.

Valid filesmust be located in the folder specified in theUSPS Presort Data Folder parameter thatmatch the filenamesPresort expects to find. If the files cannot be found, Presort will error. Presortwill not search any other location for the files. We highly recommend that you download and installthe latest directories everymonth to ensure that valid directories are always available. See Storingdirectories for more information.

When a file like the Zone directory (YYMM_zone.dir) or the Delivery Statistics File (DSF) directory(YYMM_dsf.dir) is not required for your job, such as StandardMail not using zones or a non-CARTmailing that doesn’t use delivery statistics, those directory files do not have to be present inthe folder specified in theUSPS Presort Data Folder parameter.

To specify the directories to use yourself, see You can select the directories yourself.

You can select the directories yourself

If you prefer, you can select the directories to use yourself. However, the process of determiningwhich directories are valid to use for your mailing is complex, especially when there are multipleestimated drop dates andmultiple entry points (See "Multiple entry points" in the Presort UserGuide.We recommend letting Presort choose the directories automatically to ensure that the correctdirectories are always used. (See Presort can select the directories automatically.)

To select the directories yourself, youmust first determine the correct directories to use. Thedirectories you specifymust be within the effective date range of the estimated drop dates. SeeWhich directories are valid for mymailing? for assistance in determining the correct directories touse.

Important: If you only run a job occasionally, you should verify each time that the directoriesspecified are valid. If you need to specify new directories, you will need to set up all of your entrypoints again using those new directories.

16

When selecting the directories, we highly recommend that you use directories that are all for thesamemonth, which all start with the same YYMM prefix.

You specify the directories to use by populating parameters in the Auxiliary Files block. The way youpopulate the parameters depends on where the files are located, either all in the same folder or indifferent folders.

Note: TheUSPS Presort Data Folder parameter individual directory file parameters will accept arelative path based on the current working directory.

If you want to specify the directories to use yourself and they are located in the samefolder, enter the pathname of the folder that contains the directories into theUSPS Presort DataFolder parameter, and enter the appropriate filenamewith no path (YYMM_<directory>.dir)into each individual directory file parameter.

For example, to use the directories for themonth of October 2014 located in C:\ss\dirs, youwould populate the parameters like this:

USPS Presort Data Folder (See Note).. = C:\ss\dirsZCF Directory ([path]YYMM_zcf.dir)... = 1410_zcf.dirMail Proc Ctr Dir([path]YYMM_mpc.dir) = 1410_mpc.dirPER/PSVC Zone Dir([path]YYMM_zone.dir)= 1410_zone.dirPER/STD Del Stats([path]YYMM_dsf.dir) = 1410_dsf.dirMailDirect.([path]YYMM_facility.dir). = 1410_facility.dirMailDirect.([path]YYMM_maildirect.dir)= 1410_maildirect.dir

If you want to specify the directories to use yourself and they are located in differentfolders (this is not common, and not recommended), enter the appropriate full path and filename ofeach directory ([path]YYMM_<directory>.dir) into each parameter. Leave theUSPSPresort Data Folder parameter blank.

For example, to use some directories for themonth of October 2014, with some located inC:\ss\dirs, and some located in C:\ss\data_files, youmight populate the parameters likethis:

USPS Presort Data Folder (See Note).. =ZCF Directory ([path]YYMM_zcf.dir)... = C:\ss\dirs\1410_zcf.dirMail Proc Ctr Dir([path]YYMM_mpc.dir) = C:\ss\data_files\1410_mpc.dirPER/PSVC Zone Dir([path]YYMM_zone.dir)= C:\ss\dirs\1410_zone.dirPER/STD Del Stats([path]YYMM_dsf.dir) = C:\ss\dirs\1410_dsf.dirMailDirect.([path]YYMM_facility.dir). = C:\ss\data_files\1410_facility.dirMailDirect.([path]YYMM_maildirect.dir)= C:\ss\data_files\1410_maildirect.dir

Valid directory filesmust exist in the location you specify; Presort will not search for directory files inany other location. If Presort cannot find the directories it is looking for, Presort will error.

If one directory file parameter is filled in, all remaining directory file parametersmust also be filled in,except for thePER/STD Del Stats ([path]YYMM_dsf.dir) andPER/PSVC Zone Dir ([path]YYMM_zone.dir) parameters, which are optional for mailings that do not use these directories.Otherwise, you will receive an error.

17

Specifying directory files using Views

In Views, if you browse to select directories, theSpecify <directory name> Directorywindowappears with the File name field populated with the filename of the directory that Presort wouldselect. For example:

l If the job is set up with estimated drop dates ranging fromSeptember 20 to October 20,1409_zcf.dir (for September 2014) will appear in the file name field when browsingfor the ZCF directory.

l If there aremultiple valid directories, Presort will show the name of the one it would use ifit were going to choose (which will generally be the newest directory that would be valid).For example, if the estimated drop dates range fromOctober 8 to October 25, 1410_zcf.dir (for October 2014) will appear in the file name field when browsing for the ZCFdirectory.

Presort will not verify whether the directories are in the specified location(s); it will just suggest thename of the file to be used. If the file cannot be found, you will receive an error.

For ease in finding the correct directory files, we suggest that you sort them in descending numericalorder, so that the filenameswith the largest numbers appear at the top of the list, which are thenewest directory files. For example, 1410_zcf.dirwill appear above 1409_zcf.dir. Fromhere, you can easily find the directory files you are looking for.

Optionally, once you have entered information into the ZCF Directory field, you can quickly fill in theremaining directory fields by using theUse ZCF File Path for all Directories button. See Copyingfile paths in Views for more information.

Copying file paths in Views

In Views, once you have entered information into the ZCF Directory field, you can quickly fill in theremaining directory fields by using theUse ZCF File Path for all Directories button:

1. Open the Auxiliary window.

2. Enter the ZCF directory path and/or filename ([path]YYMM_zcf.dir or YYMM_zcf.dir).

3. ClickUse ZCF File Path for all Directories.

The information from the ZCF Directory field, whether it is a full path and filename or just a filename,will be duplicated in the remaining directory fields. The filenameswill be changed to reflect therespective directories and will be for the samemonth and year as the ZCF Directory file.

18

For example, if the ZCF Directory field containsC:\ss\dir\1501_zcf.dir, the remaining fields will bepopulated as shown:

If you enter just the filename in this parameter, only the filenameswill be populated in the individualdirectory fields. When there are only filenames specified in the directory parameters, the path to thefolder where the directory files are locatedmust be specified in theUSPS Presort Data Folderfield.

If the ZCF Directory field is blank, clickingUse ZCF File Path for all Directorieswill clear anyinformation in the remaining directory fields. If these fields are already blank, nothing will be copiedinto them and theywill remain blank.

This feature does not configure Presort to pick the directories automatically. It simply duplicates theinformation in the ZCF Directory field. If you want Presort to automatically select the directories, seePresort can select the directories automatically for more information.

This feature also does not verify whether the directories specified are valid, have the correctfilename, or exist in the specified location. Presort will not search for directories if the exact filesspecified cannot be found in the specified location. You will receive an error if Presort cannot locatethe files.

Related Topics

l You can select the directories yourself

Which directories are valid for my mailing?

Directories have a three-month lifecycle, however they are valid for mailingswith estimated dropdates that fall in the second twomonths of the lifecycle. Your mailings can use a given directory setonly if the estimated drop date falls within theActive orOutgoing phases for that directory release.For information about the three phases of a directory release and when a given directory set is validto use, see Directory lifecycle.

Presort selects the directories based on the estimated drop date of your mailing and will generallyuse theActive directories by default. If theActive directories are not available, Presort will attempt to

19

use the directories from the previousmonth (Outgoing) if they are valid for your mailing. Forexample, if the estimated drop dates are in September and no September directories are available,but August directories are, Presort will use the August directories automatically. (If neither directoryset is available, Presort will return an error.) In the cases of multiple estimated drop dates, orestimated drop dates falling near the beginning of themonth, the Active directoriesmay notnecessarily be the preferred directories to use.

Here are some guidelines for determining which directories should be used:

l In each calendar month, there are two sets of files that can be used for mailingswithestimated drop dates that fall within that month: Active directories from the currentmonth's release andOutgoing directories from the previousmonth's release.

l If there are two directories that are valid for your estimated drop date, we recommendusing the newer valid (Active) directories, but you can also use the previousmonth'sdirectories (inOutgoing status). If Presort is selecting the directories automatically, thenewer valid (Active) directories will be used. If those directories are not available, Presortwill use the previousmonth's (Outgoing) directories.

l If your job containsmultiple estimated drop dates that span over two consecutivemonths,the directories for the earlier month (inOutgoing status) are the only directories that arevalid for your mailing.

l If you are preparing amailing with an estimated drop date that falls in the upcomingmonth(in theNotification phase), both the upcomingmonth's directories (inNotification status)or the current month's directories (inActive status) are valid. If Presort is selecting thedirectories automatically, the upcomingmonth's directories (inNotification status) will beused. If those directories are not available, Presort will use the current month's directories(InActive status).

l If at least one estimated drop date is near the beginning of themonth, using the previousmonth's (Outgoing) directories provides flexibility in the actual date that you submit yourmailing. Youmay submit your mailing either in themonth prior to or in themonth of yourestimated drop date, because the previousmonth's (Outgoing) directories are valid forboth the previousmonth and the current month. If Presort is selecting the directoriesautomatically, the previousmonth’s (Outgoing) directories will be used by default. If thosedirectories are not available, Presort will use the current (Active) month's directories, butyou will not be able to submit your mailing before the first of themonth. If you prefer, youcan use the current (Active) directories by specifying them yourself.

Note: If Presort is selecting directories automatically and cannot find any that are valid for yourmailing, or if you specify directories yourself and those directories cannot be found, you will receivean error.

20

The following example shows that for mailing dates in October, either Release 5 ("Septemberdirectories") inOutgoing status or Release 6 ("October directories") inActive status can be used. Formailing dates in November, either Release 6 ("October directories") inOutgoing status or Release 7("November directories") inActive status can be used.

A message with the range of dates during which you can submit your mailing (based on thedirectories used) will be printed on the job summary report under the Auxiliary Files section.

Related topics:

l Presort can select the directories automatically

l You can select the directories yourself

About estimated drop dates

In Presort, themail induction date is referred to as the estimated drop date,which determines thedirectories that should be used.

l For mailers who drop ship, the estimated drop date is the day themailing is unloaded fromthe truck at the USPS entry facility. Themail verification date is the date that the USPSverifies and accepts themailing.

l For mailers who do not drop ship, themail verification date and estimated drop date arethe same.

Every entry point must have an estimated drop date. The Estimated Drop Date parameter islocated in the Entry Point Default and Entry Point Description blocks.

21

When Presort selects the directories automatically, generally the newest valid directories will beselected. In the cases of multiple estimated drop dates or estimated drop dates that fall at thebeginning of themonth, Presort may not use the newest directories by default. However, you canspecify whichever directories you would like to use. SeeWhich directories are valid for mymailing?for information on how the correct directories to use are determined.

If at any time Presort cannot find the directories it's looking for, Presort will error.

For every job, amessage will be generated on the job summary report that indicates the valid datesfor entering themail, based on the directories used.

Multiple estimated drop dates

l If all estimated drop dates are in onemonth (and at least one of the dates occurs after theseventh day of themonth), Presort will use that month’s (Active) directories. If thatmonth's directories are not available, Presort will use the previousmonth’s (Outgoing)directories.

For example, if the estimated drop dates range fromOctober 9 to October 15, Presort willuse the October directories. If the October directories cannot be found, Presort will usethe September directories. If Presort cannot find either set of directories, Presort willerror.

l If the estimated drop dates are in two consecutivemonths, the only directories that arevalid for all estimated drop dates are for the earlier month (theOutgoing directories).

For example, if the estimated drop dates range fromOctober 3 to November 13, theOctober directories are the only ones valid. If the October directories cannot be found,Presort will error. You can either change the estimated drop dates or verify that the validdirectories are located in the folder entered in theUSPS Presort Data Folderparameter.

l If the range of estimated drop dates spansmore than two consecutivemonths, Presortwill error. There is no single set of directories that is valid because directories are valid foronly twomonths. Either reduce the range of dates to two consecutivemonths at most, ordivide the job into smaller jobswith ranges of entry dates that span two consecutivemonths at most.

Estimated drop dates at the beginning of the month

l If there are any estimated drop dates that fall within the first seven days of themonth,Presort will use the directories for the previous (Outgoing) month. This is done in case youmaywant to submit your mailing before the first of themonth. The directories are valid forboth the previousmonth (Outgoing) and themonth that the estimated drop dates fall in(Active). You will still have the remainder of themonth to submit your mailing before thedirectories used expire.

22

For example, if all of the estimated drop dates fall betweenOctober 1 andOctober 7,Presort will use the September (Outgoing) directories automatically, even if the October(Active) directories are available. If the directories fromSeptember (Outgoing) cannot befound, then Presort will use the October (Active) directories, and a warning will begenerated during verification about not entering themail too early. If no valid directoriescan be found, Presort will error.

Youmay specify the directories for that month (theActive directories) yourself if youwould like. See You can select the directories yourself for more information. Presort willallow theActive directories to be used. However, a warning will be generated duringverification about not entering themail too early, because the directories used will not bevalid until the first day of that month.

l If the estimated drop dates are all within the samemonth and they fall both before andafter the seventh day of themonth, Presort will use that month’s (Active) directories and awarning will be generated during verification about not entering themail too early. If thatmonth's (Active) directories are not available, Presort will use the previousmonth’s(Outgoing) directories. A message will be printed on the job summary indicating the validdates for entering themail based on the directories used; if the entry dates are late in themonth, Presort may generate a warning during verification about making sure themailgets entered before those earlier directories used expire. If no valid directories can befound, Presort will error.

For example, if the estimated drop dates range fromAugust 3 to August 13, Presort willuse the August (Active) directories. A warning will be generated during verification aboutnot entering themail too early (before August 1). If the August (Active) directories cannotbe found, Presort will use the July (Outgoing) directories. If neither the current or previousmonths' directories can be found, Presort will error. If you would prefer that Presort usethe previous (Outgoing) month's directories in case there is a chance youmaywant toenter your mail before August 1, you can specify these directories yourself. See You canselect the directories yourself for more information.

Estimated drop dates that fall near the end of the directories' effective period

l If there are estimated drop dates that fall within the last 14 days of a givenmonth and thedirectories used will expire at the end of that month, a warning will be generated duringverification reminding you to enter your mail before the directories used expire.

For example, if the estimated drop dates range fromAugust 10 to Sept 30, Presort willuse the August (Active) directories, a warning will be generated during verificationreminding you to enter your mail before October 1. If the August (Active) directoriescannot be found, Presort will error.

Related Topics:

l Setting upmultiple entry points in Views

23

Removing expired directories

As you install monthly directories, the folder you are storing them inmay get cluttered after severalmonths. There can be up to six files per monthly directory release for Presort. Directory files areuniquely named for eachmonth, so they are not overwritten when you store new directories.

Presort will not delete any expired directories, but you canmanually delete them if you would like.We suggest deleting expired directories on a regular basis, such aswhen you install a new servicepack or at the beginning of the year. As long as you always have at least the threemost recent setsof directories (Notification, Active, andOutgoing), you should not have any issues. There is no harmin keeping previous directories on your system. They are not very large and do not take upmuchroom.

Related topics:

l Storing directories

l Directory lifecycle

l Which directories are valid for mymailing?

Setting up multiple entry points in Presort Views

The advantage of using Presort Views to set up entry point descriptions is that Presort will generatea list valid entry points for you when you are creating entry point descriptions. If you set up the entrypoint descriptions in the job file, you need to know which entry points are valid and which ones youwant to use.

After you have created all of your entry point descriptions, you will need to verify that the entry pointdescription blocks are in the right order in the job file to maximize your entry discounts. See "How thesoftware assignsmail pieces to entry points" in the Presort User Guide for more information.

How Presort Views generates valid entry points

When you are creating entry point descriptions in Views, Presort uses the estimated drop date youentered for that entry point description, plus all other estimated drop dates in the job, to determinethe directories to use to generate the entry points valid for the entry point description you arecurrently creating.

Note: If you enter an estimated drop date in the Entry Point Defaults window and leave thisparameter blank for all entry point descriptions, Presort will determine the directories to use basedon the default estimated drop date and use those directories to generate the entry points valid for allentry point descriptions in the job.

When setting upmultiple entry points (See "Multiple entry points" in the Presort User Guide in Viewsand you are letting Presort choose the directories automatically, and you enter an estimated dropdate in each entry point description rather than one in the entry point defaults, the order in which youcreate the entry point descriptions is important.

24

Note: If you specified the directories yourself, the order in which you create entry point descriptionsis not important. Presort will use the directories you have specified to generate the valid entry pointsfor all entry point descriptions in the job.

The directories Presort has used for previous entry point descriptions in the jobmight not be thecorrect ones to use for additional entry point descriptions that are added. As you addmore entrypoint descriptions to the job, theremay bemore estimated drop dates in the job for Presort toconsider to determine the correct directories to use. (SeeWhich directories are valid for mymailing?for more information.) Presort does not "remember" which directories it used for previous entry pointdescriptions.

Entry point details can change frommonth tomonth, which can affect whether they are valid forcertain estimated drop dates. Using consistent data for setting up all of your entry point descriptionsin your mailing reduces the chances of missing out on discounts you are entitled to and the possibilityof the USPS rejecting your mailing.

We recommend creating entry point descriptions in chronological order, starting with the earliestestimated drop date. This will reduce the chances that Presort will use different directories togenerate the entry points in the job. You can also "force" Presort to use the same directories for allentry point descriptions.

Important: In all cases, if Presort cannot find the directories it's looking for and there are noalternate valid directories available, Presort will error.

Creating entry point descriptions in chronological order

In most cases, creating entry point descriptions in chronological order by estimated drop date willresult in the correct directories being used to generate valid entry points for all entry pointdescriptions. (SeeWhat may happen if you do not enter entry point descriptions in chronologicalorder when the wrong directories can be used.)

When you are creating the first entry point description and you enter the estimated drop date, thereis a total of one estimated drop date in your job so far. Presort considers all estimated drop dates todetermine the correct directories to use. Since there is just one date in the job, Presort will use thedirectories for themonth of the estimated drop date (theActive directories).

When you are creating a second entry point description, there are two estimated drop dates thatPresort considers to determine the correct directories to use.Whichever directory set is valid for bothdates is the one Presort will use to determine the entry points that are valid for the second entry pointdescription.

You continue this process until you finish creating all entry point descriptions.

Depending on the order in which you created the entry point descriptions, it is possible that Presortdid not use the same directory set to generate the entry points for every entry point description. Asmore entry point descriptions are added to the job, there aremore estimated drop dates to considerwhen determining the directories to use.

For example, say your first entry point description has an estimated drop date of August 10. Becausethere is only one estimated drop date so far, Presort will use theActive directory for that estimateddrop date, which is August in this example.

25

Say the second entry point description has an estimated drop date in the samemonth, such asAugust 25. Presort considers August 10 and August 25 to determine the directories to use for thesecond entry point description, which is August, because they are the Active directories for bothdates.

Say the third entry point description has an estimated drop date of September 15. Presort considersAugust 10, August 25, and September 15, and determines the directories for the third entry pointdescription. In this case, the August directories are the only ones that can be used for thismailingbecause there are estimated drop dates in both August and September.

At this point, you can continue to create entry point descriptions that have estimated drop dates thatwould use the August directory set. They don't necessarily have to be added in chronological orderanymore because the only directories that can be used for all dates in the job are the Augustdirectories. For example, you can create another entry point description with an estimated drop datein September. Presort will use the August directories for that entry point description, because all ofthe estimated drop dates in the job can only use August directories.

If you create an entry point description with an estimated drop date of August 3, because the Augustdirectories were used for the previous two entry point descriptions and the August directories are thecurrent (Active) directories for estimated drop dates in August. (In Entering entry point descriptionschronologically that can still cause the wrong directory to be used, we demonstrate what wouldhappen if the first estimated drop date entered had been August 3.)

What may happen if you do not enter entry point descriptions inchronological order

If the first entry point description has an estimated drop date of September 10, Presort will use theSeptember directories by default, because there is just the one date in the job at this point, and thedirectory used will be theActive directories for that one date. If the next entry point description has anestimated drop date of August 20, Presort considers August 20 and September 10 and determinesthat the August directories are the only ones valid for the second entry point description.

In this case, Presort has used both August and September directories to set up entry points in thesame job. If the directories used to generate all entry points in the job are not the same, you couldmiss out on discounts you are entitled to and the USPS could reject your mailing.

But Presort cannot "go back" and regenerate valid entry points using the correct directories for you.You would have tomanually regenerate all of your entry points that were generated with theSeptember directories to be generated with the August directories. However, Presort does not keeptrack of which directories it used to determine the valid entry points for each entry point description,so unless you know which entry points were generated with the September directories, you wouldhave to regenerate all of your entry points to be sure theywere all generated using the Augustdirectories.

When creating entry point descriptions chronologically can still cause thewrong directory to be used

If the first entry point description that you create has an estimated drop date that falls within the first 7days of themonth (for example, August 3), Presort will use the previousmonth's (Outgoing)directories by default (in this case, July). (See About estimated drop dates for information about

26

estimated drop dates that fall at the beginning of themonth.) If the second entry point description hasan estimated drop date that falls anytime during the samemonth that is not within the first 7 days (forexample, August, 31), Presort considers August 3 and August 31, and will use the August (Active)directories to generate the entry points for the second entry point description.

Even though the July directories used for the first entry point description are valid for the secondentry point description, Presort does not keep track of directories it used for previous entry pointdescriptions. You would have tomanually regenerate all of your entry points that were generatedwith the July directories to be generated with the August directories, because the entry point rangesmay not match the data in the directory anymore that will be used for the job, so some entry pointdiscountsmay be lost or available discountsmay not be claimed.

However, Presort does not keep track of which directories it used to determine the valid entry pointsfor each entry point description, so unless you know which entry points were generated with the Julydirectories, you would have to regenerate all of your entry points using the August directories.

If the range of dates is too wide

If you attempt to create additional entry point descriptionswith estimated drop dates that are outsidethe effective date range of a directory that can satisfy all of the existing estimated drop dates in thejob, you will receive amessage stating that the estimated drop dates cannot be satisfied by any onedata set.

For example, you can't create an entry point description with an estimated drop date of October 8when the earliest date in the job is August 3. Directories are not valid for dates that span acrossmorethan two consecutivemonths. You will have to either change the estimated drop date of October 8 toa date sometime in August or September, or create that entry point description in a job that usesdirectories valid for October 8.

"Forcing" Presort Views to select the same directories

It's possible to "force" Presort Views to use the same directories to generate all of the entry points inthe job, regardless of the order you create the entry point descriptions in.

Enter an estimated drop date in the Entry Point Defaults window that would cause Presort to selectdirectories that are valid for all estimated drop dates in your job, and leave the individual estimateddrop dates blank in all of the Entry Point Descriptionswindows. Presort will use the same directoriesto generate the valid entry points for each entry point description.

l If all mail will be entered within a singlemonth (for example, August), the preferreddirectories are the directories for that month. Set the Entry Point Defaults value to anestimated drop date that falls in themiddle of that month (e.g. August 15). Presort will usethat month's (August) directories to generate all of the entry points.

l If all mail will be entered EARLY in that month (for example, August 1 - 7), the preferreddirectories are the July directories. Enter a date between the 1st and the 7th of themonth(for example, August 3). Presort will use the previousmonth’s (July) directories togenerate all of the entry points.

27

l If all mail will be entered over a period of two consecutivemonths (for example, Augustand September), the only directories valid are the August directories. Set the Entry PointDefaults value to an estimated drop date that falls in themiddle of the first month (forexample, August 15). Presort will choose the directories from that month (August)because that is the only valid set to use for such amailing.

You can also specify the directories for Presort to use yourself in the Auxiliary Files block. If you donot know what the valid entry points are for that month, you can run theMaildirshow utility andcompare the output between the old and new directories, or go tohttps://fast.usps.com/fast/fastApp/facility/facilityProfile.action to perform a query on an individualentry point to determine whether the entry point is valid.

IMb serial number tracking and assignmentimprovementsThe IMb serial number tracking feature has been enhanced to allow more control over how serialnumber sequencing behaves.

Serial number sequencing restarts for every job

Previously, Presort would continue with the next available number until all numbers in the specifiedrange were used and start over again at 1. Now, each time you process a job with serial numbertracking, Presort will start with the lowest available number in the database.

For example, if numbers 1 to 1000 were last used for a job that was runmore than 45 days ago,these numbers are available to be reused. Presort will use 1 as the first number to assign when yourun your next job.

Note: Serial numbers are identified as available only in batches, so youmay notice that groups ofavailable serial numbers are skipped if your mailing requiresmore serial numbers than are in a rangeof available numbers. To continue the previous example, if your job requires 1500 serial numbers,Presort will not start at 1 in this case. Even though serial numbers 1 - 1000 are older than 45 daysand available to be reused, Presort must find a range of at least 1500 available numbers. Presort willstart with the first number of that range. So, say the first number in that range is 5000, Presort willreuse numbers up to 6500.When you run your next job, Presort will repeat this process, starting at 1and looking for a range of available dates to accommodate the number of serial numbers needed bythe job.

Serial numbers can be unique for longer than 45 days

By default, Presort will enforce the uniqueness of a serial number for 45 days from the date in theDate to Start Tracking parameter. However, we have provided three additional sample databasesthat will allow you to increase the uniqueness periods to 90, 180, and 365 days before numbers canbe reused.

https://fast.usps.com/fast/fastApp/facility/facilityProfile.action

28

The sample tracking database files are located in the ...\ss\pst\samples folder.

Filename Uniqueness periodsample_45.s3db* 45 dayssample_90.s3db 90 dayssample_180.s3db 180 dayssample_365.s3db 365 days

* This sample database behaves in the sameway as sample.s3db, but sample_45.s3db hasbeenmodified so that the table of expiration periodswill be populated with 45-day values (ratherthan letting the code use its default). If you have a sqlite database browser and want to modify thoseperiods, this allows you to easily see what values should be changed.

If you are using the 45 day uniqueness tracking database file, or a tracking database file that wasprovided prior to SP15, verify that theDate to Start Tracking value is accurate.

If you need a uniqueness period of something other than 90, 180, or 365 days, or are using anexisting 45-day tracking database file and want to increase the uniqueness period, contactCustomer Support for assistance.

For more information, see "Assigning and tracking unique IM barcode serial numbers" in the PresortUser Guide.

Excluding mail from FSS preparationThere are two options in Presort to exclude flats from FSS preparation. It is your responsibility toknow whether you qualify for any exceptions to FSS preparation.We strongly recommend that youcontact your acceptance clerk to verify that you can submit mailingswithout FSS preparation.

l You can exclude High Density and High Density Plusmail from FSS preparation, whichallows you tomake the HD/HDPmail as pure carrier route bundles placed in CR sacks,rather than going into FSS bundles and then placing those in FSS or lower levelcontainers. Mail prepared this way qualifies for the DDU discount. (Mail prepared forFSS does not qualify for the DDU discount.) This option applies to STD and PER mailonly.

l You can turn off all FSS preparation for all levels in any scheme included in the job. Seehttp://www.gpo.gov/fdsys/pkg/FR-2013-12-18/html/2013-29879.htm for informationabout when FSS preparation is optional.

http://www.gpo.gov/fdsys/pkg/FR-2013-12-18/html/2013-29879.htm

29

The USPS allows you to exclude PER and STD Automation Flat-sizemailings from FSSPreparation sortation as long as theymeet any of the following criteria:

l The pieces to exclude are High Density (HD) and/or High Density Plus (HDP) STD orPER pieces only.

l There are fewer than 5000 pieces (PER only). FSS preparation is optional for fewer than5000 PER pieces.

l Themailing will be dropped at DDU entry points to claim the DDU discount. DDUs cannotprocess FSS Scheme bundles.

Note: All Basic Carrier Route, Automation, and Regular rate automation flat mail (with more than5000 pieces and not being entered at a DDU) should be included in FSS preparation.

The Presort job summary report will show how these options are set, either as part of the OptionalProcedures block or as part of the scheme setup.

Exclude High Density and High Density Plus mail from FSS preparation

You can exclude High Density (HD) and High Density Plus (HDP) mail pieces from FSSpreparation. This allows you to create the HD and HDPmail as pure CART bundles in CART sacks,rather than in FSS bundles placed in FSS containers or lower-level containers. This option ismostcommonly used when service time is an issue or when you want to get DDU CART discounts. Mailprepared for FSS does not qualify for a DDU discount.

The following schemes support this feature:

l PER, Packages on Pallets

l PER, Sacks on Pallets

l PER, Flats

l STD, Packages on Pallets

l STD, Sacks on Pallets

l STD, Flats

To exclude HD and HDPmail from FSS preparation, set theExclude High Density from FSSparameter toYes in the appropriate scheme block. In Views, check the box for Exclude HighDensity from FSS, within the scheme block.Retain Walk Sequencemust also be set toYes,Simp, or Mix.

You can further control which entry points use this option by setting upmultiple schemes andassigning schemes to different entry points. This can be helpful if you want to drop at DDUs andSCFs in the same job, but only want to exclude the HD and HDP pieces from FSS at the DDU entrypoints. Within each scheme, Exclude High Density from FSS can be set toYes orNo as needed.In each entry point, you can assign which scheme to use. For example, DDU entry points can usethe scheme that Exclude High Density from FSS set toYes. At the SCFs, you can to use the

30

scheme that has theExclude High Density from FSS set toNo. See "Manually linking schemesto entry points" in the Presort User Guide for more information.

See "Exclude High Density from FSS parameter" in the Presort Job File Reference for moreinformation.

Turn off all FSS preparation

You can turn off all FSS levels in every scheme included in the job if you have a legitimate reason fornot preparing FSS, such as qualifying for an exception.

The Turn off all FSS Preparation parameter is in the Optional Procedures block, with a defaultsetting ofNo. In Views, there is a check box for the Turn off all FSS Preparation parameter in theOverride Settings group in theOptional Procedureswindow. Setting this parameter toYes orchecking the boxwill turn off FSS preparation completely, nomatter how other parameters are set inthe jobfile.

See "Turn off all FSS Preparation parameter" in the Presort Job File Reference for moreinformation.

Related topics:

l "Optional procedures" in the Presort User Guide

Specifying election mail or political mail contentIn January 2014, checkboxes for indicating whether amailing consists of either all election or allpolitical mail pieces in order to receive expedited processing were added to the PS-3600, PS-3602N, and PS-3602R postage statements.

Using these checkboxes is now required for postage statements and is also required in Mail.dat 14-2and 14-1. Theywere optional to use for Mail.dat 14-1 until an errata was approved inMarch, 2014that made using these checkboxes a requirement for 14-1.

Note: To qualify for expedited processing, ALL versions in themailingmust contain only ElectionMail or ALL versionsmust contain only Political Mail. Pieces cannot bemixed to qualify for expeditedprocessing.

To check the appropriate box on the postage statement that specifies the contents of themailing:

1. In the IDEAMail.dat block, set theCreate IDEA CCR File parameter toY.

2. In the Version Description block(s), enter the appropriate three character code into theIDEA CCR File Characteristics Values parameter. The code consists of two parts:

l A one-letter "Characteristic Type," which isC (for "content") in this case

l A two-letter "Characteristic value," which describes the type of content:Election or Political.

31

Codes vary for the content type and theMail.dat version you are using:

Content Type Mail.dat 14-2 Mail.dat 14-1ElectionMail EM PIPolitical Mail PM VV

For example, to indicate a content type of electionmail when usingMail.dat 14-2, enter CEM ("C" forContent and "EM" for ElectionMail) in the IDEA CCR File Characteristics Values parameter.Presort will create a .CCR record with "C" in the Characteristic Type field and "EM" in theCharacteristic field.

l If all versions in amailing are set to EM (without PM), Presort will checkNo for "This is aPolitical CampaignMailing" and Yes for "This is Official ElectionMail" on the postagestatement as shown:

l If all versions are set to PM (without EM), Presort will check Yes for “This is a PoliticalCampaignMailing” and No for “This is Official ElectionMail” on the postage statement asshown:

Enter only one code into the IDEA CCR File Characteristics Values parameter for themailingtype, eitherCEM orCPM. All versions in themailingmust be identified ONLY as either Election orPolitical Mail.

l If some versions are identified as EMand some as PM, or some versions are blank andsome versions are set to EM or PM, Presort will checkNo for "This is a Political CampaignMailing" and No for "This is Official ElectionMail" on the postage statement as shown:

32

l If the IDEA CCR File Characteristics Values parameter does happen to containmorethan one code, Presort will assume the first code is the correct value and ignore anyfurther values. For example, if the value is set toCPM, CEM, Presort will assume thisversion is a Political Mailing and will ignore the ElectionMailing value. If this is the onlyversion in the job, Presort will check Yes for “This is a Political CampaignMailing” and Nofor “This is Official ElectionMail” on the postage statement as shown:

Note: Be sure that the code you enter is correct. Presort does not validate the entry in theCharacteristic field code. The software generates aMail.dat record for each code entered, even if itis not valid.

See "IDEA CCR File Characteristic Values parameter" and "Create IDEA CCR File parameter" inthe Job File Reference for more information.

Mail.dat changesThis release supportsMail.dat 14-2 and 14-1. Mail.dat 13-1 is no longer supported.

Note:Unlike in SP14, the Edjob script will NOT automatically update theMail.dat versionparameter in the Report: IDEA Mail.dat block of your job files in SP15 . You will have tomanuallyupdate this parameter to 14-2 when you are ready to use 14-2 after upgrading to SP15.

The notable changes inMail.dat 14-2 and 14-1 that affect Presort are listed below. For all changes,see theMail.dat specifications at http://www.idealliance.org/specifications/maildat/maildat-specifications.

Mail.dat 14-2

IDEAlliance has streamlinedMail.dat 14-2 by removing several fields and some records. See theMail.dat 14-2 specification for details.

l Because the "Licensed User's Email" field was renamed andmoved in the .HDR record,we renamed the corresponding Licensed User's Email parameter in the IDEAMail.datblock toContact Email andmoved it to just below theContact Telephone parameter.Any existing information from the previous Licensed User's Email parameter is retainedin theContact Email parameter after running Edjob.

l In the .CQT record for the Rate Category field, Presort now supports the values FS andFC (both for BPMonly).

l In the .SEG record, theMove UpdateMethod of "3 = To BeDetermined" was removed,so we removed the corresponding "FASTForward" option from theMove UpdateMethod parameter in theMailing Information block. If "FASTForward" is the currently

http://www.idealliance.org/specifications/maildat/maildat-specifications

33

specified option in this parameter, it is left blank after running Edjob, and you will need tospecify a new methodmanually.

l In the .CCR record for the Characteristic field, new values "EM= ElectionMail" and "PM= Political Mail" were added to the description. See Specifying electionmail or politicalmail content for more information about how to use these options.

l In the .CSM record, the "CSA Trip ID" field was renamed to "CSA Separation ID," so werenamed the corresponding IDEA CSA Trip ID parameter in the Entry Point Defaultsand Entry Description blocks to IDEA CSA Separation ID for 14-2 when using SP15.You can enter up to 3 numeric characters in this parameter. (Previously, up to 10alphanumeric characters were accepted for 14-1 when using SP14.)

Any existing information in the renamed IDEA CSA Separation ID parameter is retainedafter running Edjob. However, if there aremore than 3 numeric characters or any non-numeric characters remaining in this parameter, you will receive an error when you runyour job. If this happens, change the entry to a value with up to 3 numeric characters.

If there are fewer than 3 characters in this parameter, leading zeroeswill be prepended tothe value Presort posts the data. For example, "4" will become "004", "73" will become"073".

l In the .PQR record, a new field for FSS Carrier Route (FSS CR) was added to supportthe new FSS BPM rates. Now when PSVC BPMFlats are prepared using FSS prep, thejob receives the carrier route price.

Mail.dat 14-1

The following changesweremade toMail.dat 14-1:

l In the .CQT record for the Rate Category field, Presort now supports the values FS andFC (both for BPMonly).

l In the .CCR record for the Characteristic field, the descriptionswere changed for "PI" and"VV" to ElectionMail and Political Mail, respectively. See Specifying electionmail orpolitical mail content for more information.

l Although the "CSA Trip ID" field in the .CSM record was not changed in the 14-1specification, because it was renamed in 14-2, we renamed the corresponding IDEACSA Trip ID parameter in the Entry Point Defaults and Entry Point Description blocks toIDEA CSA Separation ID for 14-1 when using SP15. You can enter up to 3 numericcharacters in this parameter. (Previously, up to 10 alphanumeric characters wereaccepted for 14-1 when using SP14.)

Any existing information in the renamed IDEA CSA Separation ID parameter is retainedafter running Edjob. However, if there aremore than 3 numeric characters or any non-numeric characters remaining in this parameter, you will receive an error when you runyour job. If this happens, change the entry to a value with up to 3 numeric characters.

34

If there are fewer than 3 characters in this parameter, one or two following spaceswill beappended to the value when Presort posts the data. For example,"4" will have two spacesappended to it ("4 "); "73" will have one space appended to it ("73 ").

For information about PostalOne!-required fields, see thePostalOne! Mail.dat Technical Guide.

Postage Statement changesTo see detailed information about the changes the USPSmade to the Postage Statements for theSeptember 2014 rate case, go to http://pe.usps.com/federalregisternotices.asp. Rate case links areon the left side of the page.

Notable changes to the postage statement forms are:

3602-R, 3602-N, and 3602-C

l DSCF and DFSS pieces have switched places. The DSCF pieces come before theDFSS pieces now. (DFSS is not supported by Presort.)

3605


l The Barcoded/Nonbarcoded columnwas removed from the Nonpresorted - Flats section.

l The Carrier Route and FSS Carrier Route - Flats section have been split into twosections.

8125

l Line 13e: v. No. of Airboxeswas added (not supported by Presort).

l Line 14: DBMC was changed to DNDC, and a DFSS check boxwas added (notsupported by Presort).

l Line 15: BMC was corrected to NDC.

Manifest listing summary


http://pe.usps.com/federalregisternotices.asp

35

Postage statement lengths

The following table shows the page lengths for each Postage Statement for your reference. Therewere no changes to the lengths of the statements in this release.

Form Mail class Largestmin. linesvalue

Notes

3600-R 1C 110 lines For permit imprint postage payments andpostage affixed payments.

35413541 CPP

PER 108 lines For permit imprint postage payments.For Centralized Postage Payments.

3602-C STD 88 lines For PVDS Consolidated Postage StatementRegister (STD).

3602-R3602-N

STD 120 lines For permit imprint postage payments andpostage affixed payments.

3605-R PSVC BPM, LibraryMail, MediaMail, ParcelSelect, PSLW

111 lines For permit imprint and postage affixed (correctmeter, lowest meter mlg, lowest meter job,stamps (PSLW) andmulti meter (PSLW)).

8125 All 94 lines For drop-shipmailings.

Other changes

DefMap and Edjob versions

The software versions of the DefMap and Edjob utilities have been updated tomatch the Presortsoftware version of 8.00c.15.00.

Intelligent Mail™ Package Barcode (IMpb) Non-Compliance Update

New thresholds for IMpb compliance become effective in September 2014. The USPS will charge a$0.20 non-compliance fee for each IMpb piece if your mailing does not meet theminimum thresholdpercentage of compliance. The percentage charged depends on the category of compliance, eachof which has its own threshold, as shown:

Compliance category September 2014Unique Trackable Barcode 99%Destination Delivery Address or ZIP+4 Code in the File 95%Shipping Services File 1.6 or Higher, Including Required Data Elements 95%

Presort does not verify whether your mailing complies with these thresholds, nor will it calculate anynon-compliance fees. Youmust ensure that your mailingsmeet theminimum compliancepercentages to avoid being charged the non-compliance fee.

36

Fixed issuesThe following issues have been fixed or addressed in this release:

Issuenumber

Issue description

PRSRT-822 The IMb tracking database was not overwriting existing piece numbers older than45 days. This has been corrected.

PRSRT-1344 The "Rate Type" field for Parcel Select jobswere being listed as Parcel Post, withP instead of D in theMail.dat .MPU and .CPT records. This has been corrected.

PRSRT-1383 The D2 record count was incorrect in the Shipping Services File. The H1 recordcount now reflects all detail records including D2 records. To properly create D2records, youmust define PW.AdrSsfUpa in your definition file. See "ShippingServices File" in the Presort User Guide for more information.

PRSRT-1402 When IMb tracking is on, the IMB Last Used Version Serial Num value on the jobsummary report was off by one. This has been corrected.

PRSRT-1407 The "Barcode SP" and "SP" columns have been replaced with one column called"NONPRST" (for Nonpresorted) in the .PQR record to align with the updated "PartA - Bound PrintedMatter, Nonpresorted - Flats" section on the 3605 postagestatement. (Barcoded and Nonbarcoded pieces are no longer listed separately.)

37

Using Presort during the transition periodDuring the transition period of around August 8, when Presort SP15 is released, to September 7,when the new release of PostalOne! goes into effect, youmay use either version of Presort (SP14 orSP15) according to the following constraints:

If the mail verification date is August 23 or before

l Youmust use Presort SP14 with either the SP14 August or SP14 September directories.

If the mail verification date is between August 24 and August 31

l You can use Presort SP14* with the SP14 August directories.

l You can use Presort SP15 but only if you are usingMail.dat 14-1.

l Youmust use the SP15 August directories for entry dates in August.

l Youmust use the SP15 August directories if you havemultiple entry dates thatfall in both August and September.

If the mail verification date is between September 1 and September 6

l You can use Presort SP14 with the SP14 September directories (you will receive thesedirectories at the end of August).

l You can use Presort SP15 but only if you are usingMail.dat 14-1.

l You can use the SP15 August or SP15 September directories for entry datesin September. (If you are letting Presort select the directories, Presort willchoose the August directories by default. See "Estimated drop dates at thebeginning of themonth" in About estimated drop dates for more information.)

l Youmust use the SP15 August directories if you havemultiple entry dates thatfall in both August and September.

If the mail verification date is between September 7 and September 30

l Youmust use Presort SP15* with either the SP15 August or SP15 September directories(and either Mail.dat 14-1 or 14-2).

If the mail verification date is after 10/1

l Youmust use Presort SP15* with either the SP15 September or SP15Octoberdirectories.

And so on.

* You can continue to use Presort SP14 with the SP14 September directories fromSeptember 7throughOctober 31 only if you are strictly usingMail.dat 14-1 and generating postage statementsfrom theMail.dat files via PostalOne! or other means. The data in the SP14 September directories

38

expiresOctober 31, 2014.Wewill not be issuing directories for SP14 that are valid for mailverification dates that fall after October 31.

SeeWhich directories are valid for mymailing? for information about how to determine whichdirectories should be used for your mailing based on the entry date.

39

Directory distribution from Satori SoftwareBecause both SP14 and SP15 can be used during the transition period, we will distribute thedirectories for August and September for both releases according to this schedule:

SP14

l The September directories for SP14will be available around August 31. These will be thelast directories for use with SP14 and will be valid throughOctober 31, 2014.

SP15

l Both the August and September directories for SP15will be available around August 8.

l TheOctober directories for SP15will be available around September 8.

See Directory lifecycle for more information about when new monthly directories are released.

40

Downloading service packs and fix packsEach time a product update is available, you will receive an email with instructions for downloadingand installing the update.

If you need a copy of your software product, please contact Satori Software Technical Support at800-357-3020 or email us at [email protected].

41

Upgrading to Satori Presort 8.00c.15.00These instructions describe the process to upgrade fromPresort 8.00c.14.0x to 8.00c.15.00.

If you want to install Presort 8.00c.15.00 into a different folder than where Presort 8.00c.14.0x islocated, see theSystemAdministrator Guide for instructions for installing Presort.

Upgrading a Windows standalone, server, or RemoteViews client

1. Double-click setup.exe from the uncompressed ZIP file.

2. Follow the on-screen prompts to start the software upgrade installation and accept thelicense agreement.

3. In theChoose Destination Location screen, specify the folder of where your existingPresort software is installed. The default location is C:\ss. ClickNext to accept thedefault destination folder of C:\ss, or clickBrowse to specify a different location.

4. In theComponent Selections screen, check the boxes next to the components to upgradeand clickNext.

5. A message will appear asking you whether you want the installer set up a clientinstallation program to assist with setting up client machines.

l For single computer and Remote Client upgrades: ClickNo.

l For server upgrades: ClickYes. When the software upgrade installation iscomplete, see "Upgrading aWindows client" for instructions for upgrading yourclient workstations.

6. In theSelect ProgramFolder screen, select a folder to add icons into and clickNext.

7. A message will appear asking if you want PATH and PW_PATH variables set up for you.SelectNo. These variables were set up for you in a previous Presort installation.

8. In theStart Copying Files screen, review the settings and clickNext. You will see a seriesof screens that show the progress of the upgrade installation.

9. A message appears informing you that youmust have Acrobat Reader later to read thedocumentation. ClickOK.

10. When the upgrade installation is complete, youmay be prompted to restart yourcomputer. Select Yes to restart now orNo to restart later, and clickFinish. If you chose torestart later, be sure to do so before using the software.

Important:Do not remove or rename the …\ss directory or its subdirectories. If youremove or rename these directories, Presort may not run. In addition, do not move filesfrom their subdirectory after installation.

42

Post-installation tasks

After you have installed the software, perform these tasks to complete the upgrade process forsingle computers and servers.

1. For server installations only: If you chose to have a client installation program setup in step5, follow theWindows client upgrade instructions.

2. Install the USPS directories. See Directory updates for instructions.

3. Restart your computer to finish the software upgrade installation.

Upgrading a Windows clientAfter you have upgraded Presort on the server, upgrade Presort on the client workstation(s) byrunning the client installation that was created in step 5 of the server installation.

Important: These instructions do not apply to Remote Views clients. "See the Upgrading aWindows standalone, server, or Remote Views client" for instructions. For more information aboutRemote Views, see theSystemAdministrator Guide.

1. Upgrade Presort on the server if you have not done so. See "Upgrading aWindowsstandalone, server, or Remote Views client" for instructions.

2. From themapped drive on the client workstation (set up during the initial installation ofPresort 8.00c.14.00), navigate to the …\ss\CLIENT directory on the server and double-click setup.exe.

3. When the installation is complete, restart the client.

4. Repeat steps 4 through 6 for each client that runs Presort.

Once you have run the client installation program on all clients, performed all applicable post-installation tasks, and have restarted all systems, you will be able to run the application and accessthe documentation from the Satori Software folder located on the Start menu.

Upgrading a UNIX machineThese instructions are for upgrading all UNIX machines, including Remove Views servers.

1. Stop the Remote Views server if applicable.

2. Run ./install.bin from the uncompressed ZIP or TGZ file.

3. Read the introduction information and pressEnter.

4. When asked to read the license agreement, type Y orN and pressEnter.

5. To accept the terms of the agreement, typeY and pressEnter.

43

6. Specify the directory of where Presort 8.00c.14.0x is installed, either by pressing Enterfor the default directory, which is /disk_n/ss (where /disk_n refers to the file systemor disk where you choose to install the software), or by typing the directory name. (Do notinclude “ss” as part of the path; an /ss subdirectory is automatically added to thedirectory you specify.) PressEnter to continue.

7. TypeY to verify the path and pressEnter.

8. Select the products to upgrade. By default, all products are selected. To upgrade allproducts, just pressEnter. If you want to upgrade only certain products, type a comma-separated list of numbers representing the products to deselect (and therefore not install)and pressEnter. For example: 1, 3, 4 will install only the product represented by 2.

9. Review the list of products you want to upgrade. Type back to go to the previous screen ifyou want to change your selection. PressEnter to continue.

10. When all products are successfully upgraded, pressEnter to exit the console.

Important:Do not remove or rename the …/ss directory or its subdirectories. If youremove or rename these directories, Presort may not run. In addition, do not move filesfrom their subdirectory after installation.

Upgrading Remote ViewsTo upgrade a Remote Views server, follow the instructions in "Upgrading aWindows standalone,server, or Remote Views client."

To upgrade a Remote Views client, follow the instructions in "Upgrading aWindows client."

For more information about Remote Views, see theSystemAdministrator Guide.

44

Running Edjob and patch scriptsYoumust run Edjob on all of your existing Presort and ZIPCount jobs to update them to use thefunctionality and changes included in this release of Satori Presort 8.00c.15.00. Use thepwpstjob.upd script to update your Presort jobs and the pwzctjob.upd to update yourZIPCount jobs. After you have run Edjob, edit any default parameters set by Edjob as necessary.For instructions on running Edjob, see theEdjob User’s Guide.

Note:Unlike in Presort 8.00c.14.00, the Edjob script for 8.00c.15.00 doesNOT automaticallyupdate theMail.dat version parameter in your job files. You have tomanually update this parameterto 14-2 when you are ready to use 14-2 after upgrading to 8.00c.15.00.

Before you run Edjob to update your job files, as a best practice, we recommend that you backthem up to a different location for production jobswith Satori Presort 8.00c.15.00.

You can begin using 8.00c.15.00 on August 24, 2014 to process jobs that will be entered afterSeptember 7, 2014. You can continue to use Satori Presort 8.00c.14.0x to process your jobs thatyou enter before September 7, 2014, after which youmust use only Satori Presort 8.00c.15.00.

Job file parameters that are added or changed by EdjobFor monthly directories:

l The new USPS Presort Data Folder parameter will be added to the Auxiliary Files blockand left blank.

l The individual directory parameter names in the Auxiliary Files blockwill be renamed toaccount for new filename structure.

l Any existing path information will remain. Any existing filenameswill be updated to thenewly named directory for August 2014.

l None of the Default Format or Default DEF parameter values are changed.

l Example: Here is a typical Auxiliary Files block before running Edjob:BEGIN Auxiliary Files =========================================

ZCF Directory (path & zcf10_s.dir)... = C:/ss/dirs/zcf10_s.dir

Mail Proc Ctr Dir (path & mpc09.dir). = C:/ss/dirs/mpc09.dir

PER/PSVC Zone Dir(path & zone.dir)... = C:/ss/dirs/zone.dir

+PER/STD Del Stats (path & dsf.dir).. = C:/ss/dirs/dsf.dir

Mail Direction (path & facility.dir). = C:/ss/dirs/facility.dir

Mail Direction (path & maildirect.dir)= C:/ss/dirs/maildirect.dir

Default Format (path & file.fmt)..... =

Default DEF (path & file.def)........ =

END

45

Here is the same Auxiliary File after Edjob is run:

BEGIN Auxiliary Files =========================================


ZCF Directory ([path]YYMM_zcf.dir)... = C:/ss/dirs/1408_zcf.dir

Mail Proc Ctr Dir([path]YYMM_mpc.dir) = C:/ss/dirs/1408_mpc.dir

PER/PSVC Zone Dir([path]YYMM_zone.dir)= C:/ss/dirs/1408_zone.dir

PER/STD Del Stats([path]YYMM_dsf.dir) = C:/ss/dirs/1408_dsf.dir

MailDirect.([path]YYMM_facility.dir). = C:/ss/dirs/1408_facility.dir

MailDirect.([path]YYMM_maildirect.dir)= C:/ss/dirs/1408_maildirect.dir

Default Format (path & .fmt)..... =

Default DEF (path & .file.def)........ =

END

l There is an optional patch script (USPSDataPath.upd) available that will populate theAuxiliary Files block parameters so that Presort will select the directories automatically.We highly recommend that you let Presort select the directories automatically and thatyou run this script for all of your Presort jobs.The script will populate theUSPS Presort Data Folder parameter with the path from theZCF Directory parameter in the first Auxiliary Files block and remove any existing pathand filenames from the individual directory filename parameters, leaving them blank. AllAuxiliary Files blocks in the job file will be updated even if the block is commented out, sobe sure the ZCF Directory parameter in the first Auxiliary Files block contains the correctpath.

l The following note will be added after the Auxiliary Files block for the new USPS PresortData Folder parameter:NOTE USPS Presort Data Folder

Presort can automatically select the newest valid data directories byspecifying only the path to the directory location, or you can control thedirectories used by identifying the specific files.

See the Job File Reference for more information.

46

For excludingmail from FSS preparation:

l The new Exclude High Density from FSS parameter will be added to the followingscheme blocks and set toNo:

l PER, Packages on Pallets

l PER, Sacks on Pallets

l PER, Flats

l STD, Packages on Pallets

l STD, Sacks on Pallets

l STD, Flats

l The new Turn off all FSS Preparation parameter will be added to the OptionalProcedures block and set toNo.

For Mail.dat changes:

l Because the "Licensed User's Email" field was removed from the .HDR record, werenamed the corresponding Licensed User's Email parameter in the IDEAMail.datblock toContact Email andmoved it to just below theContact Telephone parameter.Any existing information in theContact Email parameter is retained after running Edjob.

If you havemore than oneMail.dat block in your job file, theContact Email parameter inevery instance of theMail.dat blockwill be populated with the email address in theLicensed User's Email parameter from the LAST instance of theMail.dat block, even ifthis block is commented out. All Mail.dat blockswill be updated, even if they arecommented out.

l In the .SEG record, theMove UpdateMethod of "3 = To BeDetermined" was removed,so we removed the corresponding "FASTForward" option from theMove UpdateMethod parameter in theMailing Information block.

If "FASTForward" is the currently specified option in this parameter, it is left blank afterrunning Edjob, and you will need to specify a new methodmanually.

l We renamed the IDEA CSA Trip ID parameter in the Entry Point Defaults and EntryDescription blocks to IDEA CSA Separation ID. This parameter accepts up to 3 numericcharacters in SP15 (it accepted up to 10 alphanumeric characters in SP14). Any existinginformation in the IDEA CSA Separation ID parameter is retained after running Edjob,but truncated after the third character. Verify that all remaining characters in thisparameter are numeric; otherwise you will receive an error.

If you are running SP15 and usingMail.dat 14-1, the IDEA CSA Trip ID parameter in theEntry Point Defaults and Entry Description blocks accept up to 3 alphanumeric characters(it accepted up to 10 alphanumeric characters in SP14). Any existing information in thisparameter is retained after running Edjob, but truncated after the third character.

47

Directory updatesWhenmonthly postal directory updates are available, you will receive an email with instructions fordownloading and installing the updates. It is important to update your postal directories as soon asthey are available.

The .tgz or .zip files that are available for download contain the following directories:

l Zip City File (YYMM_zcf.dir)

l Delivery Statistics File (YYMM_dsf.dir)

l Zone Directory File (YYMM_zone.dir)

l Facility directory (YYMM_facility.dir)

l Mail Direction file (YYMM_maildirect.dir)

l Labeling lists (YYMM_mpc.dir)

Directory release scheduleThe USPS currently publishes the directories on amonthly basis. The schedule can be foundhere: https://ribbs.usps.gov/intelligentmail_schedule2014/LabelingListandMDFSchedule.cfm.

Mail Direction files and labeling listsMail Direction data determineswhere and whenmail pieces are dropped so that you can receivediscounts. Labeling lists are used during the processing to group, create, and label bundles, trays,sacks, and pallets at various preparation levels.

The USPS updatesMail Direction files and labeling lists eachmonth.You will receive an email fromSatori Software when the directories have been updated and are available, including instructions fordownloading and installing them.

Mail Direction files and labeling lists are always included in themonthly U.S. AddressDirectories.You should download and install themost current U.S. AddressDirectories eachmonth in order toremain current on all directory files.

https://ribbs.usps.gov/intelligentmail_schedule2014/LabelingListandMDFSchedule.cfm

48

Accessing DocumentationDocumentation is available in two formats: PDF and online help.

PDFsRelease notes, manuals, and other product documents are available in the Documentationfolder. ClickStart > All Programs > Satori Software > Documentation or Documentation(Cross-Product).

Online help An online help file is accessible fromwithin the software by clickingHelp from themenubar. Select the help file shown in the dropdownmenu. You can also press F1 at anytime to displayspecific help about the active window or reference topic.

The following documentation and online help files are installed with Satori Presort 8.00c.15.00(pathnames are shown for Windows as an example):

l Presort User Guide (...\ss\documentation\pst\pst_ug_ss.pdf)

l Presort Job File Reference Guide (...\ss\documentation\pst\pst_jfr_ss.pdf)

l Presort Help File (...\ss\pst\pstvws_ss.chm)

l Release Notes (...\ss\documentation\pst\pst_rn_ss.pdf)

l System Administrator Guide (...\ss\documentation\sysadminguide_ss.pdf)

l Defmap Help File (...\ss\adm\DEFMAP_ss.chm)

l Edjob Help File (...\ss\adm\EDJOBGUI_ss.chm)

l Quick Reference Guide for Views and Job Files (...\ss\documentation\quickref_views_ss.pdf)

l Quick Reference for Views and Job Files Help File(...\ss\documentation\quickref_views_ss.chm)

l Edjob User Guide (...\ss\documentation\edjob_usersguide_ss.pdf)

l Database Prep (...\ss\documentation\databaseprep_ss.pdf)

l Views Quick Start Guide (...\ss\documentation\views_quickstart_ss.pdf)

49

Contacting Satori Software Technical SupportYou can contact Satori Software Technical Support by telephoneMonday through Friday, 6 a.m. – 5p.m at 800-357-3020 Pacific, or by email at [email protected].

Satori ® Presort - Satori Software Inc.docs.satorisoftware.com/pst_rn_ss.pdf · Scalable...

Documents

Transcript of Satori ® Presort - Satori Software Inc.docs.satorisoftware.com/pst_rn_ss.pdf · Scalable...