IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 8 replies
  • Latest Post - ‏2013-03-09T08:38:13Z by SystemAdmin
aisheikh
aisheikh
4 Posts

Pinned topic Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

‏2011-05-11T17:16:36Z |
I am using RDz 8.0.1 client on x86 Linux and am unable to get the COBOL tutorials to work. I am following the "Running a simple COBOL application on a remote system" tutorial. I cannot succeed in the 'Rebuild SubProject step'.

The tutorial contains two COBOL files: PRINTAPP.cbl and STARTAPP.cbl where the latter is nominated as the entry point. When I try to 'Rebuild subproject', a JCL kicks off on the remote host and I do see that PRINTAPP is successfully compiled. RDz client seems to get some valid compile xml result back, as I can see an informational message from the compiler (IGYOS4096-I) regarding PRINTAPP. However, at this point an error dialog with CRRZI0514E pops up ("..verify that the JCL procedure on the host has the error feedback compile option to support this option").

STARTAPP is never compiled.

I have consulted these forums for that problem and found some possible issues, none of which are happening in my scenario.

1. https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14576117&#14576117

I am not passing any custom options to the COBOL compiler, and do not have the 'append compiler options to the parm card' selected.
I have verified in the job output that the compiler is getting the EXIT and ADATA options.

2. https://www.ibm.com/developerworks/forums/thread.jspa?threadID=369106&tstart=0
I have verified that the z/OS FileSystem mapping is
**XML xml text IBM-1047 UTF8 (inherited)
There is no higher priority rule that matches XML files.

FYI: this is the XML error log:
<PACKAGE>
<FILEREFERENCETABLE>
<FILECOUNT>1</FILECOUNT>
<FILE>
<FILENUMBER>1</FILENUMBER>
<FILENAME>ASHEIKH.REMOTE.COBOL(PRINTAPP)</FILENAME>
</FILE>
</FILEREFERENCETABLE>
<MESSAGE>
<MSGNUMBER>IGYOS4069-I</MSGNUMBER>
<MSGLINE>1</MSGLINE>
<MSGFILE>1</MSGFILE>
<MSGTEXT>
Some suboptions specified i
</MSGTEXT>
</MESSAGE>
</PACKAGE>

The above seems just normal.

