What is the recommend method of starting ACF2?
search cancel

What is the recommend method of starting ACF2?

book

Article ID: 12762

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC PanApt PanAudit

Issue/Introduction



What is the recommend method of starting ACF2?

Environment

Release:
Component: ACF2MS

Resolution

This step explains how to start CA ACF2 and CA SAF SECTRACE subsystems automatically using the CAISECxx feature. We recommend that CA ACF2 always be started from CAISECxx. You can initialize CA ACF2 from CAISECxx or from the command table SYS1.PARMLIB(COMMNDxx).

There are some advantages to starting CA ACF2, CA SAF SECTRACE through CAISECxx. One advantage is that several members can start the same task but with different operands. To use this feature for starting CA ACF2, remove the start of CA ACF2 from the command table SYS1.PARMLIB(COMMNDxx).

We highly recommend that CA ACF2 be started using the CAISECxx member in SYS1.PARMLIB.

To use CAISEC00 for your started tasks, create a member called CAISEC00. In CAISEC00, list each subsystem name, whether it should start automatically, and which members of SYS1.PARMLIB contain additional operands for the START command. Here is an example of CAISEC00 entries:

EDIT ???? SYS1.PARMLIB(CAISEC00) ? 01.01 ??????????????? COLUMNS 001 072
COMMAND ===>                                             SCROLL ===> CSR
************************* TOP OF DATA *************************
00000001 ACF2(xx START)
00000003 TRCE(xx START)
00000004 PROMPT
************************ BOTTOM OF DATA ***********************

To start some, but not all, of the subsystems listed in the CAISEC00 member, place an asterisk (*) to the left of the name of each subsystem that you do not want to start.

Each xx points to a member in SYS1.PARMLIB. For example, the following entries in CAISEC00 correspond to these member names:

 

CAISEC00 Entry

SYS1.PARMLIB Member

ACF2(01 START)

CAIACF01

TRCE(07 NOSTART)

CAITRC07

Notice that the entry number matches the SYS1.PARMLIB member. For example, ACF2(01 START) matches member CAIACF01.

In addition, you can specify the following keyword in the CAISEC00 member:

PROMPT

Indicates that the operator console should be prompted for specification of the CAISEC initialization parameters. During CA SAF initialization, a WTOR message CAS2070I is issued to allow the operator to specify the CA SAF initialization parameters.

Use one of the following options to cause CA SAF to use the CAIACFxx parmlib member.

ACF2(xx)
ACF2(xx START)
ACF2(xx NOSTART)

To specify the CAISECxx parmlib member suffix, use one of the following options:

SEC=xx orSEC(xx)

This allows a site to maintain multiple CAISECxx parmlib members. CAISEC00 is the initial parmlib member processed during CA SAF startup processing. Within the CAISEC00 member, you might specify any of the valid initialization parameters, including SEC=xx to indicate that an alternate parmlib member should be processed. The last value processed for any of the valid initialization keywords are the value selected for processing. To avoid initialization processing loops, a CAISEC member suffix can be specified only once for processing.

Use one of the following options to cause CA SAF to use the CAITRCxx parmlib member:

TRCE(xx)
TRCE(xx START)
TRCE(xx NOSTART)

Use the U option to cause CA SAF to use the CAISEC00 parmlib member as it currently exists. This is the default and lets you continue processing.

The U option is available as a response to the prompt at the console only; it cannot be used as a keyword value in CAISEC00. You are unable to specify any other parameters once U is specified.

If you specify a single parameter or multiple parameters, such as ACF2(xx), these replace only their counterparts in CAISEC00 or any other CAISECxx member that you specify with the SEC(xx) parameter. All other parameters remain the same.

Note: If you want to use one or more of these options automatically at start up, you should put them in CAISEC00 and remove the PROMPT keyword.

For example, the following two members in SYS1.PARMLIB will start up ACF2 with SYSID SYSA.

BROWSE   SYS1.PARMLIB(CAISEC00) - 01.05            Line00000000Col001 080
********************************* Top of Data *******************************
ACF2(00 START)
******************************** Bottom of Data *****************************

BROWSE   SYS1.PARMLIB(CAIACF00) - 01.00            Line00000000Col001 080
********************************* Top of Data *******************************
SYSID(SYSA)
******************************** Bottom of Data *****************************

 

Specifying Startup Options in CAIACF

The CAIACFxx parmlib member you specify at the CAISEC prompt contains parameters that apply to that eTrust CA-ACF2 system. This example shows a CAIACFxx member with specified parameters. Specify one keyword per line.

EDIT ---- SYS1.PARMLIB(CAIACF01) - 01.01 --------------- COLUMNS 001 072
COMMAND ===>                                             SCROLL ===> CSR
************************* TOP OF DATA *************************
00000001 SYSID(TESTCPU)
00000002 BACKUP
00000003 TRACEGSO(CONSOLE)
************************ BOTTOM OF DATA ***********************

 

To start some, but not all, of the subsystems listed in the CAISEC00 member, place an asterisk (*) to the

 

BACKUP|NOBACKUP

Indicates whether the automatic 24-hour backup dump of the eTrust CAACF2 databases should be bypassed. BACKUP is the default.

DDSNS(dsn-group)

Specifies the data set group names, defined in the ACFFDR, used to initiate eTrust CA-ACF2 using an alternate set of eTrust CA-ACF2 databases, if necessary.

NOCPF

Allows for bypassing of the eTrust CA-ACF2 subtask regardless of what is specified on the GSO OPTS record.

NOMLACT

Allows for bypassing of eTrust CA-ACF2 multilevel security regardless of whether MLACTIVE is specified in the GSO MLSOPTS record.

NOLDS

Allows for bypassing of the eTrust CA-ACF2 subtask regardless of what is specified on the GSO OPTS record.

NOSTATS

Allows for bypassing of the eTrust CA-ACF2 Statistics Gathering subtask regardless of whether STATS is specified on the GSO OPTS record.

SYSID(systemid)

Specifies the one- to eight-character default SYSID for the system on which eTrust CA-ACF2 is being started. This default ID is used if none is specified for entry of ACF subcommands under the CONTROL(GSO) setting and for the writing of eTrust CA-ACF2 SMF records. To find out what this default system ID is at any given time, use the ACF SHOW SYSTEMS subcommand.

TRACEGSO(destination)

Sends TRACEGSO records to the destination indicated. See the description

of the F ACF2,TRACEGSO operator command in the “Console Operator

Commands” appendix in the Systems Programmer Guide.

 

MVS symbolic substitution is also supported in the CAIACFxx parmlib member. See  section Using MVS Symbolic Substitution, below for more information.