Business objects PRESORT 7.71C User Manual

Download

Page 1

Presort

Job-File Reference

Presort 7.71c

January 2007

Page 2

Contact information Contact us on the Web at http://www.firstlogic.com/customer

If you find any problem with this documentation, please report it to Business Objects in writing at

Patents Business Objects owns the following U.S. patents, which may cover products that are

documentation@businessobjects.com

offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352.

Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise

are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners.

Third-party contributors Business Objects products in this release may contain redistributions of software

licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty

Presort Job-File Reference

Page 3

Chapter 1:

Introduction to Presort Job.......................................................................... 7

Welcome to Presort Job....................................................................................8

Getting started ..................................................................................................9

Guidelines for editing job files.......................................................................10

Steps in a Presort job......................................................................................11

Chapter 2:

Job-file blocks and parameters .................................................................. 19

Address Output File ......................................................................................20

Alternate Presort Scheme Sequence...............................................................27

Alternate Segment Sequence..........................................................................28

Auxiliary Files ...............................................................................................29

Container Output File.....................................................................................31

Container Sequence........................................................................................32

Create File for Output ....................................................................................33

Entry Point Defaults.......................................................................................38

Entry Point Description..................................................................................45

Execution........................................................................................................51

General ...........................................................................................................56

General Output ...............................................................................................57

Input File ........................................................................................................60

Mailflow .........................................................................................................61

Mailing Information .......................................................................................63

Name Optimizer Control ...............................................................................66

Name Optimizer Resource File......................................................................68

On-Demand Reporting ...................................................................................70

Output Entry Point Selection..........................................................................72

Output Order ..................................................................................................73

Output Presort Scheme Selection...................................................................74

Output Segment Selection..............................................................................75

Output Selection.............................................................................................76

Package Output File .......................................................................................77

Package Sequence ..........................................................................................78

Pallet Output File ...........................................................................................79

Pallet Sequence ..............................................................................................80

PER Ride-Along Enclosure Description........................................................82

Post to Input File ............................................................................................83

Presort scheme parameters .............................................................................84

Processing Center Sequence.........................................................................120

Report parameters ........................................................................................121

Report: EMD File.........................................................................................140

Report: IDEA Mail.dat description ..............................................................142

Report: IDEA Mail.dat parameters ..............................................................146

Segment Defaults .........................................................................................151

Segment Description ....................................................................................152

Contents

Page 4

PSVC Multi-Piece Parcel Description......................................................... 153

USPS Optional Procedures ..........................................................................155

Version Defaults ..........................................................................................160

Version Description .....................................................................................169

Appendix A:

Printer and page setup for reports...........................................................171

Calculate LPP and characters per page........................................................ 172

Make page length settings............................................................................ 174

Make page width settings ............................................................................176

Form feed..................................................................................................... 177

Table of Postage Statement page lengths ....................................................178

Printer initialization strings.......................................................................... 179

Appendix B:

Name Optimizer......................................................................................... 181

How it works................................................................................................ 182

Adding Name Optimizer to Presort ............................................................. 184

To save postage............................................................................................ 185

As a marketing tool......................................................................................186

To form a perfect, limited CART mailing ................................................... 191

Name Optimizer and the Job Summary.......................................................193

Appendix C:

Master.pst ................................................................................................... 195

Index............................................................................................................ 223

Presort Job-File Reference

Page 5

Preface

About Presort Our Presort programs help you prepare professional mailings.

The job-file version offers an editable text file that lists all of the parameters that drive the many features of Presort. You may choose to use either the job-file version or the Views GUI-interface version of Presort to set up your mailing job.

About this guide This manual presents the information that you need to set up and process a

Presort job. In it, we discuss guidelines for using job files and provide a parameter-by-parameter description of each job-file block.

Documentation The following documents are included with your installation of Presort:

 Presort Release Notes  Presort Job-File Reference (this document)  Presort User’s Guide

The Presort User’s Guide and Presort Job-File Reference are available in

Adobe system to view this file.

Reader® file (PDF format). You need to have Reader installed on your

Install Reader To install Adobe Acrobat Reader, open the AdbeRdr70_enu_full.exe located on

your Presort CD.

Access the latest documentation

You can access product documentation in several places:

 On your computer. Release notes, manuals, and other documents for each

product that you have installed are available in the Documentation folder. Choose Start > Programs > Presort > Documentation.

 On the Customer Portal. Go to www.firstlogic.com/customer, and then

click the Documentation link to access all the latest product documentation. You can view the PDFs online or save them to your computer for viewing or printing.

Preface

Page 6

Conventions This document follows these conventions:

Convention Description

Bold We use bold type for file names, paths, emphasis, and text that you

should type exactly as shown. For example, “Type

Italics We use italics for emphasis and text for which you should substitute

your own data or values. For example, “Type a name for your file, and the

.txt

extension (

testfile

Menu commands We indicate commands that you choose from menus in the following

format: Menu Name > Command Name. For example, “Choose File > New.”

.txt

).”

cd\dirs

.”

We use this symbol to alert you to important information and potential problems.

We use this symbol to point out special cases that you should know about.

We use this symbol to draw your attention to tips that may be useful to you.

Presort User’s Guide

Page 7

Chapter 1: Introduction to Presort Job

This chapter provides guidelines for working with job files and offers a Quick Start sample job that you can run right now.

Chapter 1: Introduction to Presort Job

Page 8

Welcome to Presort Job

Presort Job is based on a job file. The job file is a set of instructions that tells Presort how to process your mailing.

Open the job file as you would any other text file. There you’ll see line after line of parameters; each parameter is an instruction. These parameters give Presort such instructions as the class of mail to prepare, which presort schemes to use when sorting, and which reports to print.

In the job file, we’ve grouped together parameters that are similar to one another. These groups are called blocks. See Appendix C in this manual for a list of all blocks and parameters in the Presort master job file.

To help you fill out the instructions for your job, we’ve listed a detailed description of each parameter in Chapter 2.

Presort Job-File Reference

Page 9

Getting started

Sample job To help you get started preparing your own Presort jobs, Business Objects

provides a set of Quick Start sample job files that you can run right now. We’ve even included a sample database, and the format and definition files too. These sample jobs are designed to:

 ensure that Presort is installed correctly

 make you feel comfortable processing a completed Presort job file

Refer to “Steps in a Presort job” on page 11 in this chapter for help in setting up and processing jobs.

Templates The Presort master job file includes blocks of parameters for all mail classes and

mail preparation options. No single job will require all of these blocks and parameters; rather you'll need to use just a subset.

That’s why we’ve created the template job files—dozens of job files that each contain a subset of the blocks from the master job file. Each template is set up to reflect a different mailing scenario.

To use the template files, simply choose the template that best matches your mailing requirements for the job that you need to process today. You’ll find them in the template subdirectory.

To find the template job that’s right for you, see “Template job files for

nonpalletized jobs” on page 13 or “Template job files for pallet jobs” on page 14..

Once you’ve chosen a template file for your job, save a copy of it with a text editor (for example, choose File | Save as in the Microsoft WordPad text editor). Then edit the renamed job file and individualize it further to meet your mailing needs. If you need to add a block that’s missing from the template, copy and paste the block from the master job file. (The master job file is located in the pw\pst subdirectory for Windows/NT, or usr/postware/presort subdirectory for UNIX).

The Presort master file is named master.pst.

Chapter 1: Introduction to Presort Job

Page 10

Guidelines for editing job files

Editing tips To edit job files, you need working knowledge of a good text editor or word-

processing program. If you use a word processor, save job files as simple ASCII text.

Remember, before editing any template job, make a copy with a different file name. When software updates are shipped, new copies of the template jobs are always included. It would be unfortunate to have a new version overwrite a file on which you’ve been working!

Here are some rules and facts to remember when creating a job file:

1. Copy and edit the job files provided by Business Objects, or copy blocks between files as necessary. Do not type parameter blocks from scratch.

2. Use the file-name extension .pst.

3. Later we’ll explain which blocks are required (only a few), and which are optional. Mostly it depends on what type of mailing you need to prepare.

4. Do not edit the BEGIN or END lines, block titles, or parameter names (anything to the left of the equal sign). There is only one exception to this rule: To make Presort ignore a block, you may insert an asterisk (*) before the word BEGIN.

5. NEVER, EVER delete parameters or rearrange them within a block

7. Feel free to add comments at the beginning or end of the job file, and

8. The Presort program assumes nearly nothing. Many parameters require some

9. Where space allows, parameter names are followed by clues or options in

unless we recommend it in this manual.

6. NEVER, EVER press Enter while typing a long parameter entry. Simply let the entry wrap onto an additional line. If you press Enter, Presort will count the extra end-of-line marks as separate lines. Your job will not verify until you remove the extra end-of-line marks.

between blocks (but not within a block). Notes or comments might make it easier for one of your co-workers to understand and use your job file. Start all comment lines with an asterisk (*). Do not use the keywords BEGIN or END in comments.

sort of entry. There are some optional parameters that may be left blank. We’ll point those out in this manual.

parentheses. Clues are shown in lowercase, options in uppercase. Case doesn’t matter in the entry you type, but be sure to spell options exactly as shown, and do not abbreviate. Exception: At Y/N parameters, you may spell out Ye s or No.

10. As programs are updated, parameters and blocks may be added or changed in the job file. Do not update your job files by hand. Instead, use the Edjob utility. Look for instructions in the Edjob User’s Guide that accompanies this release.

Presort Job-File Reference

Page 11

Steps in a Presort job

When you choose a template job to use as the basis for your own job file, you’ll be making decisions about presorting. That’s the first step in running a Presort job. Each step is listed below and described in detail on the remaining pages in this chapter.

1. Plan ahead.

2. Create definition (DEF) and format (FMT) files.

3. Complete the job file.

4. Start Presort.

5. Verify the job.

6. Evaluate processing messages.

7. Check reports.

Step 1: Plan ahead There are lots of questions to ask yourself before you even choose a template job

for your mailing, let alone begin filling out parameters.

Consider what type of mail piece you're mailing, what type of containers you'll need, and what presorting goals you want to meet. Before you begin setting jobfile parameters, read the Business Objects manuals to learn the basics of USPS discount programs or mail preparation options.

You might begin by reading portions of the Mailing Standards of the United States Postal Service, Domestic Mail Manual (DMM 300) to learn how the USPS expects mail to be prepared and what you can do to earn postage discounts.

Consider your presorting goals. Most Presort users hope to gain significant postage savings by presorting. The many features of Presort can help you—

 ease mail preparation, to reduce the work of your mail-room staff

 better manage large mailings

 save postage

 improve delivery service

Next you’ll need to consider which presort schemes to use. That will dictate which template job file you choose. Use the flowchart on page 13 to find a template for nonpalletized jobs or the flowchart on page 14 for palletized jobs.

Chapter 1: Introduction to Presort Job

Page 12

Step 2: Create DEF and FMT files

These files must accompany your database input files. They help Presort understand and read the fields in your input records. Refer to our Database Prep manual for instructions. Find the most recent version in the latest Documentation CD.

Presort needs help reading the fields in your input records. Presort needs to read just certain fields in each record. It must be able to read the ZIP Code. Other fields may be necessary, depending on the Presort features you use.

Since Presort doesn’t know a ZIP field from a company name field, you must “translate” your field names into names that Presort can understand so that Presort can read your input records.

To do that, set up a definition (DEF) file. For the Quick Start sample Presort job, we’ve done this step for you. Take a look at the file; it's named quik_in.def and is located in the samples subdirectory (open it as you would any text file). Then read the Database Prep manual for complete instructions on setting up a DEF file. Find the most recent version in the latest Documentation CD.

If your input file is ASCII, you’ll also need to create a format (FMT or DMT) file. The format file tells Presort where to find each field in the input file. It lists the field names, lengths, and types. Take a look at the quik_in.fmt file. For complete instructions, see the Database Prep manual.

If you have multiple input files, and each has a different format, you must create a DEF, and an FMT or DMT file for each input file. If their formats are the same, you may use a single DEF, and FMT or DMT file. See the Default parameters in the Auxiliary Files block on page 29 for details.

Step 3: Complete the job file

When you set up a job file to process your mailing, use one of the template job files as a starting point. Make a copy of the template job of your choice and rename it so that you don’t overwrite the template.

Edit the renamed template job and adjust the parameter settings to individualize the job to the specific characteristics and needs of your mailing. See “Job-file

blocks and parameters” on page 19for parameter descriptions and instructions for

completing them.

For now, we invite you to edit one of the Quick Start sample job files that we’ve provided. We've completed these files so that you can use them to process a small mailing list, also provided. Choose one of the Quick Start jobs in PW > pst > Samples and look for one of the files listed below. The sample job you choose depends on your system and the class of mail you would normally process:

System Job-file name

Windows quikwinx.pst

UNIX quikunxx.pst

The only entries that you may need to change in this sample job are located in the Auxiliary Files block. If you’ve placed the directories in different locations from the ones we’ve chosen, you’ll need to change the paths.

Look through the rest of the job file to get an idea how we set up this job, but don’t change any of the other parameter entries in this sample job.

Close the job file, exit the text editor, and return to your system prompt.

Presort Job-File Reference

Page 13

Template job files for nonpalletized jobs

Chapter 1: Introduction to Presort Job

Page 14

Template job files for pallet jobs

Presort Job-File Reference

Page 15

Step 4: Start Presort Before running Presort, make sure that you have:

 created a format file for each ASCII input file

 created a delimited format file for each delimited-ASCII file

 created a DEF file for each input file

 completed the job file

Command line To run your job, type the Presort command, followed by the path and name of

your job file. The options are listed and described below:

Platform Options

Windows/NT

presort [/a | /nos] [/v] [/watch] [/llogfile] [path] jobfile.pst presort /rev

presort /del jobfile.pst presort

UNIX

presort [-a | -nos] [-v] [-watch] [path] jobfile.pst [> logfile] [&] presort -rev

presort -del jobfile.pst presort

Command line options Each option on the command line is listed and described below.

Option Description

Answer all verifier

a halt.

nos

Don’t stop on verifier error or warning. Handy when you are running jobs via a batch or shell script. When an error is found, Presort exits and the batch script can go on.

Verify only; do not process the job. Handy when you want to run a job overnight. Use it to verify your job during the day before you run the job overnight.

warnings

with “continue”; verifier

errors

will cause

watch

del

rev

presort

Add system time-of-day to progress messages. Handy when you redirect processing messages to a log file.

or >

logfile

Divert processing messages to log file for later reading.

Run a UNIX job in the background.

Delete work files from the work directory specified in the job file.

Display the revision level. When you call the Business Objects Help Desk, the advisor may ask you for this information.

Type just this command alone to see a display of command-line options.

Chapter 1: Introduction to Presort Job

Page 16

Step 5: Verify the job As Presort begins processing your job, it first checks the settings in your job file.

If the program detects a problem, it will stop and alert you to the error or warn you of a potential problem.

If you receive an error message, you must return to the job file and fix the error. If you receive a warning message, you have a choice. You may either continue processing or return to the job file and make a change.

When you create your own job file, don't be surprised if you find that you need to fix some errors before your job will pass the verification stage. You may need to return to the job file several times to change parameter entries before the job verifies successfully.

Step 6: Evaluate processing messages

You can select an option to view messages on screen as Presort processes your records. These messages keep you abreast of the job’s progress. This option is called Show Detailed Process Messages, and it’s in the Execution block.

On some systems, these messages fly by faster than you can read them. However, if you can read them, they’ll show you the percentage of work performed as Presort reads the input file(s), sorts records by each scheme, and generates reports.

Step 7: Check reports Check the results of your job by looking at the reports, particularly the Job

Summary. Look in the Samples subdirectory for a file with the .pjs file-name extension. Use any text editor to open the file.

The Mailing Summary section of the Job Summary will show you how the mail pieces were sorted, how much postage you owe, and how many pieces didn’t make it into the mailing.

---------------------Condensed for illustration------------------------------------

Entry Point: (1) LOCAL POST OFFICE, LA CROSSE WI 54601-9998

1 Foot 2 Foot Flat Presort Scheme Weight(lbs) Copies Packages Sacks Trays Trays Trays Pallets Postage

---------------------- ------------- ------ -------- ------- ------ ------ ------- -------- ----------(1) 1C, Automation 71.8956 951 10 3 7 $ 461.544 Letters ATM (3) 1C, Single Piece 3.7044 49 3 1 $ 26.950

------------- ------ -------- ------- ------- ----- ------- -------- ----------Totals: 75.6000 1000 13 0 4 7 0 0 $ 488.494

------------ ------ -------- ------- ------- ----- ------- ---- --- ----------Running Totals: 75.6000 1000 13 0 4 7 0 0 $ 488.494

Remaining Pieces Weight(lbs) Copies

---------------------------------------------------- -------------- ------ Qualified Non-Presort (No Qualifying Entry Points) 0.0000 0 Qualified Non-Presort (No Qualifying Schemes) 0.0000 0 Unqualified (Failed Zip Verification) 0.0000 0

-------------- ------ Totals: 0.0000 0

Postage Savings: $ 61.506 (Based on single piece rate)

That’s it! You’ve processed your first mailing with Presort! The biggest step involves

completing the job file, which we’ll show you how to do, parameter by parameter, in Chapter 2 of this manual.

Presort Job-File Reference

Page 17

Chapter 1: Introduction to Presort Job

Page 18

Presort Job-File Reference

Page 19

Chapter 2: Job-file blocks and parameters

This chapter describes each parameter in Presort Job. Parameters are listed by block; blocks are listed in alphabetical order.

All parameters from the presort scheme blocks are explained together in “Presort scheme parameters,” on page 84. Likewise, all parameters from the report blocks are explained together in “Report parameters” on page 121.

Chapter 2: Job-file blocks and parameters

Page 20

Address Output File

Use this block when you want to create address labels through label-design and printing software, such as Business Objects Label Studio.

If the output file doesn’t already exist, you’ll also need a Create File for Output block. This block defines the structure of the file, and the Address Output File block puts data into that structure. The same path and file name must be entered in both blocks.

Important: Avoid file overwrite! For best protection, set up a separate

output subdirectory for each active job, and place no other files there.

If you use the File Protection feature, Presort warns you if your first split output file (Split output: when you split your output files by entry point, segment, presort scheme, version or bindery) is about to overwrite another file. The program does not check for overwrite on subsequent files.

Setup is important It is important that you take care in setting up your output files so that software

such as Label Studio can read and use all of the data. To help you fill out this block, we have included a template file with your Presort software that shows example Address Output File blocks. You can find the file in the template jobs; look for lsadr.pst.

Automatic supporting files

