Updating user exits on VMSECURE's 191 disk

Products

• VM:Secure for z/VM

Issue/Introduction

How to reload user exits.

Environment

z/VM, VM:Secure 3.2

Resolution

If you can actually logon to VMSECURE you can SENDFILE the changed file from your ID to VMSECURE, then use the VMSECURE CMS command to do the other work while logged on and VMSECURE still running:

CMS COPY current file A current Ofile A               - make a copy of what is there but don't disturb the current copy

CMS EXEC RECEIVE spoolid  = = A (REPLACE OLDD     -  I just always use olddate so things will match from their original copy

.... and then the EXECDROP and EXECLOAD like you indicated, but the user exits may not be execloaded unless they configured them to be.

 

If you can't logon to VMSECURE you can also do the same using the VMSECURE MODULE and the VMSECURE CMS command.  You must have authorization to use the CMS command.

 

Here is an example all done from my user (which has proper authorizations):

 

sendfile vmxexitl exec a vmsecure

File VMXEXITL EXEC A1 sent to VMSECURE at system on 08/19/24 12:11:55
Ready;
q rdr vmsecure all

ORIGINID FILE CLASS RECORDS  CPY HOLD DATE  TIME     NAME      TYPE       DIST
VMSECURE 0058 T CON 00001489 001 NONE 04/15 13:45:28                      SYSTEMS
VMSECURE 0393 T CON 00000026 001 NONE 07/23 12:53:32                      SYSTEMS
VMSECURE 0391 T CON 00000784 001 NONE 07/23 12:48:24                      SYSTEMS
VMSECURE 0215 T CON 00002438 001 NONE 06/08 11:35:40                      SYSTEMS
VMSECURE 0272 T CON 00001927 001 NONE 04/19 08:41:11                      SYSTEMS
VMSECURE 0265 T CON 00004878 001 NONE 04/16 20:22:51                      SYSTEMS
VMSECURE 0285 T CON 00000460 001 NONE 05/13 20:23:55                      SYSTEMS
myuser   0405 A PUN 00000274 001 NONE 08/19 12:11:55 VMXEXITL  EXEC    SYSTEMS
Ready;

vmsecure cms copy vmxexitl exec a vmxexitl oexec a
Ready;
vmsecure cms exec receive 405 = = a (replace oldd
Ready; 

vmsecure cms execdrop vmxexitl exec

Ready(00028);
vmsecure cms execload vmxexitl exec
Ready;

 

Then, a little proof from VMSECURE (I logged on to VMSECURE and issued CMS EXEC FILELIST):

      VMXEXITL OEXEC    A1 V         72        436          6  8/19/24 12:13:03
      VMXEXITL EXEC     A1 V         72        436          6  8/19/24 12:11:32

 

 

See the VMSECURE CMS command:

VM:Secure CMS command