Modify rule S6937: Extend support to other statements (#3746)

* Modify rule S6937: Extend support to other statements

* Add more documentation

* address review comment

rules/S6937/jcl/metadata.json

@@ -8,7 +8,7 @@
   },
   "tags": [
   ],
-  "defaultSeverity": "Major",
+  "defaultSeverity": "Critical",
   "ruleSpecification": "RSPEC-6937",
   "sqKey": "S6937",
   "scope": "All",
@@ -18,6 +18,6 @@
     "impacts": {
       "RELIABILITY": "HIGH"
     },
-    "attribute": "CONVENTIONAL"
+    "attribute": "LOGICAL"
   }
 }

rules/S6937/jcl/rule.adoc

@@ -1,8 +1,12 @@
-In-stream procedures should always have a name.
-
 == Why is this an issue?
 
-In JCL, it is expected for a PROC statement inside of a job stream to have a name.
+In JCL, some statements require to have a label or name defined, otherwise it will trigger a JCL error.
+The statements that require a name/label are:
+* CNTL
+* JOB
+* NOTIFY
+* OUTPUT
+* in-stream PROC
 
 == How to fix it
 
@@ -32,4 +36,8 @@ In JCL, it is expected for a PROC statement inside of a job stream to have a nam
 
 === Documentation
 
+* https://www.ibm.com/docs/en/zos/3.1.0?topic=description-label-field[IBM Reference - CNTL Label field]
+* https://www.ibm.com/docs/en/zos/3.1.0?topic=d-name-field-5[IBM Reference - JOB Name field]
+* https://www.ibm.com/docs/en/zos/3.1.0?topic=statement-label-field[IBM Reference - NOTIFY Label field]
+* https://www.ibm.com/docs/en/zos/3.1.0?topic=d-name-field-6[IBM Reference - OUTPUT Name field]
 * https://www.ibm.com/docs/en/zos/3.1.0?topic=d-name-field-8[IBM reference - PROC statement - Name field]