Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 56f5eb3

Browse files
Minor Changes in Chapter 1
Signed-off-by: Rituraj-M50 <mahatorituraj150@gmail.com>
1 parent 3792f8c commit 56f5eb3

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

‎COBOL Programming Course #1 - Getting Started/COBOL Programming Course #1 - Getting Started.md‎

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -197,7 +197,7 @@ This section introduces the IBM Z Open Editor.
197197

198198
### What is the IBM Z Open Editor?
199199

200-
The IBM Z Open Editor is a free extension for Visual Studio Code (VSCode) that provides language support for COBOL, PL/I, and JCL languages. Along with this language support it also provides content assistance for applications that call CICS, MQ, IMS, and DB2 APIs. The source code doesn't even need to reside on z/OS, it could be in a source code repository, locally in a file, or on z/OS. Although this course focuses on COBOL as a source language, a lot of the functions we will discuss will also apply to PL/I and JCL.
200+
The IBM Z Open Editor is a free extension for Visual Studio Code (VSCode) that provides language support for COBOL, PL/I, and JCL languages. Along with this language support it also provides content assistance for applications that call CICS, MQ, and DB2 APIs. The source code doesn't even need to reside on z/OS, it could be in a source code repository, locally in a file, or on z/OS. Although this course focuses on COBOL as a source language, a lot of the functions we will discuss will also apply to PL/I and JCL.
201201

202202
### The role of the Language Server Protocol
203203

@@ -317,7 +317,7 @@ As you browse through code you will come across COBOL PERFORM statements or vari
317317

318318
## Code-completion
319319

320-
Code completion isn't exactly a new concept in most IDEs. For example, the Eclipse editor has provided auto-completion for Java APIs for a long time. The same key combination, **CTRL+SPACE**, triggers this auto-completion function while you are coding and can be used to help guide you through COBOL syntax and CICS, IMS API calls.
320+
Code completion isn't exactly a new concept in most IDEs. For example, the Eclipse editor has provided auto-completion for Java APIs for a long time. The same key combination, **CTRL+SPACE**, triggers this auto-completion function while you are coding and can be used to help guide you through COBOL syntax and CICS API calls.
321321

322322
### COBOL reserved word completion
323323

@@ -534,22 +534,22 @@ Zowe CLI provides a significant suite of z/OS data set interaction functionality
534534

535535
![](Images/zowe/zowe-cli-zos-files-actions.png)
536536

537-
*Figure 4. Zowe CLI zos-files actions*
537+
*Figure 3. Zowe CLI zos-files actions*
538538

539539
![](Images/zowe/zowe-cli-zos-files-list-ds-command.png)
540540

541-
*Figure 5. Sample Zowe CLI zos-files list ds command*
541+
*Figure 4. Sample Zowe CLI zos-files list ds command*
542542

543543
### Interacting with z/OS Jobs
544544
Zowe CLI provides a significant suite of z/OS jobs interaction functionality. See the following figures for details on available actions and a sample job submission command.
545545

546546
![](Images/zowe/zowe-cli-zos-jobs-actions.png)
547547

548-
*Figure 6. Zowe CLI zos-jobs actions*
548+
*Figure 5. Zowe CLI zos-jobs actions*
549549

550550
![](Images/zowe/zowe-cli-zos-jobs-submit-ds-command.png)
551551

552-
*Figure 7. Sample Zowe CLI zos-jobs submit ds command*
552+
*Figure 6. Sample Zowe CLI zos-jobs submit ds command*
553553

554554
## Automating tasks using Zowe CLI
555555
Running commands interactively is a great way to learn the capabilities of the Zowe CLI. However, creating custom automation for your commonly repeated tasks and making use of valuable development tooling is where significant value lies. For COBOL development, significant time can be spent reviewing compiler output and testing programs. These repetitive tasks are excellent candidates for automation.
@@ -559,31 +559,31 @@ Let’s investigate automating submitting a job and verifying the return code is
559559

560560
![](Images/automating-tasks/sample-package-json.png)
561561

562-
*Figure 8. Sample package.json*
562+
*Figure 7. Sample package.json*
563563

564564
Then I will create a config.json file to store all the variables I may wish to change for my project. In this case, we will set the job to submit and the maximum allowable return code for that job.
565565

566566
![](Images/automating-tasks/sample-config-json.png)
567567

568-
*Figure 9. Sample config.json*
568+
*Figure 8. Sample config.json*
569569

570570
Next, we will write our automation. The Zowe CLI was built with scripting in mind and can output responses in JSON format which can be easily parsed.
571571

572572
![](Images/automating-tasks/zowe-cli-response-format-json.png)
573573

574-
*Figure 10. Sample Zowe CLI response format JSON output*
574+
*Figure 9. Sample Zowe CLI response format JSON output*
575575

576576
Now, instead of issuing this command and reviewing it to see if the retcode is less than or equal to 4, we want to automate it. See the implementation in a node script below.
577577

578578
![](Images/automating-tasks/script-to-submit-job-check-rc.png)
579579

