Valid on z/OS and z/VM.
Use the CPFWAIT control option to set a default value for the TSS command WAIT keyword.
At least one of the CPF‑related control options must be entered at CA Top Secret startup to use the CPF. If not, CPF might not be activated until the next CA Top Secret startup and no CPF control options are accepted by CA Top Secret until that time.
If no CPF journal file has been specified and if WAIT(NO) is specified on the TSS command or if the CPFWAIT control option is set to NO, then there is no way to view the output generated as the result of that command.
The CPF recovery file is used if defined and when CPFWAIT(NO) or WAIT(NO) is specified.
All entry methods are accepted.
This control option has the following format:
CPFWAIT(YES|NO)
(Default) Specifies a default value for the TSS command WAIT keyword.
Specifies that no waiting will occur for messages.
The value entered here can be overridden by the WAIT value on an individual TSS command.
This example indicates that when a TSS command is routed to a remote node, the issuer of the command will not wait for a response from that remote node before continuing:
CPFWAIT(NO)
Valid on z/VM.
Use the CUSTKEY control option during product installation to define an encryption key and set up encryption for your security file. When you run the TSSINST utility during installation, you specify the control option to define the key. The utility then places the defined key in your parameter file. During startup, the product reads the parameter file and un-encrypts the key.
Note: This key definition task is mandatory. The original key in the parameter file will not work. You will also need your defined key for other utilities (for example, when using TSSFAR to review security file permissions or using TSSXTEND).
This control option has the following format:
CUSTKEY encryption_key
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|