When you make any output file, Presort automatically produces supporting files (DEF and FMT files for example) to go with it. (If you’re not sure what we’re talking about here, read our Database Prep manual.) Presort assigns the same base file name to the supporting files that you used for the output file.

However, when you split output, Presort gives these support files fixed names (see table below), and they apply to all of the split output files.

Presort does not make supporting files to go with every split output file. Usually, that would be too many files to work with. Note that the x in the file name represents the block number of the Address Output block.

Address output files

Output File (location & file name)

Type a name for the output file, or copy it from the Create File for Output block.

By default, Presort will place the file in the current directory; if you want it placed somewhere else, include a path in your entry.

For information on naming split output files, see the File Name parameter in the Create File for Output block on page 33.

DEF FMT DMT

pst_adrx.def pst_adrx.fmt pst_adrx.dmt

Presort Job-File Reference

Page 21

Existing File (APPEND/REPLACE)

This parameter takes effect only if the output file already exists. You may choose to append the output records to the end of the file, or overwrite the file and replace its contents with the new output. If you are making a new file (using a Create File for Output block), this parameter has no effect. You may set it either way, it doesn’t matter.

+ Create Files Per Entry Point (Y/N) + Create Files Per Segment (Y/N) + Create Files Per Presort Scheme (Y/N) + Create Files Per Bindery/Ver (Y/N)

You can split your output files based on any or all of these: entry point, segment, presort scheme, version, bindery or piece type. When you do, Presort divides the output records into separate files. When all of these options are turned off, Presort produces one address output file that contains records for the entire job.

Note:

 If you do split your output files, you need to use file masking to name

the files. See page 33 for details.

 The records shown in your address output file also depend upon your

choices in the Output Selection block, where you can choose to output presorted pieces, qualified non-presort pieces, and unqualified pieces.

Create Files Per Piece Type

Splitting by presort status allows you to split address output into separate files. You can create output files for the following record types: Presorted (P), Qualified Non-presort (Q), Unqualified (U), Foreign (F).

For example, you may choose to create one output file for presorted records and another to hold non-presorted, unqualified, and foreign records.

Setting Description

P_Q_U_F Presort creates four output files: one for each record type.

P_QUF Presort creates two files: one for Presorted records and the other for

Qualified Non-Presorted, Unqualified, and Foreign records.

PQ_U_F Presort creates three files: one for Presorted and Qualified Non-Pre-

sorted records, one for Unqualified records, and one for Foreign records.

PQ_UF Presort creates two files: one for Presorted and Qualified Non-Pre-

sorted records and one for Unqualified and Foreign records.

P_QU_F Presort creates three files: one for Presorted records, one for Qualified

Non-Presorted and Unqualified records and one for Foreign records.

PQU_F Presort creates two files: one for Presorted, Qualified Non-Presorted

and Unqualified records and one for Foreign records.

PF_QU This option is for Periodicals only. Presort creates two files. One for

Presorted and Foreign records and one for Qualified Non-Presorted and Unqualified records.

Chapter 2: Job-file blocks and parameters

Page 22

Notes:

 When you set the Existing File parameter to Replace (see page 21),

Presort doesn’t create zero byte or empty files.

 If you split your output files, you need to use file masking to name the

files. See page 33 for details.

 The records shown in your address output file also depend on your

choices in the Output Selection block, where you can choose to output presorted pieces, qualified non-presort pieces, and unqualified pieces.

Create Files On Number of Records (Y/N) Max Number of Records Per File

You may use these two parameters to divide address output into separate files by an arbitrary number of records. This may be helpful for users who create very large address output files and who have a problem with the 2-gigabyte maximum file-size issue (On most 32-bit computers, the maximum size of any one file is 2 gigabytes). This option also might be useful if you want to be certain that each address output file will fit onto a tape or diskette.

You may use this feature together with the options to split output along mailing boundaries such as entry points, segments, schemes, versions, and binderies.

To use this option, you need to understand the concepts of split output and file masking. When you break on a fixed number of records, the file masking character to use is the percent sign (%).

+ Concatenate Files (Y/N)

+ PER Firm Pkg Printing

Read about split output and file masking in your Presort User’s Guide. Find the latest version on the most recent Documentation CD.

