drmaa_attributes(3)            Grid Engine DRMAA           drmaa_attributes(3)



NNAAMMEE
       drmaa_get_attribute_names,            drmaa_get_vector_attribute_names,
       drmaa_get_next_attr_name,                     drmaa_get_num_attr_names,
       drmaa_release_attr_names - DRMAA job template attributes


SSYYNNOOPPSSIISS
       ##iinncclluuddee ""ddrrmmaaaa..hh""

       iinntt ddrrmmaaaa__ggeett__aattttrriibbuuttee__nnaammeess((
              ddrrmmaaaa__aattttrr__nnaammeess__tt ****vvaalluueess,,
              cchhaarr **eerrrroorr__ddiiaaggnnoossiiss,,
              ssiizzee__tt eerrrroorr__ddiiaagg__lleenn
       ));;

       iinntt ddrrmmaaaa__ggeett__vveeccttoorr__aattttrriibbuuttee__nnaammeess((
              ddrrmmaaaa__aattttrr__nnaammeess__tt ****vvaalluueess,,
              cchhaarr **eerrrroorr__ddiiaaggnnoossiiss,,
              ssiizzee__tt eerrrroorr__ddiiaagg__lleenn
       ));;

       iinntt ddrrmmaaaa__ggeett__nneexxtt__aattttrr__nnaammee((
              ddrrmmaaaa__aattttrr__nnaammeess__tt** vvaalluueess,,
              cchhaarr **vvaalluuee,,
              iinntt vvaalluuee__lleenn
       ));;

       iinntt ddrrmmaaaa__ggeett__nneexxtt__aattttrr__vvaalluuee((
              ddrrmmaaaa__aattttrr__vvaalluueess__tt** vvaalluueess,,
              cchhaarr **vvaalluuee,,
              iinntt vvaalluuee__lleenn
       ));;

       iinntt ddrrmmaaaa__ggeett__nnuumm__aattttrr__nnaammeess((
              ddrrmmaaaa__aattttrr__nnaammeess__tt** vvaalluueess,,
              iinntt **ssiizzee
       ));;

       vvooiidd ddrrmmaaaa__rreelleeaassee__aattttrr__nnaammeess((
              ddrrmmaaaa__aattttrr__nnaammeess__tt** vvaalluueess
       ));;


