Robert Mills asks:

> My question:
> 
> Is there any way of returning a job back to it's original
> capabilities after GODXL has been run?
>  
> 
> regards,

More seriously however, presuming GODXL sets the same bit that VESoft's
version does.  One can presume running VESoft's MORTAL resets the same
bit.

I don't really know if it does but I'm guessing.  I'm basing my
statement on they way I learned how the GOD program works many years
ago.  It may have changed.

Tracy Johnson
Measurement Specialties, Inc. 

BT







NNNN


> -----Original Message-----
> From: HP-3000 Systems Discussion 
> [mailto:[log in to unmask]] On Behalf Of Robert Mills
> Sent: Tuesday, March 21, 2006 10:24 AM
> To: [log in to unmask]
> Subject: [HP3000-L] Removing capabilities given by GODXL
> 
> 
> Greetings to the -L,
> 
> Background information:
> 
> Some of the jobs on our main e3000 require temporary SM 
> capability to perform some cross-account functions. We have 
> MPEX and therefore surround the commands that require this 
> ability with the GOD.PUB.VESOFT and MORTAL.PUB.VESOFT 
> commands. Before anybody raises the security implications of 
> this (Art?), GOD.PUB.VESOFT has a lockword and ACD's 
> associated with it.
> 
> To enable these jobs to run on our other e3000, which does 
> not have MPEX, we plan on using the GODXL contributed 
> program. GODXL will also have a lockword and ACD's associated with it.
> 
> My question:
> 
> Is there any way of returning a job back to it's original 
> capabilities after GODXL has been run?
>  
> 
> regards, 
>   
> Robert W.Mills 
> MIS Systems Development Manager 
> Windsong Services 
> +44 (0)20 8309 3604
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *