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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Rejecting this RFE as the customer has confirmed that they are able achieve the desired outcomie by separating the workload using the TRANSID attribute
Yes, retesting did work as pointed out by you and we are now able to separate workload using TRANSID attribute. Thanks again for your support. From my point of view this RFE could be closed.
Thanks a lot and with best regards, Reto
Reto, did your retesting verify that separating workloads using transaction ID satisfy your needs?
Our verifications using transaction ID (TRANSID) did not illustrate expected results. Re-testing with your hints showed we were using wrong transaction profile (DFHCICST instead of DFHCICSA).
Currently we are verifying if separating workloads using transaction ID is satisfying our needs.
The usual technique for separating workloads when using DPLs is to use the transaction ID (TRANSID) attribute of the dynamic PROGRAM resource itself. This field is used to specify the transaction ID that you wish to run the remote program under. CPSM can use this transaction ID to separate the request out from other requests. You would add this transaction ID to your CPSM WLM transaction group (TRANGRP), which would be added to your CPSM workload definition (WLMDEF).
Does that satisfy the requirement? If not can you help us to understand where your needs differ?