STRATIX_Upgrade_Guide

STRATIX 9.2

STRATIX UPGRADE GUIDE

Table of Contents

1. OVERVIEW .................................................................................................................................. 5

1.1 Upgrade Guide Modification History .......................................................................................... 5

1.1.1 Modifications on January 28, 2013 ................................................................................ 5

1.1.2 Modifications on March 27, 2013 .................................................................................. 5

1.1.3 Modifications on June 21, 2013 ..................................................................................... 5

1.1.4 Modifications on August 20, 2013 ................................................................................. 5

1.2 Introduction ................................................................................................................................ 5

1.2.1 Important Additional Documentation ........................................................................... 5

1.3 Critical INVEX-CUSTOMER Changes ............................................................................................ 6

2. STRATIX 9.2 UPGRADE PRE-REQUISITES ....................................................................................... 7

2.1 Verfication of Third-Party Software ............................................................................................ 7

2.1.1 AIX Version ..................................................................................................................... 7

2.1.2 IBM Informix Dynamic Server Version ........................................................................... 7

2.1.3 Java Version ................................................................................................................... 8

2.1.4 Micro Focus Version ....................................................................................................... 8

2.1.5 Web Browsers for STRATIX Web Products .................................................................... 8

2.2 STRATIX Software Related Pre-Requisites .................................................................................. 9

2.2.1 Starting Point ................................................................................................................. 9

2.2.2 Notify Invera .................................................................................................................. 9

2.2.3 STRATIXexec Version ...................................................................................................... 9

2.2.4 STRATIXmcm Version ..................................................................................................... 9

2.2.5 STRATIX/CSX Integration Testing ................................................................................... 9

2.2.6 Enterprise Parameter Data Propagation...................................................................... 10

2.2.7 Verifying NLS Settings .................................................................................................. 10

2.2.8 Accounts Payable Bank Transfer (eCIM 237045) ......................................................... 10

2.3 Logistical Issues ......................................................................................................................... 11

2.3.1 Backups ........................................................................................................................ 11

2.4 Upgrade Checklist ..................................................................................................................... 12

3. STRATIX OVERVIEW & PLANNING .............................................................................................. 16

3.1.1 Upgrade Sequence ....................................................................................................... 16

3.1.2 Differences between STRATIX & STRATIX/GL .............................................................. 16

3.1.3 Upgrading a Secondary Server ..................................................................................... 16

STRATIX Upgrade Guide – 9.2

Licensed Material, January 28, 2013

Invera

The Metal Information Technology Company

Table of Contents



Page 2

4. STRATIX SERVER UPGRADE ....................................................................................................... 17

4.1 Loading Software ....................................................................................................................... 17

4.2 Conversion Program Update ..................................................................................................... 18

4.3 STRATIXfinreps Software ........................................................................................................... 19

4.4 Updating Configuration Files ..................................................................................................... 19

4.4.1 set_stratix ..................................................................................................................... 19

4.4.2 UBBCONFIG Update ...................................................................................................... 23

4.5 Database Changes ..................................................................................................................... 23

4.5.1 General Database Update Process ............................................................................... 23

4.5.2 Installation/Upgrade Logs ............................................................................................ 24

4.5.3 Linking STRATIX to STRATIX/GL .................................................................................... 27

4.6 Backup Upgraded Database(s) .................................................................................................. 28

5. STRATIX CLIENT UPGRADE ........................................................................................................ 29

5.1 STRATIX Client update via CD .................................................................................................... 29

5.2 STRATIX Client update via Insync .............................................................................................. 31

6. DATA CHANGES & CONVERSIONS ............................................................................................. 33

6.1 Boot STRATIX Application Servers ............................................................................................. 33

6.2 Data Conversions – STRATIX Databases .................................................................................... 33

6.2.1 Create User roles Utility– zzzsur ................................................................................... 33

6.2.2 Update XRS Reship Data Utility – zzzxrs ....................................................................... 35

6.2.3 Product Item Process HistoryUtility – zzzphs ............................................................... 39

6.2.4 Add ISAM files for Inventory Planning Utility – plzais .................................................. 40

6.2.5 Blank out TAV Utility – zzzbta ....................................................................................... 41

6.2.6 Fix Job Summary Conversion Utility – zzzjdd ............................................................... 43

6.2.7 Default Document Printer Utility – zzzdpv ................................................................... 45

6.2.8 Build Freight Journal Utility – zzzbfj ............................................................................. 46

6.2.9 Invoice Request Update Utility – zzzrq1 ....................................................................... 47

6.2.10 Job Summary Header Utility – zzzjdh ........................................................................... 49

6.2.11 Order Reservation Fix Utility – zzzors ........................................................................... 50

6.2.12 Check Print Tables– zzzcpt ............................................................................................ 51

6.2.13 Cleanup Form Attachments Utility – zzzfat .................................................................. 52

6.2.14 Cost Reconciliation HeaderUtility – zzzirc .................................................................... 54

6.2.15 Delete Image Files Utility – zzzdif ................................................................................. 55

6.2.16 Average Cost Pool Utility – zzzpcn ................................................................................ 56

6.2.17 Populate IED/IEP Utility – zzzieb .................................................................................. 58

6.2.18 Populate Turn & Earn Utility – sazted .......................................................................... 59

6.3 Data Conversions – STRATIX/GL Databases .............................................................................. 61

6.3.1 Create User roles Utility – zzzsur .................................................................................. 61

6.3.2 Default Document Printer Utility – zzzdpv ................................................................... 62

Invera


Table of Contents Page 3

7. POST-INSTALLATION PROCEDURE.............................................................................................. 65

7.1 Mandatory Procedure ............................................................................................................... 65

7.1.1 Update the EP parameters in the IW database ........................................................... 65

7.1.2 Run Post-Installation Script in both Primary and GL Databases .................................. 66

7.1.3 Update Statistics for Primary, IW and GL Databases ................................................... 66

7.2 Post-Installation Conversion Utility .......................................................................................... 67

7.2.1 New End of Period Control Record for Product Turn and Earn Report ....................... 67

7.3 Post-Installation Update ........................................................................................................... 68

7.3.1 New Environment Variable for Email/Fax Prevention ................................................. 68

8. PRINT OPTIMIZER UPGRADE ..................................................................................................... 70



Invera


1.

OVERVIEW

1.1

1.1.1

1.1.2

1.1.3

1.1.4

Upgrade Guide Modification History

Modifications on January 28, 2013

 New STRATIX 9.2 Upgrade Guide

Modifications on March 27, 2013

 New Environment Variable for Email/Fax Prevention (section 7.3.1)

Modifications on June 21, 2013







Added Conversion Program Update section 4.2 and revised check list to reflect section changes

Changed the fourth sql verification for the Update XRS Reship Data Utility – zzzxrs in section 6.2.2.3 step 4.

Changed step 4 of the the sql verification for the Product Item Process HistoryUtility – zzzphs in section 6.2.3.3

Modifications on August 20, 2013

 Changed step 4 of the the sql verification once more for the Product Item Process

History Utility – zzzphs in section 6.2.3.3

1.2

Introduction

This document is intended to assist STRATIX System Administrators with the technical aspects of upgrading existing STRATIX environments to STRATIX version 9.2. The installer should also be familiar with concepts and topics found in the STRATIX Technology Installation and STRATIX Technology

Administration Manuals.

1.2.1

Important Additional Documentation

The proper operation of STRATIX relies on the accurate configuration of several key application settings. A new release of STRATIX may introduce new parameters or make changes to existing parameters that can significantly alter the behavior of STRATIX. The specific requirements for these settings will vary based on the business needs of each STRATIX site.

These settings are explained in detail in the ‘STRATIX 9.2 Upgrade Guide Application Settings’ and

‘STRATIX 9.2 Upgrade Guide Table Changes’ documents. The STRATIX Application System

Administrator must review the application settings document carefully in order to accurately determine the values of these application parameters which are to be set during the upgrade process.

The STRATIX Application System Administrator and/or the STRATIX Technical System Administrator



Invera


1. Overview Page 6 must review the table changes document carefully in order determine if changes will be necessary for custom applications and reports.

Each STRATIX release is accompanied by a STRATIXexec release. The instructions for the STRATIXexec

3.2 upgrade can be found in a separate STRATIXexec 3.2 Upgrade Guide.

A STRATIXmcm release is distributed with the STRATIX 9.2 release. The instructions for the

STRATIXmcm 2.0.6 installation can be found in a separate STRATIXmcm 2.0.6 Installation guide.

1.3

Critical INVEX-CUSTOMER Changes

The INVEX-CUSTOMER product has been replaced by the INVEX-eCOMMERCE and INVEX-SALES products. The former is targeted to the Service Center’s customers while the latter is intended for use by employees of the Service Center. As a result of this change:

1) Once the STRATIXexec Environment that controls a Domain has been updated, the INVEX-

CUSTOMER product will no longer be accessible from STRATIX Environments that are members of this Domain.

