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

How to solve S013 Abend?

IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message

New User

Joined: 08 Jun 2005
Posts: 4

PostPosted: Fri Jun 10, 2005 5:19 pm
Reply with quote


Could you please tell me what is S013 abend and how to solve this abend in mainframe.

Back to top
View user's profile Send private message

New User

Joined: 28 Apr 2005
Posts: 99

PostPosted: Fri Jun 10, 2005 5:44 pm
Reply with quote

It is member/module not found.

This is either a case of a missing control card element, or program element - a control card is not present in the library specified in the JCL. This can occur when a control card/module is promoted from one test environment to another. The resolution for this is to search the other levels of promotion for the correct element and use this library as a temporary fix - the JCL should be changed to reflect the move at a later date.

Check: S013 Abend

An error occurred in opening a data set because of conflicting or unspecified data set attributes. Possible causes: There was a conflict between the program, the JCL, and the data set label DCB information required. Some required DCB information was omitted. Directory space was not allocated for a partitioned data set. The BLKSIZE DCB sub-parameter was missing for a dummy data set. A specific member of a partitioned data set could not be located. For fixed block records, the LRECL=0, or the data set was empty. For fixed length records, the BLKSIZE was not a multiple of the LRECL. For variable length records, the blocksize was not four bytes greater than the logical record length. RECFM=F was specified and the logical record length was not the same as the block size. Solution: Check the DCB attributes of the problem data set and correct any inconsistencies. Check for inconsistencies between the program, the JCL, and the data set DCB characteristics. Verify that all the DCB information required for the data set is specified. Recreate the partitioned data set specifying a value for directory blocks in the space parameter. Specify a BLKSIZE that matches the program DCB information. Check the spelling for any programs to be executed. Verify that the appropriate STEPLIB data sets have been provided.
Back to top
View user's profile Send private message


Joined: 12 Mar 2005
Posts: 252
Location: India

PostPosted: Fri Jun 10, 2005 7:36 pm
Reply with quote

S013 --

--> Was greater than 32760 for a disk data set, or
was greater than the maximum block size supported
by the access method for a tape data set.

-->Was not an integer multiple of the LRECL
parameter for fixed-length records, or was not at
least four bytes longer than the LRECL for
variable-length records.
Back to top
View user's profile Send private message

New User

Joined: 07 Mar 2005
Posts: 4
Location: Chennai

PostPosted: Sun Jun 12, 2005 10:50 pm
Reply with quote

Hi Friends,

SO13: It is an open problem. Usually this ABEND occurs, When the program tries to read a member of PDS and the member is not found.

Ex: During compilation, If you code a non-existing member as source(SYSIN).

The S013 Abend occurs when the Program expects the DD to have a specific DCB, but the DD has a different DCB. Specify the correct DCB for the DD.
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 -> ABENDS & Debugging


Similar Topics
Topic Forum Replies
No new posts S722 abend and ESTAE ABENDS & Debugging 1
No new posts ABEND=04E FOR REASON=00E50013 DB2 4
No new posts Any idea about how to solve 3022 aben... IMS DB/DC 3
No new posts Handling abend to prevent termination CICS 0
No new posts Abend deletes last record written ABENDS & Debugging 10
Search our Forums:

Back to Top