Backup job has started getting SYBCMD251I UNIDENTIFIED INPUT KEYWORD "*BFS*" IN BACKUP OPERATION. What's going on?
search cancel

Backup job has started getting SYBCMD251I UNIDENTIFIED INPUT KEYWORD "*BFS*" IN BACKUP OPERATION. What's going on?

book

Article ID: 26246

calendar_today

Updated On:

Products

VM:Backup for z/VM VM:Backup High-Speed Disaster Recovery Option (HiDRO) Mainframe VM Product Manager VM:Manager Suite for Linux on Mainframe VM:Manager Suite for z/VM VM SUITE

Issue/Introduction

None of the files that control the HiDRO backup job, the CMDCTL, SFSCTL or SELECT file have changed. Yet a couple of tasks fail with the following set of messages:

    SYBCIP015E CMD 10814: B *BFS* VMSYS: FSPACE LDAPSRV TO TAPE ( PACK OTAPE FSN * 
    SYBCIP015E CMS 10814: CHA ( B ) 
    SYBCMD251I UNIDENTIFIED INPUT KEYWORD "*BFS*" IN BACKUP OPERATION 
    Jobs ends with a RC=4 

 

Environment

Release: VMBKUH00400-2.8-VM:Backup-HiDRO (VM:Backup HiDRO)
Component:

Resolution

HiDRO does not have support for BFS (Byte File System). Code was added to put out a warning that would draw attention to the fact that these file spaces are not getting backed up. It is recommended that once a site starts receiving this message, that they logon to SYBMON and add an exclusion record for each backup that includes SFS Filepools.

Using the failure above as an example, the Exclude record in the SELECT file for a backup would look like: E: FP VMSYS * FS LDAPSRV

To have these special file spaces backed up, CA's product, VM:Backup, has support in it to backup BFS directories.