[Susan Rosko]

Hi Matt:

Sorry for the extended response… the OPENLINK comment from Siemens sets my blood pressure up…

When I read your description it sounds to me like you might be experiencing a INVISION TIF abend when your regions are brought up again.  The interface states are ON/FREE, but no data passes on them.  This usually will display for the operations staff with a message similar to the following:

@ARKE21233: (A2G0  ) TIF ABEND T010 IN PROGRAM CHPPTIFM LOADING IGATMFUN

@A2K       01:29:07 ARKE21233: (A2G0  ) TIF ABEND T010 IN PROGRAM                                                    

Here’s what I do to resolve this:

Stop all your interfaces on INVISION.

First check to see if the COMQFILE is open.  If not, open it and reset the TIF switch in INVISION (this is in the OAS INTERFACE SUBSYSTEMS MENU, TIF SUBSYSTEM MENU, TURN OFF ABEND SWITCH; if you have INVISION model pathways this should be from the main menu options: 20,99,10, PF3, PF2).  Start your interfaces on INVISION.  You may not see anything happening at first.  If no patient updates or orders are being performed on INVISION right away, you may want to quickly “kick” the interface, just have someone do some kind of update on an active patient.  Once the first INVISION update takes place after the switch is reset the held messages should start showing up in the queue.  

If you find that the fix above does not work, you may need to skip a logfile record because it errored out on mappings or some other mismatch.   Stop all your interfaces again.  Go to the same TIF SUBSYSTEM MENU above, then SKIP LOGFILE RECORD (if you have INVISION model pathways, this should be 20, 99, 10, PF3, PF9).  You will get a warning about data being lost, but okay it.   Then TURN OFF ABEND SWITCH (on same screen PF2).  Again, you may need to kick the interface by having a patient update performed.  I find that skipping the logfile record usually takes care of the problem.

If anyone in your area has trouble ticket access in Siemens, ask for them to obtain the copy of the last resolution done for your problem.  I would bet they did one of the above fixes.  

Some other related tidbits:

A cleaner stop and start of all INVISION interfaces is to use Siemens CMONSTOP and CMONSTRT.  If you use these commands you may need to manually shut down the COMQFILE after performing the CMONSTOP and manually open the COMQFILE before performing the CMONSTRT.  After doing the CMONSTRT reset the TIF abend switch as stated above.  We typically have not had to do this with our SUT applies even our most recent ones.

We have found that the COMQFILE needs regular reorging or you might run into slow or stopped interface processing.  We have a job we created that does this during our weekly CICS recycle downtime.  If you want our JCL for that, contact me.  I assume you are an ICO site if you are doing your own SUT applies, we are an ICO site.

We have problems both with our weekly recycle of CICS regions and with SUT applies with some INVISION connections being in an unacquired state in CICS and then we need to manually acquire the CICS connections before they will connect with Cloverleaf.  Typically this has occured with our inbound (INVISION RTIF) interface connections and not our outbound (TIF) interface connections.

[Susan Rosko]

At Carle, they created job titles of Systems Integrator and Senior Systems Integrator right about the time we switched from Openlink to Cloverleaf.  

On related note, we have entertained thoughts of renaming our team to “default pager group” just to make it easier on the help desk…

Go Illini!  (don’t give us another heart attack like last night)

[Author]

Replies