Getting Started › Procedures and Triggers › Multi-User Facility Considerations for Procedures

Multi-User Facility Considerations for Procedures

This section provides considerations for executing and coding procedures to run in the CA Datacom/DB Multi-User Facility.

Note: Because SQL has no way of verifying the compatibility of the user-written code with the procedure defined by the CREATE PROCEDURE statement, it is the sole responsibility of the creator of the procedure to help ensure that the CREATE PROCEDURE statement precisely reflects the parameter list expected by the user-written program. Failure to properly coordinate parameter lists can cause the procedure subtask to abnormally terminate.

Certain tasks need to be performed to execute procedures. Do the following tasks before bringing up the CA Datacom/DB Multi-User Facility.

• Add to the Multi-User Facility library concatenation the Language Environment (LE) runtime and associated language libraries that are needed to execute the procedures. For z/OS, place these ahead of the CA Common Services for z/OS runtime libraries. For z/VSE, place these ahead of the CA CIS (Common Infrastructure Services) runtime libraries.
• Add to the Multi-User Facility library concatenation the libraries containing the programs to be executed as procedures, with any associated subroutines.
• Add an appropriate PROCEDURE Multi-User startup option to the Multi-User Facility SYSIN. Code procedure nests and subtasks carefully.
• Add the appropriate Language Environment (LE) and associated language support data sets to the Multi-User Facility startup job.
• Modify the Language Environment (LE) parameter style exit routine for COBOL, IGZEPSX, to enable the code to provide the same parameter list processing that was done when running VS COBOL II runtime with the ATTACH SVC on MVS. This allows for passing Register 1 and the parameter list without change to the main COBOL procedure program, instead of having the parameter list style determined by Language Environment.
• Make certain you have upgraded Language Environment for z/OS to at least the V2R5.0 release level.

  Note: Support for procedures and triggers requires a minimum of z/OS Version 2 Release 5 and compatible Language Environment for z/OS with the following IBM compiler products: z/OS C/C++ (only the C subset is supported), COBOL for z/OS, and PL/I for MVS.

When coding, compiling, and link editing programs that are to execute as procedures, adhere to the following guidelines:

• Do not modify in your procedure program the Language Environment (LE) user area fields (not to be confused with the PL/I user area). These are set and queried by the procedure processor and interface in the Multi-User Facility by use of the Language Environment CEE3USR callable service.
• All procedure programs with embedded SQL statements must be LE-conforming and must be link edited with the procedure interface DBXPIPR.
• All procedure programs must be coded and link edited as RENT and NODYNAM (no dynamic calls) with AMODE(31) and RMODE(ANY).
• Ensure that the link-edit step receives a return code of 0. Any return code greater than 0 indicates a possible error that could lead to a Multi-User Facility abend. A possible error could be having included an SQL User Requirements Table to resolve the DBNTRY entry point. For example, do not include DBSBTPR. All CA Datacom/DB entry points should be resolved by the inclusion of DBXPIPR, and duplicates should not occur. The exception is the include for DBXHVPR to resolve COBOL host variables.
• Modify your installation defaults for LE to specify the following recommended settings, or include with each procedure program link-edit a CEEUOPT module with these settings:

   ABTERMENC=(ABEND)
   ALL31=(ON)
   ANYHEAP=(1K,1K,ANYWHERE,FREE)
   BELOWHEAP=(1K,1K,FREE)
   HEAP=(32K,32K,ANYWHERE,FREE,8K,4K)
   LIBSTACK=(1K,1K,FREE)
   STACK=(4K,4K,ANY,KEEP)
   STORAGE=(00,NONE,00,0K)
   TERMTHDACT=(UADUMP,,32)
   TRAP=(OFF)
  

Note: While these options are recommendations, they may not be appropriate for your site or may need to be tuned according to your procedure execution environment within the Multi-User Facility. Run a typical procedure with the RPTSG=(ON) option in CEEUOPT and tune accordingly.