VMBCCK0215E 410051 FILE0001 has a variable record format or has an invalid logical record length.

Document ID : KB000074929
Last Modified Date : 16/04/2018
Show Technical Document Details
Introduction:
When we try to start VM:Backup, we get the following error: 

VMBCCK0215E 410051 FILE0001 has a variable record format or has an invalid logical record length. 
Question:
VMBCCK0215E 410051 FILE0001 has a variable record format or has an invalid logical record length.
 
We just upgraded our z/VM system to 6.4 and VM:Backup to r3.6 and now when we try to start VM:Backup, we get the following error: 

VMBCCK0215E 410051 FILE0001 has a variable record format or has an invalid logical record length. 

The doc says to contact  CA Technical Support.

 
How can we resolve this error?
 
Environment:
Running VM:Backup r3.6 on z/VM 6.4.
Answer:
Message VMBCCK0215:   filename filetype HAS A VARIABLE RECORD FORMAT OR HAS AN INVALID LOGICAL RECORD LENGTH. 

Reason: 
The logical record length (LRECL) of all catalog files *must* be the same as the blocksize of the minidisk on which they reside. 
Catalog files must have a fixed record format. 

 
 
All the catalog files must have the same LRECL as the blocksize of the catalog minidisk which is VMBACKUP's 1B0. 

Your LISTFILE of the catalog files show an LRECL of 1024 which must correspond to the blocksize of the 1B0. 

BACKUP INDEX B1 F 1024 
DOMAIN INDEX B1 F 1024 
DUMPJOB INDEX B1 F 1024 
USER INDEX B1 F 1024 
DAY101 FILE0001 B1 F 1024 
DAY102 FILE0001 B1 F 1024

 
 
The customer had changed the catalog blocksize to 4096, but done nothing to the catalog files themselves. 
Since the minidisk blocksize changed to 4096, all of the catalog files have to be changed to support the new blocksize and you do that by running an EXEC called REBLOCK. This EXEC gets loaded to VMBACKUP's 192. 
 
 
 
 
Additional Information:
The catalog minidisk blocksize changed to 4096 so all of the catalog files had to be changed to support the new blocksize by running REBLOCK EXEC.