Skip to Main Content
IBM Z Software


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).


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.

Status Not under consideration
Categories Toolkit
Created by Guest
Created on May 27, 2015

ASMLANGX needs better support for LOUD WTO message redirection

There is a need to be able to capture an redirect the WTO output that is issued in response to the use of the LOUD parameter during ASMLANGX execution. The use of the _BPXK_JOBLOG environmental variable does not work in this case since redirection does not work for WTP (programmer informational) messages like the following:

+ASMXMA001I ASMLANGX V1.R6.00 (generated 2008-03-17 21:35)
+ASMXMA002I Output file: FOOBAR ASMLANGX A1
+ASMXMA016I Input file: FOOBAR SYSADATA *
+ASMXMA003I ... scanning HLASM SYSADATA file
+ASMXMA010I SYSADATA records scanned: 16
+ASMXMA006I Post-processing begins
+ASMXMA014I Records written to output file: 12
+ASMXMA011I ...Symbols in external search list...... 1
+ASMXMA013I ...Total symbols: 1
+ASMXMA015I Operation completed for this compile unit
+ASMXMA017I Operation completed for this extract file

The _BPXK_JOBLOG environmental variable usage documentation states "Messages that would normally go to the JESYSMSG data set are captured, but messages that go to JESMSGLG are not captured."

In our case we're executing ASMLANGX from a REXX exec in a UNIX shell environment and we're doing this from a software product build cycle where we need to capture and convert the SYSADATA data through the use of the ASMLANGX program with the details of the ASMLANGX execution being piped back to a UNIX (Red Hat) "build bubble" host. There are hundreds and sometimes thousands of assemblies involved in the product(s) build cycle. We do NOT wish to see the WTOs from these ASMLANGX LOUD executions and would like to capture the WTOs related to a particular ASMLANGX execution along with the return code from that execution.

We suggest a couple options; 1) If a SYSPRINT sysout file is present then instead of issuing a WTO ROUTECDE=11 for the above messages write the text of the message to the supplied SYSPRINT DDname which can be redirected easily under the z/OS UNIX shells without the use of the _BPXK_JOBLOG environmental variable, 2) provide for a new parameter in the ASMLANGX parameter string which directs the program to write LOUD messages to that particular DDname.

Idea priority Medium
  • Guest
    Reply
    |
    Nov 16, 2021

    We have been reviewing our RFE backlog and we do not think this one will be implemented in the next two years or so due to low vote count and internal priority. As a result, we will be declining this RFE, although this item remains on our long-term list of suggested enhancements.

    We understand the requirement but at present it seems a rather unusual case, and more a limitation of the chosen execution environment than a problem in ASMLANGX itself. If ASMLANGX is run in a TSO environment, the output is written using PUTLINE rather than WTO which means it can already be trapped.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Enterprise Tooling
    Product - High Level Assembler (HLASM)

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - High Level Assembler (HLASM)

  • Guest
    Reply
    |
    Jun 6, 2015

    I agree that we should be able to either redirect or duplicate the console messages.
    We will add this requrement to the list of uncommited candidates.
    Sharuff
    Sharuff Morsa IBM Hursley Labs