Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories z/TPFDF
Created by Guest
Created on Feb 11, 2014

TPFDF should provide DBDEF user exits for invocation during the PACK operation.

TPFUG_Req_Number: DF00179
Contact Originator Id: claudio.jorge@eds.com
Abstract: TPFDF should provide user exits to be used during the pack process
Description: As each logical record is retrieved on the 'from' or input side of the file, TPFDF should check for a user exit in the DBDEF. If present, the code should be invoked with the option of returning to one of several branch vectors. Each branch point would result in a different action. For example, one branch would continue with a normal pack, another would skip the current logical record but continue and a third could stop the pack at that point and discard the rest of the data and lastly one would stop the pack and keep the rest of the data.
Critical Success Factors: The solution should be generic enough to fit the needs of a variety of contingency situation, e.g. emergency pack to decrease the size of the database, or to replace the existing chains with new pool addresses etc.
Alternative Solutions: It is possible to write applications code that can achieve same the results. However, each application would have to code, test, debug the solutions for many cases and also require driver and controller code to manage the process. This is needless duplication of effort, when TPFDF already has built-in capabilities.
Solution Considerations: There are several aspects to this requirement. The most critical is to provide logical record level exits to be used to keep or dispose of logical records and to continue or terminate the pack. Additional exits are possible, for example: At the start of PACK, (e.g. to turn on the new pool bit or turn on VFA candidacy or to switch to an alternative DBDEF version), at the point where each from block is retrieved (e.g. to set up header specific information), and finally at the end of Pack, (e.g. to turn off the new pool bit). Sample code that might be executed in a user exit could look like.

#IF TM WS02IN1,#WS02SPLT,ON INACTIVE RECORD?
L R14,CE1CR0 POINT TO RECORD
XC STDFCH(4),STDFCH CLEAR FORWARD CHAIN
B 4(,R6) TERMINATE THE PACK #ELSE
B 0(,R6) CONTINUE WITH THE PACK
#EIF

These exits can be made executable only by Utility code (e.g. ZUDFM or CRUISE) or be available even for PACKS triggered by user transactions. This could also be a DBDEF or API command line option e.g. DBCLS REF=…,PACK,CHECKEXIT=YES.

Idea priority Low
  • Guest
    Reply
    |
    Oct 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF