[intrepid-notify] ALCF Weekly Updates - October 11, 2012

[ALCF User Services]

*** Visit ALCF Representatives at the IBM SC12 Booth ***
If you're heading to SC12 in November, ALCF representatives will be easy to find--they'll be in IBM's booth. Check out the Argonne SC12 website (sc12.anl.gov) for the line-up of panels, workshops, tutorials and other events featuring ALCF and other Argonne experts. 

*** Routine Systems Maintenance Monday ***
Intrepid, Challenger and Eureka will have regularly scheduled preventive maintenance starting at 14:00 UTC on Monday, October 15. Maintenance for these systems is expected to conclude at 03:30 UTC on Tuesday, October 16. During maintenance, no jobs will be run on the systems and there will be no access to the login nodes. 

Surveyor and Gadzooks will also have regularly scheduled preventive maintenance starting at 14:00 UTC on Monday, October 15, with an expected end time of 03:30 UTC on Tuesday, October 16. During maintenance of these systems, no jobs will run, and there may be disruptions in filesystem access and possible disruptions in network access to the login nodes. 

We will email users when the work has been completed and the machines are again available for general use. Please email support at alcf.anl.gov with any concerns. 

*** Default IBM XL Compiler Versions Changing ***
As previously announced, the August 2012 update of the IBM XL compilers (XL C/C++ 9.0.0.15 and XL Fortran 11.1.0.15) will become the default on Surveyor effective Monday, October 15. The default on Intrepid/Challenger will be updated on November 12. Users are encouraged to test their code with the new compiler by using the .softenvrc key "+ibm-compilers-aug2012". Please report any problems to support at alcf.anl.gov. At any time, the old version of the compiler may be selected using the key "+ibm-compilers-apr2012". For additional instructions on setting the compiler version, please see http://www.alcf.anl.gov/resource-guides/faqs-compiling-and-linking#how-do-i-select-xl-compiler-versions?

*** User Tip: Running Dependent Jobs ***
To submit a job that waits until another job or jobs have completed, use the --dependencies argument to qsub. For example, to submit a job which depends on job 12345, run: $ qsub -q prod -n 512 -t 10 -A yourproject --dependencies 12345 a.out
For more information, see https://www.alcf.anl.gov/resource-guides/queuing#job-dependencies

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alcf.anl.gov/pipermail/intrepid-notify/attachments/20121011/e3874c67/attachment.html>