002-04,IGC0005E error



Support for OS/VS COBOL, VS COBOL II, COBOL for OS/390 & VM and Enterprise COBOL for z/OS

002-04,IGC0005E error

Postby jaggz » Fri Sep 02, 2011 3:15 pm

User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 4 times

Re: 002-04,IGC0005E error

 

Re: 002-04,IGC0005E error

Postby prino » Fri Sep 02, 2011 3:49 pm

And you really think someone will go through this for free? You've got to be kidding!

The error has nothing to do with rewrites, see IBM: LookAt - z/OS messahe help:

Return Code Explanation

04
    One of the following occurred:

        An incorrect record was encountered during a QSAM GET operation. The data set consists of variable format records. The length field in the record descriptor word (RDW) is incorrect for one of the following reasons:

            The RDW specifies a length less than 4.

            The RDW specifies a length greater than the DCBLRECL value that was specified when the data set was opened. DCBLRECL is the logical record length (LRECL) in the data control block (DCB).

        QSAM tried to read segments of variable spanned records that are not in proper sequence.

        LRECL is not large enough.

        The record area in QSAM locate mode is too small to contain a logical record from a spanned-format data set.

        The BDW contained a length greater than the blocksize specified in the data control block (DCB).
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
User avatar
prino
 
Posts: 536
Joined: Wed Mar 11, 2009 12:22 am
Location: Oostende, Belgium
Has thanked: 3 times
Been thanked: 21 times

Re: 002-04,IGC0005E error

Postby jaggz » Fri Sep 02, 2011 4:46 pm

Hi,

the infile dataset attribute are :
Management class . . : **None**        Allocated cylinders : 3,200           
Storage class  . . . : **None**        Allocated extents . : 1               
 Volume serial . . . : xxxMF2                                                 
 Device type . . . . : 3390                                                   
Data class . . . . . : **None**                                               
 Organization  . . . : PS             Current Utilization                     
 Record format . . . : VBS             Used cylinders  . . : 2,985           
 Record length . . . : 32760           Used extents  . . . : 1               
 Block size  . . . . : 32760                                                 
 1st extent cylinders: 3200                                                   
 Secondary cylinders : 200            Dates                                   
 Data set name type  :                 Creation date . . . : 2011/08/16       
 SMS Compressible. . : NO              Referenced date . . : 2011/09/02       
                                       Expiration date . . : ***None***     



Outfile :

Data Set Name . . . . : A255209.SMF.UNFMT.OUTPUT                               
                                                                               
General Data                           Current Allocation                     
 Management class . . : **None**        Allocated cylinders : 1,300           
 Storage class  . . . : **None**        Allocated extents . : 2               
  Volume serial . . . : CT3WK1                                                 
  Device type . . . . : 3390                                                   
 Data class . . . . . : **None**                                               
  Organization  . . . : PS             Current Utilization                     
  Record format . . . : FB              Used cylinders  . . : 967             
  Record length . . . : 32760           Used extents  . . . : 2               
  Block size  . . . . : 32760                                                 
  1st extent cylinders: 800                                                   
  Secondary cylinders : 500            Dates                                   
  Data set name type  :                 Creation date . . . : 2011/09/02       
  SMS Compressible. . : NO              Referenced date . . : 2011/09/02       
                                        Expiration date . . : ***None***       



but still i get an error : S002 R=4. Please suggest me your comments.


CEE3250C The system or user abend S002 R=00000004 was issued.
From compile unit SMFMAY97 at entry point SMFMAY97 at compile unit offs
at address 00CCE93E.
=00000004 was issued.
try point SMFMAY97 at compile unit offset -098326AA at entry offset -098326AA
User avatar
jaggz
 
Posts: 356
Joined: Fri Jul 23, 2010 8:51 pm
Has thanked: 8 times
Been thanked: 4 times

Re: 002-04,IGC0005E error

Postby Robert Sample » Fri Sep 02, 2011 6:18 pm

jaggz, why are you not using the debug facilities you have available at your site to find the current record being processed and look at the record length? Or even look up the value of WS-77-TEMP which will tell you how long the current record is? In other words, it does not look like you have done ANYTHING to find the cause of the problem yourself and are expecting us to find it for you. Since you did not bother to use the Code tag to preserve spacing, looking at the dump data is not something I'm interested in even attempting.

