SNAX Creator-2 Configuration and Control Manual

Migrating from the Old Creator Process
Configuring SNAX Creator-2 With SNAX/XF
E–4 117143 SNAX Creator-2 Configuration and Control Manual
Migrating from the Old
Creator Process
This example shows how to migrate from the old Creator process (T6954) to SNAX
Creator-2 with no change to an existing SNAX/XF configuration. The example defines
one application for each startup method:
A Pathway application (with user logon mypath)
A TACL process (with user logon mytacl)
A server-started application (with user logon myprog).
A single connection is defined for all applications.
Notes:
1. On the SU object:
NAMERULE is FIRSTWORD (allowing SNAX Creator-2 to parse the SNAX/XF
CONCDATA value correctly) and PLUNAME is omitted (simplifying the
configuration).
As a result, APPL objects are named C- pluname - firstword , where pluname is
the PLUNAME value in the ESS table entry, and firstword is the first character
string up to the first blank in the CONCDATA value.
PASSWORD is optional on the SU, but if used must match the SNAX/XF value.
2. For Pathway applications:
The SNAX/XF CONCDATA value is structured as follows:
PATHWAY NAME pathmon ,PROGRAM program
where the pathmon and program values are configuration-dependent. The blanks
after the keywords and the comma between the pathmon value and PROGRAM are
required.
The example uses the [#KEYWORD] built-in function to provide the PATHMON
and program names from the SNAX/XF CONCDATA value.
The SNAX/XF APPL object may be omitted if the PLUNAME in the ESS table
entry is specified as the SU name (#cre).
3. For TACL applications, the SNAX Creator-2 APPL has METHOD TACL. When
this is specified, SNAX Creator-2 ignores the SNAX/XF APPLFILE value and
always starts $system.system.mytacl.