Previous Topic: Return Code 79 - CXX IS WRONG VERSIONNext Topic: Return Code 81 - DDM PROCESSING ERROR


Return Code 80 - DDM ENVIRONMENTAL ERROR

Reason:

CA Datacom STAR has detected an error condition.

Action:

See the following internal return codes for details.

Return Code 80 Internal Return Codes

Dec

Hex

M

B

Explanation

User Response

001

01

N

N

NODE ENTITY-OCCURRENCE
NOT FOUND IN REMOTE DATADICTIONARY

Correct the CA Datacom Datadictionary definitions for the database, node, or both that are involved with the application receiving this return code.

002

02

N

N

DB ERROR WHEN READING DATADICTIONARY

CA Datacom STAR received a CA Datacom/DB error when reading CA Datacom Datadictionary.

Inspect the Multi-User Facility job log or Statistics and Diagnostics Area (PXX) for the corresponding system message.

003

03

N

N

MAXIMUM NUMBER OF NODES EXCEEDED

The current maximum number of nodes has been exceeded in your network.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

004

04

N

N

$ACCESS RELATIONSHIP NOT FOUND IN REMOTE DATADICTIONARY

Correct the CA Datacom Datadictionary definitions for the database, node, or both that are involved with the application receiving this return code. Execute DMUTLTY to verify the structure.

005

05

N

N

DDBCORE VALUE EXCEEDED

CA Datacom STAR is unable to
process the request because more memory is required than is currently allowed by the MUF startup option STAR specification.

Increase the STAR parameter specification for the amount of virtual storage and restart the Multi-User Facility. Rerun the application.

006

06

N

N

EXTWRT VALUE EXCEEDED

The value specified for the size of additional work areas generated to extend the task save areas in the
MUF startup option TASKS is not sufficient to process the remote request received.

Note This message may be
received at either the sending or receiving node.

Review the MUF startup option TASKS values at all nodes, ensuring that they are large enough to accommodate requests from all other nodes. If it is necessary to adjust the size, increase the parameter in the startup option specification and restart the Multi-User Facility. Rerun the application.

007

07

N

N

INTERNAL ERROR

CA Datacom STAR is unable to
process the request.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

008

08

N

N

LOST SESSION

A node with which CA Datacom STAR was in contact is no longer available.

CA Datacom STAR backs out any updates that were in progress to the last checkpoint. Perform the following procedure:

  • Investigate the reason for the outage with the remote node.
  • Perform recovery at both the local and remote nodes, if necessary.
  • Correct the cause of the outage.
  • Rerun any interrupted transactions.

009

09

N

N

LOST SESSION INDICATOR ON

A lost session occurred on a
previous CA Datacom/DB request
and the application has issued a
new request other than a COMIT, ROLBK, LOGCP, LOGCR, CLOSE, or LOGTB.

(See also the explanations for
Internal Return Codes 08 and 28.)

The application may continue to process if it issues a COMIT, ROLBK, LOGCP, LOGCR, CLOSE, or LOGTB. Perform the following procedure:

  • Investigate the reason for the outage with the remote node.
  • Perform recovery at both the local and remote nodes, if necessary.
  • Correct the cause of the outage.
  • Rerun any interrupted transactions.

010

0A

N

N

DATABASE ENTITY-OCCURRENCE NOT FOUND IN REMOTE DATADICTIONARY

Correct the CA Datacom Datadictionary definitions for the database, the node, or both that are involved with the application receiving this return code. Execute DMUTLTY to verify the structure.

013

0D

N

N

THE MAXELRQ PARAMETER IS LESS THAN 9

When operating CA Datacom
STAR, the minimum specification
for the MUF startup option
MAXELRQ is 9.

Increase the value for MAXELRQ to at least 9 and restart the Multi-User Facility. Rerun the application.

014

0E

N

N

DATADICTIONARY DOES NOT CONTAIN THE REQUIRED DDM ELEMENTS

