Changes between Version 7 and Version 8 of doc/app/palmrun

Timestamp:

Sep 26, 2017 12:17:31 PM (8 years ago)

Author:

raasch

Comment:

--

doc/app/palmrun

@@ -16 +16 @@
 
 * {{{palmrun}}} does not compile any more at the beginning of a batch job. The palm-executable for the batch-job (or for the interactive session) is created as part of the {{{palmrun}}}-call that you have manually entered at your terminal, and it is created before the batch-job is submitted. The executable is put into the folder {{{SOURCE_FOR_RUN_<run_identifier>}}}, where {{{<run_identifier>}}} is the string provided with {{{palmrun}}}-option {{{-d}}}. This folder is now put into the folder set with variable {{{fast_io_catalog}}} (see below for {{{fast_io_catalog}}}). If you do not use a user-interface, {{{palmrun}}} will not compile at all and will take the executable from folder {{{MAKE_DEPOSITORY_<configuration_identifier>}}} that has been generated with your last call of {{{palmbuild}}}. If {{{palmrun}}} cannot find the folder {{{MAKE_DEPOSITORY_<configuration_identifier>}}}, it will internally call {{{palmbuild}}} in order to generate it. If {{{palmrun}}} finds a folder {{{SOURCE_FOR_RUN_<run_identifier>}}} that has been generated by a previous call of {{{palmbuild}}}, it will ask you if executables from that folder shall be used. This way, you can avoid to re-compile your user-interface with each call of {{{palmrun}}}. Automatically generated restart runs will always use executables from  {{{SOURCE_FOR_RUN_<run_identifier>}}}. \\\\ You may have to remove folders {{{SOURCES_FOR_RUN_...}}} manually frm time to time, because they are not deleted automatically at the end of a job (or the last job of a restart job chain).
+
+* The option for giving the file activation strings is now {{{-a}}} instead of {{{-r}}}.
+
+* In case of automatic restart runs, hashes ("#") in the file activation strings are now replaced by character "r" instead of character "f". 
 
 * The {{{.palm.config.<ci>}}} file does not contain blocks any more. Several variable names have been changed (e.g. {{{compiler_options}}} instead of {{{fopts}}}) and new variables have been introduced (e.g. {{{execute_command}}} in order to give the command for starting the executable). Colons ({{{:}}}) for separating e.g. compiler options must not be used any more. Here is an example (with some lines truncated, as displayed by ....)
@@ -126 +130 @@
    * {{{ {{QUEUE}} }}}: The name of the queue to which the job shall be submitted. Will be replaced by the value provided with {{{palmrun}}}-option {{{-q}}}, or, if {{{-q}}} is omitted, by the value of variable {{{defaultqueue}}} (see further above).
  - Lines starting with {{{BDT:}}}: Here you have to give special batch directives for a small job that is required to send the job protocol file from the remote host back to your local host (meaning that these lines are only required if you are running batch jobs on a remote host). Since the job protocol file generated by the main job (which is started by {{{palmrun}}}) is not available before the end of the job, the main job has to start another small job at its end, which has the only task to send back the job protocol to the local host. The computing centers normally have special queues for these kind of small jobs, and you should request the job resources respectively.
-
-* Some small changes have been made concerning the file connection statements in {{{.palm.iofiles}}}.
- - change 1
- - change 2