And on z/OS 3.1 I found JAVA had to be the V17 level. V8 caused z/OS MF to stop and drop during startup.
Matthew On Wed, 17 Jul 2024 08:12:55 -0500, Tom Longfellow <[email protected]> wrote: >For those that have uncontrolled curiosity: > >RESOLVED. > >RECAP. > > September 2023 JAVA update on our system 'broke' the submission process of > software deployment. > >Issue was known to IBM Support and a correcting APAR for JAVA was recommended. > >Applying that APAR (with GROUPEXTEND) somehow hijacked the current and >current_64 symbolic links from J8.0 to J11.0. This broke the ability of >z/OSMF to communicate via https and the internet. > >We did not know first - that we had been changed to a new JAVA and second - >J11 is not approved for z/OS 2.5 > >Manual unlink and ln commands were performed to correct the current and >current_64 symbolic links now allows z/OSMF http operations AND the submission > of jobs from software deployment. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
