RD/EE Controls<P> EPICURE Software Release Note 121.0<P> <b> Updating some shared libraries</b>

RD/EE Controls

EPICURE Software Release Note 121.0

Updating some shared libraries

Debra S. Baddorf

STATICLIB

When a new version of the STATICLIB has been tested and updated, Kal usually just sends me mail saying that the staticlib has been updated. What he means is that the version in EPICURE_WORK has been updated. You need to copy his working version to the official static library, and then copy that to all other nodes. The following should be done from a SYSMANAGER account. You may need to know that ``STATICLIB'' is a logical which points to the file, so copying to ``STATICLIB'' will get it to the right place, but only on the local machine. You must use the destination name on the remote nodes (in the MCOPY command) or it won't work correctly.

$ COPY/LOG

_From: EPICURE_ROOT:[WORK.STATICLIB]STATICLIB.TLB

_To: STATICLIB

$ MCOPY STATICLIB RDCU_USERS_LIBRARIES_ROOT:[STATICLIB]

answer N (not whole list)

answer Y to MICKEY

answer N to MINNIE (same disk, USR$DISK1; don't need two copies)

answer N to HYDRA (hasn't got EPICURE on it)

answer N to ARDYH (hasn't got EPICURE on it)

answer Y to all the rest by typing about 10 or 11 carriage returns to take the default YES.

Remember to READ the messages as they go by, to make sure that it has correctly copied the file to all the nodes. For instance, if one node is down, it is up to YOU to remember to copy to that node later when the node is up. Make yourself a reminder of some sort, and DO copy it later!

APPLICATIONS_HELPLIB

About:

This library is accessed by ESM, though anyone can access it manually by typing
$ HELP /LIBRARY=APPLICATIONS_HELPLIB
For ESM's sake, each module must have the same name as the executable file for the application. Capitalization does not matter, and has thus far been left up to the author of the help module. For instance, current module names include
91Page ALCON Almdisp ASB_Report DB_History PAGE
and others. This help information is what you get when you press HELP while running a program built upon ESM. The help info is not stored in the program itself, but is submitted separately and inserted into the applications help library by the system manager (currently).

Programmer:

The text file supplied by the programmer should look similar to the file used for the general overview topic:
(WARNER::)RDCU_USERS_LIBRARIES_ROOT:[HELPLIB]GENERAL_OVERVIEW.HLP
To understand the numbering, try out the HELP command above to see how this text file translates into help information. You need a level 1 topic, with the number 1 in column one and the rest of the text indented. Keep the text less than 65 characters across, if possible, since HELP will indent it some more. The next level topics should have a number 2 in column one. Further sub-topics are numbered 3 through 9, and must immediately follow the level to which they are subsidiary. See the VMS Librarian Utility manual for more information (currently volume M-2B).

System Manager:

The commands needed for the system manager to update the help library follow. The help text file must be specified by the programmer; for this example it is ALCON.HLP in

EPICURE_ROOT:[WORK.ALCON]. First, test the text file to make sure the format is correct.

$ LIBRARY/HELP/CREATE MYHELP.TMP EPICURE_ROOT:[WORK.ALCON]ALCON.HLP

$ HELP /LIBRARY=mydisk:[mydir]MYHELP.TMP

The second line looks at the help library you've just created. Scan through the help topics to be sure they look alright. You need to specify the disk and directory on the HELP command otherwise it will look for your MYHELP.TMP file in the system help area and it won't find it there.

When the text file is verified, proceed to insert it into the applications help library, and then copy the library to all other nodes. You may need to know that ``APPLICATIONS_HELPLIB'' is a logical which points to the file, so copying to ``APPLICATIONS_HELPLIB'' will get it to the right place, but only on the local machine. You must use the destination name on the remote nodes (in the MCOPY command) or it won't work correctly.

$ LIBRARY/HELP/REPLACE

_Library: APPLICATIONS_HELPLIB

_File: EPICURE_ROOT:[WORK.ALCON]ALCON.HLP

$ MCOPY APPLICATIONS_HELPLIB RDCU_USERS_LIBRARIES_ROOT:[HELPLIB]

answer N (not whole list)

answer Y to MICKEY

answer N to MINNIE (same disk, USR$DISK1; don't need two copies)

answer N to HYDRA (hasn't got EPICURE on it)

answer N to ARDYH (hasn't got EPICURE on it)

answer Y to all the rest by typing about 10 or 11 carriage returns to take the default YES.

Remember to READ the messages as they go by, to make sure that it has correctly copied the file to all the nodes. For instance, if one node is down, it is up to YOU to remember to copy to that node later when the node is up. Make yourself a reminder of some sort, and DO copy it later!

Keywords: RDCS, EPICURE, libraries, STATICLIB, APPLICATIONS_HELPLIB

Distribution:

D Baddorf

J DeVoy

B Kramper

T Watts

Security, Privacy, Legal

rwest@fsus04.fnal.gov