Topic
17 replies Latest Post - ‏2013-09-06T12:47:11Z by Hsieh
hrobrod2
hrobrod2
91 Posts
ACCEPTED ANSWER

Pinned topic Z/OS cobol generation fails after installing new PTFS

‏2011-09-27T12:52:02Z |
RBD 8.0.1.1
TUI

The following PTF-s were installed in one apply job: UK60551,UK62413, UK69444

The only documented changes in ELA.SELASAMP were FDABPTCL procedure and ELAGRP.
Generation process reported errors when using FDAPCL and FDALINK procedures (messages are the same in both cases):

11/09/27 08:39:37
CCUI-015
The build job has been queued by the server. Position is 1.

11/09/27 08:39:39
CCUI-014
Job 'B2537650.JOB00702' has been started by the server.

11/09/27 08:39:40 CCUE-016 The build server terminated the build abnormally.

Recovery:

Examine the messages issued by the build server and
determine the cause.

11/09/27 08:39:40
CCUE-047
The DDName for the extension 'NORETURN' could not be determined.

CCUE-045
The MVS build 'fdalink' script was unsuccessfully parsed.
Determine if there are any syntax errors.
It seems that generation programs were changed and expected changed procedures too.
PTFS were restored and problem is cleared.
To open PMR?
Updated on 2011-10-13T08:14:07Z at 2011-10-13T08:14:07Z by hrobrod2
  • Hsieh
    Hsieh
    573 Posts
    ACCEPTED ANSWER

    Re: Z/OS cobol generation fails after installing new PTFS

    ‏2011-09-27T13:35:37Z  in response to hrobrod2
    Please, let me see the xxxxxx_cbl_Results.xml file.

    Hsieh
    • hrobrod2
      hrobrod2
      91 Posts
      ACCEPTED ANSWER

      Re: Z/OS cobol generation fails after installing new PTFS

      ‏2011-09-27T14:06:35Z  in response to Hsieh
      Hi Hsieh,

      we had to do restore and to generate failed programs as quickly as possible.
      Those generations overlapped existing listings in eglgener directory.
      Important messages from ....Results.xml are already shown.
      I doubt that other parts of that file would explain anything.
      After restore, generation process is flawless....but PTFs are waiting...

      Mladen
    • markevans
      markevans
      2759 Posts
      ACCEPTED ANSWER

      Re: Z/OS cobol generation fails after installing new PTFS

      ‏2011-09-27T14:16:00Z  in response to Hsieh
      Actually, can you attach your copy of FDALINK?

      NORETURN is usually associated with the listings (CCUEXTC, CCUEXTL, CCUEXTP, etc).

      And I think the message message means you set a value to a symbolic, but there was not a corresponding use of that symbolic in the script.

      So, I looked at the FDALINK we use (which should match the ones that are shipped out)

      
      Top of script 
      //              MBR=TEMPNAME,     
      //              RGN=4096K,        
      //              CCUEXTL=NORETURN, 
      //              AMODE=31,         
      //              RMODE=ANY,          JCL further down:   
      //*SYSLIN    DD  DISP=SHR,DSN=&CGHLQ..&SYSTEM..EZELED(&MBR)       
      //SYSLIN    DD  CCUEXT=LED,DISP=(NEW,DELETE),                     
      //    UNIT=SYSDA,SPACE=(TRK,(10,10)),                             
      //    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)                        
      //SYSLMOD  DD  DISP=SHR,DSN=&CGHLQ..&SYSTEM..LOAD(&MBR),ENQ=YES   
      //* RETURN LINK EDIT LISTING TO CLIENT AS FILE &PREFIX.L.SYSPRINT 
      //SYSPRINT DD  CCUEXT=&CCUEXTL,DISP=(NEW,DELETE),                 
      //    UNIT=VIO,SPACE=(TRK,(30,10)),                               
      //    DCB=(RECFM=FB,LRECL=133,BLKSIZE=6650)                       
      //*SYSPRINT DD  DISP=SHR,DSN=&CGHLQ..&SYSTEM..LINKLIST(&MBR),     
      //*             CCUEXT=&CCUEXTC,ENQ=YES                           
      //*SYSUDUMP DD  SYSOUT=&SOUT,DCB=BLKSIZE=13300                    
      //SYSUT1   DD  SPACE=(1024,(&WSPC,&WSPC)),UNIT=VIO
      


      As you can see, the uncommented SYSPRINT references CCUEXTL, so this should be ok. But the commented one still refers to CCUEXTC. So, if you uncommented out the lines with CCUEXTC, I think you would get this message.

      Please take a look.

      Also, I believe FDALINK is only used to create a load module for the form groups. (FM modules).
      • hrobrod2
        hrobrod2
        91 Posts
        ACCEPTED ANSWER

        Re: Z/OS cobol generation fails after installing new PTFS

        ‏2011-09-28T07:06:33Z  in response to markevans
        Yes, FDALINK is invoked as part of ZOSCICS application generation and is related to form group.
        The same problem is with FDAPCL for batch generation.

        Fdalink is attached.
        The only difference is CCUEXTL=CCUOUT instead of CCUEXTL=NORETURN.

        Procedure FDAPCL also has CCUEXTP,CCUEXTC,CCUEXTL,CCUEXTB all set to CCUOUT.

        Everything works as usual when PTFs are restored(removed).

        Attachments

        • Hsieh
          Hsieh
          573 Posts
          ACCEPTED ANSWER

          Re: Z/OS cobol generation fails after installing new PTFS

          ‏2011-09-28T12:31:39Z  in response to hrobrod2
          Mladen,

          on step UNLOAD, check if you have defined data sets for:

          //X IF &SYSTEM..EQ.ZOSCICS
          //EZEPPT DD DSN=&CGHLQ..&SYSTEM..EZEPPT,DISP=SHR,CCUEXT=PPT ... ELA.ZOSCICS.EZEPPT
          //EZEPCT DD DSN=&CGHLQ..&SYSTEM..EZEPCT,DISP=SHR,CCUEXT=PCT ... ELA.ZOSCICS.EZEPCT
          //X ENDIF

          Hsieh
          • markevans
            markevans
            2759 Posts
            ACCEPTED ANSWER

            Re: Z/OS cobol generation fails after installing new PTFS

            ‏2011-09-28T15:05:13Z  in response to Hsieh
            Mladen,

            I think you should go ahead and open a PMR as it sounds like something is not right.

            Along with that, can you attach a buildplan.xml for one of the ones that fails that invokes FDALINK and one that invokes FDAPCL (even one that works now..as what is passed up should be the same if you have not made any changes to your build descriptors).

            And either here or with the PMR, turning on the trace within the build job (spawned job) so that we can see what is being done internally as it parses the build scripts.
            • hrobrod2
              hrobrod2
              91 Posts
              ACCEPTED ANSWER

              Re: Z/OS cobol generation fails after installing new PTFS

              ‏2011-09-29T08:52:57Z  in response to markevans
              PTFs applied again, trace activated.
              Message is now different:

              The DDName for the extension 'LED' could not be determined.
              The MVS build 'fdalink' script was unsuccessfully parsed.

              Attached:
              ONLINE (FDALINK): BEAAVGFM_cbl_Results.xml
              BEAAVGFMBuildPlan.xml
              CICSJOB1,CICSJOB2,CISCJOB3,CICSJOB4

              BATCH: (FDAPCL): PULJAF_cbl_Results.xml
              PULJAFBuildPlan.xml
              BATCHJO1,BATCHJO2,BATCHJO3

              PTFs restored, failed applications generated successfully.

              Attachments

              • banerjee
                banerjee
                76 Posts
                ACCEPTED ANSWER

                Re: Z/OS cobol generation fails after installing new PTFS

                ‏2011-09-29T17:20:06Z  in response to hrobrod2
                Hi,
                I see error inthe build scripts FDALINK an FDAPCL.In these there are more than one ddname which contain CCUEXT=LED, so the buildsever
                cannot detrmine which one is to be used.

                Search for CCUEXT=LED in these scripts.

                FDABIND is fine

                Dev
                • hrobrod2
                  hrobrod2
                  91 Posts
                  ACCEPTED ANSWER

                  Re: Z/OS cobol generation fails after installing new PTFS

                  ‏2011-09-30T06:18:48Z  in response to banerjee
                  Hi,
                  agree with that but:
                  • previous version of parser program(s) doesn't have problem with that
                  • in the first attempt (different programs were generated) message was different:
                  CCUE-047
                  The DDName for the extension 'NORETURN' could not be determined
                  both procedures are attached for your review

                  Attachments

                  • markevans
                    markevans
                    2759 Posts
                    ACCEPTED ANSWER

                    Re: Z/OS cobol generation fails after installing new PTFS

                    ‏2011-10-05T19:51:10Z  in response to hrobrod2
                    Mladen,

                    We did make changes in UK60551 which caused dthe CCUE-047 to be issued if the build script contained more than one extension such as CCUEXT=LED was in your FDALINK and FDAPCL build scripts.

                    Previously, the build server tolerated this, but only honored the last specification of the extension which worked for you. But we had a case where it was not understood that duplicates meant only the "last" one would work, so we closed this hole in the build script parser.

                    That explains the LED message. We apologize for not having flagged this possible change to the scripts in the HOLD info of the PTF.

                    We don't understand why you would get a message related to NORETURN. With the fix to eliminate duplicates, the use of NORETURN in multiple places was flagged but should not have been. The CCUOUT, CCUSTD, NORETURN, etc (i.e. the one used for output) should ignore duplicates as they can be used in more than one CCUEXT in a script. So, PM22761 (also in UK60551) was to allow NORETURN to work as before.

                    We have had a couple of other customers also report a similar problem with NORETURN after applying this PTF, but when we ask for a trace, either the customer works around it or it "disappears"... so there is something that we cannot recreate or determine what is going wrong, but would like to resolve. If you (or anyone else) hits the problem, can you please open a PMR so that we can try to resolve it. We would need a trace of the build job (the one that is started by the build server)and the buildplan.xml (or results.xml) produced by the generate.

                    Thanks.
                    • hrobrod2
                      hrobrod2
                      91 Posts
                      ACCEPTED ANSWER

                      Re: Z/OS cobol generation fails after installing new PTFS

                      ‏2011-10-06T07:46:02Z  in response to markevans
                      Hi,
                      thanks for the explanation.
                      I will apply PTFs again and try to generate the same programs that had "NORETURN" message with build procedures unchanged (multiple CCUEXT=LED).
                      Different programs were generated after the second APPLY. Those programs had "LED" message.
                      Regards, Mladen
                      • hrobrod2
                        hrobrod2
                        91 Posts
                        ACCEPTED ANSWER

                        Re: Z/OS cobol generation fails after installing new PTFS

                        ‏2011-10-12T08:57:13Z  in response to hrobrod2
                        PTFs applied, and first generation ended with "noreturn".
                        Unfortunately in that moment CCUMVS procedure was not prepared for trace (CCURUNM was).
                        The next generations ended with duplicate LED message.
                        PTFs restored then reapplied, LED messages.
                        Z/OS restarted, PTFs applied, LED messages...

                        Now, PTFs are applied, procedures are corrected, and generations are going on as usual.
                        PMR will not be opened as I just missed to trace appearance of "noreturn".
                        Hope that "noreturn" appears only when procedure is in error. Otherwise we will see it again and deal with it when trace succeeds.

                        Regards, Mladen
                        • markevans
                          markevans
                          2759 Posts
                          ACCEPTED ANSWER

                          Re: Z/OS cobol generation fails after installing new PTFS

                          ‏2011-10-12T12:33:26Z  in response to hrobrod2
                          Mladen,

                          thanks so much for trying.

                          Just to be clear, the build scripts themselves were not changed in any attempt... Correct?

                          I will try again to recreate as well.
                          • hrobrod2
                            hrobrod2
                            91 Posts
                            ACCEPTED ANSWER

                            Re: Z/OS cobol generation fails after installing new PTFS

                            ‏2011-10-13T08:14:07Z  in response to markevans
                            Build scripts were not changed and had duplicate CCUEXT=LED usage.
                            From time to time I will also try with activating trace and reverting procedures to duplicate CCUEXT=LED.

                            Regards, Mladen
                            • NenadV
                              NenadV
                              47 Posts
                              ACCEPTED ANSWER

                              Re: Z/OS cobol generation fails after installing new PTFS

                              ‏2013-09-05T10:32:33Z  in response to hrobrod2

                              Hello,

                              the same problem here after applying maintenance :

                              SYSMOD   STATUS    TYPE  
                                                       
                              UK62413  APPLIED   PTF   
                                                       
                              UK69444  APPLIED   PTF   
                                                       
                              UK75483  APPLIED   PTF   
                                                       
                              UK79313  APPLIED   PTF   
                                                                             
                              UK81752  APPLIED   PTF   
                                                       
                              UK92032  APPLIED   PTF   
                                                       
                              UK94570  APPLIED   PTF   

                               

                              We use customized build scripts.

                              Output and the build script reported are attached.

                              Please let me know if you need anything else to resolve/diagnose this further.

                               

                              I have also raised PMR 37988,704,704 on this issue.

                              Regards,

                              Nenad

                               

                               

                              Attachments

                              Updated on 2013-09-05T10:40:18Z at 2013-09-05T10:40:18Z by NenadV
                              • This reply was deleted by Hsieh 2013-09-06T12:14:40Z. Reason for deletion: error
                              • Hsieh
                                Hsieh
                                573 Posts
                                ACCEPTED ANSWER

                                Re: Z/OS cobol generation fails after installing new PTFS

                                ‏2013-09-06T12:47:11Z  in response to NenadV

                                Hi Nenad,

                                Could you activate the build trace to find the error.

                                IBM Rational COBOL Runtime Program Directory, page 86.

                                5. The EDCENV input data set is used to provide optional variables. It can be set to DUMMY if there

                                are no options to be set. The only optional variable that can be set is for tracing.

                                To turn tracing on:

                                Create a sequential file with a Fixed Block (FB) record format and a record length (LRECL) of 80.

                                Replace the hlq.SOME.SEQ.FILE in the sample JCL with the name of this dataset and

                                uncomment out the line.

                                Comment out the line that associates EDCENV with DUMMY

                                Add the following line to the sequential dataset.

                                CCU_TRACE= *

                                The trace will be written to CCUBLOG.

                                 

                                Regard,

                                 

                                Hsieh

  • NenadV
    NenadV
    47 Posts
    ACCEPTED ANSWER

    Re: Z/OS cobol generation fails after installing new PTFS

    ‏2013-09-06T12:32:43Z  in response to hrobrod2

    Hello,

    we managed to solve the problem by following instructions to change the build script FDABCL given in the pmr:

    You have this in the upload step:                                       
                                                                            
                                                                            
                                                                            
    //UPLOAD EXEC PGM=IEFBR14                                               
    //*UNCOMMENT IF COBOL SOURCE AND LINK EDIT CMDS SHOULD BE SAVED         
    //EZESRC   DD  DSN=&CGHLQ..&SYSTEM..EZESRC,DISP=SHR,CCUEXT=CBL          
    //EZELED   DD  DSN=&CGHLQ..&SYSTEM..EZELED,DISP=SHR,CCUEXT=LED          
    //X    IF &SYSTEM..EQ.ZOSCICS                                           
    //EZEPPT   DD  DSN=&CGHLQ..ZOSCICS.EZEPPT,DISP=SHR,CCUEXT=PPT           
    //EZEPCT   DD  DSN=&CGHLQ..ZOSCICS.EZEPCT,DISP=SHR,CCUEXT=PCT           
    //X     ENDIF                                                           
                                                                            
                                                                            
                                                                            
    But in the "L" step, you are not referring to the "member" that you     
    uploaded to in the UPLOAD step.                                         
                                                                            
                                                                            
                                                                            
    //*SYSLIN    DD  DISP=SHR,DSN=&CGHLQ..&SYSTEM..EZELED(&MBR)             
    //SYSLIN    DD  CCUEXT=LED,DISP=(NEW,DELETE),                           
    //    UNIT=SYSDA,SPACE=(TRK,(10,10)),                                   
    //    DCB=(RECFM=FB,LRECL=80,BLKSIZE=3200)                              
                                                                            
                                                                            
                                                                            
    Try uncommenting out the SYSLIN to use the uploaded member in the PDS   
    and comment out the SYSLIN you are using now. (i.e the 3 lines).

    Thanks!

     

    Updated on 2013-09-06T12:36:56Z at 2013-09-06T12:36:56Z by NenadV