2) The STRATIX Domain Administrator will have to manually provide all internal users who had previously had access to INVEX-CUSTOMER with access to INVEX-SALES.

3) The STRATIX System Administrator for any STRATIX Environments that had customers who used the INVEX-CUSTOMER product will need to configure INVEX-eCOMMERCE for their use.



Invera


2.

STRATIX 9.2 UPGRADE PRE-REQUISITES

2.1

Verfication of Third-Party Software

The STRATIX Technology Standards document contains critical information regarding the required versions of the various Third-Party software packages used with STRATIXexec. The installer must review this document carefully and ensure full compliance with these requirements prior to attempting to upgrade STRATIXexec. Failure to do so may introduce errors in the upgrade process and/or may adversely affect the operation of STRATIXexec.

2.1.1

AIX Version

The STRATIX 9.2 release requires AIX Version 6.1 be installed on any server hosting

STRATIXexec, STRATIXmcm or STRATIX environments. Before upgrading any environment, ensure the AIX operating system version is 6.1. Otherwise, an AIX operating system upgrade

MUST be performed.

NOTE: IBM withdrew standard support services for AIX 5L Version 5.3 on April 30, 2012.

2.1.2

IBM Informix Dynamic Server Version

Over the last several years, IBM has withdrawn standard support services for a number of IBM

Informix Dynamic Server products:

Product

IBM Informix Dynamic Server Version 9.40



End of Support

Date

April 30, 2009

September 30, 2010

September 30, 2012

Invera has tested the STRATIX 9.2 release with the IBM Informix Dynamic Server versions 11.50 and

11.70 only. Before upgrading any environments, customers currently operating with the above unsupported versions of the IBM Informix RDBMS products should make the necessary arrangements to upgrade the IBM Informix software for their STRATIX databases.

Customers choosing to operate with an unsupported version of IBM Informix assume all risks and accept full responsibility for any STRATIX software issues and any IBM Informixrelated problems due to lack of vendor support. In addition, customers should be aware that an IBM Informix upgrade may be the only solution available for certain reported



Invera


2. STRATIX 9.2 Upgrade Pre-Requisites Page 8 problems.

2.1.3

Java Version

The STRATIX 9.2 release requires IMB 64-bit SDK and Runtime Environment for AIX, Java Technology

Edition Version 6 be installed on any server hosting STRATIXexec, STRATIXmcm or STRATIX environments.

< Build and Version Information for JVM: JRE 1.6.0 IBM AIX build pap6460sr8-20100409_01 (SR8)>

For convenience, the Java6_64.sdk.tar.gz file can be found in $STRATIXDIR/web/java-filesets of the new

STRATIX 9.2 release.

2.1.4

Micro Focus Version

The STRATIX 9.2 release requires Micro Focus Server Express Version 5.1 be installed on any server hosting STRATIXexec, STRATIXmcm or STRATIX environments.

2.1.5

Web Browsers for STRATIX Web Products

The following chart indicates Web Browser specifications for the INVEX-eCOMMERCE, INVEX-WCS and

INVEX-Sales.

Web Browser 

Firefox version 15 or higher

 Google Chrome version 22 or higher



Apple Safari 5.1 or higher

 Microsoft Internet Explorer version 8.0 or higher (PC only)

NOTE: Invera strongly recommends the Firefox, Google Chrome or

Apple Safari browsers for best application performance results.

With the Microsoft Internet Explorer browser, Invera has observed some page formatting issues and has experienced degradation in application performance.

The following chart indicates Web Browser specifications for the INVEX-SCORE and INVEX-CRM.



Invera


2. STRATIX 9.2 Upgrade Pre-Requisites Page 9

Web Browser 

Firefox version 15 or higher

 Google Chrome version 22 or higher



Apple Safari 5.1 or higher

 Microsoft Internet Explorer version 8.0 or higher (PC only)

NOTE: Invera strongly recommends the Firefox, Google Chrome or

Apple Safari browsers for best application performance results.

With the Microsoft Internet Explorer browser, Invera has observed some page formatting issues and has experienced degradation in application performance.

2.2

STRATIX Software Related Pre-Requisites

2.2.1

Starting Point

The upgrade to STRATIX 9.2 must be performed only on environments that are operational on STRATIX

9.0e. This upgrade guide assumes that all release/revisions up to and including STRATIX 9.0e have been installed in accordance with all steps described in the upgrade guide corresponding to each release/revision.

2.2.2

Notify Invera

Notify Invera of the upcoming STRATIX upgrade schedule and make arrangements for Standby Support if required.

2.2.3

STRATIXexec Version

Ensure that the STRATIXexec environment has been upgraded to STRATIXexec version 3.2 prior to the upgrade of STRATIX 9.2. Refer to the STRATIXexec Upgrade Guide for details on the upgrade process.

2.2.4

STRATIXmcm Version

If STRATIXmcm is required, ensure that the STRATIXmcm environment has been installed fully

(STRATIXmcm version 2.0.6) prior to the upgrade of STRATIX 9.2. Refer to the STRATIXmcm Installation

Guide for details on the upgrade process.

2.2.5

STRATIX/CSX Integration Testing

The STRATIX/CSX Overview document contains a master list of all screens, transaction update events, and business documents that support CSX extensions. The installer must verify all documented changes in order to ensure that any CSX customizations used by their site will remain operational after installing this new Release.

It is the customer’s responsibility to revise their CSX configuration as necessary to support any alterations to STRATIX entities that might occur with a new Release. The installer must also recreate



Invera


2. STRATIX 9.2 Upgrade Pre-Requisites Page 10 any custom triggers and/or stored procedures that they had previously created in the STRATIX database as these are removed as part of the STRATIX upgrade procedure.

2.2.6

Enterprise Parameter Data Propagation

This step ensures that the Enterprise Parameters in the primary STRATIX environment is propagated to the Information Warehouse that will help minimize any data errors encountered during the upgrade.

Step Description

1 Access the STRATIX environment that will be upgraded as the STRATIX user

2 Ensure the environment’s STRATIX Application Servers are up

3 In order to propagate the Enterprise Parameters to the Information Warehouse, key in at the command line: stxrun sczdap S

4 Run Session Log Inquiry by Program Name: sczdap. Review any errors generated. Report any errors to Invera Support and proceed with the STRATIX 9.2 Upgrade.

2.2.7

Verifying NLS Settings

Before proceeding with the STRATIX Upgrade, ensure that the database NLS settings are consistent with the STRATIX users’ language and country code and the settings within the set_stratix configuration file. Modify as necessary.


1 Log in as the STRATIX user.

2 Verify that the DB_LOCALE variable contained within the set_stratix file is set to the desired value. grep DB_LOCALE $HOME/set_stratix

3 Verify the database NLS values. dbaccess sysmaster << EOF more> select * from sysdbslocale where dbs_dbsname = “$DATABASE”

more > EOF

4 Verify the STRATIX user language and country code dbaccess $DATABASE << EOF more > select usr_lgn_id, usr_lng, usr_cty from mxrusr_rec where usr_lgn_id = “$LOGNAME”

more > EOF

2.2.8

Accounts Payable Bank Transfer (eCIM 237045)

Bank Transfer business document printing functionality has been retired effective with the STRATIX 9.2 release. For sites that use the Accounts Payable Bank Transfer business document printing feature, it is highly recommended, as a prerequisite procedure, that users review and arrange to print any previously un-printed Bank Transfer transactions if required. For further details please refer to the

STRATIX 9.2 Customer Release Notice.



Invera



2.3

Logistical Issues

2.3.1

Backups

Analysis of backup requirements is a prudent step before making modifications to any system. There are three main components of the STRATIX software implementation that can be backed up. These are the STRATIX program files, the STRATIX configuration files and the STRATIX database.

The decision to take additional backups is left up to the System Administrator. The decision can be based on how recent the most successful backup was along with the relevant impact of the upcoming changes.

The following table can facilitate System Administrators making a decision on performing backups.

Items to Backup

STRATIX program files

STRATIX configuration files

Database

Notes

Can be backed up at any time.

If required, they can be obtained from Invera’s FTP site.

Can be backed up at any time.

STRATIX set up scripts recreate the STRATIX configuration files

STRATIX set up scripts back up the most recent set_stratix configuration file

Should be backed up with users off

Errors encountered with this particular release will:

 Likely require a reload of the database

 Not likely require the reload of the database



Invera



2.4

Upgrade Checklist

The following is a suggested upgrade checklist.

Final STRATIX 9.2 UPGRADE

CHECKLIST

1 OVERVIEW

1.1 Upgrade Guide Modification History

1.2 Introduction

1.2.1 Important Additional Documentation

1.3 Critical INVEX-CUSTOMER Changes

2 STRATIX 9.2 Upgrade Pre-Requisites

2.1 Verification of Third-Party Software

2.1.1 AIX Software

2.1.2 IBM Informix Dynamic Server Version

2.1.3 Java Version

2.1.4 Micro Focus Version

2.1.5 Web Browsers for STRATIX Web Products

