CA 7 Web Client - ECOR0024 Invalid date value after Java 21 upgrade
Article ID: 439807
Updated On:
Products
Issue/Introduction
After upgrading to Java 21 (specifically version 21.0.8), users of CA 7 Web Client may experience the following symptoms:
- Unreadable Logs - The STDOUT and STDERR spool files are garbled or appear in ASCII when viewed via SDSF.
- Login Failure - After applying the common workaround `IJO="$IJO -Dfile.encoding=IBM-1047"`, users are unable to log in to the GUI.
- Error Code - The login attempt fails with error ECOR0024: Invalid date value:
Environment
Java 21 (specifically version 21.0.8)
CA7 12.1 Web Client
z/OS
SDSF
Cause
Encoding Property `-Dfile.encoding=IBM-1047` was added to Java options to resolve 'Unreadable STDERR / STDOUT logs issue.
This changes the default character encoding for the entire Java Virtual Machine (JVM).
Whilst it makes the spool output (EBCDIC) readable, it forces the application to interpret all internal data—ie: date strings, session tokens, config files—as EBCDIC.
This result in parsing failures, such as ECOR0024, as the application is expecting standard web encoding.
Resolution
- Revert Global Encoding Property
1. Remove the global encoding override from your `STDENV` DD or environment configuration file as below:
2. Delete `IJO="$IJO -Dfile.encoding=IBM-1047"'. - Implement Targeted Output Encoding
1. Use the JZOS-specific environment variable to target only the output directed to the spool as below:
2. Add the following line to your `STDENV` file: 'JZOS_OUTPUT_ENCODING="IBM-1047"' - Upgrade Java (Recommended)
1. IBM addressed several encoding inconsistencies in subsequent releases of Java 21.
2. It is highly recommended to upgrade to Java 21.0.9 or higher3. This should resolve the unreadable log issue without requiring manual encoding overrides.
- Restart CA7 Web Client
1. Verify that GUI logon is working successfully
2. Verify that STDOUT/STDERR output is readable in SDSF
Feedback
