IBM Power Ideas Portal
Hide about this portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on May 21, 2019

RELATED IDEAS

SAVLIB / RSTLIB - Guarantee that all type external procedures are saved and restored

See this idea on ideas.ibm.com

Our company does SAVLIB backups of production libraries for last resort recovery and development environment restoration. There is a hole in this process that is recognized in "External Procedures, Triggers, and User-Defined Functions on IBM DB2 for i" section 4.6, but not widely known. This has the potential for users to unknowingly have an incomplete backup when using the SAVLIB command.

When users create a procedure, the system puts the routine in sysibm.routines but also in the PAS/Marker of the created CLE object. When an external procedure is created this marker information is stored in the external object. If, however, the object is OPM or not an embedded SQL ILE object the routine will not be added to the object. If the external object that contains the routine information is deleted and recompiled the routine information will be lost.

Since the RSTLIB function relies on this PAS/Marker data to recreate the procedures at restore time routines for OPM, non SQL ILE, or recompiled objects will not be restored.

The change being requested is that all of the routines stored in sysibm.routines for the library being saved be stored in some way (i.e. a special object created at SAVLIB time and saved with the library). When restoring the library the system could check for any routine stored in this special object that had not already been created by objects that had the PAS/marker information. This would ensure that all routines that were in a library at the time of it being saved are also restored.

We have had to mitigate this by using the "GENERATE_SQL" procedure with the create or replace option to save all routines to a source member in the same library before saving the library. We run this immediately before the SAVLIB to ensure that a backup of all routines are present for the library. For automated restores to development we then use the RUNSQLSTM

Example “save” of routine Text
CALL QSYS2.GENERATE_SQL('%', 'MYLIB', 'FUNCTION',
‘SQLDUMP', 'MYLIB', 'SOURCE', REPLACE_OPTION => '1');

CALL QSYS2.GENERATE_SQL('%', 'MYLIB', 'PROCEDURE',
'SQLDUMP', 'MYLIB', 'SOURCE', REPLACE_OPTION => '0')

Example “restore” of routines
RUNSQLSTM SRCFILE(MYLIB/SQLDUMP) SRCMBR(SOURCE) NAMING(*SQL) ERRLVL(35)


Use Case:

In the event that a library had to be restored due data recovery needs or routine restoration for other reasons the user would be assured that all procedures are saved and restored.


Idea priority Medium
  • Guest
    Reply
    |     Dec 21, 2021

    Any implementation of this RFE would apply to external procedures and functions. There was an additional request added in the comments for external triggers. If new save/restore processing is needed for triggers, please submit a separate RFE request.

  • Guest
    Reply
    |     Feb 26, 2021

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.

  • Guest
    Reply
    |     Oct 20, 2020

    The CAAC has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to be addressed. This would benefit the vendors as well as the community. Having the ability to save and restore SQL procedures, triggers, etc., would enhance the adoption of SQL on IBM i.

    Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.

    For more information about CAAC, see www.common.org/caac

    For more details about CAAC's role with RFEs, see http://www.ibmsystemsmag.com/Blogs/i-Can/May-2017/COMMON-Americas-Advisory-Council-%28CAAC%29-and-RFEs/

    Nancy Uthke-Schmucki - CAAC Program Manager

  • Guest
    Reply
    |     Sep 23, 2020

    Same has to be resolved for triggers:

    CRTLIB LIB(TSTTRIGGER)
    TEXT('test saving tiggers')

    QSYS/ADDPFTRG FILE(THEO_001/AUTOVVATST)
    TRGTIME(*AFTER)
    TRGEVENT(*DELETE)
    PGM(THEO/AUTOVVATST)
    TRGLIB(TSTTRIGGER)


    crtsavf qrplobj/sav001

    SAVLIB LIB(TSTTRIGGER)
    DEV(*SAVF)
    SAVF(QRPLOBJ/SAV001)

    crtsavf qrplobj/sav002

    SAVOBJ OBJ(AUTOVVATST)
    LIB(THEO_001)
    DEV(*SAVF)
    SAVF(QRPLOBJ/SAV002)

    dltlib TSTTRIGGER

    RSTLIB SAVLIB(TSTTRIGGER)
    DEV(*SAVF)
    SAVF(QRPLOBJ/SAV001)

    NO trigger!!!!!

    RSTOBJ OBJ(AUTOVVATST)
    SAVLIB(THEO_001)
    DEV(*SAVF)
    SAVF(QRPLOBJ/SAV002)

    Still no trigger!!!

  • Guest
    Reply
    |     Jun 8, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Db2 for i
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Save, Restore
    Operating system - IBM i
    Source - None

  • Guest
    Reply
    |     Aug 6, 2019

    The COMMON Europe Advisory Council (CEAC) has reviewed this requirement and recommends that IBM view this as a high priority requirement that is important to address.

    With continuous integration, developers and managers need flawless deployment with data integrity. This enhancement will enable this and is strategic for IBM i development.

    Background: The CEAC members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a crucial role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community and has therefore reviewed your RFE.

    To find out how CEAC help to shape the future of IBM i, see CEAC @ ibm.biz/BdYSYj and the article "The Five Hottest IBM i RFEs Of The Quarter" at ibm.biz/BdYSZT

    Therese Eaton – CEAC Program Manager, IBM

  • Guest
    Reply
    |     May 23, 2019

    IBM has received the requirement and is evaluating it. IBM will provide a response after evaluation is complete.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.