Re: Applying PTF -- MIDRANGE-L

PTF  SI16412  replaces SI15663, we have that one aplyed.

When I aply SI16412 the active servers keep running, but if I stop and start the server I get the error, so I did a RMVPTF LICPGM(5722DG1) SELECT(SI16412) , start the server and it runs Ok. I didn't try the restart option, just stop (endtcpsvr) & start again. I can keep SI16412 "No aplicado" but I'm very surprised that a PTF causes something to stop working. My doubt is if I will get other problems by not having the PTF aplyed. ____________________________________________________________________ Jan Rockstedt wrote:

SPECIAL INSTRUCTIONS FOR SUPERSEDED PTF SI15663 :
 =================================================

  If you have not experienced this problem, nothing needs to be done.
  If you have experienced this problem, you need to do the following:
  This PTF will be activated for a HTTP server when that server
  instance is ended and started, or at the next IPL.  If an
  HTTP server is already active at the time this PTF is applied,
  the HTTP server must be ended and started in order to
  activate this PTF for that HTTP server instance.

  Do the following to activate this PTF for all HTTP server
  instances.
    1.  ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ALL)
    2.  Start the HTTP server(s) using:
          STRTCPSVR SERVER(*HTTP) HTTPSVR(<server name>)

  If you have HTTP servers running when this PTF is applied, you
  should not perform a restart of these servers. A restart can cause
  your HTTP server to fail.


Mvh / Regards
Jan "Janne" Rockstedt

Avinova AB 040 - 668 07 45

-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Raul A. Jager W. Sent: Monday, April 18, 2005 4:38 PM To: Midrange Systems Technical Discussion Subject: Applying PTF

We have recently aplyed the cume PTF C5032530, all went Ok until we
restarted the AS and the webserver did not statr.  The joblog had a
message refering to a null pointer in XLATE.
Un-aplying PTF  SI16412 fixed the problem, Aplying again the problem
came back.

We have a 520 at V5.3