Extended Definition Mode

Initial Entry to Screen A

IOA checks authorization:

• The class checked is FACILITY.
• The entity checked is $$CTDPNLA.qname

Subsequent Operations in Screen A

The actions (hold, delete, rerun, and so on) are separated into different categories of access authority to the Active Missions screen (Screen A). The entity checked is $$MISxrrr.qname

where

• owner is the owner ID that is specified in the Mission Definition screen.
• x is a one digit action identifier.
• rrr is a three character identifier for each action (see the following table).

  Table 53 CTDSE08 Action Identifiers

  Action Identifier	Action Code	Description
  1	ZOO LOG	Zoom Log
  2	HLD RRN FRE	Hold Rerun Free
  3	CHA DEL PPL UPD	Change Delete Print Update

To permit USERA to hold missions with owner of USERB, use the following command:

For RACF:

PERMIT $$MIS2HLD.qname.USERB ACCESS(READ) ID(USERA) CLASS(FACILITY)

For TopSecret:

TSS PERMIT(USERA) IBMFAC($$MIS2HLD.qname.USERB) ACC(READ)

For ACF2/SAF:

SET RESOURCE(CMF)
COMP
$KEY($MIS2HLD.qname.USERB) TYPE(CMF)
UID(USERA) ALLOW

Batch

The entity checked is $$CTDRRST.qname.owner

This entity is checked for batch jobs (Control‑D and Control‑V backup and restore jobs and Control‑V migration jobs). In most cases, the batch jobs runs under the user ID of the Control‑D and Control‑V started tasks.

The user ID of the Control‑D started tasks as specified in the Control‑D installation procedure.

Use the following command to allow Control‑D to access this entity:

For RACF:

PERMIT $$CTDRRST.qname.* ACCESS(READ) ID(controld‑stc’s‑userid) CLASS(FACILITY)

For TopSecret:

TSS PERMIT(controld-acid) IBMFAC($$CTDRRST.qname) ACC(READ)

For ACF2/SAF:

SET RESOURCE(CMF)
COMP
$KEY($$CTDRRST.qname) TYPE(CMF)
UID(userid) ALLOW

where userid is one or more Control‑D started tasks that are specified during Control‑D installation.