Sorry, it stands for model/view/controller, and it is a widely used
design pattern for decoupling the logic of a program from the
presentation of its inputs and outputs. The basic idea is that you can
reuse the program that does the actual work in different scenarios,
because that program is not wedded to a particular presentation layer.
https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2012-05-25 12:16, Farley, Peter x23353 wrote:
I've never seen this term before now -- "MVC design pattern"??? What is that please?
I'm guessing it is not "MoVe Character" design pattern.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of
Gord Tomlin
Sent: Friday, May 25, 2012 12:12 PM
To: [email protected]
Subject: Re: IKJTSOEV& ISPF services question
Unfortunately, ISPF significantly predates the MVC design pattern.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2012-05-25 11:23, McKown, John wrote:
From my view point, it is because the user of my program simply does EXEC PGM=MYPGM
rather than PGM=IKJEFT01,PARM='%MYPGM' which runs a, in my case, REXX program called
MYPGM, which then does the TSO allocates for the ISPF datasets, followed by ISPSTART
CMD(%MYPGM2). Which is either a TSO command, or another REXX program which does a TSO
CALL to actually invoke the processing program. All that "overhead" just so
that my program can, for instance, use a DSINFO to __easily__ get a list of cataloged
datasets and their attributes.
Again, what I really would like is something like the ISPF services (non DISPLAY). But make them
available via a simple COBOL CALL verb without the need for the "complicated" JCL and
REXX layers. This would allow a COBOL program to easily allocate and "open" a PDS, get a
list of the members, and then read one or more of the members. All in a relatively simple, easy to
use, way. The same with z/OS UNIX files too. Or use DSINFO for some DASD management reports.
I guess it's just a recent "itch" of mine. Not possible as I would like to do it, so I'm
just stuck with the "clumsy" (IMO) way.
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
