Implementing ACF2

To implement ACF2 control, use JCL similar to what is provided in member LCP#SMA1 in the LCPCNTL library to assemble the ACF2 interface and relink the primary LOCAL COPY PLUS panel processor module.

Before allowing ISPF users to perform product functions, LOCAL COPY PLUS issues an ACF2 Generalized Resource validation call. If the resource rule is coded to PREVENT access or if ACF2 installation exits deny access, the user cannot perform the function or cannot make updates.

Member LCPXSMA1 in the LCPCNTL library provides the interface to ACF2 services and validates a generalized resource name. The generalized resource name is created as follows:

• R – the class code required by ACF2 for generalized resource rules.
• BMC – the resource type code selected by BMC for LOCAL COPY PLUS generalized resource rules.
• BMCLCP20 – a fixed resource name prefix selected by BMC for LOCAL COPY PLUS resource validation.
• function – the first character of the LOCAL COPY PLUS function to be validated.
• imsid – the one- to four-character active IMSID to be validated.

If an ISPF user attempts to access a LOCAL COPY PLUS Route List for the IMSID IMSP, an ACF2 validation call is made for the full resource name:

Consider the following points regarding ACF2 resource rules:

• To create at least two ACF2 resource rules and define who may access LOCAL COPY PLUS features and facilities, use the standard ACF2 commands.
• To control who has access to the LOCAL COPY PLUS ISPF panels, use the full resource name, R BMC BMCLCP20-LCP2@.
• To control accesses to the individual functions by IMSID, by function, and by userid, use individual or masking ACF2 resource rules.
• To use resource name masking, ACF2 generalized resource rules for the type code, BMC, must be resident.

For example, to use ACF2 resource name masking to control all types of individual access to IMSID IMST in one AFC2 rule set, you could use the following resource name: