Skip to main content

Software  >  Information Management  >  DB2 Product Family  >  

Introducing DSNTPSMP level 1.15

 Flash (Alert)
 
Abstract
Introducing DSNTPSMP level 1.15, a significant update to the SQL Procedure processor on DB2® for OS/390® and z/OS™.
 
Content
Known as the "BuildUtility" to users of the DB2® Development Center, DSNTPSMP is the Language REXX stored procedure that performs all of the server-side build functions required for development of SQL stored procedures on DB2 for OS/390 and Z/OS.

During the course of any application development effort, errors inevitably occur for many reasons. These errors can range from programmer syntax errors on one end of the spectrum to tool set and process related failures on the other end. "BUILDS" using distributed function development presents additional challenges on the tool set side of the spectrum. DSNTPSMP has been updated via APAR PQ45854 to approach the difficulties of diagnosing build problems during SQL stored procedure development. Emphasis has been placed on detecting and handling the root causes of many types of problems that customers report to IBM Software Support. This solution gives the broadest coverage possible while also strengthening the integrity of the build process.

Certain problems are detected before they can cascade into larger, less distinct, and harder to diagnose issues. In these cases the Build stops before certain failure occurs and provides relevant messages about the error and, when appropriate, any recommended actions to take. This action prevents wasted time for both the user and the system. In cases where the DSNTPSMP can make corrections, they are made so a build can proceed with merely a warning.

The areas of error detection and handling addressed in DSNTPSMP 1.15 include the following situations:

  • Incorrect or missing environment setup (WLM configuration)
  • Incorrect, missing, or conflicting Build requests (Client input)
  • Missing, hidden, or misrepresented feedback (Build step output)

Even with this enhancement, problems can still occur during a Build. For example, a compile might fail. DSNTPSMP puts more effort into interpreting and returning relevant information about the failing context, such as reporting the abend code along with the failing program name.

To compensate for the extra workload, DSNTPSMP has been restructured to be more efficient in the use of SQL statements, file processing, and REXX programming techniques.

DSN8WLMP, the sample WLM startup PROC for DSNTSPMP, is updated to reflect and reenforce the required and appropriate WLM-SPAS definitions, essential for configuring a REXX stored procedure environment for the proper execution of the SQL Procedure processor.

A new build Summary was added to the result set that is returned to the development client; it provides positive confirmation of Build actions to the user. This summary includes a recap of the Build request, the action taken, and the names of program and package objects affected. This summary reduces the risks coming from problems where uncertainty is a significant factor. The new DSNTPSMP Summary can be disabled, but it is highly recommended that you use it in all cases. The following example shows sample Summary information:
                                                       
Request: BUILD routine USRT003.Proc7 was successful.
Action : "USRT003"."PROC7" was BUILT                
Package: TEST.SQL38645                              
Program: SQL38645                                   
                                                                                                                                                               
Capabilities were added for System Administrators to establish configuration settings for the SQL Procedure Processor. This capability allows features and controls to be adjusted without modifying the DSNTPSMP program itself. Each WLM-SPAS environment for DSNTPSMP can be uniquely configured. You can do the following activities:
  • Define the C compiler that DSNTPSMP should use during the build process
  • Establish defaults for selected bind package options to meet site guidelines
  • Activate or disable DSNTPSMP tracing as needed for additional build diagnosis

Refer to the APAR description for PQ45854 for additional details.

DB2 development recommends that all users that develop SQL stored procedures on DB2 for OS/390 and z/OS upgrade to DSNTPSMP level 1.15. APAR PQ45845 is available with these PTFs:
  • UQ72854 V6
  • UQ72855 V7

You can find more information about APAR PQ45854 and its associated PTFs at the zSeries® Server Support APAR Database.
 
Related information
zSeries APAR Database
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information ManagementDB2 for z/OSDB2 Rexx
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Data Management
 Data Servers (Database Management Systems)
 DB2 for z/OS
 Stored Procedures
 Operating system(s):
  OS/390, z/OS
 Software version:
  7.0, 8.0
 Reference #:
  1108839
 IBM Group:
 Software Group
 Modified date:
 2008-12-29

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.