DEFINIR TERMINAL CONTROLADOR EN OS4690 V6R1 (ENTORNO GUI)

Definir que el controlador alterno también es una terminal TPOS. Sera

el TPOS No. 1, Crear disco Enhanced RAM Disk Q:
Desde el menú principal seleccionar.

4 Ayudas de Instalación y Actualización

1 Cambiar Datos de Configuración
2 Configuración de controlador
Y ENTER
2 2 ENTER
MAESTRO SM ENTER
MAESTRO ALTERNATIVO MS ENTER

[x] Características del controlador ENTER

El controlador de tienda MS es un modelo que puede servir

Como terminal/controlador Y será utilizado de tal modo ( 1 = Sí, 2 = No) 1

Entre el número de terminal de este controlador/terminal (1 - 999) 1

Cuando se enciende o reinicia, un controlador/terminal 1 1 = Terminal

Puede empezar en una de estas modalidades. 2 = Controlador
Seleccione la modalidad.

[x] Disco RAM

Enhanced RAM Disk Q: [x] Create RAM DISK Disk Size (MB) 200

[X] Nombre de Archivos Lógicos de Usuario

Crear los siguientes nombres lógicos

TERMJAVA 2
HOSTNAME HS (Id del controlador alterno)

Activar Configuración del Controlador Alterno

4 Ayudas de Instalación y Actualización
1 Cambiar Datos de Configuración
4 Activar configuración
2 Configuración del Controlador (Reiniciar controladores CTRL + ALT + DEL)
Crear una Definición de Carga para el Terminal/Controlador
4 Ayudas de Instalación y Actualización
1 Cambiar Datos de Configuración
5 Config. terminal genérico

[X] Device Characteristics

NEW [TERMCONT - Terminal/Controlador]

Cambiar estos parámetros

Java Redirection [X] Enable Advanced Java Redirection

RAM Disks [X] Create RAM Disk X
Disk size in 32K blocks (1-1960): 1000
Number of directory entries (1-64): 64

[X] Java Applications (* Ver Anexo A de como instalar los paquetes de precarga).
Asegurarse que las siguientes aplicaciones estén definidas.
SAOPER - SA SI Operator GUI
SACUST - SA SI Customer GUI
SADD - SA DualDisplay GUI
SACTOPER - SA C/T Operator GUI
SACTCUST - SA C/T Customer GUI
SACTDD - SA C/T Dual Display GUI
SACUST2 - SA SI Customer GUI II

[X] Preload Bundles (Ver Anexo A de como instalar los paquetes de precarga).
Asegúrese que los siguientes paquetes de precarga existen.
PRO - Property files
SVUSER - USER Files
SAJARS - Application JARS
ELITE - Browser JARS
4690JARS - 4690 JARS
AEFJARS - AEF Application JARS
COMMON - Common JARS

[X] Load Definitions

“Select the load definitions to work with” 001 NEW

Select a "Device Characteristics" name for this load definition:

[TERMCONT - Terminal/Controlador]

Java Applications

Select the type of Java application to configure:

[Java 2 +]
 Select a Primary Application:
[SACUST - SA SI Customer GUI +]
Select the Secondary Applications:
┌---------------------------------|
+ SAOPER - SA SI Operator GUI +
+ SACUST - SA SI Customer GUI +
+ SADD - SA DualDisplay GUI +
+ SACTOPER - SA C/T Operator GUI +
+ SACTCUST - SA C/T Customer GUI +
└--------------------------------+|
Preload to drive:
Q+ [Importante tiene que ser el disco Q]
JVM Preload Select a drive to preload the JVM onto: Q

Preload BUNDLES

DRIVE Q PRO - Property files

SVUSER - USER Files
Add=> SAJARS - Application JARS
ELITE - Browser JARS
4690JARS - 4690 JARS
AEFJARS - AEF Application JARS
COMMON - Common JARS

Activar Configuración del Terminal

4 Ayudas de Instalación y Actualización
1 Cambiar Datos de Configuración
4 Activar configuración
1 Configuración del Terminal (Apagar/Encender Terminal/Controlador)

Asegurarse que el Terminal/Controlador No. 001 esté Asignado al

Controlador Alterno
4 Ayudas de Instalación y Actualización
1 Cambiar Datos de Configuración
3 Configuración del sistema
System Settings
LAN TERMINAL DEFINICION
Primary Controller MS
Backup Controller SM
Activar Configuración del Sistema
4 Ayudas de Instalación y Actualización
1 Cambiar Datos de Configuración
4 Activar configuración
3 Configuración del Sistema

Reiniciar todos los terminales/ Todos los Controladores de Tienda.

Modificar el archivo HOST (ADX_SDT1: ADXHSIHF.DAT)

Se debe agregar las IP de los controladores Alterno MS y Maestro SM. Agregar la IP ADDRESS
LOCALHOST también asignada a 127.0.0.1.

# hosts file
#
# This file contains the mapping of IP addresses to host names.
# The format of a host entry is the IP address followed by at
# least one space, then the host name. Each entry is entered
# on a separate line.
#
# IP addresses can be specified as decimal, hexadecimal, or octal.
# A leading '0x' indicates hex. A leading '0' indicates octal.
# Anything else indicates decimal. For example, the following three
# IP addresses are identical:
# 9.67.39.83 = 0x9.0x43.0x27.0x53 = 011.0103.047.0123
#
# Comments may be included denoted by the '#' symbol.
#
# Example entries are shown below:
# 192.168.1.1 cc # 4690 controller CC
# 10.1.1.3 store1.test.com # store1 host
#

127.0.0.1 localhost
192.168.100.100 SM
192.168.100.101 MS
ANEXO A
Use of logical name TERMJAVA to reduce the amount of
memory needed to load terminals

