IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

ICE010A 0 NO SORT OR MERGE CONTROL STATEMENT


IBM Mainframe Forums -> DFSORT/ICETOOL
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Escapa

Senior Member


Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA

PostPosted: Thu Jul 28, 2011 7:43 pm
Reply with quote

Yesterday We had strange failure in a DFSORT step which was running daily for last six months...

Below is SYSOUT...

Code:

ICE000I 1 - CONTROL STATEMENTS FOR 5694-A01, Z/OS DFSORT V1R10 - 03:33 ON WED
ICE010A 0 NO SORT OR MERGE CONTROL STATEMENT                                 
ICE751I 0 C5-K90025 C6-K90025 E7-K62201                                     
ICE052I 3 END OF DFSORT                                                     


Below is SYSIN.. Well I feel.. in this particular case it is not that relevant...

Code:

  JOINKEYS F1=SAPORD,FIELDS=(60,5,A)                                     
  JOINKEYS F2=CORPSUP,FIELDS=(1,5,A)                                     
  JOIN UNPAIRED,F1                                                       
  REFORMAT FIELDS=(F1:1,971,F2:1,5)                                     
  SORT FIELDS=COPY,EQUALS                                               
  OUTREC IFTHEN=(WHEN=(56,4,CH,NE,C'    ',AND,60,5,CH,NE,972,5,CH),     
                BUILD=(1,55,224,3,X,60,912)),                           
         IFTHEN=(WHEN=(227,4,CH,NE,C'    ',AND,60,5,CH,NE,972,5,CH),     
                BUILD=(1,226,224,3,X,231,741)),                         
         IFTHEN=(WHEN=NONE,BUILD=(1,971))                               


I am looking all over to find root cause of this failure...

Anybody can help me investigate further..

To add one more point.. Job restarted by production control team as per operational document and went fine...
Back to top
View user's profile Send private message
sqlcode1

Active Member


Joined: 08 Apr 2010
Posts: 577
Location: USA

PostPosted: Thu Jul 28, 2011 7:48 pm
Reply with quote

Escapa,
Could you please provide your JCL or PROC containing SORT step? Is the member containing SORT statements, stored in PDS?

Out of curiosity, Is the issue resolved now? If yes, how?

Thanks,
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Thu Jul 28, 2011 7:50 pm
Reply with quote

Edit, then edit:

You got the beat on me sqlcode1.

Resolution seems to have been my old non-favourite, "bung it in again and see what happens". It then worked.

My usual blah-blah which I've written several times recently.

So, guess. On a PDS and "something" was updating the PDS. Later, when re-submitted, no problem.
Back to top
View user's profile Send private message
Escapa

Senior Member


Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA

PostPosted: Thu Jul 28, 2011 8:11 pm
Reply with quote

sqlcode1 wrote:
Escapa,
Could you please provide your JCL or PROC containing SORT step? Is the member containing SORT statements, stored in PDS?

Out of curiosity, Is the issue resolved now? If yes, how?

Thanks,

Yes its PDS.

Just restarted job by production control after some time.

Bill,
Quote:
So, guess. On a PDS and "something" was updating the PDS. Later, when re-submitted, no problem.

Could be.. But there is no reason why somebody(living or non living) should update that PDS... I need to look into that..
Back to top
View user's profile Send private message
sqlcode1

Active Member


Joined: 08 Apr 2010
Posts: 577
Location: USA

PostPosted: Thu Jul 28, 2011 8:22 pm
Reply with quote

Escapa,
Since your sort cards are stored in the PDS, did something else turned to production the day the job abended?

Reason I am asking is because, if other jobs reading the same PDS, used DISP=OLD, locks "may be" issued. Again reason I say "may be" is because access is managed and control by Security. Theoritically your job would have to wait until other jobs released the lock or the system would have placed request in the queue. However, in any case, if such locking indeed had happened, you should be able to view warning messages in the JESMSGLG.

As far as research is concerned, I would start with searching proc library for any procs using the same PDS with DISP=OLD and then research to see if that same job was running at the same time, your sort job abended. If you do find a job running at the same time and using DISP=OLD, that is your answer.

