XCOMHIST migration "RECORD ... NOT WRITTEN. LENGTH INVALID"

Products

• XCOM Data Transport - z/OS
• XCOM Data Transport

Issue/Introduction

Have applied maintenance on XCOM 12.0 and the apply job was successful.
However, receiving errors when trying to migrate XCOMHIST data set using sample JCL XCOMH120 in CBXGJCL.
Job log shows:
===
  REPRO IFILE(INPUT) OFILE(OUTPUT)
0IDC3302I  ACTION ERROR ON AAA.BBB.CCC.DDD.HSTSAV.H01
 IDC3309I ** RECORD X'0000000000' NOT WRITTEN.  LENGTH INVALID
0IDC3302I  ACTION ERROR ON AAA.BBB.CCC.DDD.HSTSAV.H01
 IDC3309I ** RECORD X'0122256FDC' NOT WRITTEN.  LENGTH INVALID
0IDC3302I  ACTION ERROR ON AAA.BBB.CCC.DDD.HSTSAV.H01
 IDC3309I ** RECORD X'0122256FDC' NOT WRITTEN.  LENGTH INVALID
0IDC3302I  ACTION ERROR ON AAA.BBB.CCC.DDD.HSTSAV.H01
 IDC3309I ** RECORD X'0122274FDC' NOT WRITTEN.  LENGTH INVALID
 IDC31467I MAXIMUM ERROR LIMIT REACHED.
0IDC0005I NUMBER OF RECORDS PROCESSED WAS 0
0IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
===

Environment

XCOM™ Data Transport® for z/OS

Cause

The value LRECL=3034 is correct for a version 11.6 XCOMHIST data set, but is not correct for a version 12.0 XCOMHIST data set

Resolution

For STEP1  "IDCAMS REPRO the old XCOMHIST to a sequential file" a value of LRECL=3034 was being used i.e. DCB=(RECFM=VB,LRECL=3034,BLKSIZE=24304).  It is necessary to use LRECL=8080 as it is the new record length for version 12.0 (Define/Migrate the VSAM History File).

After applying maintenance to 12.0, it is not actually required to migrate the XCOMHIST data set i.e. the migration job should only be used when going from releases 11.5 or 11.6 to release 12.0.
To purge/reclaim space/reorganise the XCOMHIST at any time use the XCOMUTIL utility and sample XCOMUTIL JCL is located in the CBXGJCL library.
See the documentation page XCOMUTIL History File Utility and subsequent pages e.g. XCOMUTIL DD Statements ("Sample History File Purge Process (XCOMUTIL)").