2.2 STRATIX Software Related Pre-Requisites

2.2.1 Starting Point

2.2.2 Notify Invera

2.2.3 STRATIXexec Version

2.2.4 STRATIXmcm Version

2.2.5 STRATIX/CSX Integration Testing

2.2.6 Enterprise Parameter Data Propagation

2.2.7 Verifying NLS Settings

2.2.8 Accounts Payable Bank Transfer (eCIM 237045)

2.3 Logistical Issues

2.3.1 Backups

M

R

R

M

M

M

M

M

R

M

M

M

R

R

M

M

STRATIX Databases Action Responsible Status

PR = Primary A = Application TD = To Do

IW = Information

Warehouse

M = Mandatory

GL = General Ledger

O = Optional /

If Applicable

T = Technology

I = Invera

IP = In Progress

CL = Complete

CL = Client

R = Review

ALL

ALL

ALL

ALL

ALL

ALL

PR & IW

ALL

PR & GL

ALL

T

T

T

T

T

T

T

T

T

A

T

T

T

T



Invera




2.4 Upgrade Checklist

CHECKLIST

3 STRATIX OVERVIEW & PLANNING

3.1.1 Upgrade Sequence

3.1.2 Differences Between STRATIX & STRATIX/GL

3.1.3 Upgrading a Secondary Server

4 STRATIX SERVER UPGRADE

4.1 Loading Software

4.2 Conversion Program Update

4.3 STRATIX/FINREPS Software

4.4 Updating Configuration Files

4.4.1 set_stratix

4.4.2 UBBCONFIG update

4.5 Database Changes

4.5.1 General Database Update Process

4.5.2 Installation/Upgrade Logs

4.5.3 Linking STRATIX to STRATIX/GL

4.6 Backup Upgraded Database(s)

5 STRATIX CLIENT UPGRADE

5.1

5.2

STRATIX Update via CD

STRATIX Update via STRATIX InSync

6 DATA CHANGES & CONVERSIONS

6.1 Boot STRATIX Application Servers

6.2 Data Conversions – STRATIX Databases

6.2.1 Create User Roles Conversion Utility – zzzsur – eCIM 227577

6.2.2 Update XRS Reship Data Conversion – zzzxrs – eCIM 237776

6.2.3 Product Item Process History Conversion – zzzphs – eCIM 241983

6.2.4 Add ISAM Files for Inventory Planning Conversion – plzais – eCIM 241833


PR = Primary R = Review A = Application


Warehouse

M = Mandatory


O = Optional /

If Applicable

T = Technology

I = Invera

TD = To Do


CL = Complete

CL = Client

ALL R A & T

PLEASE REVIEW THIS SECTION CAREFULLY

M

M

T

T

M T


PR, IW, GL

PR, IW, GL

CL

PR, IW, GL

PR, IW, GL

PR & GL

M

M

O

M

M

M

M

M

T

T

A & T

T

T

T

T

T

PR & GL

PR & GL

PR, IW, GL

CL

CL

PR, IW

PR

PR

PR

PR

PR

M

O

M

M

M

M

M

M

T

T

T

T

T

T

T

T

O

O

T

T


M T



Invera




CHECKLIST

6.2.5 Blank out TAV Conversion Utility – zzzbta – eCIM 242634

6.2.6 Fix Job Summary Conversion – zzzjdd – eCIM 245881

6.2.7 Default Document Printer Conversion – zzzdpv – eCIM 229788

6.2.8 Build Freight Journal Conversion – zzzbfj – eCIM 238580

6.2.9 Invoice Request Update Conversion – zzzrq1 – eCIM 245948

6.2.10 Job Summary Header Conversion – zzzjdh – eCIM 239283

6.2.11 Order Reservation Fix Conversion Utility – zzzors – eCIM 247876

6.2.12 Check Print Tables Conversion Utility – zzzcpt – eCIM 237045

6.2.13 Cleanup Form Attachments Conversion – zzzfat – eCIM 251326

6.2.14 Cost Reconciliation Header Conversion – zzzirc – eCIM 252131

6.2.15 Delete Image Files Conversion – zzzdif – eCIM 252624

6.2.16 Average Cost Pool Conversion – zzzpcn – eCIM 251295

6.2.17 Populate IED/IEP Conversion – zzzieb – eCIM 236875

6.2.18 Populate Turn & Earn Conversion – sazted – eCIM 236875

6.3 Data Conversions – STRATIX/GL Databases

6.3.1 Create User Roles Conversion Utility

– zzzsur – eCIM 227577

6.3.2 Default Document Printer Conversion – zzzdpv – eCIM 229788

7 POST-INSTALLATION PROCEDURE

7.1 Mandatory Procedure

7.1.1 Update the Enterprise Parameters in the IW database

7.1.2 Run Post-Installation Script in both Primary and GL Databases

7.1.3 Run Update Statistics on All Databases

7.2 Post-Installation Conversion Utility

7.2.1 Run Vehicle Schedule Cleanup Task

7.2.2 New End of Period Control Record

7.3 Post-Installation Update

7.3.1 New Environment Variable for Email/Fax Prevention

GL

GL

GL

IW

PR & GL

PR, IW & GL

PR

PR

PR

PR

PR


PR = Primary R = Review A = Application TD = To Do


Warehouse

M = Mandatory


O = Optional /

If Applicable

T = Technology

I = Invera


CL = Complete

CL = Client

PR

PR

M

M

T

T

PR

PR

PR

PR

M

M

M

M

T

T

T

T

PR

PR

PR

PR

PR

PR

PR

PR

M

M

M

M

M

M

M

M

T

T

T

T

T

T

T

T

M

M

M

M

M

M

M

M

M

M

M

T

T

T

T

T

T

T

T

T

T

T



Invera




CHECKLIST


PR = Primary R = Review A = Application


Warehouse

M = Mandatory


O = Optional /

If Applicable

T = Technology

I = Invera

TD = To Do


CL = Complete

CL = Client

CL M T 8 Print Optimizer Upgrade



Invera


3.

STRATIX OVERVIEW & PLANNING

3.1.1

Upgrade Sequence

The STRATIX 9.2 upgrade tasks include upgrading the STRATIXexec domain as well as the regular upgrading of the STRATIX environment. The STRATIXexec domain upgrade must be performed prior to the STRATIX environment upgrade. See the STRATIXexec Upgrade Guide – 3.2 for details on upgrading

STRATIXexec.

If STRATIXmcm is being used, this also must be installed prior to the STRATIX environment upgrade. See the STRATIXmcm Upgrade Guide – 2.0.6 for details on installing STRATIXmcm.

Any time a STRATIX GL environment exists, it must be upgraded before its corresponding STRATIX environments.

Any time STRATIX and/or STRATIX G/L environments are replicated on a secondary server, the stx_setup script must always run on the primary server first.

3.1.2

Differences between STRATIX & STRATIX/GL

There are minor differences between the process for upgrading a STRATIX/GL environment as opposed to upgrading a STRATIX environment (with its corresponding Information Warehouse database). When working with a STRATIX/GL environment, all references to the Information Warehouse database can be safely ignored, as there is no Information Warehouse associated with STRATIX/GL.

All other differences between these upgrade processes are identified with this symbol:

3.1.3

Upgrading a Secondary Server

Any notes specific to the upgrade of an environment on a Secondary STRATIX Server are this symbol: identified by



Invera


4.

STRATIX SERVER UPGRADE

4.1

Loading Software

In order to proceed with the STRATIX Server Upgrade, environments must be operational on STRATIX

9.0e. The following are instructions to update the STRATIXDIR with the new STRATIX programs.


1 Access the environment that will be upgraded as the STRATIXuser

2 Bring the environment’s STRATIX Application Servers down

3 Login as root

4 Create the STRATIXDIR file system.

5 Mount the STRATIXDIR file system.

6 Set the ownership of STRATIXDIR to root:staff

7 Set the permissions of STRATIXDIR to 2755

8 Insert the STRATIX Server CD into the CDROM drive and mount the /cdrom file system.

9 Copy all files from the STRATIX CD into a temporary directory

10 Repeat steps 8 & 9 for each STRATIX CD

11 Change the directory into the temporary directory.

12 Run the stx_loader script to extract the files from the compressed TAR archives. (See Figure 4-1).

13 If an error occurs when running stx_loader, move STRATIXDIR/web.save to STRATIXDIR/web, then rerun stx_loader.

14 Set permissions to 4755 and ownership to informix:informix for the file $STRATIXDIR/bininf/stxarclog



Invera


4. STRATIX Server Upgrade

STRATIX Program Loader

Please enter the full path to the STRATIXDIR to be updated.

Path:/stx92pgms

Please select version to install:

1) 92

Selection: 1

===============================================================================

SUMMARY

===============================================================================

Ready to install STRATIX software.

Revision selected: 92

Destination path: /stx92pgms

NOTE: Please ensure that a backup of this directory exists before continuing.

Press (c) to Continue, or (a) to Abort: c

Continue...

