Hi Tony,
(I don't think this deserves the <AD> code but it's up there anyway to keep
the msg police happy. If someone else really wants this information but
doesn't read it because of the <AD>, then they deserve to remain less
informed - imho - no flames please)
We distribute our generic Pick print spooler, SpoolerPlus, to Universe/NT,
Universe/.nix, Unidata/NT and Unidata/.nix databases and have resolved some
of the same challenges that you are facing in the following ways.
First, you need to determine if Universe/Unidata object code is compatible
across all the releases that you will install on both now and in the future.
We don't know the answer to that question, so we install only BASIC source
code and then compile and catalog all BASIC programs on the target machine
to ensure that the object code is compatible with the underlying database.
We also leave the source on the customer's machine so that any changes that
need to be made (to fix a bug, to remain compatible with new versions of the
database or to move the software to an upgraded version of the datbase or a
different database) can
be done either by us or by the customer.
Second, you need to decide if your product will reside only in one account
or will also be installed directly in other accounts. If any parts of it
will actually be copied into another account (other than catalog pointers or
Q-pointers), then those parts of it will need to be configured per that
other account's flavor (which you probably won't know, or will need to
change their flavor (from within a
program, for example) when it is compiled.
If your software resides only in one account, then it doesn't matter what
flavor you use in your account. The processes in your account can be
executed from other accounts (of the same or different flavors) without a
problem.
What you don't know that does make a difference, however, is where in the
disk architecture your customer will choose to locate your account - eg.:
C:\IBM\UV\youraccountname
C:\IBM\UV\ACCOUNTS\youraccountname
or on the D drive or the F drive or any drive.
And, you don't know where the other application accounts, if any, reside,
from which your customer will want to run your software.
You also may not know if your customer wants to install your software in all
application accounts or just some of them.
To enable our customers to install SpoolerPlus anywhere that can be found
using a complete path, we catalog all programs COMPLETE (in Universe) and
LOCAL (in Unidata) to create a complete path pointer in our account VOC
which automatically reflects where the account is located and that can be
copied into the VOC of any application account wishing to use SpoolerPlus,
overwriting catalog pointers in the application account but not overwriting
commands of the same name in the Global object code directory.
We use Q-pointers with our account name and file names that are resolved
thru the UV.ACCOUNT file in the UV account for installing all other items in
an application account.
Next, I suggest that you use Type 19 files for your BASIC program source
code, because Type 1 file Item ID's are limited to 14 chars in Universe.
Also, you should turn LONGNAMES ON in your account and in every application
account.
So far, we have not found any Universe or Unidata commands that behave
differently in different releases of the same database on the same operating
system.
But, there are differences between the behavior of Universe commands on NT
vs on AIX, so you need to structure your code so that it is operating system
sensitive.
There are also differences between the same commands in Universe and in
Unidata, so you need to take that into consideration.
In our latest release of SpoolerPlus, we added a config. item to the INCLUDE
file and merged the 4 different versions of each of the same programs into
one, with CASE statements, so that the config. item can be customized for
the database/operating system of the target system and the same BASIC
programs compiled to run on that target system regardless of the database or
the operating system.
As far as the structure of the delivered product is concerned, I have been
warned against copying a Windows folder/with subfolders from Windows to any
other operatating system.
I am also concerned that the target account VOC will be damaged unless I
start with a locally created account and then add my stuff to the VOC.
So, we use mvInstaller, from Brian Leach in the UK, to ship and install our
product. It has both a graphical and a character-based user interface and
the character-based interface runs on both Universe and Unidata and on all
the operating sytems that they run on.
It allows you to create a script that creates files, load them, compiles
and catalogs programs, runs processes in the VOC, etc,. to automate the
entire installation process.
We are not reseller's for mvInstaller, but I do recommend it (Brian is also
our representative for SpoolerPlus in the UK).
This covers the major areas that we have found challenging in distributing
SpoolerPlus.
Please call or email me if you have any additional questions or just want to
discuss alternatives.
Best wishes for the success of your new product.
Rgds,
Dave
Dave Taylor
Sysmark Information Systems, Inc.
Authorized IBM Business Partner
49 Aspen Way
Rolling Hills Estates, CA 90274
(O) 800-SYSMARK (800-797-6275)
(F) 310-377-3550
(C) 310-561-5200
www.sysmarkinfo.com
----- Original Message -----
From: "Tony G" <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Thursday, January 03, 2008 2:43 PM
Subject: [U2] Deployment of software for UD and UV
<snip>
Thanks!
Tony Gravagno
Nebula Research and Development
TG@ always.remove.this.pleaseNebula-RnD.com
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
