Sysgem Support - User contributions [en]

AUTOCLOSE

2012-01-25T16:40:55Z

Baljemmett:

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

----

''How to automatically close the input form after a transaction is complete.''

'''AUTO_CLOSE'''

Normally, the "results pane" remains open after a SEM transaction is compleet, to show the output from the script that has run on the target system. Sometimes, however, it is desirable to close the window automatically as soon as the script has completed on the target server.

Output the following string to standard output from any of the following scripts:

* (M) Fields

* (M) Pre-processing

* (M) Post-processing

* (M) AS400

* (M) Windows / NT

* (M) UNIX

* (M) VMS

'''String to output:'''

"@{{AUTOCLOSE"

'''From a Perl script:'''

print "\@{{AUTOCLOSE\n";

'''From a Korn Shell script:'''

echo "@{{AUTOCLOSE"

'''From a DCL Shell script:'''

$ write sys$output "@{{AUTOCLOSE"

Spawning a Child Window

2011-03-29T22:52:07Z

Baljemmett: Corrected example of sending VALUE_SV to child window

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

----

''Spawning a child window in SEM:''

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 script comment in the Main Display Pre-processing script of the ''child'' window

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

Add the following code in the '(M) Pre-processing script' of the menu option of the parent window:

#
# 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. 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.

#
# @{{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, passes parameters to the child window using data from 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:

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 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...'''

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 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.

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

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

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

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

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:

In the Parent (M) Pre-processing script:

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

print "\@{{START_DISPLAY_PARAM SV " . join("\,", @servers) . "\n";

... and in the startup initialize script of the child:

#
# set up the connect to agent list
#

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

''(** 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.

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

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

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!)''

User:Baljemmett

2011-01-21T13:28:08Z

Baljemmett: Created page with "Hello world! This is Blarney Castle: 640px"

Hello world!

This is Blarney Castle:

[[File:Castle.jpg|640px]]

File:Castle.jpg

2011-01-21T13:26:30Z

Baljemmett: Test image - inside Blarney Castle.

Test image - inside Blarney Castle.

Dialogue Boxes

2011-01-19T17:33:26Z

Baljemmett: Tidy up a few bits

Some hints for developers working within the Sysgem Enterprise Manager (SEM) environment.

== Dialogue Boxes ==
How to display a dialogue box from a SEM script:

e.g. in a Windows Script (in Perl)

print "\@{{B Banner - Title\n";
print "\@{{T 1st Line of information for display inside the box\n";
print "\@{{T \n";
print "\@{{T Last line of information\n";
print "\@{{DI\n";

The "\@{{DI\n" will display the dialogue box as an informational Box.

To display an error box, use: "\@{{DE\n"

To display an warning box, use: "\@{{DW\n"

To display an question box, use: "\@{{DQ\n"

Note that a question box can only be effective if executed from the "(M) Post Processing" script from a Menu option, amd the effect is that if the user selects "Yes" then the remainder of the script will be executed, whereas if the user select "No" then the rest of the script after the print "\@{{DQ\n"; statement will be ignored.

Main Page

2011-01-19T17:28:34Z

Baljemmett: Add link to developer hints page

'''Welcome to the Sysgem Support wiki'''

This wiki is intended to contain useful information for those involved in supporting or customising Sysgem products. It is currently in an experimental state; for real support issues we recommend that you contact us using our normal support channels:

* [http://www.sysgem.com/support.php Sysgem Customer Support]
* [http://www.sysgem.com/company.php#contactus Contact Sysgem]

The content on this wiki is visible to everyone, to provide maximum benefit to our customers and colleagues. However, to add or edit content, a user account is required; if you wish to contribute any information, please contact Sysgem.

== Contents ==

Some useful starting points:

* [[Developer Hints]] contains example code for developers working within the SEM environment

== Getting started ==
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

Dialogue Boxes

2011-01-19T17:22:25Z

Baljemmett: moved Talk:Main Page to Developer Hints: For now, start a page for hints. We'll think about organising it neatly later...

Sysgem Enterprise Manager (SEM) Programmer Hints:

How to display a dialogue box from a SEM script:

e.g. on a Windows Script (in Perl)

print "\@{{B Banner - Title\n";
print "\@{{T 1st Line of information for display inside the box\n";
print "\@{{T \n";
print "\@{{T Last line of information\n";
print "\@{{DI\n";

The "\@{{DI\n" will display the dialogue box an an informational Box.

To display an error box, use: "\@{{DE\n"
To display an warning box, use: "\@{{DW\n"
To display an question box, use: "\@{{DQ\n"

Note that a question box can only e effective if executed from the "(M) Post Processing" script from a Menu option, amd the effect is that if the user selects "Yes" then the remainder of the script will be executed, whereas if the user select "No" then the rest of the script after the print "\@{{DQ\n"; statement will be ignored.

Main Page

2011-01-19T16:00:16Z

Baljemmett: Add note that the wiki is read-only for users without accounts.

'''Welcome to the Sysgem Support wiki'''

This wiki is intended to contain useful information for those involved in supporting or customising Sysgem products. It is currently in an experimental state; for real support issues we recommend that you contact us using our normal support channels:

* [http://www.sysgem.com/support.php Sysgem Customer Support]
* [http://www.sysgem.com/company.php#contactus Contact Sysgem]

The content on this wiki is visible to everyone, to provide maximum benefit to our customers and colleagues. However, to add or edit content, a user account is required; if you wish to contribute any information, please contact Sysgem.

== Getting started ==
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.

Main Page

2011-01-19T15:55:51Z

Baljemmett: Provide introduction on front page.