Removing unused modules from memory.

Extracting files to: /stx92pgms x ./bin x ./bin/apc_cleanup, 1568663 bytes, 3064 media blocks. x ./bin/apc_prpg_gl, 3704684 bytes, 7236 media blocks..

.

.

Program Update Complete.

Figure 4-1: stx_loader Sample Output

Page 18

Repeat the above steps on the Secondary STRATIX Server if the environment being upgraded is replicated.

4.2

Conversion Program Update

As a result of issues encountered with a test conversion, we have posted an additional 9.2 compressed

UNIX file. From Invera’s FTP site, download the STX-92cnv-Unix-1of1.Z file located in the download/stratix92 directory. Place this file into a temporary directory along with a copy of stx_loader

(this can be retrieved from the FTP site).





Invera


4. STRATIX Server Upgrade Page 19


2 Ensure environment’s application servers are down

3 Login as root

4 Change the directory into the temporary directory.

5 Run the stx_loader script to extract the files from the compressed TAR archives. (See Sample screen below)

STRATIX Program Loader

Please enter the full path to the STRATIXDIR to be updated:

/stx92pgms

Please Select Version to Install:

1) 92cnv

1

Ready to install STRATIX software.

Revision selected: 92cnv

Destination path: / stx92pgms

NOTE: Please ensure that a backup of this directory exists before continuing.

Press (c) to Continue, or (a) to Abort: c

Continue...

Removing unused modules from memory.

Extracting files to: /tmp/anna/annastx x ./pgms x ./pgms/sazted.gnt, 133187 bytes, 261 media blocks. x ./pgms/sxu663, 3154032 bytes, 6161 media blocks. x ./pgms/sxu718, 6448194 bytes, 12595 media blocks. x ./pgms/zzzphs.gnt, 83427 bytes, 163 media blocks.

Program Update Complete.

4.3

STRATIXfinreps Software

If you are using STRATIX/FINREPS, and are interested in benefiting from the modifications and software corrections described in the release notes, please contact Invera to arrange an upgrade of your current

STRATIX/FINREPS sheet.

4.4

Updating Configuration Files

4.4.1

set_stratix

Changes to set_stratix and UBBCONFIG (Tuxedo middleware only) files are implemented by running the stx_setup script. The original copy of these set_stratix is preserved and renamed to set_stratix.YYYYMMDD.hhmm (where YYYY=year, MM=month, DD=date, hh=hour, mm=minute of the time when stx_setup is run). The UBBCONFIG file is recreated with any custom settings pertaining to



Invera



MIN and MAX servers are preserved. Any customization to the UBBCONFIG can be made via the

STRATIX interface using the Tuxedo Server Management option.

The stx_setup script is used to update STRATIXexec with the proper environment parameters. If an

Authorization Code has been set up in STRATIXexec, the administrator running the stx_install script must enter the appropriate code to ensure that STRAITXexec is properly updated. If no Authorization

Code has been used, the administrator can simply press enter when prompted to enter a code.

It is important to note that the set_stratix file and all other configuration files created via the stx_setup should not be edited manually. Doing such things will renter the file(s) invalid and cause the STRATIX application servers not to boot.


1 Login as the STRATIX User.

2 Verify that the current directory is the STRATIX user's home directory.

3 At the command line, specify the full path to execute the program i.e. $STRATIXDIR/bininf/stx_setup

4 Prepare the branding files used by the INVEX web applications as follows: a) Change directory to the $STRATIXDATADIR/web/invex directory b) Copy the branding_xml.ini file from the $STRATIXDIR/ref directory to this directory as branding.xml c) Set ownership of the branding.xml file to STRATIXuser:staff d) Set permissions of the branding.xml file to 775 e) Change directory to the $STRATIXDATADIR/web/invex/images subdirectory f) Copy the background_png.ini from the $STRATIXDIR/ref directory to this directory as background.png g) Copy the invexlogo_png.ini from the $STRATIXDIR/ref directory to this directory as invexlogo.png h) Set ownership of the background.png and invexlogo.png files to STRATIXuser:staff i) Set permissions of the background.png and invexlogo.png files to 664

Skip this step when installing a STRATIX/GL environment.



Invera



===============================================================================

STRATIX Environment Configuration Utility 28 Jan 2013 16:22

===============================================================================

A previous configuration was found for this environment.

Two modes are available for you to use:

Initialize mode

~~~~~~~~~~~~~~~

This will destroy ANY previous configuration of STRATIX installed in

/u/dinastx. Use this method when you need to completely replace any configurations that you may have had previously. Please use this option only if necessary or when instructed to do so.

Update mode

~~~~~~~~~~~

This allows you to upgrade STRATIX from a previous version, or correct a problem with an existing configuration file.

[I]nitialize new config, [U]pdate existing config, or [Q]uit? U

-------------------------------------------------------------------------------

Menu A: STRATIX Environment and Location Settings

-------------------------------------------------------------------------------

## ENVIRONMENT VARIABLE STS CURRENT VALUE

-- --------------------------- --- --------------------------------------------

1 STRATIXDIR................. F /teststx

2 STRATIXDATADIR............. C /stratixdatadir/teststxdd

3 WORKDIR.................... C /workdir/teststx

4 MIDDLEWARE................. C apache (STRATIXstream)

5 ENVTYPE.................... C STX

6 ENVMODE.................... C PRI

7 ENVCLASS................... F TST

8 COBDIR..................... C /apps/mf

-------------------------------------------------------------------------------

Status: F indicates a field that is fixed. C is a field that can be changed.

[N]ext, [P]revious, Menu [A-C], select number [1-8], [S]ave, or [Q]uit:

Page 21



Invera



-------------------------------------------------------------------------------

Menu B: STRATIX Network Settings

-------------------------------------------------------------------------------


-- --------------------------- --- --------------------------------------------

1 PRI_SRVR................... C 172.20.200.62

2 PRI_PORT................... C 33552

3 PRI_EXECSRVR............... C thimar

4 PRI_EXECPORT............... C 48888

5 SEC_EXECSRVR............... C

6 SEC_EXECPORT............... C

7 STXWEB_HTTP_INTERNAL_HOST.. C 172.20.200.62

8 STXWEB_HTTP_INTERNAL_PORT.. C 60552

9 STXWEB_JBOSS_RMI_OBJECT_PORT C 61552

-------------------------------------------------------------------------------



Page 22

-------------------------------------------------------------------------------

Menu C: STRATIX Informix Database Settings

-------------------------------------------------------------------------------


-- --------------------------- --- --------------------------------------------

1 INFORMIXDIR................ C /apps/informix

2 ONCONFIG................... C onconfig.train

3 INFORMIXSERVER............. C thimartrain

4 DATABASE................... C teststxdb

5 INDEXDBS................... C datadbs

6 DBSRVRNM................... C thimar

7 DBPORT..................... C 15002

8 NET_ISERVER................ C thimartrain

9 IW_INFORMIXSERVER.......... C thimartrain

10 IW_DATABASE................ C teststxdb_iw

11 IW_INDEXDBS................ C datadbs

12 IW_DBSRVRNM................ C thimar

13 IW_DBPORT.................. C 15002

14 DB_LOCALE.................. C en_us.8859-1

-------------------------------------------------------------------------------



Figure 4-2: stx_setup Sample Screens

Repeat the above steps on the Secondary STRATIX Server if the environment being upgraded is replicated.



Invera



4.4.2

UBBCONFIG Update


1 Login as the STRATIX User.

2 Verify that the current directory is the STRATIX user's home directory.

3 Review the UBBCONFIG to ensure the MAX server is set to 100 for the sxu726 server: sxu726" SRVGRP="XA-GROUP" SRVID=5213

RQPERM=0666 REPLYQ=Y RPPERM=0666 MIN=1 MAX=100 CONV=N

SYSTEM_ACCESS=FASTPATH

MAXGEN=255 GRACE=86400 RESTART=Y

Save any changes if necessary.

4 If changes were made to the UBBCONFIG, recreate the TUXCONFIG: tmloadcf UBBCONFIG

Answer Y to “Really overwrite TUXCONFIG file:”

4.5

Database Changes

There are minor differences between the processes for updating a STRATIX/GL database as opposed to updating a STRATIX database (with its corresponding Information Warehouse database). When working with a STRATIX/GL database, all references to the Information Warehouse database can be safely ignored, as there is no Information Warehouse associated with STRATIX/GL. All other differences between the update processes are highlighted in each applicable subsection.

Unless explicitly indicated, all steps must be repeated for both a STRATIX and its corresponding

STRAIX/GL environment.

4.5.1

General Database Update Process



2 Ensure the environment’s STRATIX Application Servers are down

3 Logging status should be set to Buffered for both Primary and Information Warehouse databases

4 Verify if users are accessing the database to be upgraded.

Via dbaccess, follow these instructions run the following SQL Statement: a) Connect to sysmaster database b) Run following sql and replace the reference to STRATIX DATABASE NAME in the where statement with the actual database that is being verified. select d.name database, s.username, s.hostname, l.owner sid from syslocks l, sysdatabases d, syssessions s



