Use of SELECT PGM vs. CMD
Bonhard Robert , sys3rcb
enough hit, so here goes . . .
We're currently moving our products out of our logon procs to instead use
LIBDEF and ALTLIB. I am basically familiar with these functions as I have
used them over the years. The first product we removed uses "ISPEXEC SELECT
PGM(XXX)' for the program call, which yielded the S806 as documented (OS/390
210 ISPF Services Guide) . Using the 'ISPEXEC SELECT CMD(XXX)' method works
like a charm, also as documented. Before I role this forward, I wanted to
find out if there were any known problems or issues using the CMD() call
instead of the PGM() call.
Thanks!
Bob Bonhard/UPS/MVS Systems/201-828-3936/RBon...@UPS.com
Binyamin Dissen
<sys...@UPS.COM> wrote:
:>I ran a query against the archives on this topic and could not find a close
As it is running in its own task any storage will be automatically freed at
termination. This might be an issued if the SELECTed program expects
otherwise. On the other hand, if it doesn't properly clean up it will now.
--
Binyamin Dissen <bdi...@dissensoftware.com>
http://www.dissensoftware.com
Director, Dissen Software, Bar & Grill - Israel
Edwin Handschuh
I think you're confusing church and state. The CMD() and PGM() statements are
not the same. CMD() activates a CLIST or REXX form SYSPROC or SYSEXEC while
PGM() activates ISPLLIB, STEPLIB, or LNKLST'd programs. But to answer your
question directly, I'm not aware of any bugs with either approach. Both seem
to work as designed/documented.
Edwin Handschuh
Enterprise Systems Architect
Independent Consultant
SoftExcell, Inc.
(215) 783-2208 - cell
(888) 445-0659 - pager
e...@softexcell.com
I ran a query against the archives on this topic and could not find a close
enough hit, so here goes . . .
We're currently moving our products out of our logon procs to instead use
LIBDEF and ALTLIB. I am basically familiar with these functions as I have
used them over the years. The first product we removed uses "ISPEXEC SELECT
PGM(XXX)' for the program call, which yielded the S806 as documented (OS/390
210 ISPF Services Guide) . Using the 'ISPEXEC SELECT CMD(XXX)' method works
like a charm, also as documented. Before I role this forward, I wanted to
find out if there were any known problems or issues using the CMD() call
instead of the PGM() call.
Thanks!
Bob Bonhard/UPS/MVS Systems/201-828-3936/RBon...@UPS.com
---------------------------------------------
This message was sent using Comcation MailMan.
http://www.comcation.net/
Robin Murray
or rexx by specifying a leading %.
Edwin
Handschuh To: ISP...@listserv.nd.edu
<eth@SOFTEXCEL cc:
L.COM> Subject: Use of SELECT PGM vs. CMD
Sent by: ISPF
discussion
list
<ISPF-L@listse
rv.nd.edu>
09/19/2002
11:37 AM
Please respond
to ISPF
discussion
list
Gabor Markon
its use for me...or is there any subparameter in SELECT CMD like the PARM()
of the SELECT PGM ?
Cheers
Gabor
Robin Murray
"ISPEXEC SELECT CMD(MYCMD PARM1 PARM2)"
"ISPEXEC SELECT PGM(MYPGM) PARM(PARM1 PARM2)"
Gabor Markon
<gabor.markon@HVBSY To: ISP...@listserv.nd.edu
STEMS.COM> cc:
Sent by: ISPF Subject: Re: Use of SELECT PGM vs. CMD
discussion list
<ISP...@listserv.nd
.edu>
20/09/02 03:29 AM
Please respond to
ISPF discussion
list
Yes you can use CMD to call a program but WITHOUT parameters - that limits
Ondrejko, David
>
> "ISPEXEC SELECT CMD(MYCMD PARM1 PARM2)"
>
> "ISPEXEC SELECT PGM(MYPGM) PARM(PARM1 PARM2)"
<newbie question>
What is difference between those two ways of invoking a command/program?
Other, of course, than the obvious syntactical differences, I mean.
References to user manuals are good responses too!
</newbie question>
-- Davyd
McKown, John
But there is a difference, IIRC. With the SELECT PGM, the PARM is passed as
in batch. With SELECT CMD, the PARM is passed as it would be in a TSO
command. So the program must be written differently to pick up the parms.
--
John McKown
Senior Technical Specialist
UICI Insurance Center
Applications & Solutions Team
+1.817.255.3225
> -----Original Message-----
> From: Robin Murray [mailto:Robin_...@MARITIMELIFE.CA]
> Sent: Friday, September 20, 2002 8:16 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: Use of SELECT PGM vs. CMD
>
>
ted.macneil
-teD
-----Original Message-----
From: "Ondrejko, David" <david.o...@SAFELITE.COM>
Date: Fri, 20 Sep 2002 09:19:36
To: ISP...@listserv.nd.edu
Subject: Re: Use of SELECT PGM vs. CMD
> you pass the parms to a cmd right in the cmd area:
>
> "ISPEXEC SELECT CMD(MYCMD PARM1 PARM2)"
>
> "ISPEXEC SELECT PGM(MYPGM) PARM(PARM1 PARM2)"
<newbie question>
What is difference between those two ways of invoking a command/program?
Other, of course, than the obvious syntactical differences, I mean.
References to user manuals are good responses too!
</newbie question>
-- Davyd
Card-carrying member of "Dino's R Us" since 1981.
When the going gets stupid, the stupid get annoying!
Robin Murray
"A command processor is a program invoked by the terminal monitor program
(TMP) when a user at a terminal enters a command name. The TMP is a
program that accepts and interprets commands, and causes the appropriate
command processor to be scheduled and executed. The TMP also communicates
with the terminal user, responds to abnormal terminations and processes
attention interruptions."
the PGM is an ispf dialog service program.
the biggest difference i see is that the cmd gets passed a CPPL parm, and
the dialog program gets passed:
"REG1 Points to the address of the parameter data (from the PARM
keyword) field (half-word length) followed by the data."
"Ondrejko, David"
<david.ondrejko@SAF To: ISP...@listserv.nd.edu
ELITE.COM> cc:
Sent by: ISPF Subject: Re: Use of SELECT PGM vs. CMD
discussion list
<ISP...@listserv.nd
.edu>
20/09/02 10:19 AM
Please respond to
ISPF discussion
list
> you pass the parms to a cmd right in the cmd area:
Robin Murray
mean to imply the two were interchangable.
"McKown, John"
<JMckown@UICII To: ISP...@listserv.nd.edu
NSCTR.COM> cc:
Sent by: ISPF Subject: Re: Use of SELECT PGM vs. CMD
discussion
list
<ISPF-L@listse
rv.nd.edu>
20/09/02 10:27
AM
Please respond
to ISPF
discussion
list
Robin,
But there is a difference, IIRC. With the SELECT PGM, the PARM is passed as
in batch. With SELECT CMD, the PARM is passed as it would be in a TSO
command. So the program must be written differently to pick up the parms.
--
John McKown
Senior Technical Specialist
UICI Insurance Center
Applications & Solutions Team
+1.817.255.3225
> -----Original Message-----
> From: Robin Murray [mailto:Robin_...@MARITIMELIFE.CA]
> Sent: Friday, September 20, 2002 8:16 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: Use of SELECT PGM vs. CMD
>
>
Mark Zelden
http://listserv.nd.edu/cgi-bin/wa?A2=ind9908&L=ispf-l&P=R9358
Mark
--
+-------------------------------------------------------------------+
| Mark Zelden - z/OS and OS/390 Systems Engineer |
| mailto: mark....@zurichna.com |
| Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html |
+-------------------------------------------------------------------+
Edwin Handschuh
Not quite true...
You can pass parms using the CMD to call a program provided you place the parms
into the CMD(). Once the CLIST is invoked it can pass the parms to another
CLIST and/or the program via the PARMS() statement. For example:
1. Lets say you create a panel called PANEL1.
2. PANEL1 collects 3 pieces of user data called &P1 &P2 &P3.
3. PANEL1 invokes a CLIST named CLIST1.
4. CLIST1 passes &P1 &P2 and &P3 to CLIST2.
5. CLIST2 calls PROG1 and passes &P1 &P2 and &P3.
Here's how it's done:
------------------------------------------------------
PANEL1:
)BODY
...
Input PARM1+===>_P1
PARM2+===>_P2
PARM3+===>_P3
...
)INIT
)PROC
...
T,'CMD(CLIST1 &P1 &P2 &P3)'
------------------------------------------------------
CLIST1:
PROC 3 &PARM1 &PARM2 &PARM3
ISPEXEC SELECT CMD(CLIST2 &PARM1 &PARM2 &PARM3)
END
------------------------------------------------------
CLIST2:
PROC 3 &PARM1 &PARM2 &PARM3
ISPEXEC SELECT PGM(PROG1) PARMS(&PARM1 &PARM2 &PARM3)
------------------------------------------------------
HTH
Edwin Handschuh
Enterprise Systems Architect
Independent Consultant
SoftExcell, Inc.
(215) 783-2208 - cell
(888) 445-0659 - pager
e...@softexcell.com
Yes you can use CMD to call a program but WITHOUT parameters - that limits
its use for me...or is there any subparameter in SELECT CMD like the PARM()
of the SELECT PGM ?
Cheers
Gabor
Ondrejko, David
This sounds pretty interesting, actually. However, I don't know much about
creating panels. Is there any kind of tutorial or reference manual you
could suggest that would provide some basic background so that I might be
able to understand some of this?
</nq>
-- Davyd
> -----Original Message-----
> From: Edwin Handschuh [mailto:e...@SOFTEXCELL.COM]
> Sent: Friday, September 20, 2002 10:10 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: Use of SELECT PGM vs. CMD
>
>
Steve Comstock
david.o...@SAFELITE.COM writes:
> <nq>
> This sounds pretty interesting, actually. However, I don't know much about
> creating panels. Is there any kind of tutorial or reference manual you
> could suggest that would provide some basic background so that I might be
> able to understand some of this?
> </nq>
>
> -- Davyd
>
Ahem.
We offer an entertaining and effective five-day class, "Dialog Manager Using
TSO REXX and TSO CLIST", that covers panel definition and all aspects of
Dialog Manager. Check out http://www.trainersfriend.com/a310descrpt.htm for
detaiils.
Kind regards,
-Steve Comstock
The Traiiner's Friend, Inc.
800.993.8716
303.393.6716
http://www.trainersfriend.com