Topic
  • 5 replies
  • Latest Post - ‏2012-03-26T15:01:41Z by SystemAdmin
SystemAdmin
SystemAdmin
849 Posts

Pinned topic JCL processing error introduced into V6.0.0.2

‏2011-06-30T14:06:28Z |
Thought I'd better mention this, in case it hasn't been spotted already. I have a "stand-alone sandbox" system running V6.0.0.2, but as we were in the middle of our Project, our Production Server is still on V6.0.0.0. Processing the same components does throw up anomalies between the 2 versions. I have just discovered one I wasn't expecting!

A JOB with 3 PROCS processes fine under V6.0.0.0. Looking at the results for the identical JOB + 3 PROCS in V6.0.0.2 shows the JOB in Error. Looking at the line in the PROC stated as giving the error, it looks fine. To be absolutely sure, I processed the JOB on the mainframe LPAR with ProJCL - there is nothing wrong with the JOB's JCL.

Let me know if this is already known about, and being addressed in V6.0.0.3, which I understand is being worked upon
Updated on 2012-03-26T15:01:41Z at 2012-03-26T15:01:41Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: JCL processing error introduced into V6.0.0.2

    ‏2011-06-30T17:34:32Z  
    There is a fix for JCL Parsing Error when a symbolic is at the end of the statement coming in 6.0.0.3, ex:
    220. //SORTOU01 DD DSN=&S.SORT1,
    221. // DISP=(NEW,KEEP),
    222. // &YSORT

    Does that sound like what you have?
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: JCL processing error introduced into V6.0.0.2

    ‏2011-07-04T14:36:04Z  
    There is a fix for JCL Parsing Error when a symbolic is at the end of the statement coming in 6.0.0.3, ex:
    220. //SORTOU01 DD DSN=&S.SORT1,
    221. // DISP=(NEW,KEEP),
    222. // &YSORT

    Does that sound like what you have?
    Apologies for the delay in getting back, this actually looks like a different, new error, viz:

    // IF (&CALLSTEP..CU093020.RC NE 0) THEN
    //CU093025 EXEC PGM=EXECFAIL,
    // PARM='ABEND STEP CU093020,RETCODE NE 0 - SEE CUNEP'
    // ENDIF
    : RC=0 TYPE=JCL DMH1471I: Error found in CUP0930 at line 59
    2: RC=8 TYPE=JCL DMH1316E: Expected parameter continuation not found
    3: RC=8 TYPE=LOAD JOB record is missing
    The EXEC statement in the PROC is line 59, there is nothing wrong with the JCL, everything resolves on the mainframe in ProJCL, no error is reported in V6.0.0.0, it's definitely a V6.0.0.2 new bug. Hopefully removed in V6.0.0.3?
  • jcdelmo
    jcdelmo
    366 Posts

    Re: JCL processing error introduced into V6.0.0.2

    ‏2011-07-06T17:18:10Z  
    Apologies for the delay in getting back, this actually looks like a different, new error, viz:

    // IF (&CALLSTEP..CU093020.RC NE 0) THEN
    //CU093025 EXEC PGM=EXECFAIL,
    // PARM='ABEND STEP CU093020,RETCODE NE 0 - SEE CUNEP'
    // ENDIF
    : RC=0 TYPE=JCL DMH1471I: Error found in CUP0930 at line 59
    2: RC=8 TYPE=JCL DMH1316E: Expected parameter continuation not found
    3: RC=8 TYPE=LOAD JOB record is missing
    The EXEC statement in the PROC is line 59, there is nothing wrong with the JCL, everything resolves on the mainframe in ProJCL, no error is reported in V6.0.0.0, it's definitely a V6.0.0.2 new bug. Hopefully removed in V6.0.0.3?
    Yes, this is a regression in v6.0.0.2 - I have duplicated with v6.0.0.2 and tested the correction in both v6.0.0.3 and the next development driver.

    The issue was a change in the proper detection of the text 'THEN' in an IF statement when symbolic substition is present.

    Thank you for bringing this to our attention.
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: JCL processing error introduced into V6.0.0.2

    ‏2012-03-12T15:58:21Z  
    • jcdelmo
    • ‏2011-07-06T17:18:10Z
    Yes, this is a regression in v6.0.0.2 - I have duplicated with v6.0.0.2 and tested the correction in both v6.0.0.3 and the next development driver.

    The issue was a change in the proper detection of the text 'THEN' in an IF statement when symbolic substition is present.

    Thank you for bringing this to our attention.
    I am getting the same error in V 6.0.0.7

    1: RC=0 TYPE=JCL DMH1471I: Error found in SVROBLKP at line 1
    2: RC=8 TYPE=JCL DMH1380E: Illegal statement in procedure
    3: RC=8 TYPE=LOAD JOB record is missing

    When removed the line number in col 73 to 80, I am getting the following error

    1: RC=0 TYPE=JCL DMH1471I: Error found in SVROBLKP at line 1
    2: RC=8 TYPE=JCL DMH1380E: Illegal statement in procedure
    3: RC=8 TYPE=LOAD JOB record is missing

    Its a simple JCL calling PROC. PROC also has only one step.
    Request you to provide a solution for this issue.
  • SystemAdmin
    SystemAdmin
    849 Posts

    Re: JCL processing error introduced into V6.0.0.2

    ‏2012-03-26T15:01:41Z  
    I am getting the same error in V 6.0.0.7

    1: RC=0 TYPE=JCL DMH1471I: Error found in SVROBLKP at line 1
    2: RC=8 TYPE=JCL DMH1380E: Illegal statement in procedure
    3: RC=8 TYPE=LOAD JOB record is missing

    When removed the line number in col 73 to 80, I am getting the following error

    1: RC=0 TYPE=JCL DMH1471I: Error found in SVROBLKP at line 1
    2: RC=8 TYPE=JCL DMH1380E: Illegal statement in procedure
    3: RC=8 TYPE=LOAD JOB record is missing

    Its a simple JCL calling PROC. PROC also has only one step.
    Request you to provide a solution for this issue.
    Sihab, your question will be handled in a separate discussion thread:

    http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14805125