Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
How to solve the ABEND=SB14 ?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging
View previous topic :: :: View next topic  
Author Message
Rajanikanthbachu Newjersy

New User


Joined: 22 Aug 2007
Posts: 2
Location: new jersy

PostPosted: Thu Aug 23, 2007 2:14 am    Post subject: How to solve the ABEND=SB14 ?
Reply with quote

Hi All,

Can you please let me know how to solve ABEND=SB14 ?

1) This problem is coming @ DB2 Precompilation.

Below is the Log:

IEC130I SYSTERM DD STATEMENT MISSING
IEC217I B14-0C,IGG0201Z,LP251241,DB2PRE,DBRMLIB,3063,LT0004
IEA995I SYMPTOM DUMP OUTPUT 490
SYSTEM COMPLETION CODE=B14 REASON CODE=0000000C
TIME=16.13.17 SEQ=16468 CPU=0000 ASID=015D
PSW AT TIME OF ERROR 075C1000 80E1BCDE ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00E1BCD8 - 41003846 0A0DB20A 00509808
GR 0: 00E1BEE8 1: A4B14000
2: 00108DC8 3: 00E1B6A2
4: 008C0410 5: 00E31000
6: 008C074C 7: 008C07A4
8: 008C076C 9: 008C1120
A: 008E5F68 B: 000EF9F0
C: 008C1120 D: 00000080
E: 00E1BB04 F: 0000000C

END OF SYMPTOM DUMP

Advance Thanks
Rajani icon_biggrin.gif
Back to top
View user's profile Send private message

superk

Moderator Team Head


Joined: 26 Apr 2004
Posts: 4650
Location: Raleigh, NC, USA

PostPosted: Thu Aug 23, 2007 2:23 am    Post subject: Reply to: How to solve the ABEND=SB14 ?
Reply with quote

What is with everyone today? Why won't posters at least look up the error and post the description text?

Quote:

IEC217I B14-rc,mod,jjj,sss, ddname[-#],dev,ser,dsname( member)



Explanation: The error occurred during processing of a CLOSE macro instruction for a partitioned data set opened for output to a member.
In the message text:


rc
Associates this message with system completion code B14 and with the return code.

jjj
The job name.

sss
The step name.

ddname[-#]
DDname (followed by a concatenation number if it is part of a concatenation and not the first DD statement in the concatenation).

dev
The device number.

ser
The volume serial number.

mod
The name of the module in which the error occurred.


| dsname(member)
The data set name. Member name if specified.


The explanation for the hex return code is as follows:

Return Code Explanation

04
A duplicate name was found in the directory of a partitioned data set. The CLOSE routine attempted to add a member name to the directory using the STOW macro instruction, but a code of 4 was returned, indicating that the member already exists. Specify a different member name, or remove the old member name using the IEHPROGM utility, or specify DISP=OLD on the DD statement.

08
The CLOSE routine attempted to update the directory of a partitioned data set; however, the TTRN value for that member was not within the extents in the DEB.

0C
The CLOSE routine attempted to update the directory of a partitioned data set; however, a code of 12 was returned by the STOW macro instruction, indicating that either there is no space left in the directory, or there is no space left in the data set (space in the data set is required for writing an end of file record).
If this IEC217I message was preceded by an IEC030I (ABEND B37), IEC031I (ABEND D37), or IEC032I (ABEND E37) message, then the interpretation of this IEC217I message should be out of space in the data set. If IEC217I is issued (with return code 0C) without one of the out of space messages, the interpretation should be out of space in the directory. In either case, to resolve the problem, copy the data set to a scratch volume, reallocate space for the data set specifying either more directory blocks or more space for the data set, and then copy it back using IEBCOPY.


10
An I/O error occurred trying to update the directory of a partitioned data set.

14
The CLOSE routine attempted to update the directory of a partitioned data set; however, the DCB of the partitioned data set was not open; or opened incorrectly. Make sure the DCB is open before issuing a CLOSE.

18
Unsuccessful GETMAIN for STOW work area when CLOSE routine attempted to update a partitioned data set. Specify a larger region and rerun the job.

1C
The STOW routine failed while creating an empty data member because the PDSE was already defined as a program object.

24
The CLOSE routine attempted to update the directory of a PDSE; however, STOW returned a return code of 36, indicating that it received an incorrect member token.

2C
The CLOSE routine attempted to update the directory of a PDSE; however, STOW returned a return code of 44, indicating that it received an error return code from a system service which is used with PDSE processing.

30
The CLOSE routine attempted to update the directory of a PDSE; however, STOW returned a return code of 48, indicating that it detected an inconsistent input parameter.


System Action: The task is ended unless the error is to be ignored as specified in the DCB ABEND exit routine.
Operator Response: Start a generalized trace facility (GTF) trace, and re-create the problem. Reply to message AHL100A with:




TRACE=SYS,USR,SLIP


On the DD statement for the data set in error, specify:



DCB=DIAGNS=TRACE


Application Programmer Response: Probable user error unless an I/O error has occurred. Correct the errors causing abnormal end as indicated by the return code in the message text. Then rerun the job.
If an I/O error has occurred, a defective volume or device may be the cause. Save the output from the failing job to aid in the analysis of the problem. Rerun the job specifying a different volume or device. If a scratch volume was being used when the I/O error occurred, request a different volume. If that does not solve the problem, request a different device in the UNIT parameter of the DD statement. If a specific volume is needed, try requesting a different device in the UNIT parameter of the DD statement. Rerun the job. For return code 08, the TTRN value can be found in the DCBRELAD field of the DCB. This value can be compared with the extent information contained in the DEB.

System Programmer Response: If the error recurs and the program is not in error, look at the messages in the job log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the SYSOUT output for the job.

Source: DFSMSdfp

Detecting Module: IGG0201B

Routing Code: 11

Descriptor Code: 6

Back to top
View user's profile Send private message
Rajanikanthbachu Newjersy

New User


Joined: 22 Aug 2007
Posts: 2
Location: new jersy

PostPosted: Thu Aug 23, 2007 3:41 am    Post subject: Re: Reply to: How to solve the ABEND=SB14 ?
Reply with quote

superk wrote:
What is with everyone today? Why won't posters at least look up the error and post the description text?

Quote:

IEC217I B14-rc,mod,jjj,sss, ddname[-#],dev,ser,dsname( member)



Explanation: The error occurred during processing of a CLOSE macro instruction for a partitioned data set opened for output to a member.
In the message text:


rc
Associates this message with system completion code B14 and with the return code.

jjj
The job name.

sss
The step name.

ddname[-#]
DDname (followed by a concatenation number if it is part of a concatenation and not the first DD statement in the concatenation).

dev
The device number.

ser
The volume serial number.

mod
The name of the module in which the error occurred.


| dsname(member)
The data set name. Member name if specified.


The explanation for the hex return code is as follows:

Return Code Explanation

04
A duplicate name was found in the directory of a partitioned data set. The CLOSE routine attempted to add a member name to the directory using the STOW macro instruction, but a code of 4 was returned, indicating that the member already exists. Specify a different member name, or remove the old member name using the IEHPROGM utility, or specify DISP=OLD on the DD statement.

08
The CLOSE routine attempted to update the directory of a partitioned data set; however, the TTRN value for that member was not within the extents in the DEB.

0C
The CLOSE routine attempted to update the directory of a partitioned data set; however, a code of 12 was returned by the STOW macro instruction, indicating that either there is no space left in the directory, or there is no space left in the data set (space in the data set is required for writing an end of file record).
If this IEC217I message was preceded by an IEC030I (ABEND B37), IEC031I (ABEND D37), or IEC032I (ABEND E37) message, then the interpretation of this IEC217I message should be out of space in the data set. If IEC217I is issued (with return code 0C) without one of the out of space messages, the interpretation should be out of space in the directory. In either case, to resolve the problem, copy the data set to a scratch volume, reallocate space for the data set specifying either more directory blocks or more space for the data set, and then copy it back using IEBCOPY.


10
An I/O error occurred trying to update the directory of a partitioned data set.

14
The CLOSE routine attempted to update the directory of a partitioned data set; however, the DCB of the partitioned data set was not open; or opened incorrectly. Make sure the DCB is open before issuing a CLOSE.

18
Unsuccessful GETMAIN for STOW work area when CLOSE routine attempted to update a partitioned data set. Specify a larger region and rerun the job.

1C
The STOW routine failed while creating an empty data member because the PDSE was already defined as a program object.

24
The CLOSE routine attempted to update the directory of a PDSE; however, STOW returned a return code of 36, indicating that it received an incorrect member token.

2C
The CLOSE routine attempted to update the directory of a PDSE; however, STOW returned a return code of 44, indicating that it received an error return code from a system service which is used with PDSE processing.

30
The CLOSE routine attempted to update the directory of a PDSE; however, STOW returned a return code of 48, indicating that it detected an inconsistent input parameter.


System Action: The task is ended unless the error is to be ignored as specified in the DCB ABEND exit routine.
Operator Response: Start a generalized trace facility (GTF) trace, and re-create the problem. Reply to message AHL100A with:




TRACE=SYS,USR,SLIP


On the DD statement for the data set in error, specify:



DCB=DIAGNS=TRACE


Application Programmer Response: Probable user error unless an I/O error has occurred. Correct the errors causing abnormal end as indicated by the return code in the message text. Then rerun the job.
If an I/O error has occurred, a defective volume or device may be the cause. Save the output from the failing job to aid in the analysis of the problem. Rerun the job specifying a different volume or device. If a scratch volume was being used when the I/O error occurred, request a different volume. If that does not solve the problem, request a different device in the UNIT parameter of the DD statement. If a specific volume is needed, try requesting a different device in the UNIT parameter of the DD statement. Rerun the job. For return code 08, the TTRN value can be found in the DCBRELAD field of the DCB. This value can be compared with the extent information contained in the DEB.

System Programmer Response: If the error recurs and the program is not in error, look at the messages in the job log for more information. Search problem reporting data bases for a fix for the problem. If no fix exists, contact the IBM Support Center. Provide the SYSOUT output for the job.

Source: DFSMSdfp

Detecting Module: IGG0201B

Routing Code: 11

Descriptor Code: 6




Hi all,

Thanks superk.

I have solved the issue, after compressing the DBRM Library. its working fine.

Regards
Rajani icon_biggrin.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> ABENDS & Debugging All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts C03 ABEND sjiraga PL/I & Assembler 1 Thu Jun 01, 2017 4:51 pm
No new posts IMS region inactive - User abend code... gthmrj IMS DB/DC 5 Tue Mar 07, 2017 12:29 pm
No new posts IMS BMP program causes 878 system abend Artemk IMS DB/DC 7 Tue Nov 22, 2016 8:26 pm
No new posts abend sort based on count records in ... anatol DFSORT/ICETOOL 5 Mon Oct 17, 2016 10:10 pm
No new posts hot to get details when "EXEC CI... Andi1982 CICS 11 Tue Sep 20, 2016 5:01 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us