The CA Datacom Datadictionary which CA Datacom STAR tried to access
does not contain the elements
which are required for CA Datacom STAR. These elements are added
to the CA Datacom Datadictionary when CA Datacom STAR is installed.

Re-inspect your installation jobs for normal completion and correct any errors. Ensure that CA Datacom Datadictionary is at the correct release level.

015

0F

N

N

INVALID USER REQUIREMENTS TABLE

The DBID= parameter in the User Requirements Table is specified as
a non-numeric value or as zero (0).

Correct the User Requirements Table.

016

10

N

N

REMOTE OPEN REJECTED DUE TO REMOTE MUF TERMINATION

A job attempted to open a remote database after a normal termination request was accepted by the
remote Multi-User Facility.

Rerun the job after the remote Multi-User Facility has restarted.

017

11

N

N

STRUCTURE INVALID

When CA Datacom STAR
attempted to open either a
partitioned, replicated, or
distributed database, it found
an error.

Perform the following procedure:

  • Run DMUTLTY to determine the database structure error.
  • Correct the structure in CA Datacom Datadictionary.
  • Rerun DMUTLTY to verify the database structure.
  • Rerun the application.

018

12

N

N

INVALID OPEN OF A REPLICA

The application attempted to open
a child of a replicated database for update. A child of a replicated database can only be opened for read-only access.

Perform the following procedure:

  • Check the DBID specified in the User Requirements Table used by the application.
  • Change the DBID specified in the User Requirements Table to the DBID for the parent database.
  • Rerun the application.

020

14

N

N

ITM ERROR

CA Datacom STAR is unable to
process the request for
one of the following reasons:

  • A CA Datacom STAR
    Configuration File (DKCF) definition error.
  • An error in the communication method definition.
  • A communications method resource (such as APPLID or
    UCB) is not active.
  • The target ITM or Multi-User Facility may not be running due
    to an abend or normal shutdown or the target ITM or Multi-User Facility may not be completely initialized when the job
    executed.

Perform one or more of the following procedures and make indicated corrections:

  • Verify the CA Datacom STAR Configuration File (DKCF) and the communications method definitions.
  • Check the Multi-User Facility job log for any CA Datacom STAR console messages.
  • Verify that the node is correctly defined in the CA Datacom Datadictionary.
  • If the target ITM or Multi-User Facility is not running, start the target Multi-User Facility. If the target ITM and Multi-User Facility is running but not completely initialized (startup messages DM00560I and DK02801I have not appeared), wait until the Multi-User Facility is available before submitting the job.

021

15

N

N

BASE FROM REMOTE REQUEST
HAS CHILD

The database structure definition in CA Datacom Datadictionary is inconsistent
across nodes. This condition occurs, primarily, when you have not
defined the parent/child
relationships of partitioned or replicated databases in the
same way in the CA Datacom Datadictionary
at different nodes.

Perform the following procedure:

  • Examine the structure definition of the database on the CA Datacom Datadictionary at each node involved and resolve the differences in the definitions.
  • Run DMUTLTY against each CA Datacom Datadictionary to verify both definitions.
  • Rerun the application.

022

16

N

N

INTERNAL ERROR

CA Datacom STAR is unable to
process the request.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

027

1B

N

N

INTERNAL ERROR

CA Datacom STAR is unable to
process the request.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

028

1C

N

N

ITM RETURN ERROR

The following series of events has occurred:

  • A lost session occurred on a previous CA Datacom/DB
    request and the application
    has issued a new request
    other than a COMIT, ROLBK, LOGCP, LOGCR, CLOSE, or
    LOGTB.
  • Processing has continued and
    the application has tried to re-access the node which
    caused the original lost session condition.
  • The original lost session
    condition is still in effect, prohibiting access to the
    node.

