Use of "--#SET MAXERRORS" parameter on DB2 V8

Marcos Torres · New User Joined: 11 May 2009 Posts: 4 Location: Brazil

I am trying to use the --#SET MAXERRORS -1 parameter to run DDL on DB2 v8 and I got the following error message:

*** ERROR **************************************************************
* DSNTEP2 halted due to a functional comment (--#SET) statement error:
* Invalid value, "MAXERRORS", specified for function.
************************************************************************

Can anybody tell me how to use this parameter of if there is another way to set MAXERRORS?

Thanks in advance.

dick scherrer · Posted: Fri Jun 19, 2009 2:27 am

Hello and welcome to the forum,

Why do you want a process to continue if there is an error. . .?

Marcos Torres · New User Joined: 11 May 2009 Posts: 4 Location: Brazil

Hi dick, thanks for answering.

I need that the process continue because the error is that I´ve already did that definition, and I am running the JCL after some corrections. There is a lot of definitions and I cannot drop the definitions every time I got an error.

I know that the default value for MAXERRORS on DB2 is 10, but the way that the DB2 manual specify the SET MAXERRORS use doesn´t work.

I really need this parameter works.

dick scherrer · Posted: Fri Jun 19, 2009 3:20 am

Hi Marcos,

Maybe someone will be able to provide direction.

I looked in the db2 manuals we have linked (IBM Manuals at the top of the page), but i could not find it.

Which version of db2 are you using?

I'm going to be on the road here shortly, but will try to look some more later this evening.

Marcos Torres · New User Joined: 11 May 2009 Posts: 4 Location: Brazil

Dick,

the DB2 is version 8.

Tks.

dick scherrer · Posted: Fri Jun 19, 2009 5:00 am

Hi Marcos,

If i'd paid attention to your topic/subject. . . .

See if this will help:
publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.db2tools.adb.doc.ug/upasect.htm

Marcos Torres · New User Joined: 11 May 2009 Posts: 4 Location: Brazil

Hi Dick.

I found out today why the parameter --#SET MAXERRORS -1 was not working at that day.

I was using a DB2 V8 subsystem at COMPATIBILITY MODE. By other reasons than this, I changed to a DB2 V8 subsystem at NEW FUNCTION MODE.

This parameter only works for DB2 V8 at NEW FUNCTION MODE. A DB2 V8 at COMPATIBILITY MODE is, for all efects, a DB2 V7.

Best regards, and thanks for your helping,

Marcos Torres.

dick scherrer · Posted: Wed Jun 24, 2009 8:31 am

You're welcome and thanks for telling us the solution

d