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.
OK, to be fair, it can be achieved with something like the following...
EXTRN EXTMOD01
LLILF 15,EXTMOD01
But NOT as a V-type constant directly, your point is well taken. My apologies for the confusion, I think this is acceptable.
Yes, I know. But all you need is an entry in the ESD as for any EXTERN of A(SUBRTN) or V(EXTMOD01). The Binder should then do the appropriate address relocation.
As I said I can artificially cause that, e.g.
LLILF 15,0
ORG *-4
DC V(EXTMOD01)
A machine instruction operand is an expression, not a DC-like term, so V-type addresses cannot be supported in this context.
- Jonathan Scott, HLASM