James Cobane

Forum Replies Created

Viewing 15 replies – 1 through 15 (of 1,078 total)
  • Author
    Replies
  • in reply to: Help with xlateStrTrimLeft/Right #121852
    James Cobane
    Participant

      Remember that you should treat xlateOutVals as a list

      • This reply was modified 1 month, 1 week ago by James Cobane.
      in reply to: Help with xlateStrTrimLeft/Right #121845
      James Cobane
      Participant

        You could use the clock commands to reformat the date:

        set dateIn [lindex $xlateInVals 0]

        set dateOut [clock format [clock scan $dateIn -format “%Y%m%d”] -format “%m%d%Y”]

        set xlateOutVals

          (for some reason, it isn’t displaying the last portion of my “set xlateOutVals

            ” command above)

             

            Hope that helps.

            Jim Cobane – Henry Ford Health

            • This reply was modified 1 month, 1 week ago by James Cobane.
            • This reply was modified 1 month, 1 week ago by James Cobane.
            • This reply was modified 1 month, 1 week ago by James Cobane.
            • This reply was modified 1 month, 1 week ago by James Cobane.
            • This reply was modified 1 month, 1 week ago by James Cobane.
            James Cobane
            Participant

              I don’t know that I would recommend attempting to change the NetConfig programmatically from a script; I think you could unknowingly corrupt your NetConfig.  When I have had to do a mass change on the AutoStart settings in NetConfig in the past, I have done it via a text editor and simply done a search/replace of AUTOSTART 0 to AUTOSTART 1 (or visa versa) depending on the need.  I simply ensure that I back up the NetConfig before making this change, then load it in the GUI after the change to make sure it didn’t break.

              Hope that helps.

              Jim Cobane – Henry Ford Health

              in reply to: FTP Filename in proc #121835
              James Cobane
              Participant

                Jason,

                Yes, this information is available within the DRIVER CONTROL portion of the metadata of the message.  Here is a snippet of Tcl code that you could put into a proc in the inbound context that would give you that information from the message:

                set myklst [msgmetaget $mh DRIVERCTL]
                keylget myklst FILENAME myFileName

                Hope that helps.

                Jim Cobane – Henry Ford Health

                in reply to: SMATDB in IDE not up-to-date #121631
                James Cobane
                Participant

                  I would recommend opening an incident with Support.  It could be something as simple as adding some arguments to the JVM in the Advanced Tab on the Client preferences or even checking/unchecking items on the SMAT tab.  Support probably has some recommendations/best practices for performance related to the SMAT DB/GUI

                  Jim Cobane – Henry Ford Health

                  in reply to: Cloverleaf API – SMATDB #121550
                  James Cobane
                  Participant

                    It would be great if Infor would produce/present a webinar series on how to interact with the Cloverleaf APIs.  We have many scripts that use the ncitlib functions that I would like to replicate with the CLAPI functionality.  Just my $.02

                    Jim Cobane – Henry Ford Health

                    in reply to: Killing messages using an XLATE #121549
                    James Cobane
                    Participant

                      Rather than killing it in an Xlate, it would be more efficient to kill it in a tps proc on the route prior to translation.  Below is a snippet of code for the ‘run’ section of a tps proc for reference:

                      run {
                      # ‘run’ mode always has a MSGID; fetch and process it
                      keylget args MSGID mh

                      set disp “CONTINUE”

                      set msg [msgget $mh]

                      # get the message length in bytes
                      set msg_len [string bytelength $msg]

                      # check to see if the incoming message length in BYTES is more than 1MB
                      if { $msg_len > 1000000} {
                      set disp “KILL”
                      }

                      lappend dispList “$disp $mh”
                      }

                      return $dispList

                       

                      in reply to: Delete queued messages in a thread #121535
                      James Cobane
                      Participant

                        Do you want to delete ALL the messages queued for that thread, or only the first one on the queue?

                        You can use the Database Administrator tool from the IDE or the command line (depending on your preference and/or skill level).

                        If you want to delete ALL the messages on the queue for that thread, then the command line option would be:

                        hcidbdump -r -d destinationthread -D

                        where destinationthread is the name of your outbound thread

                        If you want to only delete the first queued message, then get the messageID of the first queued message (i.e. hcidbdump -r -d destinationthread -O i) and look at the ID of the first message queued (i.e. 0.0.12345) and use that in command for the single message.  It is likely the first queued message is in a state 16 if you are not getting ACKs from your outbound system.  Once you have the message ID then the command is:

                        hcidbdump -r -m 0.0.12345 -D

                        Where 0.0.12345 should be replaced with the actual message ID.

                        I would recommend working with Infor Support if you are not comfortable or are unsure of how to proceed

                        Jim Cobane – Henry Ford Health

                        • This reply was modified 8 months, 2 weeks ago by James Cobane.
                        in reply to: So long, and thanks for all the fish. #121417
                        James Cobane
                        Participant

                          Rob,

                          Congrats on your retirement! It is well earned and deserved! Thank you so much for all your contributions to the Cloverleaf community and direction/development/support of the product! You will be greatly missed! I’ll never forget seeing you at Level I training shortly after you joined HCI (at the time) and so glad that we chose Cloverleaf (HCI-Link back then) instead of MegaSource 🙂

                          Jim Cobane

                          James Cobane
                          Participant

                            Attached is a .zip file containing the .pdl and .pdo file that I believe we created when we had connected to Experian.  We currently use this for our connection to Passport.

                            You may want to do your own compile of the .pdl to create the .pdo in your environment.

                            Hope this helps.

                            Jim Cobane – Henry Ford Health

                            Attachments:
                            You must be logged in to view attached files.
                            in reply to: Thread IP and ports #121053
                            James Cobane
                            Participant

                              Hmm…not sure why you’re getting the error as the script runs for me.  Make sure that you’re root is set (i.e. setroot / showroot)

                              in reply to: Thread IP and ports #121039
                              James Cobane
                              Participant

                                We created a script (getportsall) that searches all your sites NetConfig(s) and pulls the data out of the NetConfig for each site.  The output looks like this:
                                <pre> Port Type Host/site thread Protocol Thread/Dest Site
                                ——– ————— —————————————- ———- —————————— —————
                                2000 Client & Dest mcwapp840b.corp.ds.some.org pdl-tcpip to_hfh_intellidesk epic1prod
                                2200 Client & Dest 10.88.205.73 tcpip to_hfhn_topcon_adt hfh1prod
                                2304 Client lsibase1.wafoote.org tcpip to_hfah_LSI_adt hfah1prod
                                2505 Client 10.32.75.70 tcpip to_hfah_WestComNurse_adt hfah1prod
                                2575 Client 10.403.0.108 tcpip to_rhyme_278N_278Referral epic2prod</pre>
                                Script is attached with a .txt extension added to allow it to be uploaded.  Feel free to modify for your needs.

                                Regards,

                                Jim Cobane – Henry Ford Health

                                P. S. – It doesn’t look like the formatting of the output stayed in the post, but you get the idea.

                                • This reply was modified 1 year, 3 months ago by James Cobane.
                                Attachments:
                                You must be logged in to view attached files.
                                in reply to: Where to place command line Tcl Procs in Windows O/S? #120846
                                James Cobane
                                Participant

                                  Hi Jim,

                                  Hope all is well.  My assumption would be that you would put them in the ‘$HCIROOT\usercmds’ folder the same as on AIX as the directory structure on Windows should be the same as on AIX.  I would also assume (perhaps incorrectly) that you would need a .bat extension.

                                  Good luck!

                                  Jim Cobane – Henry Ford Health

                                  James Cobane
                                  Participant

                                    As @ variables are dynamic temp variables, I would not expect the engine to complain or throw any warning.  So, I believe this is expected behavior (no error).

                                    • This reply was modified 1 year, 7 months ago by James Cobane.
                                    • This reply was modified 1 year, 7 months ago by James Cobane.
                                    in reply to: Unable to bind tcp/ip socket: Address already in use #120784
                                    James Cobane
                                    Participant

                                      We are AIX, and I ran the command to see what it produced:

                                      /usr/sbin/no -a | fgrep ephemeral

                                      tcp_ephemeral_high = 65535
                                      tcp_ephemeral_low = 32768
                                      udp_ephemeral_high = 65535
                                      udp_ephemeral_low = 32768

                                      Hopefully, you can find the command for your environment.

                                    Viewing 15 replies – 1 through 15 (of 1,078 total)