IBM Power Ideas Portal
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 updates on 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
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.
This could be displayed using Navbigatort for i. That would use te authentication used by Navigator.
IBM does not intend to provide a solution to this request at this time, so it is being closed.
The command to be run is not maintained as part of the job information. The SBMJOB command sends a request message to the job message queue, never storing the command string. In order for the JOB_INFO table function to return this information, it would need to access the job message queue in some way, similar to the query described in one of the comments to this RFE. It would slow down all JOB_INFO queries. In addition, there are security requirements related to showing commands from other user jobs that need to be considered.
IBM recommends defining a view that combines JOB_INFO and JOBLOG_INFO to hide the complexity from the user. If specific parameters need to be passed to the table function invocation, use global variables to set them prior to querying the view.
The CAAC has reviewed this requirement and recommends that IBM view this as a “nice to have” low priority feature. There are work-arounds, such as the one provided in an earlier comment below.
Background: The COMMON Americas Advisory Council (CAAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CAAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CAAC, see www.common.org/caac
Nancy Uthke-Schmucki - CAAC Program Manager
This is a great idea. In the mean time, you can do the following LATERAL join with JOB_INFO and JOBLOG_INFO to get the results you need. Note you may need to increase the length of the CAST for the CMDRQS field if you commands exceed 255 characters. Just change the VARCHAR(255) to a larger length.
-Bob
SELECT JQ.*,JL.CMDRQS
FROM TABLE (
qsys2.job_info(job_STATUS_FILTER => '*JOBQ')
) JQ
LEFT OUTER JOIN LATERAL (
SELECT CAST(message_text AS VARCHAR(255)) AS CMDRQS,
JQ.job_name AS JOBNAME
FROM TABLE (
qsys2.joblog_info(JQ.JOB_NAME)
) jl
WHERE MESSAGE_TYPE IS NOT DISTINCT FROM 'REQUEST'
ORDER BY ordinal_position DESC
LIMIT 1
) JL
ON jq.job_name = JL.jobname