Introduction to CA IDMS Data Manipulation Language › Programming in the CA IDMS Environment › CA IDMS/DC Statements

CA IDMS/DC Statements

CA IDMS/DC and CA IDMS UCF are fully integrated with CA IDMS/DB and the dictionary. They allow you to request both data communications and database services through standard subroutine calls generated (by the DML precompiler) from DML statements.

Example of a PL/I Data Stream with CA IDMS/DC Statements

The following is a typical PL/I data stream containing DML statements. The CA IDMS/DC MAP IN, MAP OUT, and DC RETURN statements map in a user-specified employee ID, retrieve and display the specified information, and perform a DC RETURN naming TSK02 as the next task to be performed.

BIND MAP (EMPMAPLR);
BIND MAP (EMPMAPLR) RECORD (EMPLOYEE);
ACCEPT TASK CODE INTO (TASK_CODE_IN);
IF TASK_CODE_IN = 'TSK01' THEN
        GO TO INITIAL_MAPOUT;
MAP IN (EMPMAPLR);
 .
 .
 .
Database DML statements
 .
 .
 .
MAP OUT (EMPMAPLR)
    OUTPUT DATA YES
    MESSAGE (DISPLAY_MESSAGE) LENGTH (80);
DC RETURN NEXT TASK CODE ('TSK02');

Types of Online CA IDMS/DC Statements

Online CA IDMS/DC statements request that the DC/UCF system perform data communications services. There are nine types of online CA IDMS/DC DML statements:

• Program management statements govern flow of control and abend processing.
• Storage management statements allocate and release variable storage.
• Task management statements provide runtime services that enhance control over task processing.
• Time management statements obtain the time and date, and define time-related events.
• Scratch management statements create, delete, or retrieve records from the scratch area.
• Queue management statements create, delete, or retrieve records in a queue area.
• Terminal management statements transfer data between the application program and a terminal.
• Utility function statements retrieve task-related information or statistics, send messages, and monitor access to database records.
• Recovery statements perform functions relating to database, scratch, and queue area recovery in the event of a system failure.