Skip to content

Commit badfe21

Browse files
Merge pull request #125 from UrbanCode/zos-utility-v103
Released v103 of z/OS Utility plugin
2 parents bf8f119 + eb980d7 commit badfe21

4 files changed

Lines changed: 20 additions & 0 deletions

File tree

docs/UCD/zos-deploy/downloads.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22

33
To download the plug-in, click the following version-specific links.
44

5+
- [devops-deploy-zos-deploy-103.1187825.zip](https://raw.githubusercontent.com/UrbanCode/IBM-UCD-PLUGINS/main/files/zos-deploy/devops-deploy-zos-deploy-103.1187825.zip)
56
- [devops-deploy-zos-deploy-102.1187730.zip](https://raw.githubusercontent.com/UrbanCode/IBM-UCD-PLUGINS/main/files/zos-deploy/devops-deploy-zos-deploy-102.1187730.zip)
67
- [devops-deploy-zos-deploy-101.1186159.zip](https://raw.githubusercontent.com/UrbanCode/IBM-UCD-PLUGINS/main/files/zos-deploy/devops-deploy-zos-deploy-101.1186159.zip)
78
- [devops-deploy-zos-deploy-101.1185920.zip](https://raw.githubusercontent.com/UrbanCode/IBM-UCD-PLUGINS/main/files/zos-deploy/devops-deploy-zos-deploy-101.1185920.zip)

docs/UCD/zos-deploy/overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,10 @@ No special steps are required for installation. See [Installing plug-ins in DevO
4444

4545
## History
4646

47+
### Version 103
48+
49+
* 103.1187825 - Added Run in Parallel option to Submit Job step to submit all jobs first and then wait for each job to complete instead of submitting and waiting for each job. This option is helpful when there are multiple independent jobs to submit and wait for in the process.
50+
4751
### Version 102
4852

4953
* 102.1187730 - Add option to update modified timestamp of PDS members in 'Deploy dataset and USS Files' plugin step.

docs/UCD/zos-deploy/steps.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -248,6 +248,7 @@ Submit job.
248248
| Replace Tokens | String | Specify replacement rules to apply to the JCL before submission. Rules are represented by a list of explicit tokens to replace in the following format: token->value. Separate rules with newline characters. For example, mytoken->new_value will replace the mytoken string with new_value in all files. To replace @token@ with new_value, specify @token@->new_value. Regular expressions are not supported. | No |
249249
| Show Output | String | Specify the output data set to be displayed in the log. Separate multiple data sets with commas. Specify ALL for all data sets. | No |
250250
| Stop On Fail | Boolean | Select to stop submitting jobs after a job fails. Failure is determined by the Max Return Code and Timeout fields. A JCL error is always considered a failure. | No |
251+
| Run In Parallel | Boolean | Select to submit all jobs first and then wait for each job to complete. Stop On Fail must be disabled when this option is enabled. | No |
251252
| Timeout | String | Specify the timeout in seconds. | No |
252253
| Wait For Job | Boolean | Select to wait for the job to complete. If cleared, the Timeout, Show Output, Max Lines, and Max Return Code fields are not used. | No |
253254
| | | **Hidden Properties (below)** | |

docs/UCD/zos-deploy/troubleshooting.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,19 @@
11
# Troubleshooting
22

3+
## Run MVS Command fails with JAR file does not exist error
4+
5+
When you run the `Run MVS Command` step, you might encounter the following error:
6+
7+
```
8+
[Error] SDSF Jar File /usr/include/java_classes/isfjcall.jar does not exist.
9+
```
10+
11+
SDSF no longer distributes files in /usr/include/java_classes and /usr/lib/java_runtime64 directories.
12+
* Change `/usr/include/java_classes` to `/usr/lpp/sdsf/java/classes` and
13+
* Change `/usr/lib/java_runtime64` to `/usr/lpp/sdsf/java/runtime64` in the `Run MVS Command` step.
14+
15+
Reference - [Using the SDSF Java programming language](https://www.ibm.com/docs/en/zos/3.2.0?topic=guide-using-sdsf-java-programming-language)
16+
317
## Copy Artifacts step limitation
418

519
When you use the Copy Artifacts step, you can copy only in the same logical partition (LPAR). To transfer artifacts between different LPARs, use the FTP Artifacts step.

0 commit comments

Comments
 (0)