Select this optionType Ye s at this parameter if you want to combine multiple output files into one file. If you concatenate files, you cannot use mask characters (!, @, #, ? ,%) for file masking purposes in the file name; also, you must select at least one of the Create Files Per… parameters.

This parameter applies only to Periodicals mailings and only when firm packages are being formed.

Choose how to label firm packages. Most users find Package labeling appropriate.

Option Description

Piece

Package

You’ll get one address record (label) for each physical piece in a firm package.

You’ll get one address record (label) for each firm package.

Presort Job-File Reference

Record

You’ll get one address record (label) for each input record for a firm package. (This may result in more than one address record per firm package if a firm spans more than one package).

Page 23

Copy Input Data to Output File (Y/N)

Select this parameter to automatically copy data from input records to output records. Presort will look for field names that appear both in the input and the output file; that data will be copied over.

If a field exists in the input file but not in the output file, its data will not be carried over.

If you select this parameter, you may also post additional data to your output file, beyond the automatic copying. Use the Copy parameter described below. If you would rather post everything yourself, turn off this parameter and use just the Copy parameter (repeated as many times as necessary).

Copy (source, destination)

Use the Copy parameter to place data into one field of your output file. You can repeat this parameter as many times as necessary.

First, type the information that you want to post, then a comma, then the name of the field in the output file.

You can post database (DB), PW, application fields (AP), or constants. You can use filter functions and operators to modify data before posting it.

BEGIN Address Output File ========================= Output File (location & file name)... = brochure.dbf

Existing File (APPEND/REPLACE)....... = replace

+ Create Files Per Entry Point (Y/N). = n

+ Create Files Per Segment (Y/N)..... = n

+ Create Files Per Presort Scheme(Y/N)= n + Create Files Per Bindery/Ver (Y/N). = n Create Files On Number of Records(Y/N)= n

Max Number of Records Per File....... =

+ Concatenate Files (Y/N)............ = n

+ PER Firm Pkg Printing (see NOTE)... = piece Copy Input Data to Output File (Y/N). = y

Copy (source,destination)............ = ap.adr_bc_min, adr_bc_min

Copy (source,destination)............ = ap.adr_bc_max, adr_bc_max

Copy (source,destination)............ = ap.adr_bc_dgt, adr_bc_dgt

Copy (source,destination)............ = ap.ctn_brk_1, ctn_brk_1

END

Chapter 2: Job-file blocks and parameters

Page 24

Alternate Entry Point Sequence

Use this block if you want to rearrange the sequence of entry points from the normal output order (the order of entry points in the job file).

To use this block, you must also turn on the Sequence Output by Mailflow parameter in the Execution block and the Use Alternate Entry Point Sequence parameter in the Mailflow block.

Entry Point Name -- for Sequence

Copy and repeat this parameter as many times as necessary. You need a copy of this parameter for every entry point that you want to rearrange. Names must be spelled exactly right; to save time and avoid mistakes, do not type names over again. Instead, go back to the Entry Point Description block, copy the entry point name (only the name, which is shown after the equal sign), and paste it here. Any entry point that is defined in an Entry Point Description block, but not listed here will be processed in the order in which it appears in the job setup.

BEGIN Execution ===============================================

Presort (Y/N)........................ = y

+ Name Optimizer (Y/N)............... = n

1C/STD Ltr Postage Optimization (Y/N) = n

+ USPS Optional Procedures (Y/N)..... = n

+ Sequence Output by Mailflow (Y/N).. = y ...

BEGIN Mailflow ================================================ Use Alternate Entry Point Seq (Y/N).. = y ...

BEGIN Alternate Entry Point Sequence ==========================

Entry Point Name -- for Sequence..... = SCF Detroit MI

Entry Point Name -- for Sequence..... = SCF Saint Paul MN

Entry Point Name -- for Sequence..... = SCF Anchorage AK

END

Presort Job-File Reference

Page 25

Alternate Mailstream Hierarchy Sequence

Use this block if you want to change the sequence of the output hierarchy from the normal output order (entry point, segment, and scheme) to a different order.

You can also accomplish this through the Split Output feature, but using Alternate Mailstream Hierarchy instead offers two benefits:

1. Output remains in a single file (no need to split into separate files).

2. The output order of the reports reflects the new hierarchy.

To use this block, you must also enter Y at the following parameters:

Block Parameter

Execution

Mailflow

Sequence Output by Mailflow = Y

Use Alt Mailstream Hierarchy Seq = Y

New hierarchy You can establish a new hierarchy by changing the order of the three options any

way that you like. Output by scheme first, if you like, or output by entry point first, then by scheme, and finally segment; whatever fits your needs.

For example,

 You might want to keep segments

intact—that is, output all records for a segment together. To keep a segment intact, spanning entry points, change the hierarchy to:

Segment Entry point Scheme

 You might want to keep output

records together by presort scheme, ignoring entry points and segments. This option is handy if you use different label designs or different container types, depending on the presort scheme.

Segment is dominant

English segment: Phoenix ASF, Flats (CART) Phoenix ASF, Flats (Auto/Reg) Phoenix ASF, Qualified Nonpresort Denver BMC, Flats (CART) Denver BMC, Flats (Auto/Reg) Denver BMC, Qualified Nonpresort

Spanish segment: Phoenix ASF, Flats (CART) Phoenix ASF, Flats (Auto/Reg) Phoenix ASF, Qualified Nonpresort Denver BMC, Flats (CART) Denver BMC, Flats (Auto/Reg) Denver BMC, Qualified Nonpresort

Presort Scheme is dominant

Flats (CART): Phoenix ASF, English Edition

Phoenix ASF, Spanish Edition

Denver BMC, English Edition

Denver BMC, Spanish Edition

Keeping schemes together means you don’t have to switch labels or containers so often. In this case, change the hierarchy to:

Scheme Entry Point Segment.

Flats (Auto/Reg):

Phoenix ASF, English Edition

Phoenix ASF, Spanish Edition

Denver BMC, English Edition

Denver BMC, Spanish Edition

Qualified Nonpresort:

Phoenix ASF, English Edition

Phoenix ASF, Spanish Edition

Denver BMC, English Edition

Denver BMC, Spanish Edition

File #4, for Unqualified:

default entry point, no segment

Chapter 2: Job-file blocks and parameters

Page 26

Entry Point

Segment

Presort Scheme

If you want to change the hierarchy, indicate the position of each of these three parameters in the new hierarchy by typing a 1, 2, or 3.

For example, to move segment to the dominant position in the new hierarchy, you could set the parameters like this:

BEGIN Alternate Mailstream Hierarchy Sequence================

Entry Point.......................... = 2

Segment.............................. = 1

Presort Scheme....................... = 3

END

Presort Job-File Reference

Page 27

Alternate Presort Scheme Sequence

Use this block if you want to rearrange the sequence of presort schemes from the normal output order (the order of schemes in the job file).

To use this block, you must also turn on the Sequence Output by Mailflow parameter in the Execution block and the Use Alternate Presort Scheme Sequence parameter in the Mailflow block.

Presort Scheme Name -- for Sequence

Copy and repeat this parameter as many times as necessary. You need a copy of this parameter for every scheme that you want to rearrange. Names must be spelled exactly right; to save time and avoid mistakes, do not type names over again. Instead, go back to the Presort Scheme block, copy the scheme name, and paste it here. Any scheme that is defined in a Presort Scheme block, but not listed here will be processed in the order in which it appears in the job setup.

BEGIN Presort Scheme: STD_A, Automation Letters =============== ... BEGIN Presort Scheme: 1C/STD_A, Regular Letters =============== ...

BEGIN Alternate Presort Scheme Sequence ======================= Presort Scheme Name – for Sequence.. = 1C/STD_A, Regular Letters Presort Scheme Name – for Sequence.. = STD_A, Automation Letters END

Multiple occurrence of same block

Many schemes can occur more than once in a single job file. If you want to change the output sequence of these schemes, you must type the scheme name and follow it with a number that indicates the original order of the blocks in the job file.

For example, suppose we have two 1C, Flats schemes in our job file. One is set up as an automation scheme (the Preparation Type parameter is set to Automation); the second one is set up as a regular scheme (Preparation Type is set to Regular).

Suppose that we want to output the regular-rate pieces before the automation-rate pieces. We would set up the Alternate Presort Scheme Sequence block like this:

BEGIN Alternate Presort Scheme Sequence ======================= Presort Scheme Name – for Sequence.. = 1C, Flats 2 Presort Scheme Name – for Sequence.. = 1C, Flats 1 END

Chapter 2: Job-file blocks and parameters

Page 28

Alternate Segment Sequence

Use this block if you want to rearrange the sequence of segments from the normal output order (the order of segments in the job file).

Note: Presort can process your mailing much more quickly if, instead of using Mailflow to change the order of segments, you simply change the order of the Segment Description blocks in your job file so that they are in the desired order (that is, if you are not using Auto Segmenting).

To use this block, you must also turn on the Sequence Output by Mailflow parameter in the Execution block and the Use Alternate Segment Sequence parameter in the Mailflow block.

Segment Name -- for Sequence

Copy and repeat this parameter as many times as necessary. You need one copy of this parameter for every segment that you want to rearrange. Names must be spelled exactly right; to save time and avoid mistakes, do not type names over again. Instead, go back to the Segment Description block, copy the Segment Name, and paste it here (that is, if you are not using Auto Segmenting). Any segment that is defined in a Segment Description block, but not listed here will be processed in the order in which it appears in the job setup.

BEGIN Segment Description =====================================

Segment Name (to 31 chars)........... = Eastern Edition

...

BEGIN Segment Description =====================================

Segment Name (to 31 chars)........... = Western Edition

...

BEGIN Alternate Segment Sequence ==============================

Segment Name -- for Sequence......... = Western Edition

Segment Name -- for Sequence......... = Eastern Edition

END

Presort Job-File Reference

Page 29

Auxiliary Files

This block is required! With the Presort program, you’ll receive several supporting files filled with USPS

data. At this block, tell Presort where it can find these supporting files. This information must be accurate.

ZCF Directory (path & zcfxx.dir) Mail Proc Ctr Dir (path & mpcxx.dir) PER/PSVC Zone Dir (path & zone.dir) +PER/STD Del Stats (path & dsf.dir) Mail Direction (path & facility.dir) Mail Direction (path & maildirect.dir)

The names of the required directories are entered for you. If you plan to use the Zone Directory (zone.dir) or the Delivery Statistics File (dsf.dir) as well, type the name of the directory file at the respective parameter.

Before each name, insert a path to identify where each file has been installed.

System Usual location

Windows/NT \pw\dirs

UNIX postware/dirs

The USPS requires mailers to use up-to-date ZIP City File (zcfxx.dir) directory data to determine eligibility for automated carrier-route mailings, up-to-date Mail Processing Center (mpcxx.dir) directory data to determine how to form 5-digitscheme containers, and up-to-date Delivery Statistics File (dsf.dir) when preparing walk-sequence mailings. (The “0x” here represents the version of the directory.) The data is updated by the USPS, and thus by Business Objects, every two months. Be sure to use the most current directory that we send you!

Here are descriptions of some of the files.

zcfxx.dir If you include an automated carrier-route scheme in your job file, Presort will

verify the date of your zcfxx.dir file. If the file is out of date (if you haven’t installed the latest copy of the directory provided by Business Objects), Presort will issue an error message.

If the data is current, Presort will process your job. The USPS then requires you to submit the mailing within 90 days from the date that you process your job with Presort.

Look at the report called the Job Summary. Just before the first presort scheme information is listed, Presort prints the last date that you may enter the mail (the current date plus 90 days).

mpcxx.dir If you choose to create 5-digit-scheme containers, Presort will automatically

check the date of your mpcxx.dir. If the file is out of date, Presort will issue an error message.

Chapter 2: Job-file blocks and parameters

Page 30

You must submit the job before the data expires—within 90 days of the date that the USPS released the data.

Presort prints on the Job Summary the date of the mpcxx.dir that you used to process the job. This is the date that the USPS released the data. Add 90 days to this date to determine the latest date you can submit this job to the USPS.

zone.dir For Periodicals and Standard Mail mailings, Presort uses data in the Postal Zone

directory file (zone.dir) to calculate postage based on the distance between entry and delivery offices.

dsf.dir If you prepare walk-sequence mailings, Presort will use the Delivery Statistics

File to verify that the data complies with USPS requirements for receiving saturation and high-density rates.

Presort will automatically check the date of your dsf.dir. If the file is out of date, Presort will issue an error message.

You must submit the job before the data expires—within 105 days of the date that the USPS released the data.

facility.dir This directory contains information about USPS drop ship facilities, such as drop

site keys, drop site names, and drop site delivery addresses.

maildirect.dir This directory contains information about where and when mail pieces should be

dropped in order to receive discounts on the bases of class and shape.

Default ASCII FMT (path & file.fmt) Default DEF (path & file.def)

If you use multiple input files for this job and they are all in the same format, you can create just one format (FMT) file to serve all input files. Type its path and name on this line. The same idea applies to definition (DEF) files.

You also may want to set up default FMT and DEF files if you work with a single input file whose format always stays the same. So, if you use a house.txt file every day or every week, you can save time by setting up default DEF and FMT files; no need to set up a house.def file and house.fmt file.

If you have one or two files that differ from the standard format, you must create an individual FMT or DEF for the exceptions. Presort looks for an individual FMT or DEF file. If it finds one, Presort will override the default file. If your input files do not share the same format, leave these lines blank, and use individual FMT and DEF files all the time.

Note that there are two parameters in the Input File block of which you should be aware. See “Override Default Format (path & file name)” on page 60 and “Override Default DEF (path & file name)” on page 60 for more information.

For more information on DEF and FMT files, see the Database Prep manual. Find the latest version on the most recent Documentation CD.

Presort Job-File Reference

Page 31

Container Output File

Use this block if you want to create tray or sack tags with label-design and printing software such as Label Studio.

Important: Avoid overwriting files! For best protection, set up a separate

output subdirectory for each active job, and place no other files there.

If you use the File Protection feature, Presort warns you if your first split output file is about to overwrite another file. The program does not check for overwrite on subsequent files.

Setup is important It is important that you take care in setting up your output files so that software

such as Label Studio can read and use all of the data. To help you fill out this block, we have included two template files with your Presort software. One file is set up with examples of tray mailings, (lstry.pst); the other with examples of sack mailings (lssck.pst).

Automatic supporting files

When you make any output file, Presort automatically produces supporting files—DEF, FMT, and so on—to go with it. (If you’re not sure what we’re talking about here, read our Database Prep manual.) However, when you split output, Presort gives these support files fixed names (see table below), and they apply to all of the split output files.

Container output files

Output File (location & file name) Existing File (APPEND/REPLACE) + Create Files Per Entry Point (Y/N) + Create Files Per Segment (Y/N) + Create Files Per Presort Scheme (Y/N) + Concatenate Files (Y/N) Copy (source, destination)

See “Address Output File,” on page 20 for parameter descriptions.

DEF FMT DMT

pst_ctnx.def pst_ctnx.fmt pst_ctnx.dmt

Chapter 2: Job-file blocks and parameters

Page 32

Container Sequence

Container Sequence gives you some control over the order in which Presort produces trays and sacks within each mailing. It affects reports (for example, the Mail Sort Listing), and address and container output files.

The normal container sequence makes sense for most users and jobs. Containers are output by sortation level, then by ZIP Code. Zone and destination-entry rates do not directly affect container sequence.

To use this block, you must turn on the Sequence Output by Mailflow parameter in the Execution block and the Use Container Sequence parameter in the Mailflow block.

PER/PSVC Dest Zone PER/STD Dest Rate Sort Level Destination ZIP

If you want to change the normal container sequence, use these parameters. There are up to four ways to sort containers. To indicate the priority that Presort should use when reordering, assign a unique number to each parameter that you want to activate (using 1, 2, 3, and 4). If you do not want to and are not required to sequence containers in a particular way, set that parameter to inactive. This will reduce processing time by reducing Presort’s workload.

Also, you cannot use Container Sequence to control what packages or pieces are included in containers or what containers are included in a mailing.

In addition, you can choose the priority or precedence of sorting, but not the direction. The direction of sorting is always as follows:

Sequence option Containers Packages

Zone Local, 1, 2, 3, 4, 5, 6, 7, 8

Rate DDU, DSCF, DBMC, none None, DBMC, DSCF, DDU

Sort Level Carrier-route-direct to mixed AADC

ZIP 00000 to 99999

BEGIN Container Sequence ======================================

PER/STD_B Dest Zone (See NOTE)....... = inactive

PER/STD_A Dest Rate (See NOTE)....... = inactive

Sort Level (See NOTE)................ = inactive

Destination ZIP (See NOTE)........... = 1

END

* NOTE Container Sequence entries: * Inactive -- Option not used * 1/2/3/4 -- Order of priority to perform reordering

Presort Job-File Reference

Page 33

Create File for Output

Use the Create File for Output block to create a new file and to define the physical format of that file. These files contain the data needed by label-design and printing software to print labels for mail pieces and containers.

You’ll need one copy of this block for each new output file that you want to create.

Keep in mind that this block creates only the structure of a file. You will need another block to post information into your new file. See any of the following blocks: Address, Package, Container, or Pallet Output File.

If you want to send output to an existing file, you do not need this block.

Setup is important It is important that you take care in setting up your output files so that software

such as Label Studio can read and use all of your data. To help you fill out this block, we have included four template files with your Presort software that you can use as examples when setting up different types of output files. You can find them in the Templates folder.

Output file Template file

Address

Tray

Sack

Pallet

Each of these sample files contain two sets of Create File for Output and Output File blocks. One set shows the basic fields that most people will need for a typical job. The second set shows all possible fields.

File Name (path & file name)

Type a name for the output file. By default, Presort will place the file in the current directory. If you want Presort to place it somewhere else, include a path in your entry.

lsadr.pst

lstry.pst

lssck.pst

lsplt.pst

Chapter 2: Job-file blocks and parameters

Page 34

Naming split output files

If you create split output, you must use a method called file masking to design your own pattern for naming the output files.

File masks can consist of letters and five special punctuation marks that represent all the possible ways that you can split the output:

Separate output files by Mask character

Entry Point !

Segment @

Presort scheme #

Bindery/Version ?

Fixed number of records %

Status &

For example, if you have 88 entry points, 38 segments, 3 presort schemes, and 135 versions/editions, then you might use a mask like this:

#e!!v???.s@@

Then the file name would be “3e01v044.s22” for scheme #3, entry point #1, version #44, and segment #22.

Of course, this is only one example of dozens of ways that you could arrange the information. Here are some guidelines for designing your own file masks:

 You must allot enough mask characters in the name to accommodate all the

file names to be generated. For example, if you are splitting by segment, and your job has 115 Segment Description blocks, then “ valid mask. However, “

test@@@.dbf” or “test@@@@.dbf” would be

test@@.dbf” is not a

valid.

 You may use the file-name extension to specify the mask. For example,

test.@@@” is valid.

“

 You may not span a mask across the base file name and the extension. For

example, “

 All characters within a mask must be consecutive. For example,

@@test@@.dbf” is invalid.

“

 If you use the Auto Segmenting, Auto Version, or Auto Dimension features,

test@@.@@” is invalid.

then the number of segments or versions will not be known at the time your job file is verified. The verifier will issue a warning that your mask may not be big enough to accommodate all the possible file names.

 If your mask is too small, Presort will exit with an error when the mask limit

is reached. For example, if there are 115 segments and only 2 characters for the mask, then Presort would stop creating output files after segment #99.

Presort Job-File Reference

Page 35

File Type

Create DEF File (Y/N)

Choose the file type you want to create:

 ASCII

 DELIMITED

 DBASE3

 EBCDIC

Turn on this option if you want Presort to create a DEF file to accompany the output file. The DEF file will be nearly empty and useless, but if you use the output file as input to Label Studio, you will need the corresponding DEF file. You may use this DEF file or a default DEF file.

For example, if you create an output file named clancy.dat, Label Studio will look for a corresponding DEF file named clancy.def when you use clancy.dat as input.

Here’s an example showing why you’d want to set the parameter to No:

Suppose you want to use clancy.dat as a pallet input file in a Label Studio job. But you want Label Studio to apply your default, “master” DEF file—let’s call it pallet.def—to all pallet input files. Set this parameter to No to ensure that Label Studio will not find a file named clancy.def.

If you select No, Presort still creates the automatic DEF file, but then deletes it. If you have a “good” DEF file of the same name, in the same location, Presort will leave it alone and not overwrite it. We suggest that you keep your default DEF files in a central location, such as your Label Studio subdirectory.

Rec Format to Clone (path & file name)

If you want, you may clone or “borrow” the physical format (structure) of any existing file. Type the name and location of that file here.

The file that you name here need not be one of the input files for this job. Presort will duplicate only the physical format of that file, not its data. If you want to define the format of your output file “from scratch,” leave this line blank.

You may add more fields to the end of each record by using the Field parameter. However, you cannot intersperse new fields among those cloned.

Chapter 2: Job-file blocks and parameters

Page 36

Field (name, length, type [,misc])

The Field parameter defines the name and physical format of one field in the new file. Copy this parameter as many times as necessary.

dBASE3 When you’re creating a dBASE3 output file, observe the following rules:

File characteristic

Rule

Name Conform to the dBASE3 field-naming rules: Maximum of 10

letters or numbers (first character must be a letter) and the only valid punctuation mark is underscore ( _ ).

Length Valid field length depends on the field type:



Character 1 to 254



Numeric1 to 19



Logical 1



Date 8

Note:

For dBASE3 files, the total length of all fields is limited

to 128 characters.

Type Specify the field type:



Character (printable ASCII characters only!)



Numeric



Logical



Date (yyyymmdd format)

[Decimal]

When the field type is numeric, you can add a fourth item, the decimal position. Type the number of digits to the right of the decimal point. If you omit the number of decimal places, the program will treat it as zero.

Delimited ASCII Your job file must include a Create File block if the delimited file will be created

new. The length you give will be used as a maximum length.

If the delimited output file will not be comma delimited, then you must comment out the Create File for Output block and set up a DMT file.

Presort Job-File Reference

Page 37

Fixed ASCII When creating a fixed-length ASCII output file, follow these guidelines. These

are the same instructions that you follow when creating an FMT file.

File characteristic

Rule

Name ASCII field names may consist of up to 127 printable charac-

ters.

Length Valid field length depends on the field type:



Character 1 to 32,767



Binary 1 to 32,767



Date1 to 32,767



Numeric 1 to 19



Packed numeric 2 to 8

Type Specify the field type:



Character (printable ASCII characters only!)



Binary (unprintable ASCII, EOR, filler, etc.)



Date



Numeric



Packed numeric

[Date] For Date fields, use the miscellaneous area to specify almost

any format that will fit into your field length. Use the abbreviation

for date, MM or

MMM

for month, and

YYYY

for year, in any order. Use a hyphen or slash for the delimiter. For example:

yyyy/mm/dd mmm-dd-yyyy

2000/10/11

Oct-11-2000

[Decimal] When the field type is numeric, you can add a fourth item to the

miscellaneous area, the decimal position. Type the number of digits to the right of the decimal point. If you omit the number of decimal places, the program will treat it as zero. In your output numeric field, the data will be right aligned with leading spaces.

[Packed] For packed numeric fields, use the miscellaneous area to spec-

ify the number of significant digits (to the left of the decimal point). If you omit the number of digits, Presort will assume that that number is twice the field length, less one.

Refer to your Database Prep manual for more information about working with dBASE and ASCII files. For the most recent version, refer to the latest Documentation CD.

Chapter 2: Job-file blocks and parameters

Page 38

Entry Point Defaults

If you are not planning to enter mail at multiple entry points in this job, you may skip this block and set up one Entry Point Description block. By drop-ship, we mean that you plan to enter mail at more than one USPS facility to gain postage discounts or faster delivery.

If you drop-ship, this block is required. Since you’ll need to set up multiple Entry Point Description blocks, you can use this block to save time by setting those parameters that are common to all of your entry points just once. Then leave the corresponding parameters in the individual Entry Point Description blocks blank. For example, if all of your mail is verified at one postal facility, you can set the parameters for Origin Post Office here in the Entry Point Defaults block and leave those parameters blank in the Description blocks.

Entry Point Type

What type of USPS facility is this?

 BMC (Bulk Mail Center)

 ASF (Auxiliary Service Facility)

 SCF (Sectional Center Facility)

 IBMC (International and Bulk Mail Center)

 ADC (Area Distribution Center, PER only)

 DDU (Destination Delivery Unit)

 Other (local post office or other facility not listed above)

Note: Currently, the New Jersey BMC is the only facility that is considered

an IBMC. Foreign mail entered at this IBMC may be eligible for a discount. For details, see “PER Foreign Entry Point Name,” on page 43.

Important: If you select DDU as an entry point type, Presort treats it as if

you had chosen Other. (“Other” includes local post office or other facility type not listed in Presort). The only function of the DDU entry point type

is to output the value to Mail.dat.

Presort Job-File Reference

Page 39

Scheme Nums per Entry Pt

Normally, you would apply all schemes to each entry point in a job. Presort does this automatically. However, in some cases, you may want to apply only certain schemes to a particular entry point or points (see the Presort User’s Guide for examples).

Use this parameter to limit sorting to a specific subset of schemes in all (or most) entry points.

Important: As in all jobs, when you use this feature, you must be careful to

place the schemes in sortation order in your job. For example, you would place a carrier-route scheme before an automation scheme before a regular scheme.

So, when you assign numbers to those schemes, the numbers will reflect the logical sortation order (the #1 scheme will be the highest sortation level, the #2 scheme will be the next highest sortation level, and so on).

To link schemes to entry points, you must first number the active schemes in the job file. Active means that the scheme is not commented out. If you comment-out a scheme, it is not processed or assigned a scheme number.

Scheme numbers work the same way as the output field AP.Scheme_No. Scheme numbers run from 1 to 99, per sequence of Presort Scheme sections in the job file. They are not affected by Mailflow. There is no scheme number for qualified nonpresort, unqualified, and foreign pieces.

Here's how to number the active schemes:

1. Type a number above each scheme in the job file, in a comment (see example below). Start by typing 1 above the first scheme in the job, 2 above the next, and so on.

2. To apply selected schemes to an entry point, type the scheme numbers, separated with a comma, at the Scheme Numbers per Entry Point parameter in this block.

3. At individual entry point blocks, you may override these default settings by typing a different set of numbers or by typing all to select all of the schemes in the job for that particular entry point

Note: If you type scheme numbers out of numerical sequence, Presort still

will process schemes in the order in which scheme blocks appear in the job file. The scheme numbers that you assign serve only as a label to identify which schemes to include in the entry point, not the scheme order.

* Scheme 1 BEGIN Presort Scheme: STD_A, Enhanced Carrier Route =========== ... * Scheme 2 BEGIN Presort Scheme: STD_A, Enhanced Carrier Route =========== ... BEGIN Entry Point Description =================================

Entry Point Name (to 31 chars)....... = West Salem WI (DDU CART only)

... Scheme Nums this Entry Pt (see NOTE). = 1,2 ...

Chapter 2: Job-file blocks and parameters

Page 40

PER/STD/PSVC QFY for DDU Rate (Y/N)

This parameter pertain to drop-shipping discounts for DDUs (Destination Delivery Unit). Find your settings for this parameters in the table below. Processing centers are listed in the labeling lists module in the USPS Domestic Mail Manual. See details on drop-shipping discounts in the Presort User’s Guide.

Periodicals Standard Mail Package Services

If entry facility is a: If entry facility is a:

Parame-

BMC ASF ADC SCF Local BMC ASF ADC SCF Local

ter

DDU

no yes yes yes yes no yes no yes yes

Rate

This rate is applied only to CART-presorted mail (and to non-CART mail in PSVC Bound Printed Matter).

In Periodicals, only carrier-route mail delivered from the entry point is eligible for DDU.

For Standard Mail automated carrier-route mail, ask the USPS district dropshipment coordinator where you can claim the DDU discount for this type of mail. Other Standard Mail carrier-route mail is eligible for the DDU discount on mail delivered from the entry point.

PER/STD/PSVC Use USPS DDU Data (Y/N)

Select this parameter if you want Presort to use USPS data to determine whether the mail pieces are eligible for the DDU discount. In some cases, the USPS data is not complete enough to ensure discounts on all eligible mail.

If entry facility is a:

BMC ASF ADC SCF Local

no yes no yes yes

We suggest that you set this parameter to Ye s only if you are claiming DDU rates for mail dropped at and delivered from an SCF. If you set this parameter to Ye s for an entry point that is not an SCF, Presort will issue an error.

Note: For Periodicals pallets drop-shipping at an ADC that is co-located with an SCF, choose to use USPS data for the DDU discount.

You must set this parameter to No if this job involves—

 Periodicals or Standard Mail regular carrier-route mail, and you drop at local

post offices to receive the DDU discount. Set the range parameters in the individual Entry Point Description blocks (see page 49).

 Standard Mail automated carrier-route letter mail

Origin Post Office City (to 20 chars) Origin Post Office State (to 2 chars) Origin Post Office ZIP Code (10 chars)

Type the city, state, and ZIP Code of the post office where your mail is verified and accepted, and (usually) where the postage is paid.

Presort Job-File Reference

Page 41

Create Undrfill Local 3DG/SCF Ctns Y/N

We suggest that you set this parameter to Yes.

If your entry point post office and your origin post office are the same (that is, if the ZIP Codes are the same), you must set this parameter to Yes.

In tray schemes, the USPS recommends that you create an underfilled 3-digit or 3-digit-scheme tray for every entry point where you drop mail. If you set this parameter to Yes in the Entry Point Defaults block, Presort will do just that.

Regardless of the way you set this parameter, Presort will automatically create one underfilled 3-digit or 3-digit-scheme tray for every 3-digit ZIP Code area that is served by the SCF of the local post office where you verify your mail. The USPS requires it.

In PER Automation Flats and PER Regular Flats schemes, the underfilled local container is an SCF sack.

An underfilled container is a partial container that is not associated with any full container. (Compare with overflow, which is a partial container that accompanies a full container destined for the same location.)

Trayed pieces will receive the basic rate. Pieces must be packaged. (Note: 5-digit and 3-digit packages of automation flats in 3-digit origin sacks receive the 3/5 rate.)

Pieces in sacks will receive the package rate; non-automated flats receive the basic rate and automated flats receive the automation 3/5 rate.

Note: A 3-digit-scheme tray includes pieces from more than one 3-digit ZIP

Code served by the SCF. In accordance with USPS rules, Presort creates a 3digit-scheme tray where applicable for automated letter schemes only.

If you’re preparing Standard mail and you use Mail.dat files to create an entry plan after presorting, you should set this parameter to No in the Entry Point Defaults block. Then set it to Yes only in the Entry Point Description block for the local post office where you verify your mailing (the USPS requires that you create an underfilled local 3-digit container for the entry point where you verify your mailing).

Min Auto 5DG/SCH Lvl(150 to 3000/FULL)

Specify the minimum size of a 5-digit sack or tray. If you type the word "FULL," then Presort only makes the tray if it is 75 percent full. For 5-digit packages, you can set the minimum package size differently in each scheme in your job if you want.

Chapter 2: Job-file blocks and parameters

Page 42

Min SCF/ASF Local 3DG Pallet Weight Min SCF/ASF Local SCF Pallet Weight Min SCF/ASF Loc 3DG Plt Tray Ft (1-144) Min SCF/ASF Loc SCF Plt Tray Ft (1-144)

You may prepare 3-digit and SCF pallets with less than the normal minimum pallet weight (250 pounds) if both of the following conditions apply:

 You receive special authorization from the USPS Processing and Distribution

Manager at each facility.

 The entry point is an SCF or an ASF.

Because you can negotiate the minimum weight on a facility-by-facility basis, you may need to set these parameters in the Entry Point Description blocks instead of in the Entry Point Defaults block.

Set the Min SCF/ASF Local 3DG Pallet Weight and the Min SCF/ASF Local SCF Pallet Weight parameters to the agreed-upon minimum 3-digit and SCF pallet weights, in pounds.

If you are preparing trays on pallets, set the Min SCF/ASF Local 3DG Plt Tray Ft and the Min SCF/ASF Local SCF Plt Tray Ft parameters. Specify the minimum number of feet of trays on an SCF pallet (from 1 to 144 feet). If you leave this blank, Presort uses your Default setting.

You must have USPS permission to set the minimum outside of the range of 1 to 144 feet.

Min Pieces Min Pounds

If you’re drop shipping, you can use these parameters to “cancel” an entry point when there isn’t enough mail to make it worthwhile. When you set these parameters, you must work within the minimum piece and/or pound requirement for the class of mail:

Class Minimum Pieces

Req.

Minimum Pounds Req.

First 500 0

Periodicals 0 0

Standard Mail 200 50

Package Services Bound Printed Matter 300 0

Package Services Media Mail & Library 500 0

Package Services Parcel Post & Select 50 0

Note: The minimum number of pieces (500) for Package Services Special

Standard and Library jobs applies per sortation level, not per mailing as it does for other classes.

Presort Job-File Reference

Page 43

Most mailers use this feature to make sure that their trucks will be full. For example:

Standard: Suppose you calculate that trucking to the Denver BMC will cost $950. The DBMC discount at this writing is 2.1¢ per piece. To make the Denver trip worthwhile, you need the DBMC discount on at least 45,250 pieces (2.1 X 45,250 = 950.25). You would set the Min Pieces parameter to 45250.

Periodicals: You might make a similar calculation when dropping a Periodicals mailing at an SCF. But you would be more interested in Min Pounds, because your drop-ship savings are based on weight, not number of pieces.

Presort will prepare the mailing if there is enough mail to meet either Min Pieces or Min Pounds. Once you’ve chosen to use either Min Pieces or Min Pounds, set the other parameter according to some impossibly high number.

Min Pieces = 45250 Min Pounds = 10000000

We set Min Pounds at 10 million, so it will never be met. Furthermore, we’ll enter mail at Denver only if we have at least 50,000 pieces destined there.

PER Foreign Entry Point Name

If this job involves an input file with foreign pieces, you’ll need to identify one of the entry points as the point where you plan to enter foreign mail. This ensures that Presort prints information about the foreign pieces on the correct USPS 3541 form, for example. Use the same entry that you use at the Entry Point Name parameter at one of your Entry Point Description blocks.

Note that Presort reports will show that foreign pieces are entered here even if domestic mail fails to qualify at this entry point.

If you do not set this parameter, then Presort will treat foreign pieces as though the entry point is undetermined and will handle them according to your setting at the Action parameter (see “Action (ASSIGN LAST EP/IGNORE/ABORT),” on page 44).

If you plan to drop foreign mail at the New Jersey IBMC (International and Bulk Mail Center), that mail may be eligible for a discount per pound. Presort will automatically calculate the discount if you:

1. Set up an Entry Point Description for the New Jersey BMC

2. Type the name of that entry point at this parameter

Select IBMC at the Entry Point Type parameter

Consult the DMM for current discount amounts.

Estimated Date Dropped (MMDDYYYY) Estimated Time Dropped (HHMM)

Enter the estimated date and time that you plan to drop the mailing at the USPS facility.

Chapter 2: Job-file blocks and parameters

Page 44

Del Window Start Date (MMDDYYYY) Del Window End Date (MMDDYYYY)

If you plan to participate in the USPS CONFIRM program with this mailing, estimate the first and last date in the date range for in-home delivery of this shipment.

For more information about CONFIRM, see “Participate in USPS CONFIRM Prog (Y/N),” on page 52.

Action (ASSIGN LAST EP/IGNORE/ABORT)

If Presort cannot fit a record into any of the entry points that you have set up, your options are as follows:

 Assign Last EP: Assign the record to the default entry point, which is the

last entry point that you define in this job.

 Ignore: Leave the record out of the job. This will occur only if the record

doesn’t fit into any entry point, including the default entry point.

 Abort: Stop processing. This will occur only if the record doesn’t fit into any

entry point.

Presort Job-File Reference

Page 45

Entry Point Description

This block is required! Every job must include at least one Entry Point Description block. If you enter

mail from a single job at several post offices, you’ll need one block for each office.

As you fill out this block, you’ll need several facts about the post office where you plan to deposit your mail. Accuracy is important to ensure that the USPS accepts your mail and that you receive all possible discounts. For USPS facility information, call your postmaster.

Creating entry point templates

You can use the maildirshow utility to create entry point templates. To run the utility, do the following:

1. Open a command prompt and navigate to the directory where the maildirshow utility is located.

2. Type maildirshow.exe and press Enter.

3. Enter the discount type, mail class, mail shape, estimated drop date, the path to and the name of the directories (maildirect.dir or facility.dir), and the output file name and press Enter.

ADCs that are co-located with SCFs

Some ADCs are co-located with SCFs (sectional center facilities) and DDUs (destination delivery units).

To set up your job for pallets going to co-located ADCs:

1. Include an ADC entry point and select the DADC, DSCF, and DDU discount options.

2. Choose to use USPS data for the DDU discount.

Entry Point Name (to 31 chars)

Type the name of the office or facility where you plan to enter this mail. The name should not necessarily repeat the city, state, and ZIP Code fields. Here are some examples:

 Dallas PO So. Branch  Hopkins Post Office  Billings ASF Dock 10

+ Value in PostWare Field Entry_ID

Some Presort users have a coded field in their input files that identifies the entry point for each record. If you want, Presort can assign pieces to entry points based on this input ID field, rather than by ZIP Code range.

To use an entry-point ID, create an ID field in your input file. Then in your DEF file, set Entry_ID equal to the ID code field (for example, Entry_ID = EP_CODE).

At this parameter, type the value that links records with this entry point. If all pieces are destined to the same entry point, leave this field blank.

Chapter 2: Job-file blocks and parameters

Page 46

If an entry point ID for a mail piece doesn’t match any of the values in the Value in PostWare Field Entry_ID parameters, that piece will be assigned to the default entry point (if you have set the Action parameter to Assign Last EP).

Essentially, you may assign pieces to entry points using one of three methods:

 Entry point ID  ZIP Code range (see the Range parameter on page 49)  Both entry point ID and ZIP Code range

If you use both the entry point ID and the ZIP Code range to define an entry point, Presort will assign the mail piece to the first entry point that it is able to match either the range or the ID or both.

Entry Point Post Office City (20 chrs) Entry Point Post Office State (2 chrs) Entry Point Post Office ZIP Code (10)

Type the city, state, and ZIP Code of the USPS facility where you plan to enter this mail.

Entry Point Type

See the Entry Point Defaults block on page 38 for description.

Scheme Nums this Entry Pt

Use this parameter to tell Presort which schemes to apply to this particular entry point. If you want Presort to use all schemes for this entry point, simply type all here. If you wish, you can leave the parameter blank in this block; Presort will use the settings, if any, that you make at the same parameter in the Entry Point Defaults block.

See this parameter at the Entry Point Defaults block on page 39 for instructions on linking schemes to entry points.

PER/STD/PSVC QFY for DDU Rate (Y/N) PER/STD/PSVC Use USPS DDU Data (Y/N) Origin Post Office City (to 20 chars) Origin Post Office State (to 2 chars) Origin Post Office ZIP Code (10 chars) Create Undrfill Local 3DG/SCF Ctns Y/N

See the Entry Point Defaults block beginning on page 38 for descriptions.

Presort Job-File Reference

Page 47

Create Small Service Area Plt (Y/N)

Select Yes to form one underfilled pallet for the entry-point service area. Presort will create this pallet only if the entry point is an ASF or SCF in Standard Mail jobs, or an SCF in Periodicals jobs.

Note: There is no minimum weight or volume for this pallet, so these pallets

could be very small, literally as small as one package.

Min SCF/ASF Local 3DG Pallet Weight Min SCF/ASF Local SCF Pallet Weight Min SCF/ASF Local 3DG Plt Tray Ft (1-144) Min SCF/ASF Local SCF Plt Tray Ft (1-144)

See “Entry Point Defaults,” on page 38 for descriptions.

Min Pieces Min Pounds

If you plan to enter mail only at this entry point, type one of the numbers below, according to your class of mail. If you’re drop-shipping in this job, see “Entry Point Defaults,” on page 38 for the parameter descriptions.

Class Minimum Pieces

Required

Minimum Pounds Required

First 500 0

Periodicals 0 0

Standard Mail 200 50

Package Services Bound Printed Matter 300 0

Package Services Media Mail & Library 500 0

Note: The minimum number of pieces (500) for Package Services Special

Standard and Library jobs applies per sortation level, not per mailing as it does for other classes.

Chapter 2: Job-file blocks and parameters

Page 48

PER IC Disc Eligibility (ALL/SUB/NONE) PER County of Publication

In Periodicals, some of your mail may qualify for in-county rates. If that's the case in this job, you can claim in-county discounts on all or some of your mail pieces with the PER In-County Discount parameter.

You may choose to apply the in-county rate to:

 all of the pieces in your mailing that apply  subscribers only  none of the pieces

To use the subscribers-only option, your database must contain a field that indicates whether the person is a paid subscriber. And you have to present that field to Presort, through your DEF file, as the field PW.Subscriber.

To determine if a record is eligible for in-county rates, Presort can use either the address record's ZIP or a discrete county field in your input records. Presort will tally the number of in-county mail pieces and calculate the discount.

To qualify for the in-county discount:

 The mailing must include fewer than 10,000 copies or more than half the paid

circulation must be distributed within the county.

 At least 90 percent of the recipients must be subscribers.

 Pieces must be dropped at entry points in the county in which the publication

originated.

It is your responsibility to ensure that the first two requirements are met.

If you select this feature, also select the PER Subscriber Options parameter at the Mailing Information block.

At the PER County of Publication parameter, type the 3-digit county code. Set this parameter in the Entry Point Description blocks only for the entry points at which you intend to take the in-county discount.

If you set the PER In-County Discount parameter, but leave PER County of Publication parameter blank, Presort will determine the county of publication by the origin state and ZIP Code. But, since the county of the entry point and the county of publication might differ, it is important that you complete the County of Publication parameter.

For ZIP-Codes that cross county lines

To correctly assign the county code for ZIP-Codes that cross county lines, use ACE to assign the correct county code to your addresses, then include the PW.County field in your DEF file, and enter the county code for the county of publication in the Entry Point Description block.

Estimated Date Dropped (MMDDYYYY) Estimated Time Dropped (HHMM)

Estimated date and time on which you will deliver this shipment to the post office.

Presort Job-File Reference

Page 49

Override USPS Mail Direct Disc (Y/N)

Enable this option if you do not want to use the maildirect.dir file for verification or discounts. The maildirect.dir file contains information about where and when mail pieces should be dropped. If you disable this option, all pieces in the Zip Code range will receive a discount.

Appointment Number (12 chars)

If you plan to participate in the USPS CONFIRM program with this mailing, enter the drop-ship appointment service (DSAS) number that the USPS assigns to you when you call to make an appointment to submit this drop-ship mailing.

See “Participate in USPS CONFIRM Prog (Y/N),” on page 52 for more information about CONFIRM.

Del Window Start Date (MMDDYYYY) Del Window End Date (MMDDYYYY)

If you plan to participate in the USPS CONFIRM program with this mailing, estimate the first and last date in the date range for in-home delivery of this shipment. For more information about CONFIRM, see “Participate in USPS CONFIRM Prog (Y/N),” on page 52.

Range (lower ZIP-upper ZIP) PER/STD/PSVC Range QFY for DDU (Y/N)

The Range parameter tells Presort which ZIP Codes are served by this entry point. The PER/STD/PSVC Range QFY for DDU parameter tells whether or not that range of ZIP Codes is eligible for the Destination Delivery Unit (DDU) discount.

Without Destination Entry If you’re not interested in DDU discounts, fill out these parameters like this:

Range (lower ZIP-upper ZIP) . . . . . = 00000-99999

PER/STD Range Qualified for DDU (Y/N) = No

This is all you need if:

 You mail First Class or

 You drop all of your mail at just one post office and you make no attempt to

claim a DDU discount.

Chapter 2: Job-file blocks and parameters

Page 50

With Destination Entry If you plan to drop-ship your mail at several USPS facilities to earn greater

postage discounts, use the Range parameter to tell Presort which ZIP Code ranges are eligible for DDU discounts.

If the mailing is: And it is dropped

at:

Standard Mail regular carrier-route or

and

delivered from

ASF, S C F, or A D C

Periodicals

Standard Mail

a local post office Use USPS DDU Data (Y/N)= n carrier-route or Periodicals

If this entry point serves multiple ZIP Codes, but only some of the ZIP Codes are eligible for the DDU discount, copy the Range and PER/STD Range QFY for DDU parameters as many times as necessary (up to 50) to assign the DDU discount correctly.

Set parameters like this:

Use USPS DDU Data (Y/N) =

Range (lower ZIP-upper ZIP) = ZIP range served by local post office Range QFY for DDU (Y/N) = y

Range (lower ZIP-upper ZIP) = ZIP range served by local post office Range QFY for DDU (Y/N) =

Note:

BMC entry points do not qualify for DDU discounts.

Presort Job-File Reference

Page 51

Execution

This block is required! In the Execution block, you can turn each processing step on or off.

In most cases, you’ll need to set up other blocks in the job file that are related to the processing steps you set here. For example, if you want to generate, you must set the Create Presort Reports parameter to Yes here in the Execution block, and then set up at least one report block later in the job file—for example, the Report: Job Summary block.

If you set these parameters to No, you needn’t comment out the related blocks (by inserting an asterisk before the word BEGIN). For example, if you set the Create Presort Reports parameter to No, you needn’t comment out the report blocks; Presort will automatically ignore them.

Presort (Y/N)

We suggest that you select this parameter and, in the same pass, select the Create Presort Reports parameter to produce reports. Then stop and check the reports before running Presort a second time to create output files.

Once you’ve sorted the mailing(s) and checked the reports, you can turn off this parameter. Presort will base all subsequent processing on the work files that it created in the first pass.

+ Name Optimizer (Y/N)

This feature is currently available for Periodicals and Standard Mail jobs only.

If you own the Name Optimizer feature and want to activate it, select this parameter. Presort will look for a Name Optimizer Resource File and a Name Optimizer Control block later in the job file. See “Name Optimizer Control,” on page 66 for block and parameter descriptions.

When you activate this feature, Presort will take addresses from separate resource files provided by you and add them to carrier-route packages that fall a few pieces short of the minimum pieces-per-package requirement. Thus, Presort forms complete packages and the pieces qualify for the carrier-route rate, rather than fall to the next sort level.

For complete information on Name Optimizer, refer to appendix B, “Name Optimizer,” on page 181.

1C/STD Ltr Postage Optimization (Y/N)

Activate the postage optimization feature for your First Class and Standard Mail automation letter jobs. Presort attempts to reduce the net postage by shifting mail pieces between containers and schemes. It is a multi-step process that occurs automatically after the initial presort is done. Presort only does this if it results in a net reduction in postage.

Dropping pieces to a lower sort level may increase postage and delivery time on the dropped pieces, but overall delivery time should be improved and your postage is reduced.

Chapter 2: Job-file blocks and parameters

Page 52

+ USPS Optional Procedures (Y/N)

Activate USPS Optional Procedures, only if you have permission from the USPS to customize your mailing by changing the package and container limits. If you select this feature, Presort will look for a USPS Optional Procedures block in the job file.

Presort normally forms packages and containers based on USPS regulations as printed in the Domestic Mail Manual (DMM). However, for efficiency, some of our customers have USPS permission to customize their mailings.

Important: Customizing package and container limits will take the mailing

outside of DMM compliance. Business Objects cannot accept any responsibility for problems that might result.

+ Sequence Output by Mailflow (Y/N)

To change the order in which Presort normally generates output and reports, select this feature. Then choose a new mail-stream order at the Mailflow block.

For example, if you are drop-shipping, you could change the output order of the entry points to match the order in which you load your trucks.

Note: Before choosing Mailflow, see information in the Presort User’s

Guide on split output files. Split output could generate the same results with

less work.

Participate in USPS CONFIRM Prog (Y/N)

If you plan to participate in the USPS CONFIRM program with this mailing, select Yes.

By participating in the CONFIRM program, you can print PLANET barcodes on your mail pieces to:

 Track USPS processing performance.  Track the date of delivery (to determine whether in-home date goals are met).  Track the timing of incoming return envelopes.

You might benefit from knowing delivery dates and times if, for example, you can use the information to staff a call center based on when your mailing reaches customers.

Important: You must be registered and approved by the USPS to

participate in the CONFIRM program.

Be sure to also:

 Include the PW.Prt_PLANET and PW.PLANET fields in your input DEF file

(see the Quick Reference Guide for Views and Job-File Products for descriptions of these fields).

 Add the CONFIRM field to your output file and post ap.confirm there.

 Complete the EMD (Electronic Mailing Data) File report block. (See

“Report: EMD File,” on page 140.)

Presort Job-File Reference

Page 53

 Complete the USPS 8125 report block.

 Request that Presort create a Piece Detail Record file in the Report: IDEA

Mail.dat block. (See “Create IDEA SPR02/PDR05 (Y/N),” on page 147.)

PER Co-Pallet (BEFORE/AFTER/OFF)

This parameter is for use with the USPS experimental Periodicals co-palletization program. You must be approved by the USPS to participate in the program, and you must purchase the option in Presort before you can use it.

Type Before when you set up the first job in your Periodicals co-palletization setup. The first job produces the “before” (before co-palletization) information that the USPS requires to determine if the pieces are eligible for the discount.

Type After when you set up the second job in your Periodicals co-palletization setup. The second job places the pieces that would have been sacked onto pallets and then produces the information required for the co-palletization reports for the USPS.

Leave the default value of Off if you are setting up a job that isn’t a Periodicals co-palletization job.

Refer to the Presort User’s Guide for complete information about setting up for the Periodicals co-palletization program.

Create Presort Reports (Y/N)

Use this parameter to generate reports in this job run. Be sure to also set up the report blocks for the reports you need.

+ On-Demand Reporting (Y/N)

To print reports that reflect just a partial mailing, select this feature. Then define the partial mailing at the On-Demand Reporting block.

This feature is especially helpful when you can't submit a complete mailing in one day; for example, when you need to deliberately stagger a mailing or when mail-room equipment fails.

Create Address Output File (Y/N) Create Package Output File (Y/N) Create Container Output File (Y/N) Create Pallet Output File (Y/N)

You must create Presort output files. These files contain data needed by labeldesign and printing software to print labels for mail pieces and containers.

Here in the Execution block, select the type of output files that you need to create. Then complete the Create Output File and corresponding Output File posting blocks.

Chapter 2: Job-file blocks and parameters

Page 54

+ Post to Input File (Y/N)

If you want to take data that is generated by Presort and copy it back into your input file, select this feature. Then set up a Post to Input File block. Your input file must contain a field ready to receive the data that you post; Presort cannot append new fields to input records. If you need to append new fields for this job, you need to create an output file.

Important: After posting to any input file, Presort deletes all work files. So

be sure to generate all reports at the same time that you post to the input file. If you don’t, you’ll have to re-presort the job before you can generate reports.

Warn Before File Overwrite (Y/N)

When Presort tries to create a file, it may find that the file already exists. If you want Presort to stop and warn you before overwriting a file, set this parameter to Yes. If you plan to run this job unattended, then set it to No.

Even if you plan to run this job unattended, you may want to leave this parameter set to Yes and use the /a command-line option to answer any warnings. That way, you can use this parameter as a “safety net” so that warnings are always displayed unless you deliberately override them at the command line.

Show Detailed Process Messages (Y/N)

When you start Presort, you’ll see processing messages on your screen that show the status of your job.

To see all of Presort’s messages, select this option. If you don’t select this option, Presort displays only the main processing messages.

For example, if you show detailed messages, Presort informs you that a particular presort scheme and sort level are being processed. If you don’t choose to show detailed messages, Presort displays only the scheme that it's processing and doesn’t show the percentage completed. This feature has no effect on verification messages.

Save Work Files (Y/N)

This parameter should be selected almost all the time. You might deselect it when you are certain that your job is done—you have verified that your presort is correct, printed all the reports and output files.

You can save time and avoid deleting the wrong files by having Presort delete its own work files. To do this, turn off all of the Execution block parameters, including this one. Then run Presort one more time. Presort will delete its own work files, and nothing else. It’s up to you to delete any input, report, output, or label files that you may no longer need.

Presort Job-File Reference

Note: For even easier work-file cleanup, use the del command-line option.

Then you can set the Save Work Files parameter to Yes and never change it.

Important: After posting to any input file, Presort deletes all work files. See

the Post to Input File parameter in this block for more information.

Page 55

Work File Directory (path)

Presort needs a place to store its work files. Type the path and name of your Presort work subdirectory. Be sure that you have

System Work file location

Windows/NT \pw\pst\work

UNIX postware/presort/work

adequate disk space and permission to write files into this directory.

Set aside a separate subdirectory for Presort work files, and place No other files there. For example:

For extra safety, use a separate subdirectory for each active job to prevent any job from overwriting another job’s work files. If you leave this line blank, Presort will place the work files in the current directory.

Chapter 2: Job-file blocks and parameters

Page 56

General

This block is required The General block tells Presort some general information about your job and

what it can expect to see later in the job file.

Job Description (to 80 chars)

This parameter is optional. The description might be a project or client’s name, or other key facts about the job. Presort will print this information on the Job Summary.

In your description, you may use these shortcuts:

Type this: To get this:

$date Current date (dd-mmm-yyyy; for example, 22-jan-2000)

$time Time (hh:mm:ss?m; for example, 09:13:16am)

$job Job-file base name

Job Owner (to 20 chars)

This parameter is optional. The Owner should be you, the person who created the job file. Or it might be the name of your client's company, if you plan to give the client the Job Summary. That is where Presort will print this information.

Mail Class (FIRST/PER/STD/PSVC/COMAIL)

Select the class of mailing for this job; First Class, Periodicals, Standard Mail, Package Services, or Co-mail. Presort will verify that everything else in your job file is appropriate for the class that you select here.

Presort Job-File Reference

Page 57

General Output

This block enables you to control how output is numbered.

Pallet No. (ABS/REL MLG/REL SEG) Container No. Pkg No. Label No.

Presort assigns a number to every pallet, container, package, and piece in the job (except unqualified pieces). These numbers appear on some reports. If you want, you can print them on labels and container tags using these Presort output fields:

 AP.Plt_No_Rel

 AP.Ctn_No_Rel

 AP.Pkg_No_Rel

 AP.Pc_No_Rel

These parameters give you control over the way that containers, packages, and pieces are numbered. Here are your options:

Option Description

ABS Numbering begins at 1 and runs consecutively through the end of

the job.

Note:

Container numbers are serial, even when container type changes from one scheme to the next (for example, from a tray to a sack).

REL MLG Numbering begins over again at 1 within each mailing. Presort will

divide your job into several mailings if your job qualifies for more than one presort scheme, if you drop-ship, or if you segment.

REL PLT Container, package, or piece numbering starts over again at 1 as

each pallet is formed. Select this option if you are preparing packages or trays on pallets.

REL CTN Package or piece numbering starts over again at 1 as each container

is formed.

Note:

If you are preparing a Packages on Pallets scheme and select this option, Presort numbers packages and pieces relative to the pallet, since that is the "container."

REL PKG Numbering starts over again at 1 as each package is formed.

Note

: If you want Presort to begin numbering at a number other than

1, see the Starting Number parameters described on the next page.

REL SEG Numbering starts at 1 for each new segment encountered during

output processing.

Chapter 2: Job-file blocks and parameters

Page 58

Starting Pallet No Starting Container No Starting Package No

Some mailers want the flexibility to have the numbers in one job pick up where the numbers in the previous job ended. If you want pallet, container, or package numbering to start at a number other than 1, then use these parameters to tell Presort where to start numbering.

Here are two examples that show how setting your own starting number might affect your results. Let’s say that you have 300 pallets and you set Starting Pallet Number at 501.

Example #1: If you form one mailing, your pallet numbers run from 501 to 800.

Example #2: If you form two mailings of 150 pallets each:

• With absolute numbering (that is, you set Pallet No. = ABS), your pallet numbers run from 501 to 800.

+ Mfst Serial Numbering

• With numbering relative to the mailing (that is, you set Pallet No. =

MLG

), your pallet numbers run from 501 to 650 in the first mailing, and

REL

also from 501 to 650 in the second mailing.

Your settings appear in the General Output section of your Job Summary Report. Your settings will affect the information that is reflected in other reports as well.

These starting number options affect the following output fields:

 AP.Ctn_No_*  AP.Pkg_No_*  AP.Plt_No_*

If your job involves manifesting (that is, if the job involves pieces of different weights), this parameter controls the way that manifest pieces are numbered in the manifest keyline. Here are your options:

ABS: Absolute means that numbering begins at 1 and runs consecutively through the end of the job.

REL MLG:

Relative to Mailing means that numbering begins over again at 1

within each mailing. Presort will divide your job into several mailings if you use more than one presort scheme, if you drop-ship, or if you segment.

Note: The field AP.Manfst_Key is required if you’re mailing under the

Manifest Mailing System. This field holds the manifest keyline, including serial number, weight (1C only), rate category, and postage.

REL SEG: Relative to Segment means that numbering begins over again at 1 within each segment.

Presort Job-File Reference

Page 59

Mailing Sequence No. Prefix (9 chars) Mailing Sequence No. Start (4 digits)

Mailing sequence numbers are printed on reports to help you and the USPS identify and track mailings. You can print mailing sequence numbers on labels by using the Presort output field AP.Mailing_ID.

Mailing sequence numbers consist of a prefix determined by you (up to nine characters) and a four-digit number that Presort assigns automatically.

Prefix: At the Prefix parameter, type a prefix that will identify the job, such as your job number, job name, publication name, or client's name.

Start: At the Start parameter, set the starting number. Presort automatically starts numbering mailings at ØØØ1. Use this parameter only if you want to start at a different number. For example, if you set Start = 2222, then mailings will be numbered 2222, 2223, 2224, and so on.

Note: If you use Mailflow (see “Mailflow,” on page 61), it will affect the

output sequence and therefore will affect your mailing sequence numbers.

Chapter 2: Job-file blocks and parameters

Page 60

Input File

This block is required! You will need one copy of this block for each input file; that is, for each file that

contains input address data. If your job involves more than one input file, copy and repeat this entire block as many times as necessary, up to a maximum of 255 files.

Presort will number the files and list them on reports in the order that you list the Input File blocks in the job file (see the application field AP.File_No).

Input File Name (path & file name)

Type the path and name of the input address file. If you have more than one input file for this job, copy the entire block as many times as needed to define each input file.

Override Default Format (path & file name) Override Default DEF (path & file name)

Use these parameters to specify the format and definition file options that you want to use above all other settings. For example, let’s say that you typically use a template when creating your jobs, and you have the format and definition files already specified in the Auxiliary Files block. You can set these override parameters to use a different format or definition file without having to remove the default parameters in the Auxiliary Files block. See “Default ASCII FMT

(path & file.fmt)” on page 30 and “Default DEF (path & file.def)” on page 30.

+ Filter (to 512 chars)

Presort looks for the definition and format files in the following order:

 the Override options listed in the Input File block  the files with the same name in the same folder as the input file  the files listed in the Auxiliary Files block

Entering paths in the Input File block are optional. You do not need to set these options in order to process the job.

You can set criteria for each record to meet in order to be included in processing. For example, to limit a mailing to California residents, you might set up this filter:

+Filter (to 512 chars)...... = db.state = "CA"

Complete instructions for setting up a filter are provided in the Database Prep manual. Find the latest version in the most recent Documentation CD.

Presort Job-File Reference

Page 61

Mailflow

Split Output may be easier

Mailflow on segments

Mailflow is a way to change the order in which Presort normally produces output, reports, and labels.

Before you spend time on Mailflow, consider using the Split Output feature (see

page 21). You might find that Split Output serves your needs equally well, with

simpler setup and less processing time than Mailflow.

In particular, if your job involves two or more entry points, we recommend that you split by entry point, instead of putting all entry points together and using Mailflow to control sequence. You will probably find it easier to manage your output if you use Split Output, and Presort will run faster without Mailflow.

You can use Mailflow to change the output sequence of segments. However, it is more efficient to simply change the sequence of Segment Description blocks.

For more details on Mailflow, see the Presort User’s Guide. Find the most recent version on the latest Documentation CD.

Use Alt Mailstream Hierarchy Seq (Y/N) Use Alternate Entry Point Seq (Y/N) Use Alternate Segment Sequence (Y/N) Use Alternate Pst Scheme Seq (Y/N) Use Processing Center Sequence (Y/N) Use Pallet Sequence (Y/N) Use Container Sequence (Y/N) Use Package Sequence (Y/N)

These parameters are all named after other blocks. If you select any of them, Presort will search for a block of the same name. For example, if you want to change the order in which presort schemes are output, select the Alternate Presort Scheme Sequence parameter, and set up an Alternate Presort Scheme Sequence block.

All you are doing here is telling Presort to find a Sequence block; there, you choose what sequence you want.

Chapter 2: Job-file blocks and parameters

Page 62

Print Together by Bindery/Ver (Y/N)

This parameter is useful for those who want to prepare multiple-version mailings, but who do not own selective bindery or inserter systems, or who use a combination of selective and non-selective binderies.

If you use the Bindery Sets feature to mingle multiple versions (see the Presort User’s Guide) and you set this parameter to Yes, Presort will group pieces by bindery first.

If you do not use Bindery Sets, Presort groups pieces by version first. After that, pieces are grouped by entry points, segments, and presort schemes. You can then print a single version at a time.

Note: The Print Together by Bindery or Version parameter does not cause each version or bindery set to become a separate mailing. It simply changes the way pieces are output.

After printing, you’ll need some mechanical or manual system for merging versions back into correct mail-stream sequence.

Presort will output versions according to the sequence of Version Description blocks. If you need to alter that sequence, arrange the Version Description blocks and run Presort with Mailflow.

Print Non-Pst's with Segments (Y/N)

This parameter affects only segmented jobs.

If you do not select it, Presort gathers all qualified, non-presorted pieces at the end of the mail stream.

If you would prefer to retain those pieces within their respective segments, select this parameter.

Presort Job-File Reference

Page 63

Mailing Information

This block is required! At this block, provide information about the mailer and how postage is paid.

Postage Payment Method

Select the method by which you pay postage:

Payment method

Permit For permit imprint (indicia) mailings.

Correct Meter Select Correct Meter if you have a meter that can be adjusted elec-

Lowest Meter Job This option allows you to meter all pieces at the lowest rate in the

Lowest Meter Mailing

Multi Meter If you have more than one meter rate in this job, choose Multi

Description

tronically to apply the correct postage to every piece.

whole job.

This option meters all pieces at the lowest rate per mailing. On the front of your Postage Statement, Presort will print the

amount of your lump-sum payment in the “Additional Postage Payment” box. Reports and forms will show postage as if you had applied postage to each piece.

Meter. This payment method will be very useful to you if you combine mailings for more than one customer in a job and they meter at different rates.

To use multiple meter rates in a job, in addition to selecting Multi Meter at this parameter, you must have the field PW.Meter_Rate in your file. Be sure to enter the monetary value in PW.Meter_Rate field in cents; for example you would enter 29½ cents as 29.5, not .295.

Stamps Postage

Stamps If you apply precanceled stamps, type the denomination on the next

line. You will probably owe additional postage, and pay it by attaching a lump sum to your Postage Statement.

On the front of your Postage Statement, Presort will print the amount of your lump-sum payment in the “Additional Postage Payment” box. Reports and forms will show postage as if you had applied exact postage to each piece.

This parameter applies only when you have selected Stamps as your Postage Payment Method.

Enter the denomination of your precanceled stamps. Enter the amount in cents, not dollars. For example, enter thirty three cents as 33.0, not 0.33.

The minimum entry that Presort will accept is one cent (1.0).

Chapter 2: Job-file blocks and parameters

Page 64

PER Authorized as a Newspaper (Y/N)

Select Yes if your publication is issued weekly or more frequently. Also select Yes if your publication was authorized for newspaper treatment prior to March 1,

1984.

Presort will add the word “NEWS” to the content line on your container tags.

Mail Owner Name (to 35 chars) Mail Owner Address Line 1 (35 chars) Mail Owner Address Line 2 (35 chars) Mail Owner Address Line 3 (35 chars) Mail Owner DUNS No. (9 chars)

If the mail owner is the permit holder, and you have completed all of these fields for the permit holder, you can leave these parameters blank. If the mail owner is not the permit holder type the mailer’s name, address, and DUNS Number on these lines.

DUNS Number: Presort will use the Mail Owner DUNS number first. If that field is blank, it uses the Permit Holder DUNS number, and if both of those fields are blank, Presort uses the Mailing Agent DUNS number. If all three fields are blank, Presort issues an error.

Mailing Agent Name (to 35 chars) Mailing Agent Contact (to 35 chars) Mailing Agent Address Line 1 (35 chrs) Mailing Agent Address Line 2 (35 chrs) Mailing Agent Address Line 3 (35 chrs) Mailing Agent Telephone No. (15 chars) Mailing Agent DUNS No. (9 chars)

The mailing agent is the organization that prepares the mailing. If the mailing agent is also the permit holder, and you have completed all of the information for the permit holder, you may leave these lines blank. If the mailing agent is not the same company as the permit holder, use these lines to type the mailing agent's name, the name of a contact within the organization, address, telephone number, and DUNS Number.

Statement Signer Name (to 35 chars)

Type the name of the person signing the Postage Statement.

Signer Telephone Number (to 15 chars)

Type the telephone number (including area code) of the organization that prepares and signs the Postage Statement. You may use any format.

Presort Job-File Reference

Page 65

Receipt No. (to 15 chars)

Type the receipt number if needed. This refers to a receipt you've received for a deposit into your Advanced Deposit Account (Trust Account).

Mailing Date (to 15 chars)

Type the date that the mailing will be submitted. Use any format.

If you aren’t certain of the date, leave the parameter blank. Presort will leave blank the Mailing Date line on your USPS forms so you can write in the date by hand.

You may use the shortcut $date. Presort will print the current date (according to the clock in your computer) in the format dd-mmm-yyyy.

Auto Matching/Coding Date (MMDDYYYY)

Type the date that your list was last processed for ZIP+4 matching. If you have more than one list with different dates, enter the oldest date.

CART Matching/Coding Date (MMDDYYYY)

Type the date that your list was last processed for carrier route matching. If you have more than one list with different dates, enter the oldest date.

CART Sequencing Date (MMDDYYYY)

Type the date on which the list was last updated for carrier route sequencing.

LOT Database Date (MMDDYYYY)

Type the date of the LOT database that was used to arrange the input file(s) in LOT order. This information will populate the LOT Database Date field in the SEG Mail.dat files.

Important: Presort does not check to make sure the date is valid. However,

PostalOne requires a valid date.

Note: This parameter is only used for Mail.dat output. Presort users not generating Mail.dats will not use this parameter.

Chapter 2: Job-file blocks and parameters

Page 66

Name Optimizer Control

The Name Optimizer Control block enables you to control how additional pieces are added to your carrier-route packages when you use the Name Optimizer feature.

Maximum Number of Names to Add to Job

If there’s a limit to the number of names that you want to add to the entire job, type that number here. If not, leave this parameter blank; Presort will then add as many names as it takes to optimize your carrier-route presort.

Note: This parameter doesn’t set the total number of mail pieces. It deals

only with the number of names added by Name Optimizer.

Overall Max Adds per Pkg (1-9/ALL)

Set an absolute limit on the number of pieces that you want added to any package. Normally, you should set this parameter at 1 or 2. Experienced users say that adding one piece saves postage; by adding two pieces, you may break even. If you set this parameter to All, Presort can form complete packages entirely from names in your resource files.

Use Segment_ID in Resource Files(Y/N)

Use the segment ID in your Name Optimizer resource files as criteria for selecting records used to complete carrier route packages.

Presort pulls extra records to complete a carrier route, but it pulls only records from carrier routes that have the same segment ID. See “Use Segment_ID in Resource Files parameter,” on page 190 for more information.

Dupe If Add Name Not Found (Y/N)

Turn on this parameter if you want Presort to duplicate a record that is already in the package if it cannot find a suitable record in any of the resource files. The duping feature is a last resort. Since it means that an active customer will get two pieces, it isn’t ideal, but it still may save postage.

Regardless of any other settings, this parameter affects only those packages that are one name short of qualifying. If you have any packages that are two pieces short, duping will not complete them. Also, Presort selects the record to be duped at random.

Version Name for Duped Records

This parameter applies only if you have turned on the Dupe if Add Name Not Found parameter.

When Presort adds a piece by duping, you type the version name from one of your Version Description blocks to determine which version should be used for that second piece.

Presort Job-File Reference

Page 67

Minimum Pieces Per Car-Rt Package

Normally, you should leave this parameter blank. Presort will apply the usual carrier-route package minimum (6 pieces for Periodicals, 10 for Standard Mail).

Priority Field (OFF/ASCEND/DESCEND)

When Presort needs one record to complete a package, it may find that it can pick from two or more suitable possibilities. You can control this choice by prioritizing records, based on some database field.

Remember that this is all about optimizing carrier-route packages. So when we say that Presort is searching for a “suitable” record, we mean that it is looking for a record with a certain ZIP and carrier-route number (and LOT information, if the mailing is Standard Mail Enhanced Carrier Route).

Suppose your Expire file contains a date-of-expiration or date-of-last-order field. Given the choice of two records, you might prefer to mail to the subscriber who ordered or lapsed more recently. To set this up, there are two things you must do:

In your DEF file, you would set up this database field as the PW field Priority. For example, your DEF file might include this line:

PW.Priority = EXPIR_DATE

PW.Priority = LAST_ORDER

If you like, you may use any other database field that you think makes a reasonable basis for choosing one record over another. For example, you could choose an Income database field.

Next, set this parameter to Ascend or Descend.

Ascending sequence is 0–9, A–Z, a–z. Descending sequence is z–a, Z–A, 9–0. If you’re prioritizing by a date-type field, Ascend gives priority to the earliest date, and Descend gives priority to the latest date.

If you are not using the Priority field, set this parameter to Off.

Chapter 2: Job-file blocks and parameters

Page 68

Name Optimizer Resource File

The Name Optimizer feature can be used in Periodicals and Standard Mail jobs only. Refer to “Name Optimizer,” on page 181 for information about Name Optimizer.

At this block, provide information about a single resource file.

Resource File Name (path & file name)

Type the name of the resource file. If it is located in another directory, type a path as well.

Note: You must create a definition (DEF) file for each resource file. You also may need a format (FMT or DMT) file. For details, see the Database Prep manual.

Filter (to 512 chars)

If you want, you may screen resource records using a filter. For details, see the Presort User’s Guide.

Here’s an example: Some mailers use a “counter” field in the records of their Expire file (i.e., file of inactive customers). Each time that a lapsed customer receives a free copy, this counter is increased by one. When it reaches some limit, the customer is deemed unresponsive. Usually, unresponsive records are removed from the Expire file, but instead, you might use a filter to screen out any records with a counter that is at or over your limit.

Resource File Type (EXPIRE/ADD)

What type of file is the resource file?

Expire: An Expire file is usually a list of inactive customers.

Add: An Add file is usually an outside, rented list of prospects.

File Priority (1 to 99, 1 highest)

If you have only one Expire file and/or one Add file, set this parameter to 1.

If you have two or more Expire or Add files, you can prioritize them. In effect, you are setting the order in which Presort will search the files. Priority numbers run from 1 to 99; 1 is highest, 99 is lowest. If you want two or more files to have the same priority, give them the same number.

Note: Expire and Add files are separate “tiers.” You can prioritize resource

files within each tier. Presort always searches all Expire files before searching any Add files.

Max Names to Add per Package(1-9/ALL)

You may set a limit on the number of pieces that you want added to any package from this resource file. Normally, you should set this parameter to 1 or 2 to ensure that you realize the cost-efficiency of this feature.

Presort Job-File Reference

Page 69

Total Max Names to Add from This File

Normally you’ll leave this parameter blank. If you want though, you may limit the total number of records Presort takes from this resource file. If Presort reaches this limit, it will stop taking records from this file. Instead, Presort will rely on other resource files or the Duping feature (if you use it).

Chapter 2: Job-file blocks and parameters

Page 70

On-Demand Reporting

With the On-Demand Reporting feature, you can generate reports that reflect just a portion of your mailing. This is handy if some mail-room equipment fails in the middle of a job or if you can’t finish preparing a large job in one day as you had planned.

The Job Summary always reflects the entire job; it is never affected by OnDemand Reporting.

Reports that you prepare with On-Demand Reporting will be specially marked. In the report header lines, Presort prints [ODR]. If you call our Help Desk with questions about reports, our advisors might ask you if the mark is printed on your reports. They will be able to help you better if they know whether or not the reports were printed using On-Demand Reporting.

Report files If you use On-Demand Reporting, you must plan carefully to avoid overwriting

one day’s reports with the next day’s reports—especially if you use the $job macro in report file names. Here are three options:

 In your Report blocks, set Existing File = Replace. Be sure to print all reports

each day. When you run reports again tomorrow, they will overwrite today’s reports.

 Or write each report to a separate file and don’t use $job. In your Report

blocks, change the report File Name each day.

 Or in your Report blocks, set Existing File = Append. Then one file will

contain all of your USPS 3602 forms, for example.

Important: When you use On-Demand Reporting, Presort does not

recalculate your postage, recheck your eligibility, or re label your containers. Reports will reflect the postage for just the range of pieces that you selected, but Presort will not determine whether that portion qualifies on its own merits.

If you set a break point in the middle of a mailing, the resulting partial mailings might not be prepared or documented in strict accordance with USPS regulations.

Business Objects cannot accept responsibility for any mail-acceptance dispute that might arise from a split mailing.

Important: When you use on-demand reporting in a job that involves

combining and merging automation and regular flats (and carrier-route flats, when applicable), it is very important that you check the resulting USPS Postage Statements to ensure that each rate level (carrier-route, automation, and regular) all meet the minimum mail-piece requirements.

Presort Job-File Reference

Page 71

Report Break Level (PLT/CTN/PKG/PIECE) Print Ranges (START-END)

When you use on-demand reporting, you must give Presort a range of pallet, container, package, or piece numbers on which to base the reports.

At the Report Break Level parameter, select the basis on which you want Presort to break. At the Print Ranges parameter, type a starting value followed by a hyphen and an ending value.

These are absolute numbers—they start at 1 at the beginning of the job stream and keep going up through the end of the job. Here are some tips:

 In most cases, we recommend that you use pallet or container numbers, to

keep whole pallets or containers intact.

 You might set a range of piece numbers if you simply run out of pieces or if

the stitcher breaks down in the middle of a pallet. Then you would need to print USPS reports based on the actual pieces mailed.

 If you’re drop-shipping, try to ensure that the break at the end of a day

coincides with entry points or truckloads.

BEGIN On-Demand Reporting ===================================== Report Break Level (PLT/CTN/PKG/PIECE)= PLT

Print Ranges (START-END...).......... = 1-7

END

Chapter 2: Job-file blocks and parameters

Page 72

Output Entry Point Selection

Entry Point Name -- for Selection

Copy and repeat the Name for Selection parameter as many times as necessary. You need one copy of the parameter for every entry point that you want to output. Names must be spelled exactly right, using the same case that you used to type the name at the Entry Point Description block.

To save time and avoid mistakes, do not type names over again. Instead, go back to the Entry Point Description block, copy the Entry Point Name, and paste it here. Copy only the entry to the right of the equal sign—not the whole parameter line.

BEGIN Entry Point Description =================================

Entry Point Name (to 31 chars)....... = SCF San Diego CA

+ Value in PostWare Field Entry_ID... = Entry Point Post Office City (20 chrs)= Entry Point Post Office State (2 chrs)= Entry Point Post Office ZIP Code (10) =

Entry Point Type (see NOTE).......... = other

Scheme Nums this Entry Pt (see NOTE). = ALL

STD/PSVC QFY for DBMC Rate (Y/N)..... = n

PER QFY for DADC Rate (Y/N).......... = n

PER/STD/PSVC QFY for DSCF Rate (Y/N). = n PER/STD/PSVC QFY for DDU Rate (Y/N).. = n PER/STD/PSVC Use USPS DDU Data(Y/N).. = y Origin Post Office City (to 20 chars) = Origin Post Office State (to 2 chars) = Origin Post Office ZIP Code (10 chars)= Create Undrfill Local 3DG/SCF Ctns Y/N= y Create Small Service Area Plt (Y/N).. = y Min SCF/ASF Local 3DG Pallet Weight.. = Min SCF/ASF Local SCF Pallet Weight.. = Min SCF/ASF Loc 3DG Plt Tray Ft(1-144)= Min SCF/ASF Loc SCF Plt Tray Ft(1-144)=

Min Pieces (see NOTE)................ =

Min Pounds (see NOTE)................ =

PER IC Disc Eligibility(ALL/SUB/NONE) = NONE

PER County of Publication............ =

CONF Estimated Date Dropped (MMDDYYYY)= CONF Estimated Time Dropped (HHMM)... =

Appointment Number (12 chars)........ =

Del Window Start Date (MMDDYYYY)..... =

Del Window End Date (MMDDYYYY)....... =

Range (lower ZIP-upper ZIP).......... = 00000-99999

PER/STD/PSVC Range QFY for DDU (Y/N). = n END

...

BEGIN Output Entry Point Selection =================

Entry Point Name -- for Selection.... = SCF San Diego CA

END

Presort Job-File Reference

Page 73

Output Order

Reports (1-5) Address Output File(1-5) Package Output File (1-5) Container Output File(1-5) Pallet Output File (1-5)

You may use this block to change the normal output order of the elements of your job.

If you plan to generate output files that you will use as input to label-design and printing software, such as Label Studio, you can change the order in which those files are output. Normally, Presort produces them and your reports in the order that they are listed in this block (reports first, pallet output file last).

But you might want to change this order. For example, suppose that you’ll be creating an address output file and reports. You plan to hand off the address output file to another person or company, who will use it to print mail-merge letters. Printing mail-merge letters can take a long time, so you need to get that process going as soon as possible. You might want to generate the Address Output File first.

To change the output order, change the order of the values at the five parameters in this block. Use only numbers 1 through 5.

BEGIN Output Order ============================================

Reports (1-5)........................ = 5

Address Output File(1-5)............. = 1

Package Output File(1-5)............. = 2

Container Output File(1-5)........... = 3

Pallet Output File (1-5)............. = 4

END

Chapter 2: Job-file blocks and parameters

Page 74

Output Presort Scheme Selection

Presort Scheme Name -- for Selection

Copy and repeat the Name for Selection parameter as many times as necessary. You need one parameter for every scheme that you want to output. Names must be spelled exactly right, using the same case shown in the scheme block title (for example, 1C/STD, Regular Letters).

So, to save time and avoid mistakes, do not type names over again. Instead, go back to the Presort Scheme block, copy the block title, and paste it here. Copy only the scheme name (for example, 1C, Automation Letters).

BEGIN Presort Scheme: STD, Enhanced Carrier Route Regular Letters ========

BEGIN Output Presort Scheme Selection ========================= Presort Scheme Name--for Selection = STD, Enhanced Carrier Route Regular Letters END

Multiple occurrence of same block

Some schemes might occur more than once in a single job file. If you want to use Output Selection to output schemes, you must type the scheme name and follow it with a number that indicates the original order of the blocks in the job file.

For example, suppose we have two STD, Flats schemes in our job file. One is set up as a carrier-route scheme; the second one is set up as an automation and regular scheme.

Suppose that we want to output just the carrier-route pieces in this run. We would set up the Output Presort Scheme Selection block like this:

BEGIN Output Presort Scheme Selection ======================= Presort Scheme Name – for Selection.. = STD, Flats 1 END

Presort Job-File Reference

Page 75

Output Segment Selection

Segment Name -- for Selection

Copy and repeat the Segment Name for Selection parameter as many times as necessary. You need one copy of the parameter for every segment that you want to output. Names must be spelled exactly right, using the same case that you used to type the name at the Segment Description block.

To save time and avoid mistakes, do not type names over again. Instead, go back to the Segment Description block, copy the Segment Name, and paste it here (that is, unless you are using Auto Segmenting).

BEGIN Segment Description =====================================

Segment Name (to 31 chars)........... = Eastern Edition

Value in PostWare Field Segment_ID... = E END

...

BEGIN Output Segment Selection ================================

Segment Name -- for Selection........ = Eastern Edition

END

Note: If you use Auto Segmenting, you can still use Output Selection. Be

sure to set up a unique Output Segment Selection block for each segment. Use the value in the Segment_ID field as the Segment Name in both the Segment Description block and the Output Segment Selection block.

Chapter 2: Job-file blocks and parameters

Page 76

Output Selection

Normally, Presort produces output for the entire job. That is, it produces output data for every entry point, every presort scheme, and all pieces.

You can use the Output Selection blocks to limit the output to just certain entry points, for example. If you know that the job is too large to prepare in the mail room in one day, you might output just those entry points that you plan to truck to today.

Tip: Another way to create subsets of the entire job is to use the Split Output feature (see page 21).

+ Select Entry Points To Output (Y/N) + Select Segments To Output (Y/N) Select Pst Schemes To Output (Y/N)

These parameters correspond to the following blocks—Output Entry Point Selection, Output Segment Selection, and Output Presort Scheme Selection.

If you type Yes for any of these parameters, Presort searches for the corresponding Selection block where you will list the entry points, for example, those that you want to output in this run.

Select Presorted Pieces (Y/N) Select Qualified Non-pst Pieces (Y/N) Select Unqualified Pieces (Y/N) PER Select Foreign Pieces (Y/N)

If you want, you can use these parameters to suppress or separate qualified nonpresort, unqualified, and/or foreign pieces from the mailing.

For example, if you’re mailing an advertisement using a Standard Mail job, you might save yourself some return charges by dropping unqualified pieces from the job. (Unqualified pieces have bad ZIP Codes, so there’s a chance they won’t be delivered anyway.) In this example, select presorted and qualified non-presorted pieces, but not unqualified.

Presort Job-File Reference

Page 77

Package Output File

Use this block when you want to create package labels or facing slips with labeldesign and printing software, such as Label Studio. Presort will create one output record per package.

Caution, avoid file overwrite! For best protection, set up a separate output

subdirectory for each active job, and place no other files there.

If you use the File Protection feature, Presort warns you if your first split output file is about to overwrite another file. The program does not check for overwrite on subsequent files.

Setup is important It is important that you take care in setting up your output files so that software

such as Label Studio can read and use all of the data. To help you fill out this block, look at the Container Output File blocks in the following template files that we include with your Presort software. One file is set up with examples of tray mailings, (lstry.pst); the other with examples of sack mailings (lssck.pst). The Container Output File blocks are similar in setup to this block and can be useful examples.

Supporting files When you make any output file, Presort automatically produces some supporting

files, such as an FMT file, to go with it. Some supporting files, such as a DEF file, are made at your discretion (see the Create DEF File parameter in the Create File for Output block). (If you’re not sure what we mean by FMT and DEF files, read our Database Prep manual.) In either case, the supporting file name uses the same base file name as the output file (for example, clancy.dat and clancy.def).

However, when you use Split Output, Presort gives these files fixed names (see table below), and they apply to all of the split output files.

DEF FMT DMT

Package output files

pst_pkgx.def pst_pkgx.fmt pst_pkgx.dmt

See the Address Output File block on page 20 for parameter descriptions.

Chapter 2: Job-file blocks and parameters

Page 78

Package Sequence

PER/PSVC Dest Zone PER/STD Dest Rate Sort Level Destination ZIP

Package Sequence gives you some control over the order in which Presort produces packages within each container. It affects reports (for example, the Mail Sort Listing), address labels, and address and package output files. It may be useful for tray and pallet mailings, but it makes little sense to adjust package sequence in a sacked mailing.

Packages are output by sortation level, then by ZIP Code. Zone and destinationentry rates do not directly affect package sequence.

To use this block, you must also turn on the Sequence Output by Mailflow parameter in the Execution block and the Use Package Sequence parameter in the Mailflow block.

If you want to change the normal package sequence use these parameters to change it. There are up to four ways to sort packages. Indicate the priority that Presort should use when reordering by assigning a unique number to each parameter that you want to activate (using 1, 2, 3, and 4). If you do not want to and are not required to sequence your packages in a particular way, then set that parameter to Inactive. This will reduce processing time by reducing Presort’s workload.

You cannot use Package Sequence to control which pieces are included in packages, or which packages are included in a mailing.

Also, you can choose the priority or precedence of sorting, but not the direction. The direction of sorting is always as follows:

Sequence options Containers Packages

Zone In-County, SCF, Local, 1, 2, 3, 4, 5, 6, 7, 8

Rate DDU, DSCF, DBMC, none None, DBMC, DSCF, DDU

Sort Level Carrier-Route direct to mixed AADCs

ZIP 00000 to 99999

Presort Job-File Reference

Page 79

Pallet Output File

Use this block if you want to create pallet placards with label-design and printing software, such as Label Studio.

Caution, avoid file overwrite! For best protection, set up a separate output

subdirectory for each active job, and place no other files there.

If you use the File Protection feature, Presort warns you if your first split output file is about to overwrite another file. The program does not check for overwrite on subsequent files.

Setup is important It is important that you take care in setting up your output files so that software

such as Label Studio can read and use all of the data. To help you fill out this block, we have included a template file with your Presort software. You can find the file in the template jobs; look for lsplt.pst.

Supporting files When you make any output file, Presort automatically produces some supporting

However, when you use Split Output, Presort gives these files fixed names (see table below), and they apply to all of the split output files.

Pallet output files pst_pltx.def pst_pltx.fmt pst_pltx.dmt

See the Address Output File block on page 20 for parameter descriptions.

DEF FMT DMT

Chapter 2: Job-file blocks and parameters

Page 80

Pallet Sequence

Pallet Sequence gives you some control over the order in which Presort produces pallets within each mailing. It affects reports (for example, the Mail Sort Listing), and address, container, and pallet output files.

The normal pallet sequence makes sense for most users and jobs. Pallets are output by sortation level, then by ZIP Code. Zone and destination-entry rates do not directly affect pallet sequence.

To use this block, you must also turn on the Sequence Output by Mailflow parameter in the Execution block and the Use Pallet Sequence parameter in the Mailflow block.

Container Weight Ascending Container Weight Descending

If you’re preparing Standard Mail trays on pallets, the USPS requires that the heaviest trays (the two-foot trays) be placed on the bottom of the pallet to avoid crushing the lighter trays (the one-foot trays).

You may activate one or the other of these parameters, but not both. That is, you may set one of these parameters to the value 1, 2, 3, 4, 5, or 6 and the other to Inactive.

To output the heaviest tray on the pallet first, set the Descending parameter. If you print your output in reverse order, then choose Ascending. The Mail Sort Listing will reflect the new output order, but because of USPS regulations, the Presort Qualification Report will not.

Note: When Presort sorts trays according to weight, it does so using whole pounds. Thus, it groups all the 15-pound trays, then all 14-pound trays, etc. Presort doesn’t sort to fractions of a pound. For example, Presort doesn’t make a distinction between a 14.2-pound tray and a 14.7pound tray. So a slightly heavier tray could be output after a slightly lighter tray, but since these trays will likely be placed on the same pallet tier anyway, there shouldn’t be a problem.

Presort Job-File Reference

Page 81

PER/PSVC Dest Zone PER/STD Dest Rate Sort Level Destination ZIP

If the normal pallet sequence doesn’t suit you, use these options to change it. There are up to five ways to sort pallets. Indicate the priority that Presort should use when reordering by assigning a unique number to each parameter that you want to activate (using 1, 2, 3, 4, 5, and 6). If you do not want to and are not required to sequence your pallet in a particular way, then set that parameter to Inactive. This will reduce processing time by reducing Presort’s workload.

You cannot use Pallet Sequence to control which packages or pieces are included on pallets or which pallets are included in a mailing.

Also, you can choose the priority or precedence of sorting, but not the direction. The direction of sorting is always as follows:

Sequence option Containers Packages

Zone In-county, SCF, Local, 1, 2, 3, 4, 5, 6, 7, 8

Rate DDU, DSCF, DBMC, none None, DBMC, DSCF, DDU

Sort Level Carrier-route direct to mixed-AADC

ZIP 00000 to 99999

Chapter 2: Job-file blocks and parameters

Page 82

PER Ride-Along Enclosure Description

A Ride-Along enclosure is a piece of mail that is inserted into or attached to a Periodicals piece. Previously, ride-along enclosures would mail at Standard Mail rates. Now, ride-along enclosures are charged a special per piece rate that is lower than the Standard Mail rate is.

See DMM 707.15 for complete rules and instructions for mailing Periodicals with ride-along enclosures.

Ride-Along Enc Name (to 31 chars)

Type a descriptive, unique name for the ride-along enclosure you are defining.

Ride-Along Enclosure ID

Type a ride-along enclosure ID for the ride-along you are defining.

A different ID is required for each PER Ride-Along Enclosure Description block that you complete. The ID you type here also needs to be entered in the PER Ride-Along Enclosure ID parameter in the Version Description block. Or, enter the ride-along enclosure ID in the Version Defaults block if the ride-along will go along with several different versions.

Sample Number of RAE Pieces(1 to 1000)

Type the number of pieces you are using for your sample.

This entry is required if you have entered a ride-along enclosure ID.

RAE Sample Thk (0.001 to 1000 inches)

Type the thickness of the ride-along enclosure sample.

The RAE height and width can exceed the host piece as long as the host piece and RAE are completely enclosed in a wrapper such as a polybag or envelope. Because you don’t enter height and width information in the Job, you are responsible for ensuring that your RAE conforms with USPS rules (DMM 707.15).

Mainly, you must remember that the size of your enclosure cannot change the processing category of the host piece. For example, you can’t enclose a flat piece with a letter because Presort will process the piece as a letter, and the enclosure makes it a flat

RAE Sample Wt (0.001 to 3300 ounces)

Type the weight of the ride-along enclosure sample.

The weight of the individual ride-along enclosure must be less than 3.30 ounces, and it must weigh less than the host Periodicals piece as stated in USPS rules.

Presort Job-File Reference

Page 83

Post to Input File

Input posting means copying information from Presort back into the input file. Your input file must contain a field ready to receive the data that you post; Presort cannot append new fields to input records. If you need to append new fields, you need to create an output file instead.

To set up input posting, set up one Post to Input File block for each file to which you plan to post data.

Important: After posting to any input file, Presort deletes all work files. If

you want to generate reports or output files, be sure to set them up before you run input posting.

Input File Name (path & file name)

Type the name that identifies the input file to which you are posting. If that file is not in the current directory, add a full or relative path name.

Copy (source, destination)

Use the Copy parameter to place data into one field of your input file. You may repeat this parameter as many times as necessary. First, type the information that you want to post, then a comma, then the name of the field in the input file.

You may post application (AP) fields, PostWare (PW) fields, database (DB) fields, or constants. You may use filter functions to modify data before posting it.

Important: Remember to think about field lengths! If the information that

you post is longer than the destination field, it will be truncated to fit. Also, be sure to spell field names correctly.

Chapter 2: Job-file blocks and parameters

Page 84

Presort scheme parameters

Many of the Presort scheme blocks have parameters in common. Therefore, we’ve listed all parameters available in all of the scheme blocks together in this section. The parameters are listed in alphabetical order.

If you’re not sure which presort schemes to use in your job, refer to “Template job files for nonpalletized jobs,” on page 13 and “Template job files for pallet jobs,” on page 14. Then use the recommended template job file as your starting point.

+ Create FRM Packages (Y/N) + Min FRM Package (2 to 100)

Firm packaging is a way to reduce postage by bundling nonautomated Periodicals pieces that are destined for the same delivery stop (for example, company or school). You may form firm packages at all of these levels: 5-digit, 3-digit, SCF, ADC, and mixed ADC.

Set the Create FRM Packages parameter to Yes to turn on the optional firm level, and use Min FRM Package to set the minimum number of pieces needed to form a firm package. You can minimize postage by setting it at 2, but you might have a lot of small packages to handle. Also note: Your stacker may not have adequate time to reset if you set this lower than 6.

For complete details on firm packaging, see the Presort User’s Guide.

1C Max Tray Height (inches)

See the Max Tray Height parameter description on page 99.

1C Min Tray Height (in. to hand holds)

See the Min Tray Height parameter description on page 108.

1C Number of Stacks in Tray (1.0 to 4.0)

See the Number of Stacks in Tray parameter description on page 110.

Presort Job-File Reference

Page 85

BMC Pallet Protection (Y/N)

In some instances, making mandatory ASF pallets prevents the creation of BMC pallets. With BMC pallet protection, pieces can be taken from the ASF pallet to form a complete BMC pallet. Before BMC pallet protection, pieces that didn't qualify for the BMC pallet would have fallen to sacks. These pieces can now go on a BMC pallet along with the pieces from the ASF pallet.

Important: The pieces taken from the ASF pallet are not eligible for any

DBMC discount. In some cases, better delivery consistency and labor conservation (it takes less work to make pallets than to make sacks) may outweigh the loss of any discount on the borrowed pieces.

Important: BMC Pallet Protection will only work if the ASF and BMC ZIP

ranges are included in a single entry point.

BPM Prepare Barcoded Flats (Y/N)

If your BPM job is eligible for the barcode discount, enter Y.

BPM single pieces may be eligible to receive the barcode discount. The barcode discount applies when the pieces meet the requirements for barcoded mail. For example, the pieces have the appropriate ZIP+4 or a valid barcode. There also must be 50 or more single pieces (parcels or flats).

Barcode machinable parcels automatically receive the barcode discount if there are 50 or more single pieces.

Co-Package Auto and Reg Pieces (Y/N)

You can combine automated and regular (non-automated) rate flats together in packages by setting this parameter to Y. In most cases, your postage is reduced using this preparation. It also saves the post office time and labor, and speeds up delivery.

Setting up co-packages There are three different ways to set up co-packaging. The method you choose is

based on the mail class that you are processing. For Package Services BPM, see the Co-Package Barcoded and Reg Pcs parameter description.

For Periodicals and Standard Mail flats, type Y for the Co-Package Auto and Reg Pieces parameter, type Y for the Prepare Automation Rate parameter, and type Y for the Prepare Regular Rate options.

For First Class flats, type Y for the co-Package Auto and Reg Pieces parameter and type Combined at the Preparation Type parameter. The First Class Flats block does not have the Prepare Automated and prepare Regular Rate parameters.

Chapter 2: Job-file blocks and parameters

Page 86

Co-Package Barcoded and Reg Pcs (Y/N)

For Package Services BPM regular and presorted flats and packages on pallets, type Y for the Co-Package parameter, type Y for the Prepare Regular Rate Packages parameter, and type Y for the Prepare Barcoded Flats parameter.

One package per

Co-packaging is limited to one package per destination.

destination

Example If you have 50 automated pieces and 30 regular (non-automated) pieces going to

the same destination, and you set your maximum pieces per package to 20, (and you have selected the co-package option), Presort makes four packages with 20 pieces each. Here’s how the packages are made.

Package 1

Automated

Package 2

Automated

Package 3

Co-package

automated and regular (nonautomated)

20 pieces

Package 4

Regular (nonautomated)

20 pieces

Notice in the example that the co-package is made before the regular (nonautomated) package is made. The co-package will always fall towards the middle of the sortation unless there are not enough regular (non-automated) pieces to make a package. Then it will be formed last.

Co-Packaging rates For co-packaged automated and regular pieces, rates are based on the following:

For packages in sacks and trays:

 Automated piece rates are based on the package level.

 Regular (non-automated) piece rates are based on the container level.

For packages on pallets: The rate is based on the package level.

For automated pieces in Periodicals packages with less than six pieces: The rate is the Automated basic rate.

Co-Package indicator on Mail Sort Listing

A co-package indicator appears on the extended and package format of the Mail Sort Listing. The indicator helps you determine what packages contain copackaged pieces. We use the “at” symbol ( @ ) to indicate that the pieces are copackaged.

Presort Job-File Reference

Page 87

Create 5-digit scheme (L007) packages

You can create 5-digit scheme (L007) co-packages in the two BPM schemes that have the option to co-package. When you select both the co-package and the create 5-digit scheme (L007) packages options, Presort makes 5-digit scheme copackages that contain presorted and regular rate pieces. Previously Presort would only create 5-digit scheme automated packages and sacks.

When both Co-Package and Create 5DG Scheme options are selected (set to Y), Presort places the packages in containers and pallets this way:

Scheme Packages Containers

Container Type (See Note)

BPM Flats Presort creates 5-digit scheme

co-packages.

The co-packages go in 5-digit scheme and merged 5-digit scheme containers.

BPM Packages on Pallets

Presort creates 5-digit scheme co-packages

The co-packages go on 5-digit, 3-digit, and SCF pallets when applicable.

Select the container type for this job.

 #1 Sack

 #2 Sack

 #3 Sack

 Flat tray

 1-foot tray

 2-foot tray

 1- and 2-foot tray

 2-foot EMM tray

For CMM mailing, when using letter 1- and 2-foot trays, Presort makes as few trays as possible, as described in DMM 245.03.03.e.

Create 3DG Carrier Route Trays (Y/N)

Three-digit carrier-route trays are an optional level, and we give you the choice to form these trays or not. Most of you will usually want to leave the Create 3DG Carrier Route Trays parameter set to Yes, to form these trays. Doing so generally saves substantially on postage.

However, some users may want to speed up delivery and production time, thereby increasing postage. In addtion, if you don’t use this parameter you will reduce the number of trays and no banding is required. Here’s how it works: If you set the Create 3DG Carrier Route Trays option to No, the pieces that would have gone into those trays drop to a lower sortation level, which mails at a higher rate. So your postage is almost guaranteed to increase if you set this parameter to No (unless you also set the Min Carrier 5DG Tray level to 10 pieces; almost no pieces would fall below the 5DG CART level and postage would not increase, but your labor costs would).

We’ve added this parameter to all letter schemes in which the USPS allows 3digit carrier-route trays.

Chapter 2: Job-file blocks and parameters

Page 88

Create 3DG Pallets (Y/N)

Three-digit pallets are optional in the schemes in which this parameter appears. Creating 3-digit pallets could speed delivery and could improve the results of SCF Pallet Protection (see the Presort User’s Guide).

Create 3DG Scheme (L008) Packages (Y/N)

Enter Y to create 3-digit scheme packages (bundles) for AFSM 100-compatible Periodicals, Standard Mail, and Package Services BPM flats.

Note: The 3-digit scheme is optional except when merging under DMM

705.13 (and 705.12 which is not supported in Presort).

Labeling list L008 contains all 3-digit scheme combinations for Periodicals, Standard Mail, and Package Services BPM flat-sized packages in which the pieces consist entirely of mail that meet the dimension, weight, and flexibility criteria for the AFSM 100 (DMM 301.03).

The schemes in L008 encompass multiple ZIP Codes from the same service area. They eliminate the need for you to prepare individual 3-digit ZIP Code packages for the ZIP Codes in L008. As a result, you will have fewer presort packages and containers to prepare which means less labor.

The USPS designed L008 to create packages that maximize the use of AFSM 100s for sorting incoming secondary mail. Benefits include speedier delivery because your mail is dropped closer to the final delivery location.

Labeling list L008 contains several facilities that cross SCF service areas. That means that several ZIP Codes may lose their DSCF discount eligibility based on the label-to ZIP Code. Take this into consideration when you use this option.

Note: Presort allows you to prepare UFSM 1000 flats with AFSM 100 flats when you turn on the Separate Package by Bindery option in the scheme block.

Create 5DG Auto Packages and Trays

If you want to include the optional 5-digit sortation for either Tray Automation or Automation, type Ye s for the Create 5DG Auto Pkgs & Trays parameter.

Note: When you choose Combined or Regular for the Preparation Type, the 5-digit sortation level is required and Presort ignores a No setting for the Create 5DG Auto Pkgs &Trays parameter.

Create 5DG Pallets (Y/N)

Five-digit pallets are optional in the schemes in which this parameter appears. Sorting at this level could speed delivery and could improve the results of SCF Pallet Protection (see the Presort User’s Guide).

Note: Sorting at the 5-digit pallet level might result in a lot of small pallets, unless you increase the weight for this level.

Presort Job-File Reference

Page 89

Create Flats 5DG Metro Pallets (Y/N)

Set up Presort to prepare flats 5-digit metro pallets if you are mailing into a metropolitan area (currently only New York and Chicago are included), and you are preparing packages on pallets for Periodicals flats, Standard Mail flats, and Package Services bound printed matter flats.

Benefits include faster delivery through more efficient mail handling, and destination Sectional Center facility (DSCF) discounts for metro pallets dropped at the SCF.

Presort uses labeling list L006 to make the flats 5-digit metro pallets.

Presort level hierarchy Presort forms metro pallets out of packages that don’t qualify for the 5-digit

pallets. For example, if you had several groups of packages that, when sorted to the 5-digit level, didn’t weigh enough to make the minimum pallet weight, the groups could be combined to form a metro pallet. The metro pallet is formed if the group of packages are going to one of the ZIP Code groups that are listed in labeling list L006. (Currently L006 includes ZIP Codes from Chicago and New Yo rk . )

These illustrations show how the mail is sorted with and without the metro pallet level.

Hierarchy without flats 5-

digit metro pallet level

The arrows represent the normal flow of mail from one level to the next.

Hierarchy withflats 5 digit

metro pallet level

The arrows on the right represent mail following the normal flow of mail. The arrows on the left show the levels from which the mail comes that make up the metro pallets.

Flats metro pallets are made up of mail from 5-digit and 3digit packages that don’t qualify for 5-digit pallets. Flats metro pallets are made before 3-digit pallets are made.

5-Digit Packages

5-Digit Pallets

3-Digit Packages

3-Digit Pallets

5-Digit Packages

5-Digit Pallets

3-Digit Packages

Flats 5-digit metro Pallets

3-Digit Pallets

Chapter 2: Job-file blocks and parameters

Page 90

Labeling list L006 The USPS created labeling list L006 to group the applicable ZIP Codes together

for each postal facility in the New York and Chicago metro areas. It contains:

 The eligible 5-digit ZIP Codes for each metro facility.

 The eligible 3-digit ZIP Code and acceptable mail class for the facility.

 The facility name for the container label.

All of the metro pallets going to New York will go to the New York 5-digit SCF. The SCF in turn sends the pallets to the facility listed on the label (from column C). The advantage is that the postal workers at the SCF do not have to break down the pallets and re-sort them before they send them to the appropriate mail units. This saves time and speeds delivery.

Example portion of L006 This table is a portion of labeling list L006 for New York.

Column A 5-Digit Destination ZIP Codes

10002-06, 09-14, … 100-102 (STD and BPM

Column B Package Placement for Residual 3-Digit Packages

Column C Container Label

MORGAN STATION NY 100

only)

10017, 44 … N/A GRAND CENTRAL STA NY 10017

Reading the table Column A lists the 5-digit ZIP Codes that are accepted at the facility listed in

column C. Column B lists the 3-digit ZIP Codes and the mail classes that are accepted as 3-digit packages at the facility listed in column C.

Example The Morgan Station, NY facility accepts all 5-digit packages for the ZIP Codes

listed in Column A. However, the facility only accepts 3-digit packages for the ZIP Codes listed in column B, and only for Standard Mail (STD) and Package Services bound printed matter (BPM).

The Grand Central Station, NY facility accepts all 5-digit packages for the ZIP Codes listed in column A. The N/A in column B means that the facility does not accept any 3-digit packages.

Reports All of the Presort reports list the metro pallet as MET. In addition, the metro pallet

information is included in Mail.dat output files.

Presort Job-File Reference

Important: The USPS advises that you don’t select this option for AFSM

100-compatible daily newspapers. You will experience service delays on this type of time sensitive publication.

Page 91

Create 5DG Sacks (Y/N) Create 5DG Scheme Containers (Y/N) Create 5DG Scheme Trays (Y/N) Create 5DG Trays (Y/N)

This description also applies to the Create Carrier 5DG/Scheme Sacks parameter.

The 5-digit and 5-digit-scheme levels are optional in the schemes in which they appear. These two levels are similar, except in one respect:

 5-digit trays or sacks contain pieces destined for the same 5-digit ZIP Code.

 5-digit-scheme trays contain pieces destined for multiple 5-digit ZIP Codes.

Similarly, carrier-route 5-digit scheme sacks contain packages destined for multiple 5-digit ZIP Codes. The USPS determines which ZIP Codes you can combine in a container.

We suggest that you set these parameters to Yes. You’ll benefit from—

 Lower postage in trays, because pieces in these containers receive the 5-digit

rate. There is no postage benefit to creating carrier-route 5-digit-scheme sacks.

 Speedier delivery, since more mail is routed closer to its ultimate destination.  In the case of 5-digit scheme containers, less handling. Fewer—and fuller—

trays and sacks will be formed because pieces and packages from more than one ZIP Code can be used to meet the minimum container volume.

Note: The USPS publishes a list, or scheme, of ZIP Codes that are eligible for 5-digit-scheme tray preparation and a different list for carrier-route 5digit-scheme sacks. If you are accustomed to preparing scheme trays for certain ZIP Codes, do not assume that those same ZIP Codes can be prepared in scheme sacks.

Create 5DG Scheme (L007) Packages (Y/N)

Presort automatically creates 5-digit L007 scheme packages for Periodicals, Standard Mail, and Package Services bound printed matter (BPM). This preparation is required when you are merging pallets of AFSM 100-compatible flats that are prepared under DMM 705.13, merged palletization.

When you prepare AFSM-100-compatible pieces that are not prepared under DMM 705.13 (Package Services BPM for example), turning off the option can make your bindery run more efficiently. Sometimes this time savings is more valuable than the postage savings.

For example, if you have the option selected (set to Y in Job), and the 5-digit scheme containers consist of just a few pieces or they are sporadically formed, you are forced to stop and start the bindery during the job to make small mixed ADC containers. When you set this option to N, the smaller containers are forced to the end of the job when you would normally turn off the bindery to clear out the bins.

Also, you wouldn’t want to create the 5-digit L007 scheme packages if you are preparing a daily publication. The chances that your publication would arrive late are very high.

Chapter 2: Job-file blocks and parameters

Page 92

Create 705.13 Merged 5DG/Scheme Pallets (Y/N)

Set the Create 705.13 Merged 5DG/Scheme Pallets parameter according to the processing category you choose. We recommend that you set this parameter to N for irregulars, UFSM1000s, and flats. In most cases, using 705.8 (setting the parameter to N) is less complex and has fewer limitations for merged palletization. In addition, by setting the parameter to N, you can potentially improve deliverability because more mail is brought closer to its delivery unit. If you use the AFSM100 processing category, we recommend you set the parameter to Yes.

When creating a bindery set (see “Separate Packages Per Bindery (Y/N),” on page 116), Presort is able to process both AFSM100 sized flats and nonAFSM100 sized flats in one mailing. You can choose to merge pallets for all pieces using 705.13 (setting the Create 705.13 Merged 5DG/Scheme Pallets parameter to Yes) or you can place only non-ASFSM100 flats on merged pallets using 705.8 (setting the parameter to No). It all depends on what you want to accomplish and how many pieces of each processing category you have.

Create ASF Sacks (Y/N) Create BPM ASF Pallets (Y/N) Create BPM ASF Sacks (Y/N)

The ASF sort level is optional in the schemes in which this parameter appears. Sorting at the ASF level could speed delivery or reduce mail handling.

Type Y for BPM ASF sacks to receive DBMC discounts on your BPM machinable parcels that are dropped at certain ASFs.

Create CART 5DG Container (Y/N)

Select this option to turn on carrier route preparation (carrier route containers or carrier route 5-digit containers). Regular preparation is required at the 5-digit level, but optional at the 5-digit scheme (L606) level. If you do not select this parameter, Presort will drop and process any un-containerized carrier route pieces at the regular level.

Create CART Direct Container (Y/N)

Select this option to create Carrier Route Direct containers. If you do not select this option, all pieces are processed at Carrier Route 5-digit container level (see “Create CART 5DG Container (Y/N)” on page 92 for more information). If you do not select either of the CART container parameters, Presort will drop and process any un-containerized carrier route pieces at the regular level.

Create Carrier 5DG/Scheme Sacks (Y/N)

See discussion of scheme containers at the Create 5DG Scheme containers parameters on page 91.

Presort Job-File Reference

Page 93

Create Carrier Route Rate Trays (Y/N)

The carrier-route sort level is optional in the schemes in which this parameter appears. If you choose to sort to this level, the mail pieces must be barcoded.

You’ll pay less postage on mail pieces that qualify for the carrier-route level, so it’s a good idea to set this parameter to Yes if your mailing list is dense enough to qualify for the carrier-route rate.

See the Min Carrier 5DG Tray parameter for details on reducing the number of small carrier-route trays formed.

To qualify for the carrier-route level in First Class:

 You may have as few as ten carrier-route pieces per route in this mailing.

 Mail pieces must be destined for USPS facilities that do not have barcode

sorting equipment or where the sorting equipment can process only a limited number of carrier routes at a time. These are generally small local offices. In these cases, the USPS rewards you with discounts if you sort the mail by carrier route. If the office that delivers this mail has more sophisticated sorting equipment, no discount is given for sorting to this level.

Create Irreg 3DG Pallets (Y/N) Create Irreg 3DG Sacks (Y/N)

Enter Yes to create Parcel Post nonmachinable parcels that qualify for the destination SCF (DSCF) rate. These parcels must be:

 sorted to the 3-digit level  entered at an SCF

These parcels, on pallets or in sacks, are mailed at the DSCF rate when they are dropped at the SCF that is the delivery unit for the parcels. For certain ZIP Codes, mail that would normally go to an SCF must be taken to the parent BMC. The nonmachinable parcels going to those ZIP Codes also receive the DSCF rate.

Create Machinable 5DG Trays (Y/N)

If you use the machinable preparation option, you are not required to make 5-digit trays. We recommend that you set this parameter to No. These pieces will receive the same rate whether they're prepared in 5-digit or 3-digit trays. So if you decide not to sort to the 5-digit level, delivery may be slower, but you'll possibly have fewer, and fuller, trays.

Presort will prepare mail pieces loose in 3-digit, AADC, and mixed-AADC trays. Packages will be formed only in overflow trays and in underfilled trays, and in all trays of postcard-size mail pieces.

Chapter 2: Job-file blocks and parameters

Page 94

Create MADC Tray on ASF/BMC Plt (Y/N) Create MADC Pkg on ASF/BMC Plt (Y/N) Created MADC Sack on ASF/BMC Plt (Y/N)

You can control the creation of mixed automated and mixed area distribution center (MAADC and MADC) packages and containers on ASF/BMC (area sectional facility/bulk mail center) pallets with this version of Presort.

Why turn it off? While this preparation may be beneficial in certain circumstances, it may cause

problems for others. It is beneficial because it increases the number of mail pieces that go on the pallets. However, sometimes the M(A)ADC packages and containers are small. These small packages (or bundles) slow down automated packing processes, and may sometimes jam the machine. In addition, these small packages ultimately require special handling for placement onto the ASF/BMC pallets.

Create Mixed ADC Pallets (Y/N)

Making mixed ADC pallets is optional, however it may reduce mail handling because mail that wouldn’t normally qualify for the other sortation levels may go into mixed sacks and be placed on an MADC pallet.

Note: Typing No for this option is the same as setting the No Sorting After

option to ADC. If you activate both options, Presort will not create any mixed ADC pallets.

Create Mixed BMC Pallets (Y/N)

Mixed-BMC pallets are optional in the schemes in which this parameter appears. Sorting at this level could reduce mail handling. For example, if you choose to sort to the Mixed-BMC pallet level, your entire job might be prepared on pallets.

Create MXD Origin(L201) Pkg/Sack(Y/N)

Enter Yes to create Origin Mixed ADC (L201) bundles and sacks.

The content of a sack at the new mixed package level (as well as the content of mixed packages from mail left over after the 3-digit, 5-digit and ADC bundles have been prepared), will be determined from the labeling list, L201. This labeling list is based upon the 3-digit ZIP of both the entry point and the destination. Mail left over after this level will still be prepared in mixed bundles and sacks according to the L009 labeling list.

Presort Job-File Reference

Page 95

Create Overflow Auto Trays (Y/N)

Enter Yes to make overflow trays.

As a general rule, overflow trays are allowed if the next sortation level has a higher rate. Refer to sections 125 (First Class), 707 (Periodicals), and 345 (Standard Mail) of the DMM for mail types that cannot have overflow trays.

Entering No here creates fewer trays, but those pieces that would have gone into the overflow tray fall to the next sortation level and are charged higher postage. Before you decide to turn off overflow trays, you must carefully compare the cost of making more trays and the increase in postage.

For some schemes, Presort automatically creates overflow trays when applicable. These schemes don’t have the Create Overflow Auto Trays parameter. You can control the creation of overflow trays for carrier route mail through your minimum tray settings for 5-digit trays, or by choosing to create 3-digit trays.

Create SCF Containers (Y/N)

This is an optional sort level. Use it to route mail a little closer to its ultimate destination. However, note that Presort likely will form more containers.

You can also use this parameter to control the creation of value-added 3-digit sacks for:

 PSVC BPM flats (with or without a barcode discount)

 PSVC BPM presorted packages of irregular parcels (less than 10 pounds) in

sack

To create value-added sacks only: In Job, type Ye s for the option Create SCF Containers.

To create all 3-digit sacks: Type No for the option Create SCF Containers.

Note: If you type No for this parameter, Presort won’t create any SCF

containers in your job.

ECR Reg Letter Use Mach Prep Opt

See “Reg Letter Use Mach Prep Opt (Y/N),” on page 113 for a description.

Entry Point (LAST EP/ALL)

At this parameter, you choose the entry points to which the Single Piece scheme will apply. Here are your choices:

 Type Last EP if you want this scheme to apply only to the last entry point in

the job. All single-piece-rate mail will be entered at one entry point. (You can accomplish the same results by linking the single piece scheme to the last entry point. See the Presort User Guide for details on linking schemes to entry points.)

 Type All if you want this scheme to apply to all entry points in the job. This

option may result in faster delivery of single-piece-rate mail.

Chapter 2: Job-file blocks and parameters

Page 96

Max … Pallet Weight (or Max Wt 5DG Pallet)

This section describes these parameters:

 Max 5DG/Scheme Pallet Weight

 Max 3DG Pallet Weight

 Max SCF Pallet Weight

 Max ASF Pallet Weight

 Max BMC Pallet Weight

 Max MBMC Pallet Weight

These parameters allow you to set the maximum pallet weight for Standard Mail on pallets. Note that the weight you enter has to be at least double the minimum. Making maximum pallet weight settings in each presort level gives you better control over your pallet creation. You can make sure that your pallets don’t get too heavy and awkward, and you can control the pallet load per truck and per entry point.

Find the maximum weight parameters in these schemes:

 STD, Letter Trays on Pallets  STD, Flats Letter Trays on Pallets  STD, Sacks on Pallets  STD, Packages on Pallets  STD, Machinable Parcels 5-dg & Basic Pallet  STD, Irregular Parcel Sacks on Pallets  STD, Irregular Parcel Packages on Pallets

Presort uses the Max Default Pallet Wt value if any applicable maximum setting is blank.

Also see “Max Default Pallet Wt (1000-2200 lb.),” on page 96.

Max Container Volume (50 to 100%)

If you’re mailing letters, see the Max Tray Volume parameter description on

page 100. If you’re mailing flats, see the Max Sack Volume parameter description

on page 98.

Max Default Pallet Wt (1000-2200 lb.)

Set the default weight for pallets. If the software encounters a blank pallet maximum weight for a particular pallet type, it uses this default setting. See also “Max … Pallet Weight (or Max Wt 5DG Pallet),” on page 96.

The maximum default pallet weight must be greater than or equal to twice the Min Default Pallet Wt parameter.

Set this parameter to the weight of the mail pieces only; do not include the weight of the pallet itself. The USPS allows you to form pallets that weigh up to 2,200 pounds, including the weight of the pallet, so we suggest that you never set this parameter higher than 2,100 pounds.

Presort Job-File Reference

Page 97

Max Default Tray Feet (72-144)

Use this parameter to set the maximum number of feet that Presort should use to form pallets. If the software encounters a blank maximum tray feet for a particular pallet type, it uses this default setting. See also “Max Tray Feet … Pallet (12-144),” on page 99.

Follow these guidelines:

 The maximum setting must be greater than or equal to twice the Min Default

Tray Feet parameter.

 Each pallet’s minimum setting can contain as few as 36 linear feet (three

tiers).

 A pallet must be formed when there are at least 72 linear feet (six tiers).

 No more than 144 linear feet (12 tiers) can be on a pallet.

Max Package Thickness

Set the maximum package thickness, in inches based on the guidelines in parenthesis or in the note.

If you are preparing flats packages in sacks for Periodicals or Standard Mail, choose the maximum package thickness based on the paper stock and the packaging. Follow these rules:

Type of binding Coated paper

package thickness

Uncoated paper package thickness

One strap placed along the width of the package. 3-inches 8-inches

Two straps; one placed along the width and one placed along the length of the package. (There is no

6-inches

(6-inches recommended)

longer a required banding sequence.)

Shrink-wrapped package. 3-inches

Shrink wrapped plus one or two straps. 6-inches

For mail other than flats packages in sacks for Periodicals and Standard Mail, here are some tips on setting your package thickness.

 Set the package size large enough to minimize the number of packages you

need to make.

 Set the package size small enough to stay within the limitations of your

binding equipment.

 If you form packages manually, consider the amount of mail your mail-room

staff can grasp easily.

If you’re preparing a First Class flats mailing (which are always prepared in tubs), we recommend setting the package thickness so that it doesn’t exceed one half of the height of the Max Tray Height. That’s because the USPS wants you to stack packages on top of one another to fill the tub as much as possible (and still be able to close the lid). It is much easier to fit packages into a flat tub if you follow our recommendation.

Chapter 2: Job-file blocks and parameters

Page 98

For example, if you set the Max Tray Height to 11 inches, and you set the Max Package Thickness to 6 inches, you would be able to fit just one level of packages in the tub. The USPS wants you to pack tubs more efficiently than that, so set this parameter with the Max Tray Height in mind.

For details on stacking mail in flat trays, see the Presort User’s Guide.

Max Pallet Package Wt (10 to 40 lb.)

You can use this parameter or the Max Package Thickness parameter, or both, to set the maximum package size. We recommend that you use both. Presort will form a package when it reaches one limit or the other.

The USPS sets the minimum package weight at 10 pounds. Choose a maximum package weight between 10 and 20 pounds (package weights above 20 pounds are allowed only in certain Package Services mailings).

You’ll want to set the package size large enough to minimize the number of packages you need to make, but small enough to stay within the limitations of your binding equipment. You also might consider reducing the number of heavy packages that your mail-room staff must handle.

Max Pallet Volume (75 to 100%)

You control the maximum amount of mail per pallet with this and the Max Default Pallet Wt parameter.

The Max Pallet Volume parameter is a percentage of total cubic inches.

Max Sack Volume (50 to 100%) Max Sack Weight (12-70 pounds) Max Sack Weight (20-70 pounds)

Use these parameters to control the maximum amount of mail per sack.

You must set both the maximum weight and volume limits. Presort will choose to use whichever limit best fits the mailing. To determine which limit to apply, Presort divides the weight of one piece into maximum weight, and the volume of one piece into maximum volume, and uses the limit that results in the smaller number of pieces.

For example, if you are mailing large poster tubes, it might take only 15 pieces to fill a sack by volume, but 100 pieces to fill a sack by weight. Presort would choose to form sacks based on the volume limit. If you’re mailing printed matter, weight is usually the limiting factor.

If you raise the limits too high, you might end up lugging some heavy, packed sacks. If you set them low, Presort will form more sacks, and you might waste some work by handling more sacks than necessary.

Presort Job-File Reference

Page 99

Max to Drop, ATM to REG (0 to 499) Max to Drop, CART to REG (0 to 499)

Of these two parameters, the Max to Drop, ATM to REG is most useful. Use this parameter to control how many pieces Presort drops from the automated to a regular scheme in a First Class job. Presort will drop up to the maximum number of pieces you specify here only if it can create another mailing at the regular level.

If you set this parameter to zero (0), Presort will not drop any automation pieces to the regular level. If there are fewer than 500 pieces sorted to the regular level, they will mail at the single-piece rate.

The maximum value that you can enter at the Max to Drop parameter is 499.

You could use the Max to Drop, CART to REG parameter to accomplish the same task, but we assume that you would rather drop pieces from the automation than from the carrier-route scheme, since you would want to retain as much mail at the carrier-route level and pay less postage.

If you’re using the No Sorting After parameter in another scheme, you must set the Max to Drop parameters to zero (0).

Max Tray Feet … Pallet (12-144)

This section describes these parameters:

 Max Tray Feet 5DG Pallet  Max Tray Feet 3DG Pallet  Max Tray Feet SCF Pallet  Max Tray Feet ASF Pallet  Max Tray Feet BMC Pallet  Max Tray Feet MBMC Pallet

Max Tray Height (inches)

These parameters allow you to set the maximum tray feet for Standard Mail trays on pallets schemes. Setting the maximum tray feet gives you greater control over pallet creation. You can make sure that your pallets don’t get too heavy, and you can control the pallet load per truck and per entry point.

Presort uses the Max Default Tray Feet value if any applicable maximum setting is blank.

Also see “Max Default Tray Feet (72-144),” on page 97.

This parameter applies to First Class flat trays (tubs). Set the maximum height of the mail in the tray, in inches.

We suggest that you leave the Min Tray Height parameter set to 8 inches. At this setting, packages will reach at least up to the bottom of the hand holds, which the USPS recommends.

Do not set the Max Tray Height greater than 11.25 inches. If you do, the packages will extend above the top of the tub and the lid won't close.

Chapter 2: Job-file blocks and parameters

Page 100

Max Tray Volume (50 to 100%)

Use this parameter along with the Min Tray Volume parameter to control the volume of mail in trays, expressed as a percentage.

To be considered full, a tray must be at least 75 percent full, so you may set the minimum and maximum between 75 and 100 percent.

If you set the minimum to any value other than 75, Presort will issue a warning. That's because the USPS requires you to make a full tray when you have enough mail pieces to do so to ensure that your mailing is sorted to the finest level. To optimize postage savings, you wouldn't want to set the minimum lower than 75 percent anyway.

We include the parameter here because some mailers have special permission from their local postmasters to set the minimum higher than 75 percent, but doing so takes the mailing outside of USPS regulations.

If both one-foot and two-foot trays are being used in a mailing, the volume settings that you type here will apply to both tray types.

The number of inches, and thus the number of mail pieces, that your volume setting yields depends on what type of tray(s) you use:

Tray Volume (percent) Inches

Letter one-foot 100 10.25

75 7.69

Letter two-foot 100 21.00

75 15.75

Two-foot EMM trays 100 21.75

75 16.31

For example, if the mail piece is an eighth of an inch thick (.125), then two-foot trays must contain at least 126 pieces, and no more than 168 pieces.

100

Presort Job-File Reference

Business objects PRESORT 7.71C User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Presort

Job-File Reference

Contents

Preface

Welcome to Presort Job

Getting started

Sample job To help you get started preparing your own Presort jobs, Business Objects

Templates The Presort master job file includes blocks of parameters for all mail classes and

Guidelines for editing job files

Editing tips To edit job files, you need working knowledge of a good text editor or word-

Steps in a Presort job

Step 1: Plan ahead There are lots of questions to ask yourself before you even choose a template job

Step 2: Create DEF and FMT files

Step 3: Complete the job file

Step 4: Start Presort Before running Presort, make sure that you have:

Step 5: Verify the job As Presort begins processing your job, it first checks the settings in your job file.

Step 6: Evaluate processing messages

Step 7: Check reports Check the results of your job by looking at the reports, particularly the Job

That’s it! You’ve processed your first mailing with Presort! The biggest step involves

Address Output File

Setup is important It is important that you take care in setting up your output files so that software

Automatic supporting files

Alternate Entry Point Sequence

Alternate Mailstream Hierarchy Sequence

Alternate Presort Scheme Sequence

Multiple occurrence of same block

Alternate Segment Sequence

Auxiliary Files

zone.dir For Periodicals and Standard Mail mailings, Presort uses data in the Postal Zone

dsf.dir If you prepare walk-sequence mailings, Presort will use the Delivery Statistics

facility.dir This directory contains information about USPS drop ship facilities, such as drop

maildirect.dir This directory contains information about where and when mail pieces should be

Container Output File

Setup is important It is important that you take care in setting up your output files so that software

Automatic supporting files

Container Sequence

Create File for Output

Setup is important It is important that you take care in setting up your output files so that software

Naming split output files

Entry Point Defaults

Entry Point Description

Execution

General

General Output

Input File

Mailflow

Mailing Information

Name Optimizer Control

Name Optimizer Resource File

On-Demand Reporting

Report files If you use On-Demand Reporting, you must plan carefully to avoid overwriting

Output Entry Point Selection

Output Order

Output Presort Scheme Selection

Output Segment Selection

Output Selection

Package Output File

Setup is important It is important that you take care in setting up your output files so that software

Supporting files When you make any output file, Presort automatically produces some supporting

Package Sequence

Pallet Output File

Setup is important It is important that you take care in setting up your output files so that software

Supporting files When you make any output file, Presort automatically produces some supporting

Pallet Sequence

PER Ride-Along Enclosure Description

Post to Input File

Presort scheme parameters