Load Utility error in DB2

BhavanaS · New User Joined: 20 Feb 2008 Posts: 17 Location: India

I am trying to a LOAD on Z/OS DB2 .. I do not know why I am getting this
error .. Any help is appreciated ...

DSNU000I DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = LSU0002
DSNU1044I DSNUGTIS - PROCESSING SYSIN AS EBCDIC
DSNU050I DSNUGUTC - LOAD DATA REPLACE LOG NO INDDN SYSREC00
DSNU650I -DST1 DSNURWI - INTO TABLE PSDB.PS_ABBR_TYPE_TBL
DSNU650I -DST1 DSNURWI - (BN_ANNL_BENBASE_CD POSITION(1) CHAR(4),

DSNU180I -DST1 DSNUGUCC - UTILITY IS NOT COMPATIBLE WITH THE LOAD UTILITY
UTILID = LSU0528, OBJECT = PSDBHR17.PSHR1707

DSNU012I DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8

Thanks in advance,

Gnanas N · Posted: Wed May 28, 2008 3:56 pm

From QW..,

DSNU180I csect-name UTILITY IS NOT COMPATIBLE WITH THE utility-name UTILITY UTILID = uid OBJECT = spacename.object-name

Explanation: Certain utilities cannot process the same table or index space at the same time. The message identifies the objects for which the
incompatibility occurred.

These objects, or their related log entries, might be target objects of
the utilities, a mapping table, or they might be catalog or directory
table spaces that are updated by the utilities. For example,
DSNDB06.SYSCOPY is updated by LOAD.

Severity: 8 (error)

System Action: The starting utility is not initiated, and further utility
processing in that utility job step is terminated.

User Response: Use -DISPLAY UTILITY with the provided 'uid' to determine when the utility that caused your utility to be rejected is completed.

Refer to DB2 Performance Monitoring and Tuning Guide for a discussion of which utilities are mutually compatible.

To avoid this error when running concurrent REBUILD INDEX with SHRLEVEL CHANGE, specify multiple indexes on a single utility execution instead of invoking multiple utilities.

guptae · Posted: Wed May 28, 2008 4:38 pm

Hi Bhavana,
Its not compaitable with load .Please check utility id LSU0528. Submit your load once above mentioned load is completed.

Craq Giegerich · Posted: Wed May 28, 2008 4:58 pm

An earlier unsuccessful attempt was made to load the table. You need to terminate the earlier load (LSU0528) before you can continue.

am_ne · New User Joined: 24 Mar 2007 Posts: 25 Location: Bangalore

Terminate the util-id LSU0528 (which left from a failed load job) and resubmit your job as a new job.

BhavanaS · New User Joined: 20 Feb 2008 Posts: 17 Location: India

Hi,
Thanks for the info.
The last two days I have been researching on this and all that I could understand is, if my job returns a maxcc 8 due to this incompatible UTILID all that I need to do is terminate the stopped utilid and then resubmit the job.Yes,this time the job ran successfully. But the problem is I have this error happenning in an automated load process.I have around 20 load jobs each having about 75 steps each referring to one table running at a time and if this error occurs I dont have all the tables loaded and I cant keep rerunning the jobs individually after terminating the stopped utilids.

So can someone tell me how we can avoid this incompatible utilid issue.I am using the following step in my load job for this but still this error is persistent in some of the steps

//*********************************************************
//* CLEAN UP UTILITY IF IT FAILES
//*********************************************************
//IKJTERM1 EXEC PGM=IKJEFT1A
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//UTPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN
DSN SYSTEM(TG01)
-TERM UTILITY(utility name)
/*

Thanks in advance,

dick scherrer · Posted: Fri May 30, 2008 10:25 pm

Hello,

You may have a "scheduling" problem. Currently, processes that cannot run at the same time are running at the same time. You need to change the way these processes execute so that there are no conflicts.

One thought might be to use the system scheduling software and define jobs that cannot execute concurrently as a predecessor/successor combination and they will be scheduled to run serially.

am_ne · New User Joined: 24 Mar 2007 Posts: 25 Location: Bangalore

Hi Bhavana,

It may happen in following scenario also.

One load job ran and failed. As you know all utility job associated with one "util-id". This job never resarted or get purged by the user without terminating the "utility-id".

The availability of the table/tablesapce depends on the phase of the load utility, when it failed. Assume the abend didn't change the status of the tablespace. So the application can access the data but the incompatible utilities cannot run on the table.

The clean up jcl looks fine. But how will you clean an util-id without knowing its name.

Loading of the table can be controlled by granting LOAD privilege to selected users on database level so that it will be easier to detect contentention. Once contention detected you can do scheduling change as suggested by Dick.

Thanks
Amit

Venu Rao · Posted: Tue Jun 03, 2008 1:32 am

Try to load with a new utility-id

BhavanaS · New User Joined: 20 Feb 2008 Posts: 17 Location: India

Hi,

As suggested by Dick I did a regrouping of all the tables with respect to their tablespace.As in, I now have all the tables belonging to one tablespace coming in a sequence followed by the tables in next tablespace.I have the utilid names as the tablespace name itself so that I can now have one utilid for one tablespace.I have also taken care not to submit jobs pertaining to same utilid parallely.So I dont have issues like duplicate utilid or mismatch of utilids now.The following are the steps that I have for loading a table:

Code:

//**********************************************************************
000090 //* LOAD DATA PS_ESTAB_LOC_US
000091 //**********************************************************************
000092 //LSU0228 EXEC PGM=DSNUTILB,PARM='TG01,PSHR1009',REGION=0M
000093 //SORTOUT DD UNIT=SYSDA,SPACE=(CYL,(300,20),RLSE)
000094 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000095 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000096 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000097 //SORTWK04 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000098 //SORTWK05 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000099 //SORTWK06 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000100 //SORTWK07 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000101 //SORTWK08 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000102 //SORTWK09 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000103 //SORTWK10 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000104 //SORTWK11 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000105 //SORTWK12 DD UNIT=SYSDA,SPACE=(CYL,(200,1000),RLSE)
000106 //SYSDISC DD UNIT=SYSDA,SPACE=(CYL,(330,20),RLSE)
000107 //SYSERR DD UNIT=SYSDA,SPACE=(CYL,(330,20),RLSE)
000108 //SYSMAP DD UNIT=SYSDA,SPACE=(CYL,(330,20),RLSE)
000109 //SYSREC00 DD DSN=A920080.DTS.USN0228,DISP=SHR
000110 //SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(330,20),RLSE)
000111 //SYSPRINT DD SYSOUT=*
000112 //UTPRINT DD SYSOUT=*
000113 //SYSIN DD DSN=A920080.DTS.SUL0228,DISP=SHR
000114 //BSU0228 EXEC PGM=IKJEFT1A
000115 //SYSTERM DD SYSOUT=*
000116 //SYSPRINT DD SYSOUT=*
000117 //SYSTSPRT DD SYSOUT=*
000118 //SYSTSIN DD *
000119 DSN SYSTEM(TG01)
000120 -TERM UTIL (PSHR1009)
000121 /*
000122 //ISU0228 EXEC PGM=IKJEFT1A,DYNAMNBR=20
000123 //SYSUDUMP DD SYSOUT=*
000124 //SYSPRINT DD SYSOUT=*
000125 //SYSTSPRT DD SYSOUT=*
000126 //SYSOUT DD SYSOUT=*
000127 //SYSTSIN DD *
000128 DSN SYSTEM(TG01)
000129 -START DATABASE (PSDBHR10) SPACENAM (PSHR1009) ACCESS (FORCE)
000130 END
000131 /*

I am now facing the following issue

Venu Rao · Posted: Thu Jun 05, 2008 6:58 pm

Change the utility name PSHR1009 to any other name and Run again.

dick scherrer · Posted: Fri Jun 06, 2008 12:16 am

Hello,

am_ne · New User Joined: 24 Mar 2007 Posts: 25 Location: Bangalore

Hi Bhavna,

Venu's suggestion should work.

Above jcl will work fine for LOAD REPLACE jobs provided you tablesapce is not having any index. Otherwise you have to FORCE start associated indices as well.

For LOAD RESUME jobs, I would suggest to add one FORCED abend step after load step so that the job will abend if the RC > 04 for the load step.
This can be corrected and the utility can be restarted in proper phase.
It is not a very good idea to terminate the utility id and froce start the tablespace for LOAD RESUME jobs. This may leads to data inconsistency and index corruption.

Thanks
Amit

Marlon · Posted: Fri Jul 11, 2008 11:58 am

Hi,

I just got this same problem but I'm not sure what to do, my first question how will I terminate my "UTILID" any command or jcl? I tried to cancel my job and resubmit my job as a new job but still the same problem occurs still SRMRL.SZ0$LOD6 appears as my UTILID.

DSNU180I : DSNUGUCC - UTILITY IS NOT COMPATIBLE WITH THE RUNSTATS TABLESPACE UTILITY UTILID = SRMRL.SZ0$LOD6, OBJECT = SZ0DBU.AUDT00IX

DSNU012I DSNUGBAC - UTILITY EXECUTION TERMINATED, HIGHEST RETURN CODE=8

Marlon · Posted: Fri Jul 11, 2008 12:33 pm

Sorry, just disregard my post, I was able to terminate my utilid by running the above jcl and my problem was solve. Thanks...

dick scherrer · Posted: Fri Jul 11, 2008 8:21 pm

Hello Marlon,

Good to hear it is working - thanks for letting us know

d

chitanya · New User Joined: 25 Jan 2008 Posts: 6 Location: Hyderabad

Hi bhavana,

I am also facing the same problem can you please let me know how you exactly resolved the problem.
Even i terminated UTILID same problem i am facing.

Regards
Chaitanya

dick scherrer · Posted: Wed Aug 18, 2010 8:55 pm

Hello,

Please re-read the topic.

As mentioned, jcl from this very topic was used. . .