Program works fine in JCL but not when imbedded in a PROC
in [Cobol]
|
Prev: Cobol syntax highlighting
Next: Disassembler
From: CHSB on 20 Feb 2006 12:01 I am having a problem where my COBOL programs do not work when located inside a PROC but execute fine when submitted as normal JCL. I looks like the problem is with overlaid storage because I get errors like USER-ABEND CODE 4083 and SEGMENT TRANSLATION EXCEPTION depending on which program I run. I even commented out all of the code on one program except one display statement and still get the error. My thought is that when the JCL is inside a PROC that the system doesn't allocate the proper storage for the program and it ends up writing over storage. I tried modifying the SIZE parameter on the EXEC PGM=.... statement to add an extra meg of storage but still get the same error. Is there anyway to specify a size when executing the PROC itself or does anyone have any ideas as to how I might fix this error? Thanks Chris
From: Arnold Trembley on 20 Feb 2006 15:31 CHSB wrote: > I am having a problem where my COBOL programs do not work when located > inside a PROC but execute fine when submitted as normal JCL. I looks > like the problem is with overlaid storage because I get errors like > USER-ABEND CODE 4083 and SEGMENT TRANSLATION EXCEPTION depending on > which program I run. I even commented out all of the code on one > program except one display statement and still get the error. My > thought is that when the JCL is inside a PROC that the system doesn't > allocate the proper storage for the program and it ends up writing over > storage. I tried modifying the SIZE parameter on the EXEC PGM=.... > statement to add an extra meg of storage but still get the same error. > Is there anyway to specify a size when executing the PROC itself or > does anyone have any ideas as to how I might fix this error? > > Thanks > > Chris > Please post examples of both the JCL version and the PROC version. The PROC version should include the JCL that invokes the PROC. One possibility is that your JCL includes JOBLIB DD statements that are missing from the PROC version. -- http://arnold.trembley.home.att.net/
From: Robert Jones on 20 Feb 2006 15:35 CHSB wrote: > I am having a problem where my COBOL programs do not work when located > inside a PROC but execute fine when submitted as normal JCL. I looks > like the problem is with overlaid storage because I get errors like > USER-ABEND CODE 4083 and SEGMENT TRANSLATION EXCEPTION depending on > which program I run. I even commented out all of the code on one > program except one display statement and still get the error. My > thought is that when the JCL is inside a PROC that the system doesn't > allocate the proper storage for the program and it ends up writing over > storage. I tried modifying the SIZE parameter on the EXEC PGM=.... > statement to add an extra meg of storage but still get the same error. > Is there anyway to specify a size when executing the PROC itself or > does anyone have any ideas as to how I might fix this error? > > Thanks > > Chris Hello Chris Conceptually there is no reason why they shouldn't run in a PROC. Though you don't specify it, I presume you are running under some flavour of IBM MVS. It usually helps to specify the hardware, operating system and compiler version in use. In this case, you should review the PROC JCL expansion, which can be obtained with MSGLEVEL(1,1) on the JOB card. This should tell you what options are being set from within the PROC and you can hopefully resolve the problem yourself from there, if not come back to us with the details of the parameters set within the PROC that differ from those you have set yourself in the plain JCL version that works. Robert
From: Howard Brazee on 20 Feb 2006 15:50 On Mon, 20 Feb 2006 20:31:20 GMT, Arnold Trembley <arnold.trembley(a)worldnet.att.net> wrote: >Please post examples of both the JCL version and the PROC version. >The PROC version should include the JCL that invokes the PROC. One >possibility is that your JCL includes JOBLIB DD statements that are >missing from the PROC version. That makes sense. Try replacing the JOBLIB statements with STEPLIB statements.
From: CG on 20 Feb 2006 19:39
Howard Brazee wrote: > On Mon, 20 Feb 2006 20:31:20 GMT, Arnold Trembley > <arnold.trembley(a)worldnet.att.net> wrote: > >> Please post examples of both the JCL version and the PROC version. >> The PROC version should include the JCL that invokes the PROC. One >> possibility is that your JCL includes JOBLIB DD statements that are >> missing from the PROC version. > > That makes sense. Try replacing the JOBLIB statements with STEPLIB > statements. JOBLIB and STEPLIB are identical in function. The only difference is the scope of the statement. Arnold's comment, I believe, is more a case of there either is a xxxLIB statement or there is not one applicable when the program runs or does not run. JCL is JCL: There is no combination of valid JCL that cannot be created via a PROC. You just need to be sure, for example, when you are doing an override that you are overriding the specific statement in the specific step that you intend. So, the specific JESn messages will be very key in diagnosing your problem. BTW, tell us which JESn are you running along with the other environmental info Arnold mentioned such as compiler, MVS-OS/390-z/OS release, etc. |