Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Can SysCommand be used to copy a file?

 5 Replies
 1 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
tambrosi
Veteran Member
Posts: 55
Veteran Member
3/15/2016 12:41 PM

    Hello, looking for some insight on the SysCommand node in IPA.  

    I am trying to copy a file using the node and getting an error, I thought I read on this  site, that it is possible to use SysCommand to copy files.

    Looked for it but did not find it.  

    Here is what I am trying to do,  I have a file we receive from an outside source, and we need to keep several backup copies of it, so I just want to make a copy of and attach a date time stamp to the name.  

    If I run the command in a DOS window, it works fine. 

    This is what I have in the SysCommand node, 

    Execution mode:  run cmd.exe

    C: && DIR && Copy D:FTPFiles\terry.txt D:FTPFiles\terryxyz.txt

    Output from the Flow:  

    error message I get:  The system cannot find the path specified.

    Directory of C:\

    02/09/2015  11:38 AM    

             inetpub
    06/07/2015  07:25 AM              lawson
    07/26/2012  02:44 AM              PerfLogs
    01/22/2015  05:53 PM              Program Files
    12/07/2015  11:02 AM              Program Files (x86)
    11/18/2015  02:21 PM              Temp
    02/09/2015  11:37 AM              Users
    02/09/2015  11:38 AM              Windows
                   0 File(s)              0 bytes
                   8 Dir(s)  73,039,548,416 bytes free
    The system cannot find the path specified.

    Can this be done with the SysCommand node, or is there a better way. 

    Any help would sure be appreciated.

    Thanks

    Terry 

     

    mikeP
    Veteran Member
    Posts: 151
    Veteran Member
    3/15/2016 1:08 PM

      I had similar behavior that was caused by IPA running on our Landmark server, but the files I wanted to access were on our LSF server.  In my case, the flow was trying to access files on the D: drive, but it was the D; Drive on Landmark, and they weren't there.

       

       

      tambrosi
      Veteran Member
      Posts: 55
      Veteran Member
      3/15/2016 1:15 PM

        I just figured out my own problem after I walked away from it a bit. 

        I missed a slash in the statement.   This was the command 

        C: && DIR && Copy D:\FTPFiles\terry.txt D:\FTPFiles\terryxyz.txt

        instead of: C: && DIR && Copy D:FTPFiles\terry.txt D:FTPFiles\terryxyz.txt

        Sorry to bother--

        Thanks

        Terry


        Katie
        Basic Member
        Posts: 12
        Basic Member
        5/5/2016 5:01 PM
          mikeP, would you mind sharing how you got the SysCommand node to access LSF files from the Landmark server? We are upgrading our flows to IPA and currently having issues trying to get our old SysCommand nodes that we use to archive files working with the files on LSF but IPA on Landmark.

          Thanks!
          Katie
          JimY
          Veteran Member
          Posts: 510
          Veteran Member
          5/6/2016 10:32 AM
            We set up the directories on the LSF side as shares in order to access them and then the value in the variable looks like this: "\\\\lawson-appwebt\\D$\\Data\\SyncFile\\". We are a Windows shop.
            Katie
            Basic Member
            Posts: 12
            Basic Member
            5/6/2016 6:20 PM
              Thanks, Jim! We are on Windows, too. I'll see if I can get ours working with a similar setup!