One observation: your input file is VBS with LRECL 32760; your output file is FB with LRECL 32760. This could be part of your problem.
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: 002-04,IGC0005E error

Postby Ed Goodman » Fri Sep 02, 2011 6:52 pm

For what it's worth, I had success reading SMF records using this:
FD  SMF-INFILE                       
    RECORDING MODE IS S               
    BLOCK CONTAINS 32756.             
                                     
01  SMF-INREC   PIC X(32756).         


then

READ SMF-INFILE                   
    AT END                       
        SET WSS-EOF TO TRUE       
        GO TO 40000-EXIT.         
                                 
ADD 1 TO WSA-RECORDS-READ         
MOVE SMF-INREC TO QWSMF030-RECORD


We have a process in place that extracts the SMF records and puts them on a flat file. This program would read that flat file. From what others have said, your shop probably has something similar set up, since it's a common practice.
Ed Goodman
 
Posts: 342
Joined: Thu Feb 24, 2011 12:05 am
Has thanked: 3 times
Been thanked: 17 times

Re: 002-04,IGC0005E error

Postby enrico-sorichetti » Fri Sep 02, 2011 6:57 pm

any reason why we should read all the garbage You posted!

given the frequency of Your posts ...
isn ' t it time for Your organization to use the servics of a paid consultant
instead of relying on free consultancy from public forum ? :evil:

looks like You and You company do not have a bit of ethics !
or maybe that' s Your way of doing business ???

furthermore after all Your posts You haven' t even learned how to enclose data within the code tags !

and the IBMUSER userid looks very suspicious to me,
what kind of stupid company would let anybody use the IBMUSER userid
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico-sorichetti
Global moderator
 
Posts: 2644
Joined: Fri Apr 18, 2008 11:25 pm
Has thanked: 0 time
Been thanked: 130 times

Re: 002-04,IGC0005E error

Postby steve-myers » Fri Sep 02, 2011 7:17 pm

I agree with others. Some months ago I decided not to respond to anything from jaggz. While I cannot and will not dictate what others do, I think this is a Good Idea.

SMF data in a "flat" dataset is always RECFM=VBS. LRECL=32760. I don't know about Cobol, but in Assembler it requires the BFTEK=A and MACRF=GL DCB parameters to read it.
steve-myers
Global moderator
 
Posts: 1885
Joined: Thu Jun 03, 2010 6:21 pm
Has thanked: 4 times
Been thanked: 197 times

Re: 002-04,IGC0005E error

Postby dick scherrer » Fri Sep 02, 2011 10:59 pm

Hello,

Why in the world was that mountain of junk posted. . . Why (after a year) are the code tags not being used. . . :(
As was mentioned, this will prevent most from even attempting to read it. I'll probably "Code" the entire batch, but it will still be mostly unusable and will still waste space on the forum. . .

Even though this forum is intended for students and other beginners, there still needs to be some advancement thru time spent here. . . Some appear to have no desire to actually learn and become useful / self-sufficient. . .

As we often mention, we will help people with questions/problems, but have no intention of doing the work for them.
Some people just do not have a clue that there is a difference. . .

d
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: 002-04,IGC0005E error

Postby NicC » Fri Sep 02, 2011 11:21 pm

This probably has nowt to do with the problem but in the compile step SYSLIB is coded as SYSOUT=* whereas it should be an input dataset (PDS(E)) with any COPYBOOK members.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: 002-04,IGC0005E error

Postby enrico-sorichetti » Fri Sep 02, 2011 11:29 pm

if the syslib is not used... no copy/include
I guess it can be anything, it will not be referenced anyway,
and the compilation finished wit a RC 0
0End of compilation 1, program SMFMAY97, no statements flagged.
0Return code 0
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico-sorichetti
Global moderator
 
Posts: 2644
Joined: Fri Apr 18, 2008 11:25 pm
Has thanked: 0 time
Been thanked: 130 times

Next

Return to IBM Cobol

 


  • Related topics
    Replies
    Views
    Last post