Re: U0852
On Wed, 28 Sep 2005 12:57:17 +0330, Mehrdad Rastegar [EMAIL PROTECTED] wrote: Hi all, In IMS V6R1, How a LOST POINTER may be created in a database and how we can prevent the Abend U0852 in batch process? Mehrdad, You'll have better luck getting an answer to this on the IMS-L list. See: https://po.missouri.edu/cgi-bin/wa?A0=ims-l -Rob -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: U0852
My first suspect is improper sharing. That is, databases being accessed/updated by more than one batch process at a time. Specify DISP=OLD. HTH. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mehrdad Rastegar Sent: Wednesday, September 28, 2005 4:27 AM To: IBM-MAIN@BAMA.UA.EDU Subject: U0852 Hi all, In IMS V6R1, How a LOST POINTER may be created in a database and how we can prevent the Abend U0852 in batch process? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: U0852
Short but not complete list 1. abend that didn't backout correctly 2. invalid sharing - 2 update jobs with disp=shr 3. more exotic - write failures on disk, working as designed, running a report job while online is still updateing. The proper response is to run SMU and find out if the lost pointer still exists. If yes, fix it - see IMS manuals. The abend is because someone has a job that isn't playing by the rules. Mike Bell On 9/28/05, Mehrdad Rastegar [EMAIL PROTECTED] wrote: Hi all, In IMS V6R1, How a LOST POINTER may be created in a database and how we can prevent the Abend U0852 in batch process? This is part of system log at the time of Abend: -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: U0852
To Mike's list I'd add missing APAR or PTF. Several of my worst pointer disasters were maintenance related. SMU, run standalone, is definitely a good first step. DISP=OLD at a minimum. Mike Bell [EMAIL PROTECTED] wrote: Short but not complete list 1. abend that didn't backout correctly 2. invalid sharing - 2 update jobs with disp=shr 3. more exotic - write failures on disk, working as designed, running a report job while online is still updateing. The proper response is to run SMU and find out if the lost pointer still exists. If yes, fix it - see IMS manuals. The abend is because someone has a job that isn't playing by the rules. Mike Bell On 9/28/05, Mehrdad Rastegar wrote: Hi all, In IMS V6R1, How a LOST POINTER may be created in a database and how we can prevent the Abend U0852 in batch process? This is part of system log at the time of Abend: -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Edward Long -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
