>Johno: Created page with "==Testing Vital Signs Script Changes== The new script files can be tested using the JVSLOAD_MBRSHLN extract job. You will need to make a few temporary changes prior to run..."

2015-09-23T18:36:35Z

Created page with "==Testing Vital Signs Script Changes== The new script files can be tested using the JVSLOAD_MBRSHLN extract job. You will need to make a few temporary changes prior to run..."

New page

==Testing Vital Signs Script Changes==

The new script files can be tested using the JVSLOAD_MBRSHLN extract job.

You will need to make a few temporary changes prior to running the job.

1. Edit vsrvtcp.ini and update one of the restore profiles:
:The standard vsdata_restore profile should look something like this:
<blockquote><pre>
[vsdata_restore]
login=botest
Directory=/var/summit/spectrum/TEST/vsdata
TEMP=/var/summit/spectrum/TEST/vsdata/temp
EQ_DBSERVER=localhost:eloq-TEST
script_path=/ASKPLUS/vsdata/scripts
custom_path=/ASKPLUS/vsdata/custom/live
Vmgr=/ASKPLUS/vsdata/custom/live/vmgr_eom
</pre></blockquote>
:Verify that the [vsdata_restore] profile exists and that it is referencing the correct Eloquence instance.

2. Edit the vitalsigns.ini file and disable the ftp process:
:Edit /ASKPLUS/vsdata/vitalsigns.ini and comment out the VS_HOSTIP
<blockquote><pre>
#VS_HOSTIP=192.168.1.79
</pre></blockquote>

3. Setup the new macro definition file:
:Replace the macro definition file with the new macrodef.samp file. There is no need to rebuild the macro file, the JVSLOAD jobs rebuild the macro file automatically each time they are run.
<blockquote><pre>
cd /ASKPLUS/visimage
cp macrodef macrodef_vs.save
cp macrodef.samp macrodef
</pre></blockquote>

4. Backup the existing scripts files and then copy the new script files in place:
<blockquote><pre>
cd /ASKPLUS/vsdata/scripts
cp VSLOAD-MBRFILE VSLOAD-MBRFILE_vs.save
cp VSLOAD-LOANFILE VSLOAD-LNFILE_vs.save
cp VSLOAD-LOOKUP VSLOAD-LOOKUP_vs.save
cp VSLOAD-MBRFILE.2015.02 VSLOAD-MBRFILE
cp VSLOAD-LNFILE.2015.02 VSLOAD-LNRFILE
cp VSLOAD-LOOKUP.2015.02 VSLOAD-LOOKUP
# Backup and copy any custom files that you edited.
</pre></blockquote>

5. Launch the JVSLOAD_MBRSHLN extract:
:Make a copy of your existing UC4 job that runs the daily JVSLOAD_MBRSHLN extract. The job needs to run using the restore parameter as follows:
<blockquote><pre>
/VSJOBS/JVSLOAD_MBRSHLN restore CYMD
# Where CYMD is today's date. For example, 20150922
</pre></blockquote>
:::Since we disabled the VS_HOSTIP in the vitalsigns.ini, the job should fail when it attempts to ftp the files to the Vital Signs server. If the job makes it to the FTP stage without any errors then the test is successful.

6. Reset the changes back for tonight's run:
:*Edit /ASKPLUS/vsdata/vitalsigns.ini and remove the comment from VS_HOSTIP.
:*Reset the macro file.
<blockquote><pre>
cd /ASKPLUS/visimage
cp macrodef_vs.save macrodef
</pre></blockquote>
:*Reset the script files.
<blockquote><pre>
cd /ASKPLUS/vsdata/scripts
cp VSLOAD-MBRFIE_vs.save VSLOAD-MBRFILE
cp VSLOAD-LNFILE_vs.save VSLOAD-LOANFILE
cp VSLOAD-LOOKUP_vs.save VSLOAD-LOOKUP
# Restore any custom files that you edited.
</pre></blockquote>

Testing Vital Signs Script Changes - Revision history

>Johno: Created page with "==Testing Vital Signs Script Changes== The new script files can be tested using the JVSLOAD_MBRSHLN extract job. You will need to make a few temporary changes prior to run..."