The goal here is to provide a job type with no execution at all, on any node ou frontend.

Indeed, using cosystem job type, oarexec is executed on the frontend typically. Hence if the frontend must be rebooted for a maintenance for instance, the job is killed.

This is a serious issue for long jobs.

Grid'5000 wants to use such jobs to manage long term reservation of storages.

Open question: 
  * if we manage to not execute anything for the noop job, how do we terminate the job (what state ?), and how do we handle suspend and besteffort on those jobs for instance (at least we need to check that besteffort and suspend still work).
  * if no script is executed, one may however need a way to get the environment normally set inside a job shell. -> provide a commande for that ? 

Server prologue and epilogue must be executed however.