Antwort: Abend S0C7 in PL1 program

2007-05-24 Thread Werner Kuehnel
Michael, do you have a dataset with SUBSYS=LAM (CA-LIBRARIAN masterfile) in your JCL? Werner Kuehnel IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU schrieb am 23.05.2007 21:03:00: Good day! One of our programs written in PL1 recently encountered a S0C7 abend. In the course of our

Re: Antwort: Abend S0C7 in PL1 program

2007-05-24 Thread Bulent Dulger (Garanti Teknoloji)
Technology - Istanbul TURKEY -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Werner Kuehnel Sent: Thursday, May 24, 2007 9:18 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Antwort: Abend S0C7 in PL1 program Michael, do you have a dataset with SUBSYS=LAM

Re: Abend S0C7 in PL1 program

2007-05-24 Thread Shmuel Metz (Seymour J.)
In [EMAIL PROTECTED], on 05/23/2007 at 02:03 PM, Michael Tutor [EMAIL PROTECTED] said: One of our programs written in PL1 recently encountered a S0C7 abend. Try adding some debug code, starting with ON ERROR SNAP. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see

Re: Abend S0C7 in PL1 program

2007-05-24 Thread Michael Tutor
I appreciate all of the replies and suggestions. It gives me something to check and try out. Did I mention that I am trying to learn PL1 in the process? :-) Speaking of PL1: http://ars.userfriendly.org/cartoons/?id=20040226mode=classic Best regards, michael

Abend S0C7 in PL1 program

2007-05-23 Thread Michael Tutor
Good day! One of our programs written in PL1 recently encountered a S0C7 abend. In the course of our investigation, we noticed that this abend only happens when the job runs on certain systems in our sysplex. If we run the job in CPU1, it will run ok but using the same JCL and run it on

Re: Abend S0C7 in PL1 program

2007-05-23 Thread Fletcher, Kevin
Michael, We had a similar problem, but this was cobol and S0C4. The program would run fine on one system and abend on the other (different boxes), then it would go away and come back (sometimes, not always the same box) after an IPL. After one IPL the program would not run on either and forced

Re: Abend S0C7 in PL1 program

2007-05-23 Thread Thompson, Steve
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Tutor Sent: Wednesday, May 23, 2007 2:03 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Abend S0C7 in PL1 program Good day! One of our programs written in PL1 recently encountered a S0C7 abend

Re: Abend S0C7 in PL1 program

2007-05-23 Thread McKown, John
-Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Tutor Sent: Wednesday, May 23, 2007 2:03 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Abend S0C7 in PL1 program Good day! One of our programs written in PL1 recently encountered

Re: Abend S0C7 in PL1 program

2007-05-23 Thread Mark Zelden
On Wed, 23 May 2007 14:03:00 -0500, Michael Tutor [EMAIL PROTECTED] wrote: Any ideas on what else we can check or what could be causing this abend? The dump would be a good place to start. ;-) If you have no dump, have the systems folks set a SLIP for you and /or IBM. Mark -- Mark Zelden

Re: Abend S0C7 in PL1 program

2007-05-23 Thread Howard Brazee
On 23 May 2007 12:13:07 -0700, [EMAIL PROTECTED] (Fletcher, Kevin) wrote: We had a similar problem, but this was cobol and S0C4. The program would run fine on one system and abend on the other (different boxes), then it would go away and come back (sometimes, not always the same box) after an

Re: Abend S0C7 in PL1 program

2007-05-23 Thread Michael Tutor
Thanks for the suggestions! We do have a copy of the S0C7 dump which contains the module name. We are also in the process of obtaining the compile listing so that we can make sense of the dump :-) I checked the virtual storage map per Steve's suggestion and the private area below and above

Re: Abend S0C7 in PL1 program

2007-05-23 Thread Bob Rutledge
Check the Language Environment STORAGE option. Bob Michael Tutor wrote: Thanks for the suggestions! We do have a copy of the S0C7 dump which contains the module name. We are also in the process of obtaining the compile listing so that we can make sense of the dump :-) I checked the