Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PSWI - z/OSMF Workflows: ZWEV2.SZWEEXEC no created #4083

Closed
dkelosky opened this issue Nov 12, 2024 · 3 comments · Fixed by #4097 or #4161
Closed

PSWI - z/OSMF Workflows: ZWEV2.SZWEEXEC no created #4083

dkelosky opened this issue Nov 12, 2024 · 3 comments · Fixed by #4097 or #4161
Labels
PSWI z/OSMF PSWI and Workflow

Comments

@dkelosky
Copy link

When running zwe init mvs in V3 I get the following messages:

>> Initialize Zowe custom data sets

Create data sets if they do not exist
Creating dkelosky.ZWEV2.CUST.PARMLIB
Creating dkelosky.ZWEV2.CUST.JCLLIB
Creating dkelosky.ZWEV2.SZWEAUTH
Creating dkelosky.ZWEV2.CUST.ZWESAPL

Copy dkelosky.ZWEV2.SZWESAMP(ZWESIP00) to dkelosky.ZWEV2.CUST.PARMLIB(ZWESIP00)
  * Exit code: 12
  * Output:
    exec 'dkelosky.ZWEV2.SZWEEXEC(ZWEMCOPY)' 'dkelosky.ZWEV2.SZWESAMP(ZWESIP00) dkelosky.ZWEV2.CUST.PARMLIB(ZWESIP00)'
    DATA SET DKELOSKY.ZWEV2.SZWEEXEC NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED
Error ZWEL0111E: Command aborts with error.
bash-4.3$ zwe init mvs -c '/u/users/dkelosky/zowe-smpe/zowe.yaml' --allow-overwrite

At what point should DKELOSKY.ZWEV2.SZWEEXEC be created since all of the other DKELOSKY.ZWEV2. data sets are created during zwe init mvs ?
@dkelosky
Copy link
Author

It seems like the MVS prefix:
image

Should default to the the deployment data sets specified in during the "Configure Deployment":
image

It says the prefix is where Zowe MVS data sets will be installed, but it doesn't mention that it references pre-existing data sets to use the REXX code in ...SZWEEXEC for example.

@jp669844 jp669844 added the PSWI z/OSMF PSWI and Workflow label Nov 12, 2024
@muzikovam
Copy link
Contributor

You are right, the description is not the best. But we took it from example-zowe.yaml
image
Do you reckon we should change it in the workflow? Because then we wouldn't be in sync with the example-zowe, I guess there should stay the original description because of the convenience build?

@dkelosky
Copy link
Author

There are a few options I see:

  • you could change the wording (but it puts burden on the user)
  • you could add extra information into the z/OSMF workflow informational bubble to describe what is required
  • you could default Zowe Setup MVS prefix to the data set HLQ generated at deployment for ...SZWEXEC which would be DKELOSKY.PSWI.AZWE003.T in my case.

@muzikovam muzikovam mentioned this issue Nov 22, 2024
Closed
This was referenced Nov 22, 2024
Merged
Merged
This was referenced Jan 30, 2025
Merged
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
PSWI z/OSMF PSWI and Workflow
Projects
zOS Squad Board
Archived in project
Milestone
No milestone
3 participants
@dkelosky @muzikovam @jp669844