DDEESSCCRRIIPPTTIIOONN
       The  drmaa_get_attribute_names()  function  returns into _v_a_l_u_e_s a DRMAA
       names string vector containing the set of  supported  non-vector  DRMAA
       job template attribute names. The set includes supported DRMAA reserved
       attribute names and Grid Engine native attribute names.  The  names  in
       the     names     string     vector     can    be    extracted    using
       _d_r_m_a_a___g_e_t___n_e_x_t___a_t_t_r___n_a_m_e(3).  The number of names in the  names  string
       vector  can be determined using _d_r_m_a_a___g_e_t___n_u_m___a_t_t_r___n_a_m_e_s(3).  Note that
       this function is only available in the 1.0 implementation.  The  caller
       is responsible for releasing the names string vector returned into _v_a_l_-
       _u_e_s using _d_r_m_a_a___r_e_l_e_a_s_e___a_t_t_r___n_a_m_e_s(3).  Use _d_r_m_a_a___s_e_t___a_t_t_r_i_b_u_t_e(3)  and
       _d_r_m_a_a___g_e_t___a_t_t_r_i_b_u_t_e(3)    for   setting   and   inspecting   non-vector
       attributes.

   ddrrmmaaaa__ggeett__vveeccttoorr__aattttrriibbuuttee__nnaammeess(())
       The drmaa_get_vector_attribute_names() function returns into  _v_a_l_u_e_s  a
       DRMAA  names string vector containing the set of supported vector DRMAA
       job template attribute names. The set includes supported DRMAA reserved
       attribute  names  and  Grid Engine native attribute names. The names in
       the    names    string    vector     can     be     extracted     using
       _d_r_m_a_a___g_e_t___n_e_x_t___a_t_t_r___n_a_m_e(3).   The  caller is responsible for releasing
       the    names    string    vector    returned    into    _v_a_l_u_e_s    using
       _d_r_m_a_a___r_e_l_e_a_s_e___a_t_t_r___n_a_m_e_s(3).    Use  _d_r_m_a_a___s_e_t___v_e_c_t_o_r___a_t_t_r_i_b_u_t_e(3)  and
       _d_r_m_a_a___g_e_t___v_e_c_t_o_r___a_t_t_r_i_b_u_t_e(3)  for  setting   and   inspecting   vector
       attributes.


   ddrrmmaaaa__ggeett__nneexxtt__aattttrr__nnaammee(())
       Each  time  drmaa_get_next_attr_name()  is  called  it returns into the
       buffer, _v_a_l_u_e, up to _v_a_l_u_e___l_e_n bytes of the next entry  stored  in  the
       DRMAA  names  string  vector, _v_a_l_u_e_s.  With the DRMAA 1.0 library, once
       the names list  has  been  exhausted,  DRMAA_ERRNO_NO_MORE_ELEMENTS  is
       returned.   With  the  DRMAA 0.95 library, once the names list has been
       exhausted, DRMAA_ERRNO_INVALID_ATTRIBUTE_VALUE is returned.   In  order
       to  use  the  DRMAA  0.95  library, you must define the DRMAA_95 macro,
       either in your application directly or through a compiler flag, such as
       -DDRMAA_95.


   ddrrmmaaaa__ggeett__nnuumm__aattttrr__nnaammeess(())
       The  drmaa_get_num_attr_names() returns into _s_i_z_e the number of entries
       in the DRMAA names string vector.  This function is only  available  in
       the 1.0 implementation.


   ddrrmmaaaa__rreelleeaassee__aattttrr__nnaammeess(())
       The  drmaa_release_attr_names() function releases all resources associ-
       ated with the DRMAA names string vector, _v_a_l_u_e_s.


   AAttttrriibbuuttee PPrriioorriittiieess
       DRMAA job template attributes can be set from  six  different  sources.
       In  order of precedence, from lowest to highest, these are: options set
       by DRMAA automatically by default, options set  in  the  _s_g_e___r_e_q_u_e_s_t(5)
       file(s),   options   set  in  the  script  file,  options  set  by  the
       drmaa_job_category attribute, options set by the  drmaa_native_specifi-
       cation attribute, and options set through other DRMAA attributes.

       By default DRMAA sets four options for all jobs.  These are "-p 0", "-b
       yes", "-shell no", and "-w e".  This means that by  default,  all  jobs
       will  have  priority  0,  all  jobs  will be treated as binary, i.e. no
       scripts args will be parsed, all jobs will be executed without a  wrap-
       per  shell, and jobs which are unschedulable will cause a submit error.

       The _s_g_e___r_e_q_u_e_s_t(5) file, found in the $SGE_ROOT/$SGE_CELL/common direc-
       tory,  may contain options to be applied to all jobs.  The .sge_request
       file found in the user's home directory or the current  working  direc-
       tory  may  also  contain  options  to  be applied to certain jobs.  See
       _s_g_e___r_e_q_u_e_s_t(5) for more information.

       If   the   _s_g_e___r_e_q_u_e_s_t(5)   file   contains   "-b   no"   or   if   the
       drmaa_native_specification  attribute  is set and contains "-b no", the
       script file will  be  parsed  for  in-line  arguments.   Otherwise,  no
       scripts args will be interpreted.  See _q_s_u_b(1) for more information.

       If  the drmaa_job_category attribute is set, and the category it points
       to exists in one of the _q_t_a_s_k(5) files,  the  options  associated  with
       that  category  will  be applied to the job template.  See _q_t_a_s_k(5) and
       the drmaa_job_category attribute below for more information.

       If the drmaa_native_specification attribute is set,  all  options  con-
       tained   therein  will  be  applied  to  the  job  template.   See  the
       drmaa_native_specification below for more information.

       Other DRMAA attributes will override any previous settings.  For  exam-
       ple,  if the sge_request file contains "-j y", but the drmaa_join_files
       attribute is set to "n", the ultimate result is that the input and out-
       put files will remain separate.

       For  various reasons, some options are silently ignored by DRMAA.  Set-
       ting any of these options will have no  effect.   The  ignored  options
       are:  -cwd, -help, -t, -verify, -w w, and -w v.  The -cwd option can be
       re-enabled by setting the  environment  variable,  SGE_DRMAA_ALLOW_CWD.
       However, the -cwd option is not thread safe and should not be used in a
       multi-threaded context.


   AAttttrriibbuuttee CCoorrrreellaattiioonnss
       The following DRMAA attributes  correspond  to  the  following  _q_s_u_b(1)
       options:

              DRMAA Attribute                  qsub Option
              -------------------------------------------------------
              drmaa_remote_command             script file
              drmaa_v_argv                     script file args
              drmaa_js_state = "drmaa_hold"    -h
              drmaa_v_env                      -v
              drmaa_wd = $PWD                  -cwd
              drmaa_job_category               (qtsch qtask)*
              drmaa_native_specification       ALL*
              drmaa_v_email                    -M
              drmaa_block_email = "1"          -m n
              drmaa_start_time                 -a
              drmaa_job_name                   -N
              drmaa_input_path                 -i
              drmaa_output_path                -o
              drmaa_error_path                 -e
              drmaa_join_files                 -j
              drmaa_transfer_files             (prolog and epilog)*

              * See the individual attribute description below


