first look questions

  • uschor

    uschor - 2008-02-06

    First, I have to say that it's an excellent move, and it'll be nice to
    see and try the long awaited JDBC driver of GT.M. The tools look very
    sharp (nice usage of GWT, Eclipse, and other OSS!), and it's nice to
    get a first look at PSL - yet another M++ dialect.

    Although I only took a short look, I already have a few questions:
    1.      Where's the source code? I can't find it anywhere.
    2.      Any documentation on how to map existing globals to SQL access?
    3.      I can't seem to find the PSL to C/SQL compiler either. I see that
    both the Eclipse plugin and the web tool can "test compile", but
    where's the compiler itself?
    4.      PSL seems to be pretty much a superset of M, with a few exceptions
    mentioned in the docs. Is it correct to say that PIP contains an M to
    C/SQL compiler, or something very close to that?
    5.      Are there any live systems running at Fidelity customers on Oracle,
    after automatic PIP compilation? How are they performing?

    Again, kudos for release.


    • K.S. Bhaskar

      K.S. Bhaskar - 2008-02-08

      Good to hear from you, Uri.  Thanks for the kind words & interest in PIP.

      1. The source code for PIP is in the *rtns directories as well as in code templates in global variables.  The definitive code is itself in PSL, which is compiled into M, and the PSL compiler is itself written in PSL.

      2. PIP documentation still needs to be separated from Profile documentation.  This separation was not needed when PIP was simply part of Profile.  For now, your best bet may be to use SQL to create tables, as well as some PSL queries and updates to those tables.  Then look for new generated code modules and changes to global variables (which is captured in the GT.M journal files).  This should tell you where to write code to hook up existing M globals.  Another possibility is to start the interactive mode: /opt/pip_V01/dm and execute Do ^DRV.  Login as user 1 password xxx and poke around the menus.  Caveat: this part of PIP will probably change, so don't rely on it for anything more than to develop your understanding of PIP.

      3. The compiler is in the *rtns subdirectories.

      4. There are PSL to M and SQL to M compilers.  There is no tool to generate PSL from M.  Such a tool would be nice to have, of course!

      5. PIP itself is brand new, and no one is using PIP as stand alone software in production.  But we do have customers using Profile on Oracle.  (Of course, as you know, the majority of our customers use Profile on GT.M.)

      -- Bhaskar


Log in to post a comment.