Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

LID command output redirection

 6 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
mikeP
Veteran Member
Posts: 151
Veteran Member
6/26/2014 12:13 PM

    I'm trying to see all the environment variables available in LID.  Normally you can redirect the output of command to a text file using the redirection operator ">" or pipe it to LASHOW.

    However, SET, which displays the environment variables, is a Windows command and gives an error in LID when I try to pipe or redirect, and the output scrolls of the screen.

     

    We are hosted, and cannot log into the Lawson Windows server directly, LID is our only interactive interface.

    Any ideas on how to capture the output from SET so I can see all the variables?

     

    Brian Allen
    Veteran Member
    Posts: 104
    Veteran Member
    6/26/2014 12:22 PM
      If you have access to the Windows command cmd.exe, try double clicking the top left of the Windows command window to get the menu, select Edit | Select All, then Edit | Copy, it should capture all output for that session.
      Brian Allen
      Veteran Member
      Posts: 104
      Veteran Member
      6/26/2014 12:32 PM
        We're on UNIX, but the following command works fine with LID for me:
        set > filename.txt

        You may want to check with your hosting provider to see why this is not working or if they can provide another interface like PuTTY.
        mikeP
        Veteran Member
        Posts: 151
        Veteran Member
        6/26/2014 12:35 PM
          Because we're hosted we don't have interactive accounts on the Lawson server, and I can't log in to the server to get a cmd.exe Window.

          I can run cmd.exe from the LID command line, and I tried it with the /k switch:

          d:\lawprod\launt\4JLSFPROD_PALANDRI> cmd.exe /k set > junk.txt

          but that just hangs the LID session.
          Kwane McNeal
          Veteran Member
          Posts: 479
          Veteran Member
          6/27/2014 5:06 PM
            MikeP,
            First, the reason 'set' works for Brian, is that it is a built in to the ksh shell, and ksh properly manages file handle redirection. This is NOT true for 'lashell'.

            The way lashell works is it attempts to determine if a program is an incompatible program (such as more), an extension inside 'cmd.exe' (such as 'set'), or a 'safe' program, then setups an environment to respond, by either blocking the program, launching an in-memory copy of 'cmd.exe', or allowing the program to execute.

            What you are most likely encountering is that since you don't have access to OS, the provider has placed a Group Policy in-effect disallowing 'cmd.exe' from running. Normally in that situation, if you had an interactive session (aka a WinStation for a desktop to run in), you'd see a pop-up telling you cmd.exe was disallowed, but since lashell runs from lainetd's WinStation, there is nowhere to pop that box up at.

            Ultimately, this means there is only one viable command to run... 'env | lashow' (without the quotes)
            (this is assuming Cygwin or MKS are being used as the backend. I forget if LUU has 'env.exe' delivered)

            Kwane
            mikeP
            Veteran Member
            Posts: 151
            Veteran Member
            6/27/2014 5:45 PM
              Kwane,
              Thanks for the complete yet concise explanation, that helps my understanding. I suspected it was something Infor (they host us) had done to lock us down. (That's what I'd do in their shoes ;- )

              We have LUU, and env.exe works.

              Thanks again,

              M
              .
              Kwane McNeal
              Veteran Member
              Posts: 479
              Veteran Member
              6/27/2014 6:37 PM
                mikeP,
                That was exactly my view, when I though through the processes that Infor and/or Amazon would have used to protect the infrastructure, which coupled with my understanding of the internal coding allowed the answer to effectively write itself.

                Glad I could provide the community effective and accurate content. I know John Henley works hard to keep this running and viable for us all. It's the least I could do.

                Kwane