Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

S213 Abend in Compile

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> COBOL Programming
View previous topic :: :: View next topic  
Author Message
silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 5:37 pm    Post subject: S213 Abend in Compile
Reply with quote

Hi Guys,

I am getting S213 error in the below code...

This is for testing the cobol compiler that i am trying to create.

Please find the below code. Can somebody help me with this?

//CQA1COMP JOB (999X999,DS),CQA1,CLASS=C,MSGCLASS=V,NOTIFY=CQA1,
// USER=CQA1
//COBOL EXEC PGM=IGYCRCTL,PARM='NODBCS,NSYMBOL(DBCS)'
//STEPLIB DD DISP=SHR,DSN=SYS1.SIGYCOMP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DSN=CQA1.MASTER.CPY,DISP=SHR
//SYSIN DD DSNAME=CQA1.MASTER.SRC(CASBTST1),DISP=SHR
//SYSLIN DD DSNAME=CQA1.MASTER.LOAD(CASBTST1),DISP=(MOD,PASS),
// SPACE=(TRK,(3,3)),DCB=(BLKSIZE=0)
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT5 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT6 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT7 DD UNIT=SYSDA,SPACE=(CYL,(1,1))

Error Message
----------------

SYSTEM COMPLETION CODE=213 REASON CODE=0000003C
TIME=14.06.14 SEQ=06180 CPU=0000 ASID=01CF
PSW AT TIME OF ERROR 075C1000 80D89C1A ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00D89C14 - 4100302C 0A0D010D A7E50126
AR/GR 0: A2B8C47A/00D89ED8 1: 00000000/A4213000
2: 00000000/00013ED4 3: 00000000/00D89EAC
4: 00000000/009B0410 5: 00000000/009B07A4
6: 00000000/009B074C 7: 00000000/009B07A4
8: 00000000/009B076C 9: 00000000/009BD038
A: 00000000/009B9AF0 B: 00000000/00000000
C: 00000000/00000080 D: 00000000/000000C0
E: 00000000/80D894AC F: 00000000/0000003C
END OF SYMPTOM DUMP
IEF472I CQA1COMP COBOL - COMPLETION CODE - SYSTEM=213 USER=0000 REASON=0000003C
Back to top
View user's profile Send private message

silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 5:39 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

The cobol code that I am trying to run looks like the below.

000100*PROCESS OPTIMIZE,LIST,NOOFFSET
000200 IDENTIFICATION DIVISION.
000300 PROGRAM-ID. CASBTST1.
000500 AUTHOR. PROBE TEAM.
000700 DATE-WRITTEN. JULY 2007.
000900 DATE-COMPILED. 00/00/00.
020200 PROCEDURE DIVISION.
DISPLAY 'HELLO WORLD'.
STOP RUN.
Back to top
View user's profile Send private message
Naish

New User


Joined: 07 Dec 2006
Posts: 82
Location: UK

PostPosted: Thu Jun 07, 2012 5:43 pm    Post subject:
Reply with quote

Search S213 on the forum.
Back to top
View user's profile Send private message
silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 5:58 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

Already searched. Found teh below answers but did not succeed.

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.

However, Dataset is accessible. So, thought of asking you guys some help...
Back to top
View user's profile Send private message
Craq Giegerich

Senior Member


Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA

PostPosted: Thu Jun 07, 2012 6:16 pm    Post subject: Re: Reply to: COBOL program compilaton problem
Reply with quote

silentarya wrote:
Hi Guys,

I am getting S213 error in the below code...

This is for testing the cobol compiler that i am trying to create.

Please find the below code. Can somebody help me with this?
Error Message
----------------

SYSTEM COMPLETION CODE=213 REASON IEF472I CQA1COMP COBOL - COMPLETION CODE - SYSTEM=213 USER=0000 REASON=0000003C


How are we suppose to know what the compiler you are trying to write is doing?
A compiler is not a simple project, why do you thing you need to write your own compiler?

Quote:
000100*PROCESS OPTIMIZE,LIST,NOOFFSET
000200 IDENTIFICATION DIVISION.
000300 PROGRAM-ID. CASBTST1.
000500 AUTHOR. PROBE TEAM.
000700 DATE-WRITTEN. JULY 2007.
000900 DATE-COMPILED. 00/00/00.
020200 PROCEDURE DIVISION.
DISPLAY 'HELLO WORLD'.
STOP RUN.


Is it a little strange to have sequence numbers on some lines and not on others?
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Thu Jun 07, 2012 6:21 pm    Post subject:
Reply with quote

Also, are we single threaded? How does the question from silentarya relate to the original question in this thread?
Back to top
View user's profile Send private message
silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 6:30 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

1. I don't think I am going to explain why i am trying to do?

2. A COBOL Compile JCL is a very small thing that people do on a daily basis.

3. I think This is a forum where we are trying to go beyond the day to day work and share our technical skills which i don't have today to fix this S213. Hence i have put it in the forum.

4. If you need any more info to get a solution, Kindly let me know.

5. If you don't understand what i am asking or not interested in replying, please refrain from asking why without giving any answers and at least don't reply craps.
Back to top
View user's profile Send private message
silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 6:31 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

You ar right Anuj. This was related to compiler. So, I added onto it.

Not sure if it would have been better if i would have created a new thread.
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2502
Location: Atlanta, Georgia, USA

PostPosted: Thu Jun 07, 2012 6:32 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

Shouldn't CBL be specified for compile overrides and not *PROCESS?
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Thu Jun 07, 2012 6:33 pm    Post subject:
Reply with quote

For the love of all that is holy and good in this world, please tell me this was some sort of grammar problem:
Quote:

This is for testing the cobol compiler that i am trying to create.


