Reorganized content and improved README text.

Author: waljo11

endevor/ServiceNow-Interface/COBOL+REXX+Python-Example/README.md

@@ -0,0 +1,42 @@
+# ServiceNow interface to Endevor
+
+## Overview
+Items in this folder are example Endevor objects for interfacing with ServiceNow. This interface assumes that the automated activity begins in Endevor. 
+
+Processing is exit-based and is initiated by Endevor for element actions, where a CCID must be validated, or by a package action, where a portion of the package name must be validated. Details of the actions of Endevor Exits can be found [here](https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/19-0/reference/api-and-user-exits-reference/exits-reference.html).  Note that Endevor supports "exits that are written in either assembler or in high-level languages such as COBOL". The exits provided here are written in COBOL, but there is no requirement to have knowledge of COBOL. All processing logic for this solution is coded in the Rexx, and the Python or Golang subroutines.
+
+## Where to start
+If you have not yet loaded the Python "requests" package, make that be your first step. If you are not sure whether the "requests" package is installed, you can use this step to find out.
+
+If you have already installed the "request" package, then comment out the sys.path line in the python. For example:
+
+        # Name the directory where the 'requests' are found
+        # sys.path.append('/usslocation/forpython/uptoNotIncludingrequest')
+
+Test your python or GoLang access to ServiceNow. For example, copy the Python code into a USS directory and using OMVS, issue a command like this one: 
+
+    python Servicenow.py CHG1234567
+
+## Installing the "requests" package
+
+If you know that the python "request" package has not been installed, or if you receive a message indicating that it cannot be found, then execute these steps:
+
+- On USS issue this command:
+
+        python -m pip install requests                   
+- Within the python code enter the name of the uss directory that contains the "requests" folder
+        # Name the directory where the 'requests' are found
+        sys.path.append('/usslocation/forpython/uptoNotIncludingrequests')
+
+
+
+Other items in this folder are Endevor exit code examples that query ServiceNow. Endevor functions listed below, each use a COBOL exit, a REXX subroutine and a Python subroutine. Functions include:
+- **Exit 2**. Before element action exit code to validate a CCID value with ServiceNow (C1UEXT02 / C1UEXTR2 / ServiceNow.py)
+- **Exit 7**. Package exit code to validate (a portion of) a package namee with ServiceNow. (C1UEXT07 / C1UEXTR7 / ServiceNow.py)
+
+Processing starts with an Endevor action, such as an element Generate or a package create. Endevor then calls a COBOL exit. The COBOL examples collect exit block information from Endevor and pass it to a REXX subroutine. Rexx then calls the python code to query ServiceNow. The results of the query return as a JSON string, which is visible to both the Python and REXX.
+
+REXX examples contain code that allows on-demand REXX tracing to be invoked - without modifying the REXX code. The examples allow you to limit the tracing to a list of userids. You can create your own list of userids or eliminate it altogether. Then, simply allocate the name of the REXX program to DUMMY. For example, to engage the Trace for C1UEXTR2, then allocate C1UEXTR2 to DUMMY. There are two ways to do the allocation:
+
+- In TSO forground, enter "TSO ALLLOC F(C1UEXTR2) DUMMY"
+- In batch, include a JCL line  "//C1UEXTR2  DD DUMMY"