Avoiding Database Conversion Issues in BRMS

In V5R4 and above, conversion issues with the BRMS database can occur, to get around this problem, first run this command:

QSYS/CALL QBRM/Q1AOLD PARM('INSTALL ' 'ALTERTBL ' 'Y' '01' '01' '65535' 'TEXTFLDS ' 'QUSRBRM ' 'N')

If the the conversion errors still occur, run this command:

QSYS/CALL QBRM/Q1AOLD PARM('INSTALL ' 'ALTERTBL ' 'Y' '01' '01' '65535' 'TEXTFLDS ' 'QUSRBRM ' 'Y')


If users have fields in BRMS files that have a type of "OPEN", they can run the commands in this order:

  1. QSYS/CALL QBRM/Q1AOLD PARM('INSTALL ' 'ALTERTBL ' 'Y' '01' '01'  '65535' 'TEXTFLDS ' 'QUSRBRM ' 'Y')
    • Set the field to 65535 and change it from OPEN to HEX
  2. QSYS/CALL QBRM/Q1AOLD PARM('INSTALL ' 'ALTERTBL ' 'Y' '01' '01' '65535' 'TEXTFLDS ' 'QUSRBRM ' 'N')
    • Change the field from HEX to CHAR and leave the CCSID as is


NOTES:

  1. The job log may contain some database messages about loss of data (example: CPA32B2) or other informational messages (example: CPI3210) which can be ignored.
  2. In releases IBM i 6.1 and earlier, the following PTFs or their superseding PTFs are required: