Starting with SAS 9.4M9 on z/OS, the IBM Java 21.0.4 (or later) 64-bit SDK is required. To support this Java requirement, you must apply several SAS hot fixes during the initial installation.
You must download the following hot fixes along with your SAS 9.4M9 software order and apply them during the initial installation:
|
Hot Fix |
Component |
Description |
|
Threaded Kernel Java 9.4_M9 |
Required for Threaded Kernel Java support. | |
|
Base SAS® JAR Files for z/OS 9.4 |
Required for Base SAS Java integration. | |
|
SAS® Integration Technologies JAR Files for z/OS 9.4 |
Required for Integration Technologies Java support. |
For supported Java releases, see SAS KB0041603, "Java service refresh levels currently supported by SAS® in the z/OS operating environment."
You must obtain the IBM Java SDK for z/OS systems directly from IBM. Deploy the appropriate version (21.0.4 or later) in your z/OS environment before running SAS 9.4M9.
When launching the SAS Deployment Tools or SAS 9.4M9 with IBM Semeru Java 21, the following message might occur:
Probable fatal error: No physical fonts found.
This message is generated when IBM Semeru Java detects that WorldType fonts are not installed on the z/OS system.
Resolved.
Refer to the Java Requirements section of System Requirements for 9.4 Foundation for z /OS and see the following instructions from IBM that describes the fonts to install when using IBM Semeru Java on z/OS:
The IBM Semeru Runtime Certified Edition for z/OS document for Java 21 contains the Semeru fonts support on z/OS section. This section contains the following information:
“For Semeru, the default location for fonts is /usr/lpp/fonts/worldtype. Make sure that the following FMIDs for the z/OS Font Collection are made available on your z/ OS system at that location:
Workaround
Alternately, you can circumvent this issue by creating symbolic links or copies of an existing font on the system and naming them as the expected fonts.
The installer looks for the following files:
Select an existing TrueType font on your system and create symbolic links.
Here is an example:
ln -s wt__i___.ttf wt__j__b.ttf
ln -s wt__i___.ttf tnrwt_j.ttf
Copy an existing font and rename it to the expected file names.
Either of these approaches provide the required font files so that the installer can proceed. Any valid .ttf font available on the system can be used.
This workaround avoids installing the full set of Asian fonts while still satisfying the installer requirements. Note that these font directories are often mounted read/only, so they will have to be unmounted and mounted again as read/write before making the change.
For more information, see SAS 9.4 Support for Java.