Recursos para Profesionales de TI > Página principal de foros > Windows HPC Server Job Submission and Scheduling > Cannot pass environment variables containing ";" via job submit
Formular una preguntaFormular una pregunta
 

RespondidaCannot pass environment variables containing ";" via job submit

  • miércoles, 08 de abril de 2009 19:59Dr.Darshan Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    I have a cluster with Windows HPC Server 2008 and Microsoft HPC Pack. I am trying to submit a job using the "job submit" command that needs to set an environment variable with semi-colon delimited values for each task. I have tried the following alternatives, but each of them fails in the same manner:
    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\XXXXX>job submit /env:key="value1;value2" dir
    Bad format for 'env' parameter.  Should be /env:name=value;*

    C:\Users\XXXXX>job submit /env:"key=value1;value2" dir
    Bad format for 'env' parameter.  Should be /env:name=value;*

    C:\Users\XXXXX>job submit /env:key=value1;value2 dir
    Bad format for 'env' parameter.  Should be /env:name=value;*

    Could someone please let me know what I am doing incorrectly? The error message is quite incomprehensible and the documentation did not address this problem.

Respuestas

  • viernes, 17 de abril de 2009 19:04MWirtz Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    I believe you're not doing anything wrong, because the "job submit" command seems to use the ";" as a string delimiter while parsing the argument /env. I guess it's just impossible that way. Maybe you could try to add the set variable command to your commandline string  e.g. like this:

    job submit set key=value1;value2 ^&^& dir

    Make sure to mask the "&" with "^" because otherwise the dir command would be executed directly after your submission command in the local shell.
    Hope this helps.

    - Michael
    • Marcado como respuestaDr.Darshan martes, 05 de mayo de 2009 18:28
    •  
  • sábado, 02 de mayo de 2009 0:28sayanch1MSFT, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    This issue should be fixed in SP1. However, you might try using the SetEnvironmentVariable method in the Scheduler API as that might work.
    • Marcado como respuestaDr.Darshan martes, 05 de mayo de 2009 18:29
    •  

Todas las respuestas

  • viernes, 17 de abril de 2009 19:04MWirtz Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    I believe you're not doing anything wrong, because the "job submit" command seems to use the ";" as a string delimiter while parsing the argument /env. I guess it's just impossible that way. Maybe you could try to add the set variable command to your commandline string  e.g. like this:

    job submit set key=value1;value2 ^&^& dir

    Make sure to mask the "&" with "^" because otherwise the dir command would be executed directly after your submission command in the local shell.
    Hope this helps.

    - Michael
    • Marcado como respuestaDr.Darshan martes, 05 de mayo de 2009 18:28
    •  
  • sábado, 02 de mayo de 2009 0:28sayanch1MSFT, ModeradorMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     Respondida
    This issue should be fixed in SP1. However, you might try using the SetEnvironmentVariable method in the Scheduler API as that might work.
    • Marcado como respuestaDr.Darshan martes, 05 de mayo de 2009 18:29
    •  
  • martes, 05 de mayo de 2009 18:24Dr.Darshan Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Thank you, that was indeed helpful.
  • martes, 05 de mayo de 2009 18:28Dr.Darshan Medallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuarioMedallas del usuario
     
    Thank you, I will wait for SP1 and use the previous workaround meanwhile. I would have preferred to use the Scheduler API, but cannot because I am submitting jobs from a Python application.
    • Marcado como respuestaDr.Darshan martes, 05 de mayo de 2009 18:28
    • Desmarcado como respuestaDr.Darshan martes, 05 de mayo de 2009 18:28
    •