Skip to content
CA Datacom/DB for z/VSE - 12.0
Documentation powered by DocOps

Working With CA Datacom CICS Services

Last update March 14, 2018

The CA Datacom® CICS Services provide the following features:

Supports Various Languages

Application programs can be written using:

  • CA Ideal
  • Assembler
  • COBOL (with or without the use of CA MetaCOBOL+)
  • PL/I using a command-level interface to CICS/TS

Selects URT for Executing Application

In the CA Datacom®/DB environment, it is the URT associated with the program that communicates all program-specific information to CA Datacom®/DB, such as the following:

  • Which MUF (in a multiple MUFs environment) requests using this URT are processed
  • Which tables the application can access and update
  • Whether transaction backout is made available for any abending update transactions to the listed tables
  • Relative priority within the MUF for the program-issued requests

CA Datacom®/DB requires every executing program to be associated with a URT. In batch, you determine which URT a given program is to use.

Under CICS

CA Datacom® CICS Services handles the association of a URT with your application program for you. You define several URTs from which CA Datacom® CICS Services makes a selection at execution time, depending on the database and table in which the requested data resides, and optionally (in a multiple MUFs environment) which MUF is to process the request.

Note: Multi-MUF environment is not supported in z/VSE

Connects and Disconnects MUFs

To use system resources effectively under CICS

CA Datacom® CICS Services performs connect and disconnect functions. The DBCSID macros specify how and when CICS Services connects to each MUF. All MUFs are disconnected during CICS Services shutdown. You can specify general exceptions through the DBCSID macro appended to the System Generation Options Table (DBCVTPR). Or, you can explicitly invoke connect or disconnect at anytime through online commands. In the DBCSID macros, you can specify that MUFs are connected:

  • Only when their use is required 
  • Only when you enter an online command to request connect 

If no DBCSID macro is coded, connect is done at PLT time.

Opens and Closes URTs

To use system resources effectively under CICS

The Open and Close functions are performed by CA Datacom® CICS Services. Unless you specify otherwise, CA Datacom® CICS Services opens all URTs at CICS startup and closes all URTs at CICS shutdown. You can specify general exceptions through the System Generation Options Table (DBCVTPR). Or, you can explicitly invoke an open or close at anytime through online commands. In DBCVTPR, you can list URTs to be opened only when their use is required or only when you enter an online command to request the open.

Manages Allocated Threads

CA Datacom®/DB allows applications to use multiple URTs through an extended request technique. CA Datacom® CICS Services uses this technique without requiring the CICS application programmer to code extra logic. A CICS application program can be coded with the same call request format as a batch program. The extended request logic allocates for CICS usage several processing threads to CA Datacom®/DB. CA Datacom® CICS Services obtains and releases the allocated threads as required. This allows multi-threading of application requests. The multi-thread logic permits concurrent processing of several CICS transactions.

Update requests require sole use of a single thread. CA Datacom® CICS Services optimizes thread use by placing multiple read-only transactions on the same thread, thus reserving additional threads for transactions performing update requests. Once processing on a reserved thread is complete, CA Datacom® CICS Services commits resources automatically.

Extends CICS Processing Functions

CA Datacom® CICS Services provides other functions related to CICS processing. CICS provides a trace function for CICS activities, transaction backout of abending tasks, and SYNCPOINT processing. CA Datacom® CICS Services extends these CICS functions to the CA Datacom®/DB processing environment as follows:

  • Provides a before and after CICS trace entry on each database request. See CICS Trace Table Entries.
  • Invokes a CA Datacom®/DB backout for any task which updates a database, but abends before completion.
  • Issues a CA Datacom®/DB checkpoint to the appropriate MUF or MUFs when a transaction issues a CICS SYNCPOINT. For details on techniques for improving the operating efficiency of your online applications, see Updating Technique.

Supports User Exits

CA Datacom® CICS Services provides facilities for implementing two user exits, one before CA Datacom® CICS Services issues a CA Datacom®/DB call, and one both before and after accessing CA Datacom®/DB. You can use these exits to tailor CA Datacom® CICS Services to the requirements of your site.

Displays System Resources on Request

