Hi Dave,
Could you please share the entire IZU476E error message. The system-name, HTTP-error-type and HTTP-response-code are variable for that message.
Taking a stab in the dark without that other error information, I am pretty sure that z/OSMF, as part of its CSRF protections, expects to match the host name part of the URL to the configured host name from the IZU APPSERVER HOST setting. There are a couple things you can try, but know in advance, I have never tried this with IP addresses used to access a z/OSMF server without a name server.
1) Set the IZUPRMxx CSRF_SWITCH parameter to OFF to disable CSRF checking. The default is ON. Caveats apply, bypassing CSRF protections is risky.
2) Use the reversed IP address as the reversed-hostnam in the <SAF_PREFIX>.REST.*.<reversed-hostname> ZMFAPLA resource class profile nme to allow CORS (Cross-Origin Resource Sharing) from that 'host'. Obviously this isn't a CORS request from another host, but z/OSMF will likely teat it that way because the inbound IP address in the URI is not actually a host name.
You can also submit an idea for z/OSMF to support name-server-less configurations where the server is accessed from browsers via its IP address instead of its host name.
------------------------------
John L. Czukkermann
IBM Corporation, Poughkeepsie, NY
czuk@us.ibm.com------------------------------
Original Message:
Sent: Wed October 09, 2024 02:53 PM
From: Dave Myers
Subject: ZUG464E - When doing a SYSTEMS VALIDATE on a z/OS 2.4 zOSMF COD system
I have a COD 2.4 z/OSMF running for a customer.
Customer does not have DNS setup and so we're using a localhost table in z/OS.
When we do a SYSTEMS VALIDATE on the CPAC and CPAC_001 system…we get IZU464E.
Our hostname and the IZU APPSERVER HOST setting is correct. CPAC.domainname
We can ping CPAC.domainname within z/OS, because we have the local host table entry for it.
Of course we cannot ping it from Windows because CPAC.domainname is not in their DNS server.
To get into zOSMF we use the IP address in the URL.
I'm stumped on whey we get the IZUG464E. (of course until we get this SYSTEM communications issue fixed…our submits and create workflows etc. won't work ).
Any ideas?
Thanks Dave
------------------------------
Dave Myers
------------------------------