While the application server is processing, serious errors can occur. These errors can cause the operating system, the CICS subsystem, or the application server to end abnormally. The errors can be detected by the following:
When an error causes the application server to end abnormally, it displays error messages and reason codes. Also, if the error condition appears to be an internal error, a minidump is sent to the application server console. A minidump is sent to the display device indicated in the DSPLYDEV initialization parameter on a VSE system. You should save all this information for problem determination and refer to the DB2 Server for VSE & VM Diagnosis Guide and Reference manual.
First Failure Data Capture support is also available in a VM/ESA system to help in problem determination if the following conditions exist:
With First Failure Data Capture support, if an error occurs, relevant diagnostic information, control blocks, and data areas are captured at the error detection point in a VM console and sent to the print queue of the application server or requester. For further information on first failure data capture support, see the DB2 Server for VSE & VM Diagnosis Guide and Reference manual.
For general recovery, restart the application server the same way you would usually start it. For example, in VSE:
// JOB MULTI // EXEC PROC=ARIS71DB // EXEC PROC=ARIS71PL // EXEC ARISQLDS,SIZE=AUTO,PARM='PARMID=WARM1' |
And in VM,
SQLSTART DBNAME(server-name) ID(MYBOOT) PARM(PARMID=WARMSTRT) |
After you restart the application server, you must resolve any in-doubt logical units of work. In-doubt logical units of work can only occur for VSE guests accessing an application server on VM.