VMS Help  —  PMDF  POPSTORE  TEST
    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             Defaults

    /BLOCK_DAYS
    /CONNECT
    /MESSAGE_MAPPING
    /PATHS
    /PROFILE_MAPPING

1  –  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.

2  –  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 the PMDF popstore
    & MessageStore Manager's Guide. 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.

3  –  Command Qualifiers

3.1    /BLOCK_DAYS 

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

3.2    /CONNECT 

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

3.3    /MESSAGE_MAPPING 

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

3.4    /PROFILE_MAPPING 

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

3.5    /PATHS 

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

4  –  Examples 

      In the following example, the MAP_PROFILE_FILENAME subroutine
      described in the PMDF popstore & MessageStore Manager's Guide
      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>
Close Help