580-
*Figure 11. Sample code to submit job and verify the output is less than or equal to a maximum allowable RC*
580+
*Figure 10. Sample code to submit job and verify the output is less than or equal to a maximum allowable RC*
581581

582582
I had to make the investment to write this automation but for future job submissions I can simply issue `npm run submitJob`. IDEs like VS Code can visualize these tasks making my commonly repeated tasks as easy as clicking a button :). This job could compile, link, and/or run a COBOL program.
583583

584584
![](Images/automating-tasks/npm-script-button-click-and-run.png)
585585

586-
*Figure 12. Visualization of npm script and sample run*
586+
*Figure 11. Visualization of npm script and sample run*
587587

588588
More advanced code automating the compilation, deployment to test environment, and testing of a COBOL CICS application are described in this [blog](https://medium.com/zowe/continuous-integration-for-a-mainframe-app-800657e84e96).
589589

@@ -592,13 +592,13 @@ Another good example of automating tasks using Zowe CLI is when you want to inte
592592

593593
![](Images/automating-tasks/one-click-cobol-build.png)
594594

595-
*Figure 13. "One Click" COBOL build process*
595+
*Figure 12. "One Click" COBOL build process*
596596

597597
You can then level up this process by leveraging a CI/CD pipeline. What is a CI/CD pipeline? It is an automated way of building, testing, and deploying your application and you can do the same with your COBOL development. The figure below shows the pipeline for the same automated tasks that we did earlier.
598598

599599
![](Images/automating-tasks/CircleCI-pipeline.png)
600600

601-
*Figure 14. CI/CD pipeline of the "one-click" COBOL build process*
601+
*Figure 13. CI/CD pipeline of the "one-click" COBOL build process*
602602

603603
To know more about this topic, check [this](https://medium.com/@jessielaine.punongbayan/how-i-used-typescript-to-generate-my-cobol-programs-a2a180209148) out.
604604

@@ -656,9 +656,9 @@ V20.15.1
656656

657657
If you do not see a version number after you submit the command, you do not have node.js installed, or if it shows a version less than v18, you should continue following these instructions. If you do see a version number and it is v18 or higher, you can move on to the section Install Java SDK.
658658

659-
2. If the node.js version is less than v18, or node isn’t installed at all.
659+
2. Ensure you are using a supported LTS version of Node.js. You can verify your version or find supported versions at [`https://nodejs.org/en/about/previous-releases`](https://nodejs.org/en/about/previous-releases)
660660

661-
Updating node.js to the appropriate version number is a relatively simple process because the installer takes care of most of the "heavy lifting". All you will need to do is visit the Node.js download site, provided below and follow the download and installation instructions for your specific workstation platform. Do this same process if you do not already have node.js installed.
661+
Updating node.js to the appropriate version is a relatively simple process because the installer takes care of most of the "heavy lifting". All you will need to do is visit the Node.js download site, provided below and follow the download and installation instructions for your specific workstation platform. Do this same process if you do not already have node.js installed.
662662

663663
[`https://nodejs.org/en/download/`](https://nodejs.org/en/download/)
664664

@@ -704,7 +704,7 @@ If you do not see a version number after you submit the command, you do not have
704704

705705
3. Once Java is uninstalled from your workstation, you can click the Java JDK 17 download link below and follow the installation instructions for your specific OS.
706706

707-
[`https://www.oracle.com/java/technologies/javase-jdk8-downloads.html` ](https://www.oracle.com/java/technologies/javase-jdk8-downloads.html)
707+
[`https://www.oracle.com/java/technologies/downloads/` ](https://www.oracle.com/java/technologies/downloads/)
708708

709709
4. Verify the installation and proper version number as shown in Example 2.
710710

@@ -805,7 +805,7 @@ There are two recommended methods for installing the Zowe CLI. If you have acces
805805
Issue the following command in your terminal (e.g. Command Prompt or if you are using VS Code, Terminal -> New Terminal):
806806

807807
```
808-
npm install -g @zowe/cli@zowe-v3-lts
808+
npm install -g @zowe/cli@zowe-v3-lts
809809
```
810810

811811
If the command returns an EACCESS error, refer to [Resolving EACCESS permissions errors when installing packages globally](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally) in the npm documentation.
@@ -856,7 +856,7 @@ zowe scs update
856856
```
857857

858858
## Install Zowe CLI Plug-ins
859-
Zowe CLI is an extendable technology that can be enhanced by installing plug-ins. Zowe offers a number of [plug-ins](https://docs.zowe.org/stable/user-guide/cli-extending.html). At the time of this writing, these include plug-ins for [CICS](https://www.npmjs.com/package/@zowe/cics-for-zowe-cli), [Db2](https://www.npmjs.com/package/@zowe/db2-for-zowe-cli), [FTP](https://www.npmjs.com/package/@zowe/zos-ftp-for-zowe-cli), [IMS](https://www.npmjs.com/package/@zowe/ims-for-zowe-cli), and [MQ](https://www.npmjs.com/package/@zowe/mq-for-zowe-cli). There are also many vendor plug-ins, many of which are available on the [public registry](https://www.npmjs.com/search?q=zowe-cli). At the time of this writing, these include plug-ins for [CA Endevor](https://www.npmjs.com/package/@broadcom/endevor-for-zowe-cli), [CA Endevor Bridge for Git](https://www.npmjs.com/package/@broadcom/endevor-bridge-for-git-for-zowe-cli), [CA File Master Plus](https://www.npmjs.com/package/@broadcom/file-master-plus-for-zowe-cli), [CA OPS/MVS](https://www.npmjs.com/package/@broadcom/ops-for-zowe-cli), [CA View](https://www.npmjs.com/package/@broadcom/caview-for-zowe-cli), [IBM CICS Bundle Generation and Deployment](https://www.npmjs.com/package/zowe-cli-cics-deploy-plugin), and [IBM z/OS Connect EE](https://www.npmjs.com/package/@zosconnect/zosconnect-zowe-cli).
859+
Zowe CLI is an extendable technology that can be enhanced by installing plug-ins. Zowe offers a number of [plug-ins](https://docs.zowe.org/stable/user-guide/cli-extending.html). At the time of this writing, these include plug-ins for [CICS](https://www.npmjs.com/package/@zowe/cics-for-zowe-cli), [Db2](https://www.npmjs.com/package/@zowe/db2-for-zowe-cli), [FTP](https://www.npmjs.com/package/@zowe/zos-ftp-for-zowe-cli), and [MQ](https://www.npmjs.com/package/@zowe/mq-for-zowe-cli). There are also many vendor plug-ins, many of which are available on the [public registry](https://www.npmjs.com/search?q=zowe-cli). At the time of this writing, these include plug-ins for [CA Endevor](https://www.npmjs.com/package/@broadcom/endevor-for-zowe-cli), [CA Endevor Bridge for Git](https://www.npmjs.com/package/@broadcom/endevor-bridge-for-git-for-zowe-cli), [CA File Master Plus](https://www.npmjs.com/package/@broadcom/file-master-plus-for-zowe-cli), [CA OPS/MVS](https://www.npmjs.com/package/@broadcom/ops-for-zowe-cli), [CA View](https://www.npmjs.com/package/@broadcom/caview-for-zowe-cli), [IBM CICS Bundle Generation and Deployment](https://www.npmjs.com/package/zowe-cli-cics-deploy-plugin), and [IBM z/OS Connect EE](https://www.npmjs.com/package/@zosconnect/zosconnect-zowe-cli).
860860

861861
### Install from Public npm Registry
862862
To install a Zowe CLI plug-in from the registry, simply locate the plug-in you wish to install, e.g. `@zowe/cics-for-zowe-cli`, find the distribution tag for the distribution you want to install, e.g. `zowe-v3-lts`, and issue the following command:
@@ -874,7 +874,7 @@ zowe plugins install @zowe/cics-for-zowe-cli@zowe-v3-lts
874874
Multiple plug-ins can be installed in a single command. For example, to install all Zowe CLI plug-ins available from the Zowe organization, you could issue:
875875

876876
```{.bash}
877-
zowe plugins install @zowe/cics-for-zowe-cli@zowe-v3-lts @zowe/ims-for-zowe-cli@zowe-v3-lts @zowe/mq-for-zowe-cli@zowe-v3-lts @zowe/zos-ftp-for-zowe-cli@zowe-v3-lts @zowe/db2-for-zowe-cli@zowe-v3-lts
877+
zowe plugins install @zowe/cics-for-zowe-cli@zowe-v3-lts @zowe/mq-for-zowe-cli@zowe-v3-lts @zowe/zos-ftp-for-zowe-cli@zowe-v3-lts @zowe/db2-for-zowe-cli@zowe-v3-lts
878878
```
879879

880880
Vendor plug-ins on the registry are installed in the same way. For example, to install the CA Endevor plug-in, you would issue
@@ -887,7 +887,7 @@ zowe plugins install @broadcom/endevor-for-zowe-cli@zowe-v3-lts
887887
Navigate to [Zowe.org Downloads](https://www.zowe.org/#download) and click the CLI Plugins button to download the package which includes all Zowe CLI plug-ins for the Zowe organization. After accepting the EULA for Zowe, a package named `zowe-cli-plugins-v.r.m.zip` will be downloaded to your machine. Unzip the contents of `zowe-cli-plugins-v.r.m.zip` to a preferred location on your machine. You can select which plug-ins you want to install. The IBM Db2 plug-in requires [additional configuration](https://docs.zowe.org/stable/user-guide/cli-db2plugin.html#installing-from-a-local-package) when installing from a local package. To install all plug-ins you can issue:
888888

889889
```
890-
zowe plugins install cics-for-zowe-cli.tgz zos-ftp-for-zowe-cli.tgz ims-for-zowe-cli.tgz mq-for-zowe-cli.tgz db2-for-zowe-cli.tgz
890+
zowe plugins install cics-for-zowe-cli.tgz zos-ftp-for-zowe-cli.tgz mq-for-zowe-cli.tgz db2-for-zowe-cli.tgz
891891
```
892892

893893
For offline installation of vendor plug-ins, please reach out to the specific vendor for details.

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /