Skip to Main Content
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.

Status Future consideration
Workspace z/OS
Categories ISPF
Created by Guest
Created on Feb 2, 2021

ISPF gives error ISP190A whenever a VER NONBLANK test is used on a non-panel field

The ISPF panel verify statement (VER) displays a message when a variable doesn't meet the verification criteria. It also automatically places the cursor to the last panel field referred to in any panel statement. This is likely the same field as the VER is checking, but if the VER field isn't on the panel then it would be some field referenced by a previous statement.

My enhancement suggestion is to add a new optional keyword parameter to VER, to explicitly indicate which field to set the cursor to when VER displays a message. For example, the VER could be coded as:

VER (invar,NB,NUM,CSR=chknum)

to set the cursor to field chknum if the invar field is blank or is not numeric. (An alternative idea is CUSOR=)

There are two benefits to allowing VER to explicitly set the cursor position:

1. It would allow the dialog developer to easily test one panel field but put the cursor on a different field.

2. In the case of a VER on a non-panel field, since the default is to place the cursor on the last referenced panel field, the result may not be as desired. Allowing the VER to explicitly specify the desired panel field would make it clear what should happen, without dependence on side effects of previous statements.

The TRANS function also can set a MSG, with the same logic for defaulting the cursor position. If VER is enhanced to add an optional CSR parameter, it may make sense to add the same optional CSR parameter to the TRANS function, with the same meaning: if CSR is specified, then if TRANS sets a MSG it should place the cursor at the specified field.

Idea priority Medium
  • Guest
    Reply
    |
    May 14, 2021

    Comment from the actual user who drafted this RFE...

    If the proprosed CSR/CURSOR parameter is used with a VER, then in that case, a VER NB on a non-panel field should *not* replace the standard NB message with ISPP190A.

    That is, the point of ISPP190A is that the NB error is due to a field not entered at the cursor position, but the panel is questioning whether the default cursor position would really be what the developer wants. If the developer has specifically indicated the desired cursor field then there is no ambiguity.