Here is a quick guide to running disaster recovery on each platform.
On MPE the steps are:
When moving the software from one system to another in a disaster situation on MPE, note that you should do the following:
One of our tech support engineers also may have asked you to download the latest version to provide new functionality.
Please print off and follow the instructions below if this is the case.
The ability to do Disaster recovery on HP-UX was not available until Extend version 4.8. Please see the Download and detailed installation instructions below.
C:\>ftp myhpux.company.com 220 myhpux FTP server (Version 220.127.116.11 Mon Jul 10 14:16:28 GMT 2000) ready. User (myhpux.company.com:(none)): root 331 Password required for root. Password: 230 User root logged in. ftp> cd /opt/robelle/bin 250 CWD command successful. ftp> binary 200 Type set to I. ftp> put extend.hpux.bin extend ftp> quit 221 Goodbye.
-r-xr-xr-x 1 root sys 878898 Mar 14 11:57 extend
chmod 555 extend
C:\>ftp mympe.company.com User (mympe.company.com:(none)): mgr.robelle,pub 230 User root logged in. ftp> binary 200 Type set to I. ftp> put extend.mpe.bin extend;REC=128,1,F,BINARY;DISC=2845,1;CODE=1029 ftp> quit 221 Goodbye.
The Local filename should have extend.wrq.bin and the Host file name should be Extend, when you click to upload you can Purge the old version.
Typically, what is happening is a application is failing with an error calling rdtconvert, and you did the disaster, but your application either links in and xl that was not in the Robelle account or is installed in the system sl.
To determine what xl's are attached to a program you can use either linkedit/listprog or run the program with ;lmap or both if needed. If the program is a NM program then it is likely that an xl has been linked to the program for the SmartDate Intrinsic to be resolved. The listprog command in linkedit will show this list of xl's linked to a program.
linkedit HP Link Editor/iX (HP30315A.06.17) Copyright Hewlett-Packard Co 1986 LinkEd> listprog cobst2p PROGRAM : COBST2P XL LIST : MYDATEXL.PUB.GREEN CAPABILITIES : BA, IA NMHEAP SIZE : NMSTACK SIZE : ENTRY NAME : UNSAT NAME : PRIORITY : MAX PRIORITY : POSIX : NO SHARED DATA : NO TEXT SIZE : 00005D94 DATA SIZE : 00000910 VERSION : 85082112Or you can use the lmap option. This is very verbose and sometimes I capture the output and search for sdate.asm to speed things up. A portion of the output using this method is below:
run cobst2p;lmap ============================================================================ NM Program File : COBST2P.NEIL.GREEN Module Name : COBST2 FSN : 0 SOM : 0 LP : 31C.40100000 DP : 31C.41644000 Locality Name Type Address Length XL|R/W ------------- ---- ------- ------ ------ $MILLICODE$ Code 31B.5000 1610 3 $CODE$ Code 31B.6614 4088 3 $UNWIND_START$ Code 31B.A6A0 6FC 3 $GLOBAL$ Data 31C.41644000 910 3/3 EXPORTED CODE SYMBOLS ..... Entry Name Type Proc Addr Stub Addr XL/EL ============================================================================ NM Library File : MYDATEXL.PUB.GREEN Module Name : sdate.asm
As mentioned previously the Smartdate Intrinsic can be installed in a local xl, referenced directly as sdatexl.pub.robelle, or installed in the system sl. If your LMAP listing shows that the routines are resolved in the system sl, then you can stream the job:
to install the routines in the system sl.
If however, your routines are in an xl, as shown above in the LMAP and LISTPROG examples, you can see that the sdate.asm reference is in the xl MDATEXL.PUB.GREEN. You can replace the routines that have not been enabled on the disaster machine with the following linkedit commands:
:hello mgr.green,pub :linkedit >xl mydatexl >copyxl from=sdatexl.pub.robelle; replace >exitThe above copies the disastered xl into your local xl, so that your application can run with the newly enabled routines.
The obvious way to avoid having to do all of this is to simply reference the sdatexl.pub.robelle xl file directly, however, the above helps show how to locate where the routines may be in your application and how to copy to your application xl or stream the job to re-install in the system SL. If you want to keep your SmartDate intrinsics in your own application xl it is advisable to add steps or even a job to replace the sdate xl in your application xl and add this to your disaster checklist.