Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Created by Guest
Created on Mar 5, 2021

Need to modify jobcards related to the Db2 system

Our special challenge:

We are using the SCHENV parameter in the JCL to route the job to the right LPAR.

Currently we include a note in the jobcards and every user has to change the variable:

==MSG> DB2 Admin: EDIT generated JCL 
==MSG>
000001 //#‌#‌#‌#‌#‌#‌#‌ JOB (3WIR001,000,00,'DB2 ADMIN DB2'),
000002 // ' ',NOTIFY=&SYSUID,
000003 // MSGCLASS=R,PRTY=5,TIME=(0030),
000004 // CLASS=A,SCHENV=DB2X <== !!! SET TARGET DB2 !!!


In Db2 Admin it is possible to generate jobs for all remote reachable Db2 systems.

So the SCHENV=DB2x has to be set dynamically to the right variable.


Examples:

run DB2ADMIN on TSO with local DB2A

1)

generated JCL >> SCHENV=DB2A

>> this will be ok with the suggestion


2)

connect to DB2B (same node/sysplex)

generated JCL >> SCHENV=DB2B


3)

connect to DB2T (other node/sysplex T)

generated JCL >> additional XMIT to NODE T:

first jobcards should use SCHENV=DB2A (local Db2)

then following jobcards after XMIT NODE T should use SCHENV=DB2T


EDIT FIT0BNL.ISP11034.SPFTEMP1.CNTL Columns 00001 
Command ===> Scroll ===>
****** ********************************* Top of Data ****************************
==MSG>
==MSG> DB2 Admin: EDIT generated JCL
==MSG>
000001 //#‌#‌#‌#‌#‌#‌#‌ JOB (3WIR001,000,00,'DB2 ADMIN DB2'),
000002 // ' ',NOTIFY=&SYSUID,
000003 // MSGCLASS=R,PRTY=5,TIME=(0030),
000004 // CLASS=A,SCHENV=DB2X <== !!! SET TARGET DB2 !!!
000005 /*XMIT A DLM=$$
000006 //#‌#‌#‌#‌#‌#‌#‌Z JOB (3WIR001,000,00,'DB2 ADMIN DB2'),
000007 //* RESTART=STEPNAME, <== FOR RESTART REMOVE * AND ENTER STEP NAME
000008 // ' ',NOTIFY=&SYSUID,
000009 // MSGCLASS=R,PRTY=5,TIME=(0030),
000010 // CLASS=A,SCHENV=DB2X <== !!! SET TARGET DB2 !!!
000011 //*



Needed by Date Mar 7, 2021