Does this help?

https://kinsta.com/knowledgebase/pr-end-of-file-error/#what-causes-the-pr_end_of_file_error


On Tue, Mar 26, 2024 at 6:28 PM Pommier, Rex <rpomm...@sfgmembers.com>
wrote:

> Hi List,
>
> We are attempting our first foray into getting z/OSMF up and running.
> Scenario is we're backleveled maintenance-wise on our 2.4 system.  We ran
> the security configuration setup etc and got z/OSMF up and running on the
> production LPAR we are planning on running it from.  However when we
> started to load z/OS 3.1 we ran into a problem with missing PTFs.  Got one
> set of PTFs installed and after adding a local_override.cfg file into the
> configuration directory we got z/OSMF up and running again and past that
> hurdle.  We hit the next one requiring a dozen more PTFs to bypass it.  We
> decided to move the install to our sandbox just to get z/OSMF working to
> the point we can use it to get our 3.1 software install back on track.  I
> ran disk-level flashcopy copies of my entire production LPAR to the
> sandbox, made the required changes (IP addresses etc) to get the sandbox up
> and running.  Started z/OSMF and it comes up with no errors or warnings
> (except the one telling me I'm using the local override file).  However,
> when I try to get to the web server I get a "secure connection failure"
> with " PR_END_OF_FILE_ERROR" trying to connect with Firefox and "
> 172.16.128.108 unexpectedly closed the connection" using Chrome.  Security
> (RACF) is identical to what it is on the production LPAR.  z/OSMF config is
> identical as well.  Does anybody have any idea what I'm missing?
>
> TIA,
>
> Rex
>
> ----------------------------------------------------------------------
> The information contained in this message is confidential, protected from
> disclosure and may be legally privileged. If the reader of this message is
> not the intended recipient or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any disclosure, distribution, copying, or any action taken or action
> omitted in reliance on it, is strictly prohibited and may be unlawful. If
> you have received this communication in error, please notify us immediately
> by replying to this message and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to