Converting the ALLOCATEs to BPXWDYN should work, unless you have other dependencies on a TSO environment.
Another way to do this is to convert the batch JCL that you use to run program NDVRC1 to TSO statements and run that under TSO in batch: 1. use EXEC PGM=IKJEFT01 & SYSTSPRT & SYSTSIN DD statements. 1. use TSO CALL instead of PGM= 2. you should be able to still use JCL for the required DD statements. Then you will have a TSO environment. Something like: //TSOBATCH EXEC PGM=IKJEFT01 ..... //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * CALL 'some.load.library(NDVRC1)' 'parms' // .... JCL for NDVRC1 here .... If NDVRC1 is in standard system search list, you can do CALL *(NDVRC1) instead. Bill On Wed, 11 Mar 2009 15:13:45 -0500, Paul Gilmartin <[email protected]> wrote: >On Wed, 11 Mar 2009 15:05:56 -0400, Lizette Koehler wrote: > >>I am trying to assist my Endevor support team with a TSO/REXX issue. >> >>They run in batch a program NDVRC1. This executes a REXX to interface with PRO/JCL to validate JCL standards. This works fine until you add TSO ALLOCATE commands for files in the process. >> >>We get an RC -3. Which I believe is due to TSO not being in the environment. If we run this same thing in foreground it works fine. So I believe my thought is correct. >> >>What I need to identify is how to run TSO in this batch process with Endevor and PRO/JCL. >> >>Has anyone done something like this that can point me in the right direction? >> >You can substitute BPXWDYN for most uses of ALLOCATE. > >-- gil > ---------------------------------------------------------------------- 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
