RE: An opinion please (ordering of command parameters)

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Take a look at the OS's CPYLIB ordering. Consistency is usually a good
thing.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com

-----Original Message-----
Subject: An opinion please (ordering of command parameters)

I'm working on a utility that will update a "application environment" 
library by pulling in file definitions from another environment library 
(the "source" library, usually a "test" version of the application 
environment) and applying them to the existing data in the "target" 
library (usually a "production" version of the product environment).

Scenario: Universal Foobar has been running the application on the 
environment in the FOO_PROD library for some time, but they have 
prepared an improved version of the database, and have been running 
tests on a modified version in the FOO_TEST library. They are now 
satisfied that the environment as defined in FOO_TEST is going to work 
as advertised, and want to put that version into production.

So for this utility that programmatically upgrades FOO_PROD to the new 
data definitions in FOO_TEST, should the command be

UPDATEFOO FOO_TEST FOO_PROD

or should it be

UPDATEFOO FOO_PROD FOO_TEST

???

--
JHHL