DDRRMMAAAA JJOOBB TTEEMMPPLLAATTEE AATTTTRRIIBBUUTTEESS
   ddrrmmaaaa__rreemmoottee__ccoommmmaanndd -- ""<<rreemmoottee__ccoommmmaanndd>>""
       Specifies the remote command to execute. The _r_e_m_o_t_e___c_o_m_m_a_n_d must be the
       path of an executable that is available at the  job's  execution  host.
       If  the  path  is relative, it is assumed to be relative to the working
       directory, usually set through  the  drmaa_wd  attribute.   If  working
       directory  is not set, the path is assumed to be relative to the user's
       home directory.

       The file pointed to by  remote_command  may  either  be  an  executable
       binary  or an executable script.  If a script, it must include the path
       to the shell in a #! line at the beginning of the script.  By  default,
       the  remote  command will be executed directly, as by _e_x_e_c(2).  To have
       the remote command executed in a shell, such as to preserve environment
       settings,  use  the drmaa_native_specification attribute to include the
       "-shell yes" option.  Jobs which are executed by a wrapper  shell  fail
       differently  from  jobs  which are executed directly.  When a job which
       contains a user error, such as an invalid path to  the  executable,  is
       executed  by  a  wrapper  shell, the job will execute successfully, but
       exit with a return code of 1.  When a job which contains such an  error
       is executed directly, it will enter the DRMAA_PS_FAILED state upon exe-
       cution.


   ddrrmmaaaa__jjss__ssttaattee -- ""{{ddrrmmaaaa__hhoolldd||ddrrmmaaaa__aaccttiivvee}}""
       Specifies the job state at submission. The string  values  'drmaa_hold'
       and  'drmaa_active'  are supported. When 'drmaa_active' is used the job
       is submitted in a runnable state.  When 'drmaa_hold' is used the job is
       submitted   in   user   hold  state  (either  DRMAA_PS_USER_ON_HOLD  or
       DRMAA_PS_USER_SYSTEM_ON_HOLD). This attribute is largely equivalent  to
       the _q_s_u_b(1) submit option '-h'.


   ddrrmmaaaa__wwdd -- ""<<ddiirreeccttoorryy__nnaammee>>""
       Specifies  the  directory  name  where  the  job  will  be  executed. A
       '$drmaa_hd_ph$' placeholder at  the  beginning  of  the  _d_i_r_e_c_t_o_r_y___n_a_m_e
       denotes  the remaining string portion as a relative directory name that
       is resolved relative to the job user's home directory at the  execution
       host.  When the DRMAA job template is used for bulk job submission (see
       also _d_r_m_a_a___r_u_n___b_u_l_k___j_o_b(3)) the '$drmaa_incr_ph$'  placeholder  can  be
       used at any position within _d_i_r_e_c_t_o_r_y___n_a_m_e to cause a substitution with
       the parametric job's index.  The _d_i_r_e_c_t_o_r_y___n_a_m_e must be specified in  a
       syntax  that is common at the host where the job is executed. If set to
       a relative path and no placeholder is used,  a  path  relative  to  the
       user's  home  directory  is assumed.  If not set, the working directory
       will default to the user's home directory.  If set and the given direc-
       tory  does  not exist the job will enter the DRMAA_PS_FAILED state when
       run.

       Note that the working directory path is the path on the execution host.
       If  binary  mode is disabled, an attempt to find the job script will be
       made, relative to the working directory path.  That means that the path
       to  the  script  must  be the same on both the submission and execution
       hosts.


   ddrrmmaaaa__jjoobb__nnaammee -- ""<<jjoobb__nnaammee>>""
       Specifies the job's name. Setting the job name is equivalent to use  of
       _q_s_u_b(1) submit option '-N' with _j_o_b___n_a_m_e as option argument.


   ddrrmmaaaa__iinnppuutt__ppaatthh -- ""[[<<hhoossttnnaammee>>]]::<<ffiillee__ppaatthh>>""
       Specifies  the  standard input of the job. Unless set elsewhere, if not
       explicitly set in the job template, the job is started  with  an  empty
       input  stream.  If  the  standard input is set it specifies the network
       path of the job's input stream file.

       When the 'drmaa_transfer_files' job template attribute is supported and
       contains  the  character  'i',  the  input file will be fetched by Grid
       Engine from the specified host or from the submit host if  no  _h_o_s_t_n_a_m_e
       is specified. When the 'drmaa_transfer_files' job template attribute is
       not supported or does not contain the character 'i', the input file  is
       always expected at the host where the job is executed regardless of any
       _h_o_s_t_n_a_m_e specified.

       If the DRMAA job template will be used for bulk  job  submission,  (See
       also  _d_r_m_a_a___r_u_n___b_u_l_k___j_o_b(3))  the  '$drmaa_incr_ph$' placeholder can be
       used at any position within _f_i_l_e___p_a_t_h to cause a substitution with  the
       parametric  job's index. A '$drmaa_hd_ph$' placeholder at the beginning
       of _f_i_l_e___p_a_t_h denotes the remaining portion of the _f_i_l_e___p_a_t_h as a  rela-
       tive file specification resolved relative to the job user's home direc-
       tory at the host where the file is located.  A  '$drmaa_wd_ph$'  place-
       holder  at  the beginning of _f_i_l_e___p_a_t_h denotes the remaining portion of
       the _f_i_l_e___p_a_t_h as a relative file specification resolved relative to the
       job's  working  directory  at  the  host where the file is located. The
       _f_i_l_e___p_a_t_h must be specified in a syntax that  is  common  at  the  host
       where  the  file  is located. If set and the file can't be read the job
       enters the state DRMAA_PS_FAILED.


   ddrrmmaaaa__oouuttppuutt__ppaatthh -- ""[[<<hhoossttnnaammee>>]]::<<ffiillee__ppaatthh>>""
       Specifies the standard output of the job. If not explicitly set in  the
       job  template,  the  whereabouts  of  the  job's  output  stream is not
       defined. If set, this attribute specifies the network path of the job's
       output stream file.

       When the 'drmaa_transfer_files' job template attribute is supported and
       contains the character 'o', the output file will be transferred by Grid
       Engine  to  the  specified host or to the submit host if no _h_o_s_t_n_a_m_e is
       specified. When the 'drmaa_transfer_files' job  template  attribute  is
       not supported or does not contain the character 'o', the output file is
       always kept at the host where the job is  executed  regardless  of  any
       _h_o_s_t_n_a_m_e specified.

       If  the DRMAA job template will be used for of bulk job submission (see
       also _d_r_m_a_a___r_u_n___b_u_l_k___j_o_b(3)) the '$drmaa_incr_ph$'  placeholder  can  be
       used  at any position within the _f_i_l_e___p_a_t_h to cause a substitution with
       the parametric job's  index.   A  '$drmaa_hd_ph$'  placeholder  at  the
       beginning  of  _f_i_l_e___p_a_t_h denotes the remaining portion of the _f_i_l_e___p_a_t_h
       as a relative file specification resolved relative to  the  job  user's
       home directory at the host where the file is located. A '$drmaa_wd_ph$'
       placeholder at the beginning of the  _f_i_l_e___p_a_t_h  denotes  the  remaining
       portion of _f_i_l_e___p_a_t_h as a relative file specification resolved relative
       to the job's working directory at the host where the file  is  located.
       The  _f_i_l_e___p_a_t_h must be specified in a syntax that is common at the host
       where the file is located. If set and the file can't be written  before
       execution the job enters the state DRMAA_PS_FAILED.


   ddrrmmaaaa__eerrrroorr__ppaatthh -- ""[[<<hhoossttnnaammee>>]]::<<ffiillee__ppaatthh>>""
       Specifies  the  standard error of the job. If not explicitly set in the
       job template, the whereabouts of the job's error stream is not defined.
       If  set,  this  attribute specifies the network path of the job's error
       stream file.

       When the 'drmaa_transfer_files' job template attribute is supported and
       contains the character 'e', the output file will be transferred by Grid
       Engine to the specified host or to the submit host if  no  _h_o_s_t_n_a_m_e  is
       specified.  When  the  'drmaa_transfer_files' job template attribute is
       not supported or does not contain the character 'e', the error file  is
       always  kept  at  the  host where the job is executed regardless of any
       _h_o_s_t_n_a_m_e specified.

       If the DRMAA job template will be used for of bulk job submission  (see
       also  _d_r_m_a_a___r_u_n___b_u_l_k___j_o_b(3))  the  '$drmaa_incr_ph$' placeholder can be
       used at any position within the _f_i_l_e___p_a_t_h to cause a substitution  with
       the  parametric  job's  index.   A  '$drmaa_hd_ph$'  placeholder at the
       beginning of  the  _f_i_l_e___p_a_t_h  denotes  the  remaining  portion  of  the
       _f_i_l_e___p_a_t_h as a relative file specification resolved relative to the job
       user's home directory  at  the  host  where  the  file  is  located.  A
       '$drmaa_wd_ph$'  placeholder  at the beginning of the _f_i_l_e___p_a_t_h denotes
       the remaining portion of the _f_i_l_e___p_a_t_h as a relative file specification
       resolved  relative to the job's working directory at the host where the
       file is located. The _f_i_l_e___p_a_t_h must be specified in a  syntax  that  is
       common at the host where the file is located. If set and the file can't
       be written before execution the job enters the  state  DRMAA_PS_FAILED.
       The attribute name is drmaa_error_path.



   ddrrmmaaaa__jjooiinn__ffiilleess -- ""{{yy||nn}}""
       Specifies  if the job's error stream should be intermixed with the out-
       put stream.  If not explicitly set in the job  template  the  attribute
       defaults  to  'n'. Either 'y' or 'n' can be specified. If 'y' is speci-
       fied Grid Engine will ignore the value of  the  'drmaa_error_path'  job
       template  attribute  and  intermix  the  standard error stream with the
       standard output stream as specified with 'drmaa_output_path'.


   ddrrmmaaaa__vv__aarrggvv -- ""aarrggvv11 aarrggvv22 ......""
       Specifies the arguments to the job.


   ddrrmmaaaa__jjoobb__ccaatteeggoorryy -- ""<<ccaatteeggoorryy>>""
       Specifies the DRMAA job category. The _c_a_t_e_g_o_r_y string is used  by  Grid
       Engine  as  a reference into the _q_t_a_s_k(5) file. Certain _q_s_u_b(1) options
       used in the referenced qtask file line are applied to the job  template
       before  submission to allow site-specific resolving of resources and/or
       policies.  The cluster qtask file, the local qtask file, and  the  user
       qtask file are searched. Job settings resulting from job template cate-
       gory are  overridden  by  settings  resulting  from  the  job  template
       drmaa_native_specification  attribute  as well as by explicit DRMAA job
       template settings.

       In order to avoid collisions with command names in the qtask files,  it
       is  recommended  that  DRMAA  job  category names take the form: <cate-
       gory_name>.cat.

       The options -help, -t, -verify, and  -w  w|v  are  ignored.   The  -cwd
       option  is ignored unless the $SGE_DRMAA_ALLOW_CWD environment variable
       is set.


   ddrrmmaaaa__nnaattiivvee__ssppeecciiffiiccaattiioonn -- ""<<nnaattiivvee__ssppeecciiffiiccaattiioonn>>""
       Specifies Grid Engine native _q_s_u_b(1) options which will be  interpreted
       as  part  of  the DRMAA job template.  All options available to _q_s_u_b(1)
       command may be used in the _n_a_t_i_v_e___s_p_e_c_i_f_i_c_a_t_i_o_n, except for -help,  -t,
       -verify,  and  -w  w|v.   The  -cwd  option  may  only  be  used if the
       SGE_DRMAA_ALLOW_CWD environment variable is set.  This is  because  the
       current  parsing algorithm for -cwd is not thread-safe.  Options set in
       the _n_a_t_i_v_e _s_p_e_c_i_f_i_c_a_t_i_o_n will be overridden by the corresponding  DRMAA
       attributes.  See _q_s_u_b(1) for more information on qsub options.


   ddrrmmaaaa__vv__eennvv -- ""<<nnaammee11>>==<<vvaalluuee11>> <<nnaammee22>>==<<vvaalluuee22>> ......
       Specifies  the  job  environment.  Each  environment  _v_a_l_u_e defines the
       remote environment. The _v_a_l_u_e overrides the remote  environment  values
       if there is a collision.


   ddrrmmaaaa__vv__eemmaaiill -- ""<<eemmaaiill11>> <<eemmaaiill22>> ......
       Specifies  e-mail  addresses that are used to report the job completion
       and status.


   ddrrmmaaaa__bblloocckk__eemmaaiill -- ""{{00||11}}""
       Specifies whether e-mail sending shall  blocked  or  not.   By  default
       email  is  not  sent.  If, however, a setting in a cluster or user set-
       tings  file  or  the  email  in  association  with  job   events,   the
       'drmaa_block_email'  attribute  will  override that setting, causing no
       email to be sent.


   ddrrmmaaaa__ssttaarrtt__ttiimmee -- ""[[[[[[[[CCCC]]YYYY//]]MMMM//]]DDDD]] hhhh::mmmm[[::ssss]] [[{{--||++}}UUUU::uuuu]]""
       Specifies the earliest time when the job may  be  eligible  to  be  run
       where

              CC is the first two digits of the year (century-1)
              YY is the last two digits of the year
              MM is the two digits of the month [01,12]
              DD is the two digit day of the month [01,31]
              hh is the two digit hour of the day [00,23]
              mm is the two digit minute of the day [00,59]
              ss is the two digit second of the minute [00,61]
              UU is the two digit hours since (before) UTC
              uu is the two digit minutes since (before) UTC

       If the optional UTC-offset is not specified, the offset associated with
       the local timezone will be used. If the day (DD) is not specified,  the
       current  day  will  be used unless the specified hour:mm:ss has already
       elapsed, in which case the next day will be used.  Similarly for  month
       (MM),  year (YY), and century-1 (CC).  Example: The time: Sep 3 4:47:27
       PM PDT 2002, could be represented as: 2002/09/03 16:47:27 -07:00.


   ddrrmmaaaa__ttrraannssffeerr__ffiilleess -- ""[[ii]][[oo]][[ee]]""
       Specifies, which of the standard I/O files (stdin, stdout  and  stderr)
       are  to be transferred to/from the execution host. If not set, defaults
       to "". Any combination of 'e', 'i'  and  'o'  may  be  specified.   See
       drmaa_input_path,  drmaa_output_path  and drmaa_error_path for informa-
       tion about how to specify the standard input file, standard output file
       and  standard  error  file.  The file transfer mechanism itself must be
       configured by the administrator (see _s_g_e___c_o_n_f(5) ). When it is  config-
       ured,  the  administrator has to enable drmaa_transfer_files.  If it is
       not configured, "drmaa_transfer_files" is  not  enabled  and  can't  be
       used.


EENNVVIIRROONNMMEENNTTAALL VVAARRIIAABBLLEESS
       SSGGEE__DDRRMMAAAA__AALLLLOOWW__CCWWDD
                      Enables   the  parsing  of  the  -cwd  option  from  the
                      sge_request file(s), job  category,  and/or  the  native
                      specification  attribute.   This  option  is disabled by
                      default because  the  algorithm  for  parsing  the  -cwd
                      option is not thread-safe.

       SSGGEE__RROOOOTT       Specifies  the location of the Grid Engine standard con-
                      figuration files.

       SSGGEE__CCEELLLL       If set, specifies the default Grid  Engine  cell  to  be
                      used. To address a Grid Engine cell Grid Engine uses (in
                      the order of precedence):

                             The name of the cell specified in the environment
                             variable SGE_CELL, if it is set.

                             The name of the default cell, i.e. ddeeffaauulltt.


       SSGGEE__DDEEBBUUGG__LLEEVVEELL
                      If set, specifies that debug information should be writ-
                      ten to stderr. In addition the level of detail in  which
                      debug information is generated is defined.

       SSGGEE__QQMMAASSTTEERR__PPOORRTT
                      If  set,  specifies the tcp port on which _s_g_e___q_m_a_s_t_e_r(8)
                      is expected to listen for communication requests.   Most
                      installations  will  use a services map entry instead to
                      define that port.

RREETTUURRNN VVAALLUUEESS
       Upon successful completion, drmaa_get_attribute_names(), drmaa_get_vec-
       tor_attribute_names(),     and     drmaa_get_next_attr_name()    return
       DRMAA_ERRNO_SUCCESS.  Other  values   indicate   an   error.    Up   to
       _e_r_r_o_r___d_i_a_g___l_e_n  characters  of  error  related diagnosis information is
       then provided in the buffer _e_r_r_o_r___d_i_a_g_n_o_s_i_s.


EERRRROORRSS
       The  drmaa_get_attribute_names(),   drmaa_get_vector_attribute_names(),
       and drmaa_get_next_attr_name() functions will fail if:

   DDRRMMAAAA__EERRRRNNOO__IINNTTEERRNNAALL__EERRRROORR
       Unexpected or internal DRMAA error, like system call failure, etc.

   DDRRMMAAAA__EERRRRNNOO__DDRRMM__CCOOMMMMUUNNIICCAATTIIOONN__FFAAIILLUURREE
       Could not contact DRM system for this request.

   DDRRMMAAAA__EERRRRNNOO__AAUUTTHH__FFAAIILLUURREE
       The  specified  request is not processed successfully due to authoriza-
       tion failure.

   DDRRMMAAAA__EERRRRNNOO__IINNVVAALLIIDD__AARRGGUUMMEENNTT
       The input value for an argument is invalid.

   DDRRMMAAAA__EERRRRNNOO__NNOO__AACCTTIIVVEE__SSEESSSSIIOONN
       Failed because there is no active session.

   DDRRMMAAAA__EERRRRNNOO__NNOO__MMEEMMOORRYY
       Failed allocating memory.

       The drmaa_get_next_attr_name() will fail if:

   DDRRMMAAAA__EERRRRNNOO__IINNVVAALLIIDD__AATTTTRRIIBBUUTTEE__VVAALLUUEE
       When there are no more entries in the vector.


SSEEEE AALLSSOO
       _d_r_m_a_a___j_o_b_t_e_m_p_l_a_t_e(3)and _d_r_m_a_a___s_u_b_m_i_t(3).



GE 6.1                   $Date: 2007/07/19 08:17:16 $      drmaa_attributes(3)
