View previous topic :: View next topic
|
Author |
Message |
t1nt1n
New User
Joined: 08 Jul 2005 Posts: 31
|
|
|
|
hi
Wats S0c13 error ??? can someone throw some light on this ? |
|
Back to top |
|
|
thanooz
New User
Joined: 28 Jun 2005 Posts: 99
|
|
|
|
hi
it is member not found.
thanooz |
|
Back to top |
|
|
shivashunmugam Muthu
Active User
Joined: 22 Jul 2005 Posts: 114 Location: Chennai
|
|
|
|
Thanooz,
please explain elaborate...as i never heard of this abend before....where & when/ what scnario this abend wud occur... |
|
Back to top |
|
|
vamseepotti
New User
Joined: 21 Oct 2003 Posts: 45
|
|
|
|
Hi ,
I know about S013 not S0C 13 . If it is S013 Member not found in the data set which we specified in the JCL.
Vamsee. |
|
Back to top |
|
|
shivashunmugam Muthu
Active User
Joined: 22 Jul 2005 Posts: 114 Location: Chennai
|
|
|
|
I have got some clues
A TCP/IP application may generate an S0C13-C0 abend from a socket() call or perhaps another type of TCP/IP function call.
This may be caused by one of two reasons:
The userid does not have read access to /etc/resolv.conf
The PATHOPTS parameter (e.g., PATHOPTS=ORDONLY) is NOT coded on the DD statement. PATHOPTS is used only with HFS files and specifies the access and status for the HFS file named in the PATH parameter.
//DD1 DD PATH='/usr/applics/filename',PATHOPTS=ORDONLY
To prevent the abend, ensure the userid has read access to etc/resolv.conf and/or the PATHOPTS parameter is coded on the DD statement. |
|
Back to top |
|
|
SHIVAREDDY
New User
Joined: 25 Jul 2005 Posts: 20
|
|
|
|
HI,
I found 2 possible reasons for that error.Look for the first reason,if its not look at the second one which contains all possible reasons:
1.For COBOL, the file name or DDNAME parameter of the SELECT or ASSIGN statement was incorrect.
2. For COBOL: - DISPLAY was used for COBOL messages, but the message data set was missing. Supply a message data set DD statement. (See the discussion of MSGDDN in z/OS DFSORT Application Programming Guide for an alternative solution.) - An attempt was made to reopen an open data set, or a data set was already open prior to executing the SORT USING statement. - A STOP RUN or GOBACK statement was required but not supplied; therefore, the COBOL program did not exit as intended but processed the next instruction. - Invalid logic was used in a sort I/O procedure (possibly using the STOP RUN, GOBACK, CALL, or GO TO statements), or PERFORM referred to a paragraph outside the section. - The file name or DDNAME parameter of the SELECT/ASSIGN statement was incorrect. - The LINKAGE SECTION was specified incorrectly or misplaced. - The PROCEDURE DIVISION USING statement gave an invalid parameter list. - An attempt was made to move data from the COBOL SD area prior to execution of the SORT verb. - The FD entry RECORD CONTAINS clause (LRECL) for the USING data set is different than the SD entry RECORD CONTAINS clause for the SORTWK data set. |
|
Back to top |
|
|
shivashunmugam Muthu
Active User
Joined: 22 Jul 2005 Posts: 114 Location: Chennai
|
|
|
|
hey...
S013 nt for member nt found in PDS. It occurs when u missed to mention directory blocks in SPACE parameter for a PDS |
|
Back to top |
|
|
|