You can monitor system resources at anytime by issuing an online inquiry command to display a selected resource. CA Datacom® CICS Services displays the requested information in a formatted panel or in scrollable form, depending on the transaction ID. CA Datacom® CICS Services is installed with the following CICS transaction IDs for issuing online commands to monitor system resources:

    The inquiry command invokes a scrollable display of MUFs or URTs and, if requested, the tables that are listed in each URT. In an MRO environment  the display can be limited to MUFs or URTs in a specified CICS, or extend to MUFs or URTs in all CICS systems, or a range of CICS systems.
    Twenty inquiry commands are available to invoke formatted displays of the following resources and data:
    • URTs, with or without associated CA Datacom®/DB table information
    • Trace table, either scrollable display of entries, criteria on which trace is based, or status of Auxiliary Trace
    • Statistics: Active tasks, held transactions, abending tasks, concurrent users, requests by return code
    • Options currently in use (defined through System Option Table (DBCVTPR) parameter values)
    • Software maintenance level
  • DBUT
    Displays storage areas for CICS programs and system tables at specified locations.

Controls System Resources on Request

If authorized for the required transaction ID, you can alter system resources by issuing the appropriate online command. CA Datacom® CICS Services displays messages on the command results. CA Datacom® CICS Services is installed with the following CICS transaction IDs for issuing online commands to alter system resources:

  • DBEC
    The scrollable display that an INQuire command invokes contains fields which are updatable when the command is issued through DBEC. Also, several PERform commands invoke actions which alter MUF or URT resources within the local or remote CICS systems and startup/shutdown in the local or remote CICS systems.
  • DBOC
    Twenty-four commands permit you to modify or control:
    • URTs
    • CA Datacom®/DB tables
    • CA Datacom® CICS Services modules or control tables
    • Trace Facility and Auxiliary Trace Facility
    • CA Datacom® CICS Services operation and options
  • DBUT
    Allows you to alter CICS programs and system tables.

Facilitates Application Development

CA Datacom® CICS Services facilitates application development with the following:

  • DBTX
    Accepts read-only requests to CA Datacom®/DB, allowing you to examine command syntax or simulate program logic.
  • DBTS
    Accepts read-only and update requests to CA Datacom®/DB, allowing you to examine command syntax or simulate program logic and also update the specified database.
  • DBUG
    Intercepts CA Datacom®/DB requests issued by an executing application program, allowing you to examine its processing.

Provides Means of Restricting or Extending Inquiry and Control

CA Datacom® CICS Services provides multiple transaction IDs through which the security administrator can restrict the use of control commands to authorized users.

  • Three alternate CICS transaction IDs are provided to enable the security administrator to authorize users to invoke inquiry displays while limiting their access to control commands. Specifically, the security administrator can authorize a limited set of users the access to Operational (DBOC), Enhanced (DBEC) and Test Facility (DBTS) transaction IDs which are valid with commands which allow the control of resources. The security administrator can provide unrestricted access to the Inquiry (DBIC), Enhanced Inquiry (DBEX), and Test Facility Read-Only (DBTX) transaction IDs which can be used only with "inquiry" type commands.
  • A means of limiting authorized users for the DBOC transactions to initiate/terminate CA Datacom® CICS Services or alter online the System Generation Options that are coded in DBCVTPR is provided. This limiting is accomplished through use of the MSTOPR= parameter in the System Options Table, which accepts up to 50 operator IDs.

Provides Security for Database Access

To promote the security of database access, CA Datacom® CICS Services passes CA Datacom®/DB the following with each CA Datacom®/DB request:

  • User identification: Either the 3-byte operator ID or the 8-byte operator name from the CICS sign-on table (CESN OPERID or CESN USERID), depending on your specifications. CA Datacom®/DB secures access and update to CA Datacom®/DB tables, record, fields, and elements based on the ID of the request initiator. If you have CA Top Secret or RACF from IBM, these security products provide the ACEE address to CA Datacom® CICS Services.
  • CA ACF2 supplies the eight-byte USERID to the CESN USERID field, if available. Otherwise, your DFHSNT entry is used.
Was this helpful?

Please log in to post comments.