hexagon logo
Register Sign in
  • Replies 26 replies
  • Subscribers 221 subscribers
  • Views 293 views
  • Users 0 members are here
Options
Related

External Subroutine question

constadin
Hello all,

I will explain what I want to do before asking the question / your help.

I have programs that need to call a subroutine that will have a rev number. Example "Sub_Rev_A.prg"

I have a text file that those programs read and extract the final letter of the name and assign it in a variable with the readline command. So if I have a second sub named "Sub_Rev_B.prg" and the txt file writes B, the B sub will be read instead.

Now the issue I am having is... Those programs will be read only in a read only folder. I noticed that when I start those programs, they search for the sub they had executed in the first run while NOT in read only mode and after that while executing they search for the real version to execute (and execute it correctly).

In the example I gave be4, Main Program is tested with REV A sub, saved and set to read only. It works with Rev A for some time perfectly. Later on, we revise the sub to rev B, change the Txt to B. The program starts, gives an error message that the sub A is not found (we remove the old revisions), procedes to execution, reads the txt, executes sub B. From that point if I reexecute the Main program without closing it runs without error. If I close and reopen it I am getting the same error for Rev A.

No impact on the result of the measurement but each time I am getting an annoying message that I would love to eliminate if possible. Please know that in reality I am talking about hundreds of programs and subs and it is not possible to remove readonly mode each time we revise a sub without performing validation documents etc,

any help is much appreciated! |

PC-Dmis 2017 R2
Parents



  • I do understand what you're trying to do (I think).

    You're not getting what I'm saying.

    The line...

    ASSIGN/MYSUBNUM=1

    .. .doesn't need changing.

    All it does is have an initial value that will form a valid file name (i.e. one that exists on the system) and contains a subroutine called (in my example) 'MYSUB'


    At execution time, MYSUBNUM becomes whatever is read from the text file (1,2,3 etc) as you up-rev your subroutines.



    To clarify.

    When you start execution, PC-Dmis is looking at that CALLSUB command, and doing a verification that it exists.

    In my case it's looking at the 'MYSUBFILE' assignment. This is made up of MYSUBFILE+MYSUBNUM+".prg"
    So it looks what values they currently hold

    MYSUBFILE = "C:\\Users\\Public\\Documents\\Hexagon\\PC-DMIS\\2023.1\\SubLibrary"
    MYSUBNUM = 1
    ".prg" = ".prg"

    It sticks all those together to get "C:\\Users\\Public\\Documents\\Hexagon\\PC-DMIS\\2023.1\\SubLibrary1.prg" then it checks it contains a subroutine called MYSUB (which it does).

    It doesn't matter that it might not actually be the subroutine program we eventually call, just that it's a valid file / subname when it starts.

    It's then happy to proceed with execution without displaying an error.






    That's on me, I did not clearly explain that the rev A or 1 whatever will be changed to B/2. Changed as replaced. It is not possible to have it remain in that folder due to quality policies and risks :S What I am trying to achieve is not possible as the software is not designed to work like this contrary to logic :S Maybe in a future revision this will be implemented.

    Btw, Do you know if there is a way to get rid of those error messages? Deactivate them and stop them showing from Admin menu or something?
Reply



  • I do understand what you're trying to do (I think).

    You're not getting what I'm saying.

    The line...

    ASSIGN/MYSUBNUM=1

    .. .doesn't need changing.

    All it does is have an initial value that will form a valid file name (i.e. one that exists on the system) and contains a subroutine called (in my example) 'MYSUB'


    At execution time, MYSUBNUM becomes whatever is read from the text file (1,2,3 etc) as you up-rev your subroutines.



    To clarify.

    When you start execution, PC-Dmis is looking at that CALLSUB command, and doing a verification that it exists.

    In my case it's looking at the 'MYSUBFILE' assignment. This is made up of MYSUBFILE+MYSUBNUM+".prg"
    So it looks what values they currently hold

    MYSUBFILE = "C:\\Users\\Public\\Documents\\Hexagon\\PC-DMIS\\2023.1\\SubLibrary"
    MYSUBNUM = 1
    ".prg" = ".prg"

    It sticks all those together to get "C:\\Users\\Public\\Documents\\Hexagon\\PC-DMIS\\2023.1\\SubLibrary1.prg" then it checks it contains a subroutine called MYSUB (which it does).

    It doesn't matter that it might not actually be the subroutine program we eventually call, just that it's a valid file / subname when it starts.

    It's then happy to proceed with execution without displaying an error.






    That's on me, I did not clearly explain that the rev A or 1 whatever will be changed to B/2. Changed as replaced. It is not possible to have it remain in that folder due to quality policies and risks :S What I am trying to achieve is not possible as the software is not designed to work like this contrary to logic :S Maybe in a future revision this will be implemented.

    Btw, Do you know if there is a way to get rid of those error messages? Deactivate them and stop them showing from Admin menu or something?
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement