Spawning a Child Window - Revision history

Mike.schofield at 08:16, 31 March 2011

2011-03-31T08:16:50Z

← Older revision		Revision as of 08:16, 31 March 2011
Line 86:		Line 86:

	#		#
	# Pass the server list to the child window ~~via a temporary file~~		# Pass the server list to the child window
	#		#
	my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;		my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;

Baljemmett: Corrected example of sending VALUE_SV to child window

2011-03-29T22:52:07Z

Corrected example of sending VALUE_SV to child window

← Older revision		Revision as of 22:52, 29 March 2011
Line 111:		Line 111:
	my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;		my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;

	~~open(SVRS,~~ "~~> $FilePath") \|\| die "Can't open $FilePath - $!~~\n";		print "\@{{START_DISPLAY_PARAM SV " . join("\,", @servers) . "\n";

	~~print SVRS~~ join("\,", @servers) . "\n";

	~~close(SVRS);~~

Mike.schofield at 15:08, 29 March 2011

2011-03-29T15:08:56Z

← Older revision		Revision as of 15:08, 29 March 2011
Line 76:		Line 76:
	2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.		2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.

	3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the ~~agent~~ is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.		3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the list of agents is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.

Mike.schofield at 15:05, 29 March 2011

2011-03-29T15:05:03Z

← Older revision		Revision as of 15:05, 29 March 2011
Line 78:		Line 78:
	3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the agent is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.		3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the agent is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.

	1. Automatically starting the child...
			''1. Automatically starting the child...''

	In the (M) Pre-processing script of the parent menu:		In the (M) Pre-processing script of the parent menu:
Line 98:		Line 99:


	2. Starting the child display with suggested agents, and allowing the user to change the agent selection...		''2. Starting the child display with suggested agents, and allowing the user to change the agent selection...''

	Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:		Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:
Line 133:		Line 134:


	3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...		''3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...''

	It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.		It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.

Mike.schofield at 15:04, 29 March 2011

2011-03-29T15:04:08Z

← Older revision		Revision as of 15:04, 29 March 2011
Line 68:		Line 68:
	'''To Determine which Agents Should be Started in the Child Window...'''		'''To Determine which Agents Should be Started in the Child Window...'''

	The parent window can define which agents should be used when starting the child window. For example, if the same agents ~~should be~~ used by the child as are selected in the parent window, ~~then~~ the ~~following code needs~~ to be ~~added~~ to the ~~parent:~~		The parent window can define which agents should be used when starting the child window. For example, the same agents are used by the child as are selected in entries on the parent window.

			There are three different ways of achieving this:

			1. The parent determines the list of agents to be used by the child and the child window starts without any further prompting.

			2. The parent determines the list of agents to be used by the child and the child window opens with the startup window that allows the user to accept or change the list of agents to be connected.

			3. The parent determines the list of agents to be used by the child and the child window opens with the startup window, but the agent button to change the agent is greyed out. This would be useful if the startup window has other input fields to be entered, but the agent list should not be changed.

			1. Automatically starting the child...

	In the (M) Pre-processing script of the parent menu:		In the (M) Pre-processing script of the parent menu:
Line 86:		Line 96:

	This will start the child window automatically and connect it to the selected servers.		This will start the child window automatically and connect it to the selected servers.


			2. Starting the child display with suggested agents, and allowing the user to change the agent selection...

	Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:		Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:
Line 119:		Line 132:
	''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''		''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''


			3. Starting the child display with suggested agents, but not allowing the user to change the agent selection...

	It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.		It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.
Line 130:		Line 145:

	By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.		By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.

			''(** Note: again, for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''

Mike.schofield at 14:48, 29 March 2011

2011-03-29T14:48:18Z

← Older revision		Revision as of 14:48, 29 March 2011
Line 5:		Line 5:
	''Spawning a child window in SEM:''		''Spawning a child window in SEM:''

	One window can be started from a another window by:		One window can be started from another window by:

	* adding code to the (M) Pre-processing script of menu option in the ''parent'' window		* adding code to the (M) Pre-processing script of menu option in the ''parent'' window
Line 68:		Line 68:
	'''To Determine which Agents Should be Started in the Child Window...'''		'''To Determine which Agents Should be Started in the Child Window...'''

	The parent window can define which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to ~~the menu option of~~ the parent ~~and in~~ the ~~startip initialize~~ script of the ~~child~~:		The parent window can define which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the parent:

			In the (M) Pre-processing script of the parent menu:

	~~In the (M) Pre-processing script of the parent menu option:~~


	~~use Sysgem;~~

	#		#
	# Pass the server list to the child window via a temporary file		# Pass the server list to the child window via a temporary file
	#		#
	my ~~$path~~ = ~~"";~~		my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;

	~~Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);~~

	my $~~FilePath =~~ $~~path .~~ "~~\\Temp_SV_File.txt~~";

			foreach my $server (@servers)
			{
			print "\@{{START_DISPLAY_SERVER $server\n";
			}


			This will start the child window automatically and connect it to the selected servers.

			Sometimes it is desirable simply to default the server list and allow the user to change the default settings before starting the display. To achieve this, script code needs to be added to both the parent menu (M) Pre-processing script and the child startup initialization script:

			In the Parent (M) Pre-processing script:


			#
			# Pass the server list to the child window
			#
	my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;		my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;

