Issue with docs.zowe.org/stable/user-guide/install-zowe-zos-convenience-build/

[colinpaicemq]

Description

It says
Expand the PAX file by issuing the following command in the USS shell.

You need to add before this line
create the directory for the product libraries ( where there is enough space)
md /usr/lpp/zowe31

change to this directory
cd /usr/lpp/.zowe31
....

Pages to Update

Screenshots

Expected behavior

Additional context

[colinpaicemq]

and change the pax statement

pax -ppx -rf <zowe-V.v.p>.pax

to
pax -ppx -rf dir/<zowe-V.v.p>.pax

where dir/<zowe-V.v.p>.pax is the absolute name of the file.

Once you have successfully unpaxed the file the pax file can be removed

[colinpaicemq]

It says
After you extract the Zowe convenience build, you can run the zwe install command to install MVS data sets.

I think this is the only way.. so remove the word can

---

In Step 5: Install the MVS data sets

put the tables in About the MVS data sets
in a different file and link to it.

I am instlaling it - I do not (currently) care what is in it. That's someone else's job.

---

After zwe install -c /path/to/zowe.yaml
add comment.
This will not overwrite existing files. Use the --allow-overwrite option to overwrite existing files

---

If I am migrating to a newer release - what do I need to change in my existing definitions?
eg
To migrate from V3.0 to V3.1
If you changed the HLQ data set qualifier you will have to update the APF definitions.
The following changed.

• Security definitions...
• proclib

Parmlib members did not change.

---

I got message ZWES0240W from CCPSISTC.

Does this mean I need to stop ZOWE instances when upgrading.... we should say so. something along the lines of

Before you start.
If you are upgrading or refreshing the libraries, you should stop Zowe instances running on the LPA, because the ZWESISTC loads modules into the LPA, and will refresh the in memory copy

[Martin-Zeithaml]

You need to add before this line
create the directory for the product libraries ( where there is enough space)
md /usr/lpp/zowe31

The mkdir command is mentioned on the page and some basic knowledge of Unix is expected.

It says
After you extract the Zowe convenience build, you can run the zwe install command to install MVS data sets.

I think this is the only way.. so remove the word can

You can continue with zwe command or use JCL samples. JCL for installation is here.

In Step 5: Install the MVS data sets

put the tables in About the MVS data sets
in a different file and link to it.

In progress here.

After zwe install -c /path/to/zowe.yaml
add comment.
This will not overwrite existing files. Use the --allow-overwrite option to overwrite existing files

--allow-overwrite parameter is mentioned and described there.

If I am migrating to a newer release - what do I need to change in my existing definitions?

What's new, migration requirements, etc. are noted in Getting started chapter.

I got message ZWES0240W from CCPSISTC.

Does this mean I need to stop ZOWE instances when upgrading.... we should say so. something along the lines of

ZWES0240W is a warning message and does not require any user action as the module was discarded and new loaded.
But probably mentioning to recycle the Zowe Cross Memory when upgraded, is a good idea.