Started CEMERTR - PMO - PMO230A - INVALID COMMAND PARAMETER/SYNTAX

Document ID : KB000111061
Last Modified Date : 14/08/2018
Show Technical Document Details
Question:
Started CEMERTR and PMO issues PMO230A - INVALID COMMAND PARAMETER/SYNTAX messages. How is this resolved? 
Environment:
z/OS 
PMO 4.4
Top Secret
Answer:
 If PMO abends or detects Top Secret has started after it (as described in the programmer guide) then the PMO task needs the security systems authority to start itself.
 
Specify TOPSECRT=YES in your parameter data set if you plan to reinitialize eTrust CA Top Secret while CA PMO is running. Before eTrust CA Top Secret reinitializes, it removes its old SVC 21 intercept. If CA PMO is active during the eTrust CA Top Secret initialization, CA PMO SVC 21 intercept is effectively removed. This may cause a system abend 215 or 0C4 in PMO/XSYS or in a user address space. When you specify TOPSECRT=YES, CA PMO automatically stops and restarts itself (installing its SVC 21 in the process) when you reinitialize eTrust CA Top Secret.
 
Notes:
1. CA PMO does not reuse the ECSA it needs when it is restarted. If ECSA usage at your site is critical, avoid unnecessary eTrust CA Top Secret reinitializations.
2. Some eTrust CA Top Secret functions, such as enabling PDS member level protection using the MODIFY TSS,PDSPROT(ON) command, displace the CA PMO SVC18 intercept as well as the SVC21 intercept.
Additional Information:
See CA PMO System Programmer Guide page 170
Compatibility with eTrust CA Top Secret