Decision Analytics. Integrating Lawson with the real world.
The LawsonGuru Letter

 

  

November 2002

The LawsonGuru Letter is a free periodic newsletter containing provocative
commentary about issues important to the Lawson Software community.

The LawsonGuru Letter is published by-and is solely the opinion of-John
Henley of Decision Analytics.
 
Visit Decision Analytics at http://www.danalytics.com.
For subscription information, see the bottom of this message.
 
The LawsonGuru Letter is not affiliated with Lawson Software.
In this issue:
1. Making the tough Go/No-Go Decisions
2. Focus: How Shall I Print Thee?
3. Support Decommission of NT4 Environment
4. Reader feedback
5. Survey results
6. Lawson tips & tricks
  • 1. Making the Tough Go/No-Go Decisions
    There was an interesting article in the Washington Post (10/13/02)
    recently about the abandoned conversion of the DC government's
    payroll system. If you live in the DC area, you may remember a
    few years ago when this system was being cutover--there were
    stories in the paper and on the local TV news about people not
    being paid, and how the system was a mess, etc. etc.

    In a nutshell, they've spent $20 million to replace their
    33-year-old system, and have decided to just keep using the
    old system.

    That's were it gets interesting. An additional $14 million
    has been spent moving BACK to the old system. What started out
    as a $900,000 contract to a local IT contractor has mushroomed;
    the original contract did not have to go through the normal
    purchasing approval process. The contractor got the job by
    "low-balling" (and thereby bypassing the approval process).

    Then, they just kept expanding the scope and getting incremental
    change orders.

    Oh yeah, and the guy who recommended the company in the first
    place-he's now working as a consultant for the IT contractor.

    This story got me thinking about system migrations and how
    painful they can be--both for those directly involved and for
    those affected by the conversion. In particular, the "Go-No-Go"
    decision can sometimes be the toughest decision that a manager
    makes in their entire career.. Although the "un-conversion"
    was poorly handled, the DC government's decision to abandon
    their conversion wasn't necessarily the wrong one.

    Think about a cutover decision you have looming front of you,
    or one you've made recently.

    Have you addressed every major issue? Do you have a systematic
    way to assess go-live readiness and reduce potential risks? Do
    you understand the system's impact on its users? By "users",
    I don't just mean the actual end-users of the system. I'm
    talking about everyone who's affected by the system conversion:
    employees, customers, vendors, etc. Have you communicated on
    a regular basis with them to let them know they may be affected?
    Have you set a special means (i.e. toll-free number, web pages,
    email addresses) for them to communicate and resolve any problems?

    Sometimes the best decision during the conversion is not to
    convert at all. I consulted with an organization that ended
    up filing for bankruptcy 18 days after converting, and had to
    run and support BOTH systems for another year before they
    finally liquidated. Had someone made the tough call to pull
    the plug on the conversion, they could have saved themselves
    (and their creditors and shareholders) a lot of time and money.

    Sometimes a delay (or switching from a full cutover to a
    piecemeal migration) helps to solidify everyone's product
    knowledge and the user community's confidence in the new system.
    Sometimes the impact is so profound that you simply can't cut
    over everything at once. I consulted with an organization that
    was migrating their timekeeping system as well as their payroll
    system. I wrote a program to convert their timesheets from the
    old timekeeping system to their new system, so they didn't have
    to re-enter the timesheets during parallel testing (we knew that
    part of the new system worked). This ended up working so well
    that they went live with the new payroll system, but kept their
    old timekeeping system running for another 6 months until they
    could re-energize and focus on the conversion of the timekeeping
    system.

    In your conversion efforts, make sure you're making an informed
    go-live decision. Anyone who's charged with making the "do we
    or don't we" decision needs to have HONEST input from his/her
    team, including the consultants. If it's not going to work,
    speak up!
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    J2EE vs. .NET
    -------------
    According to a study of developers by Evans Data,

    40% are using .NET
    51% are using Java 2 Enterprise Edition

    However, this will change in the next year:

    63% will be using .NET
    61% will be using J2EE

    Source: Infoworld, 10/14/02
    http://www.infoworld.com/articles/hn/xml/02/10/14/021014hnbriefs.xml
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    2. Focus: How Shall I Print Thee?
    Recently, while explaining Lawson printing solutions to a client,
    I realized how complicated and confusing this can be, particularly
    when you are running on a UNIX server. This applies somewhat to
    NT clients, although it's a little easier. My apologies to AS/400
    users: I must admit that I'm "AS/400-challenged".

    Printing is easy if all you are running is LID. Your "send to
    printer" commands map to server-based printers. Any printer that
    you can "ping" from the server can probably be set up as a Lawson
    printer. If you're running the Lawson NT Environment, these commands
    are mapped to any printer addressable by the Windows 2000 Server.
    On UNIX servers, these commands are commonly mapped to UNIX lp/lpr
    printer commands. You still have to navigate firewalls and VPNs
    if your printing across the country, but it's still manageable.

    However, new challenges arise if you're using Lawson via a browser,
    for SEA tasks, for XML User Interface, and/or Portal. Specifically,
    XML and Portal add a new feature when viewing a report. In addition
    to printing via the Lawson server to a Lawson-defined printer, you
    can also view the report as an Adobe PDF, which XML/Portal "renders"
    on-the-fly for viewing in the browser.

    So--depending on the task--you may be printing to a locally-connected
    printer (i.e. clicking the print button on your browser's toolbar),
    or you may (sometimes unknowingly) be printing remotely via the
    Lawson server to a Lawson-defined printer.

    Some examples:

    Requisitioner: Using SEA, when you print a requisition, it is
    routed to a Lawson-defined remote printer. You can also view the
    RQ111 output in the XML/Portal print manager and render it as a PDF.

    Requisition Approvers: Uses SEA for approve/reject, however SEA
    lacks an unrelease function, so you have to use use XML/LID/Portal
    to unrelease. Print via LID to Lawson-defined printer; via XML/Portal,
    use PDF option to print to local printer.

    PO Entry: View and print individual POs to Lawson-defined printer;
    Print batch POs to Lawson-defined printer. Optionally, view in
    XML/Portal, and use PDF option to print to local printer

    General User: Use XML/Portal feature to print via PDF to locally-connected
    printer. Unless report is large--then print to Lawson-defined remote printer.

    Add in the requirement for running checks, customer invoices/statements,
    delivery tickets, POs, and requisitions through server-based rendering
    software (like MHC or Formscape), and you can see that this "freedom of
    choice" gets confusing real fast! You really need to create a task-based "roadmap", so that you can explain to a specific user how to print each
    particular type of output.

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Cited as the top frustration in Customer Relationship Management (CRM)
    integration: "difficult integration" (39%)

    Infoworld, September 2, 2002
    http://www.infoworld.com/features/fecrmint.html
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  • 3. Support Decommission of NT4 Environment
    A number of clients were taken by surprise by Lawson's recent "decommission"
    announcement for Lawson Environment on the Microsoft Windows NT 4.0 Server
    platforms, effective January 1, 2003. This affects both the Lawson
    Environment, as well as Logan/IOS remote web servers.

    Lawson has since clarified this, and the upshot for Lawson clients still
    running NT is this: migrate from NT4 to Windows 2000 Server as soon as
    practical. Lawson will continue to support the Lawson Environment on NT
    until September 2003. However, Lawson issues or patches that require
    additional support or patches from Microsoft will likely require additional
    paid support from Microsoft.

    Read Lawson's revised decommission letter here:
    http://support.lawson.com/com/db_os_decom_092402_101402.pdf

    Read Lawson's clarification here:
    http://support.lawson.com/com/db_os_decom_clarify_letter_101402.pdf

    In October 2001, Microsoft announced their plans for retiring support
    for Windows NT. Beginning January 2003, they will begin providing only
    limited support for NT. In other words, if you need extra support, or
    "hot-fixes", you will likely have to pay for them. See http://www.microsoft.com/ntserver/ProductInfo/Availability/Retiring.asp.

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    - QUOTE OF THE ISSUE -
    "Computers make it easier to do a lot of things, but most of
    the things they make it easier to do don't need to be done."
    - Andy Rooney
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  • 4. Reader feedback

    I got some interesting feedback on last month's article on purchasing
    cards. One reader "scolded" me for not knowing that p-cards are a
    requirement for DoD contractors on purchases of less than $2500
    (http://www.acq.osd.mil/sadbu/compliance/jul.htm), and therefore
    that Lawson should have a ready solution. I explained that Lawson's
    client base is widely varied, and that government contractors make up
    only a small percentage.

    The prevailing response was that p-cards are an invitation for fraud,
    and that--although required by DoD for small purchases--p-cards have
    hardly been a resounding success.

    One reader relayed his consulting experience about a regional transit
    agency purchasing rail cars on p-cards to circumvent the purchasing
    approval process!

    This coincides with a recent news story on p-card abuses
    (http://www.wtopnews.com/?sid=9999&nid=116). Seems that certain Navy
    personnel were using p-cards for questionable purchases (see the
    story for details), including to "hire prostitutes at brothels, buy
    jewelry, gamble and attend New York Yankees and Los Angeles Lakers
    games".

    The Pentagon, of course, has promised to mend its ways, however the
    focus is on "after-the-fact" audits and reconciliation. No mention
    of a system to prevent fraud before it happens.

  • +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Worthwhile Reading:
    First-hand accounts by some of our most successful entrepreneurs, including Fred Smith (FedEx), Al Neuharth (Gannett...and fellow Lawson client!), Richard Thalheimer (The Sharper Image), Donna Dubinsky (Palm/Handspring) and others.
    Fortune Small Business, October 2002
    http://www.fortune.com/sitelets/innovators/full_list.html

    Integrating warehouse management systems (WMS) with your other back office systems is not easy. It's even harder when you have more than one WMS. Learn more about standardizing and other best practices.
    CIO, September 15, 2002
    http://www.cio.com/archive/091502/order.html

    Built for Speed: Executive dashboards are a requirement for intelligent organizations.
    Intelligent Enterprise, September 3, 2002
    http://www.intelligententerprise.com/020903/514feat3_1.shtml

    Food Fight: Bet you didn't know that Wal-Mart is the US's top grocer. Learn how the competitors are trying to keep up.
    CIO, October 15, 2002
    http://www.cio.com/archive/101502/food.html

    Virtual Close: Not So Fast
    Companies once assumed they'd be able to close their books in a day, but that goal has proved surprisingly elusive.
    CFO IT, October 23, 2002 http://www.cfo.com/article/1,5309,7884,00.html
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    5. Survey Results
    Frankly, I was very disappointed by the lack of response to last
    month's survey, which asked, "Was Lawson better off as a private
    company?"

    Out of over 600 subscribers, only a handful responded. This tells me
    that 1) no one has an opinion (I hope not!), 2) nobody reads this
    (again, I hope not!), 3) you fear having your opinion exposed, or
    4) what difference does it make?

    Of those who responded, all but one agreed that Lawson was better
    off before their IPO.

    The lone dissenter--a "maybe"--put it this way:

    "Down the road, we'll ask ourselves "did Lawson penetrate new
    markets, deliver its next generation products, and lead the sector
    with innovative solutions? If the answer is "yes", then the IPO
    was worth it."

    Well put. If you'd still like to respond, send me your vote and
    any thoughts to mailto:survey@lawsonguru.com.

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    Remember to VOTE on November 5th! It's your civic duty.

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    6. Lawson Tips & Tricks
    By the way, if you have a tip you'd like to share, send it to
    mailto:tips@lawsonguru.com.

    a. If you're running a Unix/NT version of Lawson, you can use the
    'nohup' command to make your admin tasks a little easier. If you've
    ever had to fight a noisy phone line during a remote dbreorg, you'll
    appreciate this command:

    nohup dbreorg productline > dbreorg.log 2>&1 &

    - The nohup tells command processor to ignore hangup signals (SIGHUP)
    - The first redirection ">" captures Unix stdout to log file
    - The second (2>&1) captures stderr (which catches Lawson error
    messages)
    - The final & tells command processor to run detached (i.e. background).

    If you log out or are disconnected from your current session, the command
    will continue to run, and you can periodically check dbreorg.log.

    If you log out and have nohup'ed jobs running when you logout, you will
    be warned "You have jobs running". Simply logout again, and your
    background jobs will continue to run.

    You can also use this technique for impexp, expsysdb, etc.

    b. With Internet Explorer, pressing Ctrl+N will open a duplicate
    window (i.e. second browser window, opened to the same URL/form).
    This gives you the same functionality using Portal or XML User
    Interface as pressing F10 in LID.

    c. If you're running Unix or NT, here's how to call an operating system
    command from inside a Lawson COBOL program (this is an example to move
    a file):

    Put something like this in your WS:

    02 WS-CMD-MOVE-REPLACE.
       03     FILLER       PIC X(06) VALUE "sh -c ".
       03     FILLER       PIC X(01) VALUE x"22".
       03     FILLER       PIC X(03) VALUE "mv ".
       03     WS-FROM-FILE PIC X(50) VALUE SPACES.
       03     FILLER       PIC X(01) VALUE SPACES.
       03     WS-TO-FILE   PIC X(50) VALUE SPACES.
       03     FILLER       PIC X(01) VALUE x"22".
       03     FILLER       PIC X(01) VALUE x"00".

    And this in your PD:

        MOVE "File1"     TO WS-FROM-FILE.
        MOVE "File2"     TO WS-TO-FILE.
        CALL "system" USING WS-CMD-MOVE-REPLACE.

    If you're running NT, remember that you're actually calling the MKS
    toolkit, so you'll need to use Unix-style commands.

    • The LawsonGuru Letter is a free periodic newsletter containing
    provocative commentary about issues important to the Lawson Software
    community. The LawsonGuru Letter is published by--and is solely the
    opinion of--John Henley of Decision Analytics.
     
    Visit Decision Analytics at http://www.danalytics.com.
    To subscribe, send an email to: mailto:letter-subscribe@lawsonguru.com
    To be removed from the subscription list, send email to:
    mailto:letter-unsubscribe@lawsonguru.com
    © Copyright 2002, Decision Analytics. All rights reserved.
     
    Please share The LawsonGuru Letter in whole or in part as long
    as copyright and attribution are always included.
    Decision Analytics is an independent consultancy, focusing on Lawson
    technical projects, and specializing in customization/modification,
    data conversion, and integration/interfaces (including BCI/Mercator).
    Please visit http://www.danalytics.com for more information.
    Decision Analytics. Integrating Lawson with the Real World.