Invera



Step Description where l.tabname = 'sysdatabases' and

l.rowidlk = d.rowid and

l.owner = s.sid order by 1 into temp sysmastertemp; select * from sysmastertemp where database = " STRATIX DATABASE NAME "; c) Note the sid number d) Exit dbaccess e) Kill the session using onmode -z <sid number>

5 Stop database replication, if applicable.

6 To update STRATIX or STRATIX/GL, key in at the command line: stx_install

NOTE: stx_install will automatically place STRATIX in ‘Administration Mode’. When in this mode, only users whose access level is System Administrator will be able to log in to STRATIX. All other users will receive a message warning them that they cannot log in at this time.

7 Installation settings will be displayed for the user to review and accept to continue with the upgrade process.

8 Re-enable database replication, if applicable.

4.5.2

Installation/Upgrade Logs

Any activity related to the installation of a new STRATIX environment or the upgrading of an existing environment on the STRATIX Server is logged within the database associated with that environment.

The viewupglog script, as show in Figure 4-3 allows the System Administrator to easily examine these

database records in order to troubleshoot upgrade problems or to trace the installation history of an environment.



Invera



/stratixpgms/ref sq82:loki> viewupglog –h

This script will display messages logged in the 'Upgrade/Installation Log' table (sytupl_rec).

Usage:

viewupglog [-v <STRATIXversion>] [-t <ERR|INF|RVW|ALL>] [-s <script>] [-l]

[ -v <STRATIXversion> ] desired version of STRATIX to display records for.

(i.e.: 68 or 70) Default is current version.

[ -t <type of message>] indicates the type of records to display.

Default is ALL. Valid values are:

ERR: error INF: informational RVW: review ALL: all

[ -s <script>] name of script that logged entries to be displayed.

Default is all scripts.

[ -l ] latest run only for selected options

[ -h ] specifies Help

Example: viewupglog -v 92 -t ERR -s stx_install

Will display all the 'Upgrade/Installation Log' error records

that stx_install logged during the installation/upgrade

of STRATIX 9.2

Example: viewupglog –l

All messages for last script

Figure 4-3: viewupglog Help Message

4.5.2.1

Warnings displayed on screen

Some warnings may be displayed when running stx_install. These warnings can be safely ignored.

4.5.2.2

Primary Database – Expected Errors from SQL Conversions

The following errors, if encountered in the Primary Database, can also be ignored:

When running sql92.sql:

206: The specified table (sytins_rec_obs) is not in the database.

111: ISAM error: no record found.

206: The specified table (sythst_rec_obs) is not in the database.


206: The specified table (zzrbag_rec) is not in the database.




Invera



206: The specified table (zzrbry_rec) is not in the database.


206: The specified table (zzrcsb_rec) is not in the database.


206: The specified table (zzrpto_rec) is not in the database.


4.5.2.3

Information Warehouse – Expected Errors from SQL Conversions

The Information Warehouse database is comprised of Inventory Planning, Sales Analysis and Enterprise

Parameters tables. The Enterprise Parameters tables reference various tables that are not defined in the Information Warehouse database, therefore, errors may be encountered in the following cases and can be ignored:



Transaction Tables – tables with ‘t’ as the 3 rd character



Archive Tables – tables with ‘a’ as the 3 rd character



History Tables – tables with ‘h’ as the 3 rd character



Control Tables – tables with ‘c’ as the 3 rd character



Balance Tables – tables with ‘b’ as the 3 rd character



Journal Tables – tables with ‘j’ as the 3 rd character



Work Tables – tables with ‘w’ as the 3 rd character



Export Tables – tables with ‘e’ as the 3 rd character



Import Tables – tables with ‘i’ as the 3 rd character

The following error can also be ignored:

4.5.2.4

Expected Errors from SQL Conversions on GL Database

The General Ledger database is comprised of GL and Enterprise Parameters tables. The Enterprise

Parameters tables reference various tables that are not defined in the GL database, therefore, errors may be encountered in the following cases and can be ignored:



Non-GL Transaction Tables – tables with “t” as the 3 rd character



Non-GL Archive Tables – tables with “a” as the 3 rd character



Non-GL History Tables – tables with “h” as the 3 rd character



Invera





Non-GL Control Tables – tables with “c” as the 3 rd character



Non-GL Balance Tables – tables with “b” as the 3 rd character



Non-GL Journal Tables – tables with “j” as the 3 rd character



Non-GL Work Tables – tables with “w” as the 3 rd character



Non-GL Export Tables – tables with “e” as the 3 rd character



Non-GL Import Tables – tables with “i” as the 3 rd character



Note: the GL database will contain tables starting with gl*, ds*, sc*, tc*, mx*, sy*, xc*

The following error can also be ignored:

206: The specified table (zzrbag_rec) is not inthe database.


206: The specified table (zzrbry_rec) is not in the database.


206: The specified table (zzrcsb_rec) is not in the database.


206: The specified table (zzrpto_rec) is not in the database.


4.5.3

Linking STRATIX to STRATIX/GL

Customers operating both STRATIX and STRATIX/GL environments must use the following procedure in order to link the STRATIX environment to the STRATIX/GL environment.

4.5.3.1

Pre-Requisite

Ensure that the STRATIX/GL environment has been upgraded prior to proceeding with the following steps.



Invera



The following steps should be run on the STRATIX environment’s Primary Database:


1 Login as the STRATIXuser for the STRATIX environment to be linked to the STRATIX/GL environment.

2 Ensure the environment’s STRATIX Application Servers are down

Shutdown servers by issuing the following command stxshutdown –a

3 Key in at the command line: stx_gl_link

4.6

Backup Upgraded Database(s)

IMPORTANT: Prior to proceeding with the additional data updates and one-time conversion procedures, a backup of the partially upgraded database should be taken.

Page 28



Invera


5.

STRATIX CLIENT UPGRADE

5.1

NOTE:

STRATIX Client update via CD

The STRATIX Client can be upgraded via the STRATIX Client CD or the equivalent downloadable Windows Component zip file.

The following process should be used to upgrade either Terminal Servers or PC’s running the STRATIX

Client. This procedure can only be used for upgrades. For a first time installation of the STRATIX Client, please refer to the STRATIX Technology Installation Manual. Steps that are only applicable to Terminal

Servers are noted and should be omitted when upgrading a PC.


1 Place the Terminal Server into ‘Install’ mode. (Terminal Server only.)

2 Insert the ‘STRATIX Windows Components’ CD into the CD-ROM drive and run setup.exe.

3 Click on ‘Next’ to start the upgrade of STRATIX



Invera


5. STRATIX Client Upgrade


4 InstallShield will install the STRATIX programs

Page

30

5 Click the ‘Finish’ button.



Invera


5. STRATIX Client Upgrade Page

31


6 Once the InstallShield process has completed the following screen will appear. Reboot the client device when prompted to do so.

7 Place the Terminal Server into ‘Execute’ mode. (Terminal Server only.)

5.2

STRATIX Client update via Insync

STRATIXUPDATE files which are used for upgrading the STRATIX clients via Insync are no longer release on the STRATIXexec CD. These can be downloaded from the FTP site and should be copied into the

$EXECDIR/clientupdates directory on the AIX server running STRATIXexec. Alternatively these

STRATIXUPDATE files can be copied onto a fileserver if the Insync Server information has been updated within the STRATIXexec Domain Administrative Console.


1 Ensure nothing else is running on the STRATIX Client.

Access the STRATIX 92 environment as usual

2 Click the green check to initiate the upgrade



Invera


5. STRATIX Client Upgrade


3 STRATIX Insync will install the STRATIX programs

Even though the percentage remains at 0%, STRATIX is still being installed.

4 STRATIX Insync will reboot the STRATIX Client

Important Note: If for any reason, Insync fails to reboot the client, a manual reboot must be performed.

Page

32



Invera


6.

DATA CHANGES & CONVERSIONS

The steps that follow must be run in sequential order. Ensure that the STRATIX Application Servers are booted. Access the STRATIX environment that will be upgraded as the STRATIXuser in order to run the one-time conversions.

6.1

Boot STRATIX Application Servers


1 Login as the STRATIX user.

2 Boot servers by issuing the following command stxboot –a

NOTE: For a tuxedo environment, the sxu613 server will not boot as STRATIX will be in Administrative Mode.

6.2

Data Conversions – STRATIX Databases

The conversion programs listed in this section are valid for STRATIX environments.

Conversion programs for STRATIX/GL are found in the following section.

Ensure that the environment’s STRATIX Application Servers are active prior to beginning any data conversions. Each conversion step lists an SQL statement that can be used to confirm the successful completion of the conversion program.

The Return String of each of conversion utility should be 0000. If this is not the case, do not proceed

with further conversion steps and contact Invera immediately for assistance.

Should any verification SQL fail, notify Invera immediately and continue with the remainder of the upgrade.

6.2.1

