This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
Current design of the clp is that a backend process(db2bp) gets created in a new shell which serves to the front end process(db2) that fires the db2 commands in the new shell. These clp processes in the new shell are completely different from the clp processes in parent shell. Hence it can't inherit the connection from parent shell to the new shell.
Request you to use one of the below options which you may already know
1) Execute the script in the current shell itself(using . operator) as shown below instead of using a new shell
. ./test.sh
2) Use new shell to execute the script like below, but establish a connection in the shell script and then call the sql file.
./test.sh dbname userid passwd
Content of test.sh could be
db2 connect to SAMPLE user $1 using $2
db2 -vf test.sql
Content of test.sql could be
select * from mytab1