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