Re: The "standard" environment

Chris,

OH MY GOD!  You have GOT to be kidding me.  We are no
where near April Fools Day.

I am deadly serious when I say that the person who
told you this needs to be identified and reported to
their supervisor at GEAC for telling you this.  They
need to be stopped before they hurt someone!

This person is so severely misinformed that they are a
danger to the customer base.  If anyone on this list
has received similar advice, and are following it, you
need to seriously consider the ramifications.

If you follow this person's advice you might just as
well stop paying maintenance because you'll never want
to apply any more PTFs that make any changes to the
Application Definitions, Library Lists, Tasks or
Menus.

You should NEVER make any changes to the STANDARD
Application Definitions, Library Lists, Tasks or
Menus.  And if you have modified the source don't
store it in the Standard library.  (I didn't think I
would have had to make such an obvious statement but
given the content of this discussion I am loath to
leave even the most obvious comment unsaid.)

Unbelievable.


~~~~Original message~~~~

"Chris Tringham" <ctringham@xxxxxxxxxxx>
Sent by: "System 21 Users"

Long ago, I was persuaded that the correct way to set
up S21 was to leave
the blank environment totally alone.  Any changes (to
library lists,
tasks, menus) would go into the appropriate
environments.  This advice is
repeated in the "redbook" that came out 3-4 years ago.

Now, Geac are saying that this is not the way to go. 
Instead, any new
tasks should be created in the blank environment and
library lists should
be amended in the blank environment.  They say that as
long as you use
library mapping and follow their standards for
customised tasks everything

will be fine, and that this setup is easier to
maintain and understand.
No need to define the applications in your "standard"
environment because
you don't need them - you can use the blank
environment.

There are some obvious benefits such as not needing to
authorize users to
both the blank and standard environments.  However, I
still have some
doubts, but I am not sure whether I have just been
thoroughly
indoctrinated in the old way of thinking and just
can't think straight.

For example, if I want to change certain jobs to run
in different job
queues, I can change the task definition in the live
and/or test
environment and it works fine, but I haven't touched
the standard
definition.  If I make changes like that in the blank
environment they may

get overwritten by a PTF or new release.  Or is there
some smarter way to
achieve the same thing?

Any thoughts?  And have Geac announced this change in
thinking somewhere
that I haven't noticed?





                
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail