CODE-1 Plus Installation Guide - Pitney Bowes · 2019. 4. 1. · Installation Steps Release 4.2.0...

CODE-1 Plus™Version 4.2.0

Installation Guide For All Platforms

Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of Pitney Bowes, 3001 Summer Street, Stamford CT 06926-0700.

© 2017, Pitney Bowes Software Inc. All rights reserved.

MapInfo, Group 1, and Group 1 Software are trademarks of Pitney Bowes Software Inc. All other marks and trademarks are property of their respective holders.

Pitney Bowes Inc. holds a non-exclusive license to publish and sell ZIP + 4® databases on optical and magnetic media. The following trademarks are owned by the United States Postal Service: CASS, CASS Certified, DPV, eLOT, FASTforward, First-Class Mail, Intelligent Mail, LACSLink, NCOALink, PAVE, PLANET Code, Postal Service, POSTNET, Post Office, RDI, SuiteLink, United States Postal Service, Standard Mail, United States Post Office, USPS, ZIP Code, and ZIP + 4. This list is not exhaustive of the trademarks belonging to the Postal Service.

Pitney Bowes Inc. is a non-exclusive licensee of USPS® for NCOALink® processing.

Prices for Pitney Bowes Inc. products, options and services are not established, controlled or approved by the USPS® or United States Government. When utilizing RDI™ data to determine parcel-shipping costs, the business decision on which parcel delivery company to use is not made by the USPS® or United States Government.

3001 Summer StreetStamford CT 06926-0700USA

www.pitneybowes.com

www.pitneybowes.com

Table of Contents

Chapter 1: Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Before You Begin the Windows Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Windows Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Contents of the *.ZIP or *.EXE File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Internet Installs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Media Installs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Default Installation Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Installation Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Installed Folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Installing the Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

CODE-1 Plus Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Verifying the Product Installation (SAMPLE Job) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Installing Product Updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Chapter 2: Installing on UNIX/Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Before You Begin the UNIX/Linux Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Important Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Determining Installation Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Creating the /opt/pitneybowes Product Registration Area . . . . . . . . . . . . . . . . . . . . . . .18

Re-Installation and New Release Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Contents of the *.ZIP or *.EXE File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Patch Installs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Media Installs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Contents of the Compressed tar file (*.taz). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19


Internet Download and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Install the Product Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Install the Database Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Verify the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Product Environment Variables - setup or setup.csh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

COBOL Environment Variables - setup or setup.csh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Product Environment Variable - setmedia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Permanent Keys and the lminstall Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24


Special Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Runtime Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26NFS Mounted File Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Sorted Raw Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Release 4.2.0 3 Installation Guide - All Platforms

Table of Contents

