MVSFORUMS.com Forum Index MVSFORUMS.com
A Community of and for MVS Professionals
 
 FAQFAQ   SearchSearch   Quick Manuals   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

block size issue

 
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> Job Control Language(JCL)
View previous topic :: View next topic  
Author Message
SMS
Beginner


Joined: 16 Oct 2005
Posts: 53
Topics: 24

PostPosted: Tue May 29, 2007 5:03 pm    Post subject: block size issue Reply with quote

Hi,


I ran a job with two steps. The first step will execute a program
and create a file which will get loaded into a table in the second step.

During execution, the first step created a blank file with zero block size and
the second step failed with the below message. But the job has not failed
because of the empty file. I guess, there is issue with the zero blk size file.
I'm not sure why the file is getting created with zero blk size and
the reason for the below abend message.

could you please give your inputs on this ?

IEC036I 002-30,IGC0005E,TSDO555B,TS533Z90,SYSREC,8F2B,DPMDU8,TSDOCD00.TSDO555B.S
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=002 REASON CODE=00000030
TIME=12.29.18 SEQ=50603 CPU=0000 ASID=009F
PSW AT TIME OF ERROR 075C1000 80D7CCDE ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00D7DDE8 - 41004346 0A0DB20A 00501208
GR 0: 00000000_00D7CEE8 1: 00000000_A1003000
2: 00000000_001E3118 3: 00000000_00D7C6A2
4: 00000000_009D94A8 5: 00000000_00D42000
6: 00000000_009D834C 7: 00000000_FFFFFF0A
8: 00000000_009D875C 9: 00000000_009CAE40
A: 00000000_009A9888 B: 00000000_001B31BC
C: 00000000_009CAE40 D: 00000000_00000070
E: 00000000_00D7CB04 F: 00000010_00000030
END OF SYMPTOM DUMP
IEF472I TSDO555B TS533Z90 TS555Z90 - COMPLETION CODE - SYSTEM=002 USER=0000 REASon code 30
IEF285I #OPER.TSDO555B.JOB56539.D0000134.? SYSOUT


-------------------------------------------------------------------

DSNU016I DSNUGBAC - UTILITY BATCH MEMORY EXECUTION ABENDED, REASON=X'0002'


Thanks
SMS
Back to top
View user's profile Send private message
CICS Guy
Intermediate


Joined: 30 Apr 2007
Posts: 292
Topics: 3

PostPosted: Tue May 29, 2007 6:43 pm    Post subject: Re: block size issue Reply with quote

SMS wrote:
I ran a job with two steps. The first step will execute a program and create a file which will get loaded into a table in the second step.
During execution, the first step created a blank file with zero block size and the second step failed with the below message. But the job has not failed because of the empty file. I guess, there is issue with the zero blk size file.
What program created the empty file?
Was the empty file created as an allocation or was it actually opened and closed?
What was the DISP for the DD of the empty file in the second step?
You gave good information with the DFSort errors, but you left out three quarters of the information by not including the other sysouts and JCL.........
If you want to "trickle" additional information, the solutions will "trickle" back at a similar rate.....
Back to top
View user's profile Send private message
expat
Intermediate


Joined: 01 Mar 2007
Posts: 475
Topics: 9
Location: Welsh Wales

PostPosted: Wed May 30, 2007 12:47 am    Post subject: Reply with quote

If you specify BLKSIZE=0 in the JCL .......... DON'T DO IT

Let the system determine the BLKSIZE for you, just code RECFM= and LRECL= and do not use DCB=(something, .................... ) either.
Back to top
View user's profile Send private message
kolusu
Site Admin
Site Admin


Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose

PostPosted: Wed May 30, 2007 4:52 am    Post subject: Reply with quote

Quote:

I'm not sure why the file is getting created with zero blk size and
the reason for the below abend message.

SMS,

If you haven't coded the blocksize in the JCL and your program did NOT open the file at all then there is a chance that the file is created with zero blocksize. Rre-run your program to create the file with the correct blocksize.

Check this link for a detailed explanation of the error message

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2M751/SPTEE036I

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu
Back to top
View user's profile Send private message Send e-mail Visit poster's website
SMS
Beginner


Joined: 16 Oct 2005
Posts: 53
Topics: 24

PostPosted: Wed May 30, 2007 7:52 am    Post subject: Reply with quote

Hi All,

Thanks. Let me try the solutions suggested by you.

SMS
_________________
Regards,
SMS
Back to top
View user's profile Send private message
Nic Clouston
Advanced


Joined: 01 Feb 2007
Posts: 1075
Topics: 7
Location: At Home

PostPosted: Wed May 30, 2007 8:07 am    Post subject: Reply with quote

expat,

Hi, what is the difference between coding blksize=0 and not specifying a blksize at all? I thought (bad idea) that blksize=0 said 'let the system do it for you'? Or has that changed whilst I was delivering pizza and driving taxis? I have come acros, somewhere, a comment that in certain circumstances you do NOT let the system do it for you.

Agency interview next week, holiday in 2 hours! 26 of the next 100 hours will be spent in an aluminium tube - bliss Question
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.
Back to top
View user's profile Send private message
Nic Clouston
Advanced


Joined: 01 Feb 2007
Posts: 1075
Topics: 7
Location: At Home

PostPosted: Wed May 30, 2007 8:08 am    Post subject: Reply with quote

bummer - that was meant to be a pm - never mind - the answer will be eductional for all who read it.
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.
Back to top
View user's profile Send private message
expat
Intermediate


Joined: 01 Mar 2007
Posts: 475
Topics: 9
Location: Welsh Wales

PostPosted: Wed May 30, 2007 8:24 am    Post subject: Reply with quote

BLKSIZE=0 used to be the accepted method of telling the system to determine the BLKSIZE, but of course if the file was never opened it accepted BLKSIZE=0 and still does, and can cause problems - as above.

If the SMS environment is set up correctly then not specifying the BLKSIZE will let the system determine it and set it correctly.

BLKSIZE=0 also causes problems for us storage guys because HSM and the like will not process datasets with a BLKSIZE=0, except for scratching them at some future time.

Can be confusing for the ops support people as well, if they are looking for a backup of a dataset for a specific date and the backup doesn't exist because it had an invalid BLKSIZE and was bypassed by HSM, they start screaming at the storage guys and saying it's all our fault, which it isn't. Just try convincing them that it's their fault ....... Shocked

Happy hols - just finished my interview Razz
Back to top
View user's profile Send private message
Nic Clouston
Advanced


Joined: 01 Feb 2007
Posts: 1075
Topics: 7
Location: At Home

PostPosted: Wed May 30, 2007 8:31 am    Post subject: Reply with quote

Of course, any well written program opens and closes it's datasets first/last thing
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic   printer-friendly view    MVSFORUMS.com Forum Index -> Job Control Language(JCL) All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


MVSFORUMS
Powered by phpBB © 2001, 2005 phpBB Group