|
2 | 2 |
|
3 | 3 | At this location are found Endevor processor utilities and snippets of example processor code. For the sake of highlighting and syntax checking, processors and processor snippets are given the .jcl extension.
|
4 | 4 |
|
| 5 | +These samples are provided as is and are not officially supported (see [license](https://github.com/BroadcomMFD/broadcom-product-scripts/blob/main/LICENSE |
| 6 | +) for more information). |
| 7 | + |
5 | 8 | ## VALUECHK
|
6 | 9 |
|
7 | 10 | This processor utility complements the use of CONPARMX within your processors. The input instructions for CONPARMX are typically called PARMS or OPTIONS, and may be extended to contain statements that are processed by VALUECHK, and not CONPARMX. Statements of this kind adhere to a format such as:
|
@@ -36,17 +39,21 @@ A processor REXX program that simulates the DB2 Masking method for Binds, used b
|
36 | 39 |
|
37 | 40 | A processor and its REXX parser that can perform syntax checking on OPTIONS elements.
|
38 | 41 |
|
| 42 | +## YAML2REX |
| 43 | + |
| 44 | + YAML2REX.rex is a utility that can convert (simple) YAML statements into usable REXX. You can allow YAML files to become data for your automated processing. Use the YAML2REX.jcl member to see what the conversion does to your YAML files. |
| 45 | + |
| 46 | +Practical applications using REXX converted from YAML can be found in the **Dyname-Syslib** members, and others on this GitHub. |
39 | 47 |
|
40 | 48 | ## Dynamic-Syslib
|
41 | 49 |
|
42 | 50 | Items in this folder support the sharing of input components across developer efforts/projects that are underway in parallel.
|
43 | 51 |
|
44 | 52 | For example, development for a January release might be underway in one sandbox (or environment) at the same time as development for a March release in another sandbox (or environment). This feature allows the March release to include libraries from the January release within its own SYSLIB concatenations, before the January release is Moved to production.
|
45 | 53 |
|
46 |
| -## OPTVALDT, TXTRPLCE, JCLRPLCE and YAML2REX |
| 54 | +## OPTVALDT, TXTRPLCE and JCLRPLCE |
47 | 55 |
|
48 | 56 | These are REXX subroutines which are used by other FDP solutions:
|
49 | 57 | - OPTVALDT processes OPTIONS statements to ensure values are numeric or properly quoted
|
50 | 58 | - TXTRPLCE is a generic Search and Replace utility
|
51 | 59 | - JCLRPLCE is like TXTRPLCE, but provides precise JCL change instructions, where jobcard and/or Stepname.DDname references point to specific locations within a JCL for changes and inserts.
|
52 |
| - - YAML2REX is converts many YAML constructs into usable REXX. The conversion might result in REXX stem arrays, so that when accompanied by appropriate Do Loops, various actions are automated. |
|
0 commit comments