Skip to content

Commit b1d26a7

Browse files
committed
Merge and rebuild PDF
Signed-off-by: MikeBauerCA <[email protected]>
2 parents d43e62b + bf06e46 commit b1d26a7

16 files changed

+16
-21
lines changed

COBOL Programming with VSCode.md

Lines changed: 16 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -353,13 +353,13 @@ To get started, you can simply open a terminal and issue zowe. This will yield t
353353

354354
![](Images/zowe-cli-help.png)
355355

356-
*Figure 1. Zowe CLI Help
356+
*Figure 1. Zowe CLI Help*
357357

358358
In the example above, multiple extensions are installed. The structure of commands is `zowe <group> <action> <object>` followed by various parameters and options specific to the command. For example, a valid command is `zowe files list data-set "HLQ.*"`. This command will list data-sets matching a pattern of "HLQ.*". You can append `-h` to any command to find out more information. Frequently referring to the help can be difficult and time consuming so if your environment has access to a web browser, simply append `--help-web` or `--hw` to any command to launch interactive web help.
359359

360360
![](Images/zowe-cli-web-help.png)
361361

362-
*Figure 2. Zowe CLI Web Help
362+
*Figure 2. Zowe CLI Web Help*
363363

364364
Don’t have the CLI installed yet? You can also check out a copy of the web help for the core Zowe CLI and Zowe plug-ins [here](https://docs.zowe.org/stable/web_help/index.html).
365365

@@ -370,29 +370,29 @@ When creating profiles you can also specify the `prompt*` keyword to be prompted
370370

371371
![](Images/zowe-cli-zosmf-profile-creation-command.png)
372372

373-
*Figure 3. Zowe CLI z/OSMF Profile Creation Command
373+
*Figure 3. Zowe CLI z/OSMF Profile Creation Command*
374374

375375
### Interacting with z/OS Data Sets
376376
Zowe CLI provides a significant suite of z/OS data set interaction functionality. See the following figures for details on available actions and a sample list command.
377377

378378
![](Images/zowe-cli-zos-files-actions.png)
379379

380-
*Figure 4. Zowe CLI zos-files actions
380+
*Figure 4. Zowe CLI zos-files actions*
381381

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

384-
*Figure 5. Sample Zowe CLI zos-files list ds command
384+
*Figure 5. Sample Zowe CLI zos-files list ds command*
385385

386386
### Interacting with z/OS Jobs
387387
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.
388388

389389
![](Images/zowe-cli-zos-jobs-actions.png)
390390

391-
*Figure 6. Zowe CLI zos-jobs actions
391+
*Figure 6. Zowe CLI zos-jobs actions*
392392

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

395-
*Figure 7. Sample Zowe CLI zos-jobs submit ds command
395+
*Figure 7. Sample Zowe CLI zos-jobs submit ds command*
396396

397397
## Automating tasks using Zowe CLI
398398
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.
@@ -402,31 +402,31 @@ Let’s investigate automating submitting a job and verifying the return code is
402402

403403
![](Images/sample-package-json.png)
404404

405-
*Figure 8. Sample package.json
405+
*Figure 8. Sample package.json*
406406

407407
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.
408408

409409
![](Images/sample-config-json.png)
410410

411-
*Figure 9. Sample config.json
411+
*Figure 9. Sample config.json*
412412

413413
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.
414414

415415
![](Images/zowe-cli-response-format-json.png)
416416

417-
*Figure 10. Sample Zowe CLI response format JSON output
417+
*Figure 10. Sample Zowe CLI response format JSON output*
418418

419419
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.
420420

421421
![](Images/script-to-submit-job-check-rc.png)
422422

423-
*Figure 11. Sample code to submit job and verify output is less than or equal to a maximum allowable RC
423+
*Figure 11. Sample code to submit job and verify output is less than or equal to a maximum allowable RC*
424424

425425
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.
426426

427427
![](Images/npm-script-button-click-and-run.png)
428428

429-
*Figure 12. Vizualization of npm script and sample run
429+
*Figure 12. Vizualization of npm script and sample run*
430430

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

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

436436
![](Images/one-click-cobol-build.png)
437437

438-
*Figure 13. "One Click" COBOL build process
438+
*Figure 13. "One Click" COBOL build process*
439439

440440
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.
441441

442442
![](Images/CircleCI-pipeline.png)
443443

444-
*Figure 14. CI/CD pipeline of the "one click" COBOL build process
444+
*Figure 14. CI/CD pipeline of the "one click" COBOL build process*
445445

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

@@ -936,8 +936,7 @@ The DATA DIVISION is where characteristics of data are defined in one of the fol
936936

937937
- LINKAGE SECTION:
938938

939-
Describe data from another program.
940-
When defining data developed for internal processing.
939+
Describes data from another program. When defining data developed for internal processing.
941940

942941
- WORKING-STORAGE SECTION:
943942

@@ -947,10 +946,6 @@ When defining data developed for internal processing.
947946

948947
Storage allocated each time a program is called and de-allocated when the program ends.
949948

950-
- LINKAGE SECTION:
951-
952-
Describes data from another program.
953-
954949
#### PROCEDURE DIVISION
955950

956951
The PROCEDURE DIVISION contains instructions related to the manipulation of data and interfaces with other procedures are specified.
@@ -1407,7 +1402,7 @@ A list of COBOL variable name restrictions or rules are:
14071402

14081403
- Must not contain a space as a part of the name.
14091404

1410-
- Name contains letters (A-Z), digits (0-9), minus sign and hyphens (-).
1405+
- Name contains letters (A-Z), digits (0-9), underscores (_) and hyphens (-).
14111406

14121407
- Maximum length of 30 characters.
14131408

COBOL Programming with VSCode.pdf

194 Bytes
Binary file not shown.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.

0 commit comments

Comments
 (0)