I have a perplexing (for me anyway) problem in the DB2I panels in ISPF. The command line within the DB2I section of our ISPF environment is coming up at the bottom of the screen. I would like up at the top where it makes sense.
The "Command line at bottom" setting in the ISPF 0 panel is deselected (no '/'). The command line for the regular ISPF editor comes up at the top as desired.
BUT, in DB2I (SPUFI Edit for example) the command line comes up at the bottom. I know there must be a way to affect this setting somewhere, but I just can't seem to find it. Google has been no help at all, even on this site.
Anybody happen to know where to fix this - It's driving me to distraction...
Joined: 01 Sep 2006 Posts: 2594 Location: Silicon Valley
not sure if this helps, from ISPF Dialog Developer's Guide and Reference:
Quote:
Requirements for specifying message and command line placement
The placement of the command line and long message field at the bottom of a
logical screen is a user-definable option. Placement is controlled by the system
variable ZPLACE. You can select or deselect Command line at bottom on the ISPF
Settings panel, and the setting changes the value of ZPLACE. ZPLACE can also be
changed in a dialog.
The value of ZPLACE is stored in the application profile pool. To change the value,
use the VPUT statement in a panel definition, the VPUT service in a dialog
function, or the ISPF Settings panel options. None of these settings takes priority
over the others. For example, an ISPF Settings panel selection can change what a
dialog set, and vice versa.
If the panel specifies ASIS on the )BODY statement for a panel, the command and
message lines are not repositioned, even if you specify placement at the BOTTOM.
The command line moves only if all of these are true:
v For primary windows:
1. If the WINDOW(w,d) keyword is specified on the header statement where w
is less than the screen width, then:
a. The keyword ASIS must not be specified on the )BODY header statement.
b. The first character of the command line must be an attribute character.
2. If the WINDOW(w,d) keyword is specified on the header statement where w
is equal to the screen width or the WINDOW keyword is not specified, then:
a. The keyword ASIS must not be specified on the )BODY header statement.
b. The first and last character of the command line must be an attribute
character, and one of these is true:
1) There is an attribute byte in the first column of the line following the
command line.
2) There is an attribute byte in the last column of the line preceding the
command line.
3. For pop-up windows, the keyword ASIS is not specified on the )BODY
header statement.
Command lines that move in panels designed for primary windows will continue
to move if these panels are displayed in pop-up windows. In addition, command
lines in panels created using the DTL and converted using the ISPF conversion
utility will move in both primary and pop-up windows.
And here is the definition for the ASIS parameter of the )BODY statement:
Quote:
Specifies that the command and long message fields are to appear on the
display as specified in the panel definition. When ASIS is specified, any user
request, using SETTINGS option 0 or by setting system variable ZPLACE, to
reposition the command and long message fields is ignored.
So it seems the developer of panel for DB2I forces you to use his preferences. One solution is to create an SMP/E USERMOD and remove the ASIS parameter. With an USERMOD, if there is any service applied to the panel, you have to re-do your mod.
Joined: 06 Jul 2010 Posts: 765 Location: Whitby, ON, Canada
DB2I likely runs under its own ISPF APPLID. Try entering the SETTINGS command when the DB2I menu is being displayed. The group of settings that you see is probably overriding what you set up via option 0 on the main ISPF menu.
