Re: command line vs exec

[Tom Huegel]

I have tried everything I can think of. LIB is a module that is loaded as a nucleus extension. The doc for LIB says it is a full XA mode program. I am on VM/ESA 2.3 I have tried with LIB below 16M and above 16M. I have tried EXEC1, EXEC2, REXX, and put it in a PIPE... Maybe for kicks I’ll write a little program that does nothing but pass parms to LIB and see what happens. I don’t see anything in the source code that would differentiate between a command coming from an exec or the command line. I’ll look a little deeper, maybe try dropping the author a note.     Thanks      From: Jim Bohnsack [mailto:[EMAIL PROTECTED] Sent: Thursday, October 13, 2005 1:07 PM To: VMESA-L@LISTSERV.UARK.EDU Subject: Re: command line vs exec   Tom--If LIB is an exec, I suggest that you enter 'EXEC LIB SERVEXEC SUBPROD EXEC PAUSEBG JCL'.  If LIB is a module, try: address command 'LIB SERVEXEC SUBPROD EXEC PAUSEBG JCL' Jim At 11:57 AM 10/13/2005, you wrote: I have this program (downloaded from the tools) that is a CMS library system.   I have the server side (IUREC) running fine and the client (LIB) works pretty good too.   When I type the following line on my CMS client it works fine.   LIB SERVEXEC SUBPROD EXEC PAUSEBG JCL   But when I include the same line in an exec the parameters – PAUSEBG JCL – don’t get passed to the server.   Has anyone run into something like this before? Is there something ‘different’ I can do in the EXEC?   This is a trace from my 1 line exec.   *-* LIB 'SERVEXEC SUBPROD EXEC PAUSEBG JCL'     >L>   "LIB"                                     >L>   "SERVEXEC SUBPROD EXEC PAUSEBG JCL"       >O>   "LIB SERVEXEC SUBPROD EXEC PAUSEBG JCL"       Thanks   Jim Bohnsack Cornell Univ. (607) 255-1760