Perform the following procedure:

  • Investigate the reason for the outage with the remote node.
  • Perform recovery at both the local and remote nodes, if necessary.
  • Correct the cause of the outage.
  • Rerun any interrupted transactions.

029

1D

N

N

ITM DRAINING

The following series of events has occurred:

  • The console command DDM,DRAIN,ITM has been
    issued.
  • The application receiving this return code has attempted to
    open a remote database after
    the DRAIN command was
    issued.

Rerun the application after restarting CA Datacom STAR.

030

1E

N

N

MAXIMUM ELEMENTS EXCEEDED

The number of elements requested
by a remote request exceeds the number of elements allowed by the local MUF startup option MAXELRQ.

Examine the value for MAXELRQ at all of the nodes in the network, ensuring that the parameters are compatible. If it is necessary, increase the value of the MAXELRQ option to at least 9 and restart the Multi-User Facility. Rerun the application.

031

1F

N

N

INTERNAL ERROR

CA Datacom STAR is unable to
process the request.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

033

21

N

N

TRANSACTION BACKOUT NOT SPECIFIED

Transaction Backout is required for access to partitioned or replicated databases.

Specify TXNUNDO=YES in the User Requirements Table for the application and rerun the application.

034

22

N

N

DEPTH COUNTER EXCEEDED

CA Datacom STAR cannot locate a distributed database because the CA Datacom Datadictionary at each node
indicates that the database resides
at another node.

Examine the CA Datacom Datadictionary definition for the database in question at each node. Correct the error(s) and rerun DMUTLTY to verify the structure.

035

23

N

N

RESERVED INTERNAL RETURN CODE

This return code reflects the use of features reserved for CA Datacom STAR development staff.

If you receive this return code without use of some undocumented features of CA Datacom STAR, contact CA Support. For information about contacting CA Support, see Troubleshooting.

036

24

N

N

DATADICTIONARY UNAVAILABLE

This return code is a response to
the issuing of a
DDM DRAIN=DATADICTIONARY or
DDM CANCEL=DATADICTIONARY console command.

Applications continue to receive this return code until a DDM START=DATADICTIONARY is issued.

037

25

N

N

PARTITIONING/REPLICATION LENGTH ERROR

At least one partitioned or replicated child base had a record length
unequal to the rest of the
partitioned or replicated children.

Run a CXX report against each child database and examine the report for discrepancies in the record length of any table. Correct the definition of the database whose tables have incorrect record lengths.

038

26

N

N

LOST SESSION FROM DMOPCPR

A node with which CA Datacom STAR was in contact is no longer available.

CA Datacom STAR backs out any updates that were in progress to the last checkpoint. Perform the following procedure:

  • Investigate the reason for the outage with the remote node.
  • Perform recovery at both the local and remote nodes, if necessary.
  • Correct the cause of the outage.
  • Rerun any interrupted transactions.

040

28

N

N

INTERNAL ERROR IN DMXXCPR

Internal logic error occurred.

Contact CA Support. For information about contacting CA Support, see Troubleshooting.

042

2A

N

N

DBINFPR MAINTENANCE LEVEL ERROR

The STEPLIB for the application contains a version of DBINFPR
whose maintenance level is not supported by CA Datacom STAR.

Verify that the STEPLIB for the application contains a version of DBINFPR whose maintenance level is supported by CA Datacom STAR.

043

2B

N

N

OPEN USING RESERVED FTNO

The file table number specified
by the application is restricted to internal use only.

Correct the file table number.

044

2C

N

N

An attempt was made to use a component of a full-featured CA Datacom STAR in a Multi-User
Facility supporting only CA Datacom STAR Server. (CA Datacom STAR Server Multi-User Facilities cannot open partitioned or replicated databases or databases at a remote location. These Multi-User Facilities can only accept in-bound requests from CA Datacom STAR for PC.)

Contact your sales representative for the purchase of the full-featured CA Datacom STAR product or, if you are already licensed for that product, contact your local CA Support group for assistance.