How to Activate a New or Changed Resource Rule?

Document ID : KB000026271
Last Modified Date : 14/02/2018
Show Technical Document Details


How to Activate a New or Changed Resource Rule?


The activation of a new or changed resource rule depends on whether the rule is globally resident (in ECSA) or locally resident in an address space (in ELSQA) or not resident at all. The type of residency is dependent upon the GSO INFODIR and RESDIR records.

The GSO INFODIR and RESDIR records indicate which resource type directories will be built and made globally resident when ACF2 initializes. The actual rules can also be made globally resident, depending on the residency code for each type. Since the RESDIR record does not support the new directory classes supported by the INFODIR record, RESDIR is now regarded as an obsolete record, though its contents are still honored. All further references will be to the INFODIR record.

If the resource type has already been included in the GSO INFODIR record, the user will get a message ACF60039 ISSUE THE F ACF2,REBUILD(typecode) COMMAND TO ACTIVATE THE RULE when the rule is compiled and stored. If the resource type is not currently in the INFODIR record, then the INFODIR record will have to be updated to add the rule's type code before the REBUILD command can be issued.

These commands accomplish the change and activation:

      set c(gso) 
      change infodir types(r-rrda) add 
      f acf2,refresh(infodir) 
      f acf2,rebuild(rda)

If the resource type is not resident in either ECSA or ELSQA (not defined in INFODIR), the new or changed resource rule will have to be retrieved from the ACF2 INFOSTG database and chained into the address space requesting that resource. If the rule was previously used in an address space, issue the command:

      f acf2,setnorul(address space)
      (where "address space" is the jobname of a JOB, the task name of an STC, or the logonid of a TSO user)

This command releases all rules currently chained to that address space so the new or changed rule can be brought in with the next validation for that resource.