RE: IBM i work management

Good point regarding customization. Here, all customization (like changing the default value of a command) are applied by a CL program. This CL is call by the startup program so that all changes get applied after any IPL. This way, we never forget.


Denis Robitaille
Chef de service TI - Solution Entreprise
Infrastructure et Opérations
Cascades Centre des technologies,
412 Marie Victorin
Kingsey falls(Québec) Canada J0A 1B0
T : 819 363 6130



-----Message d'origine-----
De : MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Jim Oberholtzer
Envoyé : 7 avril 2016 12:57
À : Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Objet : Re: IBM i work management

The procedure works really well for the database servers. One caveat: Make sure to document it properly! I've had system conversions and recoveries that have not gone well because the one person that knew about things like that was not available or just plain forgot.

I almost always set up a CL program that holds any and all changes I make to the system, one to document it, and two, so I can just run that program and reset all the customization. Yep, that program sometimes gets a bit cumbersome but you can guess how many times it's saved a world of hurt at three in the AM.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects

On Thu, Apr 7, 2016 at 11:42 AM, Englander, Douglas < Douglas_Englander@xxxxxxxxxxxxx> wrote:

Jim,

It sounds like the QSYS2.SET_SERVER_SBS_ROUTING() procedure will allow
me to do what I need to do. Since the routing procedure will only work
for database servers, I assume by that statement that the procedure
does not impact/work for QINTER and traditional green screen
applications. Is that correct?

I will look into your session presentation, as one of my coworkers did
attend COMMON last year.

Thank you,

Doug

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.