On Wed, 22 Nov 2006 11:09:09 -0600, Brian Peterson <[EMAIL PROTECTED]> wrote:
>
> I would suggest reporting this problem against the TSO/E CALL command under
> component 566528502. The CALL command is acting differently than PGM= in
> JCL.
>
Thanks. I guess the best argument I can make in support comes from:
1.10.4 "z/OS V1R7.0 TSO/E Command Reference"
__________________________________________________________________________________
1.10.4 CALL Command Return Codes
Table 8. CALL Command Return Codes
0 Processing successful.
12 Processing unsuccessful. An error message has been issued.
Other Return code is from the called program.
Clearly SMP/E succeeded (at least it thinks it did), and the return code is not
that from the called program.
And:
1.10.3 CALL Command Operands
The program to be executed must receive parameters according to the
standard
linkage conventions. These are the same conventions that would apply
if the
program was executed by batch job control language (JCL) and a
parameter string
was passed by the EXEC statement with the PARM keyword.
...
... the CALL command, whose primary
purpose is to
support the execution of programs written for a batch processing
environment
...
Which strongly suggests that it's the purpose CALL to behave like JCL EXEC.
BTW, Here I'll display my extreme TSO naivete. To get Rexx out of the picture,
I simply put
CALL *(GIMSMP) 'PROCESS=WAIT'
in my SYSTSIN. It appears to fail similarly. But now how do I display the
return code from the call in my SYSTSIN? What's the equivalent of Rexx "say RC"
or of POSIX shell "echo $?"?
Thanks again,
gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