Create User roles Utility– zzzsur

6.2.1.1

Create User Roles Conversion

This program will create User Roles records (mxruro) based on the current data that exists in the scrslp, arrcra, plrrmg, scrbyr, zzzsur (which contains a copy of scrbrh data) and mxrofa tables. Only active records are considered . For the tables scrslp, arrcra, plrrmg, scrbyr – if there are duplicate records for a

LGN-ID, only one (the first one found) will be written to the mxruro table. Any other records that exist for the same LGN-ID in each table after the first, will be set to Inactive.



Invera


6. Data Changes & Conversions Page

34

The following utility can be run with users on. It can be run multiple times only if required.

6.2.1.2

Run Utility


1 Exit dbaccess and ensure you are logged in as the STRATIX user.

2 Key in at the command line:

stxrun zzzsur S

3 The following should be displayed:

Return String: 0000

6.2.1.3

__ Verification – After Running Utility


1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzsur'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzsur';

2 Review the output from the above SQL statements to ensure that no errors were encountered.

3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzsur' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzsur Program Name in the access method window.



Invera



35


4 If unsure about the results, contact Invera to fix any data issues and continue with the upgrade.

5 If any data issues were found, once they have been resolved, re-run the utility by following the steps in 6.2.1.2.

6.2.2

Update XRS Reship Data Utility – zzzxrs

6.2.2.1

Update XRS Reship Data Conversion

This program will update the new fields in the Release Shipment Index (ortxrs) table.

The following utility must be run with users off. It can be run multiple times only if required.

6.2.2.2

Run Utility




stxrun zzzxrs S


Return String: 0000

6.2.2.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzxrs'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzxrs';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzxrs' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;



Invera



36


Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzxrs Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select count(*) from trtrsl_rec, ortxrt_rec, ortxrs_rec where rsl_cmpy_id = xrt_cmpy_id and rsl_otransp_pfx = xrt_transp_pfx and rsl_otransp_no = xrt_transp_no and rsl_orig_pk_lstno = xrt_pk_List_no and xrt_cmpy_id = xrs_cmpy_id and xrt_shpt_ctl_no = xrs_shpt_ctl_no and (xrs_rs_trac_pfx = ' ' or xrs_rs_trac_no = 0 or xrs_rs_trac_itm = 0); select count(*) from trtsrd_rec, trtrsl_rec, ortxrt_rec, ortxrs_rec where srd_sprc_pfx = 'RE' and srd_cmpy_id = rsl_cmpy_id and srd_trac_pfx = rsl_trac_pfx and srd_trac_no = rsl_trac_no and srd_trac_itm = rsl_trac_itm and rsl_cmpy_id = xrt_cmpy_id and rsl_otransp_pfx = xrt_transp_pfx and rsl_otransp_no = xrt_transp_no and rsl_orig_pk_lstno = xrt_pk_List_no and xrt_cmpy_id = xrs_cmpy_id and xrt_shpt_ctl_no = xrs_shpt_ctl_no and (xrs_rs_trac_pfx = ' ' or xrs_rs_trac_no = 0 or xrs_rs_trac_itm = 0 or xrs_rs_transp_pfx = ' ' or xrs_rs_transp_no = 0 or xrs_rs_pk_list_no = 0);



Invera



37

Step Description select count(*) from trjtud_rec, trtrsl_rec, ortxrt_rec, ortxrs_rec where tud_sprc_pfx = 'RE' and tud_cmpy_id = rsl_cmpy_id and tud_trac_pfx = rsl_trac_pfx and tud_trac_no = rsl_trac_no and tud_trac_itm = rsl_trac_itm and rsl_cmpy_id = xrt_cmpy_id and rsl_otransp_pfx = xrt_transp_pfx and rsl_otransp_no = xrt_transp_no and rsl_orig_pk_lstno = xrt_pk_List_no and xrt_cmpy_id = xrs_cmpy_id and xrt_shpt_ctl_no = xrs_shpt_ctl_no and (xrs_rs_trac_pfx = ' ' or xrs_rs_trac_no = 0 or xrs_rs_trac_itm = 0 or xrs_rs_transp_pfx = ' ' or xrs_rs_transp_no = 0 or xrs_rs_pk_list_no = 0); select /*+ ordered */ count(*) from trjrsj_rec, trjtud_rec, ortxrt_rec, ortxrs_rec where tud_sprc_pfx = 'RE' and tud_cmpy_id = rsj_cmpy_id and tud_trac_pfx = rsj_trac_pfx and tud_trac_no = rsj_trac_no and tud_trac_itm = rsj_trac_itm and rsj_cmpy_id = xrt_cmpy_id and rsj_otransp_pfx = xrt_transp_pfx and rsj_otransp_no = xrt_transp_no and rsj_orig_pk_lstno = xrt_pk_List_no and xrt_cmpy_id = xrs_cmpy_id and xrt_shpt_ctl_no = xrs_shpt_ctl_no



Invera


6. Data Changes & Conversions

Step Description and not exists

( select *

from trtrsl_rec

where rsl_cmpy_id = rsj_cmpy_id

and rsl_trac_pfx = rsj_trac_pfx

and rsl_trac_no = rsj_trac_no

and rsl_trac_itm = rsj_trac_itm ) and ( xrs_rs_trac_pfx = ' ' or xrs_rs_trac_no = 0 or xrs_rs_trac_itm = 0 or xrs_rs_transp_pfx = ' ' or xrs_rs_transp_no = 0 or xrs_rs_pk_list_no = 0);

The above sqls should return zero records.



Page

38



Invera



39

6.2.3

Product Item Process HistoryUtility – zzzphs

6.2.3.1

Product Item Process History Conversion

This program will update the new fields in the Prod Item Process History (intphs) table.


6.2.3.2

Run Utility




stxrun zzzphs S


Return String: 0000

6.2.3.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzphs'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzphs';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzphs' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzphs Program Name in the access method window.

4 Run the following SQL statement via dbaccess:



Invera



40

Step Description select count(*) from intphs_rec, intprd_rec

where phs_cmpy_id = prd_cmpy_id

and phs_itm_ctl_no = prd_itm_ctl_no

and phs_jbs_pfx = ' '

and phs_jbs_no = 0

and (exists (select * from iptjob_rec

where phs_cmpy_id = job_cmpy_id

and phs_ref_pfx = job_job_pfx

and phs_ref_no = job_job_no)

or exists (select * from ipjtrh_rec

where phs_cmpy_id = trh_cmpy_id

and PHS_REF_PFX = TRH_REF_PFX

and PHS_REF_NO = TRH_REF_NO))

The above sql should return zero records.



6.2.4

Add ISAM files for Inventory Planning Utility – plzais

6.2.4.1

Add ISAM files for Inventory Planning Conversion

This program will create the replenishment warehouse and replenishment product ISAM workfiles and the PLI record.


6.2.4.2

Run Utility




stxrun plzais S


Return String: 0000



Invera



41

6.2.4.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'plzais'; select * from sctmsg_rec where msg_svc_pgm_nm = 'plzais';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'plzais' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the plzais Program Name in the access method window.

4 Connect to the Information Warehouse database by running the following command dbaccess $IW_DATABASE@$IW_INFORMIXSERVER

Run the following SQL statement via dbaccess: select plr_cmpy_id from pltplr_rec where plr_extc_sts = 1 and plr_spm_map_sts = 0; select pli_cmpy_id from pltpli_rec;

If a PLR record exists and the associated PLI record with the same company ID does not exist, the data for that company is not valid and investigation is required.



6.2.5

Blank out TAV Utility – zzzbta



Invera



42

6.2.5.1

Blank out TAV Conversion

This program blanks out the TAV data fields on the TRTSRD record when the business rules apply.


6.2.5.2

Run Utility




stxrun zzzbta S


Return String: 0000

6.2.5.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzbta'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzbta';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzbta' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzbta Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select srd_cmpy_id, srd_sprc_pfx, srd_sprc_no, srd_trac_pfx, srd_trac_no, srd_trac_itm



Invera



43

Step Description from trtsrd_rec where srd_trac_pfx is not null and srd_trac_no is not null and srd_trac_itm is not null and not exists

( select * from trttav_rec where tav_cmpy_id = srd_cmpy_id and tav_trac_pfx = srd_trac_pfx and tav_trac_no = srd_trac_no and tav_trac_itm = srd_trac_itm );

The above SQL should return no records



6.2.6

Fix Job Summary Conversion Utility – zzzjdd

6.2.6.1

Fix Job Summary Conversion

This program will update Order Release (ortorl) data, setting the due date as well as the requested date to zero for job summary release zero orders.


6.2.6.2

Run Utility




stxrun zzzjdd S


Return String: 0000

6.2.6.3



1 Connect to the Primary database and run the following SQL statements via dbaccess:



Invera



44

Step Description select * from sctmsg_rec where msg_pgm_nm = 'zzzjdd'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzjdd';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzjdd' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzjdd Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select count(*) from ortorh_rec where orh_ord_typ = "J" and orh_sts_actn <> "C" and exists

