Upgrading to v352

Hi all,


Here is a brief document on upgrading to v352.  It is a collection of hints
and problems you may encounter whilst performing this task.

System Manager:
If wanting to go to Version V3.5.2b, upgrade System Manager first (it runs
independently to the applications and can be a higher version without
problems, System Manager V3.5.2 has a great utility /
command called AMINSAPP to help create upgrade other named environments.
You can upgrade System Manager at any time provided NO users are logged into
S/21 and the scheduler and all S/21 subsystems have been brought down.


Using AMINSAPP to help create a new environment:
This is similar to the tried, proved and loved AMINSTALL command used to
initialise applications when first installed (adds menus, tasks, adds
library lists for the application and changes other library lists to use the
libraries just installed).

AMINSAPP basically helps you create a new environment (eg 'UPG' could be the
suffix and environment code for the upgrade duplicate environment, or you
may use 'TST' for testing environment). Simply restore your OSLxxF3
libraries to be renamed during the restore to OSLxxF3UPG, where xx is any
application you have installed. The environment code is/must be the last 3
characters of the library name, remember the production environment is
called
the "blank" environment ('   ')? Now restore the OSLxxS3, OSLxxP3, OSLxxD3,
OSLxxI3, OSLxxQ3 libraries from the Silver copy CD for the target version
(ie V3.5.2b) also being renamed during the restore to become OSLxxS3UPG,
OSLxxP3UPG, OSLxxD3UPG, OSLxxI3UPG, OSLxxS3UPG etc. Once the libraries exist
with the suffix 'UPG' or 'TST' (your choice) call AMINSAPP from a command
line, follow the prompts and make sure you use the AUTOMAP function which
automatically uses the environment code entered (again 'UPG' or 'TST' in my
example) with the library names having that suffix, and generates this
environments menus, tasks, library lists for you.

Of course you can use complex SQL statements over the APG25PHY, APG26PHY,
APG51PHY, APG61PHY, APG62PHY and APG63PHY.

The environment is not necessarily ready for use, but you have a duplicate
database setup with all menus, etc. Apply the PTF's (in your UPG or TST
environment) for the FILES only (in the UPG / TST libraries), from you
current version up to your target version, to complete your test/upgrade
environment. No level checks exist as all libraries are now at your target
version. Your current LIVE version is still intact and being used!

We found you will need to then update all the data areas in the OSLxxD3UPG /
TST or OSLxxP3UPG /TST libraries if going up a few versions as the
background processing programs may have changed as well, so they may fail if
you were (say) trying to update V3.5.2b G/L sessions using your current
v3.4.x or V3.5.0 background processing programs in subsystem GLBACK3 instead
of GLBACK3UPG. You need to look for and change the JOBQ, JOBD, CLS and SBSD
to use xxBACK3UPG instead of xxBACK3 (where xx = any application code using
it's own subsystem). You will need to remove job queue entries (RMVJOBQE)
and add new enrties (ADDJOBQE) for the OSLxxD3UPG/xxBACK3UPG subsystem
descriptions, if you do a display of the sbsystem descriptions first, you
can print the screen to refer to for the correct sequence numbers to use and
pool id's needed to add the new entries.

For example - G/L
CHGDTAARA (OSLGLD3UPG/GLSBSDTA ) positions 8 - 10 need to be 'UPG' if that
is the environment.

RNMOBJ (OSLGLD3UPG/GLBACK3) type *JOBQ to be GLBACK3UPG.
RNMOBJ (OSLGLD3UPG/GLBACK3) type *JOBD to be GLBACK3UPG.
RNMOBJ (OSLGLD3UPG/GLBACK3) type *CLS to be GLBACK3UPG.
RNMOBJ (OSLGLD3UPG/GLBACK3) type *SBSD to be GLBACK3UPG.

CHGJOBD (OSLGLD3UPG/GLBACK3UPG)and prompt to
 -      change all libraries to have suffix 'UPG'.
 -      change JOBQ OSLGLD3/GLBACK3 to OSLGLD3UPG/GLBACK3UPG.

Use DSPSBSD (OSLGLD3UPG/GLBACK3UPG) to retrieve the correct sequence number
and pool id for the following commands.
RMVJOBQE SBSD(OSLGLD3UPG/GLBACK3UPG) JOBQ(OSLGLD3/GLBACK3)then add the new
entry -
ADDJOBQE SBSD(OSLGLD3UPG/GLBACK3UPG) JOBQ(OSLGLD3UPG/GLBACK3UPG)

RMVAJE SBSD(OSLGLD3UPG/GLBACK3UPG) JOB(GLUPDATE)
ADDAJE SBSD(OSLGLD3UPG/GLBACK3UPG) JOB(GLUPDATE) JOBD(OSLGLD3UPG/GLBACK3UPG)

RMVRTGE SBSD(OSLGLD3UPG/GLBACK3UPG) SEQNBR(9999)
ADDRTGE SBSD(OSLGLD3UPG/GLBACK3UPG) SEQNBR(9999) CMPVAL(*ANY) PGM(QCMD)
POOLID(2) >Check poolid!


This then needs to be done for PL, SL, CS, AO, FA (if used), IN, MJ (if
used), WH (if used) and there may be more I have not used at a customer
site! Check all data queues in all D3 & P3 libraries as WH uses P3 lib, not
D3!!!!!!



Service Packs:
When upgrading to version 3.5.2b, always load Service Packs 1 & 2 as a
minimum.If using STYLE, you have to be on V3.5.2. as a MINIMUM with any
service
packs, preferably V3.5.2b with SP's,  this will correct some "interesting
challenges" to your programmers. If using manufacturing, a manufacturing
allocations problem (negative enhancement introduced in V3.5.0)is corrected
in Service Pack 3.

Financials V3.5.2b without service packs has a Y2K problem in manual journal
postings for A/R. the century code ('1') is lost so all you journals are for
1900 not 2000,
entries show 90+ days on statements even if they were entered for the
current period and all dates show as correct on the displays and files.
Supposedly fixed in SP1.


WORKFLOW trap when upgrading:
An interesting pre-requisite to upgrading to V3.5.1 (or base V3.5.2 sorry I
can't remember exactly) or above is the need to create an empty Work Flow
application library OSLWFF3 (even if you are not going to use / attempt Work
Flow) and the mandatory application of the Workflow PTF's creating the
application and modifying your library lists accordingly. This Workflow
library will be used by the PTF that should create it(WF PTF # 1). The PTF
will fail if OSLWFF3 does NOT exist and come up with a warning / error
message if it does exist. When installing the PTF's, ignore the warning
message and you will install successfully. Don't create the library and the
PTF's fail, with the result that invoicing will not work in Advanced Order
Entry as the programs will check for files in this library, and fail / dump
if the library / files don't exist stopping, invoices being printed.


What is V3.5.2b Service Pack 3?:
The service packs for V3.5.2b(mainly SP3) constitutes what we believe should
have been
V3.5.3 or V3.6.0 but JBA/GEAC decided against releasing it as a new version.
Always apply ALL the PTF's across all
applications installed if not well practised in the art of PTF review and
application, there is always a link or dependancy you may miss by reading
the manual (ie SP3 manufacturing has new files dependencies, required from
the inventory PTF's where they are created)


Hope this helps

Paul Steel
Managing Director
Steel Technology Pty Ltd

Sydney: PO Box 723 Brookvale NSW 2100
Melbourne: PO Box 846 Boronia Vic 3155

+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---