PMDF popstore & MessageStore Manager's Guide


Previous Contents Index


TEST-Test site-supplied subroutines

Test optional, site-supplied subroutines to verify that they load and function correctly.

Syntax

TEST/BLOCK_DAYS image-spec starting-time ending-time size remainder

TEST/CONNECT image-spec starting-time ending-time

TEST/MESSAGE_MAPPING image-spec

TEST/PATHS path-file-spec

TEST/PROFILE_MAPPING image-spec

Command Qualifiers
/BLOCK_DAYS
/CONNECT
/MESSAGE_MAPPING
/PATHS
/PROFILE_MAPPING

Parameters

image-spec

Executive mode logical whose translation value is the file specification for the shareable image containing the subroutine to test.

starting-time

Starting time value to pass to the compute_connect or compute_block_days subroutine.

ending-time

Ending time value to pass to the compute_connect or compute_block_days subroutine.

size

Size value to pass to the compute_block_days subroutine.

remainder

Remainder value to pass to the compute_block_days subroutine.

path-file-spec

File specification for the file of directory paths to check.

Description

The TEST command provides a mechanism to test site-supplied subroutines intended for use with the popstore. The purpose and usage of those subroutines is described in Chapter 14. Note that the shareable image containing the subroutine to be tested must be installed as a known image with the DCL INSTALL CREATE command. Moreover, an executive mode logical must be used to reference the image. The name of that logical is specified with the image-spec parameter. And, any logical referenced by that logical must also be an executive mode logical. These requirements are OpenVMS requirements and are enforced by LIB$FIND_IMAGE_SYMBOL , the run-time library subroutine used by the popstore to dynamically load and link to the subroutine. Note that if you use the TEST command and then subsequently change your subroutine, then you will need to exit the utility and restart it before you can retest your subroutine. This is because LIB$FIND_IMAGE_SYMBOL won't reload the subroutine a second time. Also, when rebuilding a shareable image, be sure to use the DCL INSTALL REPLACE command to install the new version of the image. The TEST/MESSAGE_MAPPING and TEST/PROFILE_MAPPING commands test, respectively, map_message_filename and map_profile_filename subroutines. The command will load the subroutine from the specified image and then, for each stored message or profile file, run the filename through the subroutine. The input and output file names for each file will be displayed along with diagnostic information, should an error occur. The TEST/CONNECT and TEST/BLOCK_DAYS commands test, respectively, the compute_connect and compute_block_days subroutines. With each command, you can specify the values of the input arguments to be passed to those subroutines. The results produced by the subroutine will then be displayed. Should an error occur, diagnostic information will be displayed. Text files intended for use as PMDF_TABLE:popstore_message_paths. or PMDF_TABLE:popstore_profiles_paths. files can be tested with the TEST /PATHS command. The command will scan the directory trees listed in the specified file, displaying the files found in each directory tree.

Command Qualifiers

/BLOCK_DAYS

Test the compute_block_days subroutine from the shareable image image-spec.

/CONNECT

Test the compute_connect subroutine from the shareable image image-spec.

/MESSAGE_MAPPING

Test the map_message_filename subroutine from the shareable image image-spec.

/PROFILE_MAPPING

Test the map_profile_filename subroutine from the shareable image image-spec.

/PATHS

List the files from the directory trees specified in the path file path-file-spec.

Examples

In the following example, the map_profile_filename subroutine of Example 14-5 is tested with the TEST/PROFILE_MAPPING command on an OpenVMS Alpha system.


$ DEFINE/SYSTEM/EXECUTIVE_MODE POP_MAP_PROFILES -
_$      DISK3:[IMAGES]MAP_PROFILES.EXE
$ CC MAP_PROFILES.C
$ LINK/SHAREABLE=POP_MAP_PROFILES MAP_PROFILES.OBJ,SYS$INPUT:/OPT
SYMBOL_VECTOR=(map_profile_filename=PROCEDURE)
[CTRL/Z]
$ INSTALL CREATE POP_MAP_PROFILES
$ PMDF POPSTORE
popstore> TEST/PROFILE_MAPPING POP_MAP_PROFILES
PMDF_POPSTORE_PROFILES:[C.R.W]CRW.;1 -> DISK0:[PROFILES.C.R.W]CRW.; 
PMDF_POPSTORE_PROFILES:[D.A.D]DAVID.;1 -> DISK0:[PROFILES.D.A.D]DAVID.; 
PMDF_POPSTORE_PROFILES:[D.A.N]DAN.;1 -> DISK0:[PROFILES.D.A.N]DAN.; 
PMDF_POPSTORE_PROFILES:[D.E.T]DEFAULT.;1 -> DISK0:[PROFILES.D.E.T]DEFAULT.; 
PMDF_POPSTORE_PROFILES:[K.E.N]KEVIN.;1 -> DISK0:[PROFILES.K.E.N]KEVIN.; 
PMDF_POPSTORE_PROFILES:[K.R.N]KRISTIN.;1 -> DISK0:[PROFILES.K.R.N]KRISTIN.; 
PMDF_POPSTORE_PROFILES:[P.E.E]PEKIE.;1 -> DISK1:[PROFILES.P.E.E]PEKIE.; 
PMDF_POPSTORE_PROFILES:[T.E.T]TEST.;1 -> DISK1:[PROFILES.T.E.T]TEST.; 
popstore> 


Previous Next Contents Index