IBM Mainframe Forum

[fornanthakumar]

Hi,

I have JCL like below,

Select all

1. //YBEQFTPD JOB (034G000,SF),SBEQ,CLASS=H,       
2. //         MSGCLASS=I,NOTIFY=YBEQ,             
3. //         RESTART=*                           
4. //********************************************************
5. //*                                                                    *
6. //SBEQFTPD EXEC SBEQFTPD   

When this JCL submitted in Production environment , it ABENDed with Continuation not received in line 6 as we have non-blank character at 72nd column in 5th line.

But when i was executing the same JCL in test environment it was not ABENDed. Why ? Is there any system installation check at background or JES2 or JES3..
because i can assume it may expect any JES2 or JES3 command as its blank from 4th column but.. you have to answer me..

FYI : My JOB submitted in JES2 for processing.

[dick scherrer]

Hello,

There is probably more in the sysout that we would need to see in order to help.

The same jcl works fine on my system. . .

[steve-myers]

If you look at line 5 you will find a character at the far right, possibly in column 72. If it is in column 72, that indicates line 6 is a continuation, not a new JCL statement, and that could well be the problem. Was it really the same JCL?

[Anuj Dhawan]

But when i was executing the same JCL in test environment it was not ABENDed. Why ? Is there any system installation check at background or JES2 or JES3..

To answer the "why" - you got to prove that both the Jobs were same. Post the SYSOUT of failed job as Dick has asked for. On the other hand, there are intellignet JCL-syntax check tool in market now and they flag it as an error if there is some-character in 72nd column. e.g.: This

Select all

=COLS> ----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
000005 // JCLLIB ORDER=(HLQ.SLQ.PROCLIB.NEW)                                  *
==MSG> // JCLLIB ORDER=(HLQ.SLQ.PROCLIB.NEW)                               
==MSG> CAY6020E EXPECTED CONTINUATION NOT RECEIVED                             

flagged me an error, though such syntax-check-tools vary shop-to-shop with good differences, so to have a look on the SYSOUT of your failed is the only thing I can think of can help us to help you.

[NicC]

I doubt if the same JCL was submitted in a production environment - different RACF authorities, HLQs etc. so the JCL would have to have been altered in some respect.

[fornanthakumar]

Thanks for all your replies. The mistake is from my side. The actuall error had occured in different line for the same reason as mentioned by anuj dhawan.

[dick scherrer]

Good to hear it is working - thank you for letting us know

d