To get Slurm job environment variables, you have several options depending on your needs:

1. Print All Environment Variables in Your Job Script

You can print all environment variables inside your Slurm job script using:

bash
Copy
#!/bin/bash
#SBATCH --job-name=my_job
#SBATCH --output=output.log

# Print all environment variables
env

or

bash
Copy
printenv

This will output all environment variables, including those set by Slurm.

---

2. Access Slurm-Specific Environment Variables

Slurm sets several environment variables for your job. You can access them directly in your script or after the job completes:

bash
Copy
echo $SLURM_JOB_ID
echo $SLURM_JOB_NAME
echo $SLURM_NODELIST
echo $SLURM_NTASKS

Common Slurm environment variables

---

3. Pass Custom Environment Variables to Your Job

If you want to pass specific environment variables to your job, use the --export option:

bash
Copy
sbatch --export=ALL,MY_VAR=value my_script.sh

or export only certain variables:

bash
Copy
sbatch --export=MY_VAR1,MY_VAR2=value my_script.sh

---

4. Check Environment Variables After Job Submission

After submitting your job, you can check the environment variables set for a specific job using:

bash
Copy
scontrol show job <job_id> | grep Environment

or

bash
Copy
sacct -j <job_id> --format=JobID,JobName,Environment

---

5. Debugging Environment Issues

If you suspect environment issues, you can run a simple bash job with -s to source your environment:

bash
Copy
sbatch -s -o debug.log ./my_script.sh

---