The CA IDMS R19 AGJ4RECD job may get errors GIM20311E & GIM56701E along with a RC = 8. These errors are not unique to CA IDMS or to r19; they can appear on any RECEIVE job. The rest of the job may appear to run with complete success, even when these errors are issued.
CA has one HOLDDATA bucket for all mainframe products. So when the HOLDDATA parm is included on the include (which is required in case there are HOLDDATA members for the FMIDs you're installing), the RECEIVE will actually try to process everything in the CA HOLDDATA file.
In general, on an RECEIVE job, the GIM20311E & GIM56701E errors can be ignored. They usually relate to products (FMIDs) that are not installed at the client site; they could be non-IDMS products or components of IDMS that you have not installed.
For example, in applying CA IDMS 19.0, the AGJ4RECD job may abend with a RC = 8 along with the following messages:
GIM39401I SMPTLIB DATA SETS WERE LOADED FOR SYSMOD CAGJJ05.
GIM22701I RECEIVE PROCESSING WAS SUCCESSFUL FOR SYSMOD CAGJJ05.
----------++HOLD(RO95494) ERROR FMID(CBTDC10)
GIM20311E ** THERE IS A SYNTAX ERROR IN THE CONTROL STATEMENT AT COLUMN 36.
GIM56701E ** THERE IS AN ERROR IN A ++HOLD MCS FOR SYSMOD RO95494 IN SMPHOLD.
----------++HOLD(RO95495) ERROR FMID(CBTDC50)
GIM20311E ** THERE IS A SYNTAX ERROR IN THE CONTROL STATEMENT AT COLUMN 36.
GIM56701E ** THERE IS AN ERROR IN A ++HOLD MCS FOR SYSMOD RO95495 IN SMPHOLD.
----------++HOLD(CB0V530) ERROR FMID(CB0V530)
GIM20311E ** THERE IS A SYNTAX ERROR IN THE CONTROL STATEMENT AT COLUMN 36.
GIM56701E ** THERE IS AN ERROR IN A ++HOLD MCS FOR SYSMOD CB0V530 IN SMPHOLD.
From these errors we extract the following list of FMIDs, shown here with the product names the represent:
FMID(CBTDC10) Product CA MII
FMID(CBTDC50) Product CA MII
FMID(CB0V530) Product CA-TPX
FMID(CAVQE05) Product CA IPC-IPC
If your job generates these messages, it is likely that your site does not have any of these other CA products installed. If your site does have any of these installed, you should contact CA Support to determine how to resolve these errors. If your site doesn't have of them involved, then these messages can be ignored.