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.

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

Issue with docs.zowe.org/stable/user-guide/configuring-zowe-via-jcl/ #4169

Open
colinpaicemq opened this issue Feb 2, 2025 · 4 comments
Open

Comments

@colinpaicemq
Copy link

Description

IBMUSER.ZWEV3A.CUST.JCLLIB(ZWEIRAC)

You should have two parts to the RACF definitions.
System wide and ZOWE specific.

Zowe specific changes can be made quickly as they only affect Zowe.

System wide defintions such as
RDEFINE FACILITY BPX.JOBNAME UACC(NONE)


RDEFINE FACILITY IRR.RUSERMAP UACC(NONE)


RDEFINE FACILITY IRR.IDIDMAP.QUERY UACC(NONE)
RDEFINE FACILITY IRR.RAUDITX UACC(NONE)

need a much more cautions approach ... if you enable any of the system wide definitions, will they impact existing jobs,next time they start?
Customers may take a week or so to roll these into production.

First on the sysprogs sysytem - then preprod- then production.

I expect most customers have these enabled, but it would make the change control process easier if the file had the definitions reordered

/**************************************************************/

System wide definitions

/*****************Instance specific definitions ****************/

....

If you are defining a second instance --- you should not need to define the system wide ones again the sysprog can just delete them.

Pages to Update

Screenshots

Expected behavior

Additional context

@colinpaicemq
Copy link
Author

and if you want to remove Zowe ... it is easier to see what definitions you need to remove !

@colinpaicemq
Copy link
Author

In fact you may want 3 sections

Systems wide

Zowe userids

Instance

such as

/* started task for ZOWE main server /
RLIST STARTED ZWESLSTC
ALL STDATA
RDEFINE STARTED ZWESLSTC* -
STDATA(USER(ZWESVUSR) -
GROUP(ZWEADMIN) -
TRUSTED(NO)) DATA('ZOWE MAIN SERVER')

/* started task for ZIS cross memory server /
RLIST STARTED ZWESISTC
ALL STDATA
RDEFINE STARTED ZWESISTC* -
STDATA(USER(ZWESIUSR) -
GROUP(ZWEADMIN) -
TRUSTED(NO)) DATA('ZOWE ZIS CROSS MEMORY SERVER')

/* started task for ZIS Auxiliary cross memory server /
RLIST STARTED ZWESASTC
ALL STDATA
RDEFINE STARTED ZWESASTC* -
STDATA(USER(ZWESIUSR) -
GROUP(ZWEADMIN) -
TRUSTED(NO)) DATA('ZOWE ZIS AUX CROSS MEMORY SERVER')

SETROPTS RACLIST(STARTED) REFRESH

@1000TurquoisePogs 1000TurquoisePogs transferred this issue from zowe/docs-site Feb 3, 2025
@1000TurquoisePogs
Copy link
Member

Are you able to provide a draft on how you'd split https://github.com/zowe/zowe-install-packaging/blob/v3.x/staging/files/SZWESAMP/ZWEIRAC ?

@colinpaicemq
Copy link
Author

CCPIRAC2.txt

CCPIRAC3.txt
CCPIRAC4.txt
CCPIRAC5.txt

CCPIRAC2 is for system wide definitions which could affect all users on the system.
These may take a few weeks to implement - because of the potential impact

CCPIRAC3 defines userids and groups. It is possible ( but i guess unlikely) that these would be run more than once
so you have two Zowe instances with different task names and userids

CCPIRAC4 defines the started tasks

CCPIRAC5 - defines the rest...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants