Well ... I did things in an 'unconventional' way - e.g. if any command
began with "%" it meant "invoke as Clist or REXX and with parms if any".
In my panel I had:
<etc.>
)PROC
<etc.>
&CLIST = TRUNC(&ZCMD,1) /* <--- here */
&ZCMD = TRUNC(&ZCMD,' ')
&ZTRAIL = .TRAIL
IF (&CLIST='%') /* <--- here */
&CLIST = &ZCMD
&ZCMD = 'CLIST' /* <--- here */
&ZCMDTEMP = TRANS( &ZCMD
<etc.>
*,*) /* <--- here */
&ZSEL = TRANS( &ZCMDTEMP
<etc.>
CLIST,'CMD(&CLIST &ZTRAIL) NEWAPPL(&ZAPPLID) PASSLIB'
/* <--- here */
<etc.>
*,'' )
)END
In my Clist I then had:
<etc.>
ISPEXEC SELECT &ZSEL
<etc.>
My Clist and REXX executed under ISPF and needed an ADDRESS TSO (or
TSOEXEC) for LISTA, SUBMIT, VERIFY, DELETE etc. (I started them from the
TSO READY prompt to bypass the ISPF primary menu panel.)
Apples & oranges indeed.
Paul Gilmartin wrote:
On Sun, 30 Mar 2014 13:30:23 -0400, Ted MacNEIL wrote:
What I'm saying is you don't need TSOEXEC for LISTA.
But, you do for TRANSMIT.
(Actually only under ISPF)
This is so wretchedly complicated! I see:
http://pic.dhe.ibm.com/infocenter/zos/v1r12/topic/com.ibm.zos.r12.ikjc500/tsoexeccom.htm
TSOEXEC command
z/OS V1R12.0 TSO/E Command Reference
SA22-7782-13
Use the TSOEXEC command to invoke an authorized command from an unauthorized
environment. ...
Is ISPF the *only* unauthorized environment? But I'm sure I've done:
"call *(IEBCOPY)" /* Back when IEBCOPY needed authorization. */
And I didn't need either:
"TSOEXEC call *(IEBCOPY)" /* or */"
" call TSOEXEC *(IEBCOPY)" /* (wouldn't make sense, anyway.) */
Is this because the rule for load modules (IEBCOPY) is different from
commands (TRANSMIT)?
And I thought that 'RECEIVE' failed for me in an EXEC invoked from the
READY prompt, and a mentor told me to use 'TSOEXEC RECEIVE', and
that made it work. I may need to test again. It may have got conflated
in my recollection with'PROFILE PROMPT'.
And, you don't need the address TSO if you invoked it in a TSO environment.
But, that's a digression.
But here, I'm on more comfortable ground. I believe the initial command
environment for an EXEC invoked in an ISPF evironment, or even as an
EDIT macro is still TSO (although ISPEXEC or ISREDIT would seem to me
to make more sense -- cf. XEDIT macros). So you shouldn't need
"address TSO" in either of those cases. In an EXEC invoked with IRXJCL,
"address TSO" simply doesn't work. In an EXEC invoked from shell,
there is lately an "address TSO", but it's very different from the usual
"address TSO" in that it forks a separate address space to run the
command; your ALLOCATEs are likely not to work there.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
