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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Enhance SQL *PRV Signature Support to be at least as good as *SRVPGM Signatures
When creating an SQL VIEW that uses an IBM i Service or another SQL Table Function on release "N" and the restoring that SQL VIEW onto another system with release N-1, a Signature Violation occurs when attempting to query that SQL VIEW using SQL. This RFE requests that either that signature violation be reduced to a warning and the VIEW be permitted to work as expected, or you implement a multiple (endless) signature support in SQL Functions as has been done with Binder Language and *SRVPGM Signatures.
I create an SQL VIEW on V7R3 (see example below) using RUNSQLSTM with TGTRLS(V7R2M0) specified and then send that VIEW object to a V7R2 partition. I then use SQL to query that view. It fails with Signature Violation. The likely cause is that the SQL Table Function being used has had additional parameters added to it in V7R3 or later. However in this context, none of those extra parms are not being used. Thus our clients (and some developers) react with "Not only is AS/400 old, it no longer works". Here's a great example . the SYSTEM_STATUS table function had one additional parameter added after V7R2. however in this context, I am using ZERO parameters so it should not matter. (Whether or not it does internally). However while this runs flawlessly on V7R3 and R4, it fails to run on V7R2. This is NOT how TGTRLS is supposed to work. However, if I "compile" on V7R2, it will run on V7R3, R3, R4, and presumably V7R+1. CREATE OR REPLACE VIEW SQLTOOLS.QSYSERR ( SYSTEM_NAME FOR COLUMN SYSNAME, MESSAGE_ID FOR COLUMN MSGID, MESSAGE_SEV FOR COLUMN MSGSEV, DATE_POSTED FOR COLUMN POSTED, RESOURCE, FAILING_PART FOR COLUMN ITEMNUMBER, MESSAGE_TEXT FOR COLUMN MSGTEXT ) AS (SELECT CAST(SYS.HOST_NAME AS VARCHAR(10)) AS SYSTEM, M1.message_ID AS MSGID, M1.severity AS MSGSEV, CAST(M1.MESSAGE_TIMESTAMP AS TIMESTAMP(0)) AS POSTED, RTRIM(CAST(REGEXP_SUBSTR(M1.MESSAGE_SECOND_LEVEL_TEXT, '(\bdisk device\b)\W(\w+)', 1, 1, 'i', 2) AS VARCHAR(20))) AS RESOURCE, LTRIM( RTRIM( CAST( COALESCE( REGEXP_SUBSTR(M1.MESSAGE_SECOND_LEVEL_TEXT, '(\bfailing item\b)\W(\w+)', 1, 1, 'i', 2), REPLACE( REGEXP_SUBSTR(M1.MESSAGE_SECOND_LEVEL_TEXT, '(\bpossible failing items: &P\b)\W(.*)Press F14', 1, 1, 'i', 2), '&P', '')) AS VARCHAR(120) ))) AS FAILING_PARTS, CAST(M1.MESSAGE_TEXT AS VARCHAR(132)) AS MSGTEXT FROM TABLE ( QSYS2.MESSAGE_QUEUE_INFO() ) M1, LATERAL ( SELECT host_name FROM TABLE ( QSYS2.system_status(reset_statistics=>'NO') ) S ) SYS WHERE LEFT(M1.message_ID, 3) = 'CPP' AND M1.message_ID <> 'CPP8988');
Do not place IBM confidential, company confidential, or personal information into any field.