Re: Fw: Clarification - confused consultant

[rob@xxxxxxxxx]

Andy,

This is what would happen.  Your SEU developers would either not use that 
bif or would let SEU flag it as an error but save and exit SEU anyway.

This is what I suggest.
1 - Get your developers high performance laptops.  New policy states that 
they must have laptops.  Laptops must be taken home at night as part of 
the disaster recovery policy.
2 - When tech support loads laptops ensure that latest RDi is loaded with 
all appropriate fixes.
   2a - If you are using a Change Management package ensure that their 
interface into RDi is loaded also.
3 - Schedule Jon Paris and/or Susan Gantner to come on site and spend a 
week training them in RDi.  Their brand new wireless enabled laptops could 
be lugged into a common conference room for the training session. Schedule 
this around the time of your LUG meeting.  See if you can con one of them 
into spending one of the nights giving a presentation at the LUG (let them 
know in advance).
  3a - If you are using a Change Management package, it might not be a bad 
time for a refresher course in that, including a how to use their software 
in RDi.
4 - Secure, rename or delete the command STRSEU immediately after, if not 
during, the training.  For a minimum of 30 days, if not permanently. Force 
them to grunt through the learning curve.  For the BS excuse of the 
emergency project, tell them there's always EDTF.  Securing the command 
may not be enough if you're like some shops where developers have *ALLOBJ, 
or where developers are quite clever with the Change Management software 
to whip up an adopted authority program to get to STRSEU.



Rob Berendt