none
CCS: How to create task using batch RRS feed

  • Question

  • Dear All,

    I've got strange situation: I have Delft3d software witch is installed on each compute node of my cluster. For starting calculations I have to start batch file with key mel (name of data files). The body of my batch:

    echo %1% > runid
    call C:\Delft3D\w32\flow\bin\tdatom.exe
    call C:\Delft3D\w32\flow\bin\trisim.exe

    But I have to start it only under folder where I have my data files. I tried to choose me folder with data-files as working directory, but I wasn't succesfull. After that I tried to create another batch file for going to the folder with data and start my batch:

    cd \
    cd C:\test
    flow mel

    I tried to start it under windows command line and It works, but when I tried under cluster I didn't have any result.

    What should I do?

    Best regards, Nick
    Friday, February 8, 2008 11:25 AM

Answers

  • Hmm...I'm unsure of how to answer this because I am unable to reproduce the issue.  Below are the repro steps taken:

    Just remember that when you run a job using clusrun, you're saying "cmd.exe /c".  The "/c" carries out the specified task following it and then terminates cmd.exe.

     

    However, it's worth noting that your batch files must be local to every node in the cluster.  Is that the case?

     

    -Jarred

     

     

    -----------------  Barebones -------------------------

    --- Batch files

    Flow.bat

                Del runid.

                Del runstd.log

                Del runerr.log

                Echo %1% > runid

                Call C:\A\B\flow\bin\atom.exe

                Call C:\A\B\flow\sim.exe

     

    ---- Placement

    In test folder

                test.dat

     

    In bin folder

                Flow.bat

                Atom.exe

                Sim.exe

    --- Program specifications

    Atom.exe

                Copy test.dat to atom.dat

    Sim.exe

                Copy atom.dat to sim.dat

    Both programs use pwd for the path to all files.

     

    An xcopy deployment was used:

                Test folder to C:\test

                Bin folder to C:\A\B\flow\bin

     

    Ran ok locally

    Ran ok with cluster, but not clusrun

     

     

    ----------------- Execution results

    --- from command line

    Cd \test

    C:\A\B\flow\bin\flow mel

    Microsoft Windows [Version 5.2.3790]

    (C) Copyright 1985-2003 Microsoft Corp.

     

    C:\Documents and Settings\Administrator.EDLAS-HPCN01A>cd \test

     

    C:\test>C:\A\B\flow\bin\flow mel

     

    C:\test>del runid.

     

    C:\test>del atom.dat

     

    C:\test>del sim.dat

     

    C:\test>echo mel  1>runid

     

    C:\test>Call C:\A\B\flow\bin\atom.exe

     

    C:\test>Call C:\A\B\flow\bin\sim.exe

     

    C:\test>

    --- from cluster

    Job submit /scheduler:edlas-hpctophn /workdir:c:\test /stdout:runstd.log  C:\A\B\flow\bin\flow mel

    -------------------------------------------------------------------------------------------

     

    C:\test>del runid.

     

    C:\test>del atom.dat

     

    C:\test>del sim.dat

     

    C:\test>echo mel  1>runid

     

    C:\test>Call C:\A\B\flow\bin\atom.exe

     

    C:\test>Call C:\A\B\flow\bin\sim.exe

     

    C:\test>

     

    The runid, atom.dat, and sim.dat content was the same in each case.

    Thursday, February 21, 2008 2:13 AM

All replies

  • Hmm...I'm unsure of how to answer this because I am unable to reproduce the issue.  Below are the repro steps taken:

    Just remember that when you run a job using clusrun, you're saying "cmd.exe /c".  The "/c" carries out the specified task following it and then terminates cmd.exe.

     

    However, it's worth noting that your batch files must be local to every node in the cluster.  Is that the case?

     

    -Jarred

     

     

    -----------------  Barebones -------------------------

    --- Batch files

    Flow.bat

                Del runid.

                Del runstd.log

                Del runerr.log

                Echo %1% > runid

                Call C:\A\B\flow\bin\atom.exe

                Call C:\A\B\flow\sim.exe

     

    ---- Placement

    In test folder

                test.dat

     

    In bin folder

                Flow.bat

                Atom.exe

                Sim.exe

    --- Program specifications

    Atom.exe

                Copy test.dat to atom.dat

    Sim.exe

                Copy atom.dat to sim.dat

    Both programs use pwd for the path to all files.

     

    An xcopy deployment was used:

                Test folder to C:\test

                Bin folder to C:\A\B\flow\bin

     

    Ran ok locally

    Ran ok with cluster, but not clusrun

     

     

    ----------------- Execution results

    --- from command line

    Cd \test

    C:\A\B\flow\bin\flow mel

    Microsoft Windows [Version 5.2.3790]

    (C) Copyright 1985-2003 Microsoft Corp.

     

    C:\Documents and Settings\Administrator.EDLAS-HPCN01A>cd \test

     

    C:\test>C:\A\B\flow\bin\flow mel

     

    C:\test>del runid.

     

    C:\test>del atom.dat

     

    C:\test>del sim.dat

     

    C:\test>echo mel  1>runid

     

    C:\test>Call C:\A\B\flow\bin\atom.exe

     

    C:\test>Call C:\A\B\flow\bin\sim.exe

     

    C:\test>

    --- from cluster

    Job submit /scheduler:edlas-hpctophn /workdir:c:\test /stdout:runstd.log  C:\A\B\flow\bin\flow mel

    -------------------------------------------------------------------------------------------

     

    C:\test>del runid.

     

    C:\test>del atom.dat

     

    C:\test>del sim.dat

     

    C:\test>echo mel  1>runid

     

    C:\test>Call C:\A\B\flow\bin\atom.exe

     

    C:\test>Call C:\A\B\flow\bin\sim.exe

     

    C:\test>

     

    The runid, atom.dat, and sim.dat content was the same in each case.

    Thursday, February 21, 2008 2:13 AM
  •  

    Can you confirm that C:\Delft3D\w32\flow\bin exists on all of the CN's (Compute Nodes)?
    Thursday, February 28, 2008 10:55 PM
    Moderator
  • Yes, it is installed on each node in the same directory
    Monday, March 3, 2008 9:29 PM