Technote (FAQ)

Question
Terminals get into a dump loop during loading and U007 displays briefly.

Cause
The terminal is running out of memory during terminal load.

Answer
Define TERMJAVA as follows:

 0 - The terminal will not load any Java™ components.

 1 - The terminal will load Java 11.
 2 - The terminal will load Java 2.

If you do not need Java in the terminal, set TERMJAVA2 to 0 because this
requires less memory during terminal load. Implement the change as
follows:

1. Define the logical name3 on all of your controllers.

2. Activate the configuration.
3. Reboot the controllers.

Note 1: Using this logical name will not reduce terminal memory use for
normal operations. It only reduces the amount of memory needed for
loading.

Note 2: For Java 2, the preferred method of loading the JVM is with preload
bundles.

Note 3: The TERMJAVA logical name should not be used with Java 5 on V6.

1
Java 1 is no longer supported as of September 1, 2006. It has not been
removed from 4690 Operating System Version 5 and earlier, but Java 1 is no
longer shipped with Version 6. TERMJAVA = 1 on Version 6 will cause a
terminal load shrink build failure.
2
The 4690 OS Programming Guide describes the use of TERMJAVA in the
section titled "Differences between Java1 and Java2."
3
For further information about creating user logical names, see the
Knowledgebase article "How to create a controller user logical name with the
4690 Operating System."
How to create a controller User Logical Name with the 4690
Operating System

Technote (FAQ)

Question
This article explains the procedure for creating a controller User Logical
Name with the 4690 Operating System.

Answer
To create one of these names, use the following information as a guide.
User Logical Names for the 4690 Controller are created using Controller
Configuration. When creating a User Logical Name in order to activate some
option on a controller, create that User Logical Name on each and every
controller where the option should be activated. Therefore, modifying each
controller's configuration is needed. After modifying the controllers'
configuration, activate controller configuration and re-IPL the controllers.
Use the following detailed procedure to create a User Logical Name:

1. Select option 4, Installation and Update Aids from the System Main
Menu on the acting Master Controller.
2. Select option 1, Change Configuration Data from the Installation and
Update Aids Menu.
3. Select option 2, Controller Configuration from the Configuration
Menu.
4. If running a controller that has Multiple Controller Feature, answer Y
to the question "Are you configuring a Store System that uses the
IBM Multiple Controller Feature (LAN) to support the Data
Distribution Application?" and press ENTER.
5. Answer the questions about the LAN media type and the TCC media
type, then press ENTER.
6. Press ENTER on the screen that requires entering the store
controller IDs.
7. Select the controller whose configuration to be changed and press
ENTER.
8. Tab down and place an X next to the User Logical File Names
option and press ENTER.
9. Select option 1, Define A Logical File Name.
10. Enter the logical file name. If the name begins with the letters ADX,
there will be a prompt to confirm the request to use a reserved IBM
system name. Enter Y.
11. Enter the value requested to assign to the logical name. All logical
names must have a value of some sort, so if the logical name that is
created does not need a specific value, enter any valid characters.
Press ENTER.
12. To create this logical name for any additional controllers, press PF3
two times to return to the screen that lists all the defined controller
node IDs. Then repeat steps 7 through 11 for each additional
controller.
13. When finished creating the logical name for all controllers, press the
ESCAPE key to return to the Configuration Main Menu screen.
14. Select option 4, Activate Configuration.
15. Select option 2, Controller Configuration.
16. When the configuration has been activated, re-IPL all of the
controllers to put the new User Logical Name into effect.
Using 4690 OS V4 advanced Java configuration and
bundling instead of .rsp files
PAQUETES DE PRECARGA

Flash (Alert)

Abstract
With the introduction of Version 4 of IBM® 4690 Operating System comes a
new enhancement that enables users of the IBM Store Integrator GUI to skip
running the TOF.BAT utility when making changes to the operating system,
the base application, or the Store Integrator GUI. No longer will it be
required to run TOF or TOFLite and reload the terminals.

This new functionality enables the user to define bundles of files to be

preloaded to the terminal when it is powered off and back on or reloaded.
These bundles contain the files that would normally be included when
running TOF or TOFLite. As part of the new function, the need to run TOF or
TOFLite is completely eliminated.

There are several advantages to using this new enhancement. Previously,

running TOF (20+ minutes) or TOFLite (5-8 minutes) and then reloading the
terminals might take 10-30 minutes. When implementing this new
enhancement, the customer will now be able to fully load a GUI terminal in
as little as 3-5 minutes. Instead of running TOF or TOFLite, the customer
runs ADXPLDRB in command mode and the terminals are reloaded.
Depending on how you decide to bundle your files, terminal reloading can
take as little as 3 minutes.

The other advantage to using this feature revolves around full Java™ 2
multiapp support. With the old method, some Java 2 classes were not
accessible when offline. This solution eliminates that issue.

The savings mentioned above are realized through the concept of bundling.
When the ADXPLDRB command line program is run, it compares the files in
each bundle to the files on the controller. If any of the files in the bundle has
changed, the bundle is rebuilt. If there are no changes, the bundle is
skipped. It is advantageous to create a bundle with modules that change
often and bundles with modules that are changed less frequently.

The following documents list the configuration changes that are required to
successfully use the new enhancement. You should download the appropriate
ADXJAV?F files (based on the application you are using) and the Microsoft®
Word document. The ADXJAV?F files are inactive Java application and
preload bundle configurations. If you already have any user Java applications
defined, you will need to merge the attached files with your current Java
applications. These steps are used in place of selecting Legacy Java
Application (which is where you would define a specific response file). In the
future, the concept of reading the following information from files will be
implemented (a further time savings in setup and maintenance).