PEF; VMXCMD1117E The VMXENCMD command is not a VM:Secure command.
Article ID: 139933
Updated On:
Products
Issue/Introduction
Trying to do password encryption, like I've done a dozen times before. PEF using PENCRYPT from VMANAGER, with 'GRANT PEF TO VMANAGER' in the AUTHORIZ CONFIG file.
My VMXRPI CONFIG says ENCRYPT REVERSE.
sm vmsecure version
21:12:18 CA VM:Secure (TM) Version 03.2 RSU-1801
I have SO01866 and SO03826 applied.
I have my new CP nuc genned with the encryption version of HCPRxx's, but have not IPLed it yet.
When I issue the PENCRYPT command from VMANAGER I get the expected warning screen, then immediately the
VMXCMD1117E The VMXENCMD command is not a CA VM:Secure command.
On the VMSECURE console I get:
21:19:13 VMANAGER 0024 VMXCMD1111I Beginning command: VMXENCMD REVERSE
21:19:13 VMANAGER 0024 VMXCMD1117E The VMXENCMD command is not a CA VM:Secure command.
VMANAGER 0024 VMXCMD1112I Ending command VMXENCMD with completion code 24.
But I can see the VMXENCMD VMSECURE macro on VMSECURE's 192 D disk, the RUNTIM disk.
Interestingly, when I try the VMSECURE RULEMAP USER VMANAGER, I get:
vmsecure rulemap user vmanager
VMXCMD1117E The RULEMAP command is not a CA VM:Secure command.
All the 'normal' more trivial commands have worked, CONFIG, EDIT, MANAGE, etc...
Environment
Release : 3.2 RSU-1801
Component : CA VM:Secure for z/VM
Installing on z/VM 7.1
Cause
Verify you have Rules installed on this system.
Rules must be installed before you can encrypt, requiring two separate IPLs.
Issue command VMSECURE QCPCFG
If it gives you VMXMSC1117E then Rules are not installed in CP, therefore, PENCRYPT won't work.
That would also explain why RULEMAP got the VMXCMD1117E .
You can also try issuing VMSECURE RULES USER VMANAGER
Rules not being installed is the other thing that can cause the VMXCMD1117E you 're getting.
Resolution
Rules not installed. Rules *must* be installed before you can encrypt, requiring two separate IPLs.
Additional Information
Feedback
