After creating a new Datacom/DB or Datacom/AD Multi-User Facility (called MUF), and setting up the security definitions to use Datacom External Security, you might receive an error message when using SYSVIEW commands for Datacom, such as DCAREAS, DCBASES, etc. This error message might be:
DCOM006E GETDATA request failed, RC 15, RS 39, FC 51, Job xxxxxxxx or
DCOM006E GETDATA request failed, RC 15, RS 139, FC 51, Job xxxxxxxx
Release: All supported releases
In this message, the RC 15, combined with the RS 39 (which is a truncated "139" value) indicates the problem. the FC 51 value indicates that this SYSVIEW instance is connected to a Datacom version 15.1 MUF.
The Return Code 15 (139) error indicates that there is a problem with the ESM security definition, and that the SYSVIEW user does not have access to the Datacom System Tables in database 1000 for the selected MUF.
The most probable cause for this error is that a rule or profile is missing from the External Setting setup for this MUF.
Within the External Security schema, there are multiple resource types used, and in this case, the resource type is called DTTABLE (called DT@ABLE in IBM RACF). There are multiple profiles that could be defined inside this resource, and it is necessary to have one like one of the following:
Note that DB 1000 is used by default here, and is based on your MUF Startup Option SYSTEMDBID. If you have changed this value, then you need to use that DBID value in the DTTABLE (or DT@ABLE) profile.
Finally, to be sure that your SYSVIEW session can access the Datacom System Tables correctly, you need to be sure to grant UPDATE access to the tables in DB 1000 (in ACF2: SERVICE(READ,UPDATE); in Top Secret: ACCESS(UPDATE); in IBM RACF: ACCESS(UPDATE)).
For more information about Datacom External Security configuration and usage, please refer to the Datacom documentation section Using External Security for Datacom.
As always, please contact Broadcom support for Datacom if you have further questions.