This configuration is not only for Windows terminal Server or Citrix environments.
When the user PCs don’t have a unique IP address, or, when the 5250 emulation is handled through a front end, then, the "TSE mode" configuration can be used.
In standard configuration (TSE not active), LAUNCHER server on the PC is waiting for a call comming from an AS/400 job.
The
AS/400 program needs to know the IP address of the PC or its DNS name, to be
able to contactd it via LNCOPEN.
With special value "*DEV", LAUNCHER retreive the PC IP address from
the display device description.
If the IP address cannot be known from the AS/400 program, or, if multiple PCs
have the same IP address (like when TSE or CITRIX is used), then, the way of
the conversation must be changed by configuring the LAUNCHER Office TSE mode.
This configuration is set on the PC by the “Configuration” tab on the administration screen.
Note :The two configurations can be used together with the same AS/400.
Special features of AS/400 installation:
- Launch LAUNCHERD deamon on AS/400:
ADDLIBLE LAUNCHER
STRLNCD MSGLVL(1) <F4>
This program must be launched under a profile with priority rights on other profiles, otherwise the LAUNCHERD program from LAUNCHER must be modified so that it will run with QSECOFR :
CHGPGM LAUNCHER/LAUNCHERD USRPRF(*OWNER)
A deamon LAUNCHERD program will be launched.
If the default JOBQ value is used, LAUNCHERD will be launched in QSYSWRK sub system.
The DSPLNCD command is used to view connected workstations
Special features on the TSE server :
Running LAUNCHER Office on a all users "Terminal Services" Server requires a LAUNCHER Office instance that will operate for each user.
These instances may come in addition to another LAUNCHER Office instance as NT service.
To manage those many LAUNCHER Office instances a station cannot be identified anymore only with its IP address.
Each LAUNCHER Office TSE user must have a unique name, and indicate its AS/400 IP address.
So, on configuration screen, one of the "Terminal Services" modes must be selected (Configuration tab).
Name choice can be made either from :
• Using the user name option: WINDOWS user name will be used as name.
• Using the station name option: the PC name connected to TSE (user station) will be used as name.
• Using a fixed name option : allows choice of any name (in this case you have to check if this name does not already exist in the TSE server).
Your application will have to manage the names, for example, using the user name as unique local name assuming that the user connects from only one station.
When the TSE mode is on (LAUNCHERD is running on the AS/400), when passing a name to LNCOPEN, LAUNCHER server looks for the PC in the following order:
• Look for a PC having the requested "TSE" name.
• Look for a PC having the requested "DNS" name.
Configuring
5250 emulator in the same way (example station name), allows to use *DEV name
in LNCOPEN command.
Otherwise, use the corresponding name.
When "*DEV" is used, and LAUNCHERD is running, LAUNCHER Server looks for the PC as follow:
• Looks for a PC having a "TSE" name equal to the current job name (see job name filtering here after).
• Connect to the display device IP address.
Job name filtering:
If you configure your Client Access emulator, to build the terminal name from the station name, you will be able to use "*DEV" on LNCOPEN calls.
Change the content of the data area LNCNET, position 1 to 100:
CHGDTAARA DTAARA(LNCNET (1 100) VALUE(‘AUTO;STNNAME=<filter>;’)
The value of <filter> tells LAUNCHER how the terminal name is built.
<filter> can have the following values :
o +&COMPN No prefix or suffix is added.
o %+&COMPN One prefix character is added to identify a display or printer.
o +&COMPN* One suffix character is added to have unique names on the station.
o +&COMPN= One suffix character is added to have unique names on the network.
o +&COMPN*= Two suffix characters are added.
o %+&COMPN*= One prefix and two suffix added.
Note : Those values are used by Client access in the display definition files (Files .WS).
Example :
The station name is PAUL.
The LAUNCHER server on the PC is configured in TSE mode, using the station name as Launcher name.
Client access is configured to add the prefix and two suffix. The current job name is : SPAULA1
The data area value must be :
AUTO;STNNAME==%+&COMPN*= ;
Note :
Using a generic name (user name or station name) makes it possible to configure LAUNCHER Office in unique way valid for ALL users. To do so, set up the configuration on one station and then make a copy of the user launcher.ini file in LAUNCHER Office directory.
See section : "Launcher.ini".
If any problems occur, display the PC trace and see AS/400 message file :
DSPMSG LAUNCHER/LNCMSGQ