What mystefies me is why is one file compiled successfully and not the other? Its clear that the compiler feedback is working properly, so why do I get the CRRZI0514E error?
Updated on 2013-03-09T08:38:13Z at 2013-03-09T08:38:13Z by SystemAdmin
  • asrudd
    asrudd
    70 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2011-05-12T04:27:54Z  
    The rebuild subproject creates a job that runs on the remote system (this job should have two compilation steps and a bind step). Have you looked at the SDSF output to see why the second program is not compiled.
  • aisheikh
    aisheikh
    4 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2011-05-12T14:59:14Z  
    • asrudd
    • ‏2011-05-12T04:27:54Z
    The rebuild subproject creates a job that runs on the remote system (this job should have two compilation steps and a bind step). Have you looked at the SDSF output to see why the second program is not compiled.
    The job created by "rebuild subproject" has only one compile step.

    1 //ASHEIKH1 JOB , JOB01206
    // MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=144M,COND=(16,LT)
    2 //MYLIB JCLLIB ORDER=ASHEIKH.CNTL.JCL
    //*
    3 //STP0000 EXEC PROC=ELAXFCOC,
    // CICS=,
    // DB2=,
    // COMP=
    XX*********************************************************************
    XX* Licensed materials - Property of IBM *
    XX* 5724-T07 © Copyright IBM Corp. 2003, 2009 *
    XX* All rights reserved *
    XX* US Government users restricted rights - Use, duplication or *
    XX* disclosure restricted by GSA ADP schedule contract with IBM Corp. *
    XX* *
    XX* Rational Developer for System z *
    XX* Procedure for COBOL compiles. This procedure is also used to *
    XX* do integrated 'CICS translate' and 'DB2 co-process' for COBOL *
    XX* programs having EXEC CICS or EXEC SQL statements. *
    XX* *
    XX* *
    XX* Customize this procedure to match your site requirements. *
    XX* Do not change procedure or step names however, unless you *
    XX* reflect those changes on all RD/z clients. *
    XX* *
    XX* 1) Modify the LNGPRFX value to the high level qualifier of your *
    XX* COBOL libraries. Default value is 'IGY.V4R1M0'. *
    XX* *
    XX* 2) Modify the LODPRFX value to the high level qualifier of your *
    XX* RD/z libraries. Default value is 'FEK'. *
    XX* *
    XX* 3) If the level of COBOL compiler, CICS and DB2 installed at your *
    XX* site supports integrated CICS translate and DB2 co-process, *
    XX* - uncomment the CICPRFX and DB2PRFX procedure parameters *
    XX* - provide correct high level qualifier values for them *
    XX* defaults are CICSTS32.CICS and DSN810, respectively *
    XX* - uncomment the corresponding DD statements in the STEPLIB *
    XX* concatenation *
    XX* *
    XX* Note(s): *
    XX* *
    XX* 1. SYSIN, SYSLIN, SYSLIB and SYSADATA DD cards will be provided *
    XX* by the generated code. *
    XX* *
    XX* 2. Do not modify the variables &CICS, &DB2 and &COMP. These are *
    XX* used by the generated code to provide appropriate parms when *
    XX* using integrated CICS translate, DB2 co-process or syntax *
    XX* check operations. *
    XX* *
    XX* 3. The parameters 'EXIT(ADEXIT(ELAXMGUX)),ADATA' are required *
    XX* for population of the task list on the client and for error *
    XX* feedback of any COBOL compile, integrated CICS translate or *
    XX* DB2 co-process. *
    XX* *
    XX*********************************************************************
    4 XXELAXFCOC PROC LNGPRFX='SHARE.IGY410',
    XX* CICPRFX='CICSTS32.CICS',
    XX* DB2PRFX='DSN810',
    XX LODPRFX='SHARE.RDZ801'
    XX*
    5 XXCOBOL EXEC PGM=IGYCRCTL,REGION=2048K,
    XX PARM=('EXIT(ADEXIT(ELAXMGUX))',
    XX 'ADATA',
    XX 'LIB',
    XX 'TEST(NONE,SEP)',
    XX 'LIST',
    XX 'FLAG(I,I)'&CICS&DB2&COMP)
    IEFC653I SUBSTITUTION JCL - PGM=IGYCRCTL,REGION=2048K,PARM=('EXIT(ADEXIT(ELAXMGUX))','ADATA','LIB','TEST(NONE,
    SEP)','LIST','FLAG(I,I)')
    6 XXSTEPLIB DD DISP=SHR,
    XX DSN=&LNGPRFX..SIGYCOMP
    IEFC653I SUBSTITUTION JCL - DISP=SHR,DSN=SHARE.IGY410.SIGYCOMP
    7 XX DD DISP=SHR,
    XX DSN=&LODPRFX..SFEKLOAD
    XX* DD DISP=SHR,
    XX* DSN=&CICPRFX..SDFHLOAD
    XX* DD DISP=SHR,
    XX* DSN=&DB2PRFX..SDSNLOAD
    IEFC653I SUBSTITUTION JCL - DISP=SHR,DSN=SHARE.RDZ801.SFEKLOAD
    8 //COBOL.SYSIN DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.COBOL(PRINTAPP)
    X/SYSIN DD DUMMY
    9 //COBOL.SYSLIN DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.OBJECT(PRINTAPP)
    X/SYSLIN DD DUMMY
    10 //COBOL.SYSLIB DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.COPYLIB
    X/SYSLIB DD DUMMY
    11 XXSYSADATA DD DUMMY
    12 //SYSPRINT DD SYSOUT=*
    X/SYSPRINT DD SYSOUT=*
    13 XXSYSUT1 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    14 XXSYSUT2 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    15 XXSYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    16 XXSYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    17 XXSYSUT5 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    18 XXSYSUT6 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    19 XXSYSUT7 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    XX*
    20 //COBOL.SYSDEBUG DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.SYSDEBUG(PRINTAPP)
    21 //COBOL.SYSXMLSD DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z943219.XML,
    // DISP=SHR
    22 //COBOL.WSEDSF1 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z834043.XML,
    // DISP=SHR
    23 //COBOL.WSEDSF2 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z723363.XML,
    // DISP=SHR
    24 //COBOL.WSEDSF3 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z629222.XML,
    // DISP=SHR
    25 //COBOL.WSEDSF4 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z447445.XML,
    // DISP=SHR
    26 //SYSOUT DD SYSOUT=*
    27 //SYSIN DD *
    28 XXS99 EXEC PGM=IEBGENER
    29 XXSYSPRINT DD DUMMY
    30 XXSYSIN DD DUMMY
    31 XXSYSUT1 DD DSN=*.COBOL.SYSXMLSD,DISP=OLD
    32 XXSYSUT2 DD SYSOUT=*
    //*
    //******* ADDITIONAL JCL FOR COMPILE HERE ******
    33 //
    STMT NO. MESSAGE
    3 IEFC001I PROCEDURE ELAXFCOC WAS EXPANDED USING PRIVATE LIBRARY ASHEIKH.CNTL.JCL
  • lilcubby
    lilcubby
    5 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2011-05-24T21:17:32Z  
    • aisheikh
    • ‏2011-05-12T14:59:14Z
    The job created by "rebuild subproject" has only one compile step.

    1 //ASHEIKH1 JOB , JOB01206
    // MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=144M,COND=(16,LT)
    2 //MYLIB JCLLIB ORDER=ASHEIKH.CNTL.JCL
    //*
    3 //STP0000 EXEC PROC=ELAXFCOC,
    // CICS=,
    // DB2=,
    // COMP=
    XX*********************************************************************
    XX* Licensed materials - Property of IBM *
    XX* 5724-T07 © Copyright IBM Corp. 2003, 2009 *
    XX* All rights reserved *
    XX* US Government users restricted rights - Use, duplication or *
    XX* disclosure restricted by GSA ADP schedule contract with IBM Corp. *
    XX* *
    XX* Rational Developer for System z *
    XX* Procedure for COBOL compiles. This procedure is also used to *
    XX* do integrated 'CICS translate' and 'DB2 co-process' for COBOL *
    XX* programs having EXEC CICS or EXEC SQL statements. *
    XX* *
    XX* *
    XX* Customize this procedure to match your site requirements. *
    XX* Do not change procedure or step names however, unless you *
    XX* reflect those changes on all RD/z clients. *
    XX* *
    XX* 1) Modify the LNGPRFX value to the high level qualifier of your *
    XX* COBOL libraries. Default value is 'IGY.V4R1M0'. *
    XX* *
    XX* 2) Modify the LODPRFX value to the high level qualifier of your *
    XX* RD/z libraries. Default value is 'FEK'. *
    XX* *
    XX* 3) If the level of COBOL compiler, CICS and DB2 installed at your *
    XX* site supports integrated CICS translate and DB2 co-process, *
    XX* - uncomment the CICPRFX and DB2PRFX procedure parameters *
    XX* - provide correct high level qualifier values for them *
    XX* defaults are CICSTS32.CICS and DSN810, respectively *
    XX* - uncomment the corresponding DD statements in the STEPLIB *
    XX* concatenation *
    XX* *
    XX* Note(s): *
    XX* *
    XX* 1. SYSIN, SYSLIN, SYSLIB and SYSADATA DD cards will be provided *
    XX* by the generated code. *
    XX* *
    XX* 2. Do not modify the variables &CICS, &DB2 and &COMP. These are *
    XX* used by the generated code to provide appropriate parms when *
    XX* using integrated CICS translate, DB2 co-process or syntax *
    XX* check operations. *
    XX* *
    XX* 3. The parameters 'EXIT(ADEXIT(ELAXMGUX)),ADATA' are required *
    XX* for population of the task list on the client and for error *
    XX* feedback of any COBOL compile, integrated CICS translate or *
    XX* DB2 co-process. *
    XX* *
    XX*********************************************************************
    4 XXELAXFCOC PROC LNGPRFX='SHARE.IGY410',
    XX* CICPRFX='CICSTS32.CICS',
    XX* DB2PRFX='DSN810',
    XX LODPRFX='SHARE.RDZ801'
    XX*
    5 XXCOBOL EXEC PGM=IGYCRCTL,REGION=2048K,
    XX PARM=('EXIT(ADEXIT(ELAXMGUX))',
    XX 'ADATA',
    XX 'LIB',
    XX 'TEST(NONE,SEP)',
    XX 'LIST',
    XX 'FLAG(I,I)'&CICS&DB2&COMP)
    IEFC653I SUBSTITUTION JCL - PGM=IGYCRCTL,REGION=2048K,PARM=('EXIT(ADEXIT(ELAXMGUX))','ADATA','LIB','TEST(NONE,
    SEP)','LIST','FLAG(I,I)')
    6 XXSTEPLIB DD DISP=SHR,
    XX DSN=&LNGPRFX..SIGYCOMP
    IEFC653I SUBSTITUTION JCL - DISP=SHR,DSN=SHARE.IGY410.SIGYCOMP
    7 XX DD DISP=SHR,
    XX DSN=&LODPRFX..SFEKLOAD
    XX* DD DISP=SHR,
    XX* DSN=&CICPRFX..SDFHLOAD
    XX* DD DISP=SHR,
    XX* DSN=&DB2PRFX..SDSNLOAD
    IEFC653I SUBSTITUTION JCL - DISP=SHR,DSN=SHARE.RDZ801.SFEKLOAD
    8 //COBOL.SYSIN DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.COBOL(PRINTAPP)
    X/SYSIN DD DUMMY
    9 //COBOL.SYSLIN DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.OBJECT(PRINTAPP)
    X/SYSLIN DD DUMMY
    10 //COBOL.SYSLIB DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.COPYLIB
    X/SYSLIB DD DUMMY
    11 XXSYSADATA DD DUMMY
    12 //SYSPRINT DD SYSOUT=*
    X/SYSPRINT DD SYSOUT=*
    13 XXSYSUT1 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    14 XXSYSUT2 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    15 XXSYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    16 XXSYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    17 XXSYSUT5 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    18 XXSYSUT6 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    19 XXSYSUT7 DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
    XX*
    20 //COBOL.SYSDEBUG DD DISP=SHR,
    // DSN=ASHEIKH.REMOTE.SYSDEBUG(PRINTAPP)
    21 //COBOL.SYSXMLSD DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z943219.XML,
    // DISP=SHR
    22 //COBOL.WSEDSF1 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z834043.XML,
    // DISP=SHR
    23 //COBOL.WSEDSF2 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z723363.XML,
    // DISP=SHR
    24 //COBOL.WSEDSF3 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z629222.XML,
    // DISP=SHR
    25 //COBOL.WSEDSF4 DD DSN=ASHEIKH.REMOTE.ERRLOG.PRINTAPP.Z447445.XML,
    // DISP=SHR
    26 //SYSOUT DD SYSOUT=*
    27 //SYSIN DD *
    28 XXS99 EXEC PGM=IEBGENER
    29 XXSYSPRINT DD DUMMY
    30 XXSYSIN DD DUMMY
    31 XXSYSUT1 DD DSN=*.COBOL.SYSXMLSD,DISP=OLD
    32 XXSYSUT2 DD SYSOUT=*
    //*
    //******* ADDITIONAL JCL FOR COMPILE HERE ******
    33 //
    STMT NO. MESSAGE
    3 IEFC001I PROCEDURE ELAXFCOC WAS EXPANDED USING PRIVATE LIBRARY ASHEIKH.CNTL.JCL
    The fact that you are getting an error message after the first compile possibly indicates the properties for STARTAPP.cbl may not be right - were any of the properties overridden for STARTAPP ? Especially - is any of the separate pre-process steps for CICS or DB2 enabled ?
  • MelFowler
    MelFowler
    4 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2011-05-24T22:50:45Z  
    Hello Aisheikh,

    The main problem here seems to be that the compile step for StartApp was never generated.

    1) Do you have both PrintApp and StartApp in the same subProject?
    2) Do you have a property group associated with the subProject where both PrintApp and StartApp reside.
    3) Have you selected Nominate as Entry Point on StartApp? Did the icon change for StartApp?
    4) Can you generate JCL for compile for StartApp? Right click on StartApp in the subProject, and and select Generate JCL -> for Compile. You will be prompted for a dataset for the generated JCL if you have not already specified it on the JCL tab of your property group.
    5) Are you able to right click on StartApp, and select Syntax Check ->Remote Syntax Check?
    As far as the message box asking for the error feedback options, this messae pops up when an error feedback XML file is expected, but not available. One of the things that will cause this will be if the error feedback compile options are not specified on a build. There was a recent fix that went into our last fixpack, which will add the error feedback options if you are performing a subproject build. But specifying the error feedback options in the property group will also get around this.

    Thanks,

    Mel
  • aisheikh
    aisheikh
    4 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2011-05-30T13:58:42Z  
    • lilcubby
    • ‏2011-05-24T21:17:32Z
    The fact that you are getting an error message after the first compile possibly indicates the properties for STARTAPP.cbl may not be right - were any of the properties overridden for STARTAPP ? Especially - is any of the separate pre-process steps for CICS or DB2 enabled ?
    > "were any of the properties overridden for STARTAPP ? Especially - is any of the separate pre-process steps for CICS or DB2 enabled ?"

    No, and no.

    I am basically following the Remote COBOL tutorial, as it ships with RDz.
  • aisheikh
    aisheikh
    4 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2011-05-30T14:06:22Z  
    • MelFowler
    • ‏2011-05-24T22:50:45Z
    Hello Aisheikh,

    The main problem here seems to be that the compile step for StartApp was never generated.

    1) Do you have both PrintApp and StartApp in the same subProject?
    2) Do you have a property group associated with the subProject where both PrintApp and StartApp reside.
    3) Have you selected Nominate as Entry Point on StartApp? Did the icon change for StartApp?
    4) Can you generate JCL for compile for StartApp? Right click on StartApp in the subProject, and and select Generate JCL -> for Compile. You will be prompted for a dataset for the generated JCL if you have not already specified it on the JCL tab of your property group.
    5) Are you able to right click on StartApp, and select Syntax Check ->Remote Syntax Check?
    As far as the message box asking for the error feedback options, this messae pops up when an error feedback XML file is expected, but not available. One of the things that will cause this will be if the error feedback compile options are not specified on a build. There was a recent fix that went into our last fixpack, which will add the error feedback options if you are performing a subproject build. But specifying the error feedback options in the property group will also get around this.

    Thanks,

    Mel
    > The main problem here seems to be that the compile step for StartApp was never generated.

    I agree. I suspect this is a bug in the client, or a deficiency in the "Remote COBOL Tutorial".

    > 1) Do you have both PrintApp and StartApp in the same subProject?

    Yes. Both show up underneath the "RemoteCOBOLSample" zOS subproject.

    > 2) Do you have a property group associated with the subProject where both PrintApp and StartApp reside.

    Yes, as per the tutorial, I have "SamplePropGroup" associated with my RemoveCOBOLSample subproject. I verified this is the case by going to RemoteCOBOLSample->Properties->Property Group. "SamplePropGroup" is listed and enabled.

    > 3) Have you selected Nominate as Entry Point on StartApp? Did the icon change for StartApp?

    Yes. The icon changed to one with a red ticky-mark.

    > 4) Can you generate JCL for compile for StartApp? Right click on StartApp in the subProject, and and select Generate JCL -> for Compile. You will be prompted for a dataset for the generated JCL if you have not already specified it on the JCL tab of your property group.

    I generated the JCL for compile. It runs successfully with RC 0.

    > 5) Are you able to right click on StartApp, and select Syntax Check ->Remote Syntax Check?

    Yes. The JCL runs successfully, with RC 0.

    > As far as the message box asking for the error feedback options, this messae pops up when an error feedback XML file is expected, but not available. One of the things that will cause this will be if the error feedback compile options are not specified on a build. There was a recent fix that went into our last fixpack, which will add the error feedback options if you are performing a subproject build. But specifying the error feedback options in the property group will also get around this

    I saw this listed as a possibility in one of the other threads in the forum. I DO NOT think this is the cause of my woes -- I have verified that the XML feedback is indeed generated for PrintApp.

    For some reason, the RDz client is not generating the JCL for BOTH files when I try to do a "RebuildSubProject". However, I think it still expects XML for both files. The feedback never comes for the second file, hence the error message.
  • SystemAdmin
    SystemAdmin
    1086 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2013-03-09T06:22:19Z  
    • aisheikh
    • ‏2011-05-30T14:06:22Z
    > The main problem here seems to be that the compile step for StartApp was never generated.

    I agree. I suspect this is a bug in the client, or a deficiency in the "Remote COBOL Tutorial".

    > 1) Do you have both PrintApp and StartApp in the same subProject?

    Yes. Both show up underneath the "RemoteCOBOLSample" zOS subproject.

    > 2) Do you have a property group associated with the subProject where both PrintApp and StartApp reside.

    Yes, as per the tutorial, I have "SamplePropGroup" associated with my RemoveCOBOLSample subproject. I verified this is the case by going to RemoteCOBOLSample->Properties->Property Group. "SamplePropGroup" is listed and enabled.

    > 3) Have you selected Nominate as Entry Point on StartApp? Did the icon change for StartApp?

    Yes. The icon changed to one with a red ticky-mark.

    > 4) Can you generate JCL for compile for StartApp? Right click on StartApp in the subProject, and and select Generate JCL -> for Compile. You will be prompted for a dataset for the generated JCL if you have not already specified it on the JCL tab of your property group.

    I generated the JCL for compile. It runs successfully with RC 0.

    > 5) Are you able to right click on StartApp, and select Syntax Check ->Remote Syntax Check?

    Yes. The JCL runs successfully, with RC 0.

    > As far as the message box asking for the error feedback options, this messae pops up when an error feedback XML file is expected, but not available. One of the things that will cause this will be if the error feedback compile options are not specified on a build. There was a recent fix that went into our last fixpack, which will add the error feedback options if you are performing a subproject build. But specifying the error feedback options in the property group will also get around this

    I saw this listed as a possibility in one of the other threads in the forum. I DO NOT think this is the cause of my woes -- I have verified that the XML feedback is indeed generated for PrintApp.

    For some reason, the RDz client is not generating the JCL for BOTH files when I try to do a "RebuildSubProject". However, I think it still expects XML for both files. The feedback never comes for the second file, hence the error message.
    I have a similar problem when I am trying to rebuild this sample remote project, I am getting error msg that the

    00.47.35 JOB04362 ---- SATURDAY, 09 MAR 2013 ----
    00.47.35 JOB04362 IRR010I USERID SUS0115 IS ASSIGNED TO THIS JOB.
    00.47.35 JOB04362 IEFC452I SUS01151 - JOB NOT RUN - JCL ERROR 660

    JES2 JOB STATISTICS
    69 CARDS READ
    182 SYSOUT PRINT RECORDS
    0 SYSOUT PUNCH RECORDS
    8 SYSOUT SPOOL KBYTES
    0.00 MINUTES EXECUTION TIME
    ############################################################################
    That the job was not run, my doubt is on the point 5.d
    when it says specify the remote library name in the PROCS statement of the JOB card.
    Can someone please help on how I can specify the remote library location on the job card.Please.
  • SystemAdmin
    SystemAdmin
    1086 Posts

    Re: Compiler error feedback problem (CRRZI0514E) with RDz 8.0.1

    ‏2013-03-09T08:38:13Z  
    I have a similar problem when I am trying to rebuild this sample remote project, I am getting error msg that the

    00.47.35 JOB04362 ---- SATURDAY, 09 MAR 2013 ----
    00.47.35 JOB04362 IRR010I USERID SUS0115 IS ASSIGNED TO THIS JOB.
    00.47.35 JOB04362 IEFC452I SUS01151 - JOB NOT RUN - JCL ERROR 660

    JES2 JOB STATISTICS
    69 CARDS READ
    182 SYSOUT PRINT RECORDS
    0 SYSOUT PUNCH RECORDS
    8 SYSOUT SPOOL KBYTES
    0.00 MINUTES EXECUTION TIME
    ############################################################################
    That the job was not run, my doubt is on the point 5.d
    when it says specify the remote library name in the PROCS statement of the JOB card.
    Can someone please help on how I can specify the remote library location on the job card.Please.
    You do not specify the JCL or where the error is in the JCL
    REgarding your question, if I understood correctly, you need a JCL statement like this

    //MYPROCS JCLLIB ORDER=<mylibrary>

    where mylibrary should be your ELAXF* RDZ procedure JCLs.

    This must be coded in the property group under tab JCL job card, like this exasmple
    //DAVISV8 JOB ,
    // MSGCLASS=H,MSGLEVEL=(1,1),TIME=(,4),REGION=70M,COND=(16,LT)
    //ANYNAME JCLLIB ORDER=(RDZ810.#CUST.PROCLIB)