Skip to content

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

Open
@colinpaicemq

Description

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status

      No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions