DBIA 5746 - Revision history

DavidWhitten at 13:18, 5 March 2018

2018-03-05T13:18:14Z

← Older revision		Revision as of 13:18, 5 March 2018
Line 37:		Line 37:
	DATE ACTIVATED 2012/03/20		DATE ACTIVATED 2012/03/20
	MAIL MESSAGE 55632380		MAIL MESSAGE 55632380
	DATE/TIME EDITED 1.ACTION: ~~APPROVEDAT~~ THE REQUEST OF: REDINGTON,PATRICK		DATE/TIME EDITED

			1.
			ACTION: APPROVED
			AT THE REQUEST OF: REDINGTON,PATRICK
	WITH CONCURRENCE OF: BEUSCHEL,GARY		WITH CONCURRENCE OF: BEUSCHEL,GARY
	DATE/TIME EDITED: 2011/11/04 13:05		DATE/TIME EDITED: 2011/11/04 13:05

DavidWhitten at 13:17, 5 March 2018

2018-03-05T13:17:27Z

← Older revision		Revision as of 13:17, 5 March 2018
Line 15:		Line 15:
	:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.		:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.

	:In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before		:In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before invoking the Browser.
	invoking the Browser.

	:In summary, this ICR allows the application to read, kill, set, and NEW the DDS variable.		:In summary, this ICR allows the application to read, kill, set, and NEW the DDS variable.

DavidWhitten at 13:17, 5 March 2018

2018-03-05T13:17:11Z

← Older revision		Revision as of 13:17, 5 March 2018
Line 15:		Line 15:
	:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.		:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.

	:In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will		:In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before
	not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before
	invoking the Browser.		invoking the Browser.

DavidWhitten at 13:16, 5 March 2018

2018-03-05T13:16:47Z

← Older revision		Revision as of 13:16, 5 March 2018
Line 15:		Line 15:
	:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.		:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.

	In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will		:In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will
	not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before		not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before
	invoking the Browser.		invoking the Browser.

	In summary, this ICR allows the application to read, kill, set, and NEW the DDS variable.		:In summary, this ICR allows the application to read, kill, set, and NEW the DDS variable.

			:Note that if List Manager is being invoked from ScreenMan the following Kernel calls should be made to restore the terminal settings required by ScreenMan before calling REFRESH^DDSUTL.

	~~Note that if List Manager is being invoked from ScreenMan the following Kernel calls should be made to restore the terminal settings required by ScreenMan before calling REFRESH^DDSUTL.~~
	<CODE>		<CODE>
	N IOAWMO,X S X=0 X ^%ZOSF("RM"),^%ZOSF("TYPE-AHEAD") S X="IOAWM0" D ENDR^%ZISS W IOAWM0		N IOAWMO,X S X=0 X ^%ZOSF("RM"),^%ZOSF("TYPE-AHEAD") S X="IOAWM0" D ENDR^%ZISS W IOAWM0
	</CODE>		</CODE>

	If this is not done the ScreenMan display will be corrupted.		:If this is not done the ScreenMan display will be corrupted.

	STATUS Active		STATUS Active

DavidWhitten: Created page with "USE SCREENMAN DDS VARIABLE (5746) ICR (5746) Name Value NUMBER 5746 IA # 5746 DATE CREATED 2011/11/04 CUSTODIAL PACKAGE VA FILEMAN USAGE Private TYPE Other..."

2018-03-05T13:16:13Z

Created page with "USE SCREENMAN DDS VARIABLE (5746) ICR (5746) Name Value NUMBER 5746 IA # 5746 DATE CREATED 2011/11/04 CUSTODIAL PACKAGE VA FILEMAN USAGE Private TYPE Other..."

New page

USE SCREENMAN DDS VARIABLE (5746) ICR (5746)

Name Value

NUMBER 5746
IA # 5746
DATE CREATED 2011/11/04
CUSTODIAL PACKAGE VA FILEMAN
USAGE Private
TYPE Other
DBIC APPROVAL STATUS APPROVED
NAME USE SCREENMAN DDS VARIABLE
;GENERAL DESCRIPTION
:The ScreenMan documentation recommends that applications use $D(DDS) to determine if their code is being executed from within a ScreenMan form. Reading the contents of ScreenMan's DDS variable allows application developers to determine the ScreenMan form their code is being invoked from. The format of DDS is formIEN^formName. This ICR allows reading of DDS variable.

In order for an application to integrate and simultaneously use the Browser, List Manager, and ScreenMan the application must be able to manipulate the DDS variable. If List Manager is invoked from ScreenMan List Manager prompts will
not display correctly because ^DIR works differently when DDS is defined. Therefore the application must save DDS and kill it before calling List Manager and restore it when returning from List Manager to ScreenMan. If the Browser is invoked from List Manager and DDS is not defined because of the above situation then the Browser will kill on exit some of variables needed by ScreenMan. Therefore the application needs to temporarily set DDS=1 before
invoking the Browser.

In summary, this ICR allows the application to read, kill, set, and NEW the DDS variable.

Note that if List Manager is being invoked from ScreenMan the following Kernel calls should be made to restore the terminal settings required by ScreenMan before calling REFRESH^DDSUTL.
<CODE>
N IOAWMO,X S X=0 X ^%ZOSF("RM"),^%ZOSF("TYPE-AHEAD") S X="IOAWM0" D ENDR^%ZISS W IOAWM0
</CODE>

If this is not done the ScreenMan display will be corrupted.

STATUS Active
DURATION Till Otherwise Agreed
SUBSCRIBING PACKAGE 1.SUBSCRIBING PACKAGE: CLINICAL REMINDERS
CREATOR REDINGTON,PATRICK
DBA Comments Activated by Debbie Trost. No VA FileMan patch is involved.
This authorizes access to an existing variable.

DATE ACTIVATED 2012/03/20
MAIL MESSAGE 55632380
DATE/TIME EDITED 1.ACTION: APPROVEDAT THE REQUEST OF: REDINGTON,PATRICK
WITH CONCURRENCE OF: BEUSCHEL,GARY
DATE/TIME EDITED: 2011/11/04 13:05

2.
ACTION: DEACTIVATED FOR EDITS AT THE REQUEST OF: REDINGTON,PATRICK
WITH CONCURRENCE OF: BEUSCHEL,GARYDATE/TIME EDITED: 2012/03/16 16:30

3.
ACTION: APPROVEDAT THE REQUEST OF: REDINGTON,PATRICK
WITH CONCURRENCE OF: BEUSCHEL,GARY
DATE/TIME EDITED: 2012/03/20 12:30