Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Multiple jobs submitted when compiling SQLRPGLE program

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Multiple jobs submitted when compiling SQLRPGLE program

    Check WDSC updates to see if you are at least 5.1.2.4.

  • #2
    Multiple jobs submitted when compiling SQLRPGLE program

    I'm now at 5.1.2.4 and I'm still getting two jobs. Any more ideas? Thanks.

    Comment


    • #3
      Multiple jobs submitted when compiling SQLRPGLE program

      I created my own command but I found this at IBM: SE19366 - WHEN RUNNING A CRTSQLRPGI COMMAND ON AN SQLRPGLE PROGRAM 2 COMPILES ARE SUBMITTED WHEN USING WDSC. APAR (Authorized Program Analysis Report) Abstract WHEN RUNNING A CRTSQLRPGI COMMAND ON AN SQLRPGLE PROGRAM 2 COMPILES ARE SUBMITTED WHEN USING WDSC. Error Description When running a CRTSQLRPGI command on an SQLRPGLE program 2 compile jobs are submitted when using WDSC. There should only be one job submitted, just like in the 5250 environment Problem Summary[*]************************************************** ************* * USERS AFFECTED: All users who compile SQL source on V5R3. * ************************************************** ************** * PROBLEM DESCRIPTION: The RSE was incorrectly compiling * * SQL programs twice on V5R3M0 iSeries * * hosts. * ************************************************** ************** * RECOMMENDATION: * ************************************************** ************** The compile support in WDSC incorrectly assumed that V5R3 hosts required two SQL compiles be submitted when the *EVENTF option is specified and a DBGVIEW option is other than *NONE is specified so that error messages are displayed in the iSeries Error List view. The first compile would specify the *EVENTF option with DBGVIEW(*NONE) in order to retrieve the error messages. The second compile would not specify *EVENTF and would specify the original DBGVIEW option. This is not required on V5R3 but is required on V5R1, due to SQL precompiler restrictions. Problem Conclusion This problem will be fixed in the next service of RSE after 5.1.2 Temporary Fix Comments Circumvention PTFs Available Affected Modules Affected Publications Summary Information Status............................................ CLOSED PER HIPER........................................... No Component.................................. 5722WDS82 Failing Module.......................... NONE Reported Release................... R512 Duplicate Of..............................

      Comment


      • #4
        Multiple jobs submitted when compiling SQLRPGLE program

        Thanks.

        Comment


        • #5
          Multiple jobs submitted when compiling SQLRPGLE program

          WDSc 5.1.2 820 V5R3 I have created a compile command for creating modules from ILE RPG SQL source as follows: CRTSQLRPGI OBJ(mylib/mypgm) SRCFILE(mylib/myfile) SRCMBR(mypgm) OBJTYPE(*MODULE) OPTION(*EVENTF) REPLACE(*YES) DBGVIEW(*SOURCE) TOSRCFILE(mylib/QSQLTEMP) When I compile a program 2 jobs are submitted: 1. CRTSQLRPGI OBJ(mylib/mypgm) SRCFILE(mylib/myfile) SRCMBR(mypgm) OBJTYPE(*MODULE) OPTION(*EVENTF) REPLACE(*YES) DBGVIEW(*NONE) TOSRCFILE(mylib/QSQLTEMP) 2. CRTSQLRPGI OBJ(mylib/mypgm) SRCFILE(mylib/myfile) SRCMBR(mypgm) OBJTYPE(*MODULE) OPTION(*NOEVENTF) REPLACE(*YES) DBGVIEW(*SOURCE) TOSRCFILE(mylib/QSQLTEMP) The only differences that I see is that #1 has OPTION(*EVENTF) DBGVIEW(*NONE) and #2 has OPTION(*NOEVENTF) DBGVIEW(*SOURCE). Does anyone have an idea what I've done to accomplish this feat? It doesn't seem to cause any problems, I just get two compile listings and chew up a few extra CPU cycles. Thanks, Dave

          Comment

          Working...
          X