Re: Problems With Modified VMSECURE Exit

Article View: bit.listserv.l-vmctr

Article #643

Back to bit.listserv.l-vmctr Previous Next

#643

From: Robert Chambers
Date: Wed, 20 Jan 1993 13:54

10 lines
981 bytes

You might check to make sure you are passing the return code back to
the calling module correctly.  I know VMBACKUP's user exits like their
retcodes a certain way (not normal) - The new release of VMB did away
with the restriction.  You could always put a trace in the exec and
see where the '4' comes from.  Hopefully you would only need one or two
invocations to see where the problem lies.

Good luck

Robert

Technical Details

Message-ID: <93020.085408RMCCU@CUNYVM.BITNET>

Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!uwm.edu!psuvax1!psuvm!cunyvm!rmccu

References: <L-VMCTR%93011923182737@VM1.CC.UAKRON.EDU>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe320,e12e8b4cc8746369
X-Google-Attributes: gidfe320,public
X-Google-ArrivalTime: 1993-01-20 07:01:25 PST
Path: arc1-ca.pugleaf.net!sparky!uunet!spool.mu.edu!uwm.edu!psuvax1!psuvm!cunyvm!rmccu
Organization: CUNY/UCC VM Systems
Date: Wednesday, 20 Jan 1993 08:54:08 EST
From: Robert Chambers <RMCCU@CUNYVM.BITNET>
Message-ID: <93020.085408RMCCU@CUNYVM.BITNET>
Newsgroups: bit.listserv.l-vmctr
Subject: Re: Problems With Modified VMSECURE Exit
References:  <L-VMCTR%93011923182737@VM1.CC.UAKRON.EDU>
Lines: 10

Reply to Parent Message