Line 92:		Line 103:
	close(SVRS);		close(SVRS);




	In the startup ~~Initialize~~ script of the child:		... and in the startup initialize script of the child:


	~~use Sysgem;~~

	#		#
	# ~~Open~~ the ~~selected server~~ list ~~from the parent window via a temporary file~~		# set up the connect to agent list
	#		#
	~~my $path = "";~~

	~~Sysgem::GetApplicationPath(~~"~~Sysgem AG", "TempFiles~~"~~, $path)~~;		print "\@{{LOAD_SERVERS $VALUE_SV\n"; # to preselect the same servers as those selected in the parent window

	~~my $FilePath = $path~~ . "\~~\Temp_SV_File~~.~~txt";~~

			''(** Note: for this to work, the startup window needs to have an input field defined - even if only a field of type "-None-" with no text label!)''


			It is also possible to show the startup window, perhaps to allow the user to make an entry in a startup field, but not to allow the user to change the list of selected agents.

			To achieve this, the following script line should be added to the startup initialisation script after the print "\@{{LOAD_SERVERS command shown above.



	~~open(SVRS,~~ "~~< $FilePath") \|\| die "Can't open $FilePath - $!~~\n";		print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used

	~~my @servers = <SVRS>;~~
			By using the "LOCK_SERVERS" command - the startup window will be shown, but the Agents button will be greyed out.
	~~close(SRVS);~~

	~~print~~ "~~\@{{LOAD_SERVERS $servers[0]\n~~"~~; # to preselect~~ the ~~same servers as those selected in~~ the ~~parent window~~

	~~print "\@{{LOCK_SERVERS\n"; # to force these and only these to~~ be ~~used~~

Mike.schofield at 09:29, 29 March 2011

2011-03-29T09:29:27Z

← Older revision		Revision as of 09:29, 29 March 2011
Line 115:		Line 115:
	close(SRVS);		close(SRVS);

	print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the ~~parnet~~ window		print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the parent window

	print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used		print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used

Mike.schofield at 09:26, 29 March 2011

2011-03-29T09:26:57Z

← Older revision		Revision as of 09:26, 29 March 2011
Line 5:		Line 5:
	''Spawning a child window in SEM:''		''Spawning a child window in SEM:''

			One window can be started from a another window by:

			* adding code to the (M) Pre-processing script of menu option in the ''parent'' window
			* adding script comment in the Main Display Pre-processing script of the ''child'' window


	'''To Initiate the Spawn Command from the Parent Window...'''		'''To Initiate the Spawn Command from the Parent Window...'''

	~~To spawn a new window from a menu option,~~ code ~~needs to be entered~~ in the '(M) Pre-processing script' of the menu option ~~in the main 'Pre-processing' script~~ of the ~~child~~ window.		Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:

	~~In the (M) Pre-processing script enter the following code:~~


Line 35:		Line 39:
	'''To Identify the Child Window...'''		'''To Identify the Child Window...'''

	The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. ~~The~~ phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.		The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. In the example below, the phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.


Line 46:		Line 50:
	'''To Pass Parameters from the Parent to the Child Window...'''		'''To Pass Parameters from the Parent to the Child Window...'''

			The following code added to the Parent menu option, in the (M) Pre-processing script, passes parameters to the child window using data from the selected entry in the parent window.

	~~The following code added to~~ the ~~Parent menu option (~~in the ~~(M) Pre-processing script) will pass parameters~~ to the child window ~~using the selected entry in the parent window.~~		In this example, fields AA and AB of the selected entry in the parent window are sent to the child window:


Line 54:		Line 59:


	This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Agent script of the child window ~~when the display window has been spawned~~. In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.		This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Windows Agent script of the child window.

			In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}.

			In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.


	'''To Determine which Agents Should be Started in the Child Window...'''		'''To Determine which Agents Should be Started in the Child Window...'''

			The parent window can define which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the menu option of the parent and in the startip initialize script of the child:
	The parent window can ~~specify~~ which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the menu option of the parent and in the startip initialize script of the child:

	In the (M) Pre-processing script of the parent menu option:		In the (M) Pre-processing script of the parent menu option:
Line 85:		Line 93:




	In the startup Initialize script of the child:		In the startup Initialize script of the child:

Mike.schofield at 08:00, 29 March 2011

2011-03-29T08:00:13Z

← Older revision		Revision as of 08:00, 29 March 2011
Line 60:		Line 60:


	The parent window can specify which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code ~~neds~~ to be added to the menu option of the parent and in the startip initialize script of the child:		The parent window can specify which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code needs to be added to the menu option of the parent and in the startip initialize script of the child:

	In the (M) Pre-processing script of the parent menu option:		In the (M) Pre-processing script of the parent menu option:

Mike.schofield: Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. ---- ''Spawning a child window in SEM:'' '''To Initiate the Spawn Command from the Paren..."

2011-03-28T16:39:30Z

Created page with "'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. ---- ''Spawning a child window in SEM:'' '''To Initiate the Spawn Command from the Paren..."

New page

'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.

----

''Spawning a child window in SEM:''

'''To Initiate the Spawn Command from the Parent Window...'''

To spawn a new window from a menu option, code needs to be entered in the '(M) Pre-processing script' of the menu option in the main 'Pre-processing' script of the child window.

In the (M) Pre-processing script enter the following code:

#
# start another display window, passing along information
# extracted from the selected entries.
#
# @{{START_DISPLAY_SCRIPT

#
# Don't display the menu dialog.
#
# @{{MENU_OPTION_SILENT
#

print "\@{{START_DISPLAY_TITLE Child Example\n";

print "\@{{START_DISPLAY_NEW\n";

print "\@{{START_DISPLAY_TILED\n";

'''To Identify the Child Window...'''

The following comment is added to the main 'Pre-processing' script to identify the display window as the one required. The phrase "Child Example" is variable text to identify this particular window. The same text is used in the "\@{{START_DISPLAY_TITLE" output initiated by the (M) Pre-processing script in the menu option of the parent window.

#
# @{{AUTOSTART_DISPLAY_TITLE Child Example
#

'''To Pass Parameters from the Parent to the Child Window...'''

The following code added to the Parent menu option (in the (M) Pre-processing script) will pass parameters to the child window using the selected entry in the parent window.

print "\@{{START_DISPLAY_PARAM AA $SelectedEntry{0}{AA}\n";
print "\@{{START_DISPLAY_PARAM AB $SelectedEntry{0}{AB}\n";

This will cause the variables $INPUT_AA and $INPUT_AB to be defined in the Main Agent script of the child window when the display window has been spawned. In UNIX agent scripts - access the Korn shell variables as ${INPUT_AA} and ${INPUT_AB}. In VMS agent scripts - access the DCL logical names as INPUT_AA and INPUT_AB.

'''To Determine which Agents Should be Started in the Child Window...'''

The parent window can specify which agents should be used when starting the child window. For example, if the same agents should be used by the child as are selected in the parent window, then the following code neds to be added to the menu option of the parent and in the startip initialize script of the child:

In the (M) Pre-processing script of the parent menu option:

use Sysgem;

#
# Pass the server list to the child window via a temporary file
#
my $path = "";

Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);

my $FilePath = $path . "\\Temp_SV_File.txt";

my @servers = map $SelectedEntry{$_}{"SV"}, sort keys %SelectedEntry;

open(SVRS, "> $FilePath") || die "Can't open $FilePath - $!\n";

print SVRS join("\,", @servers) . "\n";

close(SVRS);

In the startup Initialize script of the child:

use Sysgem;

#
# Open the selected server list from the parent window via a temporary file
#
my $path = "";

Sysgem::GetApplicationPath("Sysgem AG", "TempFiles", $path);

my $FilePath = $path . "\\Temp_SV_File.txt";

open(SVRS, "< $FilePath") || die "Can't open $FilePath - $!\n";

my @servers = <SVRS>;

close(SRVS);

print "\@{{LOAD_SERVERS $servers[0]\n"; # to preselect the same servers as those selected in the parnet window

print "\@{{LOCK_SERVERS\n"; # to force these and only these to be used