IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 z/OS
Categories z/OSMF
Created by Guest
Created on Oct 5, 2020

RELATED IDEAS

Please add NJE routing to z/OSMF Job Submission

I am opening this on behalf of a customer (see business justification). The customer runs 5-10 z/OS instances in a sysplex but they run as many as 4 JES2 MAS's within a single sysplex. In order for z/OSMF to route jobs to a system today it uses SYSTEM= on the job card. This can only be done if the target system is in the same MAS. Alternatively z/OSMF can use REST API's remotely to talk to a remote z/OSMF in another sysplex. The problem here is the customer has one sysplex with 4 MAS's which means that they have to deploy 4 z/OSMF servers within their sysplex. Things like CPM and WLM are sysplex wide in that scenario... but Jobs are MAS wide. Knowing which instance of z/OSMF to use for which function is confusing just to start with.

The requirement asks for z/OSMF to use ROUTE XEQ to route jobs to execute on another NJE node. This would only require 1) z/OSMF to capture the NJE Node names in the system table 2) add the Route XEQ nodename as an additional JCL statement after the job card for that job.

This would give them the ability to send the jobs where ever they need to go without requiring a z/OSMF server on each system.

Idea priority High
  • Guest
    Reply
    |     Aug 10, 2021

    Hi IBM
    We would require ZOSMF to support NJE to route jobs to other lpars (which is not part of the current ZOSMF) to perform certain specific activity within the ZOSMF workflow. (eg. we require to update our global inventory which is stored on a different lpar when a CICS region is created/deleted through ZOSMF workflow)

  • Guest
    Reply
    |     Oct 13, 2020

    Hi,
    even we are still a JES3-site I voted for this feature for 2 reasons:
    First, we plan to migrate to Jes2 by the end of 2022 and we Need support for NJE to submit in other sysplexes (we still believe in focal Point structures).
    But the important Thing is, we don't allow the parm SYSTEM= oder SYSAFF or anything similar, because this undermine the concept of scheduling environments.

    Kind regards,
    Björn

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.