All messages should be posted in plain text.  HTML will be converted to
attachments.    The meditech-l web site is MTUsers.com
======================================

For those of you who are using, or have used, a call to
MIS.SCREEN.kernal from within a CDS (a CDS calling another CDS, and then
returning to the calling CDS) - how stable are you finding this?  Is it
still a viable option?  I've seen some sources say that this program is
no longer there (we are Magic release 5.5) - even though it is still
there.  Some say don't use it.  Some give a whole list of modifications
that allow them to continue using it.  What is the most up-to-date
status of this technique?

>From a technical standpoint (in our 5.5 release) I found that the slash
variable /KERN is killed off when returning to the first (calling) CDS. 
This contains critical information - a long packed string of it - about
the screen.  Included are the row and column offsets - without which
screen corruption can be caused.  /KERN seems to contain a lot of
variables that used to be scalar in nature - i.e. /ROWT (top of row
offset).  /KERN could be saved and restored - but this only begs the
question.  What else might potentially be altered by the second call to
MIS.SCREEN.kernal, and what other vairables might be `stepped on' in
subsequent Meditech releases/updates?

Any information would be appreciated.
_______________________________________________
meditech-l mailing list
[email protected]
http://mtusers.com/mailman/listinfo/meditech-l

Reply via email to