|
View previous topic :: View next topic
|
| Author |
Message |
santhunaveen
New User
Joined: 22 Sep 2006
Posts: 33
|
|
|
|
Hi,
While submitting a job using eztrieve program I got abend S213....can any one tell me how to resolve... |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
Please post the output showing the abend messages. S213 can be caused by a number of things, so until we see what you see, we can not help.
Have you looked in the messages and codes manuals to see what the abend code means ? |
|
| Back to top |
|
|
santhunaveen
New User
Joined: 22 Sep 2006
Posts: 33
|
|
|
|
My output is showing like this,
ABEND=S213 U0000 REASON=00000004
SYSTEM COMPLETION CODE=213 REASON CODE=00000004
TIME=05.45.41 SEQ=28237 CPU=0000 ASID=0082
PSW AT TIME OF ERROR 075C1000 80DD06AE ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00DD06A8 - 41003B62 0A0D41F0 38A656F0
GR 0: 00DD0974 1: A4213000
2: 000064C0 3: 00DCFE12
4: 009BB388 5: 009BB71C
6: 009BB6C4 7: 009BB71C
8: 009BB6E4 9: 009C5DF0
A: 00DD21C2 B: 00DD2B04
C: 80DD2BE4 D: 009BB648
E: 80DCFF4A F: 00000004
END OF SYMPTOM DUMP |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8796
Location: Welsh Wales
|
|
|
|
| Quote: |
Explanation: The error occurred during processing of an OPEN macro
instruction for a direct access device. This system completion code
is accompanied by message IEC143I. Refer to the explanation of message
IEC143I for complete information about the task that was ended and for
an explanation of the return code (rc in the message text) in register
15.
Source: DFSMSdfp
Application Programmer Response: Respond as indicated to the
applicable message.
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 JCL and the program listing for the job.
|
|
|
| Back to top |
|
|
cpuhawg
Active User
Joined: 14 Jun 2006
Posts: 331
Location: Jacksonville, FL
|
|
|
|
| A S213-04 abend is caused by the disk dataset you are attempting to READ being unavailable. It can be caused by specifying the VOLSER that a dataset resides on and it is NOT on that volume. It can also be caused by the master catalogue. If the master catalogue indicates the dataset is on a specific VOLSER, the job runs, looks to the VOLSER for the dataset, and it's not there. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
The S213 abend occurs due to the following reasons:
Dataset Name Incorrect: The dataset name specified in the program or job control language (JCL) is incorrect, misspelled, or does not match an existing dataset.
Dataset Not Allocated: The dataset has not been allocated or created before the program or job attempts to access it.
Permissions Issue: The program or job does not have the necessary permissions or access rights to the dataset.
Dataset Deleted or Moved: The dataset was deleted or moved from its original location, making it inaccessible to the program or job.
To resolve the S213 abend, you can take the following steps:
Verify Dataset Name: Double-check the dataset name specified in your program or JCL to ensure it is correct and matches the actual dataset you intend to access.
Allocate Dataset: Ensure that the dataset is allocated or created before your program or job attempts to access it. You can allocate datasets using JCL DD statements or by using utility programs like IDCAMS or IEFBR14.
Permissions and Access: Make sure that your program or job has the necessary permissions and access rights to read, write, or modify the dataset as required.
Check Dataset Status: Verify that the dataset exists and is available for access. If the dataset was recently moved or deleted, update your program or JCL accordingly.
Review Job or Program Logic: Check your job or program logic to ensure there are no logical errors or assumptions causing the dataset not found issue.
If you post your jcl and the part of the first JES sysout file that is for this step, we will be better able to offer suggestions. |
|
| Back to top |
|
|
cvishu
Active User
Joined: 31 Jul 2007
Posts: 136
Location: india
|
|
|
|
These are a few possible reasons for S213 Abend
S213 DSCB not found; I/O error in reading or writing DSCB. Possible causes:
the data set is not the specified volume
DISP=MOD is not compatible with a volume reference
incorrect tape positioning.
S213-04 An I/O error occurred reading the FORMAT 1 DSCB, or the FORMAT 1 DSCB could not be found on the first volume specified by the DD statement volume serial field.
S213-08 An OPEN macro was issued for a password protected dataset but the system was unable to locate the password dataset.
S213-0C An I/O error occurred reading a FORMAT 1 DSCB for a direct or indexed sequential dataset, or the FORMAT 1 DSCB could not be found on the volume specified by the DD statement.
S213-18 An I/O error occurred writing back a FORMAT 1 DSCB.
S213-20 During an open, a volume contained more than 16 extends of the indicated dataset. Try browsing or editing the file via SPF 3.4. Check the upper right-most corner of the ISPF panel for an indicator message.
S213-28 An OPEN macro ws issued for a direct access dataset specifying UNIT=SYSDA, but the UNIT already contained 127 users, whcih is the maximum allowed. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix
|
|
|
|
Hello,
Please be aware that you have replied to a topic that has been inactive for almost 9 months. . . |
|
| Back to top |
|
|
|
|