To me, this reads that you are trying to write your own COBOL compiler. However, the earlier posts (from a different userid) make it seem like they are trying to create a COBOL program and are having trouble with the IBM compiler accepting the code.

BTW, when I get S213, it's usually because the member isn't there in the PDS I specified. Check to make sure the name of the member is actually what you think it is.
Back to top
View user's profile Send private message
silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 6:34 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

@Anuj,


I think i pasted the word Compiler in the beginning which might cause confusion. It is not a compiler rather just a simple cimplie JCL for compiling a COBOL Program.


Apologies for the same ...
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Thu Jun 07, 2012 6:36 pm    Post subject:
Reply with quote

Bill: section 2.1.5.1 of the Enterprise COBOL Programming Guide manual indicates PROCESS and CBL can be used interchangeably.
Back to top
View user's profile Send private message
silentarya

New User


Joined: 11 Mar 2007
Posts: 35
Location: Chennai

PostPosted: Thu Jun 07, 2012 6:42 pm    Post subject: Reply to: COBOL program compilaton problem
Reply with quote

Hi Guys,

Just to re iterate... Do you see any error in the below compile JCL as I am getting the errors S213 for a simple Cobol code during compilation.

//CQA1COMP JOB (999X999,DS),CQA1,CLASS=C,MSGCLASS=V,NOTIFY=CQA1,
// USER=CQA1
//COBOL EXEC PGM=IGYCRCTL,PARM='NODBCS,NSYMBOL(DBCS)'
//STEPLIB DD DISP=SHR,DSN=SYS1.SIGYCOMP
//SYSPRINT DD SYSOUT=*
//SYSLIB DD DSN=CQA1.MASTER.CPY,DISP=SHR
//SYSIN DD DSNAME=CQA1.MASTER.SRC(CASBTST1),DISP=SHR
//SYSLIN DD DSNAME=CQA1.MASTER.LOAD(CASBTST1),DISP=(MOD,PASS),
// SPACE=(TRK,(3,3)),DCB=(BLKSIZE=0)
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT5 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT6 DD UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT7 DD UNIT=SYSDA,SPACE=(CYL,(1,1))


Error Message
----------------

SYSTEM COMPLETION CODE=213 REASON CODE=0000003C
TIME=14.06.14 SEQ=06180 CPU=0000 ASID=01CF
PSW AT TIME OF ERROR 075C1000 80D89C1A ILC 2 INTC 0D
NO ACTIVE MODULE FOUND
NAME=UNKNOWN
DATA AT PSW 00D89C14 - 4100302C 0A0D010D A7E50126
AR/GR 0: A2B8C47A/00D89ED8 1: 00000000/A4213000
2: 00000000/00013ED4 3: 00000000/00D89EAC
4: 00000000/009B0410 5: 00000000/009B07A4
6: 00000000/009B074C 7: 00000000/009B07A4
8: 00000000/009B076C 9: 00000000/009BD038
A: 00000000/009B9AF0 B: 00000000/00000000
C: 00000000/00000080 D: 00000000/000000C0
E: 00000000/80D894AC F: 00000000/0000003C
END OF SYMPTOM DUMP
IEF472I CQA1COMP COBOL - COMPLETION CODE - SYSTEM=213 USER=0000 REASON=0000003C

Thanks,
Debidatta
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 7913
Location: Bellevue, IA

PostPosted: Thu Jun 07, 2012 6:45 pm    Post subject:
Reply with quote

Arya, besides hijacking a thread, I see at least three problems with your posted JCL:
1) SYSLIN in the COBOL step points to an object library, not a load library. An object library is RECFM=FB,LRECL=80 whereas a load library is RECFM=U with no LRECL
2) Where's your linkage editor / binder step to convert the compiler output (the object code) into a load module?
3) DISP=(MOD,PASS) on a PDS member is NOT a good idea. It will work the first time you compile the program, but after that it will fail since the member must not exist for DISP=MOD to work (when you specify the member name in the JCL).
Back to top
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Thu Jun 07, 2012 7:00 pm    Post subject:
Reply with quote

Hello,

Your topic has been split into a new topic with a title that relates to your question. As you have been here 5 you would know that a new question should begin a new topic. . .

Is there some reason you did not post the ddname/dsn of the dataset that caused the s213?

What business reason is ther for you to try to create your own compile jcl? This is unaccepted in every organization i've supported and is cause for termination in some organizations.

Your code should never cause the compiler to experience an s213 . . .
Back to top
View user's profile Send private message
pawasthi

New User


Joined: 08 Mar 2010
Posts: 15
Location: India

PostPosted: Fri Jun 08, 2012 3:42 pm    Post subject:
Reply with quote

S213 - 3C - WHEN OPENING A PDSE THE RECFM IN THE DCB WAS DIFFERENT FROM THE RECFM ALREADY IN THE FORMAT-1 DSCB IN THE VTOC.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1738
Location: Bloomington, IL

PostPosted: Fri Jun 08, 2012 4:04 pm    Post subject:
Reply with quote

pawasthi wrote:
S213 - 3C - WHEN OPENING A PDSE THE RECFM IN THE DCB WAS DIFFERENT FROM THE RECFM ALREADY IN THE FORMAT-1 DSCB IN THE VTOC.

You realize that Mr. Sample told you the reason he wrote
Quote:
SYSLIN in the COBOL step points to an object library, not a load library. An object library is RECFM=FB,LRECL=80 whereas a load library is RECFM=U with no LRECL
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 -> COBOL Programming All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts I can not compile my program PL1 V3.R... Miguel Fernandez PL/I & Assembler 13 Tue Dec 06, 2016 8:30 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 COBOL 5 Compile oerdgie COBOL Programming 3 Thu Oct 06, 2016 6:14 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
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us