search cancel

Automatic backup not working on the new ACF2 system

book

Article ID: 134687

calendar_today

Updated On:

Products

ACF2 ACF2 - z/OS ACF2 - MISC

Issue/Introduction

Attempting to figure out why one system is not taking an automatic backup at midnight.

Compared the GSO records and they both look the same.

BACKUP:

AUTO BACKUP TIME=00:01   CPUID=SYS1,
WORK FILE UNIT=SYSDA     PRIMARY SPACE=5          SECONDARY SPACE=1,
COMMAND STRING=S ACFBKUP COPY TO SYSUT1=ON,

The IPL on this system showing the start-up of ACF2.

ACF8A904 NO AUTOMATIC BACKUPS WILL BE TAKEN

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Cause

This system running SMF SYSID is MVS1

Resolution

The problem is the CPUID on the BACKUP record. 

 SYS1 / BACKUP LAST CHANGED BY SECADM ON mm/dd/yy-hh:mm                         

CPUID(SYS1) PRISPACE(5) SECSPACE(1) STRING(S ACFBKUP) SYSUT1 TIME(00:01) WORKUNIT(SYSDA) 

This is documented in the CA ACF2™ FOR Z/OS 16.0 documentation in section 'Automatic Backup Options (BACKUP)':

CPUID(smfid) Specifies the SMF ID of the CPU designated to take the automatic backups in a multi-CPU environment. If you specify this field, ACF2 compares it with the actual MVS system SMF ID. ACF2 bypasses the automatic backup if the two do not match. Operators can take backups at any time from any CPU. You should designate a single CPU in a multi-system configuration as the sole automatic backup processor. Masking cannot be used in the CPUID( ) field value. ACF2 interprets the dash and the asterisk as literal values and not as masking characters. 

Correct the CPUID to match the running system, MVS1.