Add ++HOLD data to Zowe PTFs with required steps

[bobbydixon]

Customer content

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

While working on a Zowe case, our Zowe developers suggested running the zwe init command for mvs and stc. The client seemed surprised, and asked why they should be manually manipulating SMP/E installed tasks manually.

Describe the solution you'd like A clear and concise description of what you want to happen.

In one of our Zowe meeting with Joe Punn, Andrew Metzger, and Rafael Quende, we agreed that it would be a good idea to mention any steps like mentioned above as ++HOLD, so that Zowe admins are aware of additional tasks that need to be carried out. That way, they have to consciously insert a bypass into the SMP/E SYSTSIN to 'force' the receive and apply to go through, which usually assumes the admin has taken note of the ACTION step(s)

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Add any other context or screenshots about the feature request here.

---

Engineering team info (eg https://github.com/zowe/explorer-jes/issues/4)

As a [type of user],
I want [some goal]
so that [some reason].

Details/notes
[Detail - implementation notes]

Acceptance Criteria

*Scenario 1: [Title]
Given [context]
And [some more context]...
When [event]
Then [outcome]
 And [another outcome]...

[MarkAckert]

Could you provide additional information about the client's issue and how the two init commands you mention resolved it?

What version of Zowe was the client using before applying maintenance, and to what version did they upgrade to?

[bobbydixon]

The two zwe init commands did not resolve the issue. The client was merely concerned that we even suggested running the command without the PTFs mentioning to do this as part of the ++HOLD ACTION.

The client upgraded from V2.14 to V2.16.

[MarkAckert]

OK, I understand your feedback, and to the best of my knowledge applying SMP/e maintenance should never require re-issuing zwe init commands. Generally you run these (a) on first installation and (b) in case of any major user configuration updates in the zowe.setup section of zowe.yaml. So philosophically if zwe commands must be re-run after applying SMP/e maintenance, I agree that should find its way into HOLDDATA.

If there's something more concrete to this specific example you'd like to discuss but don't want to share in this issue, we can discuss it in a private chat.

[bobbydixon]

Thanks for the feedback, which makes it sound like we're on the same page. Anything I need to do to make sure this is followed going forwards, or is it already a practice that the Zowe team are following? the reason I'm asking, is so that I can provide feedback to my client.

[JoeNemo]

This needs broader discussion in TSC. @balhar-jakub

[1000TurquoisePogs]

zwe init mvs creates non-smpe managed datasets. zwe init stc prepares proclib content.

you don't need to do this regularly.

but, sometimes that content does change and so should be updated one way or another (zwe, sample jcls, manually, whatever)

I don't think we have much process around when and how to inform users of an action they must take, especially in the form of ++HOLD.

This could go beyond "zwe" and also apply to user actions expected within "zowe.yaml", though we're reducing the possibility of that happening in the future.

So I second that we should discuss this in TSC so that all squads can do the right thing.

[balhar-jakub]

I will bring the topic to the TSC on 06/12