Re: command line vs exec

[Jim Bohnsack]

If you have not tried the 'ADDRESS COMMAND' that I suggested earlier, your problem may be that there is a LIB EXEC somewhere on the system.  Unless you have 'IMPEX' (implied execution) OFF, an EXEC is executed ahead of a MODULE.  Address command would force the use of a module.  Is there a chance that there is more than one LIB on the system somewhere?  Are you sure that the LIB that is loaded as a nucleus extension is the one you want?  You could do a NUCXDROP LIB and make sure that the LIB MODULE you want is on your A-disk.

Jim

At 01:31 PM 10/13/2005, you wrote:

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

Jim Bohnsack
Cornell Univ.
(607) 255-1760