IBM High Level Assembler for z/OS and z/VM

Showing 40

Improve ability to define structures with power-of-2 size

When writing assembler code, it is often desirable or even necessary to define a structure with a length that is an integral power of 2. Reasons for such might be to avoid crossing a cache-line boundary; to be able to allocate an array of structur...

almost 8 years ago in IBM High Level Assembler for z/OS and z/VM / Assembler 1 Not under consideration

2 VOTE

Provide SPM ITERATE-like analogue with conditions, similar to LEAVE/DOEXIT

An analogous macro to ITERATE with conditions, similar to DOEXIT & ASMLEAVE, would be very helpful to write more understandable code and take advantage of internal z Systems pipelining, instruction prefetch, and branch prediction. (Note: I hav...

almost 8 years ago in IBM High Level Assembler for z/OS and z/VM / Toolkit 2 Not under consideration

14 VOTE

Structured Programming Macros: support parenthetical grouping of logical conditions via parentheses

Support for parenthetical grouping of logical conditions is currently only possible by using the ANDIF and ORIF operators. This is because the Structured Programming Macros do not support the use of parentheses to specify logical hierarchy of cond...

about 8 years ago in IBM High Level Assembler for z/OS and z/VM / Toolkit 1 Not under consideration

16 VOTE

True length of DSECT

There should be a method (perhaps a new parameter) that would cause the "length" attribute of a DSECT to return the actual size of the dummy section, rather than simply returning a value of 1.

about 8 years ago in IBM High Level Assembler for z/OS and z/VM / Assembler 3 Not under consideration

4 VOTE

Allow fields >= 64k

The assembler currently only supports the definition of fields less than 64k bytes in length. The assembler should be revised to support the definition of fields greater than or equal to 64k bytes in length.

over 8 years ago in IBM High Level Assembler for z/OS and z/VM / Assembler 1 Not under consideration

5 VOTE

Option to check instruction-to-field mismatches

Looking for an option which when specified would have HLASM report instances where the instruction mismatched the data that it would operate on. Like "check that I am using instructions that match the data length of the field".

over 8 years ago in IBM High Level Assembler for z/OS and z/VM / Assembler 1 Not under consideration

3 VOTE

ISRSUPC Support Of Datasets Created With Large Block Interface

Request for ISRSUPC (batch program for SUPERC compare) to support datasets created with Large Block Interface.

almost 9 years ago in IBM High Level Assembler for z/OS and z/VM / Assembler 4 Not under consideration

10 VOTE

Additional SuperC returncode for changed data compare

Batch invocation of SuperC (ISRSUPC) currently gives two "normal" completion return codes, 0 for "No differences" and "1" for "Differences found". A third "normal" completion return code of 2 would be advantageous for those cases where there are n...

almost 9 years ago in IBM High Level Assembler for z/OS and z/VM / Other 4 Not under consideration

1 VOTE

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

almost 9 years ago in IBM High Level Assembler for z/OS and z/VM / Toolkit 3 Not under consideration

12 VOTE

Allow wildcards in SuperC batch member selection

Using SuperC Search-For from the ISPF panels allows members to be selected using '*' and '%' wildcards, i.e. like '*SP3%' as a membername. It would be very useful if the same format could be used in SELECT statements in the JCL SYSIN dataset

about 9 years ago in IBM High Level Assembler for z/OS and z/VM / Other 4 Future consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use