🚀 go-pugleaf

We have had a production job running since last june - it run a series
of REXX execs at 9pm every weeknight. At least one of the EXECs queues
commands to the program stack, from which they are executed as soon as
'exit' statement is reached. Last fall I upgraded to VMSCHED 4.2 without
any hassles or necessary changes.  Recently, due to a mixup on holday
scheduling, the scheduled run was canceled & purged, then rescheduled.
Now the run ( scheduled logoff=no, BTW ) fills the program stack as
usual, but does NOT empty it when the exec ends. ( A debug exec tacked
on the end shows all commands in the stack correct and ready )
if I pull from the stack then interpret, it works almost perfectly -
------
we have gotten around this particular problem by rewriting a previous
step to eliminate the need for queueing commands, BUT I'd like to
understand what happened before it bites again. IS it possible to
autolog/xautolog a job such that the program stack is ignored ???
*---------------------------------------------------------------------*
:  Michael R. Ramundo                        Fax (518) 442-3697       :
:  Systems Programmer / Analyst            Audio (518) 442-3709       :
:  Computing Services Center, CS-9C               Network             :
:  State University of N.Y. at Albany        SYSMRR @ ALBNYVM1        :
:  Albany,  New York    12222            SYSMRR @ uacsc2.albany.edu   :