APAR status
Closed as documentation error.
Error description
INFO APAR to document IBM z System Automation V4R3 non-defect problems and documentation changes 5698SA300 VERSION 4 RELEASE 4 R430 DOC ZSA +------ System Automation for z/OS Version 4 Release 3 --------+ | | |PROGRAM NUMBER: 5698-SA4 | | | |TITLE: IBM Z System Automation Configuring | | | |CHAPTER Traditional SA z/OS Configuration | | | |TOPIC Step 29B(I): Configurations for the | | OPT_EMBEDDED_WEBSERVER Option | | | |SUBTOPIC Configure the properties for using RACF or ICSF | | key rings (OA62518) | | | |CHANGE: | | New subtopic name will be: | | Configure the properties for using RACF or ICSF | | key rings (OA65704) | | | | To use a RACF or ICSF key ring, complete the following | | configurations: | | 1. Navigate to the ing.operations.environment configuration | | file. Ensure that the ENABLE_KEYRING_SUPPORT property is set| | to true and use appropriate IBM_CRYPTO_PROVIDER value. | | Starting from OA62518, RACF key ring is enabled by default. | | For RACF key ring, | | use IBM_CRYPTO_PROVIDER="com.ibm.crypto.zsecurity.provider"| | For ICSF key ring, | | use IBM_CRYPTO_PROVIDER="com.ibm.crypto.hdwrCCA.provider" | | | | 2. Navigate to the ing.operations.security.properties | | configuration file, set the keystore, truststore, or both | | properties to the following values: | | | | Table 1. Properties for using RACF or ICSF key rings | | | | ing.security.tls.keystore = | | safkeyring://<USERID>/<KEYRING_NAME> | | (two forward-slashes instead of four)| | ing.security.tls.truststore = | | safkeyring://<USERID>/<KEYRING_NAME> | | (two forward-slashes instead of four)| +--------------------------------------------------------------+ +------ System Automation for z/OS Version 4 Release 3 --------+ | | |PROGRAM NUMBER: 5698-SA4 | | | |TITLE: IBM Z System Automation Configuring | | | |CHAPTER Traditional SA z/OS Configuration | | | |TOPIC Step 29E: Migrate to Java 17 (OA65704) | | | |SUBTOPIC Deployed with its own embedded web server | | | |CHANGE: | | The current documentation contains an error in step 4 of | | the migration steps. The incorrect statement is that no | | property update is required if a key ring is used. | | With Java 17, the key ring URL has been adapted and now | | only requires two slashes instead of four, so the keystore | | and truststore properties must be updated. | | | | Migration steps | | 4. Change the ing.operations.security.properties file. | | If you are using a key ring, then you have to update the | | following properties: | | | | ing.security.tls.keystore = | | safkeyring://<USERID>/<KEYRING_NAME> | | (two forward-slashes instead of four)| | ing.security.tls.truststore = | | safkeyring://<USERID>/<KEYRING_NAME> | | (two forward-slashes instead of four)| +--------------------------------------------------------------+ +------ System Automation for z/OS Version 4 Release 3 --------+ | | |PROGRAM NUMBER: 5698-SA4 | | | |TITLE: IBM Z System Automation Administering | | | |CHAPTER SA z/OS User Exits | | | |TOPIC Command Exits | | | | | |CHANGE: | | Add new subtopic : AOFEXC12 | | This exit is called on entry on the command worker | | (EVJRVCMD) for the SA command server (EVJRVCM0). The exit | | allows you to perform authorization checking of the | | commands scheduled via the TWS batch interface (EVJRYCMD) | | against the user ID of the batch job requesting the command.| | Refer to the sample exit for details of the parameters | | passed to the exit and the return codes. | +--------------------------------------------------------------+
Local fix
Problem summary
Placeholder for documentation changes required in IBM Z System Automation V430 documentation
Problem conclusion
Documentation changes has been made in IBM Z System Automation V430 documentation
Temporary fix
Comments
APAR Information
APAR number
II14877
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2024-09-10
Closed date
2025-05-12
Last modified date
2025-05-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"001","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
12 May 2025