UpdateMacroDefFile
Revision as of 18:17, 10 November 2014 by >Johno (→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.
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!)
- 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:
- Contact support if you are unsure about any of these steps.