AS400 host cannot access Data Domain VTL and dumps continuous errors

IBMi commands to access or display Tape Cartridges fail and cause AS400 host to dump errors.
Following it's an example with DSPTAPCTG, but similar error is reported by WRKTAPCTG:

DSPTAPCTG DEV(TAPMLB14)                                             
Dump output directed to spooled file 1, job 784780/ECCJAK/QPADEV0001
  created on system ECC on 01/13/23 14:49:44.                       
Dump output directed to spooled file 2, job 784780/ECCJAK/QPADEV0001
  created on system ECC on 01/13/23 14:49:44.                       
Ownership of object QSC1350912 in QSYS type *LIB changed.           
Ownership of object QSCAPAROQ in QSC1350912 type *OUTQ changed.     
Ownership of object QSCAPARMST in QSC1350912 type *USRSPC changed.  
Ownership of object QSCPROBLEM in QSC1350912 type *USRSPC changed.  
Ownership of object QSCASF000A in QSC1350912 type *USRSPC changed.  
Ownership of object QSCASF000D in QSC1350912 type *USRSPC changed.  
Ownership of object QSCASF001A in QSC1350912 type *USRSPC changed.  
Ownership of object QSCASF001D in QSC1350912 type *USRSPC changed.  
Save APAR Data function completed                                   
Problem information created for 2301350912.                         
Cartridge command was not successful.

VTL reports conflicting information to some specific Read Element Status request from AS400.
The trigger for the issue is a vtl export from drive to vault.
After this operation has been executed on Data Domain, either in CLI or GUI, when AS400 host try to access tape cartridges the information provided by DD about the exported tape cartridge are not valid.
If IBMi Read Element Status command does not request barcode information, DD VTL reports the drive still loaded.
If IBMi Read Element Status command requests barcode information, DD VTL reports the drive as empty.

Conflicting information provided by DD VTL causes an inconsistent inventory on AS400 host and the host cannot manage VTL anymore.

The issue has been escalated to Data Domain engineering and a code fix will be released in a future release.
For the time being, vtl export from drive to vault should be avoided.

The suggested workaround is as follows:

1. If not already done, configure CAP for all VTLs accessed by AS400 hosts.

   # vtl cap add <VTL_name> count <numer_of_CAP_slots>

2. Check the status of option auto-eject for all the VTLs configured.

   # vtl option show auto-eject

3. If disabled, enable vtl option auto-eject for all the VTLs accessed by AS400 hosts

   # vtl option enable auto-eject vtl <VTL_name>

4. Use IBMi Eject command to move the tape from drive to CAP. The auto-eject option will automatically move the tape from CAP to Vault, emulating vtl export command.

If you don't want to configure CAP and enable auto-eject you should run vtl export command in 2 steps:

1. Move the tape from drive to slot.

   # vtl tape move <VTL_name> source drive <drive_number>  destination slot <slot_number>

2. Export tape from slot.

   # vtl export <VTL_name> slot <slot_number>