From f0740f73241c774d48272ba690d8091499e246f0 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Fri, 4 Mar 2022 14:46:23 +0100
Subject: [PATCH] Promote squeue --me

---
 .../docs/data_transfer/datamover.md                 |  2 +-
 .../docs/jobs_and_resources/slurm.md                | 13 +++++++++----
 2 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md b/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
index 670c2d5c4..0bd3fbe88 100644
--- a/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
+++ b/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
@@ -23,7 +23,7 @@ There are the commands `dtinfo`, `dtqueue`, `dtq`, and `dtcancel` to manage your
 and jobs.
 
 * `dtinfo` shows information about the nodes of the data transfer machine (like `sinfo`).
-* `dtqueue` and `dtq` show all your data transfer jobs (like `squeue -u $USER`).
+* `dtqueue` and `dtq` show all your data transfer jobs (like `squeue --me`).
 * `dtcancel` signals data transfer jobs (like `scancel`).
 
 To identify the mount points of the different filesystems on the data transfer machine, use
diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
index 98e37b5ac..f7456662f 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
@@ -283,10 +283,15 @@ provide a comprehensive collection of job examples.
 
 ### Job and Slurm Monitoring
 
-On the command line, use `squeue` to watch the scheduling queue. This command will tell the reason,
-why a job is not running (job status in the last column of the output). More information about job
-parameters can also be determined with `scontrol -d show job <jobid>`. The following table holds
-detailed descriptions of the possible job states:
+On the command line, use `squeue` to watch the scheduling queue.
+
+!!! tip "Show your jobs"
+
+    Invoke `squeue --me` to list only your jobs.
+
+The command `squeue` will tell the reason, why a job is not running (job status in the last column
+of the output). More information about job parameters can also be determined with `scontrol -d show
+job <jobid>`. The following table holds detailed descriptions of the possible job states:
 
 ??? tip "Reason Table"
 
-- 
GitLab