Switching Between Live and Test - Revision history

Johno: /* Using -b and -uprofile */

2023-01-20T17:23:01Z

‎Using -b and -uprofile

>Johno: /* Using -b and -uvmgrfile */

2020-07-09T17:23:36Z

‎Using -b and -uvmgrfile

>Johno: /* Switching to the EOM Databases using $LOGNAME */

2020-07-09T17:21:58Z

‎Switching to the EOM Databases using $LOGNAME

>Johno: /* Using $LOGNAME as the Profile */

2020-07-09T17:21:35Z

‎Using $LOGNAME as the Profile

>Johno: /* Using $LOGNAME as the Profile */

2020-07-08T22:06:51Z

‎Using $LOGNAME as the Profile

>Johno at 21:36, 8 July 2020

2020-07-08T21:36:34Z

>Johno at 21:34, 8 July 2020

2020-07-08T21:34:41Z

>Johno at 21:25, 8 July 2020

2020-07-08T21:25:34Z

>Johno: Created page with "== Spectrum Clients == Switching the login of a job from bolive to botest may not be sufficient to have the job execute as expected. The exact behavior depends on the run line..."

2020-07-08T21:19:36Z

Created page with "== Spectrum Clients == Switching the login of a job from bolive to botest may not be sufficient to have the job execute as expected. The exact behavior depends on the run line..."

New page

== Spectrum Clients ==
Switching the login of a job from bolive to botest may not be sufficient to have the job execute as expected. The exact behavior depends on the run line options that are specified:
=== Using -b Only ===
Generally speaking, there are no special considerations when the job does not use '''-aprofile''' or '''-uvmgrfile'''. Provided the login user has access to the specified files and directories everything should work as expected. When opening Eloquence databases, AskPlus will use the default setting for EQ_DBSERVER which is typically set in the user's .profile file.
=== Using -b and -uprofile ===
Jobs using '''-aprofile''' will typically need to have the profile name changed when the job login is changed from bolive to botest. Most profiles contain a '''directory=''' statement and an '''EQ_DBSERVER''' statement. It is important that the settings for these and other options accurately reflect the login user. Jobs that login as botest should open a test instance of the database and create files in a directory configured for testing. Thus a production job will look like this:
<pre>
# Job logging in as bolive
...
/ASKPLUS/askplus -b -asummit_live << EOD
...
EOD
</pre>
And a test job will look like this:
<pre>
# Job logging in as botest
...
/ASKPLUS/askplus -b -asummit_test << EOD
...
EOD
</pre>
=== Using $LOGNAME as the Profile ===
A good solution to this problem is to create VsrvTcp profiles for bolive, botest and any other logins your job might use like botrain. Once you have created the appropriate VsrvTcp profiles, the following syntax will work.
<pre>
# Job logging in as bolive or botest
...
/ASKPLUS/askplus -b -a${LOGNAME} << EOD
...
EOD
</pre>
=== Switching to the EOM Databases using $LOGNAME ===
To access the EOM databases, create profiles called bolive_eom and botest_eom. Then use the following syntax:
<pre>
# Job logging in as bolive or botest
...
/ASKPLUS/askplus -b -a${LOGNAME}_eom << EOD
...
EOD
</pre>
Simply adding '''_eom''' to the profile name will access either bolive_eom or botest_eom.

@@ Line 51: / Line 51: @@
 </pre>
 *Remember when the job uses '-uvmgefile''' and not '''-aprofile''' none of the settings from your VsrvTcp profiles will be used.
-*If your VsrvTcp profiles contain settings required by your jobs, it is best to use the '''-a$LOGNAME''' approach as described above.
+*If your VsrvTcp profiles contain settings required by your jobs, it is best to use the '''-a$SPXLOGIN''' approach as described above.

@@ Line 21: / Line 21: @@
 </pre>
 ==== Using $LOGNAME as the Profile ====
-A good solution to this problem is to create VsrvTcp profiles for bolive, botest and any other logins your job might use like botrain.  Once you have created the appropriate VsrvTcp profiles, the following syntax will work and no changes are needed to the profile name.
+A good solution to this problem is to create VsrvTcp profiles for bolive, botest and any other logins your job might use like botrn.  Once you have created the appropriate VsrvTcp profiles, the following syntax will work and no changes are needed to the profile name.
 <pre>
 # Job logging in as bolive or botest
@@ Line 29: / Line 29: @@
 EOD
 </pre>
 ==== Switching to the EOM Databases using $LOGNAME ====
 To access the EOM databases, create profiles called bolive_eom and botest_eom. Then use the following syntax:

@@ Line 21: / Line 21: @@
 </pre>
 ==== Using $LOGNAME as the Profile ====
-A good solution to this problem is to create VsrvTcp profiles for bolive, botest and any other logins your job might use like botrain.  Once you have created the appropriate VsrvTcp profiles, the following syntax will work.
+A good solution to this problem is to create VsrvTcp profiles for bolive, botest and any other logins your job might use like botrain.  Once you have created the appropriate VsrvTcp profiles, the following syntax will work and no changes are needed to the profile name.
 <pre>
 # Job logging in as bolive or botest

@@ Line 38: / Line 38: @@
 EOD
 </pre>
-Simply adding '''_eom''' to the profile name will access either bolive_eom or botest_eom.
+*Adding '''_eom''' to the profile name will access either bolive_eom or botest_eom.
 === Using -b and -uvmgrfile ===

@@ Line 3: / Line 3: @@
 === Using -b Only ===
 Generally speaking, there are no special considerations when the job does not use '''-aprofile''' or '''-uvmgrfile'''.  Provided the login user has access to the specified files and directories everything should work as expected. When opening Eloquence databases, AskPlus will use the default setting for EQ_DBSERVER which is typically set in the user's .profile file.
-=== Using -b and -uprofile ===
+=== Using -b and -aprofile ===
 Jobs using '''-aprofile''' will typically need to have the profile name changed when the job login is changed from bolive to botest. Most profiles contain a '''directory=''' statement and an '''EQ_DBSERVER''' statement.  It is important that the settings for these and other options accurately reflect the login user.  Jobs that login as botest should open a test instance of the database and create files in a directory configured for testing. Thus a production job will look like this:
 <pre>

@@ Line 20: / Line 20: @@
 EOD
 </pre>
-==== Using $LOGNAME as the Profile ====
+==== Using $SPXLOGIN as the Profile ====
 A good solution to this problem is to create VsrvTcp profiles for bolive, botest and any other logins your job might use like botrn.  Once you have created the appropriate VsrvTcp profiles, the following syntax will work and no changes are needed to the profile name.
 <pre>
 # Job logging in as bolive or botest
 ...
-/ASKPLUS/askplus -b -a${LOGNAME} << EOD
+/ASKPLUS/askplus -b -a${SPXLOGIN} << EOD
 ...
 EOD