Thanks,
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Thu Jul 28, 2011 9:06 pm
Reply with quote

Easy to check for the living/dead - just the date/time on the member. OK, easy if you have it.

What about a scheduled backup/reorg? If someone naughtily runs that as disp=shr, can get you that way. What else was on the system at the time? If "something" is updating the directory while your job is trying to read the same directory block, it would look like this.

If not something like that, then you get into "weirdness"...
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales

PostPosted: Thu Jul 28, 2011 9:11 pm
Reply with quote

Queue the X files music icon_lol.gif

Have had that happen once, many many moons ago and a stright rerun worked fine. Never did find out the reason as it was deemed as fixed.
Back to top
View user's profile Send private message
Skolusu

Senior Member


Joined: 07 Dec 2007
Posts: 2205
Location: San Jose

PostPosted: Thu Jul 28, 2011 9:11 pm
Reply with quote

ESCAPA,

I would start with checking the complete JES messages (IEFxxx) of the failed job to see if there is an issue with the PDS containing the control cards.
Back to top
View user's profile Send private message
Escapa

Senior Member


Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA

PostPosted: Thu Jul 28, 2011 9:29 pm
Reply with quote

Skolusu wrote:
ESCAPA,

I would start with checking the complete JES messages (IEFxxx) of the failed job to see if there is an issue with the PDS containing the control cards.

Both IEF* and IGD* messages are as usual..
IGD103I and IGD104I mesages are shown up for that dataset

@Expat.. Same case here.. Nobody is pestering at the moment.. icon_cool.gif
Back to top
View user's profile Send private message
gcicchet

Senior Member


Joined: 28 Jul 2006
Posts: 1702
Location: Australia

PostPosted: Fri Jul 29, 2011 3:59 am
Reply with quote

Hi,

why not interrogate SMF to see if it throws some light on the issue.



Gerry
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Fri Jul 29, 2011 9:21 pm
Reply with quote

Escapa,

Any update on this? I'm feeling nervous about our questioners beginning to believe magic can happen...
Back to top
View user's profile Send private message
Escapa

Senior Member


Joined: 16 Feb 2007
Posts: 1399
Location: IL, USA

PostPosted: Fri Jul 29, 2011 9:31 pm
Reply with quote

Bill Woodger wrote:
Escapa,

Any update on this? I'm feeling nervous about our questioners beginning to believe magic can happen...


Bill, I know.. there is nothing called magic.. Everything has reason....

Just not getting hold of it yet...I am keen on it too..

...
I scanned all the job procedures and none uses access old for that PDS..
And I was negative about this possibility as there wasn't any warning also about dataset getting held...


Now I am suspecting online program creating PDS member into that PDS and then sumbitting job from program at that time. (Its M204 programming language) ... ....

I will keep forum posted.. when discovered...
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Fri Jul 29, 2011 9:42 pm
Reply with quote

OK. Gerry's idea seems to be the all-in-one-place possibility.

I think the DISP=OLD was a red-herring, as if DISP=OLD job is running, yours would have not got on, and vice-versa. DISP=SHR is another kettle... whoops, in deference to your Avatar, I won't complete that thought.

If you can't find anything, I suggest deletion of the whole topic, and no-one ever mention it again :-)
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Sat Jul 30, 2011 12:03 am
Reply with quote

Hello,

Something really awful to track down is when "someone" changed something in the pds (while the job was running or just before) and then made another change removing all traces of the change. . .

Is this a pds or a pdse? Can you tell if the problem member has been moved about (look at the ttr) if you can or ask the system support people to look a this.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DFSORT/ICETOOL

 


Similar Topics
Topic Forum Replies
No new posts How to split large record length file... DFSORT/ICETOOL 9
No new posts JCL sort card - get first day and las... JCL & VSAM 9
No new posts Using Dynamic file handler in the Fil... COBOL Programming 2
No new posts Sort First/last record of a subset th... DFSORT/ICETOOL 7
No new posts Merge two VSAM KSDS files into third ... JCL & VSAM 6
Search our Forums:

Back to Top