Welcome to the SRP Forum! Please refer to the SRP Forum FAQ post if you have any questions regarding how the forum works.

v3.4.6 install SRP_EDITOR_SERVICES

2»

Comments

  • I am now stumped.
    I checked and changed the OI configuration settings on clean to my dev copy.
  • edited December 20
    Ok, stae-of-the nation

    Made a copy of my dev system 10.2.3 b2 with srpeditor 3.4.7.1
    Copied to laptop
    Copied SYSENV records from clean to the laptop OI10
    Still compile error.
    Found on my laptop a srpEditor version 3.4.4.3 and installed that
    Compiled NO ERRORS
    Installed SRPEditor 3.4.7.1
    Compiled GOT VNAV WARNING ERRORS

    OK, so Now What!!!
  • Fiddling and installed 3.4.7.1 which maybe the editor proc di8d not update.
    About shows
    EDitor 3.4.7.1
    ocx 3.4.6.12

    Comp OK.

    But now with another copy I cant reproduce!!!!!!!!!!!
  • Barry - Perhaps check a few things:
    • Are there any instances of SRP object records that happen to be in your local application?
    • Is there a copy of $BLINT in your local application?
    • What is the datetime stamp of your version of $BLINT?
    • If you try to compile your procedure in SYSPROG or EXAMPLES, does it still give you those false warnings?
  • • Are there any instances of SRP object records that happen to be in your local application?
    No none of the obvious object code ones

    Just this stuff:
    $SRP_EDITOR_TEMP_... other apps * but not *PBC

    • Is there a copy of $BLINT in your local application?

    No

    • What is the datetime stamp of your version of $BLINT?

    20742.4177083333
    10.2.3

    • If you try to compile your procedure in SYSPROG or EXAMPLES, does it still give you those false warnings?

    Yes
  • edited December 20
    On the laptop copy where I have the issue with 3.4.7.1
    if I install srpeditor:
    3.4.4.3 (Editor & OCX) no issue
    3.4.6.12 (Editor & OCX) I get the issue
  • You cold hook into BLINT using the MD table and observe it's output.
  • I have this routine that I run and the proc in question did not show VNAVs

    hook into BLINT using the MD table and observe it's output.

    How should I 'observe'?

    I have a zip of my OI10 along with the SRPEditor upgrade exes that you could ckeck out.
    I can email you a dropbox link if that might help ?

    subroutine bsbs_check_compile_vnavs(Void) $insert LOGICAL Declare Function get_repos_entities,rti_resolve_main_stprocname,Repository,get_Status,Unassigned declare function SRP_Editor_Utility declare subroutine Set_Status Equ Crlf$ To Char(13):Char(10) ProcsToSkip ="INET_,WTK_,WWA_" Appid =@appID<1> entities = get_repos_entities(AppId, 'STPROC', '', '', '', '', '') compile_errors = null$ vnavs = null$ statuscode = null$ Err =null$ col = null$ Loop bRemove entity From entities At col Setting mark While entity != "" AppId =entity[1,"*"] mainname = rti_resolve_main_stprocname(entity) ProgID =mainname:"*":AppId ProcSource =xlate("SYSPROCS",ProgID,"","X") SourceName =field(ProcSource,"(",1)[-1,"B "] ProcPrefix =mainname[1,"_"] locate ProcPrefix:"_" in ProcsToSkip using ',' setting foo else if (mainname) and (mainname _eqc SourceName) then Set_Status(0) rv = Repository("COMPILE", entity, 0, "", "", mainname, StatusCode) Status = Get_Status(Err) If rv EQ 0 then Response = SRP_Editor_Utility("PROCESSERRORS", If Len(StatusCode) then StatusCode else Err) if response then cnt =dcount(response,@fm) compile_errors := AppId:"|":mainname:"|":cnt:" Compile Errors" :@fm end end else *if mainname _eqc 'bsbs_monitor_clockoffs' then debug SuspectedVNAVs = StatusCode if SuspectedVNAVs then cnt =dcount(SuspectedVNAVs,@fm) VNavList =null$ loop while SuspectedVNAVs ThisVNAV =SuspectedVNAVs[1,@fm] SuspectedVNAVs[1,col2()] =null$ VNavList := ThisVNAV<0,1>:"~" Repeat VNavList[-1,1] =null$ *vnavs := AppId:"|":mainname:"|":cnt:" Suspected VNAV Errors = ":VNavList :@fm vnavs := mainname:"|":cnt:" Suspected VNAV Errors = ":VNavList :@fm end end end end repeat compile_errors[-1,1] =null$ vnavs[-1,1] =null$ call write_Row('SYSLISTS', 'COMPILE_ERRORS':"*":AppId, compile_errors, 0) call write_Row('SYSLISTS', 'VNAVS':"*":AppId, vnavs, 0) if vnavs then convert @fm to crlf$ in vnavs oswrite vnavs to "c:\temp\":AppId:"_expanded_vnavs.txt" end return
  • @BarryStevens -

    I'll send you an upload link so we can look at your system directly. I should have some time to investigate and confirm, but Kevin is on holiday for a week and a half, so even if there is a fix that can be made, it won't happen until he returns.

    Regarding your hook into BLINT question, there are two ways to do this:
    1. Follow the instructions laid out in this hooking blog post.
    2. Use the SRP Editor's command line to do the work for you. In the SRP Editor command line enter: HOOK FUNCTION BLINT. This will create the shell that you can use to observe what BLINT does.
  • edited December 20
    HOOK FUNCTION BLINT
    Wow, that is so cool. Did not realise it would do the absolute lot for you.
  • Srp compile calls blint twice , 2nd call shows the errors.
    OI Compile only calls once

    Srp Compile 1st call


    Srp Compile 2nd call


    OI Compile 1st call


    No OI Compile 2nd call
  • Call Stack observations:
    Srp Compile 1st call

    Srp Compile 2nd call



    OI Compile 1st call


    This is 3.4.7.1

    I will now install the working 3.4.4 version and check the same observations.
  • Well, that sure is different - 3.4.4.3

    Call stack - first and only call

  • I'm hoping you noted that SRP Editor 1st call is indirectly handled via the Repository COMPILE request, which is what the OI editor is doing on its only call. The SRP Editor 2nd call is made directly, which I believe we added as a means to get more information.

    The main question is, are you seeing any reference to your unexpected VNAV error warnings in any of your debugs?
  • edited December 21
    Yes, this one:
    Srp Compile 2nd call


Sign In or Register to comment.