BroadcomMFD · adam-wolfe · May 12, 2025 · May 8, 2025
diff --git a/endevor/Automated-Test-Facility-Using-Test4Z/README.MD b/endevor/Automated-Test-Facility-Using-Test4Z/README.MD
@@ -1,5 +1,8 @@
 # Automated Testing in Endevor with Test4Z
 
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 ## Introduction
 
 Items in this folder can be used to introduce and automate testing in Endevor, running the kinds of test supported by Test4Z. 

diff --git a/endevor/Automated-Test-Facility-for-Batch-Applications/README.md b/endevor/Automated-Test-Facility-for-Batch-Applications/README.md
@@ -1,5 +1,8 @@
 # Automated Test Facility for Batch Applications
 
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 This procedure allows Endevor processors to automate the tailoring, submission and evaluation of Batch application tests. Tests are triggered automatically by the Move or Generate actions of elements of any element type. For example, you may initiate automated tests when a COBOL program is Moved or Generated at a certain stage of Endevor. The test will locate, tailor, submit and evaluate results for one or more JCL elements whose names appear in the "OPTIONS" content of the COBOL program. 
 
 The use of "OPTIONS" is not a new concept to Endevor. Typically, they are objects that provide detailed instructions to the CONPARMX steps of an Endevor processor. To implement this procedure, it is not necessary that you be familiar with the use of OPTIONS or with the CONPARMX utility. Example OPTIONS and processors are provided with this procedure. However, if you would like to know more about the use of OPTIONS in an Endevor processor, see [this doc](https://techdocs.broadcom.com/us/en/ca-mainframe-software/devops/ca-endevor-software-change-manager/18-1/administrating/processors/processor-utilities.html#concept.dita_f657792fe5b63ba8cd9304095175664793517854_CONPARMXUtility).

diff --git a/endevor/ELIB-Update-Stamp-Reporting/README.md b/endevor/ELIB-Update-Stamp-Reporting/README.md
@@ -1,4 +1,8 @@
 # Endevor ELIB Update Stamp reporting
+
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 This entry is a follow-up to the 
 [Announcement on the Endevor Community site](https://community.broadcom.com/mainframesoftware/discussion/important-notice-for-endevor-elib-users) regarding Endevor ELIBS. The item in this folder gives you a method for reporting on your ELIB datasets, to determine whether any action is necessary.
 

diff --git a/endevor/Package-Shipping-Model-and-Script-Examples/README.md b/endevor/Package-Shipping-Model-and-Script-Examples/README.md
@@ -3,6 +3,9 @@
 There are a few challenges when working with Endevor's package shipping. 
 One Package shipment can submit up to 4 jobs, depending on the transmission tool used. If you are shipping to and from multiple sites, there are some things you can do to make it easier to track job outputs to the site names and packages that spawned them.
 
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 Items in this folder may help with these challenges, and to complement the material found in [Shipping and Post Ship Scripts demysfied](https://community.broadcom.com/blogs/joseph-walther/2023/11/27/package-shipping-and-post-ship-scripts-de-mystifie). Included are: 
 
  - Reminders for Setting up Package Shipments

diff --git a/endevor/README.md b/endevor/README.md
@@ -1,5 +1,8 @@
 # Endevor - Sample Scripts
 
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 ## Automated Test Facility for Batch Applications
 This [sample repository](https://github.com/BroadcomMFD/broadcom-product-scripts/tree/main/endevor/Automated-Test-Facility-for-Batch-Applications) contains artifacts described in the [How to Leverage Endevor Processors to Test Batch Applications](https://medium.com/modern-mainframe/how-to-leverage-endevor-processors-to-test-batch-applications-6247a9dfdafa) blog on Medium.  The objects are for using Endevor processors in Building an Automated Test Facility for Batch Applications in Endevor.
 

diff --git a/endevor/ServiceNow-Interface/README.md b/endevor/ServiceNow-Interface/README.md
@@ -1,6 +1,7 @@
 # ServiceNow interface to Endevor
 
-Items in this folder show example Endevor exit code that interfaces with ServiceNow. This interface assumes that the automated activity begins in Endevor. 
+Items in this folder show example Endevor exit code that interfaces with ServiceNow. This interface assumes that the automated activity begins in Endevor. These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
 
 An alternative interface begins with ServiceNow, and allows actions in ServiceNow to automate package actions in Endevor. See these sites for more details:
 

diff --git a/endevor/Shipments-for-Multiple-Destinations (zowe)/README.md b/endevor/Shipments-for-Multiple-Destinations (zowe)/README.md
@@ -1,4 +1,8 @@
 # Zowe Shipments for Multiple Destinations
+
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 This procedure supports zowe commands to execute Endevor package shipments. For example:
 
 `zowe zos-tso issue command "PKGESHIP 'name-of-package'"`

diff --git a/endevor/Shipments-for-a-Single-Destination (zowe)/README.md b/endevor/Shipments-for-a-Single-Destination (zowe)/README.md
@@ -1,4 +1,8 @@
 # Zowe Endevor Package Automation - Shipments for a Single Destination
+
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 This procedure allows zowe commands to execute Endevor package shipments. 
 
 For example: `zowe zos-tso issue command "PKGESHIP 'name-of-package'"`

diff --git a/endevor/Software-Bill-Of-Materials/README.md b/endevor/Software-Bill-Of-Materials/README.md
@@ -1,5 +1,8 @@
 # Software Bill Of Materials 
 
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
+
 The items in this folder support the blog [Adding SBOM Generation and Hash Validation to Endevor Package Ship Facility](https://medium.com/modern-mainframe/adding-sbom-generation-and-hash-validation-to-endevor-package-ship-facility-3183f5354212) .
 
 ## SBOM Shipping Approach 

diff --git a/endevor/zunit/README.md b/endevor/zunit/README.md
@@ -0,0 +1,2 @@
+These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
+) for more information).
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE
		) for more information).