(select * from ortorl_rec, ortord_rec where orl_ord_no = orh_ord_no and orl_ord_rls_no = 0 and orl_due_dt_ent <> 0 and ord_ord_no = orl_ord_no and ord_ord_itm = orl_ord_itm and ord_ord_itm_typ <> "G" and ord_sts_actn = "A")






Invera



45

6.2.7

Default Document Printer Utility – zzzdpv

6.2.7.1

Default Document Printer Conversion

This program will leave the first active record found for the following fields as active and set any others for the same combination to inactive.

CMPY-ID

DOC-TYP = “PKL”

DIST-WHS


6.2.7.2

Run Utility




stxrun zzzdpv S


Return String: 0000

6.2.7.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzdpv'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzdpv';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzdpv' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;



Invera



46


Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzdpv Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select unique(ddp_cmpy_id||" "||ddp_dist_whs) from dsrddp_rec where ddp_bus_doc_typ = "PKL" and ddp_actv = 1; select count(*) from dsrddp_rec where ddp_bus_doc_typ = "PKL" and ddp_actv = 1 and exists (select * from scrcsc_rec

where csc_cmpy_id = ddp_cmpy_id) and exists (select * from scrwhs_rec

where whs_whs = ddp_dist_whs);

The number of rows returned from the first SQL must match the count of the second SQL.



6.2.8

Build Freight Journal Utility – zzzbfj

6.2.8.1

Build Freight Journal Conversion

This program will create Receipt Item Freight Journal records for vendor-owned final product items.

When vendor-owned product items are purchased to become company-owned product items, the purchasing program will use the freight cost and fuel cost from the freight journal records.


6.2.8.2

Run Utility






Invera



47


stxrun zzzbfj S


Return String: 0000

6.2.8.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzbfj'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzbfj';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzbfj' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzpfj Program Name in the access method window.



6.2.9

Invoice Request Update Utility – zzzrq1

6.2.9.1

Invoice Request Update Conversion

This program will populate the order prefix and number for shipment invoices.


6.2.9.2

Run Utility



Invera



48




stxrun zzzrq1 S


Return String: 0000

6.2.9.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzrq1'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzrq1';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzrq1' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzrq1 Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select count(*) from ivtrqs_rec where rqs_transp_no <> 0 and rqs_ord_no = 0

The result of the above sql should return zero records





Invera



49

6.2.10

Job Summary Header Utility – zzzjdh

6.2.10.1

_ Job Summary Header Conversion

This program will loop on Order Header (ortorh) records of type "J" and status action = "A" or "H" and populates ORH-TOT-JBDT-WGT with the sum of all open items' ORD-JBDT-WGT.


6.2.10.2

_ Run Utility




stxrun zzzjdh S


Return String: 0000

6.2.10.3

_ Verification – After Running Utility


1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzjdh'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzjdh';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzjdh' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzjdh Program Name in the access method window.





Invera



50

6.2.11

Order Reservation Fix Utility – zzzors

6.2.11.1

_ Clean Up Order Reservations Conversion

This program will delete the leftover reservations that may have been created for release 0 for Closed

Blanked and/or Job Summary orders.


6.2.11.2

_ Run Utility




stxrun zzzors S


Return String: 0000

6.2.11.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzors'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzors';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzors' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzors Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select count (*) from ortorh_rec



Invera



51

Step Description where exists

(select * from rvtres_rec

where res_ref_pfx = orh_ord_pfx

and res_ref_no = orh_ord_no

and orh_ord_typ in ("B","J")

and orh_sts_actn = "C")




6.2.12

Check Print Tables– zzzcpt

6.2.12.1

_ Check Print Tables Conversion

This program will remove "T" type Check Printing records.


6.2.12.2

_ Run Utility




stxrun zzzcpt S


Return String: 0000

6.2.12.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzcpt'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzcpt';



Invera



52



3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzcpt' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzcpt Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select * from aptckh_rec where ckh_pmt_typ = "T";




6.2.13

Cleanup Form Attachments Utility – zzzfat

6.2.13.1

_ Cleanup Form Attachments Conversion

This program will delete orphaned imtepa/imtepc records for deleted Forms (inrfrm). It will move imtepa, imtepc and imtimg data for ‘inrfrm’ to the following new tables in STRATIX 9.2: imteac imteat imtima

This program will also verify and update the EAC-NBR-ATCH field in imteac.


6.2.13.2

_ Run Utility





Invera



53



stxrun zzzfat S


Return String: 0000

6.2.13.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzfat'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzfat';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzfat' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzfat Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select count(*) from imtepc_rec where epc_tbl_nm = "inrfrm" and epc_key_val not in (select frm_frm from inrfrm_rec); select count(*) from imtepa_rec where epa_tbl_nm = "inrfrm" and epa_key_val not in (select frm_frm from inrfrm_rec); select count(*) from imtepc_rec where epc_tbl_nm = "inrfrm" ;



Invera



54

Step Description select count(*) from imtepa_rec where epa_tbl_nm = "inrfrm" ;

The result of the above 4 sqls should be zero records



6.2.14

Cost Reconciliation HeaderUtility – zzzirc

6.2.14.1

_ Cost Reconciliation Header Conversion

The program will populate the value of CRH-BAL-QTY with the formula "[CRH-CST-QTY] minus [ ∑ CRP-

APLD-QTY] = [CRH-BAL-QTY]".


6.2.14.2

_ Run Utility




stxrun zzzirc S


Return String: 0000

6.2.14.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzirc'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzirc';





Invera



55

Step Description select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzirc' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzirc Program Name in the access method window.



6.2.15

Delete Image Files Utility – zzzdif

6.2.15.1

_ Delete Image Files Conversion

This program will delete image files from the $STRATIXDATADIR/images directory where the image files are no longer associated to a TRN transport record.


6.2.15.2

_ Run Utility




stxrun zzzdif S


Return String: 0000

6.2.15.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzdif'; select * from sctmsg_rec



Invera



56

Step Description where msg_svc_pgm_nm = 'zzzdif';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzdif' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzdif Program Name in the access method window.



6.2.16

Average Cost Pool Utility – zzzpcn

6.2.16.1

_ Average Cost Pool Conversion

This program will populate new fields ACP-TOT-WGT and ACP-TOT-BK-WGT on the Average Cost pool table (intacp).


6.2.16.2

_ Run Utility




stxrun zzzpcn S


Return String: 0000

6.2.16.3



1 Connect to the Primary database and run the following SQL statements via dbaccess:



Invera



57

Step Description select * from sctmsg_rec where msg_pgm_nm = 'zzzpcn'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzpcn';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzpcn' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzpcn Program Name in the access method window.


CREATE TEMP TABLE a251295_rec

(a251295_CMPY_ID nchar(3) NOT NULL,

a251295_AVG_CST_POOL decimal(10,0),

a251295_OHD_WGT decimal(12,2) NOT NULL,

a251295_BK_WGT decimal(12,2) NOT NULL,

a251295_TOT_QTY decimal(18,4) NOT NULL,

a251295_TOT_BK_QTY decimal(18,4) NOT NULL); insert into a251295_rec select prd_cmpy_id,

prd_avg_cst_pool,

sum(prd_ohd_wgt) PrdOhdWgt,

sum(prd_bk_wgt) PrdBKWgt,

sum(prd_ohd_qty) PrdOhdQty,

sum(prd_bk_qty) PrdBKQty from intprd_rec where prd_avg_cst_pool <> 0 group by prd_cmpy_id, prd_avg_cst_pool;



Invera



Step Description select a251295_CMPY_ID cmpy,

a251295_AVG_CST_POOL pool,

a251295_OHD_WGT pooltotwgt,

a251295_BK_WGT poolbkwgt,

acp_tot_wgt ACPTOTWGT,

acp_tot_bk_wgt ACPTOTBKWGT from a251295_rec, intacp_rec where acp_cmpy_id = a251295_CMPY_ID and acp_avg_cst_pool = a251295_AVG_CST_POOL and (acp_tot_wgt <> a251295_OHD_WGT or acp_tot_bk_wgt <> a251295_BK_WGT) and (acp_tot_qty = a251295_TOT_QTY and acp_tot_bk_qty = a251295_TOT_BK_QTY)


Page

58


6 If any data issues were found, re-run the utility by following the steps in 6.2.16.2.

6.2.17

Populate IED/IEP Utility – zzzieb

6.2.17.1

_ Populate IED/IEP Conversion

This program will build the initial data for the Inventory Summary tables inseid and insiep from the intied and intidp tables.


6.2.17.2

_ Run Utility





Invera



59



stxrun zzzieb S


Return String: 0000

6.2.17.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzieb'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzieb';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzieb' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzieb Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select * from insied_rec

Ensure the insied table exists. select * from insiep_rec

Ensure the insiep table exists.



6.2.18

Populate Turn & Earn Utility – sazted



Invera



60

6.2.18.1

_ Populate Turn & Earn Conversion

This program will build the initial data for the sasted table from the sasmsu table.


