crestart [csub options] [-f] checkpoint_dir [job_ID | "job_ID[index]"]
-B
-f
-N
-x
-b begin_time
-C core_limit
-c [hour:]minute[/host_name | /host_model]
-D data_limit
-E "pre_exec_command [argument ...]"
-F file_limit
-m "host_name[+[pref_level]] | host_group[+[pref_level]] ..."
-G user_group
-M mem_limit
-q "queue_name ..."
-S stack_limit
-t term_time
-w `dependency_expression'
-W run_limit[/host_name| /host_model]
checkpoint_dir [job_ID | "job_ID[index]"]
[-h | -V]
Restarts a checkpointed job using the checkpoint files saved in checkpoint_dir/last_job_ID/. Only jobs that have been successfully checkpointed can be restarted.
Jobs are re-submitted and assigned a new job ID. The checkpoint directory is renamed using the new job ID, checkpoint_dir/new_job_ID/.
By default, jobs are restarted with the same output file and file transfer specifications, job name, window signal value, checkpoint directory and period, and rerun options as the original job.
To restart a job on another host, both hosts must be binary compatible, run the same OS version, have access to the executable, have access to all open files (AIP must locate them with an absolute path name), and have access to the checkpoint directory.
The environment variable CB_RESTART is set to Y when a job is restarted.
AIP invokes the erestart(8) executable found in CB_SERVERDIR to perform the restart.
Only the csub options listed here can be used with crestart.
Only the csub options listed in the option list above can be used for brestart. Except for the following option, see csub(1) for a description of brestart options.
csub(1), cjobs(1), cmod(1), cqueues(1), chosts(1), cchkpnt(1), cb.yaml(5), echkpnt(8), erestart(8)
In kernel-level checkpointing, you cannot change the value of core limit, CPU limit, stack limit or memory limit with crestart.