Temporary Directories (/tmp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Special Notes for Uninstalling Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26


Chapter 3: Installing on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Before You Begin the z/OS Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30


Contents of the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

If Your Product Has License Management... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Installing from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Installing from Internet Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Contents of the .exe File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Installing Software Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Installing Downloaded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Installing CICS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Configuring CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36


The Next Step - Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37


Chapter 4: Installing on IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Before You Begin the IMS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40


Contents of the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

If Your Product Has License Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41


Installing from the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Contents of the Downloaded File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Installing Software Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Installing Downloaded Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46


The Next Step — Running Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48


Chapter 5: Installing on IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Before You Begin the IBM i Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Will Any Objects Be Changed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

License Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Installing from Internet Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51


Selecting the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Installing the Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Global Library Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Product Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Locked Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Completing the Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Defining Custom Screen Headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Installing a Product Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Installing Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60


Table of Contents

What You Need to Know.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

File Size Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60


Installing Downloaded (IDS) Database Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Installing Database Files from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Changing the Default Library Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Running the Installation Verification Procedure (IVP). . . . . . . . . . . . . . . . . . . . . . . . . .63

Additional Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63


Chapter 6: License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Understanding CODE-1 Plus License Management . . . . . . . . . . . . . . . . . . . . . . . . . . .66

License Management Process for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Finding Your System ID for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

License Management Screen Error Messages for Windows . . . . . . . . . . . . . . . . . . . . .66

License Management Report Error Messages for Windows . . . . . . . . . . . . . . . . . . . . .67CODE-1 Plus™ Execution Log File (XLG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

CODE-1 Plus™ License Management Execution Log File (LMREPORT.XLG) . . . . . . . . . . . 67

CODE-1 Plus™ License Management Report (LMREPORT.RPT) . . . . . . . . . . . . . . . . . . . . 68

License Management Process for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Finding Your System ID for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

AIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SunOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Display Error Messages for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

License Management Report Error Messages for UNIX . . . . . . . . . . . . . . . . . . . . . . . .70

License Management Process for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Finding Your System ID for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Red Hat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

SuSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Linux Display Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71

Linux License Management Report Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .71

License Management for z/OS and IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Finding Your System ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72z/OS and IMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

License Management Error Messages for z/OS and IMS . . . . . . . . . . . . . . . . . . . . . . .72

License Management for IBM i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Finding Your System ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Interactive Processing License Management Error Messages . . . . . . . . . . . . . . . . . . .74

Batch Processing License Management Error Messages . . . . . . . . . . . . . . . . . . . . . . .74

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Table of Contents


1
Installing on Windows
In this chapter...

Before You Begin the Windows Installation . . . . . . . . . . . . . . . . . .8 Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Installing the Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Verifying the Product Installation (SAMPLE Job) . . . . . . . . . . . . .13 Installing Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Before You Begin the Windows Installation

Before You Begin the Windows Installation

Pitney Bowes delivers CODE-1 Plus software for the Windows platform via internet download at http://www.g1.com/support. If needed, you can obtain installation media at an additional charge from the Pitney Bowes estore. Please log in to the Pitney Bowes estore for media purchasing and shipping.

IMPORTANT: The CODE-1 Plus™ Windows® installation procedure has changed for the CODE-1 Plus™ 4.2.0 release. The new installation process supports Windows® Server 2008 or later versions. If you attempt to install on an unsupported version, the installation will end and issue a warning message. Job scripts used with previous releases of CODE-1 Plus™ will no longer run because of variable name changes. Please review the CODE-1 Plus 4.2.0 Release Notes at http://www.g1.com/support and this chapter for information on the required variable name changes you must make for CODE-1 Plus™ 4.2.0.

Before installing the CODE-1 Plus™ 4.2.0 release, we recommend that you back up any library locations that contain custom scripts.

System Requirements

The requirements for installing CODE-1 Plus on a Windows platform are:

• An account with Administrator privileges. Since CODE-1 Plus uses system environment variables, you must be logged on as an administrator to successfully install software and databases.

• A supported platform. For a list of supported platforms, see the “Supported Platforms” document available at http://www.g1.com/support.

• A minimum of 32 MB RAM. This memory requirement does not include memory for your application code and data.

• A minimum of 20 MB of free hard disk space to install the software.

• Additional hard disk space to install all databases on disk as noted below:

• If you are upgrading an installed product, be sure to back up any files you have changed.

Database Space Required

U. S. Postal database 1.1 GB

Early Warning System (EWS) 300 KB

Line of Travel (LOT) 350 MB

Delivery Point Validation (DPV) The space required for the DPV database depends on the database type:

• FULL - 955 MB

• SPLIT - 1.4 GB

• FLAT - 2.2 GB

LACSLink 375 MB

SuiteLink 525 MB

Residential Delivery Indicator (RDI) 48 MB


http://www.g1.com/support



Chapter 1: Installing on WindowsBefore You Begin the Windows Installation

• Permanent License Key available (for a new installation, if required). The Access Key only allows temporary use of the software. The Access Key that appears on the Download Software screen is valid for ten days. If your Access Key expires, return to the Pitney Bowes website at http://www.g1.com/support to get a new Access Key (in the My Products section), or obtain your permanent license file.

• Product documentation and release notes downloaded from http://www.g1.com/support.

Installing more than one Pitney Bowes product in the same library is not advised. There are several modules that have common names that are used by more than one product. These modules are periodically updated to accommodate added functionality in one software product, and may cause conflicts if shared with other Pitney Bowes applications. Pitney Bowes highly recommends that each application's programs are put into separate application libraries.

Windows Naming Convention

When installing software on Windows Server 2012 or later, ensure that the file system supports the 8.3 naming convention.

If you are installing your product and databases for the first time, perform a check on the status of 8.3 format support. From a Windows command line, use the following command, assuming drive "c" for this example: fsutil 8dot3name query c:

Windows will display a message with 8.3 file name support status. If 8.3 file name support is disabled, use this command to enable that feature, replacing "c" with your drive letter: fsutil 8dot3name set c: 0

Setting Environment Variables

The following variables are either set at installation ("Required") or are user-defined ("Optional"). You can overwrite default paths during installation.

Variable Description DefaultRequired or Optional?

PBC1P Path of the product software directory containing the lib and rts folders. Set at installation.

[Program Files]\Pitney Bowes\CODE-1 Plus

Required

PBC1PDB Path of the database/reference file directory. Set at installation.

[Public Documents]\Pitney Bowes\CODE-1 Plus\DB

Required

PBC1PDOCS Top-level directory for user-modifiable files (*.bat scripts, parameters, data). This directory contains the CODE-1 Plus bin and data folders. Set at installation.

[Public Documents]\Pitney Bowes\CODE-1 Plus

Required

PBCD Source location for media. Set at installation.

First media drive found on your machine, if present. Defaults to the directory containing the installation media if no media drive is found.

Required




Installation Steps

Contents of the *.ZIP or *.EXE File

Internet Installs

We deliver software releases in a zipped or executable file named C1Pnnn.ZIP or C1Pnnn.EXE, where nnn is the release number. The file name may also contain additional characters, following the C1Pnnn structure, that indicate post-release build numbers and other important internal information. This file contains an install image (which in turn contains setup.exe) that must be downloaded to a temporary folder you define.

Software updates (also called “fixes” or "patches") may also be identified by a fix level, along with the product code and release number; for example: C1PnnnCaabbcc.zip or C1PnnnSaabbcc.zip (or with the *.exe extension).

Media Installs

Installation media is only available from the Pitney Bowes estore. Please log in to the Pitney Bowes estore for media purchasing and shipping. Additional information may be provided in a README.TXT file.

Default Installation Directories

The default installation directory for installing CODE-1 Plus on a 32-bit operating system is C:\Program Files\Pitney Bowes\CODE-1 Plus.

The default installation directory for installing CODE-1 Plus on a 64-bit operating system is C:\Program Files (x86)\Pitney Bowes\CODE-1 Plus.

Installation Steps

This section provides instructions for installing CODE-1 Plus on a Windows platform from internet download or media.

Installing the Software

To install your CODE-1 Plus software, follow these steps:

1. Log in to the Technical Support web site at http://www.g1.com/support.

2. Click My Products.

PBEDIT Defines the text editor to use for jobs and parameters using the edit icon. Set this as a user variable. If not explicitly set by user, the default value is used.

Notepad™ Optional

PBPAUSE Defines whether to pause at the end of the job when running in Windowed mode. If not explicitly set by user, the default value is used.

By default, jobs do not run in Windowed mode. Jobs run in the background

Optional

PBTMP Location for temporary files. If not explicitly set by user, the default value is used.

%PBC1PDOCS%\data Optional

Variable Description DefaultRequired or Optional?



Chapter 1: Installing on WindowsInstalling the Databases

3. Click CODE-1 Plus.

4. Click View Available Downloads for your platform.

5. Click Software and download the CODE-1 Plus software files.

6. Locate the setup.exe file and double-click to start the software installation process.

7. Follow the prompts to complete the software installation process.

Installed Folders

1. Locate the folder that contains the scripts and data for running CODE-1 Plus jobs. By default, this folder is identified by the PBC1PDOCS environment variable as [Public Documents]\Pitney Bowes\CODE-1 Plus).

2. Locate the folder that contains the CODE-1 Plus application and runtime. By default, this folder is identified by the PBC1P environment variable as [Program Files]\Pitney Bowes\CODE-1 Plus.

Installing the Databases

After installing the software, follow these steps to install the subscription databases:

1. Review the README file and/or the product documentation for detailed information on installing the appropriate databases for your product.

2. Log in to the Technical Support web site at http://www.g1.com/support.

3. Click My Products.

4. Click the product link to access the appropriate databases to install.

5. Click View Available Downloads for your platform.

6. Click Databases and download the database files for your product.

Folder Description

bin Contains files, scripts, and icons used to run/edit CODE-1 Plus jobs.

• Batch files (.bat)– SAMPLE.bat - batch installation verification procedure that runs the SAMPLE job

• Visual basic scripts (.vbs)

– C1PJOB.VBS - Utility to edit CODE-1 Plus job batch file

– C1PRun.VBS - Runs a CODE-1 Plus job

• Icon files (.ico)

data Contains job parameters, report files, input name/address file, and output files generated by the job

DB Contains databases

Folder or File Description

bin Contains the CODE-1 Plus™ help files.

lib Contains the CODE-1 Plus program files

rts Contains the runtime system

README.TXT File containing late-breaking information from the Pitney Bowes programming team



Installing the Databases

CODE-1 Plus Databases

The following table describes the databases available for use with CODE-1 Plus.

DatabaseRequired or Recommended Description

U.S. Postal Database

Required Contains U.S. Postal data in a Pitney Bowes proprietary format. This database contains every house number range in the United States and is updated on a monthly basis. The database files contain the following information:

• ZIP + 4 Code

• Standardized address elements

• City and state information

Data needed to perform Enhanced Street Matching (ESM) and All Street Matching (ASM). ESM and ASM apply extra matching logic to any input address that is not matched through the regular address validation process.

SuiteLink Required to generate a USPS Form 3553 (CASS Summary Report)

The SuiteLink database corrects secondary address information for U.S. business addresses whose secondary address information could not be validated.

LACSLink Required to generate a USPS Form 3553 (CASS Summary Report)

The LACSLink database allows you to correct addresses that have changed as a result of a rural route address converting to street-style address, a PO Box renumbering, or a street-style address update.

DPV Required to generate a USPS Form 3553 (CASS Summary Report)

The Delivery Point Validation (DPV) database allows you to check the validity of individual U.S. mailing addresses. This database enhances the U.S. Postal database's ability to validate mailing addresses. Select the DPV file format for your environment:

• Full (often called "Hash") — Use DPV Full when database storage space is the most critical factor.

• Split — Use DPV Split for a medium-sized space storage factor.

• Flat — Use DPV Flat for the largest space storage factor.

RDI Recommended The Residential Delivery Indicator (RDI™) database contains data that identifies whether an address is a residential or a business address.

EWS Recommended The Early Warning System (EWS) database provides early alerts to address changes that could impact your address file.

eLOT Recommended The Enhanced Line Of Travel or eLOT processing provides routing information for your coded addresses. While eLOT processing is not required for CASS certification, it is required to obtain discounts. To accomplish this, perform eLOT processing as part of your address hygiene processing or separately as part of your presort processing.


Chapter 1: Installing on WindowsVerifying the Product Installation (SAMPLE Job)

Verifying the Product Installation (SAMPLE Job)

For new product releases, we recommend you run the installation verification procedure (IVP) SAMPLE job before running your own production jobs.

1. Go to the Start button and choose Programs > Pitney Bowes CODE-1 Plus > Run CODE-1 Plus Job.

2. Enter the job name, SAMPLE, and click OK. The job takes a few minutes to run.

3. When the job is complete, you will receive notification via a dialog box. Click Yes to review the output for errors.

4. To ensure that output files were produced, you can check the execution log (JobName.xlg) in the data directory where you loaded the software (for example, in [Public Documents]\Pitney Bowes\CODE-1 Plus\Data). The execution log/report lists the number of records processed.

5. If the SAMPLE job did not run to completion, contact Technical Support for assistance.

Installing Product Updates

To install a product update, follow these steps:

1. Back up your lib subdirectory.

2. Download the appropriate files from the Pitney Bowes web site at http://www.g1.com/support.

3. Extract the objects contained in the .ZIP file to a temporary directory on the same computer as your product installation. If the update contains an install.bat file, simply execute this file to install the update. If install.bat is not included in the update, copy the objects extracted from the .ZIP file to the lib subdirectory of your existing product installation. When prompted to overwrite existing files, reply Yes to all.

4. Check to see if the files updated successfully.

If You Need More Help

If you are unable to resolve a problem, contact Technical Support for assistance. Please have the following information ready:

• A description of the task you were performing.

• The resulting reports (specifically, the Execution Log and Parameter Record Listing).

The Technical Support Hot line number for customers in the United States and Canada is800-367-6950. You can also obtain product information and updates from http://www.g1.com/support.






2
Installing on UNIX/Linux
In this chapter...

Before You Begin the UNIX/Linux Installation . . . . . . . . . . . . . . . .16 Internet Download and Installation. . . . . . . . . . . . . . . . . . . . . . . . .20 License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Installing Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Special Notes for Uninstalling Products . . . . . . . . . . . . . . . . . . . .26 If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Before You Begin the UNIX/Linux Installation


Pitney Bowes delivers CODE-1 Plus software and databases via Internet download at http://www.g1.com/support or from the Pitney Bowes estore. If needed, you can obtain installation media at an additional charge from the Pitney Bowes estore. Please log in to the estore for media purchasing and shipping.

IMPORTANT: The UNIX®/Linux™ installation procedure has changed for the CODE-1 Plus™ 4.2.0 release. Job scripts used with previous releases of CODE-1 Plus™ will no longer run because of variable name changes. Please review the CODE-1 Plus 4.2.0 Release Notes at http://www.g1.com/support and this chapter for information on the required variable name changes you must make for CODE-1 Plus™ 4.2.0.

Before installing the CODE-1 Plus™ 4.2.0 release, we recommend that you back up any library locations that contain custom scripts.

System Requirements

The requirements for installing CODE-1 Plus on a UNIX or Linux platform are:

• An account with Administrative privileges to prepare the install environment. Specifically, the individual installing must have write access to the product install area of the target machine as well as write access to the /opt/pitneybowes shared registry area. Please refer to the "Determining Installation Permissions” on page 18 and "Creating the /opt/pitneybowes Product Registration Area” on page 18 for help with permission issues and the shared registry area.

• A supported platform. For a list of supported platforms, see the “Supported Platforms” document available at http://www.g1.com/support.

• A minimum of 32 MB RAM. This memory requirement does not include memory for your application code and data.

• A minimum of 20 MB of free hard disk space to install the software.

• Additional hard disk space to install all databases on disk as noted below:

• Permissions and privileges to access, read, and write to the target install area for Pitney Bowes products (including user:group permissions).

• Establish the /opt/pitneybowes area and grant write permission for the installer.

Database Space Required

U. S. Postal database 1.1 GB

Early Warning System (EWS) 300 KB

Line of Travel (LOT) 350 MB

Delivery Point Validation (DPV) The space required for the DPV database depends on the database type:

• FULL - 955 MB

• SPLIT - 1.4 GB

• FLAT - 2.2 GB

LACSLink 375 MB

SuiteLink 525 MB

Residential Delivery Indicator (RDI) 48 MB





Chapter 2: Installing on UNIX/LinuxBefore You Begin the UNIX/Linux Installation

• Run the optional permtest utility (see Determining Installation Permissions) to determine if the target install area is writable by the person installing. You can skip this step if you know the area you are installing into and the /opt/pitneybowes area is writable by the person installing.

• If you are upgrading an installed product, be sure to back up any files you have changed.

• Permanent License Key available (for a new installation, if required). The Access Key only allows temporary use of the software. The Access Key that appears on the Download Software screen is valid for ten days. If your Access Key expires, return to the Pitney Bowes website available at http://www.g1.com/support to get a new Access Key (in the My Products section), or obtain your permanent license file.

• Product documentation and release notes downloaded from http://www.g1.com/support.


Important Installation Notes

Before you install, verify that you have these checks in place to ensure a successful installation:

• Set up the proper user:group permissions for the area where this product is installed. If you do NOT have write access to the area where you are installing this product, the install process will not run to normal completion.

• You must establish a shared license area in /opt/pitneybowes. You only need to create this area once per target machine. You can use the shared license area to manage software licenses for multiple Pitney Bowes products.

• Verify that the /opt/pitneybowes area is present AND writeable by the person installing so the installation process runs to normal completion. You can use the optional utility pbprep, found in the same area as the install script, to create the /opt/pitneybowes area for you. If you have installed an earlier version of CODE-1 Plus, the install process will attempt to create this area for you assuming the individual installing has permissions to create the /opt/pitneybowes area.

The install process creates a log file to assist our Technical Support Representatives in resolving problems you may encounter during the installation. The installation script places file “pbauto.log” in the /opt/pitneybowes/var/log directory. If the person installing the software does not have write access to the /opt/pitneybowes/var/log area, or if they do not have write access to an existing pbauto.log file, the install process terminates with a warning message.

Root access is not required; however, you must have proper permissions for the area where you want to install CODE-1 Plus. If the installer does not have the proper privileges and authority, the install procedure terminates with a warning message.

HP-UX and AIX Users: If during the initial phase of the installation process the acushare license management daemon is running, the installation will issue a warning to the installer and stop. If this occurs, you must shut down the acushare daemon before the installation can continue. This is a precaution to ensure that the installation continues and does not “hang” while waiting for the acushare daemon to free up from memory.





Determining Installation Permissions

The root area of the downloaded installation package includes the optional permtest utility to help you determine if your target installation area has proper permissions (is writable). You can run the permtest utility, using the target installation as an argument to determine the permission settings. It should also be used on the /opt/pitneybowes area to determine if that area is writable as well.

To find valid permtest arguments and usage information, run permtest without any arguments:

./permtest

To determine permissions, run permtest with a target area as the first argument followed by the appropriate option:

./permtest <target installation area> <option>

where <target install area> is the path in which to install the product or the /opt/pitneybowes license area. Both areas should be checked for proper permissions prior to running the installation process.

<option> is -V, -v or blank.

Creating the /opt/pitneybowes Product Registration Area

CODE-1 Plus requires a product registration area, located in the /opt directory, where third-party software should be located. This product registration area must be defined as /opt/pitneybowes. During installation, CODE-1 Plus accesses /opt/pitneybowes to track production installation versions. You can install product software in any location you choose. The product registration area requires less than 10 megabytes of space.

CODE-1 Plus provides a script, pbprep, to create the /opt/pitneybowes product registration area. A System Administrator, or someone with root privileges, must run the pbprep script. Run the pbprep script as:

pbprep <user> <group>

Where <user> is the owner of the /opt/pitneybowes area and <group> is the group id of the group to have write access to the /opt/pitneybowes. The /opt/pitneybowes product registration area is updated during the installation process and the person installing CODE-1 Plus must have write access to this area. We recommend against installing software into the /opt/pitneybowes area, since this location is at the root level, and CODE-1 Plus needs additional space during processing.

Anyone with root privileges, such as a system administrator, can create the /opt/pitneybowes product registration area. The product registration area must contain the following subdirectories:

• /etc

• /man

• /var

• /var/log

If these directories are not present at the time of installation, the installation stops. The /opt/pitneybowes product registration area needs to be created only once per target machine.

During the installation process, the installation script provides these product registration area setup options:

• Install to a production area: Similar to a production installation, this area can be any location on the target machine, including NFS mounts. The product registration area tracks this product location.

• Install to a test area: The product registration file does not track the test area. Patches/updates are not applied to any test areas. You may create as many test areas as needed. Although TEST installations are not tracked by the shared product registration area, the /opt/pitneybowes directory structure must be present on the target machine, even for a TEST installation.


Chapter 2: Installing on UNIX/LinuxBefore You Begin the UNIX/Linux Installation

Re-Installation and New Release Information

If you are re-installing or installing a newer release of CODE-1 Plus, you must have appropriate privileges. When replacing an old version of CODE-1 Plus with a new one, we suggest that you establish separate TEST and PROD (Production) areas and environments. Run the new software in the TEST environment until you are satisfied with the processing results of the new release before you delete or overlay the previous release. If you choose to re-install or install a newer release in an existing area, please be advised that certain scripts (setmedia and setup) will NOT be overwritten and the newer scripts will be named setmedia.new and setup.new. The original script will not be modified. However, you should compare (diff) the old and new scripts to see if there have been changes (for example, new DD file statements) in the .new script that you may have to incorporate into the original script.

Contents of the *.ZIP or *.EXE File

Patch Installs

Pitney Bowes delivers software patch releases in a zipped or executable file named C1Pnnn.ZIP or C1Pnnn.EXE, where nnn is the release number. The file name may also contain additional characters, following the C1Pnnn structure, that indicate post-release build numbers and other important internal information. This file contains an install image (which in turn contains the install script) that must be downloaded to a temporary folder you define.

Software updates (also called “fixes”) may also be identified by a fix level, along with the product code and release number; for example: C1PnnnCaabbcc.zip or C1PnnnSaabbcc.zip (or with the *.exe extension).

Media Installs

Installation media is only available from the Pitney Bowes estore. Please log in to the Pitney Bowes estore for media purchasing and shipping. The Pitney Bowes estore delivers a media image on the product DVD. Additional information may be provided in a README file.

Contents of the Compressed tar file (*.taz).

Pitney Bowes delivers Internet software updates in compressed format as a zipped file containing the following files:

• install - installation script

• Platform-specific .taz (compress tar’d and zipped product) files:

• c1paix.taz - For AIX

• aixacu.taz - For AIX runtime

• c1phpx.taz - For HP-UX

• hpxacu.taz - For HP-UX runtime

• c1plnx.taz - For Linux

• lnxacu.taz - For Linux runtime

• c1psol.taz - For Solaris

• solacu.taz - For Solaris runtime

• permtest - Permissions Utility script (optional)

• pbprep - Script to setup the Pitney Bowes Software /opt/pitneybowes shared registry area (optional)

• uninstall - Script to remove existing products

• uninstall.main - Driver script for uninstall

• README - Test file containing relevant installation notes


Internet Download and Installation




Please archive your installed CODE-1 Plus prior to installing a newer version. If you install into an area that contains an earlier version of CODE-1 Plus, the install program overwrites existing files. For example, if you have installed in /usr/pb, and you then install a new version or copy into /usr/pb, the newer version deletes the previous release.




• ZIP + 4 Code

















Chapter 2: Installing on UNIX/LinuxInternet Download and Installation

You must have appropriate privileges to install, re-install, or update the CODE-1 Plus software. If not, it is possible that the installation may not update all files. For new releases, you may want to establish separate TEST and PROD (Production) environments. Run the new software in the TEST environment until you are satisfied with the processing results of the new release before you delete the previous release.

Install the Product Files

1. Download the product software from the Internet, extract the files, and FTP (in binary mode) all files to your system.

2. If you are in the directory where the files were FTP’d, proceed to the next step. Otherwise, change to the directory where those files are located.

3. Modify the permissions on the install script by using the chmod command:chmod -R 775 install

4. Type the install command:

./install

5. Follow the instructions provided in the installation script.

The installation script is intended to be a conversational package that queries both you and your system for information. Based upon the operating system level, the installation script determines which product package to install. In most cases, you should use the installation defaults.

Some additional points to consider:

– If you install the new product over the existing product, the current setup script (found in the bin subdirectory) is saved, and a new script with a file name extension of .new is installed.

– Because there may have been significant changes since you last installed the product, we recommend that you compare the current setup script with the setup.new script. Note the differences and modify the current script to include the new changes found in the .new script.

6. After you load the files, you may need to change the owner and group of each file via the chown command.

chown -R owner:group *Change owner to your owner name, and group to your group name. The asterisk (*) modifies all files and directories and -R modifies all subdirectories. You may change file permissions to limit or expand access to product files; however, this is not required.

Install the Database Files

After installing the software, follow these steps to install the database(s).

1. Download the database(s) from the Internet. The database(s) must be loaded before using the product.

2. For database files that are 2 GB or larger, remove the comment character (#) from the following commands in the setuprts script:

USE_LARGE_FILE_API=1; export USE_LARGE_FILE_API

3. If necessary, change the setmedia script to contain the correct information about the type and names of media.

4. If you specified a non-default directory for your database, you must change the $PBDB environment variable in the $PBDIR/c1p/bin/setup script. The database defaults to the directory $PBDIR/db.



5. Issue the appropriate source command to setup the environment:

. bin/setup for Bourne shells

source bin/setup.csh for C shell

6. Run the database installation script using one of the following commands:

$PBDIR/c1p/bin/installdb

or

cd to $PBDIR/c1p/bin and type installdb

7. Follow the prompts generated from the installdb script to complete the database installation.

Verify the Installation

After installing the software and database(s), run the verification procedures to ensure that everything works properly.

1. Issue the appropriate source command to set up the environment:

• . bin/setup for Bourne shells

• source bin/setup.csh for C shell scripts.

You must issue this command every time you establish a new environment by either logging in or exiting the shell in which the source command was issued. Normally, you do this as soon as you have logged on so all subshells you create have the product environment variables defined. Pitney Bowes recommends that you add the source command to your *.profile or *.cshrc file. However, this is optional. During the product installation process, the various environment scripts needed to run CODE-1 Plus are customized for your hardware and software environment.

These environment scripts include:

• setup• setup.csh (for C shell)

On rare occasions, you may need to modify these scripts after CODE-1 Plus has been installed. However, most scripts do not need to be modified. If there is a need to modify these scripts, refer to the following list of environment variables that can be changed for each script name listed.

2. Make the product license keys available.

The product licenses must be available before running the sample job. If you have a prior installation area where there are valid license files (found in c1p/data), and the product has been tracked by the product registration file found in the old /var/group1 area, the installation process copies the existing license files from the current area to the new install area. This only occurs if you are installing into a production installation area. The existing license files will NOT be copied for test areas.

If you have a current installation but have NOT used the /var/group1 product registration area, you must copy the current license files to the new installation area. The two license files (g1lmlic and g1lmlic.vix) can be found in the current c1p/data subdirectory.

CODE-1 Plus no longer includes a License Management process as part of the installation process. You must run the license management process after completing the software installation. License Management files must be present, active, and validated before running any CODE-1 Plus job.


Chapter 2: Installing on UNIX/LinuxInternet Download and Installation

3. If applicable, enter the 45-day access keys using the accesskeys script.

If this is a first-time installation and you have obtained temporary access keys from Pitney Bowes, you may enter these keys to provide you with 45 days of CODE-1 Plus processing before you obtain your permanent keys. To install the temporary access keys:

a. Change directories (cd) to the $PBDIR/c1p/bin area.

b. Source the setup script.

c. Run the accesskeys script. The accesskeys script will request one required key for CODE-1 Plus. After entering the key, you may proceed to run the sample job, assuming the database files have also been installed as mentioned above.

Typically, the following scripts will not have to be changed. These scripts are described here only to provide assistance if a script needs to be changed after the CODE-1 Plus installation.

Product Environment Variables - setup or setup.csh

COBOL Environment Variables - setup or setup.csh

Product Environment Variable - setmedia

Variable Refers to

PBSYS Type of OS (for example, AIX, SOLARIS, LINUX).

PBDIR Root path to where CODE-1 Plus is installed.

PBC1P Full path to where CODE-1 Plus is installed.

PBC1PDB Full path where the CODE-1 Plus database is located. This variable is modified in the setup and setup.csh script under the $PBDIR/C1P/bin directory. This environment variable is used by the product batch drivers and sample programs.

Variable Refers to

PBC1PRTS Full path to the location of the COBOL runtime directories.

CODE_PREFIX Full path to the location of the Pitney Bowes programs.

PATH The COBOL bin directory should be added to the path.

LD_LIBRARY_PATH Used for UNIX/Linux SVR4 system only. Add $PBC1PRTS/lib to the existing LD_LIBRARY_PATH.

SHLIB_PATH Used for HP-UX systems only. Add $PBC1PRTS/lib to the existing SHLIB_PATH.

LIBPATH Used for AIX systems only. Add $PBC1PRTS/lib to the existing LIBPATH.

Product Environment Variables

Variable Refers to

PBCDDIR Full path to the location of the database files. Typically points to the local directory where the raw input database files are located; however, the path can be modified to point to an NFS mount or directory where the input files are located on a remote device.


License Management

4. Issue the appropriate source command to set up the environment:

. ./setup

5. Set up the verification job (sample) environment variables by sourcing the sample job. Type the following product verification command.

. ./sample

6. Submit the IVP or sample job by typing the following command.

./runc1bm00

The IVP/sample job runs in the background and takes up to 10 minutes to complete. You may monitor its progress using the ps command (ps -ef | grep sample | grep -v grep or for IVP jobs, ps-ef | grep ivp.job | grep -v grep) or by running the chkrun script found in the product bin subdirectory.

7. Verify that the job executed properly by running the script bin/chkrun or look at the sample log file created in $PBDIR/C1P/data.

You have successfully installed your software. You can use the IVP or sample jobs supplied by Pitney Bowes as templates for your own jobs. Please refer to your CODE-1 Plus documentation for instructions on setting up and running your first job.

Permanent Keys and the lminstall Script

To install the permanent License Management files, follow these steps:

1. Download your permanent license keys from the Pitney Bowes Fulfillment.

2. FTP the license (.txt file) as ASCII to the /data directory.

3. Once the permanent license keys are in the /data subdirectory, cd to the $PBDIR/c1p/bin area.

4. Source the setup script then run the lminstall script.

5. The License Management files (g1lmlic, g1lmlic.vix) are, by default, loaded into the $PBDIR/c1p/data subdirectory area where the CODE-1 Plus product is installed.

The initial temporary Access Keys that are loaded and activated via the access keys process described above contain a 45-day key that allows you to run your CODE-1 Plus jobs. At the end of the 45-day period, you will be unable to run your CODE-1 Plus jobs unless you load your permanent license keys.

If this is an upgrade installation, and you have previous versions of CODE-1 Plus installed, your License Management files will be copied from the previous location to the new location, assuming you have used the default /var/group1 product registration area.

If you have installed prior CODE-1 Plus releases in an area that cannot be tracked via the /var/group1 product registration file, you have to copy the license files manually.

License Management

CODE-1 Plus requires license keys. To install License Management files, please follow these steps:

1. Change to directory (cd) $PBDIR/c1p/bin.

2. FTP the license file as ASCII to c1p/data.

3. Go to the bin directory and run the license management install:

./lminstall

4. Follow the prompts generated from the lminstall script to complete installation.


Chapter 2: Installing on UNIX/LinuxInstalling Product Updates


Before installing, verify that you have downloaded the correct version of the patch from the web site for your UNIX or Linux version. To install the product update:

1. Download the product update file. The downloaded file has a .zip or .exe extension.

2. Unzip the file. One of the files that will appear should be a .tar file. Use this file in the steps below.

3. Copy or FTP the .tar file to your UNIX or Linux platform and place it into the Pitney Bowes product $PBDIR/c1p/lib directory. If you FTP, be sure to use binary mode.

Make sure you back up or save your $PBDIR/c1p/lib directory before going to the next step.

4. Un-tar the file into the $PBDIR/c1p/lib area using the following command:

tar -xvf c1pXnn.download.tar

where Xnn is the update designator (with X being the update type and nn being the update number). The person performing this step must have write privileges on all files in the current directory or the tar command will fail.

Two new files should now be available:

• c1pXnn.tar

• install

where Xnn is the update designator.

5. Run the install script ($PBDIR/c1p/lib/install) to install the product updates from the c1pPXnn.tar file. Do not manually un-tar the c1pXnn.tar file unless you are directed to do so by Pitney Bowes Technical Support.

The install script must be executed from the lib subdirectory of the product being updated. The tar file must also be present in this area.

A new file (for example, aix_O01rls, hpx_S02rls) will be placed under the $PBDIR/c1p/lib to verify the patch installation.

6. Run the IVP/sample job to verify a successful installation of the product update.

Special Considerations

Runtime Changes

The runtime that is installed with the product is no longer placed in a separate directory and shared by all installed Pitney Bowes products. Instead, each product has its own version of the runtime and it is placed in the product directory area. The runtime directory name is "rts" and can be found along with the bin, data and lib directories within the product installed root directory. With the inclusion of the runtime with the product there will be reduced compatibility issues when a product is updated with a new runtime version. In addition, the placing of the runtime with the product facilitates the process of supporting both 32-bit and 64-bit products on the same target machine.


Special Notes for Uninstalling Products

Performance Considerations

Please review the following performance considerations.

NFS Mounted File Systems

Network File Systems (NFS) are mounted file systems that are used on most UNIX/Linux systems today. However, due to the performance issues concerning NFS mounts, we recommend that all files used in the production process of Pitney Bowes products be located on the target machine’s local file system. Although some Pitney Bowes products may run efficiently on NFS mounted files systems, performance and record locking issues can cause processing bottlenecks that cannot be tuned or modified for performance gains. If you choose to use NFS mounted file systems for your production processes, Pitney Bowes cannot assist in product efficiency or performance metrics.

Sorted Raw Input File

If possible, all raw data input files into Pitney Bowes products, especially files with address information, should be pre-sorted on specific fields that your process uses for matching, merging, and duplicate record elimination. Unsorted raw data input files require more processing time due to normal sequential file batch processing and caching techniques. Sorted raw data files benefit from these caching techniques. If you need more information on sorting, please contact Pitney Bowes Technical Support for assistance.

Temporary Directories (/tmp)

Pitney Bowes products use temporary directories for internal sorts and for record caching techniques. As noted above in the NFS section, if your temporary directory (typically /tmp) is located on an NFS mount for space reasons, please be aware of poor performance consequences. We recommend that your temp space be allocated on the local file system.

You can modify your temp directory on a product by product basis by changing the TMPDIR environment variable located in the setup script in the product bin subdirectory.

Special Notes for Uninstalling Products

Anyone who un-installs the software MUST have proper permissions to do so, or the uninstall will not complete successfully.

Un-install scripts are included with your product in the /opt/pitneybowes/etc location. You can select any product from the list of available products.

It is important to note that running this script removes product files and ALL files within the product’s directory structure such as parameter files, input files, and output files. For this reason, it is a good idea to have a current backup before you uninstall your product.

Use the following steps to un-install your software:

1. Create a backup before uninstalling the product. This ensures that any user-created content is not lost.

2. Change the current directory to the /opt/pitneybowes/etc directory.

3. Issue ./uninstall from the command line.

4. Follow the on-screen prompts to remove the desired product.


Chapter 2: Installing on UNIX/LinuxIf You Need More Help





The Technical Support Hot line number for customers in the United States and Canada is 800-367-6950. You can also obtain product information and updates from http://www.g1.com/support.





3
Installing on z/OS
In this chapter:

Before You Begin the z/OS Installation . . . . . . . . . . . . . . . . . . . . .30 Installing from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Installing from Internet Download . . . . . . . . . . . . . . . . . . . . . . . . .34 Installing CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Installing Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 The Next Step - Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Before You Begin the z/OS Installation

Before You Begin the z/OS Installation

Chapter 3 provides instructions for installing CODE-1 Plus on a z/OS platform. This chapter also includes information for installing product updates. The CODE-1 Plus product and database releases are distributed via the Pitney Bowes Internet site or on media. Please refer to the appropriate section for instructions on installing your new product release or product update. The individual installing CODE-1 Plus must

• Have authority or permission to delete, replace, and allocate libraries and files

• Have authority or permission to submit jobs

• Know the site file/member naming conventions

• Know how to FTP files to the mainframe (for Internet installations)

• Be familiar with CICS maintenance (if performing a CICS installation)

• Download the product documentation and release notes from http://www.g1.com/support







• ZIP + 4 Code





The SuiteLink Database corrects secondary address information for U.S. business addresses whose secondary address information could not be validated.





Chapter 3: Installing on z/OSBefore You Begin the z/OS Installation

Contents of the Installation Media

If installing from media, you have received 3490e tape cartridges containing the software application and database(s). You can obtain a listing of the tape file contents by printing the first (physical) file on the installation/software tape. This file has 80-byte records and a block size of 8000. Your installation/software tape contains files that either assist in the installation process or load onto your system during the installation process. These files may include:

• CONTENTS - Table of Contents/Copyright Information

• INSTALIB - Installation library; a description of each member in this library is in the $$READIN member

• OBJCMVS - Object modules that are used to build the load modules for the software applications

• LNKCMVS - Load library for running the software application; may include CICS modules

• NAMEADDR - Input name/address file for the Installation Verification Procedure (IVP)

• LICMGTKY - License Management temporary key

• All files necessary to build your product’s database or reference file

• Other optional product-specific files

If Your Product Has License Management...

The Pitney Bowes License Management technology prohibits overwriting of the Pitney Bowes License File (G1LICEN). If you overwrite the License File, your product ceases to operate. Please carefully read the following upgrade procedures to ensure proper installation of your license-managed product.

WARNING! Do NOT delete or modify your production License File!











Installing from Media

Installation to a Production System - If you install your Pitney Bowes product directly onto a production system, the installation routines will automatically account for an existing License File, and the product will operate as expected.

Copy From Test System to Production System - If you copy the product from a test system onto a production system, it is vital that you DO NOT COPY THE LICENSE FILE from the test environment as part of the upgrade process. You must not modify the production License File (G1LICEN) during the upgrade process. If you overwrite the License File, your Pitney Bowes product will cease to operate.

If license management is not yet installed in your production environment, you must obtain a permanent license key from Pitney Bowes and perform installation of the license file. For details, see the Pitney Bowes License Management Guide available from the web site at www.g1.com/support.


To install CODE-1 Plus from tape media, follow these steps.

1. Unload the Installation JCL.

Create a job stream (IEBCOPY) similar to the one below to unload the installation library. Edit as needed for your site requirements. Variables that you will supply appear in lowercase, bold type. Add your site-defined jobcard.

//jobcard

//*//* UNLOAD <PRODUCT NAME> JCL LIBRARY.

//*

//LOAD EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*

//INDD DD DSN=INSTALIB,DISP=OLD,

// UNIT=device,VOL=SER=tvolser,LABEL=(2,NL),// DCB=BLKSIZE=27920

//OUTDD DD DSN=yourhlq.INSTALL.JCL,DISP=(,CATLG),

// DCB=(LRECL=80,BLKSIZE=27920,RECFM=FB,DSORG=PO),// SPACE=(CYL,(5,1,20)),UNIT=SYSDA

//SYSUT3 DD UNIT=DISK,SPACE=(TRK,(10))

//SYSUT4 DD UNIT=DISK,SPACE=(TRK,(10))//SYSIN DD *

COPY OUTDD=OUTDD

INDD=INDD/*

//

2. Run the Install Job (UNLOAD)

After you unload the installation library, you are ready to customize the JCL variables and submit the job to install the software. The installation JCL is a multi-step process that:

• Unloads the application object modules

• Unloads the application load modules

• Unloads the Installation Verification Procedure (IVP) name/address file

• Unloads any optional database files

• Defines and loads a Temporary License File and associated product-enabling key, if applicable

Make a backup copy of the original installation library before you make any modifications. Alternatively, save the edited members under another name and cancel your edits to the unloaded member.



Chapter 3: Installing on z/OSInstalling from Media

Follow the steps below to run the install job:

a. Modify variables in the UNLOAD JCL, as needed.

Once you make a backup copy, edit the installation JCL skeleton by replacing the lower-cased variables to suit your standards. The variable names that you replace are unique, and therefore, you can use ISPF’s “change all” function. Add your site-defined jobcard. Comments within the JCL describe this process.

This job deletes the specifically-named files and libraries that you specify prior to unloading the tape. Ensure that no other files or libraries are using these names. Also, set your ISPF Edit profile to uppercase using the “caps on” command.

b. Submit the job and check the return codes.

The installation JCL copies from tape to disk the entire application’s software and IVP file. Check the output from the job to ensure that all steps completed. If your product requires license management, various other steps execute to provide a load of the license management file.

3. Load the License Management Key (if applicable)

Follow the instructions in ‘License Management” on page 65, as applicable.

4. Install the Database (if applicable)

CODE-1 Plus requires databases. Please see the section ‘CODE-1 Plus Databases” on page 30 for details. Databases are provided in one of three ways: on tape, on DVD, or via the Internet. If you have downloaded your database from the Internet, please see the section entitled ‘Installing Downloaded Databases” on page 35.

Loading a Database from Tape

The C1PDBINS JCL creates the database. There are one or more database files. To load the database:

a. Locate DASD space to accommodate the product database.

b. Edit the C1PDBINS JCL member in the INSTALIB JCL.

c. Submit the JCL for execution. Check the output of the job to ensure that all steps completed with a zero return code.

d. Review the Database Summary output for your particular product.

Loading a Database from DVD

a. Store the files to a drive on your LAN.

b. Log onto your mainframe and locate the product's installation library.

c. Locate and customize the C1PALOCF member to suit your site standards. Then submit the member. The C1PALOCF member will allocate temporary/sequential file(s) on the mainframe, then upload the downloaded file(s) to the mainframe.

d. Locate and customize the C1PDBIND member to suit your site standards. Then submit the member. The C1PDBIND member will create the appropriate VSAM database file(s) from the sequential files uploaded in the prior step and will then remove the flat files from the mainframe.

5. Run the Installation Verification Procedure (IVP)

Run the IVPFILE JCL member to ensure that the batch load modules function properly. The IVP job “exercises” a large number of programs in the system, so you can be sure that the verification process is comprehensive. Be sure to add the LE run-time library reference to your steplib concatenation.

6. Configure/Test CICS (if applicable)

If your product has a CICS component that you wish to install, please go to ‘Installing CICS” on page 36. Instructions on configuring CICS are provided in ‘Installing CICS” on page 36. CICS must be configured as part of the installation process if you wish to use the Interactive System.


Installing from Internet Download


This section provides instructions for installing CODE-1 Plus on a z/OS platform from internet download.

Contents of the .exe File

Pitney Bowes delivers Internet software updates in compressed format as a self-extracting file. This file includes:

• IDSINSTL.JCL, which is used to upload and install your new software release.

• Installation JCL and the LE Runtime Option Macro (CEEUOPT) in effect for this product. The $$READIN member will contain an index of all the members in the install library.

• Load file containing load modules (available for only some products. You can check your download for a file named pppCMVS.LOAD).

• Load PDSE file containing PDSE (Partitioned DataSet Extended) load modules (available for only some products. You can check your download for a file named pppCMVS.LOAD.PDSE).

• Object file(s) containing the software (*.OBJ files).

• Input data file for the installation verification procedure.

• (Optional) SAMPLE library containing sample JCL, programs, copybooks, and text files. The $$READSM member will contain an index of all the members in the optional sample library.

• A Temporary License Management Key (if applicable).

• Other files that may be pertinent to your release (*.DAT files).

The IDSINSTL JCL member is a complete job that will perform all functions required to upload a specific product’s libraries and support files to the mainframe. If your site does not use FTP as the preferred file transfer protocol, substitute the FTP step with the utility used at your site and the job will continue to be operational.

Installing Software Files

Complete the following steps to install the software files downloaded from the Pitney Bowes website at www.g1.com/support. The following steps assume you have already unzipped the .exe or .zip file to extract the installation files.

1. FTP the IDSINSTL JCL.

Follow the steps below to FTP the IDSINSTL JCL to the mainframe:

a. Use the following file transfer settings:

– EBCDIC - Translate to EBCDIC; the file is sent in ASCII format

– NOCRLF - No Carriage Return/Line Feed

– RECFM - FB (fixed-block)

– BLKSIZE - 1600 or the blocksize of the receiving library

– LRECL - 80

b. With your company’s file transfer protocol set to ASCII, upload IDSINSTL JCL to the mainframe.

2. Customize the IDSINSTL JCL.

Customize the IDSINSTL as needed for your site requirements. Variables that you supply appear in lowercase, bold type (see the Variable Replacement Table in the IDSINSTL JCL).


www.g1.com/support

www.g1.com/support

Chapter 3: Installing on z/OSInstalling from Internet Download

3. Run the IDSINSTL Job.

To run the install job, submit the job and check the return codes. The job should complete with zero return codes.

Running the IDSINSTL install deletes all files associated with the installation of the product so it is important to create backups first.

4. Load the License Management Key (if applicable).

5. Load the Required Product Database Files (if any)

At this point, you will load your new or updated database file(s). Please see Installing Downloaded Databases for more information.

6. Run the Installation Verification Procedure (IVP).

Run the IVPFILE JCL member to ensure that the batch load modules function properly. The IVP job “exercises” a large number of programs in the system, so you can be sure that the verification process is comprehensive. Be sure to add the LE run time library reference to your steplib concatenation.

7. Configure/Test CICS (if applicable)

If your product has a CICS component to install, please refer to ‘Configuring CICS” on page 36. CICS must be configured as part of the installation process if you wish to use the Interactive System.

Please see ‘Installing Downloaded Databases” on page 35 for instructions for loading a database downloaded from the Pitney Bowes web site.

Installing Downloaded Databases

Pitney Bowes provides database images for downloading from the internet at http://www.g1.com/support. Login to the Support site. If you do not have a user ID or password, contact Technical Support. To install the databases, follow these steps.

1. Locate the file(s) you wish to download and initiate the download.

Once the download completes, the file(s) will be on your LAN in the location you specified.

2. Log onto your mainframe and locate the product's installation library.

3. Locate and customize the C1PALOCF member to suit your site standards. Then submit the member. The C1PALOCF member will allocate temporary/sequential file(s) on the mainframe, then upload the downloaded file(s) to the mainframe.

4. Locate and customize the C1PDBIND member to suit your site standards. Then submit the member. The C1PDBIND member creates the appropriate VSAM database file(s) from the sequential files uploaded in the prior step, then removes the flat files from the mainframe.




Installing CICS

Installing CICS

This section describes the CICS installation process for CODE-1 Plus.

Configuring CICS

CODE-1 Plus requires you to configure CICS as part of the installation process if you wish to use the Interactive System. These instructions assume that you are familiar with modifying the CICS environment. If you are not, please ask a CICS systems programmer for assistance.

For a list of supported CICS versions, see the “Supported Platforms” document available at http://www.g1.com/support.

Interactive components are not compatible with any prior releases of your Pitney Bowes product and cannot co-exist in the same CICS region or load library with prior releases.

The execution load library contains the load modules required for the interactive system. The install library (yourhlq.INSTALL.JCL) contains the JCL for updating the CSD entries.

To install the interactive system in CICS, follow these steps:

1. Install the Resource Definitions.

a. Modify the C1PCSD member according to the instructions within the member.

b. Submit the job and check the output.

2. Install the Customization File (optional).

The following members in the install library assist you in installing the customization file G1xxFDF. Follow the instructions within the members to install this new file.

• DEFCUSTM—Contains the JCL to define and initialize the file.

• CUSTMUTL—Contains the JCL to repair, re-initialize, and display the password.

3. Define the Product Loadlib to CICS.

Add the load library and PDSE load library unloaded above to the DFHRPL concatenation. On the next startup of that CICS region, the interactive system should be available.

4. Execute the Interactive System.

You are ready to execute the interactive system. From a blank CICS screen, enter the transaction name. Please refer to your User's Guide for more information about running the software.

Be sure to make copies of your programs, or recycle your CICS region to pick up the fixes and run the driver transaction to test the new programs.


To install product updates (also called “patches”), downloaded from the Pitney Bowes Web site at www.g1.com/support, follow these steps.

1. Configure Your File Transfer Utility.

Before uploading the JCL from the PC to the mainframe, use the following settings to configure your installation-approved file transfer utility.

• ASCII - file is provided in ASCII format

• CRLF - Carriage Return/Line Feed

• RECFM - FB (fixed-block)

• BLKSIZE - 80

• LRECL - 80


www.g1.com/support

www.g1.com/support


Chapter 3: Installing on z/OSThe Next Step - Running Jobs

2. Upload the MVSPATCH JCL member.

Use your site's file transfer utility to upload the MVS PRODUCT UPDATE JCL member, MVSPATCH, to a location on your mainframe where it can be edited.

3. Determine whether MVSPATCH is applicable.

Review the MVSPATCH JCL member and determine if you need to substitute or remove the FTP step from the job. If you are substituting another utility, or removing the step and using an interactive file transfer, be sure to use the following settings.

File Transfer Settings for the .OBJ File:

• BINARY - Binary transfer (the file is provided in EBCDIC format)

• NOCRLF - No Carriage Return/Line Feed


• BLKSIZE - 1600

• LRECL - 80

4. Customize the MVSPATCH JCL member.

Similar to all Pitney Bowes JCL, the MVSPATCH member contains a list of variables, enclosed in a “flower box,” at the start of the member. Review the variable requirements in the JCL member and follow the directions contained within.

5. Run the MVSPATCH JCL member.

After you have performed the customization, submit the job. The job should complete with zero return codes.

6. Test the product update.

If the product update was for the batch component of a Pitney Bowes product, run the IVPFILE provided with the original software tape (or any existing job at your site) to ensure that the batch load modules function properly. The IVPFILE job “exercises” a large number of programs in the system, so you can be sure that the verification process is comprehensive.

If the product update was for the CICS component of a Pitney Bowes product, issue the “CEMT S PROGRAM (programid) NEW” command in the CICS region, or recycle the CICS partition. Then issue the startup transaction-id for the product and verify that the changes were applied.

We recommend that you run this procedure before going on to the next step.

If you call Pitney Bowes programs from your applications statically, we suggest that you re-compile your programs at this point to pick up the new modules.

7. Implement the product update.

After you test the new TEST load library and are satisfied with the results, copy the TEST libraries into production.

You may use IEBCOPY or ISPF (or any other valid utility) to copy the TEST load and TEST object libraries into your respective production libraries. It is important that you use the replace option with either method.

The Next Step - Running Jobs

You have successfully installed the software and database files. You’ve run the IVP job and looked at the execution log to ensure that the job ran to completion. Please refer to your CODE-1 Plus User's Guide for instructions on setting up and running your first job.










4
Installing on IMS
In this chapter:

Before You Begin the IMS Installation . . . . . . . . . . . . . . . . . . . . . .40 Installing from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Installing from the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Installing Downloaded Databases . . . . . . . . . . . . . . . . . . . . . . . . .46 Installing Product Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 The Next Step — Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . .48 If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Before You Begin the IMS Installation

Before You Begin the IMS Installation

Chapter 4 provides instructions for installing CODE-1 Plus on an IMS platform. This chapter also includes information for installing product updates. The CODE-1 Plus product and database releases are distributed via the Pitney Bowes Internet site or on media. Please refer to the appropriate section for instructions on installing your new product release or product update. The individual installing CODE-1 Plus must:

• Have the authority or permission to delete, replace, and allocate libraries and files

• Have the authority or permission to submit jobs

• Know the site file/member naming conventions

• Know how to FTP files to the mainframe (for Internet installs)

• Download the product documentation and release notes from http://www.g1.com/support






• ZIP + 4 Code
















Chapter 4: Installing on IMSBefore You Begin the IMS Installation

Contents of the Installation Media

If you are installing from media, you have received 3480 tape cartridges containing the software application and database(s). You can obtain a listing of the tape file contents by printing the first (physical) file on the installation/software tape. This file has 80-byte records and a block size of 8000.

Your installation/software tape contains files that either assist in the installation process or load onto your system during the installation process. These files can include:

• CONTENTS - Table of contents/copyright information

• INSTALIB - Installation library; a description of each member in this library is in the $$READIN member

• OBJCMVS - Object modules that are used to build the link modules

• LNKCMVS - Load library for running the software application; may include CICS modules

• MFS - Message Format Service Source

• PSB - Program Specification Blocks Source

• DBD - Database Definition Source

• NAMEADDR - Input name/address file for the Installation Verification Procedure (IVP)

• LICMGTKY - License Management temporary key

• Other product-specific files

Your installation/database tape(s) contains all the files necessary to build your database or reference file.

If Your Product Has License Management. . .

Pitney Bowes License Management technology prohibits overwriting of the License File (G1LICEN). If you overwrite the License File, your product ceases to operate. Please carefully read the following upgrade procedures to ensure proper installation of your license-managed product.

Do NOT delete or change your production License File!

• Installation to a Production System — If you install your product directly onto a production system, the installation routines will automatically account for an existing License File, and the product will operate as expected.






• Copy from Test System to Production System — If you copy the product from a test system onto a production system, it is vital that you DO NOT COPY THE LICENSE FILE from the test environment as part of the upgrade process. You must not modify the production License File (G1LICEN) during the upgrade process. If you overwrite the License File, your product will cease to operate.

If license management is not yet installed in your production environment, you must obtain a permanent license key from Pitney Bowes, and perform installation of the license file.


To install the software and database files from media, follow these steps. Some products have an interactive component. Steps 3 and 4 of this procedure address the installation of the IMS interactive component.

1. Unload the installation JCL.

Create a job stream (IEBCOPY) similar to the one below to unload the installation library. Edit as needed for your site’s requirements. Variables that you will supply appear in lowercase, bold type. Add your site-defined job card.

//jobcard//*//* UNLOAD <PRODUCT NAME> JCL LIBRARY.//*//LOAD EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//INDD DD DSN=INSTALIB,DISP=OLD,// UNIT=device,VOL=SER=tvolser,LABEL=(2,NL),// DCB=BLKSIZE=27920//OUTDD DD DSN=yourhlq.INSTALL.JCL,DISP=(,CATLG),// DCB=(LRECL=80,BLKSIZE=27920,RECFM=FB,DSORG=PO),// SPACE=(CYL,(5,1,20)),UNIT=SYSDA//SYSUT3 DD UNIT=DISK,SPACE=(TRK,(10))//SYSUT4 DD UNIT=DISK,SPACE=(TRK,(10))//SYSIN DD * COPY OUTDD=OUTDD INDD=INDD

/*//

2. Run the installation job

After you unload the installation library, you are ready to customize the JCL variables and submit the job to install the software. The installation JCL is a multi-step process that:

• Unloads the application object modules

• Unloads the application load modules

• Unloads the Installation Verification Procedure (IVP) name/address file

• Unloads the necessary PSBs, DBDs, and MFSs associated with this IMS product

• Unloads any optional database files

• Defines and loads a Temporary License Management File and associated product-enabling key, if applicable.

Make a backup copy of the original installation library before you make any modifications. Alternatively, save the edited members under another name and cancel your edits to the unloaded member.


Chapter 4: Installing on IMSInstalling from Media

Follow the steps below to run the install job:

a. Modify variables in the UNLOAD JCL, as needed.

After making a backup copy, edit the installation JCL skeleton by replacing the lower-cased variables to suit your standards. The variable names that you replace are unique, and therefore, you can use the ISPF “change all” function. Add your site-defined job card. Comments within the JCL describe this process.

This job deletes the specifically-named files and libraries that you specify prior to unloading the tape. Ensure that no other files or libraries are using these names.

Also, set your ISPF Edit profile to uppercase using the “caps on” command.

b. Submit the job and check the return codes.

The installation JCL copies from tape to disk the entire application’s software and IVP file. Check the output from the job to ensure that all steps completed with a zero return code.

3. Incorporate transaction and database definitions.

Sample transaction definitions and database definitions are contained in the member DYNAMC1P, which is in the installation library that was copied from the installation software tape in Step 1. Using these as a guide, modify them to fit your installation’s standards and incorporate them into your IMS SYSGEN and/or IMS region startup procedures.

4. Perform PSB, DBD, and ACB Gens.

a. After you unzip the source members (MFS, PSB, and DBD) from the *.exe or .zip file, upload the members to the library of your choice and incorporate them into your IMS region’s SYSGEN.

b. The IDSINSTL job will unload members into a library of your choice and incorporate them into your IMS region’s SYSGEN table.

c. The DYNAMC1P member in the Install Library contains sample database definitions to suit your installation standards and incorporate them into your IMS SYSGEN and/or IMS regions start-up procedure.

A limited amount of modifications can be made to CODE-1 Plus IMS in order to adapt it to your site. It is possible to alter the Transaction Codes used by the product, and it is possible to change the maximum message size to be less than 1,000 bytes.

If your installation requires application specific transaction IDs different from those provided, you must modify the WS-TRAN-TBL working storage area in the G1CPTRAN program, starting in position 5 of the value literal, to agree with the transaction IDs that you want to use. The sequence of the default transaction IDs in the WS-TRAN-TBL should not be modified. In addition, you must change the first MFLD of the input description (MID) to agree with your installation assigned transaction IDs before you assemble the MFS file (#7). (Except for G1CP00, which does not have a transaction ID associated with it.)

Library Name Description

yourhlq.prdct.MFSSRC Message Format Service Source

yourhlq.prdct.PSBSRC Program Specification Blocks Source

yourhlq.prdct.DBDSRC Database Definition Source



CODE-1 Plus allows you to restrict the length of the messages it uses to a maximum of 1,000 bytes. If you choose to do this, please be aware that this option requires approximately twice as many ISRT calls as not restricting the message length. To limit the message length, perform the following steps.

1. Edit the MFS source code members and remove the asterisk, which causes the SEG statements in the output to be treated as comments. See file 7.

2. Edit the COBOL program G1CPTRAN, and change the initial value for WS-MAX-MSG-SIZE-SW to “Y.” See file 10.

3. Generate the MFS panels.

4. Compile and link G1CPTRAN as a non-IMS program. Be sure to use above the line compile and link parameters or below the line parameters, whichever match to the version that has been installed.

5. Load the license management key (if applicable).

Follow the instructions in your User’s Guide or the License Management Guide. If applicable, the Access Key that appears on your packing slip is good for 45 days from the shipping date. The Access Key that appears on the Download Software screen from the Pitney Bowes web site is good for only ten days. If your Access Key expires, you will need to return to the web site to get a new one (in the My Products section) or obtain your permanent license file.

The LMDBIND job must be run to complete the installation of License Management.

6. Install the database (if applicable).

CODE-1 Plus requires databases. Please see "CODE-1 Plus Databases” on page 40 for more information on the CODE-1 Plus databases. Databases are provided on tape or via the Internet. If you have downloaded your database from the Internet, please see the section "Installing Downloaded Databases” on page 46.

The C1PDBINS JCL creates the database. There are one or more database files. To load the database:

a. Locate DASD space to accommodate the product database.

b. Edit the C1PDBINS JCL member in the INSTALIB JCL.

c. Submit the JCL for execution. Check the output of the job to ensure that all steps completed with a zero return code.

d. Review the Database Summary output for your particular product.


Run the IVPFILE JCL member to ensure that the batch load modules function properly. The IVP job “exercises” a large number of programs in the system, so you can be sure that the verification process is comprehensive. Be sure to add the LE run time library reference to your steplib concatenation.


Chapter 4: Installing on IMSInstalling from the Internet

Installing from the Internet

These steps assume you have already downloaded the *.zip or *.exe file and unzipped it to extract the files.

Contents of the Downloaded File

Internet software updates are in a compressed format as a self-extracting .zip or .exe files. This file includes:

• IDSINSTL.JCL, which is used to upload and install your new software release.

• Installation JCL and the LE Runtime Option Macro in effect for this product. The $$READIN member will contain an index of all the members in the install library.

• Load the file containing load modules (available for only some products. You can check your download for a file named pppCMS.LOAD).

• Object file(s) containing the software (*.OBJ files).

• MFS — Message Format Service Source.

• PSB — Program Specification Blocks Source.

• DBD — Database Definition Source.

• Input data file for the installation verification procedure.

• (Optional) SAMPLE library containing sample JCL, programs, copybooks, and text files. The $$READSM member will contain an index of all the members in the optional sample library.

• A temporary license management key (if applicable).

• Other files that may be pertinent to your release (*.DAT files).

The IDSINSTL JCL member is a complete job that will perform all of the functions required to upload a specific product’s libraries and support files to the mainframe. If your site does not utilize FTP as the preferred file transfer protocol, then substitute the FTP step with the utility used at your site and the job will continue to be operational.

Installing Software Files

To install the software files downloaded from www.g1.com/support, follow these steps. Steps 5 and 6 of this procedure address installation of the IMS interactive component.

1. Follow the steps below to FTP the IDSINSTL JCL to the mainframe:

a. Use the following file transfer settings:

– EBCDIC — Translate to EBCDIC; the file is sent in ASCII format.

– NOCRLF — No Carriage Return/Line Feed

– RECFM — FB (fixed-block)

– BLKSIZE — 1600 or the block size of the receiving library)

– LRECL — 80

b. With your company’s file transfer protocol set to ASCII, upload IDSINSTL JCL to the mainframe.

2. Customize the IDSINSTL JCL as needed for your site requirements. Variables that you will supply appear in lowercase, bold type.

3. Run the Install Job.

a. Modify variables in the IDSINSTL JCL as needed.




b. Submit the job and check the return codes. The job should complete with zero return codes.

Running the IDSINSTL JCL deletes your existing object library. You need to create a backup first. The backup library is the location where the install objects are uploaded.

4. Incorporate transaction and database definitions.

Sample transaction definitions and database definitions are contained in the member DYNAM in the installation library. Using these as a guide, modify them to fit your installation standards and incorporate them into your IMS SYSGEN and/or IMS region startup procedures.

5. Perform PSB, DBD and ACB Gens:

a. After you unzip the source members (MFS, PSB, and DBD) from the .exe file, upload the members to the library of your choice and incorporate them into your IMS region’s SYSGEN.

b. The IDSINSTL job will unload members into a library of your choice and incorporate the members into your IMS region’s SYSGEN table.

c. The DYNAMC1P member in the Install Library contains sample database definitions to suit your installation standards and incorporate them into your IMS SYSGEN and/or IMS regions start-up procedure.

6. Load the license management key (if applicable).

Follow the instructions in either your User’s Guide or the License Management Guide. If applicable, the Access Key that appears on your packing slip is good for 45 days from the shipping date. The Access Key that appears on the Download Software screen from the support web site is good for only ten days. If your Access Key expires, you will need to return to the web site to get a new one (in the My Products section) or obtain your permanent license file.

The LMDBIND job must be run to complete the installation of License Management.


Run the IVPFILE JCL member to ensure that the batch load modules function properly. The IVP job “exercises” a large number of programs in the system, so you can be sure that the verification process is comprehensive. Be sure to add the LE run-time library reference to your steplib concatenation.


Pitney Bowes provides database images on the Internet for some of the products that require a database (see "CODE-1 Plus Databases” on page 40 for a listing of those products). Databases for downloading from the web site are located at www.g1.com/support. Check the web site to see if your product’s database is available as a download. If so, login to the Support site (if you do not have a user ID or password, contact Technical Support) and complete the steps below.

1. Locate the file(s) you wish to download and initiate the download.

Once the download completes, the file(s) will be on your LAN in the location you specified.

2. Log onto your mainframe and locate the product's installation library.

Library Name Description

yourhlq.prdct.MFSSRC Message Format Service Source



Chapter 4: Installing on IMSInstalling Product Updates

3. Locate and customize the C1PALOCF member to suit your site standards. Then submit the member. The C1PALOCF member will allocate temporary/sequential file(s) on the mainframe, then upload the downloaded file(s) to the mainframe.

4. Locate and customize the C1PDBIND member to suit your site standards. Then submit the member. The C1PDBIND member creates the appropriate VSAM database file(s) from the sequential files uploaded in the prior step and will then remove the flat files from the mainframe.


To install product updates (also called “patches”), downloaded from the Pitney Bowes Web site at http://www.g1.com/support, follow these steps.

1. Configure your file transfer utility.

Before uploading the JCL from the PC to the mainframe, use the following settings to configure your installation-approved file transfer utility.

• ASCII - file is provided in ASCII format

• CRLF - Carriage Return/Line Feed


• BLKSIZE - 80

• LRECL - 80

2. Upload IMSPATCH JCL member.

Use your site's file transfer utility to upload the IMS PRODUCT UPDATE JCL member, IMSPATCH, to a location on your mainframe where it can be edited.

3. Determine if IMSPATCH is suitable for your site.

Review the IMSPATCH JCL member to determine if you need to substitute or remove the FTP step from the job. If you are substituting another utility, or removing the step and using an interactive file transfer, be sure to use the following file transfer settings for the .OBJ file:

• BINARY - Binary transfer (the file is provided in EBCDIC format)

• NOCRLF - No Carriage Return/Line Feed


• BLKSIZE - 1600

• LRECL - 80

4. Customize the IMSPATCH JCL member.

The IMSPATCH member contains a list of variables, enclosed in a “flower box,” at the start of the member. Review the variable requirements in the JCL member and follow the directions contained within.

5. Run the IMSPATCH JCL member.

After you perform the customization, submit the job. The job should complete with zero return codes.



The Next Step — Running Jobs

6. Test the product update.

If the product update was for the batch component of any Pitney Bowes product, run the IVPFILE provided with the original software tape (or any existing job at your site) to ensure that the batch load modules function properly. The IVPFILE job “exercises” a large number of programs in the system, so you can be sure that the verification process is comprehensive.

We highly recommend that you run this procedure before going on to the next step.

If you call Pitney Bowes programs from your applications statically, we suggest that you re-compile your programs at this point to pick up the new modules.

7. Implement the Product Update

After you test the new TEST load library and are satisfied with the results, you may copy the TEST libraries into production.

You may use IECOPY or ISPF (or any other valid utility) to copy the TEST load and TEST object libraries into your respective production libraries. It is important that you use the replace option with either method.

The Next Step — Running Jobs

You have successfully installed the software and loaded any database files. The installation verification procedure (IVP) supplied by Pitney Bowes is a sample job. You can use this as a template for setting up your own jobs. Please refer to your CODE-1 Plus User's Guide for instructions on setting up and running your first job.








5
Installing on IBM i
In this chapter...

Before You Begin the IBM i Installation . . . . . . . . . . . . . . . . . . . . .50 Installing from Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Installing from Internet Download . . . . . . . . . . . . . . . . . . . . . . . . .51 Installing the Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Installing a Product Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Installing Databases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Running the Installation Verification Procedure (IVP) . . . . . . . . .63 Additional Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 If You Need More Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Before You Begin the IBM i Installation

Before You Begin the IBM i Installation

This chapter provides instructions for installing CODE-1 Plus on the IBM i platform. This chapter also includes information for installing product updates. The CODE-1 Plus product and database releases are distributed via the Pitney Bowes Internet site or on media. Installation media is only available from the Pitney Bowes estore. Please log in to the Pitney Bowes estore for media purchasing and shipping. The requirements for installing CODE-1 Plus in an IBM i environment are:

• Working knowledge of the IBM i operating system and commands, as well as knowledge of IBM i file structure.

• Downloading the product documentation and release notes from http://www.g1.com/support.

Will Any Objects Be Changed?

Product installation creates or modifies the objects listed below.

Do not create or clear the default libraries.

License Management

License Management technology prohibits overwriting of the License File (G1LICEN in library G1C1PGMS). If you overwrite the License File, your product ceases to operate. Please carefully read the following upgrade procedures to ensure proper installation of your license-managed product.

Do NOT delete or modify your production License File!

• Installation to a Production System - If you install your product in a production system, the installation routines will automatically account for an existing License File, and the product will operate as expected.

• Copy from Test System to Production System - WE DO NOT RECOMMEND COPYING FROM A TEST TO A PRODUCTION SYSTEM.

Object Description

GROUP1USER User profile connected to the main Application Selection menu.

G1HELP Folder containing on-line help text for all applications.

GRP1USER System distribution directory entry, with address GRP1USER.

G1@@PGMS Library containing elementary functions used by all Pitney Bowes applications. You may change the name of this library to any other name at the time of installation. However, the library chosen may not contain any extraneous objects.

G1C1PGMS Library containing your application. You may specify a different name at installation time if you wish. However, this library may not be the same as the Function Library (above), may not be the same as the name of any other product library, and may not contain any extraneous objects.



Chapter 5: Installing on IBM iInstalling from Internet Download


Before starting the installation process, back up the functions library (G1@@PGMS) and the product library (G1C1PGMS). If for any reason the installation procedure fails, you may cancel the install, restore your previously-made backups for G1@@PGMS and G1C1PGMS or their equivalents, check for object locks or other abnormalities, and try again. If you do not have any backups, or if you have any questions, please call Technical Support.

To install the CODE-1 Plus software from an Internet download, follow these steps:

1. Download the appropriate file to a Windows-based machine. If the file is a self-extracting *.exe file, execute the file now. If the file is a *.zip file, unzip the file using an unzip utility.

2. To prepare the installation library and save file, follow these steps.

a. Create a library called G1INSTALL:CRTLIB LIB(G1INSTALL) TYPE(*PROD) TEXT('Installation Library')

b. If library G1INSTALL already exists, clear the library:CLRLIB LIB(G1INSTALL)

c. Create a save file (SAVF) for the extracted file in the G1INSTALL library:CRTSAVF FILE(G1INSTALL/G1SVINSTL)

3. FTP the extracted image file to its corresponding SAVF in the library you created. Be sure that you specify Binary when you FTP the file to your target machine.

4. Sign on to the system with your own user profile.

You do not need to be signed onto the system as QSECOFR to perform an installation. However, you must have *SECADM or *SECOFR special authority.

5. At the IBM i command line, type:

RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF)

SAVF(YourLib/G1SVINSTL)

...where YourLib is the library that contains the Save files from which you are installing. Or, if you prefer to prompt (F4) the RSTOBJ command, you should fill in the screen as shown below.

Restore Object (RSTOBJ) Type choices, press Enter. Objects . . . . . . . . . . . . > *ALL Name, generic*, *ALL + for more values Saved library . . . . . . . . . > QTEMP Name Device . . . . . . . . . . . . . > *SAVF Name, *SAVF, *MEDDFN + for more values Object types . . . . . . . . . . *ALL *ALL, *ALRTBL, *BNDDIR... + for more values Save file . . . . . . . . . . . > G1SVINSTL Name Library . . . . . . . . . . . > YourLib Name, *LIBL, *CURLIB



6. When the command completes, you should see the following message at the bottom of your screen:

n objects restored from QTEMP to QTEMP

...where n is a varying number.

7. To start the install program, type:

CALL G1UI

8. Continue the installation process in the section "Selecting the Product” on page 52.


Before starting the installation process, back up the functions library (G1@@PGMS) and the product library (G1C1PGMS). If for any reason the installation procedure fails, you may cancel the install, restore your previously-made backups for G1@@PGMS and G1C1PGMS or their equivalents, check for object locks or other abnormalities, and try again. If you do not have any backups, or if you have any questions, please call Technical Support

To install the software from a DVD, follow these steps:

1. Load the software DVD in your IBM i machine.

2. Sign onto the system with your own user profile. You do not need to be signed onto the system as QSECOFR to perform an installation. However, you must have a user class of *SECOFR and *SECADM or *SECOFR special authority.

3. At the IBM i command line, type:

LODRUN DEV(DeviceName)

...where DeviceName is the name of the DVD drive, such as “OPT01” or “OPT02.”

4. Continue the installation process in the section "Selecting the Product” on page 52.

Selecting the Product

To select the product to install on your IBM i machine, follow these steps:

1. The install source is scanned for products to install. The Product Selection screen (G1INST200) displays.

[Time] Pitney Bowes - Application Installation G1UI [Date] Product Selection G1INST200 Select the products you wish to install and press F6 to continue: 1=Select 1 *PRD @@ G1SV@@PGM PB Software Global Library 1 *PRD C1 G1SVC1PGM CODE-1 Plus 1 *HLP @@ G1SV@@HLP Global Library Help Text Folder 1 *HLP C1 G1SVC1HLP CODE-1 Plus Help Text Folder Bottom _______________________________________________________________________________ F3/12=Exit F6=Continue


Chapter 5: Installing on IBM iInstalling the Product

2. To prevent an item from being installed, remove the "1" next to item.

In order to ensure that your application version numbers display correctly we recommend always updating the Global library.

3. Press F6 to continue with the installation.

Installing the Product

This section describes the steps to complete the installation of software on your IBM i machine.

Global Library Options

1. If you have selected the “Software Global Library,” the Global Library Special Options screen (G1INST300) displays.

2. To prevent a step from being performed, remove the "1" next to the step.

3. Press F6 to continue the installation.

[Time] Pitney Bowes - Application Installation G1UI [Date] Global Library Special Options G1INST300 These steps are part of the Group 1 Global Function library installation. Select steps to be performed, press F6. 1=Select 1 Create GROUP1USER user profile 1 Change initial program to G1MM00 for GROUP1USER 1 Add GROUP1USER to System Distribution Directory

_______________________________________________________________________________ F3/12=Exit F6=Continue



Product Installation Options

The Product Installation screen (G1INST400) displays for each product you selected on the Product Selection screen (G1INST200). If the “Install to library” already exists, the “Backup library name” field displays as shown in the example below. The library name is automatically generated as “G1yymmddnn,” where yymmdd is the current date, and nn is a sequential number.

Keep track of your backup library name in case you want to restore your original library.

1. If you want to install the Installation Verification Procedure (IVP) job, select “Y” for yes.

If a warning in yellow appears on this screen, you must review the warning before you are allowed to proceed to the next screen. If an error in red appears on this screen, you must resolve the condition that caused the error before you are allowed to proceed.

2. To install the product, press F6.

3. If the Lock Library screen (G1INST401) appears, continue to the section "Locked Libraries” on page 55.

4. After all components are installed, the Installation Complete screen (G1INST999) displays.

5. Continue to the section "Completing the Installation” on page 55.

[Time] Pitney Bowes - Application Installation G1UI [Date] Product Installation G1INST400 Installation details: Installing from . . . *SAVF Product ID/Desc . . . C1 / CODE-1 Plus Version on Media. . . 04.0M00 Enter product installation parameters, press F6. Global library. . . . ZM@@PGMS Install to library. . ZMG9PGMS * Same version already installed! Backup library name . G103052817 Install IVP job?. . . Y Y,N

_______________________________________________________________________ F3=Exit F6=Continue



Locked Libraries

1. If you are overlaying an existing installation, the installer checks for locks before the installation begins. If locks are found, the Locked Library screen (G1INST401) displays.

2. You must clear the locks before you can continue the installation. Use a second session to run the command shown on the screen above to determine what jobs are holding the locks.

3. When the locks are released, return to this session, and press F6 to continue.

Completing the Installation

1. After completing the product installation, the Installation Complete screen (G1INST999) displays.

2. Press Enter to exit the install program.

3. You may review the G1UILOG spool file. The G1UILOG is a log of steps taken by the install program. Below is an example of a G1UILOG from an overlay install of the software with comments:

20xx-05-30-14.37.37 G1UI *PGM G1UI *PGM started

The initial authority check ensures that you have *SECADM or *SECOFR special authorities in your profile for performing an install.

20xx-05-30-14.37.37 G1UI *PGM Checking user's authority

The install source is examined.

20xx-05-30-14.37.47 G1UI *PGM Source=save file library QTEMP

20xx-05-30-14.37.47 G1UI *PGM Examining media20xx-05-30-14.37.47 RtvLbl Retrieving labels from save file library C1050G9PG

Next, the SCR200 screen displays.

20xx-05-30-14.37.47 G1UI *PGM Req prod to inst (SCR200)

Processing the list of products from SCR200 begins.

20xx-05-30-14.38.13 G1UI *PGM Processing install queue

[Time] Pitney Bowes - Application Installation G1UI [Date] Locked Library G1INST401 Library Name. . . . . . . . . . . G1@@PGMS This library is locked by one or more users. Clear the locks, then press F6 to continue the installation. To see which jobs are holding locks on this library, use the command: WRKOBJLCK OBJ(LibraryName) OBJTYPE(*LIB)

_______________________________________________________________________ F3/12=Exit F6=Continue



The first product installed was the global library, so SCR300 is displayed, then SCR400.

20xx-05-30-14.38.13 SRC300 Req Global options (SCR300)

20xx-05-30-14.38.43 SCR400 Req prod inst opts (SCR400)

After you press F6 on the SCR400, work begins. First, some notes appear about what we are installing, and where the backup copy is going.

20xx-05-30-14.40.46 InstPrd Starting install of @@ version XX.XM0020xx-05-30-14.40.46 InstPrd -Installing to library ZM@@PGMS

20xx-05-30-14.40.46 InstPrd -Overlaying XX.XM00

20xx-05-30-14.40.46 InstPrd -Old library will b renamed G103053001

The global library special options are performed.

20xx-05-30-14.40.46 PreInstGlb Start of Global pre-processing20xx-05-30-14.40.46 PreInstGlb Creating GROUP1USER *USRPRF

Before attempting to install, check for locks on the existing library.

20xx-05-30-14.40.47 ChkLibLck Checking for locks on library ZM@@PGMS

Install the new library.

20xx-05-30-14.40.47 InstPrdUpd Renaming ZM@@PGMS to G103053001

20xx-05-30-14.40.48 InstPrdUpd Restoring product library

20xx-05-30-14.40.48 RstPrd Restoring library for @@20xx-05-30-14.40.52 InstPrdUpd Merging objects from old library

Update the various data areas that track where products are installed, their version, and install dates.

20xx-05-30-14.40.58 InstPrdUpd Processing data areas20xx-05-30-14.40.58 PrcDtaAra Reading G0@@PG *DTAARA

20xx-05-30-14.40.58 PrcDtaAra Updating G1@@PG *DTAARA

Now the rest of the global library options can be performed.

20xx-05-30-14.40.58 PstInstGlb Start of Global post-processing20xx-05-30-14.40.58 PstInstGlb Changing GROUP1USER *USRPRF INLPGM to G1MM0020xx-05-30-14.40.58 PstInstGlb Granting GROUP1USER *USRPRF *USE authority to CHG20xx-05-30-14.40.58 PstInstGlb Adding Directory Entry for GROUP1USER *USRPRF

The C1RUNJOB and C1SBMJOB commands must be updated during an install.

20xx-05-30-14.40.59 UpdCmd Updating C1SBMJOB/C1RUNJOB *CMDs

And the global library completes.

20xx-05-30-14.40.59 InstPrd Installation of @@ has completed.

You return to screen SCR400 to get options for the product install in this example. Follow the same steps, with the exception of the global library special options.

20xx-05-30-14.40.59 SCR400 Req prod inst opts (SCR400)

20xx-05-30-14.41.29 InstPrd Starting install of G9 version 05.0M00

20xx-05-30-14.41.29 InstPrd -Installing to library ZMG9PGMS20xx-05-30-14.41.29 InstPrd -Overlaying 05.0M00

20xx-05-30-14.41.29 InstPrd -Old library will be renamed G103053002

20xx-05-30-14.41.29 InstPrd -Associated with global library ZM@@PGMS20xx-05-30-14.41.29 ChkLibLck Checking for locks on library ZMG9PGMS

20xx-05-30-14.41.29 InstPrdUpd Renaming ZMG9PGMS to G103053002

20xx-05-30-14.41.30 InstPrdUpd Restoring product library 20xx-05-30-14.41.30 RstPrd Restoring library for G9

20xx-05-30-14.41.36 InstPrdUpd Merging objects from old library

20xx-05-30-14.47.29 InstPrdUpd Processing data areas 20xx-05-30-14.47.29 PrcDtaAra Copying G1@@PG *DTAARA

20xx-05-30-14.47.29 PrcDtaAra -Deleting old G1@@PG *DTAARA

20xx-05-30-14.47.29 PrcDtaAra Reading G0G9PG *DTAARA 20xx-05-30-14.47.30 PrcDtaAra Updating G1G9PG *DTAARA



20xx-05-30-14.47.30 InstPrdUpd Forwarding from previous release

20xx-05-30-14.47.30 UpdCmd Updating C1SBMJOB/C1RUNJOB *CMDs

This product has an IVP and you are installing it:

20xx-05-30-14.47.30 InstPrd Installing IVP job

And C1 is complete.

20xx-05-30-14.47.34 InstPrd Installation of C1 has completed.

That’s it!

20xx-05-30-14.47.37 G1UI *PGM G1UI *PGM ended normally

Defining Custom Screen Headings

To change your heading when you are not installing software:

1. Sign on using your site-specific procedure.

2. Go to the Application Selection screen as you normally do, and instead of selecting a product to use, type CN (this is not a listed option).

Pitney Bowes Application Selection G1MM01 Replace with screen heading desired G1MM0001 Select one of the following:

1. MailStream Plus Presorting and Reporting System 2. List Conversion System 3. Label Printing System 4. Merge/Purge System 5. CODE-1 Plus Name/Address Coding System 6. Generalized Selection System 7. EZ-CASE Plus 8. Geographic Coding Plus 9. I/O-Jet Plus 10. Business Merge/Purge Plus 11. GeoTAX 60. Canadian /International Products

Option __



3. Press ENTER to display the Change Screen Heading screen.

4. Type your new heading in the Enter new Screen Heading field. Press ENTER to save the definition. The screen displays your previous heading and your new heading.

5. If you wish to change the heading, press F12 to return to the previous screen and repeat steps 3 and 4.

6. If you want to save the heading, press ENTER. The new heading displays at the top of your selection screen.

Pitney Bowes Application Selection G1CN00 Replace with screen heading desired G1CN0001

This function allows you to change the Screen Heading which is displayed on ALL Group 1 application screens. If this is not the function that was intended, press the F3 key now to return to the main menu.

Enter new Screen Heading: Replace with screen heading desired

Pitney Bowes Application Selection G1CN00 Replace with screen heading desired G1CN0001

This function allows you to change the Screen Heading which is displayed on ALL Group 1 application screens. If this is not the function that was intended, press the F3 key now to return to the main menu.

Enter new Screen Heading: Pitney Bowes

Previous Screen Heading: Replace with screen heading desired

Press the Enter key again to accept the changes to the Screen Heading.

F3=Exit F5=Refresh F12=PrvScrn Enter=Accept


Chapter 5: Installing on IBM iInstalling a Product Update

Installing a Product Update

To install a product update:

1. Download the product update file from the Product Updates page on the Pitney Bowes web site at http://www.g1.com/support. The downloaded file is a self-extracting zip file with a *.exe extension, or a regular *.zip file that should be unzipped.

2. If you download the *.zip file, unzip this file with a standard unzipping utility to extract the contents of the update. If you downloaded a self-extracting *.EXE, double-click the *.EXE file on a Windows-based machine to extract the contents of the file.

One of the extracted files will be an IBM i save file with an *.SVF extension. This file is the actual Product Update and must be on a PC that has file transfer capabilities (such as FTP) to your IBM i system.

If there are two files with an *.SVF extension, then this patch includes code for both the global library and the product library. You must follow additional instructions to install both sets of code. These instructions are contained in NOTES accompanying each affected step.

3. On the IBM i machine, create a save file in your own library. This is the location that will hold the file after it is transferred from the PC. For example:

CRTSAVF FILE(YourLib/YourSaveFileName)

Create two save files in your own library. This is the location that will hold the files after they are transferred from the PC. For example: CRTSAVF FILE(YourLib/SAVF@@)

CRTSAVF FILE(YourLib/SAVFC1)

4. Transfer the *.SVF file from the PC to the IBM i save file created in the previous step. Transfer the file using FTP in binary mode.

Transfer the *.SVF files from the PC to the IBM i save files created in the previous step. Transfer the files using FTP in binary mode. The name of one of the *.SVF files will end in “@@.” This is the patch for the global library: FTP it into your Lib/SAVF@@.

The other *.SVF file will end in the product code. FTP this file into your Lib/SAVFC1. FTP the remaining *.SVF file to the remaining save file on your IBM i machine.

5. Verify that the file was transferred successfully using the following command:

DSPSAVF FILE(YourLib/YourSaveFileName)

6. Restore the objects to your product library using the following command.

RSTOBJ OBJ(*ALL) SAVLIB(G1C1PGMS) DEV(*SAVF) SAVF(YourLib/YourSaveFileName) MBROPT(*ALL) ALWOBJDIF(*ALL)

where G1C1PGMS is the default product library. If your product library is not the default of G1C1PGMS, you will need to add an RSTLIB (YourProductLibrary) parameter to the above command.



Installing Databases

Restore the objects to your global install library using the following command:

RSTOBJ OBJ(*ALL) SAVLIB(G1@@PGMS) DEV(*SAVF) SAVF(YourLib/SAVF@@)

MBROPT(*ALL) ALWOBJDIF(*ALL)

...where G1@@PGMS is the default global install library.

If your global library is not the default of G1@@PGMS, you will need to add an RSTLIB (YourFunctionLibrary) parameter to the above command. Restore the objects to your product library using the following command:

RSTOBJ OBJ(*ALL) SAVLIB(G1C1PGMS) DEV(*SAVF) SAVF(YourLib/SAVFxx)

MBROPT(*ALL) ALWOBJDIF(*ALL)

...where G1C1PGMS is the default product library. If your product library is not the default of G1C1PGMS, you will need to add an RSTLIB (YourFunctionLibrary) parameter to the above command.

7. Check your job log (DSPJOBLOG) to ensure that all objects were successfully restored. You can compare the results of Step 5 with the job log to ensure that all of the intended objects transferred and installed properly.

8. You may now delete or clear the save file(s) that was created in Step 3.

If you are ready to install the product database, follow the instructions in "Installing Databases” on page 60.


This section describes the process to install database releases or updates on media or downloaded from the Internet. The instructions describe the process of installing and verifying subscription databases and reference files.

What You Need to Know...

The person who performs the installation must:

• For Internet downloads:

• Know how to transfer (FTP) files to the system.

• Have the downloaded, compressed file. Database updates are delivered as a compressed, self-extracting *.exe file.

• Be prepared to define a temporary library/file for the FTP’d file(s).

• Know the site file/member naming conventions.

File Size Requirements

Please review the "Space Requirements for Products and Databases" table on at http://www.g1.com/support. Login to Support, select Product Documentation, then Technical Product Info for specific information on your product’s masterfile size requirements. Please note that these space allocations change between releases and database file updates.



Chapter 5: Installing on IBM iInstalling Databases






• ZIP + 4 Code





The SuiteLink Database corrects secondary address information for U.S. business addresses whose secondary address information could not be validated.













Installing Downloaded (IDS) Database Files

To install downloaded (IDS) database files, follow these steps:

1. For Internet downloads (also referred to as “IDS”), download the appropriate file to a Windows-based machine and execute it, or unzip it using a standard unzip utility.

2. Sign on to your product.

3. From the Work with Jobs screen, press F20 to access the Database Functions screen. Depending on your product, select the option that indicates you are doing an Internet (or IDS) installation.

4. Specify the library name where you want the database installed in the Install to Library field and press F6 to confirm your choices. If installing over a previous version of the database, that database will be overwritten.

5. Follow the on-screen instructions to FTP database files.

Installing Database Files from Media

The database installation-from-media process is essentially the same as the database installation-from-Internet-download process. The only difference is that you must specify the device name and mount the database media when prompted. In addition, you may have options to install a reduced database, or install additional, optional databases, depending on the product you have.

1. Sign on to your product.

2. From the Work with Jobs screen, press F20 to access the Database Functions screen.

3. Select the option that indicates you want to install a new database.

4. Specify the name of the media device from which you will load the database in the Device field. OPT01 is the default.

5. Specify the name of an existing library on your system where you want to install the database.

If this is a new installation, a default library name appears. If not, the current database library name appears. You can change the library name by typing over the displayed name.

6. Load the first DVD and press F6 to confirm your choices.

7. Follow the screen prompts to complete the installation process. If you have created a new library, go to the section, “Changing the Default Library Name.”

Changing the Default Library Name

If you are installing a database into a new library, you must change the default library from the existing one to the new one for any new jobs submitted. To change the default library, follow these steps:

1. From the Work with Jobs screen, press F20 for the Database Functions screen.

2. Select the option that indicates you wish to change the default library. For example, for CODE-1 Plus, enter 8 in the Option field to change the default database library.

A Database Functions screen appears prompting you to enter the default database library name. The current library name appears as default.

3. Enter the library name you specified for the new database installation and press Enter.

4. Press F6 to confirm your choices. To exit without saving, press F3.


Chapter 5: Installing on IBM iRunning the Installation Verification Procedure (IVP)

Running the Installation Verification Procedure (IVP)

1. From the Work with Jobs screen for your product, select 16 on the @IVP@ line to submit the job.

2. When the Submit Batch Job screen appears, enter the appropriate parameters and press F6 to submit the job.

Please review your CODE-1 Plus User’s Guide for specific details on job submission options.

3. From the IBM i Main Menu, enter WRKSPLF on the command line.

4. When the Work With All Spooled Files screen appears, enter 5 next to PRNTXLG which is the execution log (the last PRNTXLG will be the most recent). The following message should appear at the end of the log:

All Functions Completed Normally

If you have problems running the IVP job, contact Technical Support at 1-800-367-6950 to speak with a CODE-1 Plus™ Technical Support Representative.

Additional Notes

• The database library may be called by any name, with the exception of product and function library names.

• As mentioned previously, you have the option of installing to a new library or overwriting your existing database. Installing into a new library will not interrupt your current jobs. You can switch to the new database by changing your default database library on the Database Functions menu. We recommend that you re-run your jobs with the most current database.

• For postal database and reference files, if you are processing mail for more than one month at a time, you will want your library name to indicate the month and year during which this postal file may be used. For example, use the name C1PMAR17 for CODE-1 Plus jobs processed during March 2017.

• Before you install any of the database files, ensure that you can allocate at least the amount indicated in the “Space Requirements for Software Products and Databases” table on the Pitney Bowes website at http://www.g1.com/support. Login to Support, select Product Documentation, then Technical Product Info. Please note that these space allocations will fluctuate between releases and database file updates. That is why we advise you to allocate “at least” these amounts.

• CODE-1 Plus gives you the option of installing a "reduced" database. A reduced database is limited to the ZIP Code ranges, states, or countries (depending on product) that you specify. Follow the prompts from the Database Functions screen to install a reduced database.











6
License Management
In this chapter...

Understanding CODE-1 Plus License Management . . . . . . . . . . .66 License Management Process for Windows . . . . . . . . . . . . . . . . .66 License Management Process for UNIX. . . . . . . . . . . . . . . . . . . . .69 License Management Process for Linux . . . . . . . . . . . . . . . . . . . .70 License Management for z/OS and IMS . . . . . . . . . . . . . . . . . . . . .72 License Management for IBM i . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Understanding CODE-1 Plus License Management

Understanding CODE-1 Plus License Management

This chapter provides license management information for each platform.

License Management Process for Windows

Finding Your System ID for Windows

You can use the following method to find your System ID information.

Windows

1. From a Command prompt, issue the following command:

ipconfig /all

2. The response is similar to:

Windows IP Configuration

Host Name . . . . . . . . . . . . : xxxxxx Primary Dns Suffix . . . . . . . : xxx.com…Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix : xxx.com Description . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit Controller #2 Physical Address. . . . . . . . : 00-1C-23-32-2F-90 Dhcp Enabled. . . . . . . . . . : Yes Autoconfiguration Enabled . . . : Yes…Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix : xxx.com Description . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection Physical Address. . . . . . . . : 00-1C-BF-CE-9C-2B Dhcp Enabled. . . . . . . . . . : Yes Autoconfiguration Enabled . . . : Yes…

3. The System ID is the last six actual characters following the Physical Address. In the example above, the two values are:

322F90CE9C2B

License Management Screen Error Messages for Windows

The following error message displays on the screen providing advance notice of the expiration of your license master file:

Master File will EXPIRE in XX days, CODE-1 Plus will STOP functioning.Contact Pitney Bowes, Inc. Customer Support.

The following error message displays on the screen when the license check fails due to the System ID not matching the System ID in the license file.

CODE-1 PLUS PROGRAM ERROR, RETURN CODE=MTSIID FOR THIS MACHINE DOES NOT MATCH LICENSE FILE

The following error message displays on the screen when the CODE-1 Plus™ license has expired.

CODE-1 PLUS PROGRAM ERROR, RETURN CODE=MTSEThe C1P license has expired


Chapter 6: License ManagementLicense Management Process for Windows

License Management Report Error Messages for Windows

CODE-1 Plus™ Execution Log File (XLG)

The error message below displays in the CODE-1 Plus™ execution log file (XLG) when the license check fails due to a System ID not being found in the CODE-1 Plus™ license file. You may need to load a new license file that includes your System ID.

CODE-1 PLUS ADDRESS MATCHING SYSTEM, RXX.XM00 EXECUTION LOG 1

C1BM00 I PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.C1BM00 I EXECUTING CODE-1 PLUS N.NN.NN.NC1BM00 I C1BM00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 ended.C1BM00 I You are attempting to run CP software on a system that is not licensed.C1BM00 I Your ID is AEC839.C1BM00 IC1BM00 I The following IDs were found in your license file:C1BM00 I (None)C1BM00 IC1BM00 I Please contact your sales executive so that your software license may beC1BM00 I appropriately modified without further interruption of service.C1BM00 IC1BM00 IC1BM00 I CODE1-Plus ABENDED DUE TO LICENSING, SEE ABOVE

The message below displays in the CODE-1 Plus™ execution log file (XLG) when the license check fails due to CODE-1 Plus™ not being licensed.


C1BMCBD I PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.C1BMCBD I EXECUTING CODE-1 PLUS N.NN.NN.NC1BMCBD I C1BMCBD STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 ENDED.C1BMCBD I THE PRODUCT YOU HAVE REQUESTED CP IS NOT LICENSED. PLEASE CONTACT YOUR SALESC1BMCBD I EXECUTIVE. IF YOU ARE REQUESTING A USAGE REPORT, CHECK THE PRODUCT CODE IN THEC1BMCBD I REQUEST, IT MAY BE INCORRECT.C1BMCBD IC1BMCBD IC1BMCBD IC1BMCBD IC1BMCBD IC1BMCBD IC1BMCBD IC1BMCBD I CLIENT NOT FOUNDC1BMCBD I CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE

CODE-1 Plus™ License Management Execution Log File (LMREPORT.XLG)

The message below displays in the License Management Execution Log (LMREPORT.XLG) when the license check fails due to the System ID not matching the System ID in the license file.

PITNEY BOWES GLOBAL PROGRAMMING SYSTEM, RXX.XM00 EXECUTION LOG 1

LMRPT10 I PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.LMRPT10 I LMRPT10 started. Compiled MM/DD/YYYY at HH:MM:SS.LMRVP00 I LMRVP00 started. Compiled MM/DD/YYYY at HH:MM:SS.LMRVP00 I LMRVP00 ended.You are attempting to run CP software on a system that is not licensed.Your ID is AEC839.

The following IDs were found in your license file:0294E1

Please contact your sales executive so that your software license may beappropriately modified without further interruption of service.


License Management Process for Windows

The message below displays in the License Management Execution Log (LMREPORT.XLG) when the license check is successful.

PITNEY BOWES GLOBAL PROGRAMMING SYSTEM, RXX.XM00 EXECUTION LOG 1

LMRPT10 I PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.LMRPT10 I LMRPT10 started. Compiled MM/DD/YYYY at HH:MM:SS.LMRVP00 I LMRVP00 started. Compiled MM/DD/YYYY at HH:MM:SS.LMRVP00 I LMRVP00 ended.LMRPT10 I LMRPT10 ended.

CODE-1 Plus™ License Management Report (LMREPORT.RPT)

The message below displays in the License Management Report (LMREPORT.RPT) when the license check fails due to the System ID not being licensed.

G1RPT10 - License Management Reporting Program NN.N 1

MM/DD/YYYY License Management Report

You are attempting to run CP software on a system that is not licensed.Your ID is AEC839.

The following IDs were found in your license file:0294E1

Please contact your sales executive so that your software license may beappropriately modified without further interruption of service.

The message below displays in the License Management Report (LMREPORT.RPT) when the license check is successful.

G1RPT10 - License Management Reporting Program NN.N 1

MM/DD/YYYY License Management Report

Client ID: 000000000000001Pitney Bowes INC. Pitney Bowes Inc.4200 PARLIAMENT PLACE SUITE 600 4200 Parliament Place Suite 600

LANHAM MD 20706-1844 Lanham Maryland 20706-1844USAATTN: NEW CLIENT800-367-6950 Phone: 888-413-6763 http://www.g1.com

Product: CP Today's Date: MM/DD/YYYY Original License Date: License Expiration Date: Perpetual Maximum Number of Transactions: unlimited To be used between: MM/DD/YYYY through MM/DD/YYYY Date of Last Run: MM/DD/YYYY IDs: AEC839

Total number of transactions for last run: 28Total number of transactions since MM/DD/YYYY 14,819,311 0.00% of Limit


Chapter 6: License ManagementLicense Management Process for UNIX

License Management Process for UNIX

Finding Your System ID for UNIX


HP-UX

1. From a prompt, issue the following command:

uname -i


3509210850

3. The System ID for CODE-1 PlusTM is the last six characters. In the example above, the value is:

210850

AIX


uname -m


00C2E8BE4C0

3. The System ID for CODE-1 PlusTM is in characters 3-8 of the response. In the example above, the value is:

C2E8BE

SunOS


hostid


830294e1

3. The number returns in a hexadecimal format. Convert the number to decimal. The sample response converts to:

2197984481

4. The System ID for CODE-1 PlusTM is the last six characters. In the example above, the value is:

984481

Display Error Messages for UNIX

The following error message displays on the screen when the license check fails due to the System ID not matching the System ID in the CODE-1 Plus™ license file.





License Management Process for Linux

License Management Report Error Messages for UNIX

The error message below displays in CODE-1 Plus™ execution log file (PRNTXLG) when the license check fails due to the System ID not matching the System ID in the CODE-1 Plus™ license file.


C1BM00 I PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.C1BM00 I EXECUTING CODE-1 PLUS N.NN.NN.NC1BM00 I C1BM00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 ENDED.C1BM00 I YOU ARE ATTEMPTING TO RUN CP SOFTWARE ON A SYSTEM THAT IS NOT LICENSED.C1BM00 I YOUR ID IS C2E8DE.C1BM00 IC1BM00 I THE FOLLOWING IDS WERE FOUND IN YOUR LICENSE FILE:C1BM00 I 0294E1 444640 1AF577 962C9B 210850 3230A3 09686DC1BM00 IC1BM00 I PLEASE CONTACT YOUR SALES EXECUTIVE SO THAT YOUR SOFTWARE LICENSE MAY BEC1BM00 I APPROPRIATELY MODIFIED WITHOUT FURTHER INTERRUPTION OF SERVICE.C1BM00 IC1BM00 IC1BM00 I CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE

License Management Process for Linux

Finding Your System ID for Linux


Red Hat


/sbin/ifconfig


eth0 Link encap:Ethernet HWaddr 00:14:22:1A:F5:2A inet addr:161.228.116.232 Bcast:161.228.116.255 Mask:255.255.255.0 inet6 addr: fe80::214:22ff:fe1a:f52a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1149617719 errors:0 dropped:0 overruns:0 frame:0 TX packets:1302517025 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:723243630821 (673.5 GiB) TX bytes:1453197625092 (1.3 TiB) Base address:0xdcc0 Memory:fe5e0000-fe600000

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:153869438 errors:0 dropped:0 overruns:0 frame:0 TX packets:153869438 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:44955029267 (41.8 GiB) TX bytes:44955029267 (41.8 GiB)

3. The System ID for CODE-1 PlusTM is the last six actual characters following Ethernet HWaddr. In the example above, the value is:

1AF52A


Chapter 6: License ManagementLicense Management Process for Linux

SuSE


/sbin/ifconfig


eth1 Link encap:Ethernet HWaddr 00:14:22:1A:F5:77 inet addr:161.228.116.231 Bcast:161.228.116.255 Mask:255.255.255.0 inet6 addr: fe80::214:22ff:fe1a:f577/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:474476962 errors:0 dropped:0 overruns:0 frame:0 TX packets:555646622 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:244813309135 (233472.1 Mb) TX bytes:698222475083 (665876.8 Mb) Base address:0xccc0 Memory:fe3e0000-fe400000

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:42309 errors:0 dropped:0 overruns:0 frame:0 TX packets:42309 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4040716 (3.8 Mb) TX bytes:4040716 (3.8 Mb)

3. The System ID for CODE-1 PlusTM is the last six actual characters following Ethernet HWaddr. In the example above, the value is:

1AF577

Linux Display Error Messages

The following error message displays on the screen when the license check fails due to the System ID not matching the System ID in the CODE-1 Plus™ license file.




Linux License Management Report Error Messages

The error message below displays in CODE-1 Plus™ execution log file (PRNTXLG) when the license check fails due to the System ID not matching the System ID in the CODE-1 Plus™ license file.


C1BM00 I PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.C1BM00 I EXECUTING CODE-1 PLUS N.NN.NN.NC1BM00 I C1BM00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 I C1BMVP00 ENDED.C1BM00 I YOU ARE ATTEMPTING TO RUN CP SOFTWARE ON A SYSTEM THAT IS NOT LICENSED.C1BM00 I YOUR ID IS C2E8DE.C1BM00 IC1BM00 I THE FOLLOWING IDS WERE FOUND IN YOUR LICENSE FILE:C1BM00 I 0294E1 444640 1AF577 962C9B 210850 3230A3 09686DC1BM00 IC1BM00 I PLEASE CONTACT YOUR SALES EXECUTIVE SO THAT YOUR SOFTWARE LICENSE MAY BEC1BM00 I APPROPRIATELY MODIFIED WITHOUT FURTHER INTERRUPTION OF SERVICE.C1BM00 IC1BM00 IC1BM00 I CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE


License Management for z/OS and IMS

License Management for z/OS and IMS

The CODE-1 Plus™ key is restricted to your licensed System ID(s). The System ID information must be provided to your Pitney Bowes Account Manager before a software key can be created for your use. If you use CODE-1 Plus™ on more than one system, you can provide up to seven System IDs.

When you upgrade your hardware, you must provide the new System ID information to your Account Manager so a new software key can be generated.

Finding Your System ID


z/OS and IMS

1. Issue the operator command:

D M=CPU


IEE174I 15.33.37 DISPLAY M 648PROCESSOR STATUSID CPU SERIAL00 + 02E3E02096…

3. The System ID for CODE-1 Plus is the first six characters below the SERIAL field. In the example above, the value is:

02E3E0

License Management Error Messages for z/OS and IMS

The following are examples of new License Management error messages that display during the License Management process when the System ID does not match the license file.

If you use a license management file from a previous release with CODE-1 Plus 3.6.0 or later, the following error information displays.

EXECUTION LOG PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY. EXECUTING CODE-1 PLUS N.NN.NN.M C1BM00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS. C1BMVP00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS. C1BMVP00 ENDED. YOU ARE ATTEMPTING TO RUN CP SOFTWARE ON A SYSTEM THAT IS NOT LICENSED. YOUR ID IS 02E3E0. THE FOLLOWING ID'S WERE FOUND ON YOUR LICENSE FILE: (NONE) PLEASE CONTACT YOUR SALES EXECUTIVE SO THAT YOUR SOFTWARE LICENSE MAY BE APPROPRIATELY MODIFIED WITHOUT FURTHER INTERRUPTION OF SERVICE. CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE.

If you use the new format license file with CODE-1 Plus 3.6.0 or later, but the license ID(s) does not match the system, the following error information displays.

EXECUTION LOG

PROGRAMS AND DESIGN (C) COPYRIGHT PITNEY BOWES SOFTWARE, INC. YYYY-YYYY.EXECUTING CODE-1 PLUS N.NN.NN.MC1BM00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.C1BMVP00 STARTED. COMPILED MM/DD/YYYY AT HH:MM:SS.


Chapter 6: License ManagementLicense Management for IBM i

C1BMVP00 ENDED.YOU ARE ATTEMPTING TO RUN CP SOFTWARE ON A SYSTEM THAT IS NOT LICENSED.YOUR ID IS 02E3E0.

THE FOLLOWING ID'S WERE FOUND ON YOUR LICENSE FILE:01E2E4 01E9E3 02E8E7 09E8E7 08F8F7 07E1E1 05E3E4

PLEASE CONTACT YOUR SALES EXECUTIVE SO THAT YOUR SOFTWARE LICENSE MAY BEAPPROPRIATELY MODIFIED WITHOUT FURTHER INTERRUPTION OF SERVICE.

CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE.

The sample driver (SMPLDRVR) has been modified for the exception flags that display when there is a license discrepancy. This message appears in "SYSOUT".

LICENSING KEY ERROR.

The system generates this message when encountering "S" in the P9OLIA-KEY-STATUS field.

* LM PRODUCT KEY STATUS * BLANK - PRODUCT/KEY COMBINATION IS GOOD* B - PRODUCT KEY IS MARKED BAD* N - PRODUCT KEY NOT FOUND* S - LICENSE ID DOES NOT MATCH SYSTEM* X - PRODUCT KEY EXPIRED*10 P9OLIA-KEY-STATUS PIC X.

When the matcher encounters a license key that does not match, interactive processing shuts down and generates this message.




License Management for IBM i

The CODE-1 Plus key for the IBM i platform is restricted to your licensed System ID(s). The System ID information must be provided to your Pitney Bowes Account Manager before a software key can be created for your use.

When you upgrade your hardware, you must provide the new System ID information to your PBBI Account Manager so a new software key can be generated.

Finding Your System ID


IBM i

1. From a Command prompt, issue the following command:

DSPSYSVAL QSRLNBR


System value . . . . . : QSRLNBRDescription . . . . . : System serial numberSerial number . . . . : 109123D

3. The System ID is the last six characters of the "Serial number." In the example above, the value is:

09123D


License Management for IBM i

Interactive Processing License Management Error Messages

When a user starts Interactive and attempts a match, CODE-1 Plus performs a license check. If the license check fails, Interactive exits and a messages displays in red on the C1CPMM03 screen.

The following message displays when the license check failed due to an empty license file or a missing license for CP (CODE-1 Plus):

PRODUCT RECORD FOR CP NOT FOUND IN LICENSE FILE

The following message displays when the license check failed due to the System ID not matching the System ID in the license file:

ID FOR THIS MACHINE DOES NOT MATCH LICENSE FILE

Batch Processing License Management Error Messages

The message below displays in PRNTXLG when the license check fails due to a missing client record or an empty license file.

EMPTY G1LICEN:

I CLIENT NF I CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE

The message below displays in PRNTXLG when the license check fails due to a System ID not being found in the license file. You may need to load a new license file that includes your System ID.

I YOU ARE ATTEMPTING TO RUN CP SOFTWARE ON A SYSTEM THAT IS NOT LICENSED.I YOUR ID IS 09123D. I I THE FOLLOWING IDS WERE FOUND IN YOUR LICENSE FILE: I (NONE) I I PLEASE CONTACT YOUR SALES EXECUTIVE SO THAT YOUR SOFTWARE LICENSE MAY BEI APPROPRIATELY MODIFIED TO PREVENT ANY FURTHER INTERRUPTION OF SERVICE. I I I CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE

The message below displays in PRNTXLG when the license check fails due toCODE-1 Plus not being licensed.

NO PRODUCT RECORD:

I THE PRODUCT YOU HAVE REQUESTED CP IS NOT LICENSED. PLEASE CONTACT YOUR SALES I EXECUTIVE. IF YOU ARE REQUESTING A USAGE REPORT, CHECK THE PRODUCT CODE IN THEI REQUEST, IT MAY BE INCORRECT.

The message below displays in PRNTXLG when the license check fails due to the System ID not being licensed:

I YOU ARE ATTEMPTING TO RUN CP SOFTWARE ON A SYSTEM THAT IS NOT LICENSED.I YOUR ID IS 09999D. I I THE FOLLOWING IDS WERE FOUND IN YOUR LICENSE FILE: I 01234A I I PLEASE CONTACT YOUR SALES EXECUTIVE SO THAT YOUR SOFTWARE LICENSE MAY BEI APPROPRIATELY MODIFIED TO PREVENT ANY FURTHER INTERRUPTION OF SERVICE. I I I CODE1-PLUS ABENDED DUE TO LICENSING, SEE ABOVE


Index

C

CICSConfiguring 36Installing 36

D

Databases 12, 20, 30, 40, 61Installing 46Installing on Windows 11

F

Finding your System ID 66, 69–70, 72–73

I

IBM iDatabase 60Installation prerequisites 50Installing 49, 65Installing databases 60Installing from DVD 52Installing from internet 51Installing product update 59Installing software 53license management 73System ID, finding 73Verifying the installation 63

IMSerror messages, license management 72Installation prerequisites 40Installing 39Installing databases 46Installing from internet 45

Software 45Installing from media 42

databases 42software 42

Installing product updates 47license management 72System ID, finding 72

L

License Managementerror messages 66Error messages for IMS 72Error messages for Linux 71

Error messages for UNIX/Linux 69Error messages for z/OS 72Finding your System ID 66, 69–70, 72–73IBM i 73IMS 72Linux 70UNIX/Linux 69Windows 66z/OS 72

Linuxerror messages, license management 71license management 70System ID, finding 70

S

System IDfinding 66, 69–70, 72–73

T

Technical support 13, 27, 38, 48, 63

U

UNIX/Linuxerror messages, license management 69Installation 15Installation prerequisites 16Installation system requirements 16Installing from internet 20

Installing databases 21Installing product files 21Verifying the installation 22

Installing product updates 25License management 24license management 69Special considerations 25System ID, finding 69Uninstalling 26

W

WindowsInstallation 7, 15Installation prerequisites 8Installation steps 10Installing databases 11Installing product updates 11


Installing the software 10license management 66System ID, finding 66Verifying the installation 11

Z

z/OSerror messages, license management 72Installation prerequisites 30Installation steps 34Installing CICS 36Installing databases 35Installing from internet 34Installing from media 32

databases 32Software 32

Installing product updates 36License management 31license management 72System ID, finding 72


Feedback

Contact Preferences

May we contact you if we have questions about your comments?

Yes

No

Contact Information

Name:

Email:

Phone:

Best time to contact:

Comments

Enter you comments here:

Document Title:

Document Date:

Software Version:

Comment regarding page:

Date post:	24-Jan-2021
Category:	Documents
Upload:	others
View:	7 times
Download:	0 times