CONTROL DISPLAY SAVE/RESTORE POP-UP/FULL SCREEN

[FAISAL ZAHIR]

thanks a lot Marv. your suggestion worked perfectly. but instead of coding
an exec to edit a dataset, i coded it to execute any command that i pass,
using interpret, that way i can use it for all purposes.

thanks
faisal

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@listserv.nd.edu]On Behalf Of
Marvin Knight
Sent: Thursday, August 08, 2002 11:44 PM
To: ISP...@listserv.nd.edu
Subject: Re: CONTROL DISPLAY SAVE/RESTORE POP-UP/FULL SCREEN

Have you tried to invoke the edit service using a nested exec
and then use suspend to get rid of the popup

ispexec control display save
ispexec select cmd(%myedit &dsn) suspend
ispexec control display restore

the myedit clist/exec can be a simple exec that you pass the dsn to and
just invokes edit

/* REXX myedit */
PARSE ARG DSN
ADDRESS ISPEXEC
"EDIT DATASET('"DSN"') "
EXIT

Marv

[Robin Murray]

i've been playing with ispf for probably 15 years now, and i've always had
a great respect for the authors of it. there's rarely a problem you can't
find a solution for, and the product has been able to expand and take on
new functionality with ease, a sign of a good design foundation.

the only areas that i think could stand some improvement are the
workstation interface and table services. i've looked at w/s a few times,
and found it too cumbersome to bother with, and the table services,
although they get the job done, tend to be a bit finicky and limited in
functionality for my taste. if you're going to provide table services, why
not include some basic database functions and an sql interface?

does anyone else have ideas for improvement?

FAISAL ZAHIR
<faisal_zahir@TCS To: ISP...@listserv.nd.edu
CAL.CO.IN> cc:
Sent by: ISPF Subject: Re: CONTROL DISPLAY SAVE/RESTORE
discussion list POP-UP/FULL SCREEN
<ISPF-L@listserv.
nd.edu>

08/12/2002 01:16
AM
Please respond to
ISPF discussion
list

[Zemanek, Jerry]

An SQL interface/lookalike for table manipulation would be excellent. I
haven't worked with the WS component...so I can't comment much about it's
design or navigational capabilities. But, I too admire the developers of
ISPF/Dialog Mgr. If they could implement or provide those simple SCREEN
mapping functions (of ISPF/DM) through a BROWSER front-end/DB2 STP back-end
(or something like that) it would even be nicer. We need that simple data
mapper/presentation ability that ISPF/DM provides in the MF world in the
NETWORK/SERVER/BROWSER world. It would be nice to develop a BACK-END STP
which supplies a temporary table to the BROWSER for display...all
implemented with one simple statement TBDISPL. Have the HTML generated from
the stored PANEL definition. SELECT a row for processing and return it to
the STP. I don't know...maybe the WS component works somewhat this way and
I just don't know it. AppDevelopers are now spending lots of time working
with the PRESENTATION MANAGEMENT of a WEB transaction...let ISPF/DM or a
generic product do that stuff. Just tell it what you want through a
definition.

[Hobart Spitz]

Funny you should ask about ideas for improvement.

I whole heartedly agree with the comments about ISPF starting out with a
strong foundation. Credit is due both to the original developers and to
those who have followed.

I've found that handling of numbered datasets has some quirks that have been
around for a long time. The problem seems most problematic with edit
macros. It seems that positional finds do not work the same in edit macros
and from the command line. I've found that you have to turn numbers off to
get positional finds to work in VB, numbered datasets. Otherwise, it counts
the position after the number field as 1. "f xyz 1" doesn't search the
same columns from the command line and as from an edit macro.

Sensitivity to "/*" in host commands is a big mistake. It frequently causes
confusion here and in coding. From the command line "f //** 1" works fine.
From an edit macro, it fails. (Bounds at 4 and 71.) Working around this is
a big pain, and it is poorly documented. After 20+ years with ISPF, I just
found out about it this year. Give us an option, like the edit macro
command "scan off" to suppress this.

When doing a create/replace from numbered FB80 to VB, I should get the
option to move the number from 73-80 to 1-8. It takes about 6 steps
otherwise.

I would like to see all compilers, the panel compressor, the binder, etc.,
with help from ISPF update statistics in object, load, panel, DBRM, etc.
libraries. This would support a UNIX like "make".

Of course, a web browser interface would be nice. That should include
making existing dialogs work as web applications.

Just my buck-three-eighty. :)

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@listserv.nd.edu] On Behalf Of

Robin Murray
Sent: Monday, August 12, 2002 8:54 AM