Difference between revisions of "UpdateMacroDefFile"

From Vital Soft Wiki
Jump to: navigation, search
>Johno
(→‎Updating the Macro Definition File)
>Johno
(→‎Updating the Macro Definition File)
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
== Updating the Macro Definition File ==
 
== Updating the Macro Definition File ==
  
−
The macro definition file is a text file that should be uploaded using an ASCII transfer.
+
The macro definition file is a text file that should be uploaded using an ASCII transfer. '''Vital Signs users should perform the test at the end of these instructions after updating the macro file.'''
 
   
 
   
 
Download the macro definition file [https://www.vital-soft.com/product-downloads/ here].
 
Download the macro definition file [https://www.vital-soft.com/product-downloads/ here].
−
:* Scroll to the bottom of the page and choose the version appropriate for AskPlus version E.8.3.3.
+
:* Scroll to the bottom of the page and choose the version appropriate for Visimage3 and AskPlus version E.8.3.3.
  
 
'''1. Transfer the file to UNIX:'''
 
'''1. Transfer the file to UNIX:'''
 
:* Transfer the '''samp''' macrodef file, using an ASCII transfer, to the /ASKPLUS/visimage directory.
 
:* Transfer the '''samp''' macrodef file, using an ASCII transfer, to the /ASKPLUS/visimage directory.
  
−
:: Using vi, verify that the file is a valid UNIX file.  In vi, you should not see any ^M characters at the end of each line.  If ^M characters appear at the end of each line, convert the file using the following commands.
+
::Using vi, verify that the file is a valid UNIX file.  In vi, you should '''not''' see any ^M characters at the end of each line.  If ^M characters appear at the end of each line, convert the file using the following commands.
  
−
::: mv macrodef_e83.samp macrodef_e83.dos
+
:::mv macrodef_e83.samp macrodef_e83.dos
−
::: dos2unix <macrodef_e83.dos >macrodef_e83.samp
+
:::dos2ux <macrodef_e83.dos >macrodef_e83.samp
  
 
'''2. Backup the old definition file and copy the new one:'''
 
'''2. Backup the old definition file and copy the new one:'''
 
:* Logon to HPUX as '''askplus'''
 
:* Logon to HPUX as '''askplus'''
−
:: cd /ASKPLUS/visimage
+
::cd /ASKPLUS/visimage
−
:: mv macrodef macrodefv26
+
::mv macrodef macrodefv26
−
:: chmod macrodef_e83.samp 644 (The downloaded macrodef file may have a different name.)
+
::cp macrodef_e83.samp macrodef (The downloaded macrodef file may have a different name.)
−
:: cp macrodef_e83.samp macrodef
+
::chown askplus macrodef (Make sure the file is owned by askplus)
 +
::chmod 644 macrodef  
  
 
'''3. Rebuild the indexed macro file used by AskPlus and Visimage:'''
 
'''3. Rebuild the indexed macro file used by AskPlus and Visimage:'''
−
:This step requires that the macro file (/ASKPLUS/visimage/macro) is '''not''' in use.  All Visimage users must exit server and no AskPlus jobs should be running.
 
 
:* While still logged in as '''askplus'''
 
:* While still logged in as '''askplus'''
−
:: cd /ASKPLUS/visimage
+
::cd /ASKPLUS/visimage
−
:: ./load_macros
+
::rm macro (if the purge fails, make sure the file is owned by askplus)
 +
::/ASKPLUS/load_macros
  
−
:If you get an error that the file is in use and cannot be created (or purged), it might be necessary to bring the listener(s) down to ensure that the file is not being accessed.   
+
::Note, Visimage users will need to restart server to see the new macro definitions.   
  
−
:*To kill the listener:
+
To test that the new setup is valid, start server from Visimage or run a test job that uses AskPlus. 
  
−
::* Login as root
+
'''Vital Signs users should run the following test:'''
−
::: /ASKPLUS/kill_vsrvtcp -stop_all
 
−
 
−
:::Note, the above command will kill all copies of the listener running on any port.
 
−
 
 
−
:::Run the '''load_macros''' script again, remember to login as the askplus user and cd visimage.
 
−
 
 
−
:* To restart the listener:
 
−
 
 
−
::* Login as root
 
−
::: /ASKPLUS/vsrvtcp -a -t –n30501 –a >/dev/null
 
−
::: /ASKPLUS/vsrvtcp_49 -a -t –n30503 –a >/dev/null
 
  
−
::: Remember to start two listeners (on two different ports) if you have users running Visimage 2.6 and Visimage3.  Use port numbers appropriate on your system.  Please note, the default port number is normally defined in '''/etc/services''' under the '''askplus''' entry.  There is no need to specify the -n parameter to start server on the default port.
 
−
 
−
To test that the new setup is valid, start server from Visimage or run a test job that uses AskPlus.  Vital Signs users should run the following test.
 
 
:* Login as bolive
 
:* Login as bolive
 
:: /VSJOBS/JVSLOAD_MBRSHLN
 
:: /VSJOBS/JVSLOAD_MBRSHLN
  
−
Once the job has started successfully and built at least one extract file successfully, kill the job, then ''clean up'' any created files as follows:
+
::Once the job has started successfully and built at least one extract file successfully, kill the job, then ''clean up'' any created files as follows:
−
:: cd /var/summit/spectrum/LIVE/vsdata/data/mbrshln  (Check /ASKPLUS/vsdata/vitalsigns.ini for the correct path)
+
:::cd /var/summit/spectrum/LIVE/vsdata/data/mbrshln  (Check /ASKPLUS/vsdata/vitalsigns.ini for the correct path)
−
:: ls (if the files are all extract files MBRFILECCYYMMDD, SHFILECCYYMMDD, etc - you are in the correct directory)
+
:::ls (if the files are all extract files MBRFILECCYYMMDD, SHFILECCYYMMDD, etc - you are in the correct directory)
−
:: rm * ('''Make sure you are in the correct location before issuing this command!''')
+
:::rm * ('''Make sure you are in the correct location before issuing this command!''')
 +
 
 +
::Contact support if you are unsure about any of these steps.

Latest revision as of 18:21, 10 November 2014

Updating the Macro Definition File

The macro definition file is a text file that should be uploaded using an ASCII transfer. Vital Signs users should perform the test at the end of these instructions after updating the macro file.

Download the macro definition file here.

  • Scroll to the bottom of the page and choose the version appropriate for Visimage3 and AskPlus version E.8.3.3.

1. Transfer the file to UNIX:

  • Transfer the samp macrodef file, using an ASCII transfer, to the /ASKPLUS/visimage directory.
Using vi, verify that the file is a valid UNIX file. In vi, you should not see any ^M characters at the end of each line. If ^M characters appear at the end of each line, convert the file using the following commands.
mv macrodef_e83.samp macrodef_e83.dos
dos2ux <macrodef_e83.dos >macrodef_e83.samp

2. Backup the old definition file and copy the new one:

  • Logon to HPUX as askplus
cd /ASKPLUS/visimage
mv macrodef macrodefv26
cp macrodef_e83.samp macrodef (The downloaded macrodef file may have a different name.)
chown askplus macrodef (Make sure the file is owned by askplus)
chmod 644 macrodef

3. Rebuild the indexed macro file used by AskPlus and Visimage:

  • While still logged in as askplus
cd /ASKPLUS/visimage
rm macro (if the purge fails, make sure the file is owned by askplus)
/ASKPLUS/load_macros
Note, Visimage users will need to restart server to see the new macro definitions.

To test that the new setup is valid, start server from Visimage or run a test job that uses AskPlus.

Vital Signs users should run the following test:

  • Login as bolive
/VSJOBS/JVSLOAD_MBRSHLN
Once the job has started successfully and built at least one extract file successfully, kill the job, then clean up any created files as follows:
cd /var/summit/spectrum/LIVE/vsdata/data/mbrshln (Check /ASKPLUS/vsdata/vitalsigns.ini for the correct path)
ls (if the files are all extract files MBRFILECCYYMMDD, SHFILECCYYMMDD, etc - you are in the correct directory)
rm * (Make sure you are in the correct location before issuing this command!)
Contact support if you are unsure about any of these steps.
Retrieved from "https://wiki.vital-soft.com/index.php?title=UpdateMacroDefFile&oldid=2340"