RE: SQL vs V5R1 and service woes

PTF is currently in test mode, but it worked wonders for me.  SI02167.

One ptf had some special instructions.  I did these on our development
machine late at night with no ramifications.  However they are hot to trot
to get this ptf into production.  Any nasty ramifications of doing these
steps midday on a busy production box?  Other facts:
- Little to no C/S applications
- No web ap's on these machines.

SPECIAL INSTRUCTIONS:
To properly enable this PTF for prestarted server jobs,
you will need to stop and restart the SQL server jobs,
the Directory Services server jobs, the DRDA TCPIP server
jobs, and the host server jobs.  Otherwise
the prestarted server jobs may continue to use older versions
of programs and unexpected results may occur.  Applying this
PTF as delayed would achieve the same results.

To stop and restart the SQL server jobs, run the following:

ENDPJ SBS(QSYSWRK) PGM(QSQSRVR)
STRPJ SBS(QSYSWRK) PGM(QSQSRVR)

To stop and restart the DRDA TCPIP server jobs, run the following:

ENDTCPSVR SERVER(*DDM)
STRTCPSVR SERVER(*DDM)
To stop and restart the Directory Services server job,
run the following:

ENDTCPSVR SERVER(*DIRSRV)
STRTCPSVR SERVER(*DIRSRV)

To stop and restart the host server jobs, the following directions
must be followed.

The database server prestart jobs (QZDAINIT, QZDASOINIT, and QZDASSINIT)
by default are shipped to run in subsystem QSERVER (QZDAINIT)
and QUSRWRK (QZDASOINIT and QZDASSINIT).  However, systems can be
customized to allow the database server prestart jobs to run in other
subsystems.


SYSTEMS WITH DEFAULT CONFIGURATION (database server prestart jobs run
ONLY in the QSERVER and QUSRWRK subsystems).
----------------------------------------------------------------

1) To ensure that the database server prestart jobs are ended,
   issue the requests:

   QSYS/ENDPJ SBS(QSERVER) PGM(QSYS/QZDAINIT) OPTION(*IMMED)
   and
   QSYS/ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT) OPTION(*IMMED)
   and
   QSYS/ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASSINIT) OPTION(*IMMED)

   If the above commands fail with CPF0922, nothing more needs
   to be done (the prestarted jobs are already inactive).

2) To re-enable the function after the PTF is applied, issue the
   requests:

   QSYS/STRPJ SBS(QSERVER) PGM(QSYS/QZDAINIT)
   and
   QSYS/STRPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT)
   and
   QSYS/STRPJ SBS(QUSRWRK) PGM(QSYS/QZDASSINIT)

   If the above commands fail with CPF0921, nothing more needs
   to be done (the prestarted jobs are already active).

3) To re-enable the function for each subsystem "subsystem-name"
   identified, issue the following requests after the PTF is applied:

   QSYS/STRPJ SBS("subsystem-name") PGM(QSYS/QZDAINIT)
   and
   QSYS/STRPJ SBS("subsystem-name") PGM(QSYS/QZDASOINIT)
   and
   QSYS/STRPJ SBS("subsystem-name") PGM(QSYS/QZDASSINIT)

     ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT)
     STRPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT)

Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    rob@dekko.com
                    Sent by:                  To:     midrange-l@midrange.com
                    midrange-l-admin@mi       cc:
                    drange.com                Fax to:
                                              Subject:     RE: SQL vs V5R1 and 
service woes

                    09/11/2001 04:58 PM
                    Please respond to
                    midrange-l







Reply from the support line, (name stripped)

I have opened APAR SE02800 for this problem. I will advise you when I hear
when development expects to have a fix for the problem.



Rob Berendt

==================
A smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.