6.2.18.2

_ Run Utility




stxrun sazted S


Return String: 0000

6.2.18.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'sazted'; select * from sctmsg_rec where msg_svc_pgm_nm = 'sazted';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'sazted' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the sazted Program Name in the access method window.

4 Connect to the Information Warehouse database by running the following command: dbaccess $IW_DATABASE@$IW_INFORMIXSERVER

Run the following SQL statement via dbaccess:



Invera



61

Step Description select count(*) from sasmsu_rec

If the result of the above sql is greater than zero, then the result of the following sql should be also greater than zero. select count(*) from sasted_rec



6.3

6.3.1

Data Conversions – STRATIX/GL Databases

Create User roles Utility – zzzsur

6.3.1.1

Create User Roles Conversion

This program will create User Roles records (mxruro) based on the current data that exists in the scrslp, arrcra, plrrmg, scrbyr, zzzsur (which contains a copy of scrbrh data) and mxrofa tables. Only active records are considered . For the tables scrslp, arrcra, plrrmg, scrbyr – if there are duplicate records for a

LGN-ID, only one (the first one found) will be written to the mxruro table. Any other records that exist for the same LGN-ID in each table after the first, will be set to Inactive.


6.3.1.2

Run Utility




stxrun zzzsur S


Return String: 0000

6.3.1.3





Invera



62


1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzsur'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzsur';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzsur' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzsur Program Name in the access method window.



6.3.2

Default Document Printer Utility – zzzdpv

6.3.2.1

Default Document Printer Conversion

This program will leave the first active record found for the following fields as active and set any others for the same combination to inactive.

CMPY-ID

DOC-TYP = “PKL”

DIST-WHS


6.3.2.2

Run Utility






Invera



63


stxrun zzzdpv S


Return String: 0000

6.3.2.3



1 Connect to the Primary database and run the following SQL statements via dbaccess: select * from sctmsg_rec where msg_pgm_nm = 'zzzdpv'; select * from sctmsg_rec where msg_svc_pgm_nm = 'zzzdpv';


3 Run the following SQL statement via dbaccess: select * from sctslg_rec, sctmsg_rec where slg_pgm_nm = 'zzzdpv' and slg_clnt_host_nm = msg_clnt_host_nm and slg_clnt_tty_nm = msg_clnt_tty_nm and slg_clnt_pid = msg_clnt_pid and slg_clnt_dtts = msg_clnt_dtts and slg_clnt_dtms = msg_clnt_dtms order by slg_ssn_log_ctl_no, slg_ssn_log_seq_no, msg_msg_dtts, msg_msg_dtms;

Review the output to ensure that no errors were encountered. The session Log Inquiry program from the STRATIX menu can also be used to verify using the zzzdpv Program Name in the access method window.

4 Run the following SQL statement via dbaccess: select unique(ddp_cmpy_id||" "||ddp_dist_whs) from dsrddp_rec where ddp_bus_doc_typ = "PKL" and ddp_actv = 1; select count(*) from dsrddp_rec where ddp_bus_doc_typ = "PKL" and ddp_actv = 1 and exists (select * from scrcsc_rec

where csc_cmpy_id = ddp_cmpy_id) and exists (select * from scrwhs_rec



Invera




where whs_whs = ddp_dist_whs);

The results of the above SQLs statements should match.



Page

64



Invera


7.

POST-INSTALLATION PROCEDURE

7.1

Mandatory Procedure

7.1.1

Update the EP parameters in the IW database

This step is required to update the enterprise parameter data in the IW databases only for tables that have been updated in 9.2.

As the STRATIX user, key in at the command line: stx_iw_init -e -f iw-ep-data-92upg.ini

You will then be prompted, reply Y to continue. The following sample output will be displayed on the screen:

Starting program [stx_iw_init] at date Mon Jan 7 15:35:25 EST 2013

This script will drop any existing enterprise parameter tables and/or sales analysis transaction tables in the Information Warehouse database

[dinanew_iw@thimartrain] and recreate them

Are you sure you want to continue (Y/N) ? y

Resuming program ....

Locking and Deleting all records from sctpre_rec

Loading scrbrh_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading arrcra_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading scrslp_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading dsrddp_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading inrrdr_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading inrtdr_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading mxrofa_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading scrbyr_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading mxruro_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Loading plrrmg_rec from upg92a@aramupgpr to upg92a_iw@aramupgiw

Unlocking sctpre_rec

The IW Initialization [stx_iw_init] completed without errors at Mon Jan 7 15:35:42 EST

2013



Invera


7. Post-Installation Procedure Page

66

Log file: /workdir/livestx/stx_iw_init.20130107.1535.log

7.1.2

Run Post-Installation Script in both Primary and GL Databases

The following steps are mandatory and should be run for the STRATIX environment’s Primary and the

GL Database as well:


1 Ensure the environment’s STRATIX Application Servers are down.

Shutdown servers by issuing the following command stxshutdown –a

2 To create triggers and views, key in at the command line: stx_postinst

3 Verify log by running viewupglog viewupglog –t ERR –s stx_postinst –v 92

6 Boot servers by issuing the following command stxboot –a

NOTE: stx_postinst will automatically disable ‘Administration Mode’ for STRATIX and allow users to log in normally.

The following is an expected error from stx_rptg_prim_views.sql when running apvppt.sql. if

STRATIX/GL is not installed.

206: The specified table (glhglh_rec) is not in the database.


Error in line 40

Near character position 40

7.1.3

Update Statistics for Primary, IW and GL Databases

Update Statistics should be run in each database. This will update system catalog information which is used by the query optimizer for enhanced performance.



Invera


7. Post-Installation Procedure


1 Within dbaccess, run the following command:

update statistics

2 Repeat Step 1 for the IW and GL databases

7.2

Post-Installation Conversion Utility

7.2.1

New End of Period Control Record for Product Turn and Earn Report


1 Connect to the STRATIX application

2 Launch the Enterprise Parameters application from the STRATIX menu

3 Choose the System Common EP Grouping when the following window appears:

4 Choose End of Period Control:

Page

67

Add an entry in the 'End of Period Control as follows:

Program Name = inzies

Min Hrs before next run = 0



Invera


7. Post-Installation Procedure Page

68


Continue Script/Pgm Fail = 0 (unchecked)

7.3

Post-Installation Update

7.3.1

New Environment Variable for Email/Fax Prevention

The new DFE Environment Variable which, when set to Y, prevents email messages and faxes from being sent. This setting is typically used in Test/Train environments to prevent customers from being notified whenever test transactions are generated.


1 Login as the STRATIX user.

2 Review the .profile and the set_invera files for information on the following variable

STX_EMAILFAX

If STX_EMAILFAX=N, then set the DFE Environment Variable within the STRATIX application (continue with Step 3).

If the STX_EMAILFAX is not set, exit STRATIX the environment

3 Connect to the STRATIX application

4 Launch the Enterprise Parameters application from the STRATIX menu

5 Choose the System Common EP Grouping when the following window appears:

6 Choose Environment Variable:



Invera


7. Post-Installation Procedure


Page

69

Add an entry DFE as follows:

Identifier Value = Y



Invera


8.

PRINT OPTIMIZER UPGRADE


1 Log on to the Print Optimizer as the local administrator.

2 Insert the ‘STRATIX Windows Components’ CD into the CD-ROM drive and run setup.exe.

3 Click on ‘Next’ to start the upgrade of STRATIX

4 Once the InstallShield process has completed the following two screens will appear. Reboot the client device when prompted to do so.



Invera


8. Print Optimizer Upgrade


Page

71

5 After the system reboot, follow the on screen instructions to complete the upgrade.



Invera


STRATIX_Upgrade_Guide

STRATIX 9.2

STRATIX UPGRADE GUIDE

Table of Contents

OVERVIEW

1.1

Upgrade Guide Modification History

1.2

Introduction

1.3

Critical INVEX-CUSTOMER Changes

STRATIX 9.2 UPGRADE PRE-REQUISITES

2.1

Verfication of Third-Party Software

2.2

STRATIX Software Related Pre-Requisites

2.3

Logistical Issues

2.4

Upgrade Checklist

STRATIX OVERVIEW & PLANNING

STRATIX SERVER UPGRADE

4.1

Loading Software

4.2

Conversion Program Update

4.3

STRATIXfinreps Software

4.4

Updating Configuration Files

4.5

Database Changes

4.6

Backup Upgraded Database(s)

STRATIX CLIENT UPGRADE

5.1

STRATIX Client update via CD

5.2

STRATIX Client update via Insync

DATA CHANGES & CONVERSIONS

6.1

Boot STRATIX Application Servers

6.2

Data Conversions – STRATIX Databases

6.3

Data Conversions – STRATIX/GL Databases

POST-INSTALLATION PROCEDURE

7.1

Mandatory Procedure

7.2

Post-Installation Conversion Utility

7.3

Post-Installation Update

PRINT OPTIMIZER UPGRADE

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib