Merge branch 'master' into prepare-for-publishing

Author: MikeBauerCA

COBOL Programming Course #1 - Getting Started/Labs/README.md

@@ -1,23 +1,37 @@
-COBOL labs
-4 folders
+# COBOL Programming Course #1 - Getting Started - Lab Setup
 
-1. **cbl** – COBOL source code
-2. **jcl** – JCL to compile, link, and execute COBOL source code
-3. **jclproc** – JCL PROCEDUREs used for labs in JCL folder
-4. **data** – COBOL program input records
+The labs for this course are set up on z/OS 2.4 with Enterprise COBOL v6.3. Modification may be necessary if your installation uses a different version.
 
-Note:
-**cbl** folder
-- copy cobol source members into student id.CBL partitioned data set name
+Please note that the following instruction is provided as-is. Neither this project nor the Open Mainframe Project will be held responsible or liable for any loss, costs, liabilities, or damages resulting from your direct or indirect use of this Lab Setup.
 
-**jcl** folder 
-- copy jcl members into student id.JCL partitioned data set name
-- jcl members reference student id.CBL and student id.LOAD partitioned data set names
+## Contents
 
-**jclproc** folder 
-- members need to be copied into z/OS JES procedure library
+There are 4 folders within this directory:
+- **cbl**, containing the actual COBOL source code
+- **jcl**, containing the JCL used to compile, link, and execute COBOL source code
+- **jclproc**, containing the supplied cataloged procedure used in the JCL
+- **data**, containing the data used as input for the COBOL program
 
-**data** folder
-- member **data** must be transferred binary to z/OS because the data contains EBCDIC and Packed Decimal
-- member **xdata** is a viewable ASCII data but the packed decimal fields were translated to ASCII and are unreadable
+There are 2 kinds of data provided inside the **data** folder:
+- **data** is a binary file that is still encoded in EBCDIC with packed decimal
+- **xdata** is a viewable ASCII file, however, the packed decimal fields are unreadable
 
+There are 3 supplied cataloged procedures inside the **jclproc** folder:
+- **IGYWC** for COBOL code compilation
+- **IGYWCL** for COBOL code compilation and link-edit
+- **IGYWCLG** for COBOL code compilation, link-edit, and execution
+
+## Setup 
+
+For the following instructions, `&SYSUID.` refers to the course taker's ID.
+
+To set up your environment for the Course,
+- You will need to copy the members from **cbl** to your own PDS. The Course Document and JCL assume that the PDS is `&SYSUID..CBL`.
+- You will need to copy the members from **jcl** to your own PDS. The Course Document assumes that the PDS is `&SYSUID..JCL`.
+- You will need to transfer the binary **data** from the data folder to your own sequential data set. The Course Document and JCL assume that the PDS is `&SYSUID..DATA`.
+- You will need to make sure that the procedures IGYWC, IGYWCL, and IGYWCLG are available in your procedure library. 
+
+Note that the JCL references the following data sets,
+- `&SYSUID..CBL` where the COBOL source codes are stored
+- `&SYSUID..LOAD` where the COBOL load modules are stored
+- `&SYSUID..DATA` where the input data are stored

COBOL Programming Course #2 - Advanced Topics/Labs/README.md

@@ -1,20 +1,33 @@
-COBOL labs
-4 folders
+# COBOL Programming Course #2 - Advanced Topics - Lab Setup
 
-1. **cbl** – COBOL source code
-2. **jcl** – JCL to compile, link, and execute COBOL source code
-3. **jclproc** – JCL PROCEDUREs used for labs in JCL folder
+The labs for this course are set up on z/OS 2.4 with Enterprise COBOL v6.3 and Db2 for z/OS 12. Modification may be necessary if your installation uses a different version.
 
-Note:
-**cbl** folder
-- copy cobol source members into student id.CBL partitioned data set name
+Please note that the following instruction is provided as-is. Neither this project nor the Open Mainframe Project will be held responsible or liable for any loss, costs, liabilities, or damages resulting from your direct or indirect use of this Lab Setup.
 
-**jcl** folder 
-- copy jcl members into student id.JCL partitioned data set name
-- jcl members reference student id.CBL and student id.LOAD partitioned data set names
-- jcl setup for DB2 assume Course 1 data are available 
+## Contents
 
-**jclproc** folder 
-- members need to be copied into z/OS JES procedure library
+There are 3 folders within this directory:
+- **cbl**, containing the actual COBOL source code
+- **jcl**, containing the JCL used to compile, link, and execute COBOL source code
+- **jclproc**, containing the supplied cataloged procedure used in the JCL
 
+There are 3 supplied cataloged procedures inside the **jclproc** folder:
+- **DB2CBL** for COBOL code compilation, link-edit, and Db2 binding
+- **DB2JCL** for the execution of SQL statements via JCL
+- **DSNUPROC** for invoking Db2 online utility
 
+## Setup
+
+For the following instructions, `&SYSUID.` refers to the course taker's ID.
+
+To set up your own environment for the Course,
+- You will need to make sure that the Lab Setup for Course 1 has been followed.
+- You will need to copy the members from **cbl** to your own PDS. The Course Document and JCL assume that the PDS is `&SYSUID..CBL`.
+- You will need to copy the members from **jcl** to your own PDS. The Course Document assumes that the PDS is `&SYSUID..JCL`.
+- You will need to make sure that the procedures DB2CBL, DB2JCL, and DSNUPROC are available in your procedure library.
+
+Note that the JCL references the following data sets,
+- `&SYSUID..CBL` where the COBOL source codes are stored
+- `&SYSUID..LOAD` where the COBOL load modules are stored
+- `&SYSUID..DATA` where the input data are stored
+- `&SYSUID..DBRMLIB` where the Db2 database request module output is stored, generated when the course taker submitted either the DB2SETUP or DBRMLIB JCL