Anybody who has any of the CA VM:Manager products also likely has a copy of the VRXUTIL program which CA uses to compile their EXECs. This can also quite nicely compile your EXECs too. I don't recall to what extent it is documented/supported. Syntax is VRXUTIL COMPILE filename filetype filemode outname outtype outmode. Options include LIST, XREF and REPLACE.
Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Neale Ferguson Sent: October 15, 2010 13:04 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: REXX that verify what MINIDISK is a file Years ago we used the alternative EXEC processor support to encrypt our execs and make these the ones the users executed. On 10/15/10 12:51 PM, "gclo...@br.ibm.com" <gclo...@br.ibm.com> wrote: Hi, A lot of years ago (VSE age), I saw a similar problem: how to protect an exec that puts controlled programs in production. That time, my solution was a simple ASSEMBLER program (public) that links another mdisk (SUPPORT 11F if I remember correctly), and calling the correct EXEC who did all the checks and finish detaching the mdisk. The only problem was to recompile the program all the times when the mdisk password was changed. I will search for this program source into my backups... If found, I put the program in this list... The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
