Re: moving to new iSeries

[Chris Whisonant <Chris.Whisonant@xxxxxxxxxxxxx>]

Do any tasks other than SERVER and QNNINSTS start?

I can think of two initial possiblities

1 - Do you have a Program Document in your NAB that may be referring to a 
file that may not exist on the new box?

2 - Do you have a script specified in the Fault Recovery section on your 
server document? Does this script exist on the new box?

Also, do you have the DMPCLLSTK and/or DMPSVRSTKS commands? You can use 
these while the jobs are starting up to generate a more detailed dump of 
what they are doing and get that information to Lotus.

Chris Whisonant
Comporium
Senior Mid-Range Systems Administrator
IBM eServer Certified Systems Expert - iSeries Technical Solutions V5R2
IBM Certified System Administrator - Lotus Notes and Domino 6/6.5
803.326.7270 | 803.326.6142 fax
http://cwhisonant.blogspot.com/

domino400-bounces+chris.whisonant=comporium.com@xxxxxxxxxxxx wrote on 
09/30/2005 03:58:46 PM:

> We're moving from an 800 to a 520 and did a full save on the 800 and
> restore on the 520.  Updated the resource names and IP settings,
> disconnected the old box from the network and fired up one of our Domino
> servers on the new box.  Server does not start, joblog messages follow.
> Tried firing up our Sametime and Quickplace servers on the new box and 
they
> start OK.  Take a look at the joblog messages and let me know if anyone 
has
> any ideas
> 
> There are two joblogs that appear after trying to start the server, one 
for
> the SERVER job, the other for the QNNINSTS job.  The messages below are
> from the SERVER job.  There does't appear to anything meaningful in the
> QNNINSTS joblog.
> 
> Both boxes V5R3, same PTF levels.  Domino at 6.5.4 FP1 on both boxes
> 
> MCH3402    Escape                  40   09/30/05  15:43:56.562456 
LIBNOTES
> QDOMINO654  *STMT    LIBNOTES    QDOMINO654  *STMT
> >From module . . . . . . . . :   CLEANUP
> >From procedure  . . . . . . :   OSFaultRecoveryRemovePid
> Statement . . . . . . . . . :   1
> To module . . . . . . . . . :   CLEANUP
> To procedure  . . . . . . . :   OSFaultRecoveryRemovePid
> Statement . . . . . . . . . :   1
> Message . . . . :   Tried to refer to all or part of an object that no
> longer exists.
> Cause . . . . . :   The most common cause is that a stored address to an
> object is no longer correct because that object was deleted or part of 
the
> object was deleted
> 
> CEE9901    Escape                  30   09/30/05  15:43:56.604296 QLEAWI
> QSYS        *STMT    QP0ZPCPN    QSYS        *STMT
> >From module . . . . . . . . :   QLEDEH
> >From procedure  . . . . . . :   Q LE leDefaultEh
> Statement . . . . . . . . . :   168
> To module . . . . . . . . . :   QP0ZPCPN
> To procedure  . . . . . . . :   InvokeTargetPgm__FP11qp0z_pcp_cb
> Statement . . . . . . . . . :   187
> Message . . . . :   Application error.  MCH3402 unmonitored by LIBNOTES 
at
> statement 0000000001, instruction X'0000'.
> Cause . . . . . :   The application ended abnormally because an 
exception
> occurred and was not handled.  The name of the program to which the
> unhandled exception is sent is LIBNOTES CLEANUP 
OSFaultRecoveryRemovePid.
> The program was stopped at the high-level language statement number(s)
> 0000000001 at the time the message was sent.  If more than one statement
> number is shown, the program is an optimized ILE program.  Optimization
> does not allow a single statement number to be determined.  If *N is 
shown
> as a value, it means the real value was not available.
> Recovery  . . . :   See the low level messages previously listed to 
locate
> the cause of the exception.  Correct any errors, and then try the 
request
> again.
> 
> Bob
> 
> 
> _______________________________________________
> This is the Lotus Domino on the iSeries / AS400 (Domino400) mailing list
> To post a message email: Domino400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/domino400
> or email: Domino400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/domino400.
>